aboutsummaryrefslogtreecommitdiff
path: root/draft-schanzen-gns.xml
diff options
context:
space:
mode:
Diffstat (limited to 'draft-schanzen-gns.xml')
-rw-r--r--draft-schanzen-gns.xml15
1 files changed, 9 insertions, 6 deletions
diff --git a/draft-schanzen-gns.xml b/draft-schanzen-gns.xml
index 87f5204..5ff50c5 100644
--- a/draft-schanzen-gns.xml
+++ b/draft-schanzen-gns.xml
@@ -115,8 +115,8 @@
115 <t> 115 <t>
116 This specification describes the GNU Name System (GNS), a 116 This specification describes the GNU Name System (GNS), a
117 censorship-resistant, privacy-preserving and decentralized 117 censorship-resistant, privacy-preserving and decentralized
118 domain name resolution protocol. GNS can bind names to any 118 domain name resolution protocol. GNS cryptographically secures
119 kind of cryptographically secured token, enabling it to double 119 the binding of names to arbitrary tokens, enabling it to double
120 in some respects as an alternative to some of today’s public 120 in some respects as an alternative to some of today’s public
121 key infrastructures. 121 key infrastructures.
122 </t> 122 </t>
@@ -129,7 +129,10 @@
129 root zone. In the GNS reference implementation, users can 129 root zone. In the GNS reference implementation, users can
130 autonomously and freely delegate control of names to zones 130 autonomously and freely delegate control of names to zones
131 through their local configurations. 131 through their local configurations.
132 In this model, users are expected to manage their local configurations, so as to avoid any confusion as to how names are resolved. 132 GNS expects each user to be in control of their setup.
133 By following <xref target="namespace_ambiguity" /> guidelines,
134 users should manage to avoid any confusion as to how names are
135 resolved.
133 </t> 136 </t>
134 <t> 137 <t>
135 Name resolution and zone dissemination is based on the 138 Name resolution and zone dissemination is based on the
@@ -3799,14 +3802,14 @@ Base32GNS-Decode:
3799 </section> 3802 </section>
3800 <section> 3803 <section>
3801 <name>Record sets</name> 3804 <name>Record sets</name>
3802 3805
3803 <t> 3806 <t>
3804 The test vectors include record sets with a variety 3807 The test vectors include record sets with a variety
3805 of record types and flags for both PKEY and EDKEY zones. 3808 of record types and flags for both PKEY and EDKEY zones.
3806 This includes labels with UTF-8 characters to demonstrate 3809 This includes labels with UTF-8 characters to demonstrate
3807 internationalized labels. 3810 internationalized labels.
3808 </t> 3811 </t>
3809 <t><strong>(1) PKEY zone with ASCII label and one delegation record</strong></t> 3812 <t><strong>(1) PKEY zone with ASCII label and one delegation record</strong></t>
3810 <artwork name="" type="" align="left" alt=""> 3813 <artwork name="" type="" align="left" alt="">
3811 <![CDATA[ 3814 <![CDATA[
3812Zone private key (d, big-endian): 3815Zone private key (d, big-endian):
@@ -3911,7 +3914,7 @@ ae a4 39 91 48 d5 0c ff
3911 3914
3912 ]]> 3915 ]]>
3913 </artwork> 3916 </artwork>
3914 <t><strong>(2) PKEY zone with UTF-8 label and three records</strong></t> 3917 <t><strong>(2) PKEY zone with UTF-8 label and three records</strong></t>
3915 <artwork name="" type="" align="left" alt=""> 3918 <artwork name="" type="" align="left" alt="">
3916 <![CDATA[ 3919 <![CDATA[
3917Zone private key (d, big-endian): 3920Zone private key (d, big-endian):