diff options
Diffstat (limited to 'template/news/2023-11-RFC9498.html.j2')
| -rw-r--r-- | template/news/2023-11-RFC9498.html.j2 | 48 |
1 files changed, 48 insertions, 0 deletions
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 @@ | |||
| 1 | {% extends "common/news.j2" %} | ||
| 2 | {% block body_content %} | ||
| 3 | <h1>RFC 9498: The GNU Name System</h1> | ||
| 4 | <p> | ||
| 5 | We are happy to announce that our <i>The GNU Name System</i> (GNS) specification is now published as | ||
| 6 | <a href="https://www.rfc-editor.org/rfc/rfc9498.html">RFC 9498</a>. | ||
| 7 | </p> | ||
| 8 | <p> | ||
| 9 | GNS addresses long-standing <a href="https://www.wired.com/2014/03/quantum/">security</a> and | ||
| 10 | <a href="https://roarmag.org/essays/nsa-leak-domain-name-system/">privacy</a> issues in the ubiquitous | ||
| 11 | <a href="https://www.rfc-editor.org/rfc/rfc882">Domain Name System (DNS)</a>. | ||
| 12 | 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> | ||
| 13 | such as end-to-end security, query privacy, censorship, and centralization of root zone governance. | ||
| 14 | After 40 years of patching, it is time for a new beginning. | ||
| 15 | </p> | ||
| 16 | <p> | ||
| 17 | The GNU Name System is our contribution towards a decentralized and | ||
| 18 | censorship-resistant domain name resolution system that provides a | ||
| 19 | privacy-enhancing alternative to the Domain Name System (DNS). | ||
| 20 | </p> | ||
| 21 | <p> | ||
| 22 | As part of our work on RFC 9498, we have also contributed to the specification | ||
| 23 | of the <a href="https://www.rfc-editor.org/rfc/rfc9476.html">.alt top-level | ||
| 24 | domain</a> to be used by alternative name resolution systems and have | ||
| 25 | established <a href="https://gana.gnunet.org/dot-alt/dot_alt.html">the GANA registry for ".alt"</a>. | ||
| 26 | </p> | ||
| 27 | <p> | ||
| 28 | GNS is implemented according to RFC 9598 in GNUnet 0.20.0. It is also implemented | ||
| 29 | as part of <a href="https://git.gnunet.org/gnunet-go.git/">GNUnet-Go</a>. | ||
| 30 | </p> | ||
| 31 | <p> | ||
| 32 | We thank all reviewers for their comments. | ||
| 33 | In particular, we thank D. J. Bernstein, S. Bortzmeyer, A. Farrel, E. Lear, and R. Salz for their insightful and detailed technical reviews. | ||
| 34 | We thank J. Yao and J. Klensin for the internationalization reviews. | ||
| 35 | We thank Dr. J. Appelbaum for suggesting the name "GNU Name System" and Dr. Richard Stallman for approving its use. | ||
| 36 | We thank T. Lange and M. Wachs for their earlier contributions to the design and implementation of GNS. | ||
| 37 | We thank J. Yao and J. Klensin for the internationalization reviews. | ||
| 38 | 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. | ||
| 39 | </p> | ||
| 40 | <p> | ||
| 41 | The work does not stop here: We encourage further implementations of RFC 9498 | ||
| 42 | to learn more both in terms of technical documentation and actual deployment | ||
| 43 | experiences. | ||
| 44 | Further, we are currently working on the specification of the | ||
| 45 | <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 | ||
| 46 | building blocks of GNS in GNUnet and not covered by RFC 9498. | ||
| 47 | </p> | ||
| 48 | {% endblock body_content %} | ||