The GNU Name System

The GNU Name System Fraunhofer AISEC

Lichtenbergstrasse 11 Garching 85748 DE martin.schanzenbach@aisec.fraunhofer.de

Berner Fachhochschule

Hoeheweg 80 Biel/Bienne 2501 CH grothoff@gnunet.org

GNUnet e.V.

Boltzmannstrasse 3 Garching 85748 DE fix@gnunet.org

General Independent Stream name systems This document contains the GNU Name System (GNS) technical specification. GNS is a decentralized and censorship-resistant domain name resolution protocol that provides a privacy-enhancing alternative to the Domain Name System (DNS) protocols. This document defines the normative wire format of resource records, resolution processes, cryptographic routines and security considerations for use by implementers. This specification was developed outside the IETF and does not have IETF consensus. It is published here to inform readers about the function of GNS, guide future GNS implementations, and ensure interoperability among implementations including with the pre-existing GNUnet implementation.

Introduction This specification describes the GNU Name System (GNS), a censorship-resistant, privacy-preserving and decentralized domain name resolution protocol. GNS cryptographically secures the binding of names to arbitrary tokens, enabling it to double in some respects as an alternative to some of today’s public key infrastructures. In the terminology of the Domain Name System (DNS) , GNS roughly follows the idea of a local root zone deployment (see ), with the difference that the design encourages alternative roots and does not expect all deployments to use the same or any specific root zone. In the GNS reference implementation, users can autonomously and freely delegate control of names to zones through their local configurations. GNS expects each user to be in control of their setup. By following guidelines, users should manage to avoid any confusion as to how names are resolved. Name resolution and zone dissemination is based on the principle of a petname system where users can assign local names to zones. The GNS has its roots in ideas from the Simple Distributed Security Infrastructure , enabling the decentralized mapping of secure identifiers to memorable names. A first academic description of the cryptographic ideas behind GNS can be found in . This document defines the normative wire format of resource records, resolution processes, cryptographic routines and security considerations for use by implementers.

Requirements Notation The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 when, and only when, they appear in all capitals, as shown here.

Terminology

Apex Label: This type of label is used to publish resource records in a zone that can be resolved without providing a specific label. It is the GNS method to provide what is the "zone apex" in DNS . The apex label is represented using the character U+0040 ("@" without the quotes).
Application: A component which uses a GNS implementation to resolve names into records and processes its contents.
Blinded Zone Key: Key derived from a zone key and a label. The zone key and any blinded zone key derived from it are unlinkable without knowledge of the specific label used for the derivation.
Extension Label: This type of label is used to refer to the authoritative zone that the record is in. The primary use for the extension label is in redirections where the redirection target is defined relative to the authoritative zone of the redirection record (see ). The extension label is represented using the character U+002B ("+" without the quotes).
Label Separator: Labels in a name are separated using the label separator U+002E ("." without the quotes). In GNS, with the exceptions of zone Top-Level Domains (see below) and boxed records (see ), every label separator in a name indicates delegation to another zone.
Label: A GNS label is a label as defined in . Labels are UTF-8 strings in Unicode Normalization Form C (NFC) . The apex label and the extension label have special purposes in the resolution protocol which are defined in the rest of the document. Zone administrators MAY disallow certain labels that might be easily confused with other labels through registration policies (see also ).
Name: A name in GNS is a domain name as defined in : Names are UTF-8 strings consisting of an ordered list of labels concatenated with a label separator. Names are resolved starting from the rightmost label. GNS does not impose length restrictions on names or labels. However, applications MAY ensure that name and label lengths are compatible with DNS and in particular IDNA . In the spirit of , applications MAY preprocess names and labels to ensure compatibility with DNS or support specific user expectations, for example according to . A GNS name may be indistinguishable from a DNS name and care must be taken by applications and implementors when handling GNS names (see ). In order to avoid misinterpretation of example domains with (reserved) DNS domains this draft uses the suffix ".gns.alt" in examples which is also registered in the GANA ".alt Subdomains" registry (see also ).
Resolver: The component of a GNS implementation which provides the recursive name resolution logic defined in .
Resource Record: A GNS resource record is the information associated with a label in a GNS zone. A GNS resource record contains information as defined by its resource record type.
Start Zone: In order to resolve any given GNS name an initial start zone must be determined for this name. The start zone can be explicitly defined as part of the name using a zone Top-Level Domain (zTLD). Otherwise, it is determined through a local suffix-to-zone mapping (see ).
Top-Level Domain: The rightmost part of a GNS name is a GNS Top-Level Domain (TLD). A GNS TLD can consist of one or more labels. Unlike DNS Top-Level Domains (defined in ), GNS does not expect all users to use the same global root zone. Instead, with the exception of Zone Top-Level Domains (see ), GNS TLDs are typically part of the configuration of the local resolver (see ), and might thus not be globally unique.
Zone: A GNS zone contains authoritative information (resource records). A zone is uniquely identified by its zone key. Unlike DNS zones, a GNS zone does not need to have a SOA record under the apex label.
Zone Key: A key which uniquely identifies a zone. It is usually a public key of an asymmetric key pair. However, the established technical term "public key" is misleading, as in GNS a zone key may be a shared secret that should not be disclosed to unauthorized parties.
Zone Key Derivation Function: The zone key derivation function (ZKDF) blinds a zone key using a label.
Zone Master: The component of a GNS implementation which provides local zone management and publication as defined in .
Zone Owner: The holder of the secret (typically a private key) that (together with a label and a value to sign) allows the creation of zone signatures that can be validated against the respective blinded zone key.
Zone Top-Level Domain: A GNS Zone Top-Level Domain (zTLD) is a sequence of GNS labels at the end of a GNS name which encodes a zone type and zone key of a zone (see ). Due to the statistical uniqueness of zone keys, zTLDs are also globally unique. A zTLD label sequence can only be distinguished from ordinary TLD label sequences by attempting to decode the labels into a zone type and zone key.
Zone Type: The type of a GNS zone determines the cipher system and binary encoding format of the zone key, blinded zone keys, and cryptographic signatures.

Overview GNS exhibits the three properties that are commonly used to describe a petname system:

Global names through the concept of zone top-level domains (zTLDs): As zones can be uniquely identified by their zone key and are statistically unique, zTLDs are globally unique mappings to zones. Consequently, GNS domain names with a zTLD suffix are also globally unique. Names with zTLDs suffixes are not human-readable.
Memorable petnames for zones: Users can configure local, human-readable references to zones. Such petnames serve as zTLD monikers which provide convenient names for zones to the local operator. The petnames may also be published as suggestions for other users searching for good label to use when referencing the respective zone.
A secure mapping from names to records: GNS allows zone owners to map labels to resource records or to delegate authority of names in the subdomain induced by a label to other zones. Zone owners MAY choose to publish this information to make it available to other users. To publishing mappings, mappings MUST be signed and encrypted using keys derived from the respective label. When names are resolved, signatures on resource records including delegations MUST be verified by the implementation.

In the remainder of this document, the "implementer" refers to the developer building a GNS implementation including the resolver, zone master, and supporting configuration such as start zones (see ).

Names and Zones It follows from the above that GNS does not support names which are simultaneously global, secure and human-readable. Instead, names are either global and not human-readable or not globally unique and human-readable. An example for a global name pointing to the record "example" in a zone is: example.000G006K2TJNMD9VTCYRX7BRVV3HAEPS15E6NHDXKPJA1KAJJEG9AFF884 Now consider the case where a user locally configured the petname "pet.gns.alt" for the zone with the "example" record of the name above. The name "example.pet.gns.alt" would then point to the same record as the globally unique name above, but name resolution would only work on the local system where the "pet.gns.alt" petname is configured. The delegation of petnames and subsequent resolution of delegation builds on ideas from the Simple Distributed Security Infrastructure . In GNS, any user can create and manage any number of zones (see ) if their system provides a zone master implementation. For each zone, the zone type determines the respective set of cryptographic operations and the wire formats for encrypted data, public keys and signatures. A zone can be populated with mappings from labels to resource records (see ) by its owner. A label can be mapped to a delegation record which results in the corresponding subdomain being delegated to another zone. Circular delegations are explicitly allowed, including delegating a subdomain to its immediate parent zone. In order to support (legacy) applications as well as to facilitate the use of petnames, GNS defines auxiliary record types in addition to supporting existing DNS records.

Publishing Binding Information Zone contents are encrypted and signed before being published in a remote key-value storage (see ) as illustrated in . In this process, unique zone identification is hidden from the network through the use of key blinding. Key blinding allows the creation of signatures for zone contents using a blinded public/private key pair. This blinding is realized using a deterministic key derivation from the original zone key and corresponding private key using record label values as inputs from which blinding factors are derived. Specifically, the zone owner can derive blinded private keys for each record set published under a label, and a resolver can derive the corresponding blinded public keys. It is expected that GNS implementations use decentralized remote storages such as distributed hash tables (DHT) in order to facilitate availability within a network without the need for dedicated infrastructure. Specification of such a distributed or decentralized storage is out of scope of this document, but possible existing implementations include those based on , or .

| Record | |<-|----------| Zone | | Master | | | Storage | | | | Master | +---------+ | | |/ | +---------+ A | +---------+ | A | | | | +---------+ | | +---------+ / | /| | | / | /| +---------+ | | | +---------+ | | | | | | | | | | Local | | | | | Local | | | Zones | | | | | Zones | | | |/ | | | |/ +---------+ | | +---------+ ]]> A zone master implementation SHOULD be provided as part of a GNS implementation to enable users to create and manage zones. If this functionality is not implemented, names can still be resolved if zone keys for the initial step in the name resolution have been configured (see ) or if the names end with a zTLD suffix.

Resolving Names Applications use the resolver to lookup GNS names. Starting from a configurable start zone, names are resolved by following zone delegations recursively as illustrated in . For each label in a name, the recursive GNS resolver fetches the respective record set from the storage layer (see ). Without knowledge of the label values and the zone keys, the different derived keys are unlinkable both to the original zone key and to each other. This prevents zone enumeration (except via expensive online brute force attacks): To confirm affiliation of a query or the corresponding encrypted record set with a specific zone requires knowledge of both the zone key and the label, neither of which are disclosed to remote storage by the protocol. At the same time, the blinded zone key and digital signatures associated with each encrypted record set allow resolvers and oblivious remote storage to verify the integrity of the published information without disclosing anything about the originating zone or the record sets.

| Storage | | | |<---------| |<------------|--| |/ +-----------+ Results +----------+ Intermediate| +---------+ A Results | | | +---------+ | / | /| | +---------+ | | | | | | | Start | | | | Zones | | | | |/ | +---------+ | ]]>

Zones A zone in GNS is uniquely identified by its zone type and zone key. Each zone can be referenced by its zone Top-Level Domain (zTLD) string (see ) which encodes the zone type and zone key. A zone type (ztype) is a unique 32-bit number which corresponds to a resource record type number identifying a delegation record type in the GANA "GNS Record Types" registry . The ztype is a unique identifier for the set cryptographic functions of the zone and the format of the delegation record type. Any ztype registration MUST define the following set of cryptographic functions:

KeyGen() -> d, zk: is a function to generate a new private key d and the corresponding public zone key zk.
ZKDF(zk,label) -> zk': is a zone key derivation function which blinds a zone key zk using a label. zk and zk' must be unlinkable. Furthermore, blinding zk with different values for the label must result in different, unlinkable zk' values.
S-Encrypt(zk,label,expiration,plaintext) -> ciphertext: is a symmetric encryption function which encrypts the plaintext to derive ciphertext based on key material derived from the zone key zk, a label and an expiration timestamp. In order to leverage performance-enhancing caching features of certain underlying storages, in particular DHTs, a deterministic encryption scheme is recommended.
S-Decrypt(zk,label,expiration,ciphertext) -> plaintext: is a symmetric decryption function which decrypts the ciphertext into plaintext based on key material derived from the zone key, a label, and an expiration timestamp.
Sign(d,message) -> signature: is a function to sign a message using the private key d, yielding an unforgeable cryptographic signature. In order to leverage performance-enhancing caching features of certain underlying storages, in particular DHTs, a deterministic signature scheme is recommended.
Verify(zk,message,signature) -> boolean: is a function to verify the signature was created using the private key d corresponding to the zone key zk where d,zk := Keygen(). The function returns a boolean value of "TRUE" if the signature is valid, and otherwise "FALSE".
SignDerived(d,label,message) -> signature: is a function to sign a message (typically encrypted record data) that can be verified using the derived zone key zk' := ZKDF(zk,label). In order to leverage performance-enhancing caching features of certain underlying storages, in particular DHTs, a deterministic signature scheme is recommended.
VerifyDerived(zk,label,message,signature) -> boolean: is function to verify the signature using the derived zone key zk' := ZKDF(zk,label). The function returns a boolean value of "TRUE" if the signature is valid, and otherwise "FALSE".

The cryptographic functions of the default ztypes are specified with their corresponding delegation records in . In order to support cryptographic agility, additional ztypes MAY be defined in the future which replace or update the default ztypes defined in this document. All ztypes MUST be registered as dedicated zone delegation record types in the GANA "GNS Record Types" registry (see ). When defining new record types the cryptographic security considerations of this document apply, in particular .

Zone Top-Level Domain A zone Top-Level Domain (zTLD) is a string which encodes the zone type and zone key into a domain name suffix. A zTLD is used as a globally unique references to a zone in the process of name resolution. It is created by encoding a binary concatenation of the zone type and zone key (see ). The used encoding is a variation of the Crockford Base32 encoding called Base32GNS. The encoding and decoding symbols for Base32GNS including this modification are defined in . The functions for encoding and decoding based on this table are called Base32GNS-Encode and Base32GNS-Decode, respectively.

The ZONE TYPE must be encoded in network byte order. The format of the ZONE KEY depends entirely on the ZONE TYPE. Consequently, a zTLD is encoded and decoded as follows: where "||" is the concatenation operator. The zTLD can be used as-is as a rightmost label in a GNS name. If an application wants to ensure DNS compatibility of the name, it MAY also represent the zTLD as follows: If the zTLD is less than or equal to 63 characters, it can be used as a zTLD as-is. If the zTLD is longer than 63 characters, the zTLD is divided into smaller labels separated by the label separator. Here, the most significant bytes of the "ztype||zkey" concatenation must be contained in the rightmost label of the resulting string and the least significant bytes in the leftmost label of the resulting string. This allows the resolver to determine the ztype and zTLD length from the rightmost label and to subsequently determine how many labels the zTLD should span. A GNS implementation MUST support the division of zTLDs in DNS compatible label lengths. For example, assuming a zTLD of 130 characters, the division is:

Zone Revocation In order to revoke a zone key, a signed revocation message MUST be published. This message MUST be signed using the private key of the zone. The revocation message is broadcast to the network. The specification of the broadcast mechanism is out of scope for this document. A possible broadcast mechanism for efficient flooding in a distributed network is implemented in . Alternatively, revocation messages could also be distributed via a distributed ledger or a trusted central server. To prevent flooding attacks, the revocation message MUST contain a proof of work (PoW). The revocation message including the PoW MAY be calculated ahead of time to support timely revocation. For all occurrences below, "Argon2id" is the Password-based Key Derivation Function as defined in . For the PoW calculations the algorithm is instantiated with the following parameters:

S: The salt. Fixed 16-byte string: "GnsRevocationPow".
t: Number of iterations: 3
m: Memory size in KiB: 1024
T: Output length of hash in bytes: 64
p: Parallelization parameter: 1
v: Algorithm version: 0x13
y: Algorithm type (Argon2id): 2
X: Unused
K: Unused

illustrates the format of the data "P" on which the PoW is calculated.

POW: A 64-bit value that is a solution to the PoW. In network byte order.
TIMESTAMP: denotes the absolute 64-bit date when the revocation was computed. In microseconds since midnight (0 hour), January 1, 1970 UTC in network byte order.
ZONE TYPE: is the 32-bit zone type in network byte order.
ZONE KEY: is the 256-bit public key zk of the zone which is being revoked. The wire format of this value is defined by the ZONE TYPE.

Usually, PoW schemes require to find one POW value such that a specific number of leading zeroes are found in the hash result. This number is then referred to as the difficulty of the PoW. In order to reduce the variance in time it takes to calculate the PoW, a valid GNS revocation requires that a number Z different PoWs must be found that on average have D leading zeroes. Given an average difficulty of D, the proofs have an expiration time of EPOCH. Applications MAY calculate proofs with a difficulty that is higher than D by providing POW values where there are (on average) more than D bits of leading zeros. With each additional bit of difficulty, the lifetime of the proof is prolonged by another EPOCH. Consequently, by calculating a more difficult PoW, the lifetime of the proof and thus the persistence of the revocation message can be increased on demand by the zone owner. The parameters are defined as follows:

Z: The number of PoWs that are required. Its value is fixed at 32.
D: The lower limit of the average difficulty. Its value is fixed at 22.
EPOCH: A single epoch. Its value is fixed at 365 days in microseconds.

The revocation message wire format is illustrated in .

TIMESTAMP: denotes the absolute 64-bit date when the revocation was computed. In microseconds since midnight (0 hour), January 1, 1970 UTC in network byte order. This is the same value as the time stamp used in the individual PoW calculations.
TTL: denotes the relative 64-bit time to live of the record in microseconds in network byte order. The field SHOULD be set to EPOCH * 1.1. Given an average number of leading zeros D', then the field value MAY be increased up to (D'-D+1) * EPOCH * 1.1. Validators MAY reject messages with lower or higher values when received.
POW_i: The values calculated as part of the PoW, in network byte order. Each POW_i MUST be unique in the set of POW values. To facilitate fast verification of uniqueness, the POW values must be given in strictly monotonically increasing order in the message.
ZONE TYPE: The 32-bit zone type corresponding to the zone key in network byte order.
ZONE KEY: is the public key zk of the zone which is being revoked and the key to be used to verify SIGNATURE.
SIGNATURE: A signature over a time stamp and the zone zk of the zone which is revoked and corresponds to the key used in the PoW. The signature is created using the Sign() function of the cryptosystem of the zone and the private key (see ).

The signature over the public key covers a 32-bit header prefixed to the time stamp and public key fields. The header includes the key length and signature purpose. The wire format is illustrated in .

SIZE: A 32-bit value containing the length of the signed data in bytes in network byte order.
PURPOSE: A 32-bit signature purpose flag. The value of this field MUST be 3. The value is encoded in network byte order. It defines the context in which the signature is created so that it cannot be reused in other parts of the protocol including possible future extensions. The value of this field corresponds to an entry in the GANA "GNUnet Signature Purpose" registry .
TIMESTAMP: Field as defined in the revocation message above.
ZONE TYPE: Field as defined in the revocation message above.
ZONE KEY: Field as defined in the revocation message above.

In order to validate a revocation the following steps MUST be taken:

The signature MUST be verified against the zone key.
The set of POW values MUST NOT contain duplicates which MUST be checked by verifying that the values are strictly monotonically increasing.
The average number of leading zeroes D' resulting from the provided POW values MUST be greater than or equal to D. Implementers MUST NOT use an integer data type to calculate or represent D'.

The TTL field in the revocation message is informational. A revocation MAY be discarded without checking the POW values or the signature if the TTL (in combination with TIMESTAMP) indicates that the revocation has already expired. The actual validity period of the revocation MUST be determined by examining the leading zeroes in the POW values. The validity period of the revocation is calculated as (D'-D+1) * EPOCH * 1.1. The EPOCH is extended by 10% in order to deal with unsynchronized clocks. The validity period added on top of the TIMESTAMP yields the expiration date. If the current time is after the expiration date, the revocation is considered stale. Verified revocations MUST be stored locally. The implementation MAY discard stale revocations and evict then from the local store at any time. Implementations MUST broadcast received revocations if they are valid and not stale. Should the calculated validity period differ from the TTL field value, the calculated value MUST be used as TTL field value when forwarding the revocation message. Systems might disagree on the current time, so implementations MAY use stale but otherwise valid revocations but SHOULD NOT broadcast them. Forwarded stale revocations MAY be discarded. Any locally stored revocation MUST be considered during delegation record processing (see ).

Resource Records A GNS implementation SHOULD provide a mechanism to create and manage local zones as well as a persistence mechanism (such as a local database) for resource records. A new local zone is established by selecting a zone type and creating a zone key pair. If this mechanism is not implemented, no zones can be published in the storage (see ) and name resolution is limited to non-local start zones (see ). A GNS resource record holds the data of a specific record in a zone. The resource record format is defined in .

EXPIRATION: denotes the absolute 64-bit expiration date of the record. In microseconds since midnight (0 hour), January 1, 1970 UTC in network byte order.
SIZE: denotes the 16-bit size of the DATA field in bytes in network byte order.
FLAGS: is a 16-bit bit field indicating special properties of the resource record. The semantics of the different bits are defined below.
TYPE: is the 32-bit resource record type in network byte order. This type can be one of the GNS resource records as defined in or a DNS record type as defined in or any of the complementary standardized DNS resource record types. Note that values below 2^16 are reserved for 16-bit DNS Resorce Record types allocated by IANA . Values above 2^16 are allocated by the GANA "GNS Record Types" registry .
DATA: the variable-length resource record data payload. The content is defined by the respective type of the resource record.

The FLAGS field is used to indicate special properties of the resource record. An application creating resource records MUST set all bits in FLAGS to 0 unless it specifically understands and wants to set the respective flag. As additional flags can be defined in future protocol versions, if an application or implementation encounters a flag which it does not recognize, it MUST be ignored. However, all implementations MUST understand the SHADOW and CRITICAL flags defined below. Any combination of the flags specified below are valid. illustrates the flag distribution in the 16-bit FLAGS field of a resource record:

CRITICAL: If this flag is set, it indicates that processing is critical. Implementations that do not support the record type or are otherwise unable to process the record MUST abort resolution upon encountering the record in the resolution process.
SHADOW: If this flag is set, this record MUST be ignored by resolvers unless all (other) records of the same record type have expired. Used to allow zone publishers to facilitate good performance when records change by allowing them to put future values of records into the storage. This way, future values can propagate and can be cached before the transition becomes active.
SUPPLEMENTAL: This is a supplemental record. It is provided in addition to the other records. This flag indicates that this record is not explicitly managed alongside the other records under the respective name but might be useful for the application.

Zone Delegation Records This section defines the initial set of zone delegation record types. Any implementation SHOULD support all zone types defined here and MAY support any number of additional delegation records defined in the GANA "GNS Record Types" registry (see ). Not supporting some zone types will result in resolution failures in case the respective zone type is encountered. This can be a valid choice if some zone delegation record types have been determined to be cryptographically insecure. Zone delegation records MUST NOT be stored and published under the apex label. A zone delegation record type value is the same as the respective ztype value. The ztype defines the cryptographic primitives for the zone that is being delegated to. A zone delegation record payload contains the public key of the zone to delegate to. A zone delegation record MUST have the CRITICAL flag set and MUST be the only non-supplemental record under a label. There MAY be inactive records of the same type which have the SHADOW flag set in order to facilitate smooth key rollovers. In the following, "||" is the concatenation operator of two byte strings. The algorithm specification uses character strings such as GNS labels or constant values. When used in concatenations or as input to functions the null-terminator of the character strings MUST NOT be included.

PKEY In GNS, a delegation of a label to a zone of type "PKEY" is represented through a PKEY record. The PKEY DATA entry wire format can be found in .

PUBLIC KEY: A 256-bit Ed25519 public key.

For PKEY zones the zone key material is derived using the curve parameters of the twisted Edwards representation of Curve25519 (the reasoning behind choosing this curve can be found in ) with the ECDSA scheme . The following naming convention is used for the cryptographic primitives of PKEY zones:

d: is a 256-bit Ed25519 private key (private scalar).
zk: is the Ed25519 public zone key corresponding to d.
p: is the prime of edwards25519 as defined in , i.e. 2^255 - 19.
G: is the group generator (X(P),Y(P)). With X(P),Y(P) of edwards25519 as defined in .
L: is the order of the prime-order subgroup of edwards25519 in .
KeyGen(): The generation of the private scalar d and the curve point zk := d*G (where G is the group generator of the elliptic curve) as defined in Section 2.2. of represents the KeyGen() function.

The zone type and zone key of a PKEY are 4 + 32 bytes in length. This means that a zTLD will always fit into a single label and does not need any further conversion. Given a label, the output zk' of the ZKDF(zk,label) function is calculated as follows for PKEY zones: The PKEY cryptosystem uses a hash-based key derivation function (HKDF) as defined in , using SHA-512 for the extraction phase and SHA-256 for the expansion phase. PRK_h is key material retrieved using an HKDF using the string "key-derivation" as salt and the zone key as initial keying material. h is the 512-bit HKDF expansion result and must be interpreted in network byte order. The expansion information input is a concatenation of the label and the string "gns". The multiplication of zk with h is a point multiplication, while the multiplication of d with h is a scalar multiplication. The Sign() and Verify() functions for PKEY zones are implemented using 512-bit ECDSA deterministic signatures as specified in . The same functions can be used for derived keys: A signature (R,S) is valid if the following holds: The S-Encrypt() and S-Decrypt() functions use AES in counter mode as defined in (CTR-AES-256): The key K and counter IV are derived from the record label and the zone key zk using a hash-based key derivation function (HKDF) as defined in . SHA-512 is used for the extraction phase and SHA-256 for the expansion phase. The output keying material is 32 bytes (256 bits) for the symmetric key and 4 bytes (32 bits) for the nonce. The symmetric key K is a 256-bit AES key. The nonce is combined with a 64-bit initialization vector and a 32-bit block counter as defined in . The block counter begins with the value of 1, and it is incremented to generate subsequent portions of the key stream. The block counter is a 32-bit integer value in network byte order. The initialization vector is the expiration time of the resource record block in network byte order. The resulting counter (IV) wire format can be found in .

EDKEY In GNS, a delegation of a label to a zone of type "EDKEY" is represented through a EDKEY record. The EDKEY DATA entry wire format is illustrated in .

PUBLIC KEY: A 256-bit EdDSA zone key.

For EDKEY zones the zone key material is derived using the curve parameters of the twisted edwards representation of Curve25519 (a.k.a. Ed25519) with the Ed25519 scheme as specified in . The following naming convention is used for the cryptographic primitives of EDKEY zones:

d: is a 256-bit EdDSA private key.
a: is is an integer derived from d using the SHA-512 hash function as defined in .
zk: is the EdDSA public key corresponding to d. It is defined as the curve point a*G where G is the group generator of the elliptic curve as defined in .
p: is the prime of edwards25519 as defined in , i.e. 2^255 - 19.
G: is the group generator (X(P),Y(P)). With X(P),Y(P) of edwards25519 as defined in .
L: is the order of the prime-order subgroup of edwards25519 in .
KeyGen(): The generation of the private key d and the associated public key zk := a*G where G is the group generator of the elliptic curve and a is an integer derived from d using the SHA-512 hash function as defined in Section 5.1.5 of represents the KeyGen() function.

The zone type and zone key of an EDKEY are 4 + 32 bytes in length. This means that a zTLD will always fit into a single label and does not need any further conversion. The "EDKEY" ZKDF instantiation is based on . The calculation of a is defined in Section 5.1.5 of . Given a label, the output of the ZKDF function is calculated as follows: Implementers SHOULD employ a constant time scalar multiplication for the constructions above to protect against timing attacks. Otherwise, timing attacks could leak private key material if an attacker can predict when a system starts the publication process. The EDKEY cryptosystem uses a hash-based key derivation function (HKDF) as defined in , using SHA-512 for the extraction phase and HMAC-SHA256 for the expansion phase. PRK_h is key material retrieved using an HKDF using the string "key-derivation" as salt and the zone key as initial keying material. The blinding factor h is the 512-bit HKDF expansion result. The expansion information input is a concatenation of the label and the string "gns". The result of the HKDF must be clamped and interpreted in network byte order. a is the 256-bit integer corresponding to the 256-bit private key d. The multiplication of zk with h is a point multiplication, while the division and multiplication of a and a1 with the co-factor are integer operations. The Sign(d,message) and Verify(zk,message,signature) procedures MUST be implemented as defined in . Signatures for EDKEY zones use a derived private scalar d' which is not compliant with . As the corresponding private key to the derived private scalar is not known, it is not possible to deterministically derive the signature part R according to . Instead, signatures MUST be generated as follows for any given message and private zone key: A nonce is calculated from the highest 32 bytes of the expansion of the private key d and the blinding factor h. The nonce is then hashed with the message to r. This way, the full derivation path is included in the calculation of the R value of the signature, ensuring that it is never reused for two different derivation paths or messages. > 3 a2 := (h * a1) mod L d' := a2 << 3 nonce := SHA-256 (dh[32..63] || h) r := SHA-512 (nonce || message) R := r * G S := r + SHA-512(R || zk' || message) * d' mod L return (R,S) ]]> A signature (R,S) is valid if the following holds: The S-Encrypt() and S-Decrypt() functions use XSalsa20 as defined in (XSalsa20-Poly1305): The result of the XSalsa20-Poly1305 encryption function is the encrypted ciphertext followed by the 128-bit authentication tag. Accordingly, the length of encrypted data equals the length of the data plus the 16 bytes of the authentication tag. The key K and counter IV are derived from the record label and the zone key zk using a hash-based key derivation function (HKDF) as defined in . SHA-512 is used for the extraction phase and SHA-256 for the expansion phase. The output keying material is 32 bytes (256 bits) for the symmetric key and 16 bytes (128 bits) for the NONCE. The symmetric key K is a 256-bit XSalsa20 key. No additional authenticated data (AAD) is used. The nonce is combined with an 8 byte initialization vector. The initialization vector is the expiration time of the resource record block in network byte order. The resulting counter (IV) wire format is illustrated in .

Redirection Records Redirect records are used to redirect resolution. Any implementation SHOULD support all redirection record types defined here and MAY support any number of additional redirection records defined in the GANA "GNS Record Types" registry . Redirection records MUST have the CRITICAL flag set. Not supporting some record types can result in resolution failures. This can be a valid choice if some redirection record types have been determined to be insecure, or if an application has reasons to not support redirection to DNS for reasons such as complexity or security. Redirection records MUST NOT be stored and published under the apex label.

REDIRECT A REDIRECT record is the GNS equivalent of a CNAME record in DNS. A REDIRECT record MUST be the only non-supplemental record under a label. There MAY be inactive records of the same type which have the SHADOW flag set in order to facilitate smooth changes of redirection targets. No other records are allowed. Details on processing of this record is defined in . A REDIRECT DATA entry is illustrated in .

REDIRECT NAME: The name to continue with. The value of a redirect record can be a regular name, or a relative name. Relative GNS names are indicated by an extension label (U+002B, "+") as rightmost label. The string is UTF-8 encoded and 0-terminated.

GNS2DNS A GNS2DNS record delegates resolution to DNS. The resource record contains a DNS name for the resolver to continue with in DNS followed by a DNS server. Both names are in the format defined in for DNS names. There MAY be multiple GNS2DNS records under a label. There MAY also be DNSSEC DS records or any other records used to secure the connection with the DNS servers under the same label. There MAY be inactive records of the same type(s) which have the SHADOW flag set in order to facilitate smooth changes of redirection targets. No other non-supplemental record types are allowed in the same record set. A GNS2DNS DATA entry is illustrated in .

NAME: The name to continue with in DNS. The value is UTF-8 encoded and 0-terminated.
DNS SERVER NAME: The DNS server to use. This value can be an IPv4 address in dotted-decimal form or an IPv6 address in colon-hexadecimal form or a DNS name. It can also be a relative GNS name ending with a "+" as the rightmost label. The implementation MUST check the string syntactically for an IP address in the respective notation before checking for a relative GNS name. If all three checks fail, the name MUST be treated as a DNS name. The value is UTF-8 encoded and 0-terminated.

NOTE: If an application uses DNS names obtained from GNS2DNS records in a DNS request they MUST first be converted to an IDNA compliant representation .

Auxiliary Records This section defines the initial set of auxiliary GNS record types. Any implementation SHOULD be able to process the specified record types according to .

LEHO This record is used to provide a hint for LEgacy HOstnames: Applications can use the GNS to lookup IPv4 or IPv6 addresses of internet services. However, sometimes connecting to such services does not only require the knowledge of an address and port, but also requires the canonical DNS name of the service to be transmitted over the transport protocol. In GNS, legacy host name records provide applications the DNS name that is required to establish a connection to such a service. The most common use case is HTTP virtual hosting and TLS Server Name Indication , where a DNS name must be supplied in the HTTP "Host"-header and the TLS handshake, respectively. Using a GNS name in those cases might not work as it might not be globally unique. Furthermore, even if uniqueness is not an issue, the legacy service might not even be aware of GNS. A LEHO resource record is expected to be found together in a single resource record with an IPv4 or IPv6 address. A LEHO DATA entry is illustrated in .

LEGACY HOSTNAME: A UTF-8 string (which is not 0-terminated) representing the legacy hostname.

NOTE: If an application uses a LEHO value in an HTTP request header (e.g. "Host:" header) it MUST be converted to an IDNA compliant representation .

NICK Nickname records can be used by zone administrators to publish a label that a zone prefers to have used when it is referred to. This is a suggestion to other zones what label to use when creating a delegation record () containing this zone key. This record SHOULD only be stored locally under the apex label "@" but MAY be returned with record sets under any label as a supplemental record. details how a resolver must process supplemental and non-supplemental NICK records. A NICK DATA entry is illustrated in .

NICKNAME: A UTF-8 string (which is not 0-terminated) representing the preferred label of the zone. This string MUST be a valid GNS label.

BOX GNS lookups are expected to return all of the required useful information in one record set. This avoids unnecessary additional lookups and cryptographically ties together information that belongs together, making it impossible for an adversarial storage to provide partial answers that might omit information critical for security. This general strategy is incompatible with the special labels used by DNS for SRV and TLSA records. Thus, GNS defines the BOX record format to box up SRV and TLSA records and include them in the record set of the label they are associated with. For example, a TLSA record for "_https._tcp.example.org" will be stored in the record set of "example.org" as a BOX record with service (SVC) 443 (https) and protocol (PROTO) 6 (tcp) and record TYPE "TLSA". For reference, see also . A BOX DATA entry is illustrated in .

PROTO: the 16-bit protocol number in network byte order. Values below 2^8 are reserved for 8-bit Internet Protocol numbers allocated by IANA (e.g. 6 for TCP). Values above 2^8 are allocated by the GANA "Overlay Protocols" registry .
SVC: the 16-bit service value of the boxed record in network byte order. In case of TCP and UDP it is the port number.
TYPE: is the 32-bit record type of the boxed record in network byte order.
RECORD DATA: is a variable length field containing the "DATA" format of TYPE as defined for the respective TYPE. Thus, for TYPE values below 2^16, the format is the same as the respective record type's binary format in DNS.

Record Encoding for Remote Storage Any API which allows storing a block under a 512-bit key and retrieving one or more blocks from a key can be used by an implementation for remote storage. To be useful, the API MUST permit storing at least 176 byte blocks to be able to support the defined zone delegation record encodings, and SHOULD allow at least 1024 byte blocks. In the following, it is assumed that an implementation realizes two procedures on top of a storage: block ]]> A GNS implementation publishes blocks in accordance to the properties and recommendations of the underlying remote storage. This can include a periodic refresh operation to preserve the availability of published blocks. There is no mechanism to explicitly delete individual blocks from remote storage. However, blocks include an EXPIRATION field which guides remote storage implementations to decide when to delete blocks. Given multiple blocks for the same key, remote storage implementations SHOULD try to preserve and return the block with the largest EXPIRATION value. All resource records from the same zone sharing the same label are encrypted and published together in a single resource records block (RRBLOCK) in the remote storage under a key q as illustrated in . A GNS implementation MUST NOT include expired resource records in blocks. An implementation MUST use the PUT storage procedure when record sets change to update the zone contents. Implementations MUST ensure that the EXPIRATION fields of RRBLOCKs increases strictly monotonically for every change, even if the smallest expiration time of records in the block does not.

| Storage | | | | | Master | | | |/ +-----------+ +---------+ | +---------+ | A | | | Zone records | | | grouped by label | | | | | +---------+ | |Create / Delete / | /| | |and Update +---------+ | | |Local Zones | | | | | | Local | | | +-------------->| Zones | | | | |/ | +---------+ | ]]> The storage key derivation and records block creation is specified in the following sections and illustrated in .

| S-Encrypt | | +----------|---------->+-----------+ | | | | | | | | | v v | | | +-------------+ | +---------------|-->| SignDerived | | | | +-------------+ | | | | | v v v | +------+ +---------------+ +----->| ZKDF |------->| Records Block | +------+ +---------------+ | v +------+ +-------------+ | Hash |------->| Storage Key | +------+ +-------------+ ]]>

The Storage Key The storage key is derived from the zone key and the respective label of the contained records. The required knowledge of both zone key and label in combination with the similarly derived symmetric secret keys and blinded zone keys ensures query privacy (see , Section 3.5). Given a label, the storage key q is derived as follows:

label: is a UTF-8 string under which the resource records are published.
zk: is the zone key.
q: Is the 512-bit storage key under which the resource records block is published. It is the SHA-512 hash over the derived zone key.

Plaintext Record Data (RDATA) GNS records from a zone are grouped by their labels such that all records under the same label published together as a single block in the storage. Such grouped record sets MAY be paired with supplemental records. Record data (RDATA) is the format used to encode such a group of GNS records. The binary format of RDATA is illustrated in .

EXPIRATION, SIZE, TYPE, FLAGS and DATA: These fields were defined in the resource record format in .
PADDING: When serializing records into RDATA, a GNS implementation MUST ensure that the size of the RDATA is a power of two using the padding field. The field MUST be set to zero and MUST be ignored on receipt. As a special exception, record sets with (only) a zone delegation record type are never padded.

The Resource Records Block The resource records grouped in an RDATA are encrypted using the S-Encrypt() function defined by the zone type of the zone to which the resource records belong and prefixed with meta data into a resource record block (RRBLOCK) for remote storage. The GNS RRBLOCK wire format is illustrated in .

SIZE: A 32-bit value containing the length of the block in bytes in network byte order. Despite the message format's use of a 32-bit value, implementations MAY refuse to publish blocks beyond a certain size significantly below the theoretical block size limit of 4 GB.
ZONE TYPE: is the 32-bit ztype in network byte order.
ZONE KEY (BLINDED): is the blinded zone key "ZKDF(zk, label)" to be used to verify SIGNATURE. The length and format of the blinded public key depends on the ztype.
SIGNATURE: The signature is computed over the EXPIRATION and BDATA fields as detailed in . The length and format of the signature depends on the ztype. The signature is created using the SignDerived() function of the cryptosystem of the zone (see ).
EXPIRATION: Specifies when the RRBLOCK expires and the encrypted block SHOULD be removed from the storage and caches as it is likely stale. However, applications MAY continue to use non-expired individual records until they expire. The value MUST be set to the maximum of the expiration time of the resource record contained within this block with the smallest expiration time and the previous EXPIRATION value (if any) plus one to ensure strict monotonicity (see ). If the RDATA includes shadow records, then the maximum expiration time of all shadow records with matching type and the expiration times of the non-shadow records is considered. This is a 64-bit absolute date in microseconds since midnight (0 hour), January 1, 1970 UTC in network byte order.
BDATA: The encrypted RDATA computed using S-Encrypt() with the zone key, label and expiration time as additional inputs. Its ultimate size and content are determined by the S-Encrypt() function of the ztype.

The signature over the public key covers a 32-bit pseudo header conceptually prefixed to the EXPIRATION and the BDATA fields. The wire format is illustrated in .

SIZE: A 32-bit value containing the length of the signed data in bytes in network byte order.
PURPOSE: A 32-bit signature purpose flag in network byte order. The value of this field MUST be 15. It defines the context in which the signature is created so that it cannot be reused in other parts of the protocol including possible future extensions. The value of this field corresponds to an entry in the GANA "GNUnet Signature Purpose" registry .
EXPIRATION: Field as defined in the RRBLOCK message above.
BDATA: Field as defined in the RRBLOCK message above.

Name Resolution Names in GNS are resolved by recursively querying the record storage. Recursive in this context means that a resolver does not provide intermediate results for a query to the application. Instead, it MUST respond to a resolution request with either the requested resource record or an error message in case resolution fails. illustrates how an application requests the lookup of a GNS name (1). The application MAY provide a desired record type to the resolver. Subsequently, a Start Zone is determined (2) and the recursive resolution process started. This is where the desired record type is used to guide processing. For example, if a zone delegation record type is requested, the resolution of the apex label in that zone must be skipped, as the desired record is already found. Details on how the resolution process is initiated and each iterative result (3a,3b) in the resolution is processed are provided in the sections below. The results of the lookup are eventually returned to the application (4). The implementation MUST NOT filter the returned resource record sets according to the desired record type. Filtering of record sets is typically done by the application.

| Storage | | | |<---------| |<--------------|--| |/ +-----------+ (4) +----------+ (3b) RRBLOCK | +---------+ Records A | | | (2) Determination of | | Start Zone | | | | +---------+ | / | /| | +---------+ | | | | | | | Start | | | | Zones | | | | |/ | +---------+ | ]]>

Start Zones The resolution of a GNS name starts by identifying the start zone suffix. Once the start zone suffix is identified, recursive resolution of the remainder of the name is initiated (see ). There are two types of start zone suffixes: zTLDs and local suffix-to-zone mappings. The choice of available suffix-to-zone mappings is at the sole discretion of the local system administrator or user. This property addresses the issue of a single hierarchy with a centrally controlled root and the related issue of distribution and management of root servers in DNS (see , Sections 3.10 and 3.12). For names ending with a zTLD the start zone is explicitly given in the suffix of the name to resolve. In order to ensure uniqueness of names with zTLDs any implementation MUST use the given zone as start zone. An implementation MUST first try to interpret the rightmost label of the given name as the beginning of a zTLD (see ). If the rightmost label cannot be (partially) decoded or if it does not indicate a supported ztype, the name is treated as a normal name and start zone discovery MUST continue with finding a local suffix-to-zone mapping. If a valid ztype can be found in the rightmost label, the implementation MUST try to synthesize and decode the zTLD to retrieve the start zone key according to . If the zTLD cannot be synthesized or decoded, the resolution of the name fails and an error is returned to the application. Otherwise, the zone key MUST be used as the start zone: => Start zone: zk of type ztype => Name to resolve from start zone: www.example ]]> For names not ending with a zTLD the resolver MUST determine the start zone through a local suffix-to-zone mapping. Suffix-to-zone mappings MUST be configurable through a local configuration file or database by the user or system administrator. A suffix MAY consist of multiple GNS labels concatenated with a label separator. If multiple suffixes match the name to resolve, the longest matching suffix MUST be used. The suffix length of two results MUST NOT be equal. This indicates a misconfiguration and the implementation MUST return an error. The following is a non-normative example mapping of start zones: Start zone: zk1 => Name to resolve from start zone: www ]]> The process given above MAY be supplemented with other mechanisms if the particular application requires a different process. If no start zone can be discovered, resolution MUST fail and an error MUST be returned to the application.

Recursion In each step of the recursive name resolution, there is an authoritative zone zk and a name to resolve. The name MAY be empty. If the name is empty, it is interpreted as the apex label "@". Initially, the authoritative zone is the start zone. From here, the following steps are recursively executed, in order:

Extract the right-most label from the name to look up.
Calculate q using the label and zk as defined in .
Perform a storage query GET(q) to retrieve the RRBLOCK.
Verify and process the RRBLOCK and decrypt the BDATA contained in it as defined in .

Upon receiving the RRBLOCK from the storage, as part of verifying the provided signature, the resolver MUST check that the SHA-512 hash of the derived authoritative zone key zk' from the RRBLOCK matches the query q and that the block is not yet expired. If the signature does not match or the block is expired, the RRBLOCK MUST be ignored and, if applicable, the storage lookup GET(q) MUST continue to look for other RRBLOCKs.

Record Processing Record processing occurs once a well-formed block has been decrypted. In record processing, only the valid records obtained are considered. To filter records by validity, the resolver MUST at least check the expiration time and the FLAGS field of the respective record. Specifically, the resolver MUST disregard expired records. Furthermore, SHADOW and SUPPLEMENTAL flags can also exclude records from being considered. If the resolver encounters a record with the CRITICAL flag set and does not support the record type the resolution MUST be aborted and an error MUST be returned. The information that the critical record could not be processed SHOULD be returned in the error description. The implementation MAY choose not to return the reason for the failure, merely complicating troubleshooting for the user. The next steps depend on the context of the name that is being resolved:

Case 1: If the filtered record set consists of a single REDIRECT record, the remainder of the name is prepended to the REDIRECT data and the recursion is started again from the resulting name. Details are described in .
Case 2: If the filtered record set consists exclusively of one or more GNS2DNS records resolution continues with DNS. Details are described in .
Case 3: If the remainder of the name to be resolved is of the format "_SERVICE._PROTO" and the record set contains one or more matching BOX records, the records in the BOX records are the final result and the recursion is concluded as described in .
Case 4: If the current record set consist of a single delegation record, resolution of the remainder of the name is delegated to the target zone as described in .
Case 5: If the remainder of the name to resolve is empty the record set is the final result. If any NICK records are in the final result set, it MUST be processed according to . Otherwise, the final result set is returned.
Finally, if none of the above is applicable resolution fails and the resolver MUST return an empty record set.

REDIRECT If the remaining name is empty and the desired record type is REDIRECT, in which case the resolution concludes with the REDIRECT record. If the rightmost label of the redirect name is the extension label (U+002B, "+"), resolution continues in GNS with the new name in the current zone. Otherwise, the resulting name is resolved via the default operating system name resolution process. This can in turn trigger a GNS name resolution process depending on the system configuration. In case resolution continues in DNS, the name MUST first be converted to an IDNA compliant representation . In order to prevent infinite loops, the resolver MUST implement loop detection or limit the number of recursive resolution steps. The loop detection MUST be effective even if a REDIRECT found in GNS triggers subsequent GNS lookups via the default operating system name resolution process.

GNS2DNS When a resolver encounters one or more GNS2DNS records and the remaining name is empty and the desired record type is GNS2DNS, the GNS2DNS records are returned. Otherwise, it is expected that the resolver first resolves the IP addresses of the specified DNS name servers. The DNS name MUST be converted to an IDNA compliant representation for resolution in DNS. GNS2DNS records MAY contain numeric IPv4 or IPv6 addresses, allowing the resolver to skip this step. The DNS server names might themselves be names in GNS or DNS. If the rightmost label of the DNS server name is the extension label (U+002B, "+"), the rest of the name is to be interpreted relative to the zone of the GNS2DNS record. If the DNS server name ends in a label representation of a zone key, the DNS server name is to be resolved against the GNS zone zk. Multiple GNS2DNS records can be stored under the same label, in which case the resolver MUST try all of them. The resolver MAY try them in any order or even in parallel. If multiple GNS2DNS records are present, the DNS name MUST be identical for all of them. Otherwise, it is not clear which name the resolver is supposed to follow. If multiple DNS names are present the resolution fails and an appropriate error is SHOULD be returned to the application. If there are DNSSEC DS records or any other records used to secure the connection with the DNS servers stored under the label, the DNS resolver SHOULD use them to secure the connection with the DNS server. Once the IP addresses of the DNS servers have been determined, the DNS name from the GNS2DNS record is appended to the remainder of the name to be resolved, and resolved by querying the DNS name server(s). The synthesized name has to be converted to an IDNA compliant representation for resolution in DNS. If such a conversion is not possible, the resolution MUST be aborted and an error MUST be returned. The information that the critical record could not be processed SHOULD be returned in the error description. The implementation MAY choose not to return the reason for the failure, merely complicating troubleshooting for the user. As the DNS servers specified are possibly authoritative DNS servers, the GNS resolver MUST support recursive DNS resolution and MUST NOT delegate this to the authoritative DNS servers. The first successful recursive name resolution result is returned to the application. In addition, the resolver SHOULD return the queried DNS name as a supplemental LEHO record (see ) with a relative expiration time of one hour. Once the transition from GNS into DNS is made through a GNS2DNS record, there is no "going back". The (possibly recursive) resolution of the DNS name MUST NOT delegate back into GNS and should only follow the DNS specifications. For example, names contained in DNS CNAME records MUST NOT be interpreted by resolvers that support both DNS and GNS as GNS names. GNS resolvers SHOULD offer a configuration option to disable DNS processing to avoid information leakage and provide a consistent security profile for all name resolutions. Such resolvers would return an empty record set upon encountering a GNS2DNS record during the recursion. However, if GNS2DNS records are encountered in the record set for the apex label and a GNS2DNS record is explicitly requested by the application, such records MUST still be returned, even if DNS support is disabled by the GNS resolver configuration.

BOX When a BOX record is received, a GNS resolver must unbox it if the name to be resolved continues with "_SERVICE._PROTO". Otherwise, the BOX record is to be left untouched. This way, TLSA (and SRV) records do not require a separate network request, and TLSA records become inseparable from the corresponding address records.

Zone Delegation Records When the resolver encounters a record of a supported zone delegation record type (such as PKEY or EDKEY) and the remainder of the name is not empty, resolution continues recursively with the remainder of the name in the GNS zone specified in the delegation record. Whenever a resolver encounters a new GNS zone, it MUST check against the local revocation list whether the respective zone key has been revoked. If the zone key was revoked, the resolution MUST fail with an empty result set. Implementations MUST NOT allow multiple different zone delegations under a single label. Implementations MAY support any subset of ztypes. Handling of Implementations MUST NOT process zone delegation for the apex label "@". Upon encountering a zone delegation record under this label, resolution fails and an error MUST be returned. The implementation MAY choose not to return the reason for the failure, merely impacting troubleshooting information for the user. If the remainder of the name to resolve is empty and a record set was received containing only a single delegation record, the recursion is continued with the record value as authoritative zone and the apex label "@" as remaining name. Except in the case where the desired record type as specified by the application is equal to the ztype, in which case the delegation record is returned.

NICK NICK records are only relevant to the recursive resolver if the record set in question is the final result which is to be returned to the application. The encountered NICK records can either be supplemental (see ) or non-supplemental. If the NICK record is supplemental, the resolver only returns the record set if one of the non-supplemental records matches the queried record type. It is possible that one record set contains both supplemental and non-supplemental NICK records. The differentiation between a supplemental and non-supplemental NICK record allows the application to match the record to the authoritative zone. Consider the following example: In this example, the returned NICK record is non-supplemental. For the application, this means that the NICK belongs to the zone "alice.example.gns.alt" and is published under the apex label along with an A record. The NICK record is interpreted as: The zone defined by "alice.example.gns.alt" wants to be referred to as "eve". In contrast, consider the following: In this case, the NICK record is marked as supplemental. This means that the NICK record belongs to the zone "example.gns.alt" and is published under the label "alice" along with an A record. The NICK record should be interpreted as: The zone defined by "example.gns.alt" wants to be referred to as "john". This distinction is likely useful for other records published as supplemental.

Internationalization and Character Encoding All names in GNS are encoded in UTF-8 . Labels MUST be canonicalized using Normalization Form C (NFC) . This does not include any DNS names found in DNS records, such as CNAME record data, which is internationalized through the IDNA specifications .

Security and Privacy Considerations

Availability In order to ensure availability of records beyond their absolute expiration times, implementations MAY allow to locally define relative expiration time values of records. Records can then be published recurringly with updated absolute expiration times by the implementation. Implementations MAY allow users to manage private records in their zones that are not published in the storage. Private records are considered just like regular records when resolving labels in local zones, but their data is completely unavailable to non-local users.

Agility The security of cryptographic systems depends on both the strength of the cryptographic algorithms chosen and the strength of the keys used with those algorithms. The security also depends on the engineering of the protocol used by the system to ensure that there are no non-cryptographic ways to bypass the security of the overall system. This is why developers of applications managing GNS zones SHOULD select a default ztype considered secure at the time of releasing the software. For applications targeting end users that are not expected to understand cryptography, the application developer MUST NOT leave the ztype selection of new zones to end users. This document concerns itself with the selection of cryptographic algorithms used in GNS. The algorithms identified in this document are not known to be broken (in the cryptographic sense) at the current time, and cryptographic research so far leads us to believe that they are likely to remain secure into the foreseeable future. However, this is not necessarily forever, and it is expected that new revisions of this document will be issued from time to time to reflect the current best practices in this area. In terms of crypto-agility, whenever the need for an updated cryptographic scheme arises to, for example, replace ECDSA over Ed25519 for PKEY records it can simply be introduced through a new record type. Zone administrators can then replace the delegation record type for future records. The old record type remains and zones can iteratively migrate to the updated zone keys. To ensure that implementations correctly generate an error message when encountering a ztype that they do not support, current and future delegation records must always have the CRITICAL flag set.

Cryptography The following considerations provide background on the design choices of the ztypes specified in this document. When specifying new ztypes as per , the same considerations apply. GNS PKEY zone keys use ECDSA over Ed25519. This is an unconventional choice, as ECDSA is usually used with other curves. However, standardized ECDSA curves are problematic for a range of reasons described in the Curve25519 and EdDSA papers . Using EdDSA directly is also not possible, as a hash function is used on the private key which destroys the linearity that the key blinding in GNS depends upon. We are not aware of anyone suggesting that using Ed25519 instead of another common curve of similar size would lower the security of ECDSA. GNS uses 256-bit curves because that way the encoded (public) keys fit into a single DNS label, which is good for usability. In order to ensure ciphertext indistinguishability, care must be taken with respect to the initialization vector in the counter block. In our design, the IV always includes the expiration time of the record block. When applications store records with relative expiration times, monotonicity is implicitly ensured because each time a block is published into the storage, its IV is unique as the expiration time is calculated dynamically and increases monotonically with the system time. Still, an implementation MUST ensure that when relative expiration times are decreased, the expiration time of the next record block MUST be after the last published block. For records where an absolute expiration time is used, the implementation MUST ensure that the expiration time is always increased when the record data changes. For example, the expiration time on the wire could be increased by a single microsecond even if the user did not request a change. In case of deletion of all resource records under a label, the implementation MUST keep track of the last absolute expiration time of the last published resource block. Implementations MAY define and use a special record type as a tombstone that preserves the last absolute expiration time, but then MUST take care to not publish a block with this record. When new records are added under this label later, the implementation MUST ensure that the expiration times are after the last published block. Finally, in order to ensure monotonically increasing expiration times the implementation MUST keep a local record of the last time obtained from the system clock, so as to construct a monotonic clock in case the system clock jumps backwards.

Abuse Mitigation GNS names are UTF-8 strings. Consequently, GNS faces similar issues with respect to name spoofing as DNS does for internationalized domain names. In DNS, attackers can register similar sounding or looking names (see above) in order to execute phishing attacks. GNS zone administrators must take into account this attack vector and incorporate rules in order to mitigate it. Further, DNS can be used to combat illegal content on the internet by having the respective domains seized by authorities. However, the same mechanisms can also be abused in order to impose state censorship. Avoiding that possibility is one of the motivations behind GNS. In GNS, TLDs are not enumerable. By design, the start zone of the resolver is defined locally and hence such a seizure is difficult and ineffective in GNS.

Zone Management In GNS, zone administrators need to manage and protect their zone keys. Once a zone key is lost, it cannot be recovered or revoked. Revocation messages can be pre-calculated if revocation is required in case a zone key is lost. Zone administrators, and for GNS this includes end-users, are required to responsibly and diligently protect their cryptographic keys. GNS supports signing records in advance ("offline") in order to support processes which aim to protect private keys such as air gaps. Similarly, users are required to manage their local start zone configuration. In order to ensure integrity and availability or names, users must ensure that their local start zone information is not compromised or outdated. It can be expected that the processing of zone revocations and an initial start zone is provided with a GNS implementation ("drop shipping"). Shipping an initial start zone configuration effectively establishes a root zone. Extension and customization of the zone is at the full discretion of the user. While implementations following this specification will be interoperable, if two implementations connect to different storages they are mutually unreachable. This can lead to a state where a record exists in the global namespace for a particular name, but the implementation is not communicating with the storage and is hence unable to resolve it. This situation is similar to a split-horizon DNS configuration. Which storages are implemented usually depends on the application it is built for. The storage used will most likely depend on the specific application context using GNS resolution. For example, one application is the resolution of hidden services within the Tor network, which would suggest using Tor routers for storage. Implementations of "aggregated" storages are conceivable, but are expected to be the exception.

DHTs as Storage This document does not specify the properties of the underlying storage which is required by any GNS implementation. It is important to note that the properties of the underlying storage are directly inherited by the GNS implementation. This includes both security as well as other non-functional properties such as scalability and performance. Implementers should take great care when selecting or implementing a DHT for use as storage in a GNS implementation. DHTs with reasonable security and performance properties exist . It should also be taken into consideration that GNS implementations which build upon different DHT overlays are unlikely to be interoperable with each other.

Revocations Zone administrators are advised to pre-generate zone revocations and to securely store the revocation information in case the zone key is lost, compromised or replaced in the future. Pre-calculated revocations can cease to be valid due to expirations or protocol changes such as epoch adjustments. Consequently, implementers and users must take precautions in order to manage revocations accordingly. Revocation payloads do not include a 'new' key for key replacement. Inclusion of such a key would have two major disadvantages:

If a revocation is published after a private key was compromised, allowing key replacement would be dangerous: if an adversary took over the private key, the adversary could then broadcast a revocation with a key replacement. For the replacement, the compromised owner would have no chance to issue even a revocation. Thus, allowing a revocation message to replace a private key makes dealing with key compromise situations worse.
Sometimes, key revocations are used with the objective of changing cryptosystems. Migration to another cryptosystem by replacing keys via a revocation message would only be secure as long as both cryptosystems are still secure against forgery. Such a planned, non-emergency migration to another cryptosystem should be done by running zones for both cipher systems in parallel for a while. The migration would conclude by revoking the legacy zone key only once it is deemed no longer secure, and hopefully after most users have migrated to the replacement.

Zone Privacy GNS does not support authenticated denial of existence of names within a zone. Record blocks are published in encrypted form using keys derived from the zone key and record label. Zone administrators should carefully consider if the label and zone key is public or if those should be used and considered as a shared secret. Unlike zone keys, labels can also be guessed by an attacker in the network observing queries and responses. Given a known and targeted zone key, the use of well known or easily guessable labels effectively results in general disclosure of the records to the public. If the labels and hence the records should be kept secret except to those knowing a secret label and the zone in which to look, the label must be chosen accordingly. It is recommended to then use a label with sufficient entropy as to prevent guessing attacks. It should be noted that this attack on labels only applies if the zone key is somehow disclosed to the adversary. GNS itself does not disclose it during a lookup or when resource records are published as the zone keys are blinded beforehand. However, zone keys do become public during revocation.

Zone Governance While DNS is distributed, in practice it relies on centralized, trusted registrars to provide globally unique names. As the awareness of the central role DNS plays on the Internet rises, various institutions are using their power (including legal means) to engage in attacks on the DNS, thus threatening the global availability and integrity of information on the Internet. While a wider discussion of this issue is out of scope for this document, analyses and investigations can be found in recent academic research works including . GNS is designed to provide a secure, privacy-enhancing alternative to the DNS name resolution protocol, especially when censorship or manipulation is encountered. In particular, it directly addresses concerns in DNS with respect to query privacy. However, depending on the governance of the root zone, any deployment will likely suffer from the issues of a "Single Hierarchy with a Centrally Controlled Root" and "Distribution and Management of Root Servers" as raised in . In DNS, those issues are a direct result from the centralized root zone governance at the Internet Corporation for Assigned Names and Numbers (ICANN) which allows it to provide globally unique names. In GNS, start zones give users local authority over their preferred root zone governance. It enables users to replace or enhance a trusted root zone configuration provided by a third party (e.g. the implementer or a multi-stakeholder governance body like ICANN) with secure delegation of authority using local petnames while operating under a very strong adversary model. In combination with zTLDs, this provides users of GNS with a global, secure and memorable mapping without a trusted authority. Any GNS implementation MAY provide a default governance model in the form of an initial start zone mapping.

Namespace Ambiguity Technically, the GNS protocol can be used to resolve names in the namespace of the global DNS. However, this would require the respective governance bodies and stakeholders (e.g. IETF and ICANN) to standardize the use of GNS for this particular use case. However, this capability implies that GNS names may be indistinguishable from DNS names in their respective common display format or other special-use domain names if a local start zone configuration maps suffixes from the global DNS to GNS zones. For applications, it is then ambiguous which name system should be used in order to resolve a given name. This poses a risk when trying to resolve a name through DNS when it is actually a GNS name as discussed in . In such a case, the GNS name is likely to be leaked as part of the DNS resolution. In order to prevent disclosure of queried GNS names it is RECOMMENDED that GNS-aware applications try to resolve a given name in GNS before any other method taking into account potential suffix-to-zone mappings and zTLDs. Suffix-to-zone mappings are expected to be configured by the user or local administrator and as such the resolution in GNS is in line with user expectations even if the name could also be resolved through DNS. If no suffix-to-zone mapping for the name exists and no zTLD is found, resolution MAY continue with other methods such as DNS. If a suffix-to-zone mapping for the name exists or the name ends with a zTLD, it MUST be resolved using GNS and resolution MUST NOT continue by any other means independent of the GNS resolution result. Mechanisms such as the Name Service Switch (NSS) of Unix-like operating systems are an example of how such a resolution process can be implemented and used. It allows system administrators to configure host name resolution precedence and is integrated with the system resolver implementation. For use cases where GNS names may be confused with names of other name resolution mechanisms (in particular DNS), the ".gns.alt" domain SHOULD be used. For use cases like implementing sinkholes to block malware sites or serving DNS domains via GNS to bypass censorship, GNS MAY be deliberately used in ways that interfere with resolution of another name system.

GANA Considerations GANA has assigned signature purposes in its "GNUnet Signature Purpose" registry as listed in .

GNS Record Types Registry GANA manages the "GNS Record Types" registry. Each entry has the following format:

Name: The name of the record type (case-insensitive ASCII string, restricted to alphanumeric characters). For zone delegation records, the assigned number represents the ztype value of the zone.
Number: 32-bit, above 65535
Comment: Optionally, a brief English text describing the purpose of the record type (in UTF-8)
Contact: Optionally, the contact information of a person to contact for further information.
References: Optionally, references describing the record type (such as an RFC).

The registration policy for this registry is "First Come First Served". This policy is modeled on that described in , and describes the actions taken by GANA: Adding new entries is possible after review by any authorized GANA contributor, using a first-come-first-served policy for unique name allocation. Reviewers are responsible to ensure that the chosen "Name" is appropriate for the record type. The registry will define a unique number for the entry. Authorized GANA contributors for review of new entries are reachable at gns-registry@gnunet.org. Any request MUST contain a unique name and a point of contact. The contact information MAY be added to the registry given the consent of the requester. The request MAY optionally also contain relevant references as well as a descriptive comment as defined above. GANA has assigned numbers for the record types defined in this specification in the "GNU Name System Record Types" registry as listed in .

.alt Subdomains Registry GANA manages the ".alt Subdomains" registry. Each entry has the following format:

Label: The label of the subdomain (in DNS LDH format as defined in Section 2.3.1 of ).
Comment: Optionally, a brief English text describing the purpose of the subdomain (in UTF-8)
Contact: Optionally, the contact information of a person to contact for further information.
References: Optionally, references describing the record type (such as an RFC).

The registration policy for this registry is "First Come First Served". This policy is modeled on that described in , and describes the actions taken by GANA: Adding new entries is possible after review by any authorized GANA contributor, using a first-come-first-served policy for unique subdomain allocation. Reviewers are responsible to ensure that the chosen "Subdomain" is appropriate for the purpose. Authorized GANA contributors for review of new entries are reachable at alt-registry@gnunet.org. Any request MUST contain a unique subdomain and a point of contact. The contact information MAY be added to the registry given the consent of the requester. The request MAY optionally also contain relevant references as well as a descriptive comment as defined above. GANA has assigned the subdomain defined in this specification in the ".alt subdomains" registry as listed in .

IANA Considerations This document makes no requests for IANA action. This section may be removed on publication as an RFC.

Implementation and Deployment Status There are two implementations conforming to this specification written in C and Go, respectively. The C implementation as part of GNUnet represents the original and reference implementation. The Go implementation demonstrates how two implementations of GNS are interoperable if they are built on top of the same underlying DHT storage. Currently, the GNUnet peer-to-peer network is an active deployment of GNS on top of its DHT. The implementation uses this deployment by building on top of the GNUnet DHT services available on any GNUnet peer. It shows how GNS implementations can attach to this existing deployment and participate in name resolution as well as zone publication. The self-sovereign identity system re:claimID is using GNS in order to selectively share identity attributes and attestations with third parties. The Ascension tool facilitates the migration of DNS zones to GNS zones by translating information retrieved from a DNS zone transfer into a GNS zone.

Acknowledgements The authors 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 NLnet and NGI DISCOVERY for funding work on the GNU Name System.

Normative References &RFC1034; &RFC1035; &RFC2782; &RFC2119; &RFC3629; &RFC3686; &RFC3826; &RFC5237; &RFC5869; &RFC5890; &RFC5895; &RFC6234; &RFC6895; &RFC6979; &RFC7748; &RFC8032; &RFC8126; &RFC8174; &RFC8499; &RFC9106; GNUnet Assigned Numbers Authority (GANA) GNUnet e.V. Recommendation for Block Cipher Modes of Operation: Methods and Techniques NIST This recommendation defines five confidentiality modes of operation for use with an underlying symmetric key block cipher algorithm: Electronic Codebook (ECB), Cipher Block Chaining (CBC), Cipher Feedback (CFB), Output Feedback (OFB), and Counter (CTR). Used with an underlying block cipher algorithm that is approved in a Federal Information Processing Standard (FIPS), these modes can provide cryptographic protection for sensitive, but unclassified, computer data. Base32 Extending the Salsa20 nonce University of Illinois at Chicago Unicode Standard Annex #15: Unicode Normalization Forms, Revision 31 The Unicode Consortium Unicode Technical Standard #46: Unicode IDNA Compatibility Processing, Revision 27 The Unicode Consortium Informative References &RFC1928; &RFC4033; &RFC6066; &RFC7363; &RFC8324; &RFC8806; &RFC6761; &RFC8244; &I-D.ietf-dnsop-alt-tld; Next-Generation Hidden Services in Tor SDSI - A Simple Distributed Security Infrastructure Kademlia: A peer-to-peer information system based on the xor metric. High-Speed High-Security Signatures University of Illinois at Chicago Technische Universiteit Eindhoven Technische Universiteit Eindhoven National Taiwan University Academia Sinica A Censorship-Resistant, Privacy-Enhancing and Fully Decentralized Name System Technische Universität München Technische Universität München Technische Universität München R5N: Randomized recursive routing for restricted-route networks Technische Universität München Technische Universität München Towards secure name resolution on the Internet Bern University of Applied Sciences Technische Universität München TU Eindhoven The GNUnet GNS Implementation GNUnet e.V. The Ascension Implementation GNUnet e.V. The GNUnet Project GNUnet e.V. re:claimID GNUnet e.V. The Go GNS Implementation System Databases and Name Service Switch GNU Project

Usage and Migration This section outlines a number of specific use cases which may help readers of the technical specification to understand the protocol better. The considerations below are not meant to be normative for the GNS protocol in any way. Instead, they are provided in order to give context and to provide some background on what the intended use of the protocol is by its designers. Further, this section contains pointers to migration paths.

Zone Dissemination In order to become a zone owner, it is sufficient to generate a zone key and a corresponding secret key using a GNS implementation. At this point, the zone owner can manage GNS resource records in a local zone database. The resource records can then be published by a GNS implementation as defined in . For other users to resolve the resource records, respective zone information must be disseminated first. The zone owner may decide to make the zone key and labels known to a selected set of users only or to make this information available to the general public. Sharing zone information directly with specific users not only allows to potentially preserve zone and record privacy, but also allows the zone owner and the user to establish strong trust relationships. For example, a bank may send a customer letter with a QR code which contains the GNS zone of the bank. This allows the user to scan the QR code and establish a strong link to the zone of the bank and with it, for example, the IP address of the online banking web site. Most Internet services likely want to make their zones available to the general public as efficiently as possible. First, it is reasonable to assume that zones which are commanding high levels of reputation and trust are likely included in the default suffix-to-zone mappings of implementations. Hence dissemination of a zone through delegation under such zones can be a viable path in order to disseminate a zone publicly. For example, it is conceivable that organizations such as ICANN or country-code top-level domain registrars also manage GNS zones and offer registration or delegation services. Following best practices in particularly those relating to security and abuse mitigation are methods which allow zone owners and aspiring registrars to gain a good reputation and eventually trust. This includes, of course, diligent protection of private zone key material. Formalizing such best practices is out of scope of this specification and should be addressed in a separate document and take into account.

Start Zone Configuration A user is expected to install a GNS implementation if it is not already provided through other means such as the operating system or the browser. It is likely that the implementation ships with a default start zone configuration. This means that the user is able to resolve GNS names ending on a zTLD or ending on any suffix-to-name mapping that is part of the default start zone configuration. At this point the user may delete or otherwise modify the implementation's default configuration: Deletion of suffix-to-zone mappings may become necessary of the zone owner referenced by the mapping has lost the trust of the user. For example, this could be due to lax registration policies resulting in phishing activities. Modification and addition of new mappings are means to heal the namespace perforation which would occur in the case of a deletion or to simply establish a strong direct trust relationship. However, this requires the user's knowledge of the respective zone keys. This information must be retrieved out of band, as illustrated in : A bank may send the user a letter with a QR code which contains the GNS zone of the bank. The user scans the QR code and adds a new suffix-to-name mapping using a chosen local name for his bank. Other examples include scanning zone information off the device of a friend, from a storefront, or an advertisement. The level of trust in the respective zone is contextual and likely varies from user to user. Trust in a zone provided through a letter from a bank which may also include a credit card is certainly different from a zone found on a random advertisement in the streets. However, this trust is immediately tangible to the user and can be reflected in the local naming as well. User clients should facilitate the modification of the start zone configuration, for example by providing a QR code reader or other import mechanisms. Implementations are ideally implemented according to best practices and addressing applicable points from . Formalizing such best practices is out of scope of this specification.

Globally Unique Names and the Web HTTP virtual hosting and TLS Server Name Indication are common use cases on the Web. HTTP clients supply a DNS name in the HTTP "Host"-header or as part of the TLS handshake, respectively. This allows the HTTP server to serve the indicated virtual host with a matching TLS certificate. The global uniqueness of DNS names are a prerequisite of those use cases. Not all GNS names are globally unique. But, any resource record in GNS can be represented as a concatenation of of a GNS label and the zTLD of the zone. While not human-readable, this globally unique GNS name can be leveraged in order to facilitate the same use cases. Consider the GNS name "www.example.gns" entered in a GNS-aware HTTP client. At first, "www.example.gns" is resolved using GNS yielding a record set. Then, the HTTP client determines the virtual host as follows: If there is a LEHO record () containing "www.example.com" in the record set, then the HTTP client uses this as the value of the "Host"-header field of the HTTP request: If there is no LEHO record in the record set, then the HTTP client tries to find the zone of the record and translates the GNS name into a globally unique zTLD-representation before using it in the "Host"-header field of the HTTP request: In order to determine the canonical representation of the record with a zTLD, at most two queries are required: First, it must be checked whether "www.example.gns.alt" itself points to a zone delegation record which would imply that the record set which was originally resolved is published under the apex label. If it does, the unique GNS name is simply the zTLD representation of the delegated zone: If it does not, the unique GNS name is the concatenation of the label "www" and the zTLD representation of the zone as given in the example above. In any case, this representation is globally unique. As such, it can be configured by the HTTP server administrator as a virtual host name and respective certificates may be issued. If the HTTP client is a browser, the use of a unique GNS name for virtual hosting or TLS SNI does not necessarily have to be shown to the user. For example, the name in the URL bar may remain as "www.example.gns.alt" even if the used unique name differs.

Migration Paths DNS resolution is built into a variety of existing software components. Most significantly operating systems and HTTP clients. This section illustrates possible migration paths for both in order to enable "legacy" applications to resolve GNS names. One way to efficiently facilitate the resolution of GNS names are GNS-enabled DNS server implementations. Local DNS queries are thereby either rerouted or explicitly configured to be resolved by a "DNS-to-GNS" server that runs locally. This DNS server tries to interpret any incoming query for a name as a GNS resolution request. If no start zone can be found for the name and it does not end in a zTLD, the server tries to resolve the name in DNS. Otherwise, the name is resolved in GNS. In the latter case, the resulting record set is converted to a DNS answer packet and is returned accordingly. An implementation of a DNS-to-GNS server can be found in . A similar approach is to use operating systems extensions such as the name service switch . It allows the system administrator to configure plugins which are used for hostname resolution. A GNS name service switch plugin can be used in a similar fashion as the "DNS-to-GNS" server. An implementation of a glibc-compatible nsswitch plugin for GNS can be found in . The methods above are usually also effective for HTTP client software. However, HTTP clients are commonly used in combination with TLS. TLS certificate validation and in particular server name indication (SNI) requires additional logic in HTTP clients when GNS names are in play (). In order to transparently enable this functionality for migration purposes, a local GNS-aware SOCKS5 proxy can be configured to resolve domain names. The SOCKS5 proxy, similar to the DNS-to-GNS server, is capable of resolving both GNS and DNS names. In the event of a TLS connection request with a GNS name, the SOCKS5 proxy can act as a man-in-the-middle, terminating the TLS connection and establishing a secure connection against the requested host. In order to establish a secure connection, the proxy may use LEHO and TLSA records stored in the record set under the GNS name. The proxy must provide a locally trusted certificate for the GNS name to the HTTP client which usually requires the generation and configuration of a local trust anchor in the browser. An implementation of this SOCKS5 proxy can be found in .

Example flows

AAAA Example Resolution

| Storage | | | |<---------| |<--------------|--| |/ +-----------+ (8) +----------+ (5,7) | +---------+ A | | | (2,3) | | | | | | +---------+ | / v /| | +---------+ | | | | | | | Start | | | | Zones | | | | |/ | +---------+ | ]]>

Lookup AAAA record for name: www.example.gnu.gns.alt.
Determine start zone for www.example.gnu.gns.alt.
Start zone: zk0 - Remainder: www.example.
Calculate q0=SHA512(ZKDF(zk0, "example")) and initiate GET(q0).
Retrieve and decrypt RRBLOCK consisting of a single PKEY record containing zk1.
Calculate q1=SHA512(ZKDF(zk1, "www")) and initiate GET(q1).
Retrieve RRBLOCK consisting of a single AAAA record containing the IPv6 address 2001:db8::1.
Return record set to application

REDIRECT Example Resolution

| Storage | | | |<---------| |<---------------|--| |/ +-----------+ (10) +----------+ (5,7,9) | +---------+ A | | | (2,3) | | | | | | +---------+ | / v /| | +---------+ | | | | | | | Start | | | | Zones | | | | |/ | +---------+ | ]]>

Lookup AAAA record for name: www.example.tld.gns.alt.
Determine start zone for www.example.tld.gns.alt.
Start zone: zk0 - Remainder: www.example.
Calculate q0=SHA512(ZKDF(zk0, "example")) and initiate GET(q0).
Retrieve and decrypt RRBLOCK consisting of a single PKEY record containing zk1.
Calculate q1=SHA512(ZKDF(zk1, "www")) and initiate GET(q1).
Retrieve and decrypt RRBLOCK consisting of a single REDIRECT record containing www2.+.
Calculate q2=SHA512(ZKDF(zk1, "www2")) and initiate GET(q2).
Retrieve and decrypt RRBLOCK consisting of a single AAAA record containing the IPv6 address 2001:db8::1.
Return record set to application.

GNS2DNS Example Resolution

| Storage | | | |<---------| |<-----------------|--| |/ +-----------+ (8) +----------+ (5) | +---------+ A A | | | (6,7) | (2,3) | +----------+ | | | | | v | +---------+ +------------+ | / v /| | System DNS | | +---------+ | | resolver | | | | | +------------+ | | Start | | | | Zones | | | | |/ | +---------+ | ]]>

Lookup AAAA record for name: www.example.gnu.gns.alt
Determine start zone for www.example.gnu.gns.alt.
Start zone: zk0 - Remainder: www.example.
Calculate q0=SHA512(ZKDF(zk0, "example")) and initiate GET(q0).
Retrieve and decrypt RRBLOCK consisting of a single GNS2DNS record containing the name example.com and the DNS server IPv4 address 192.0.2.1.
Use system resolver to lookup an AAAA record for the DNS name www.example.com.
Retrieve a DNS reply consisting of a single AAAA record containing the IPv6 address 2001:db8::1.
Return record set to application.

Base32GNS Encoding converts a byte array into a string of symbols. Decoding converts a string of symbols into a byte array. Decoding fails if the input string has symbols outside the defined set. This table defines the encode and decode symbols for a given symbol value. Each symbol value encodes 5 bits. It can be used to implement the encoding by reading it as: A symbol "A" or "a" is decoded to a 5 bit value 10 when decoding. A 5 bit block with a value of 18 is encoded to the character "J" when encoding. If the bit length of the byte string to encode is not a multiple of 5 it is padded to the next multiple with zeroes. In order to further increase tolerance for failures in character recognition, the letter "U" MUST be decoded to the same value as the letter "V" in Base32GNS.

Test Vectors The following test vectors can be used by implementations to test for conformance with this specification. Unless indicated otherwise, the test vectors are provided as hexadecimal byte arrays.

Base32GNS en-/decoding The following are test vectors for the Base32GNS encoding used for zTLDs. The input strings are encoded without the zero terminator.

Record sets The test vectors include record sets with a variety of record types and flags for both PKEY and EDKEY zones. This includes labels with UTF-8 characters to demonstrate internationalized labels. (1) PKEY zone with ASCII label and one delegation record (2) PKEY zone with UTF-8 label and three records (3) EDKEY zone with ASCII label and delegation record (4) EDKEY zone with UTF-8 label and three records

Zone revocation The following is an example revocation for a zone: