gnunet-svn
[Top][All Lists]
Advanced

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

[lsd0001] branch master updated: move some normative references to infor


From: gnunet
Subject: [lsd0001] branch master updated: move some normative references to informative; remove whois
Date: Sun, 16 Jan 2022 21:16:10 +0100

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 3cd40a4  move some normative references to informative; remove whois
3cd40a4 is described below

commit 3cd40a4d0603b9d6e7de52d92b22f22222b29dc6
Author: Martin Schanzenbach <schanzen@gnunet.org>
AuthorDate: Sun Jan 16 21:16:07 2022 +0100

    move some normative references to informative; remove whois
---
 draft-schanzen-gns.xml | 13 +++++++------
 1 file changed, 7 insertions(+), 6 deletions(-)

diff --git a/draft-schanzen-gns.xml b/draft-schanzen-gns.xml
index 9cb95e1..9e2980b 100644
--- a/draft-schanzen-gns.xml
+++ b/draft-schanzen-gns.xml
@@ -8,7 +8,7 @@
 <!ENTITY RFC3629 PUBLIC '' 
"http://xml.resource.org/public/rfc/bibxml/reference.RFC.3629.xml";>
 <!ENTITY RFC3686 PUBLIC '' 
"http://xml.resource.org/public/rfc/bibxml/reference.RFC.3686.xml";>
 <!ENTITY RFC3826 PUBLIC '' 
"http://xml.resource.org/public/rfc/bibxml/reference.RFC.3826.xml";>
-<!ENTITY RFC3912 PUBLIC '' 
"http://xml.resource.org/public/rfc/bibxml/reference.RFC.3912.xml";>
+<!--<!ENTITY RFC3912 PUBLIC '' 
"http://xml.resource.org/public/rfc/bibxml/reference.RFC.3912.xml";>-->
 <!ENTITY RFC5869 PUBLIC '' 
"http://xml.resource.org/public/rfc/bibxml/reference.RFC.5869.xml";>
 <!ENTITY RFC5890 PUBLIC '' 
"http://xml.resource.org/public/rfc/bibxml/reference.RFC.5890.xml";>
 <!ENTITY RFC5891 PUBLIC '' 
"http://xml.resource.org/public/rfc/bibxml/reference.RFC.5891.xml";>
@@ -2076,7 +2076,7 @@ NICK: john (Supplemental)
            However, the same mechanisms can also be abused in order to impose
            state censorship, which is one of the motivations behind GNS.
            Hence, such a seizure is, by design, difficult to impossible in GNS.
-           In particular, GNS does not support WHOIS (<xref target="RFC3912" 
/>).
+           <!--In particular, GNS does not support WHOIS (<xref 
target="RFC3912" />).-->
          </t>
        </section>
        <section anchor="security_keymanagement" numbered="true" toc="default">
@@ -2609,17 +2609,14 @@ cae1789d
 
        &RFC1034;
        &RFC1035;
-       &RFC2693;
        &RFC2782;
        &RFC2119;
        &RFC3629;
        &RFC3686;
        &RFC3826;
-       &RFC3912;
        &RFC5869;
        &RFC5890;
        &RFC5891;
-       &RFC6781;
        &RFC6895;
        &RFC6979;
        &RFC7748;
@@ -2704,7 +2701,11 @@ cae1789d
      </references>
      <references>
        <name>Informative References</name>
-       &RFC7363;
+         &RFC2693;
+         &RFC6781;
+         &RFC7363;
+       <!--         &RFC3912;-->
+
        <reference anchor="Tor224" 
target="https://gitweb.torproject.org/torspec.git/tree/proposals/224-rend-spec-ng.txt#n2135";>
          <front>
            <title>Next-Generation Hidden Services in Tor</title>

-- 
To stop receiving notification emails like this one, please contact
gnunet@gnunet.org.



reply via email to

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