gnunet-svn
[Top][All Lists]
Advanced

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

[GNUnet-SVN] [lsd0001] branch master updated: update punycode refs


From: gnunet
Subject: [GNUnet-SVN] [lsd0001] branch master updated: update punycode refs
Date: Sat, 05 Oct 2019 12:46:07 +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 050c36f  update punycode refs
050c36f is described below

commit 050c36f8b667809ebc282b2a718e3322d128ec6b
Author: Schanzenbach, Martin <address@hidden>
AuthorDate: Sat Oct 5 12:43:57 2019 +0200

    update punycode refs
---
 draft-schanzen-gns.html |  8 ++++----
 draft-schanzen-gns.txt  | 12 ++++++------
 draft-schanzen-gns.xml  |  4 ++--
 3 files changed, 12 insertions(+), 12 deletions(-)

diff --git a/draft-schanzen-gns.html b/draft-schanzen-gns.html
index 3b5b8cc..ed0302e 100644
--- a/draft-schanzen-gns.html
+++ b/draft-schanzen-gns.html
@@ -1451,7 +1451,7 @@ async function addMetadata(){try{const 
e=document.styleSheets[0].cssRules;for(le
 <p id="section-3.3-3">
          NOTE: If an application uses a LEHO value in an HTTP request header
          (e.g. "Host:" header) it must be converted to a punycode 
representation
-         <span>[<a href="#RFC3492" class="xref">RFC3492</a>]</span>.<a 
href="#section-3.3-3" class="pilcrow">¶</a></p>
+         <span>[<a href="#RFC5891" class="xref">RFC5891</a>]</span>.<a 
href="#section-3.3-3" class="pilcrow">¶</a></p>
 </section>
 </div>
 <div id="gnsrecords_nick">
@@ -2144,9 +2144,6 @@ async function addMetadata(){try{const 
e=document.styleSheets[0].cssRules;for(le
 <dt id="RFC1035">[RFC1035]</dt>
       <dd>
 <span class="refAuthor">Mockapetris, P.</span>, <span class="refTitle">"Domain 
names - implementation and specification"</span>, <span class="seriesInfo">STD 
13</span>, <span class="seriesInfo">RFC 1035</span>, <span 
class="seriesInfo">DOI 10.17487/RFC1035</span>, <time 
datetime="1987-11">November 1987</time>, <span>&lt;<a 
href="https://www.rfc-editor.org/info/rfc1035";>https://www.rfc-editor.org/info/rfc1035</a>&gt;</span>.
 </dd>
-<dt id="RFC3492">[RFC3492]</dt>
-      <dd>
-<span class="refAuthor">Costello, A.</span>, <span class="refTitle">"Punycode: 
A Bootstring encoding of Unicode for Internationalized Domain Names in 
Applications (IDNA)"</span>, <span class="seriesInfo">RFC 3492</span>, <span 
class="seriesInfo">DOI 10.17487/RFC3492</span>, <time datetime="2003-03">March 
2003</time>, <span>&lt;<a 
href="https://www.rfc-editor.org/info/rfc3492";>https://www.rfc-editor.org/info/rfc3492</a>&gt;</span>.
 </dd>
 <dt id="RFC3629">[RFC3629]</dt>
       <dd>
 <span class="refAuthor">Yergeau, F.</span>, <span class="refTitle">"UTF-8, a 
transformation format of ISO 10646"</span>, <span class="seriesInfo">STD 
63</span>, <span class="seriesInfo">RFC 3629</span>, <span 
class="seriesInfo">DOI 10.17487/RFC3629</span>, <time 
datetime="2003-11">November 2003</time>, <span>&lt;<a 
href="https://www.rfc-editor.org/info/rfc3629";>https://www.rfc-editor.org/info/rfc3629</a>&gt;</span>.
 </dd>
@@ -2161,6 +2158,9 @@ async function addMetadata(){try{const 
e=document.styleSheets[0].cssRules;for(le
 <dt id="RFC5890">[RFC5890]</dt>
       <dd>
 <span class="refAuthor">Klensin, J.</span>, <span 
class="refTitle">"Internationalized Domain Names for Applications (IDNA): 
Definitions and Document Framework"</span>, <span class="seriesInfo">RFC 
5890</span>, <span class="seriesInfo">DOI 10.17487/RFC5890</span>, <time 
datetime="2010-08">August 2010</time>, <span>&lt;<a 
href="https://www.rfc-editor.org/info/rfc5890";>https://www.rfc-editor.org/info/rfc5890</a>&gt;</span>.
 </dd>
+<dt id="RFC5891">[RFC5891]</dt>
+      <dd>
+<span class="refAuthor">Klensin, J.</span>, <span 
class="refTitle">"Internationalized Domain Names in Applications (IDNA): 
Protocol"</span>, <span class="seriesInfo">RFC 5891</span>, <span 
class="seriesInfo">DOI 10.17487/RFC5891</span>, <time datetime="2010-08">August 
2010</time>, <span>&lt;<a 
href="https://www.rfc-editor.org/info/rfc5891";>https://www.rfc-editor.org/info/rfc5891</a>&gt;</span>.
 </dd>
 <dt id="RFC6895">[RFC6895]</dt>
       <dd>
 <span class="refAuthor">Eastlake 3rd, D.</span>, <span 
class="refTitle">"Domain Name System (DNS) IANA Considerations"</span>, <span 
class="seriesInfo">BCP 42</span>, <span class="seriesInfo">RFC 6895</span>, 
<span class="seriesInfo">DOI 10.17487/RFC6895</span>, <time 
datetime="2013-04">April 2013</time>, <span>&lt;<a 
href="https://www.rfc-editor.org/info/rfc6895";>https://www.rfc-editor.org/info/rfc6895</a>&gt;</span>.
 </dd>
diff --git a/draft-schanzen-gns.txt b/draft-schanzen-gns.txt
index c6b7677..5a92bc1 100644
--- a/draft-schanzen-gns.txt
+++ b/draft-schanzen-gns.txt
@@ -350,7 +350,7 @@ Internet-Draft             The GNU Name System              
   July 2019
 
    NOTE: If an application uses a LEHO value in an HTTP request header
    (e.g.  "Host:" header) it must be converted to a punycode
-   representation [RFC3492].
+   representation [RFC5891].
 
 3.4.  NICK
 
@@ -978,11 +978,6 @@ Internet-Draft             The GNU Name System             
    July 2019
               specification", STD 13, RFC 1035, DOI 10.17487/RFC1035,
               November 1987, <https://www.rfc-editor.org/info/rfc1035>.
 
-   [RFC3492]  Costello, A., "Punycode: A Bootstring encoding of Unicode
-              for Internationalized Domain Names in Applications
-              (IDNA)", RFC 3492, DOI 10.17487/RFC3492, March 2003,
-              <https://www.rfc-editor.org/info/rfc3492>.
-
    [RFC3629]  Yergeau, F., "UTF-8, a transformation format of ISO
               10646", STD 63, RFC 3629, DOI 10.17487/RFC3629, November
               2003, <https://www.rfc-editor.org/info/rfc3629>.
@@ -1003,6 +998,11 @@ Internet-Draft             The GNU Name System            
     July 2019
               RFC 5890, DOI 10.17487/RFC5890, August 2010,
               <https://www.rfc-editor.org/info/rfc5890>.
 
+   [RFC5891]  Klensin, J., "Internationalized Domain Names in
+              Applications (IDNA): Protocol", RFC 5891,
+              DOI 10.17487/RFC5891, August 2010,
+              <https://www.rfc-editor.org/info/rfc5891>.
+
 
 
 Schanzenbach, et al.     Expires 24 January 2020               [Page 18]
diff --git a/draft-schanzen-gns.xml b/draft-schanzen-gns.xml
index 2165422..8bcec1e 100644
--- a/draft-schanzen-gns.xml
+++ b/draft-schanzen-gns.xml
@@ -342,7 +342,7 @@
        <t>
          NOTE: If an application uses a LEHO value in an HTTP request header
          (e.g. "Host:" header) it must be converted to a punycode 
representation
-         <xref target="RFC3492" />.
+         <xref target="RFC5891" />.
        </t>
      </section>
      <section anchor="gnsrecords_nick" numbered="true" toc="default">
@@ -977,10 +977,10 @@
    <back>
      <references>
        <name>Normative References</name>
-       <reference anchor="RFC3492" 
target="https://www.rfc-editor.org/info/rfc3492";><front><title>Punycode: A 
Bootstring encoding of Unicode for Internationalized Domain Names in 
Applications (IDNA)</title><author initials="A." surname="Costello" 
fullname="A. Costello"><organization/></author><date year="2003" 
month="March"/><abstract><t>Punycode is a simple and efficient transfer 
encoding syntax designed for use with Internationalized Domain Names in 
Applications (IDNA).  It uniquely an [...]
        <reference anchor="RFC7748" 
target="https://www.rfc-editor.org/info/rfc7748";><front><title>Elliptic Curves 
for Security</title><author initials="A." surname="Langley" fullname="A. 
Langley"><organization/></author><author initials="M." surname="Hamburg" 
fullname="M. Hamburg"><organization/></author><author initials="S." 
surname="Turner" fullname="S. Turner"><organization/></author><date year="2016" 
month="January"/><abstract><t>This memo specifies two elliptic curves over 
prime fie [...]
        <reference anchor="RFC3826" 
target="https://www.rfc-editor.org/info/rfc3826";><front><title>The Advanced 
Encryption Standard (AES) Cipher Algorithm in the SNMP User-based Security 
Model</title><author initials="U." surname="Blumenthal" fullname="U. 
Blumenthal"><organization/></author><author initials="F." surname="Maino" 
fullname="F. Maino"><organization/></author><author initials="K." 
surname="McCloghrie" fullname="K. McCloghrie"><organization/></author><date 
year="2004" month="Ju [...]
        <reference anchor="RFC5890" 
target="https://www.rfc-editor.org/info/rfc5890";><front><title>Internationalized
 Domain Names for Applications (IDNA): Definitions and Document 
Framework</title><author initials="J." surname="Klensin" fullname="J. 
Klensin"><organization/></author><date year="2010" 
month="August"/><abstract><t>This document is one of a collection that, 
together, describe the protocol and usage context for a revision of 
Internationalized Domain Names for Applications (IDN [...]
+       <reference anchor="RFC5891" 
target="https://www.rfc-editor.org/info/rfc5891";><front><title>Internationalized
 Domain Names in Applications (IDNA): Protocol</title><author initials="J." 
surname="Klensin" fullname="J. Klensin"><organization/></author><date 
year="2010" month="August"/><abstract><t>This document is the revised protocol 
definition for Internationalized Domain Names (IDNs).  The rationale for 
changes, the relationship to the older specification, and important terminology 
[...]
        <reference anchor="RFC5869" 
target="https://www.rfc-editor.org/info/rfc5869";>
          <front>
            <title>

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



reply via email to

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