From 991bb6a695a292e7cc61d2e8fcb5ccdffb7335d8 Mon Sep 17 00:00:00 2001 From: Martin Schanzenbach Date: Thu, 5 May 2022 15:46:40 +0200 Subject: clarify IANA number ranges --- draft-schanzen-gns.xml | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/draft-schanzen-gns.xml b/draft-schanzen-gns.xml index 1ab17d4..d47ae9c 100644 --- a/draft-schanzen-gns.xml +++ b/draft-schanzen-gns.xml @@ -347,7 +347,7 @@ Zone contents are encrypted and signed - before being published in a distributed key-value storage () + before being published in a key-value storage () as illustrated in . In this process, unique zone identification is hidden from the network through the use of key blinding. @@ -931,8 +931,8 @@ zTLD[126..129].zTLD[63..125].zTLD[0..62] type as defined in or any of the complementary standardized DNS resource record types. This value must be stored in network byte order. Note that values - below 2^16 are reserved for allocation via IANA , - while values above 2^16 are allocated by the + below 2^16 are reserved for 16-bit DNS Resorce Record types allocated by IANA . + Values above 2^16 are allocated by the GNUnet Assigned Numbers Authority .
DATA
@@ -1658,8 +1658,8 @@ S-Decrypt(zk,label,expiration,ciphertext):
the 16-bit protocol number, e.g. 6 for TCP. Note that values - below 2^8 are reserved for allocation via IANA , - while values above 2^8 are allocated by the + below 2^8 are reserved for 8-bit Internet Protocol numbers allocated by IANA . + Values above 2^8 are allocated by the GNUnet Assigned Numbers Authority . In network byte order.
-- cgit v1.2.3