[www] branch stable updated (22d6d6da -> 9c7549e9)

[gnunet]

This is an automated email from the git hooks/post-receive script.

martin-schanzenbach pushed a change to branch stable
in repository www.

    from 22d6d6da add rfc9498
     add 9c7549e9 forgot file

No new revisions were added by this update.

Summary of changes:
 template/news/2023-11-RFC9498.html.j2 | 48 +++++++++++++++++++++++++++++++++++
 1 file changed, 48 insertions(+)
 create mode 100644 template/news/2023-11-RFC9498.html.j2

diff --git a/template/news/2023-11-RFC9498.html.j2 
b/template/news/2023-11-RFC9498.html.j2
new file mode 100644
index 00000000..1b00efc9
--- /dev/null
+++ b/template/news/2023-11-RFC9498.html.j2
@@ -0,0 +1,48 @@
+{% extends "common/news.j2" %}
+{% block body_content %}
+  <h1>RFC 9498: The GNU Name System</h1>
+<p>
+  We are happy to announce that our <i>The GNU Name System</i> (GNS) 
specification is now published as
+  <a href="https://www.rfc-editor.org/rfc/rfc9498.html";>RFC 9498</a>.
+</p>
+<p>
+  GNS addresses long-standing <a 
href="https://www.wired.com/2014/03/quantum/";>security</a> and
+  <a 
href="https://roarmag.org/essays/nsa-leak-domain-name-system/";>privacy</a> 
issues in the ubiquitous
+  <a href="https://www.rfc-editor.org/rfc/rfc882";>Domain Name System (DNS)</a>.
+  Previous attempts to secure DNS (<a 
href="https://www.rfc-editor.org/rfc/rfc9364";>DNSSEC</a>) fail to address <a 
href="https://www.rfc-editor.org/rfc/rfc8324";>critical security issues</a>
+  such as end-to-end security, query privacy, censorship, and centralization 
of root zone governance.
+  After 40 years of patching, it is time for a new beginning.
+</p>
+<p>
+  The GNU Name System is our contribution towards a decentralized and
+  censorship-resistant domain name resolution system that provides a
+  privacy-enhancing alternative to the Domain Name System (DNS).
+</p>
+<p>
+  As part of our work on RFC 9498, we have also contributed to the 
specification
+  of the <a href="https://www.rfc-editor.org/rfc/rfc9476.html";>.alt top-level
+  domain</a> to be used by alternative name resolution systems and have
+  established <a href="https://gana.gnunet.org/dot-alt/dot_alt.html";>the GANA 
registry for ".alt"</a>.
+</p>
+<p>
+  GNS is implemented according to RFC 9598 in GNUnet 0.20.0. It is also 
implemented
+  as part of <a href="https://git.gnunet.org/gnunet-go.git/";>GNUnet-Go</a>.
+</p>
+<p>
+  We thank all reviewers for their comments.
+  In particular, we thank D. J. Bernstein, S. Bortzmeyer, A. Farrel, E. Lear, 
and R. Salz for their insightful and detailed technical reviews.
+  We thank J. Yao and J. Klensin for the internationalization reviews.
+  We thank Dr. J. Appelbaum for suggesting the name "GNU Name System" and Dr. 
Richard Stallman for approving its use.
+  We thank T. Lange and M. Wachs for their earlier contributions to the design 
and implementation of GNS. 
+  We thank J. Yao and J. Klensin for the internationalization reviews.
+  We thank <a href="https://nlnet.nl";>NLnet</a> and <a 
href="https://nlnet.nl/project/GNS/";>NGI DISCOVERY</a> for funding work on the 
GNU Name System.
+</p>
+<p>
+  The work does not stop here: We encourage further implementations of RFC 9498
+  to learn more both in terms of technical documentation and actual deployment
+  experiences.
+  Further, we are currently working on the specification of the
+  <a href="https://lsd.gnunet.org/lsd0004";>R<sup>5</sup>N DHT</a> and <a 
href="https://lsd.gnunet.org/lsd0003";>BFT Set Reconciliation</a> which are 
underlying
+  building blocks of GNS in GNUnet and not covered by RFC 9498.
+</p>
+{% endblock body_content %}

-- 
To stop receiving notification emails like this one, please contact
gnunet@gnunet.org.