commit 518369161f62b33412e1d5e409fa207bee92edbe
parent de531dc8dd16d77eab8905172ea3dedfdb183b6f
Author: Schanzenbach, Martin <mschanzenbach@posteo.de>
Date: Sun, 8 Sep 2019 11:30:31 +0200
update
Diffstat:
2 files changed, 251 insertions(+), 1 deletion(-)
diff --git a/draft-schanzen-gns.txt b/draft-schanzen-gns.txt
@@ -0,0 +1,224 @@
+
+
+
+
+Independent Stream M. Schanzenbach
+Internet-Draft GNUnet e.V.
+Intended status: Informational July 23, 2019
+Expires: January 24, 2020
+
+
+ The GNU Name System Specification
+ draft-schanzen-gns-00
+
+Abstract
+
+ This document contains the GNU Name System (GNS) technical
+ specification.
+
+Status of This Memo
+
+ This Internet-Draft is submitted in full conformance with the
+ provisions of BCP 78 and BCP 79.
+
+ Internet-Drafts are working documents of the Internet Engineering
+ Task Force (IETF). Note that other groups may also distribute
+ working documents as Internet-Drafts. The list of current Internet-
+ Drafts is at https://datatracker.ietf.org/drafts/current/.
+
+ Internet-Drafts are draft documents valid for a maximum of six months
+ and may be updated, replaced, or obsoleted by other documents at any
+ time. It is inappropriate to use Internet-Drafts as reference
+ material or to cite them other than as "work in progress."
+
+ This Internet-Draft will expire on January 24, 2020.
+
+Copyright Notice
+
+ Copyright (c) 2019 IETF Trust and the persons identified as the
+ document authors. All rights reserved.
+
+ This document is subject to BCP 78 and the IETF Trust's Legal
+ Provisions Relating to IETF Documents
+ (https://trustee.ietf.org/license-info) in effect on the date of
+ publication of this document. Please review these documents
+ carefully, as they describe your rights and restrictions with respect
+ to this document. Code Components extracted from this document must
+ include Simplified BSD License text as described in Section 4.e of
+ the Trust Legal Provisions and are provided without warranty as
+ described in the Simplified BSD License.
+
+
+
+
+
+
+Schanzenbach Expires January 24, 2020 [Page 1]
+
+Internet-Draft The GNU Name System July 2019
+
+
+Table of Contents
+
+ 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
+ 2. Resource Records . . . . . . . . . . . . . . . . . . . . . . 2
+ 2.1. Wire format . . . . . . . . . . . . . . . . . . . . . . . 2
+ 2.2. Examples . . . . . . . . . . . . . . . . . . . . . . . . 3
+ 2.3. Serialization format . . . . . . . . . . . . . . . . . . 3
+ 2.4. Internationalization and Character Encoding . . . . . . . 3
+ 2.5. Security Considerations . . . . . . . . . . . . . . . . . 3
+ 3. Record Resolution . . . . . . . . . . . . . . . . . . . . . . 3
+ 4. Namespace Revocation . . . . . . . . . . . . . . . . . . . . 4
+ 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4
+ 6. Normative References . . . . . . . . . . . . . . . . . . . . 4
+ Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 4
+
+1. Introduction
+
+ This document contains the GNU Name System (GNS) technical
+ specification for secure, censorship-resistant and decentralised name
+ resolution.
+
+ This document defines the normative wire format of resource records,
+ resolution processes, cryptographic routines and security
+ considerations for use by implementors.
+
+2. Resource Records
+
+2.1. Wire format
+
+ TODO
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+Schanzenbach Expires January 24, 2020 [Page 2]
+
+Internet-Draft The GNU Name System July 2019
+
+
+ A GNS resource record has the following format:
+
+ 0 1 2 3 4 5 6 7
+ +-----+-----+-----+-----+-----+-----+-----+-----+
+ | SIGNATURE |
+ | |
+ | |
+ | |
+ +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
+ | PUBLIC KEY |
+ | |
+ +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
+ | SIZE |
+ +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
+ | PURPOSE |
+ | |
+ +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
+ | EXPIRATION |
+ +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
+ / RDATA /
+ / /
+ +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
+
+ Figure 1
+
+2.2. Examples
+
+ TODO
+
+2.3. Serialization format
+
+ TODO (Is this not the same as wire format?)
+
+2.4. Internationalization and Character Encoding
+
+ TODO
+
+2.5. Security Considerations
+
+ TODO
+
+3. Record Resolution
+
+ TODO
+
+
+
+
+
+
+
+Schanzenbach Expires January 24, 2020 [Page 3]
+
+Internet-Draft The GNU Name System July 2019
+
+
+4. Namespace Revocation
+
+ TODO
+
+5. IANA Considerations
+
+ This will be fun
+
+6. Normative References
+
+ [RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform
+ Resource Identifier (URI): Generic Syntax", STD 66,
+ RFC 3986, DOI 10.17487/RFC3986, January 2005,
+ <https://www.rfc-editor.org/info/rfc3986>.
+
+Author's Address
+
+ Martin Schanzenbach
+ GNUnet e.V.
+ Boltzmannstrasse 3
+ Garching 85748
+ DE
+
+ Email: schanzen@gnunet.org
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+Schanzenbach Expires January 24, 2020 [Page 4]
diff --git a/draft-schanzen-gns.xml b/draft-schanzen-gns.xml
@@ -25,7 +25,7 @@
<organization>GNUnet e.V.</organization>
<address>
<postal>
- <street>Boltzmannstraße 3</street>
+ <street ascii="Boltzmannstrasse 3">Boltzmannstrasse 3</street>
<city>Garching</city>
<code>85748</code>
<country>DE</country>
@@ -72,6 +72,32 @@
<t>
TODO
</t>
+ <figure anchor="figure_example">
+ <preamble>A GNS resource record has the following format:</preamble>
+ <artwork>
+ 0 1 2 3 4 5 6 7
+ +-----+-----+-----+-----+-----+-----+-----+-----+
+ | SIGNATURE |
+ | |
+ | |
+ | |
+ +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
+ | PUBLIC KEY |
+ | |
+ +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
+ | SIZE |
+ +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
+ | PURPOSE |
+ | |
+ +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
+ | EXPIRATION |
+ +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
+ / RDATA /
+ / /
+ +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
+ </artwork>
+ <!-- <postamble>which is a very simple example.</postamble>-->
+ </figure>
</section>
<section anchor="examples" title="Examples">
