[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[lsd0001] branch master updated: call it zTLD
From: |
gnunet |
Subject: |
[lsd0001] branch master updated: call it zTLD |
Date: |
Sun, 06 Sep 2020 11:02:45 +0200 |
This is an automated email from the git hooks/post-receive script.
martin-schanzenbach pushed a commit to branch master
in repository lsd0001.
The following commit(s) were added to refs/heads/master by this push:
new 45bc343 call it zTLD
45bc343 is described below
commit 45bc34347e99210e9ff302b866dd0b7ea8149376
Author: Martin Schanzenbach <mschanzenbach@posteo.de>
AuthorDate: Sun Sep 6 10:56:15 2020 +0200
call it zTLD
---
draft-schanzen-gns.xml | 19 +++++++++----------
1 file changed, 9 insertions(+), 10 deletions(-)
diff --git a/draft-schanzen-gns.xml b/draft-schanzen-gns.xml
index 65c7113..4b6cab3 100644
--- a/draft-schanzen-gns.xml
+++ b/draft-schanzen-gns.xml
@@ -184,12 +184,10 @@
is a HDKD function which blinds a public zone key "zk" of the
respective type.
</dd>
- <dt>NameSuffix(ztype, zk) -> zkl</dt>
+ <dt>zTLD</dt>
<dd>
- is a function which defines a mapping from zone public key to
- a string "zkl" of the respective type.
- It is a string which encodes the "ztype" as well as the zone
- key "zk" into one or more labels. The "zkl" is used as a
+ is a string which encodes the "ztype" as well as the zone
+ key "zk" into one or more labels. The "zTLD" is used as a
globally unique reference to a specific namespace in the
process of name resolution.
</dd>
@@ -214,7 +212,8 @@
<artwork name="" type="" align="left" alt=""><![CDATA[
zkl := <Base32(zid)>
]]></artwork>
- <t>
+ <t>
+ If "zkl" is less than 63 characters, it is also the "zTLD".
If the resulting "zkl" should be longer than 63 characters, the
String must be divided into smaller labels separated by the label
separator ".". Where the most significant bytes of the "zid" be
contained
@@ -223,7 +222,7 @@ zkl := <Base32(zid)>
assuming a "zkl" of 130 characters:
</t>
<artwork name="" type="" align="left" alt=""><![CDATA[
-zkl[126:129].zkl[63:125].zkl[0:62]
+zTLD := zkl[126:129].zkl[63:125].zkl[0:62]
]]></artwork>
<!-- FIXME: We probably want to define more things here such as
how zone types are registered and identified ? -->
@@ -336,7 +335,7 @@ zk' := h mod L * zk
</t>
<t>
The "zid" of a PKEY is 32 + 4 bytes in length. This means that
- a Base32-encoded "zkl" will always fit into a single label and does
+ a Base32-encoded "zTLD" will always fit into a single label and does
not need any further conversion.
</t>
</section>
@@ -1527,13 +1526,13 @@ NICK: john (Supplemental)
</t>
<t>
GNS clients MUST first try to interpret the top-level domain of
- a GNS name as a zone key representation "zkl := NameSuffix(ztype,
zk)".
+ a GNS name as a zone key representation ("zTLD").
If the top-level domain is indicated to be a label representation of
a public zone key with a well-defined "ztype" value, the root zone of
the resolution process is implicitly given by the suffic of the name:
</t>
<artwork name="" type="" align="left" alt=""><![CDATA[
-Example name: www.example.<NameSuffix(ztype, zk)>
+Example name: www.example.<zTLD>
=> Root zone: zk of type ztype
=> Name to resolve from root zone: www.example
]]></artwork>
--
To stop receiving notification emails like this one, please contact
gnunet@gnunet.org.
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [lsd0001] branch master updated: call it zTLD,
gnunet <=