commit 9bc90a8feb6eb6615466c5b9bd3c6614e418065f
parent 7ec725013d657e2cddfff031091f20983c813986
Author: Schanzenbach, Martin <mschanzenbach@posteo.de>
Date: Sat, 5 Oct 2019 13:35:13 +0200
headings
Diffstat:
3 files changed, 21 insertions(+), 21 deletions(-)
diff --git a/draft-schanzen-gns.html b/draft-schanzen-gns.html
@@ -1078,7 +1078,7 @@ async function addMetadata(){try{const e=document.styleSheets[0].cssRules;for(le
<p id="section-boilerplate.3-1.2.1"><a href="#section-2" class="xref">2</a>. <a href="#name-zones" class="xref">Zones</a><a href="#section-boilerplate.3-1.2.1" class="pilcrow">¶</a></p>
</li>
<li class="toc ulEmpty" id="section-boilerplate.3-1.3">
- <p id="section-boilerplate.3-1.3.1"><a href="#section-3" class="xref">3</a>. <a href="#name-resource-records" class="xref">Resource records</a><a href="#section-boilerplate.3-1.3.1" class="pilcrow">¶</a></p>
+ <p id="section-boilerplate.3-1.3.1"><a href="#section-3" class="xref">3</a>. <a href="#name-resource-records" class="xref">Resource Records</a><a href="#section-boilerplate.3-1.3.1" class="pilcrow">¶</a></p>
<ul class="toc ulEmpty">
<li class="toc ulEmpty" id="section-boilerplate.3-1.3.2.1">
<p id="section-boilerplate.3-1.3.2.1.1"><a href="#section-3.1" class="xref">3.1</a>. <a href="#name-pkey" class="xref">PKEY</a><a href="#section-boilerplate.3-1.3.2.1.1" class="pilcrow">¶</a></p>
@@ -1101,13 +1101,13 @@ async function addMetadata(){try{const e=document.styleSheets[0].cssRules;for(le
<p id="section-boilerplate.3-1.4.1"><a href="#section-4" class="xref">4</a>. <a href="#name-publishing-records" class="xref">Publishing Records</a><a href="#section-boilerplate.3-1.4.1" class="pilcrow">¶</a></p>
<ul class="toc ulEmpty">
<li class="toc ulEmpty" id="section-boilerplate.3-1.4.2.1">
- <p id="section-boilerplate.3-1.4.2.1.1"><a href="#section-4.1" class="xref">4.1</a>. <a href="#name-key-derivations" class="xref">Key derivations</a><a href="#section-boilerplate.3-1.4.2.1.1" class="pilcrow">¶</a></p>
+ <p id="section-boilerplate.3-1.4.2.1.1"><a href="#section-4.1" class="xref">4.1</a>. <a href="#name-key-derivations" class="xref">Key Derivations</a><a href="#section-boilerplate.3-1.4.2.1.1" class="pilcrow">¶</a></p>
</li>
<li class="toc ulEmpty" id="section-boilerplate.3-1.4.2.2">
- <p id="section-boilerplate.3-1.4.2.2.1"><a href="#section-4.2" class="xref">4.2</a>. <a href="#name-resource-records-block" class="xref">Resource records block</a><a href="#section-boilerplate.3-1.4.2.2.1" class="pilcrow">¶</a></p>
+ <p id="section-boilerplate.3-1.4.2.2.1"><a href="#section-4.2" class="xref">4.2</a>. <a href="#name-resource-records-block" class="xref">Resource Records Block</a><a href="#section-boilerplate.3-1.4.2.2.1" class="pilcrow">¶</a></p>
</li>
<li class="toc ulEmpty" id="section-boilerplate.3-1.4.2.3">
- <p id="section-boilerplate.3-1.4.2.3.1"><a href="#section-4.3" class="xref">4.3</a>. <a href="#name-block-data-encryption-and-d" class="xref">Block data encryption and decryption</a><a href="#section-boilerplate.3-1.4.2.3.1" class="pilcrow">¶</a></p>
+ <p id="section-boilerplate.3-1.4.2.3.1"><a href="#section-4.3" class="xref">4.3</a>. <a href="#name-record-data-encryption-and-" class="xref">Record Data Encryption and Decryption</a><a href="#section-boilerplate.3-1.4.2.3.1" class="pilcrow">¶</a></p>
</li>
</ul>
</li>
@@ -1243,7 +1243,7 @@ async function addMetadata(){try{const e=document.styleSheets[0].cssRules;for(le
<div id="rrecords">
<section id="section-3">
<h2 id="name-resource-records">
-<a href="#section-3" class="section-number selfRef">3. </a><a href="#name-resource-records" class="section-name selfRef">Resource records</a>
+<a href="#section-3" class="section-number selfRef">3. </a><a href="#name-resource-records" class="section-name selfRef">Resource Records</a>
</h2>
<p id="section-3-1">
A GNS implementor MUST provide a mechanism to create and manage resource
@@ -1567,7 +1567,7 @@ async function addMetadata(){try{const e=document.styleSheets[0].cssRules;for(le
<div id="blinding">
<section id="section-4.1">
<h3 id="name-key-derivations">
-<a href="#section-4.1" class="section-number selfRef">4.1. </a><a href="#name-key-derivations" class="section-name selfRef">Key derivations</a>
+<a href="#section-4.1" class="section-number selfRef">4.1. </a><a href="#name-key-derivations" class="section-name selfRef">Key Derivations</a>
</h3>
<p id="section-4.1-1">
Given a label, the DHT key "q" is derived as follows:<a href="#section-4.1-1" class="pilcrow">¶</a></p>
@@ -1634,7 +1634,7 @@ async function addMetadata(){try{const e=document.styleSheets[0].cssRules;for(le
<div id="wire">
<section id="section-4.2">
<h3 id="name-resource-records-block">
-<a href="#section-4.2" class="section-number selfRef">4.2. </a><a href="#name-resource-records-block" class="section-name selfRef">Resource records block</a>
+<a href="#section-4.2" class="section-number selfRef">4.2. </a><a href="#name-resource-records-block" class="section-name selfRef">Resource Records Block</a>
</h3>
<p id="section-4.2-1">
GNS records are grouped by their labels and published as a single
@@ -1730,8 +1730,8 @@ async function addMetadata(){try{const e=document.styleSheets[0].cssRules;for(le
</section>
</div>
<section id="section-4.3">
- <h3 id="name-block-data-encryption-and-d">
-<a href="#section-4.3" class="section-number selfRef">4.3. </a><a href="#name-block-data-encryption-and-d" class="section-name selfRef">Block data encryption and decryption</a>
+ <h3 id="name-record-data-encryption-and-">
+<a href="#section-4.3" class="section-number selfRef">4.3. </a><a href="#name-record-data-encryption-and-" class="section-name selfRef">Record Data Encryption and Decryption</a>
</h3>
<p id="section-4.3-1">
A symmetric encryption scheme is used to encrypt the resource records
diff --git a/draft-schanzen-gns.txt b/draft-schanzen-gns.txt
@@ -62,16 +62,16 @@ Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Zones . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
- 3. Resource records . . . . . . . . . . . . . . . . . . . . . . 4
+ 3. Resource Records . . . . . . . . . . . . . . . . . . . . . . 4
3.1. PKEY . . . . . . . . . . . . . . . . . . . . . . . . . . 5
3.2. GNS2DNS . . . . . . . . . . . . . . . . . . . . . . . . . 6
3.3. LEHO . . . . . . . . . . . . . . . . . . . . . . . . . . 6
3.4. NICK . . . . . . . . . . . . . . . . . . . . . . . . . . 7
3.5. BOX . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
4. Publishing Records . . . . . . . . . . . . . . . . . . . . . 8
- 4.1. Key derivations . . . . . . . . . . . . . . . . . . . . . 8
- 4.2. Resource records block . . . . . . . . . . . . . . . . . 9
- 4.3. Block data encryption and decryption . . . . . . . . . . 11
+ 4.1. Key Derivations . . . . . . . . . . . . . . . . . . . . . 8
+ 4.2. Resource Records Block . . . . . . . . . . . . . . . . . 9
+ 4.3. Record Data Encryption and Decryption . . . . . . . . . . 11
5. Internationalization and Character Encoding . . . . . . . . . 13
6. Name Resolution . . . . . . . . . . . . . . . . . . . . . . . 13
6.1. Entry Zone . . . . . . . . . . . . . . . . . . . . . . . 13
@@ -170,7 +170,7 @@ Schanzenbach, et al. Expires 24 January 2020 [Page 3]
Internet-Draft The GNU Name System July 2019
-3. Resource records
+3. Resource Records
A GNS implementor MUST provide a mechanism to create and manage
resource records for local zones. A local zone is established by
@@ -433,7 +433,7 @@ Internet-Draft The GNU Name System July 2019
RRBLOCK). The key "q" which is derived from the zone key "zk" and
the respective label of the contained records.
-4.1. Key derivations
+4.1. Key Derivations
Given a label, the DHT key "q" is derived as follows:
@@ -482,7 +482,7 @@ Internet-Draft The GNU Name System July 2019
multiplication, while the multiplication of "d" with "h" is a scalar
multiplication.
-4.2. Resource records block
+4.2. Resource Records Block
GNS records are grouped by their labels and published as a single
block in the DHT. The contained resource records are encrypted using
@@ -576,7 +576,7 @@ Internet-Draft The GNU Name System July 2019
BDATA The encrypted resource records with a total size of SIZE - 16.
-4.3. Block data encryption and decryption
+4.3. Record Data Encryption and Decryption
A symmetric encryption scheme is used to encrypt the resource records
set RDATA into the BDATA field of a GNS RRBLOCK. The wire format of
diff --git a/draft-schanzen-gns.xml b/draft-schanzen-gns.xml
@@ -154,7 +154,7 @@
</dl>
</section>
<section anchor="rrecords" numbered="true" toc="default">
- <name>Resource records</name>
+ <name>Resource Records</name>
<t>
A GNS implementor MUST provide a mechanism to create and manage resource
records for local zones. A local zone is established by creating a zone
@@ -439,7 +439,7 @@
label of the contained records.
</t>
<section anchor="blinding" numbered="true" toc="default">
- <name>Key derivations</name>
+ <name>Key Derivations</name>
<t>
Given a label, the DHT key "q" is derived as follows:
</t>
@@ -503,7 +503,7 @@
</t>
</section>
<section anchor="wire" numbered="true" toc="default">
- <name>Resource records block</name>
+ <name>Resource Records Block</name>
<t>
GNS records are grouped by their labels and published as a single
block in the DHT.
@@ -595,7 +595,7 @@
</dl>
</section>
<section numbered="true" toc="default">
- <name>Block data encryption and decryption</name>
+ <name>Record Data Encryption and Decryption</name>
<t>
A symmetric encryption scheme is used to encrypt the resource records
set RDATA into the BDATA field of a GNS RRBLOCK.
