From d81f693b9630384fc4a6d791da5f91494109ee10 Mon Sep 17 00:00:00 2001 From: Martin Schanzenbach Date: Sun, 16 Jan 2022 20:47:48 +0100 Subject: domain names and labels --- draft-schanzen-gns.xml | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/draft-schanzen-gns.xml b/draft-schanzen-gns.xml index 8434063..6effff4 100644 --- a/draft-schanzen-gns.xml +++ b/draft-schanzen-gns.xml @@ -20,6 +20,7 @@ + ]> @@ -172,7 +173,8 @@ public/private key pairs and encryption of zone contents. - A zone can be populated with mappings from labels to resource records by + A zone can be populated with mappings from labels + (as defined in , Section 2) to resource records by its owner (). Labels can be delegated to other zones using delegation records and in order to support (legacy) applications as well as facilitate the use @@ -202,6 +204,7 @@ . + Names in GNS are domain names as defined in . Starting from a configurable root zone, names are resolved following zone delegations which are recursively queried from the storage (). Without knowledge of the label values and the zone public keys, the @@ -2618,6 +2621,7 @@ cae1789d &RFC8032; &RFC8126; &RFC8174; + &RFC8499; &RFC9106; -- cgit v1.2.3