gnunet-svn
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[GNUnet-SVN] [lsd0001] branch master updated: move to v3


From: gnunet
Subject: [GNUnet-SVN] [lsd0001] branch master updated: move to v3
Date: Sun, 08 Sep 2019 12:49:16 +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 bf8ff19  move to v3
bf8ff19 is described below

commit bf8ff19e15df6d1c65401ba3c3f4e10fc0d193f5
Author: Schanzenbach, Martin <address@hidden>
AuthorDate: Sun Sep 8 12:47:25 2019 +0200

    move to v3
---
 draft-schanzen-gns.txt |  36 ++++++-------
 draft-schanzen-gns.xml | 139 ++++++++++++++++++++++++++++---------------------
 2 files changed, 97 insertions(+), 78 deletions(-)

diff --git a/draft-schanzen-gns.txt b/draft-schanzen-gns.txt
index db16118..651c088 100644
--- a/draft-schanzen-gns.txt
+++ b/draft-schanzen-gns.txt
@@ -62,11 +62,13 @@ Table of Contents
 
    1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
    2.  Resource Records  . . . . . . . . . . . . . . . . . . . . . .   2
-     2.1.  Wire format . . . . . . . . . . . . . . . . . . . . . . .   2
-     2.2.  Examples  . . . . . . . . . . . . . . . . . . . . . . . .   4
-     2.3.  Serialization format  . . . . . . . . . . . . . . . . . .   4
-     2.4.  Internationalization and Character Encoding . . . . . . .   4
-     2.5.  Security Considerations . . . . . . . . . . . . . . . . .   5
+     2.1.  Record blocks . . . . . . . . . . . . . . . . . . . . . .   2
+       2.1.1.  BDATA SET cryptography  . . . . . . . . . . . . . . .   3
+     2.2.  Record data . . . . . . . . . . . . . . . . . . . . . . .   3
+     2.3.  Examples  . . . . . . . . . . . . . . . . . . . . . . . .   4
+     2.4.  Serialization format  . . . . . . . . . . . . . . . . . .   4
+     2.5.  Internationalization and Character Encoding . . . . . . .   4
+     2.6.  Security Considerations . . . . . . . . . . . . . . . . .   5
    3.  Record Resolution . . . . . . . . . . . . . . . . . . . . . .   5
    4.  Namespace Revocation  . . . . . . . . . . . . . . . . . . . .   5
    5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
@@ -85,7 +87,7 @@ Table of Contents
 
 2.  Resource Records
 
-2.1.  Wire format
+2.1.  Record blocks
 
    TODO
 
@@ -106,8 +108,6 @@ Table of Contents
 
 
 
-
-
 
 Schanzenbach            Expires January 24, 2020                [Page 2]
 
@@ -142,15 +142,15 @@ Internet-Draft             The GNU Name System            
     July 2019
 
                                  Figure 1
 
+2.1.1.  BDATA SET cryptography
 
+   TEST
 
+               h := H(l,P)
+               d := h*x mod n
+               k := HKDF (P,l)
 
-
-
-
-
-
-
+2.2.  Record data
 
 
 
@@ -204,15 +204,15 @@ Internet-Draft             The GNU Name System            
     July 2019
 
                                  Figure 3
 
-2.2.  Examples
+2.3.  Examples
 
    TODO
 
-2.3.  Serialization format
+2.4.  Serialization format
 
    TODO (Is this not the same as wire format?)
 
-2.4.  Internationalization and Character Encoding
+2.5.  Internationalization and Character Encoding
 
    TODO
 
@@ -226,7 +226,7 @@ Schanzenbach            Expires January 24, 2020            
    [Page 4]
 Internet-Draft             The GNU Name System                 July 2019
 
 
-2.5.  Security Considerations
+2.6.  Security Considerations
 
    TODO
 
diff --git a/draft-schanzen-gns.xml b/draft-schanzen-gns.xml
index 34209a7..18ad092 100644
--- a/draft-schanzen-gns.xml
+++ b/draft-schanzen-gns.xml
@@ -1,26 +1,22 @@
-<?xml version="1.0" encoding="US-ASCII"?>
-<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [
+<?xml version='1.0' encoding='utf-8'?>
+<!DOCTYPE rfc SYSTEM "rfc2629-xhtml.ent" [
 <!ENTITY RFC3986 SYSTEM 
"http://xml.resource.org/public/rfc/bibxml/reference.RFC.3986.xml";>
 <!ENTITY RFC3629 SYSTEM 
"http://xml.resource.org/public/rfc/bibxml/reference.RFC.3629.xml";>
 ]>
 <?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?>
-
 <?rfc strict="yes" ?>
 <?rfc toc="yes" ?>
 <?rfc symrefs="yes"?>
 <?rfc sortrefs="yes" ?>
 <?rfc compact="yes" ?>
 <?rfc subcompact="no" ?>
-
-<rfc category="info"
-  docName="draft-schanzen-gns-00"
-  ipr="trust200902">
-
+<rfc xmlns:xi="http://www.w3.org/2001/XInclude"; category="info" 
docName="draft-schanzen-gns-00" ipr="trust200902" obsoletes="" updates="" 
submissionType="IETF" xml:lang="en" version="3">
+  <!-- xml2rfc v2v3 conversion 2.26.0 -->
   <front>
     <title abbrev="The GNU Name System">
       The GNU Name System Specification
     </title>
-
+    <seriesInfo name="Internet-Draft" value="draft-schanzen-gns-00"/>
     <author fullname="Martin Schanzenbach" initials="M.S." 
surname="Schanzenbach">
       <organization>GNUnet e.V.</organization>
       <address>
@@ -33,25 +29,18 @@
         <email>address@hidden</email>
       </address>
     </author>
-
-    <date day="23" month="July" year="2019" />
-
+    <date day="23" month="July" year="2019"/>
     <!-- Meta-data Declarations -->
     <area>General</area>
     <workgroup>Independent Stream</workgroup>
     <keyword>name systems</keyword>
-
     <abstract>
-
       <t>This document contains the GNU Name System (GNS) technical 
specification.</t>
-
     </abstract>
-
   </front>
-
   <middle>
-
-    <section anchor="introduction" title="Introduction">
+    <section anchor="introduction" numbered="true" toc="default">
+      <name>Introduction</name>
       <t>
         This document contains the GNU Name System (GNS) technical 
specification
         for secure, censorship-resistant and decentralised name resolution.
@@ -64,17 +53,16 @@
 
       </t>
     </section>
-
-    <section anchor="rrecords"
-      title="Resource Records">
-
-      <section anchor="wire" title="Wire format">
+    <section anchor="rrecords" numbered="true" toc="default">
+      <name>Resource Records</name>
+      <section anchor="wire" numbered="true" toc="default">
+        <name>Record blocks</name>
         <t>
           TODO
         </t>
+        <t>A GNS record block has the following format:</t>
         <figure anchor="figure_record_block">
-          <preamble>A GNS resource record has the following format:</preamble>
-          <artwork>
+          <artwork name="" type="" align="left" alt=""><![CDATA[
             0     1     2     3     4     5     6     7
             +-----+-----+-----+-----+-----+-----+-----+-----+
             |                   SIGNATURE                   |
@@ -98,12 +86,30 @@
             /                    BDATA SET                  /
             /                                               /
             +-----+-----+-----+-----+-----+-----+-----+-----+
-          </artwork>
-          <!--        <postamble>which is a very simple example.</postamble>-->
+          ]]></artwork>
         </figure>
+        <t>where:</t>
+        <dl>
+          <dt>SIGNATURE</dt>
+          <dd>A signature</dd>
+        </dl>
+        <section numbered="true" toc="default">
+          <name>BDATA SET cryptography</name>
+          <t>
+            TEST
+          </t>
+          <artwork name="" type="" align="left" alt=""><![CDATA[
+            h := H(l,P)
+            d := h*x mod n
+            k := HKDF (P,l)
+          ]]></artwork>
+        </section>
+      </section>
+      <section numbered="true" toc="default">
+        <name>Record data</name>
+        <t>A single entry in the decrypted BDATA SET has the following 
format:</t>
         <figure anchor="figure_gnsrecord">
-          <preamble>A single entry in the decrypted BDATA SET has the 
following format:</preamble>
-          <artwork>
+          <artwork name="" type="" align="left" alt=""><![CDATA[
             0     1     2     3     4     5     6     7
             +-----+-----+-----+-----+-----+-----+-----+-----+
             |                   EXPIRATION                  |
@@ -121,13 +127,12 @@
             /                                               /
             |                                               |
             +-----+-----+-----+-----+-----+-----+-----+-----+
-          </artwork>
+          ]]></artwork>
           <!--        <postamble>which is a very simple example.</postamble>-->
         </figure>
-
+        <t>The a PKEY RDATA has the following format:</t>
         <figure anchor="figure_pkeyrecord">
-          <preamble>The a PKEY RDATA has the following format:</preamble>
-          <artwork>
+          <artwork name="" type="" align="left" alt=""><![CDATA[
             0     1     2     3     4     5     6     7
             +-----+-----+-----+-----+-----+-----+-----+-----+
             |                   PUBLIC KEY                  |
@@ -135,62 +140,79 @@
             |                                               |
             |                                               |
             +-----+-----+-----+-----+-----+-----+-----+-----+
-          </artwork>
+          ]]></artwork>
           <!--        <postamble>which is a very simple example.</postamble>-->
         </figure>
       </section>
-
-
-      <section anchor="examples" title="Examples">
+      <section anchor="examples" numbered="true" toc="default">
+        <name>Examples</name>
         <t>
           TODO
         </t>
       </section>
-
-      <section anchor="serialization" title="Serialization format">
+      <section anchor="serialization" numbered="true" toc="default">
+        <name>Serialization format</name>
         <t>
           TODO (Is this not the same as wire format?)
         </t>
       </section>
-
-
-      <section anchor="encoding" title="Internationalization and Character 
Encoding">
+      <section anchor="encoding" numbered="true" toc="default">
+        <name>Internationalization and Character Encoding</name>
         <t>
           TODO
         </t>
       </section>
-
-      <section anchor="security" title="Security Considerations">
+      <section anchor="security" numbered="true" toc="default">
+        <name>Security Considerations</name>
         <t>
           TODO
         </t>
       </section>
     </section>
-    <section anchor="resolution" title="Record Resolution">
+    <section anchor="resolution" numbered="true" toc="default">
+      <name>Record Resolution</name>
       <t>
         TODO
       </t>
     </section>
-    <section anchor="revocation" title="Namespace Revocation">
+    <section anchor="revocation" numbered="true" toc="default">
+      <name>Namespace Revocation</name>
       <t>
         TODO
       </t>
     </section>
-    <section anchor="iana" title="IANA Considerations">
+    <section anchor="iana" numbered="true" toc="default">
+      <name>IANA Considerations</name>
       <t>
         This will be fun
       </t>
-    </section><!-- iana -->
-
-
+    </section>
+    <!-- iana -->
   </middle>
-
   <back>
-
-    <references title="Normative References">
-
-      &RFC3986;
-
+    <references>
+      <name>Normative References</name>
+      <reference anchor="RFC3986" 
target="https://www.rfc-editor.org/info/rfc3986"; 
xml:base="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.3986.xml";>
+        <front>
+          <title>Uniform Resource Identifier (URI): Generic Syntax</title>
+          <seriesInfo name="DOI" value="10.17487/RFC3986"/>
+          <seriesInfo name="RFC" value="3986"/>
+          <seriesInfo name="STD" value="66"/>
+          <author initials="T." surname="Berners-Lee" fullname="T. 
Berners-Lee">
+            <organization/>
+          </author>
+          <author initials="R." surname="Fielding" fullname="R. Fielding">
+            <organization/>
+          </author>
+          <author initials="L." surname="Masinter" fullname="L. Masinter">
+            <organization/>
+          </author>
+          <date year="2005" month="January"/>
+          <abstract>
+            <t>A Uniform Resource Identifier (URI) is a compact sequence of 
characters that identifies an abstract or physical resource.  This 
specification defines the generic URI syntax and a process for resolving URI 
references that might be in relative form, along with guidelines and security 
considerations for the use of URIs on the Internet.  The URI syntax defines a 
grammar that is a superset of all valid URIs, allowing an implementation to 
parse the common components of a URI ref [...]
+          </abstract>
+        </front>
+      </reference>
       <!--    <reference anchor="ISO20022">
         <front>
           <title>ISO 20022 Financial Services - Universal financial industry 
message scheme</title>
@@ -203,10 +225,7 @@
           <date month="May" year="2013"/>
         </front>
       </reference>-->
-
-
     </references>
-
     <!-- Change Log
     v00 2017-07-23  MS   Initial version
     -->

-- 
To stop receiving notification emails like this one, please contact
address@hidden.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]