1 files changed, 63 insertions, 29 deletions
diff --git a/draft-schanzen-gns.html b/draft-schanzen-gns.html
index d8e173a..3a1ee65 100644
--- a/draft-schanzen-gns.html
+++ b/draft-schanzen-gns.html
@@ -1090,7 +1090,10 @@ async function addMetadata(){try{const e=document.styleSheets[0].cssRules;for(le
                <p id="section-boilerplate.3-1.3.2.3.1"><a href="#section-3.3" class="xref">3.3</a>.  <a href="#name-leho" class="xref">LEHO</a><a href="#section-boilerplate.3-1.3.2.3.1" class="pilcrow">¶</a></p>
 </li>
              <li class="toc ulEmpty" id="section-boilerplate.3-1.3.2.4">
-                <p id="section-boilerplate.3-1.3.2.4.1"><a href="#section-3.4" class="xref">3.4</a>.  <a href="#name-box" class="xref">BOX</a><a href="#section-boilerplate.3-1.3.2.4.1" class="pilcrow">¶</a></p>
+                <p id="section-boilerplate.3-1.3.2.4.1"><a href="#section-3.4" class="xref">3.4</a>.  <a href="#name-nick" class="xref">NICK</a><a href="#section-boilerplate.3-1.3.2.4.1" class="pilcrow">¶</a></p>
+</li>
+              <li class="toc ulEmpty" id="section-boilerplate.3-1.3.2.5">
+                <p id="section-boilerplate.3-1.3.2.5.1"><a href="#section-3.5" class="xref">3.5</a>.  <a href="#name-box" class="xref">BOX</a><a href="#section-boilerplate.3-1.3.2.5.1" class="pilcrow">¶</a></p>
 </li>
            </ul>
 </li>
@@ -1451,12 +1454,43 @@ async function addMetadata(){try{const e=document.styleSheets[0].cssRules;for(le
         <span>[<a href="#RFC3492" class="xref">RFC3492</a>]</span>.<a href="#section-3.3-3" class="pilcrow">¶</a></p>
 </section>
 </div>
-<div id="gnsrecords_box">
+<div id="gnsrecords_nick">
 <section id="section-3.4">
+        <h3 id="name-nick">
+<a href="#section-3.4" class="section-number selfRef">3.4. </a><a href="#name-nick" class="section-name selfRef">NICK</a>
+        </h3>
+<p id="section-3.4-1">Nickname records can be used by zone administrators to publish an
+         indication on what label this zone prefers to be referred to.
+         This is a suggestion to other zones what label to use when creating a
+         PKEY <a href="#gnsrecords_pkey" class="xref">Section 3.1</a> record containing this zone's
+         public zone key.
+         A NICK resource record contains an UTF-8 string
+         (which is not 0-terminated) representing the preferred label.
+         This string may NOT inlcude a ".".
+         A NICK DATA entry has the following format:<a href="#section-3.4-1" class="pilcrow">¶</a></p>
+<div id="figure_nickrecord">
+<figure id="figure-6">
+          <div class="artwork art-text alignLeft" id="section-3.4-2.1">
+<pre>
+           0     8     16    24    32    40    48    56
+           +-----+-----+-----+-----+-----+-----+-----+-----+
+           |                  NICKNAME                     |
+           /                                               /
+           /                                               /
+           |                                               |
+           +-----+-----+-----+-----+-----+-----+-----+-----+
+           </pre>
+</div>
+<figcaption><a href="#figure-6" class="selfRef">Figure 6</a></figcaption></figure>
+</div>
+</section>
+</div>
+<div id="gnsrecords_box">
+<section id="section-3.5">
        <h3 id="name-box">
-<a href="#section-3.4" class="section-number selfRef">3.4. </a><a href="#name-box" class="section-name selfRef">BOX</a>
+<a href="#section-3.5" class="section-number selfRef">3.5. </a><a href="#name-box" class="section-name selfRef">BOX</a>
        </h3>
-<p id="section-3.4-1">
+<p id="section-3.5-1">
         In GNS, every "." in a name delegates to another zone, and
         GNS lookups are expected to return all of the required useful
         information in one record set.  This is incompatible with the
@@ -1471,10 +1505,10 @@ async function addMetadata(){try{const e=document.styleSheets[0].cssRules;for(le
         otherwise it 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.
-         A BOX DATA entry has the following format:<a href="#section-3.4-1" class="pilcrow">¶</a></p>
+         A BOX DATA entry has the following format:<a href="#section-3.5-1" class="pilcrow">¶</a></p>
 <div id="figure_boxrecord">
-<figure id="figure-6">
+<figure id="figure-7">
-          <div class="artwork art-text alignLeft" id="section-3.4-2.1">
+          <div class="artwork art-text alignLeft" id="section-3.5-2.1">
 <pre>
           0     8     16    24    32    40    48    56
           +-----+-----+-----+-----+-----+-----+-----+-----+
@@ -1487,26 +1521,26 @@ async function addMetadata(){try{const e=document.styleSheets[0].cssRules;for(le
           +-----+-----+-----+-----+-----+-----+-----+-----+
           </pre>
 </div>
-<figcaption><a href="#figure-6" class="selfRef">Figure 6</a></figcaption></figure>
+<figcaption><a href="#figure-7" class="selfRef">Figure 7</a></figcaption></figure>
 </div>
-<dl class="dlParallel" id="section-3.4-3">
+<dl class="dlParallel" id="section-3.5-3">
-          <dt id="section-3.4-3.1">PROTO</dt>
+          <dt id="section-3.5-3.1">PROTO</dt>
-          <dd id="section-3.4-3.2">
+          <dd id="section-3.5-3.2">
-           the 16-bit protocol number, e.g. 6 for tcp. In network byte order.<a href="#section-3.4-3.2" class="pilcrow">¶</a>
+           the 16-bit protocol number, e.g. 6 for tcp. In network byte order.<a href="#section-3.5-3.2" class="pilcrow">¶</a>
 </dd>
-          <dt id="section-3.4-3.3">SVC</dt>
+          <dt id="section-3.5-3.3">SVC</dt>
-          <dd id="section-3.4-3.4">
+          <dd id="section-3.5-3.4">
           the 16-bit service value of the boxed record, i.e. the port number.
-           In network byte order.<a href="#section-3.4-3.4" class="pilcrow">¶</a>
+           In network byte order.<a href="#section-3.5-3.4" class="pilcrow">¶</a>
 </dd>
-          <dt id="section-3.4-3.5">TYPE</dt>
+          <dt id="section-3.5-3.5">TYPE</dt>
-          <dd id="section-3.4-3.6">
+          <dd id="section-3.5-3.6">
-           is the 32-bit record type of the boxed record. In network byte order.<a href="#section-3.4-3.6" class="pilcrow">¶</a>
+           is the 32-bit record type of the boxed record. In network byte order.<a href="#section-3.5-3.6" class="pilcrow">¶</a>
 </dd>
-          <dt id="section-3.4-3.7">RECORD DATA</dt>
+          <dt id="section-3.5-3.7">RECORD DATA</dt>
-          <dd id="section-3.4-3.8">
+          <dd id="section-3.5-3.8">
           is a variable length field containing the "DATA" format of TYPE as
-           defined for the respective TYPE in DNS.<a href="#section-3.4-3.8" class="pilcrow">¶</a>
+           defined for the respective TYPE in DNS.<a href="#section-3.5-3.8" class="pilcrow">¶</a>
 </dd>
        </dl>
 </section>
@@ -1606,7 +1640,7 @@ async function addMetadata(){try{const e=document.styleSheets[0].cssRules;for(le
         include a periodic refresh publication.
         A GNS resource records block has the following format:<a href="#section-4.2-1" class="pilcrow">¶</a></p>
 <div id="figure_record_block">
-<figure id="figure-7">
+<figure id="figure-8">
          <div class="artwork art-text alignLeft" id="section-4.2-2.1">
 <pre>
           0     8     16    24    32    40    48    56
@@ -1635,7 +1669,7 @@ async function addMetadata(){try{const e=document.styleSheets[0].cssRules;for(le
           +-----+-----+-----+-----+-----+-----+-----+-----+
           </pre>
 </div>
-<figcaption><a href="#figure-7" class="selfRef">Figure 7</a></figcaption></figure>
+<figcaption><a href="#figure-8" class="selfRef">Figure 8</a></figcaption></figure>
 </div>
 <p id="section-4.2-3">where:<a href="#section-4.2-3" class="pilcrow">¶</a></p>
 <dl class="dlParallel" id="section-4.2-4">
@@ -1698,7 +1732,7 @@ async function addMetadata(){try{const e=document.styleSheets[0].cssRules;for(le
         set RDATA into the BDATA field of a GNS record block.
         The wire format of the RDATA looks as follows:<a href="#section-4.3-1" class="pilcrow">¶</a></p>
 <div id="figure_rdata">
-<figure id="figure-8">
+<figure id="figure-9">
          <div class="artwork art-text alignLeft" id="section-4.3-2.1">
 <pre>
           0     8     16    24    32    40    48    56
@@ -1726,7 +1760,7 @@ async function addMetadata(){try{const e=document.styleSheets[0].cssRules;for(le
           /                                               /
           </pre>
 </div>
-<figcaption><a href="#figure-8" class="selfRef">Figure 8</a></figcaption></figure>
+<figcaption><a href="#figure-9" class="selfRef">Figure 9</a></figcaption></figure>
 </div>
 <p id="section-4.3-3">where:<a href="#section-4.3-3" class="pilcrow">¶</a></p>
 <dl class="dlParallel" id="section-4.3-4">
@@ -1785,7 +1819,7 @@ async function addMetadata(){try{const e=document.styleSheets[0].cssRules;for(le
         <span>[<a href="#RFC3826" class="xref">RFC3826</a>]</span> key
         and a 256-bit TWOFISH <span>[<a href="#TWOFISH" class="xref">TWOFISH</a>]</span> key:<a href="#section-4.3-8" class="pilcrow">¶</a></p>
 <div id="figure_hkdf_keys">
-<figure id="figure-9">
+<figure id="figure-10">
          <div class="artwork art-text alignLeft" id="section-4.3-9.1">
 <pre>
           0     8     16    24    32    40    48    56
@@ -1802,13 +1836,13 @@ async function addMetadata(){try{const e=document.styleSheets[0].cssRules;for(le
           +-----+-----+-----+-----+-----+-----+-----+-----+
           </pre>
 </div>
-<figcaption><a href="#figure-9" class="selfRef">Figure 9</a></figcaption></figure>
+<figcaption><a href="#figure-10" class="selfRef">Figure 10</a></figcaption></figure>
 </div>
 <p id="section-4.3-10">
         Similarly, we divide "IV" into a 128-bit initialization vector
         and a 128-bit initialization vector:<a href="#section-4.3-10" class="pilcrow">¶</a></p>
 <div id="figure_hkdf_ivs">
-<figure id="figure-10">
+<figure id="figure-11">
          <div class="artwork art-text alignLeft" id="section-4.3-11.1">
 <pre>
           0     8     16    24    32    40    48    56
@@ -1821,7 +1855,7 @@ async function addMetadata(){try{const e=document.styleSheets[0].cssRules;for(le
           +-----+-----+-----+-----+-----+-----+-----+-----+
           </pre>
 </div>
-<figcaption><a href="#figure-10" class="selfRef">Figure 10</a></figcaption></figure>
+<figcaption><a href="#figure-11" class="selfRef">Figure 11</a></figcaption></figure>
 </div>
 <p id="section-4.3-12">
         The keys and IVs are used for a CFB128-AES-256 and