diff --git a/.htaccess b/.htaccess new file mode 100644 index 0000000..40fddde --- /dev/null +++ b/.htaccess @@ -0,0 +1 @@ +DirectoryIndex index.xml diff --git a/index.xml b/index.xml new file mode 100644 index 0000000..d8e8fab --- /dev/null +++ b/index.xml @@ -0,0 +1,198 @@ + + + + + + + +]> + + + + + + + + + + Cryptographic Hyperlinks + + + Digital Bazaar +
+ + 203 Roanoke Street W. + Blacksburg + VA + 24060 + US + + +1 540 961 4469 + msporny@digitalbazaar.com + http://manu.sporny.org/ +
+ + + + Security + + hyperlink + cryptography + security + + + +When using a hyperlink to fetch a resource from the Internet, it is often useful +to know if the resource has changed since the data was published. Cryptographic +hashes, such as SHA-256, are often used to determine if published data has +changed in unexpected ways. Due to the nature of most hyperlinks, the +cryptographic hash is often published separately from the link itself. +This specification describes a data model and serialization formats for +expressing cryptographically protected hyperlinks. The mechanisms described +in the document enables a system to publish a hyperlink in a way that +empowers a consuming application to determine if the resource associated with +the hyperlink has changed in unexpected ways. + + + + + +This specification is a work product of the +W3C Digital Verification Community Group +and the +W3C Credentials Community Group. +Feedback related to this specification should be logged in the +issue tracker +or be sent to +public-credentials@w3.org. + + + + +
+ +TBD - introduction + +
+
+ +A hashlink can be encoded in two different ways, the RECOMMENDED way to +express a hashlink is: +
+ hl:<resource-hash>:<optional-metadata> +
+ + +To enable existing applications utilizing historical URL schemes to provide +content integrity protection, hashlinks may also be encoded using URL +parameters: +
+ <url>?hl=<resource-hash> +
+ + + +TBD - refs to multihash and multibase + +
+ +TBD - resource hash +
+ +
+ +
+
+ +TBD - optional metadata + +
+ + +
+
+ + +
+
+
+ +
+ +TBD - serialization + + +
+ +TBD - CBOR Serialization + +
+ +TBD - hashlink example +
+ +
+ +
+
+ +
+ +TBD - URL Parameter Serialization + +
+ +TBD - hashlink as encoded URL parameters example +
+ +
+ +
+
+
+ + + + +&rfc2119; +&rfc6234; +&rfc7693; + + + +&rfc6150; +&rfc6151; + + +
+ +There are a number of security considerations to take into account when +implementing or utilizing this specification. + +TBD + +
+
+ + +TBD - test values + + +
+ + + + +
+ +
+
+ +The editors would like to thank the following individuals for feedback on and +implementations of the specification (in alphabetical order): + +
+ + \ No newline at end of file diff --git a/rfc2629.xsl b/rfc2629.xsl new file mode 100644 index 0000000..01f6b24 --- /dev/null +++ b/rfc2629.xsl @@ -0,0 +1,7412 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + 1 + 2 + 3 + 4 + 5 + 99 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + This stylesheet requires either an XSLT-1.0 processor with node-set() + extension function, or an XSLT-2.0 processor. Therefore, parts of the + document couldn't be displayed. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + IETF + + + + + + + + + + + + + + + + + + + + + + + yes + no + + + + + + + + + + + + + + 2010 + + + + + + + + 2010 + + + + + + + + 2010 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

Abstract

+ + + + + function parseXml(str) { + try { + var doc = new ActiveXObject("MSXML2.DOMDocument"); + doc.async = false; + if (doc.loadXML(str)) { + return ""; + } + else { + return doc.parseError.reason + "\n" + doc.parseError.srcText + " (" + doc.parseError.line + "/" + doc.parseError.linepos + ")"; + } + } + catch(e) { + return ""; + } + } + + + + + + inline + + + text2 + + + text + + + drawing + + + text + + + + + + + + 
<CODE BEGINS>
+ + + + + + 
<CODE ENDS>
+ + + + + + + + + +
+ XML PARSE ERROR; parsed the body below: + 
+        
+
+ resulting in: + 
+        
+
+
+ + + + + +
+ XML PARSE ERROR: +
+
+ + + + + + + + + + + + + + + +
+ + 
+          
+          
+          
+
+ +
+ + +
+ + 
+          
+          
+          
+
+ +
+ + + + 
+        
+        
+        
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + artwork line too long: '' ( characters) + + + + + + + + + + 69 + + + + + artwork line too long: '' ( characters) + + + + + + + + + + +

+ + + text-align: center + + + text-align: right + + + + + + + + + + + + + + + + + + + + + + + + + + {.} + + + + + + + + + +

+ + + + +
+ + + + + + () + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + , + + + + + + + + + + + + + +   + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Phone: + + + + + + + + + + + + + + Fax: + + + + + + + + + + + + Email: + EMail: + + + + mailto: + + + + + + + + + + + + URI: + + + + + + + + +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + < + + > + + + + + +
+ + + + +
+ + + +

Figure :

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ + +

+ + + + + + +
+ + + + + + + The @docName attribute '' should contain the base name, not the filename (thus no file extension). + + + + + + + + + + + + + + The @docName attribute '' should not contain the character ''. + + + + + + + The @docName attribute '' should not contain the character sequence '--'. + + + + + + The @docName attribute '' should start with 'draft-'. + + + + + + + latest + + + + + + + + The @docName attribute '' should end with a two-digit sequence number or 'latest'. + + + + + + The @docName attribute '', excluding sequence number, should have less than 50 characters. + + + + +

+ + + + +

+ Note: a later version of this document has been published as . +

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ + + + + +
+ + + + + + + + + + .iref.. + + + .iref. + + + + + + + + + + .extref.. + + + .extref. + + + + + + + +
    + + +
+ + + +
+ + +
+ + + +
+ + +
+ + + +
    + + +
+ + + + +
    + + +
+ + + +
    + + +
+ + + + +
    + + +
+ + + +
    + + +
+ + + + + + + + + + + +
  • + + + +
    • +     + + +
  • + + +
    • +     + + + + + + + +
  • + + + + + + +
    • +     + + + +
    + + + + + + + + + + + +
    +     +
    + + + + margin-left: em + + +
    +     + + + +
    + + + + + + + + + + + + + +
    +     + + + + + + +
    + + + + margin-left: em + + +
    +     +     + + + + + + + + + + + + + + +
    + + + + + + + + + +
    +
    + +
    +     + + + + + + + + +

    + + + + +

    + +     + + + +

    + + + +

    +     +     + + + +

    + + + + +

    +     +     + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + unused reference '' + + + + + + + + + + + + OK + + + + + all references to the normative reference '' appear to be informative + + + + + + + + + + + + invalid (empty) target attribute in reference '' + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + , Ed. + + + + + + + mailto: + + + + + + + + + + + + + + + , + and + + + , + + + + + + + + + + + + + + + + , + and + + + , + + + + + + + + “ + + + + + + + + + ” + + + + + , + + + + + +   + + + + +   + (work in progress) + + + + + + + RFC number preceding number in reference '' + + + + + + + + , + + + + + + <date> missing in reference '' (note that it can be empty) + + + + + + + date/@year should be a number: '' in reference '' + + + , +   + + + + + , < + + > + + + . + + +
    + +     + + + + + +     + + + + + + + del- + + + + + + + + + +

    + + + + + + + + + + + +

    +     + + + + h2 + h1 + + + + + + + + + + + + + + + + + + + + + . + + + + + + + + + + + + + + + + + + + + + + + +
    + +     + + + + + + + + + + + + + + + + + + + + + + http://www.w3.org/2006/03/hcard + + + http://dublincore.org/documents/2008/08/04/dc-html/ + + + + <xsl:apply-templates select="front/title" mode="get-text-content" /> + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + init(); + + + + + + + + + + + + + + + + + The paragraph below is misplaced; maybe a section is closed in the wrong place: + + + + + +
    +     + + + +     +     + + + + + + + + + + + + + + + + +

    + + .section. + + + + +

    +     + +     + + + + + + + + + + + + + + + + + + + + + + + + + + title/@abbrev too long (max 40 characters) + + + + + + title too long, should supply title/@abbrev attribute with less than 40 characters + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + The "appendix" element is deprecated, use "section" inside "back" instead. + + + + + + + + + + + + + + + + + + h + h6 + + + + + + + + + .section. + + + + + np + + + + + + + + + + + + + + + +   + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    + +     + +
    + +     + +
    + + + +     +     +     + + +
    +     + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + .xref.. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + ( + + + + + + + + + + + ) + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + .xref.. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Anchor '' in not found in source file ''. + + + + + + + + + x:rel attribute '' in reference to is expected to start with '#'. + + + + + + + + + + + + Appendix + Section + + + + + + + , + of + + + + + + + + + + + Anchor '' not found in . + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + of + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + ( + + + + + + + ) + + + , + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + no XSLT template for element '' + + <> + + </> + + + + + + + + + + + + + + + Independent Submission + + + Internet Engineering Task Force (IETF) + + + Internet Research Task Force (IRTF) + + + Internet Architecture Board (IAB) + + + + + + The /rfc/front/workgroup should only be used for Working Group drafts + + + + + + + + + + + WG submissions should include a /rfc/front/workgroup element + + + Network Working Group + + + + + Internet-Draft + Request for Comments: + + + + + Obsoletes: + + + + (if approved) + + + + + + BCP: + FYI: + STD: + + + + + + + Updates: + + + + (if approved) + + + + + + Category: + + + Intended status: + + + + + + Expires: + + + + + + + + + + ISSN: 2070-1721 + + + + + + + + + + + + + + + + , Editor + + + , + + + + + + + + + + + + + + + + + + + + + + + + + + + + , + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + on + + + + + + + + + + in + + + July + August + September + October + November + December + January + February + March + April + May + June + WRONG SYNTAX FOR MONTH + + + + + + + + + + + + + + + + + 31 + 29 + 28 + 30 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + 01 + 02 + 03 + 04 + 05 + 06 + 07 + 08 + 09 + 10 + 11 + 12 + WRONG SYNTAX FOR MONTH + + + + + + + January + February + March + April + May + June + July + August + September + October + November + December + WRONG SYNTAX FOR MONTH + + + + + + + Author's Address + Authors' Addresses + + + + + + + + + + + + + + + + + + +
    +

    + + + . + + + +

    + + +
    +     +     + + + + + + + + +
    + + + + + + Copyright © The IETF Trust (). + + + Copyright © The Internet Society (). + + + + + This document is subject to the rights, licenses and restrictions + contained in BCP 78 and at http://www.rfc-editor.org/copyright.html, and except as set forth therein, the authors + retain all their rights. + + + This document and the information contained herein are provided + on an “AS IS” basis and THE CONTRIBUTOR, + THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), + THE INTERNET SOCIETY, THE IETF TRUST + AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, + EXPRESS OR IMPLIED, + INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE + INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED + WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. + + + + + + Copyright © The Internet Society (). All Rights Reserved. + + + This document and translations of it may be copied and furnished to + others, and derivative works that comment on or otherwise explain it + or assist in its implementation may be prepared, copied, published and + distributed, in whole or in part, without restriction of any kind, + provided that the above copyright notice and this paragraph are + included on all such copies and derivative works. However, this + document itself may not be modified in any way, such as by removing + the copyright notice or references to the Internet Society or other + Internet organizations, except as needed for the purpose of + developing Internet standards in which case the procedures for + copyrights defined in the Internet Standards process must be + followed, or as required to translate it into languages other than + English. + + + The limited permissions granted above are perpetual and will not be + revoked by the Internet Society or its successors or assigns. + + + This document and the information contained herein is provided on an + “AS IS” basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING + TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING + BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION + HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF + MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. + + + +
    + +
    + + + + The IETF takes no position regarding the validity or scope of any + Intellectual Property Rights or other rights that might be claimed to + pertain to the implementation or use of the technology described in + this document or the extent to which any license under such rights + might or might not be available; nor does it represent that it has + made any independent effort to identify any such rights. Information + on the procedures with respect to rights in RFC documents + can be found in BCP 78 and BCP 79. + + + Copies of IPR disclosures made to the IETF Secretariat and any + assurances of licenses to be made available, or the result of an + attempt made to obtain a general license or permission for the use + of such proprietary rights by implementers or users of this + specification can be obtained from the IETF on-line IPR repository + at http://www.ietf.org/ipr. + + + The IETF invites any interested party to bring to its attention any + copyrights, patents or patent applications, or other proprietary + rights that may cover technology that may be required to implement + this standard. Please address the information to the IETF at + ietf-ipr@ietf.org. + + + + + The IETF takes no position regarding the validity or scope of + any intellectual property or other rights that might be claimed + to pertain to the implementation or use of the technology + described in this document or the extent to which any license + under such rights might or might not be available; neither does + it represent that it has made any effort to identify any such + rights. Information on the IETF's procedures with respect to + rights in standards-track and standards-related documentation + can be found in BCP-11. Copies of claims of rights made + available for publication and any assurances of licenses to + be made available, or the result of an attempt made + to obtain a general license or permission for the use of such + proprietary rights by implementors or users of this + specification can be obtained from the IETF Secretariat. + + + The IETF invites any interested party to bring to its + attention any copyrights, patents or patent applications, or + other proprietary rights which may cover technology that may be + required to practice this standard. Please address the + information to the IETF Executive Director. + + + + The IETF has been notified of intellectual property rights + claimed in regard to some or all of the specification contained + in this document. For more information consult the online list + of claimed rights. + + + + +
    + + + + +
    + + + Acknowledgement + Acknowledgment + + + + Funding for the RFC Editor function is provided by the IETF + Administrative Support Activity (IASA). + +
    +     + +
    + + + Acknowledgement + Acknowledgment + + + + Funding for the RFC Editor function is currently provided by + the Internet Society. + +
    +     + +     +     + +     + + + + + + + + + + + + + + + + + + + + + + [ + + , + + + + + + + + + + + ] + , + + + + + + + + + + + § + + + + + + + workaround for Saxon 9.1 bug; force evalutation of: + + # + + .xref. + + . + + + + # + + + + # + + + + Unsupported element type for insertSingleIref + + + + + + + + + + + , + + + + + + + + + + + + + + § + + + + + + + + + + + + #.xref.. + + + + + + + , + + + + + + +

    + + Index +

    + + +

    + + + + + + + + + + + + + + + + + + + + + + + + +

    + + +
    +
      + + + + + + + + + + +
    • + + + + + + + + + + + + + +
        + + + + + + + +
      • + + + +    + + + + + + + + + + +
          + + + + +
        • + + + + Appendix + + + Section + + + + +    + + + +
          • +           +           +
        +         + + + + + +
          + + + +
        • + + + + + + + + + Appendix + + + Section + + + + +    + + + +
          • +           +           +
        +         +         +
        • +         +         + + + + + + +
      • + + + + + + + + +    + + + + + + + + + + + + +
          + + + + + + + +
        • + + + + + + + + + +    + + + + + + + + + + +
          • +           +           +
        +         +
        • +         +         +         + + +         +
      +
      • +       + +       +
    +
    + +     + + + + + + This document may contain material from IETF Documents or IETF Contributions published or + made publicly available before November 10, 2008. The person(s) controlling the copyright in + some of this material may not have granted the IETF Trust the right to allow modifications of such + material outside the IETF Standards Process. Without obtaining an adequate license from the + person(s) controlling the copyright in such materials, this document may not be modified outside + the IETF Standards Process, and derivative works of it may not be created outside the IETF + Standards Process, except to format it for publication as an RFC or to translate it into languages + other than English. + + + + + This document may not be modified, and derivative works of it may not be + created, except to format it for publication as an RFC and to translate it + into languages other than English. + + + + + This document may not be modified, and derivative works of it may not be + created, except to format it for publication as an RFC or to translate it + into languages other than English. + + + + + This document may not be modified, and derivative works of it may not be + created, and it may not be published except as an Internet-Draft. + + +
    + + + Status of This Memo + Status of this Memo + + + + + + + + + + + This document is an Internet-Draft and is + in full conformance with all provisions of Section 10 of RFC2026. + + + This document is an Internet-Draft and is + in full conformance with all provisions of Section 10 of RFC2026 + except that the right to produce derivative works is not granted. + + + This document is an Internet-Draft and is + in full conformance with all provisions of Section 10 of RFC2026 + except that the right to produce derivative works is not granted. + (If this document becomes part of an IETF working group activity, + then it will be brought into full compliance with Section 10 of RFC2026.) + + + This document is an Internet-Draft and is + NOT offered in accordance with Section 10 of RFC2026, + and the author does not provide the IETF with any rights other + than to publish as an Internet-Draft. + + + + + This document is an Internet-Draft and is subject to all provisions + of section 3 of RFC 3667. By submitting this Internet-Draft, each + author represents that any applicable patent or other IPR claims of + which he or she is aware have been or will be disclosed, and any of + which he or she become aware will be disclosed, in accordance with + RFC 3668. + + + This document is an Internet-Draft and is subject to all provisions + of section 3 of RFC 3667. By submitting this Internet-Draft, each + author represents that any applicable patent or other IPR claims of + which he or she is aware have been or will be disclosed, and any of + which he or she become aware will be disclosed, in accordance with + RFC 3668. This document may not be modified, and derivative works of + it may not be created, except to publish it as an RFC and to + translate it into languages other than English, + other than to extract as-is + for separate use. + + + This document is an Internet-Draft and is subject to all provisions + of section 3 of RFC 3667 except for the right to produce derivative + works. By submitting this Internet-Draft, each author represents + that any applicable patent or other IPR claims of which he or she + is aware have been or will be disclosed, and any of which he or she + become aware will be disclosed, in accordance with RFC 3668. This + document may not be modified, and derivative works of it may + not be created, other than to extract + as-is for separate use. + + + + + By submitting this Internet-Draft, each + author represents that any applicable patent or other IPR claims of + which he or she is aware have been or will be disclosed, and any of + which he or she becomes aware will be disclosed, in accordance with + Section 6 of BCP 79. + + + By submitting this Internet-Draft, each + author represents that any applicable patent or other IPR claims of + which he or she is aware have been or will be disclosed, and any of + which he or she becomes aware will be disclosed, in accordance with + Section 6 of BCP 79. This document may not be modified, and derivative works of + it may not be created, except to publish it as an RFC and to + translate it into languages other than English, + other than to extract as-is + for separate use. + + + By submitting this Internet-Draft, each author represents + that any applicable patent or other IPR claims of which he or she + is aware have been or will be disclosed, and any of which he or she + becomes aware will be disclosed, in accordance with Section 6 of BCP 79. This + document may not be modified, and derivative works of it may + not be created, other than to extract + as-is for separate use. + + + + + This Internet-Draft is submitted in full conformance with + the provisions of BCP 78 and BCP 79. + + + + + This Internet-Draft is submitted to IETF in full conformance with + the provisions of BCP 78 and BCP 79. + + + CONFORMANCE UNDEFINED. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Internet-Drafts are working documents of the Internet Engineering + Task Force (IETF). Note that other groups may also distribute + working documents as Internet-Drafts. The list of current + Internet-Drafts is at http://datatracker.ietf.org/drafts/current/. + + + + + Internet-Drafts are working documents of the Internet Engineering + Task Force (IETF), its areas, and its working groups. + Note that other groups may also distribute working documents as + Internet-Drafts. + + + + + Internet-Drafts are draft documents valid for a maximum of six months + and may be updated, replaced, or obsoleted by other documents at any time. + It is inappropriate to use Internet-Drafts as reference material or to cite + them other than as “work in progress”. + + + + The list of current Internet-Drafts can be accessed at + http://www.ietf.org/ietf/1id-abstracts.txt. + + + The list of Internet-Draft Shadow Directories can be accessed at + http://www.ietf.org/shadow.html. + + + + This Internet-Draft will expire . + + + + + + This memo documents an Internet Best Current Practice. + + + + + This document specifies an Internet Best Current Practices for the Internet + Community, and requests discussion and suggestions for improvements. + Distribution of this memo is unlimited. + + + + + This document is not an Internet Standards Track specification; it is + published for examination, experimental implementation, and evaluation. + + + + + This memo defines an Experimental Protocol for the Internet community. + It does not specify an Internet standard of any kind. + Discussion and suggestions for improvement are requested. + Distribution of this memo is unlimited. + + + + + This document is not an Internet Standards Track specification; it is + published for the historical record. + + + + + This memo describes a historic protocol for the Internet community. + It does not specify an Internet standard of any kind. + Distribution of this memo is unlimited. + + + + + This is an Internet Standards Track document. + + + + + This document specifies an Internet standards track protocol for the Internet + community, and requests discussion and suggestions for improvements. + Please refer to the current edition of the “Internet Official Protocol + Standards” (STD 1) for the standardization state and status of this + protocol. Distribution of this memo is unlimited. + + + + + This document is not an Internet Standards Track specification; it is + published for informational purposes. + + + + + This memo provides information for the Internet community. + It does not specify an Internet standard of any kind. + Distribution of this memo is unlimited. + + + + + UNSUPPORTED CATEGORY. + + + + + + + + + + + + + This document defines an Experimental Protocol for the Internet + community. + + + This document defines a Historic Document for the Internet community. + + + + This document is a product of the Internet Engineering Task Force + (IETF). + + + It represents the consensus of the IETF community. It has + received public review and has been approved for publication by + the Internet Engineering Steering Group (IESG). + + + It has been approved for publication by the Internet Engineering + Steering Group (IESG). + + + + + + + + + + + + This document is a product of the Internet Architecture Board (IAB) + and represents information that the IAB has deemed valuable to + provide for permanent record. + + It represents the consensus of the Internet Architecture Board (IAB). + + + + This document is a product of the Internet Research Task Force (IRTF). + The IRTF publishes the results of Internet-related research and + development activities. These results might not be suitable for + deployment. + + + This RFC represents the consensus of the + Research Group of the Internet + Research Task Force (IRTF). + + + This RFC represents the individual opinion(s) of one or more + members of the Research Group of the + Internet Research Task Force (IRTF). + + + + + + + + This is a contribution to the RFC Series, independently of any other + RFC stream. The RFC Editor has chosen to publish this document at + its discretion and makes no statement about its value for + implementation or deployment. + + + + + + + + + + + Further information on BCPs is available in Section 2 of RFC 5741. + + + Further information on Internet Standards is available in Section + 2 of RFC 5741. + + + Not all documents approved by the IESG are a candidate for any + level of Internet Standard; see Section 2 of RFC 5741. + + + + + + + IAB + IRSG + RFC Editor + + + + Documents approved for publication by the + are not a candidate for any level + of Internet Standard; see Section 2 of RFC 5741. + + + + + Information about the current status of this document, any errata, and + how to provide feedback on it may be obtained at + http://www.rfc-editor.org/info/rfc. + + + +
    + + + + + + +
    + + Copyright © IETF Trust and the persons identified + as the document authors. All rights reserved. + + + + + This document is subject to BCP 78 and the IETF Trust's Legal + Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) + in effect on the date of publication of this document. Please + review these documents carefully, as they describe your rights + and restrictions with respect to this document. + + Code Components extracted from this document must include + Simplified BSD License text as described in Section 4.e of the + Trust Legal Provisions and are provided without warranty as + described in the Simplified BSD License. + + + + + + This document is subject to BCP 78 and the IETF Trust's Legal + Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) + in effect on the date of publication of this document. Please + review these documents carefully, as they describe your rights + and restrictions with respect to this document. Code Components + extracted from this document must include Simplified BSD License + text as described in Section 4.e of the Trust Legal Provisions + and are provided without warranty as described in the BSD License. + + + + + This document is subject to BCP 78 and the IETF Trust's Legal + Provisions Relating to IETF Documents in effect on the date of + publication of this document + (http://trustee.ietf.org/license-info). + Please review these documents carefully, as they describe your rights and restrictions with + respect to this document. + + + + + This document is subject to BCP 78 and the IETF Trust's Legal + Provisions Relating to IETF Documents + (http://trustee.ietf.org/license-info) in effect on the date of + publication of this document. Please review these documents + carefully, as they describe your rights and restrictions with respect + to this document. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    +     + + + + +
    + + Copyright © The IETF Trust (). All Rights Reserved. + +
    +     + +
    + + Copyright © The Internet Society (). All Rights Reserved. + +
    +     +     + +     + + + + +
    + +

    + Table of Contents +

    + +
      + +
    +     + + + + + + + + + + + + + + excluded + + + + excluded + + + + + + + + + + + + + + + + +     + + + + + + + + + + + + + + + + + + + + + +
  • + + + + +
    • +     + + + + + + + + +
  • + + + + +
    • +     + + + + + + + +
  • + + + + +
    • +     + +     + + + + + + + + + + + +
  • + + + + + +
    • +     + +     + + + + + + + + + + + + + + + + + + + + +
  • + + + + + + + +
    • +     +     + +
  • + + + + + + + + + +
      + + + + + + + + + + + + + + + + + +
    • + + + + + +
      • +       +
    +
    • +     +     +     + + + + + + + + + + .section. + + + + + +
  • + + + + + + + + + +
      + +
    +
    • +     + + +
  • + + + + + + + + + + + +
      + +
    +     + + + +
      + +
    +     +
    • +     +     + + + + + + + + + + + + + + + + + + + + + +
      +
    • Figures +
        + + Figure : + +
      • + + + + +
        • +         +
      +
      • +
    +     + + + + + + +     + + + + + + + + + + + + + + + Deleted duplicate anchors should have the prefix "deleted-": + + + + + + [] + + [del] + + [] + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + , + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + !"#$%&'()*+,-./0123456789;<=>?@[\]^`[|}~ + + + + + + + + + + + + + + + + + + !"#$%&'()*+,/;<=>?@[\]^`[|}~ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + .p. + + + + + +   + + + + + + + + + + + + + internal link target for '' is ambiguous; picking first. + + + + + + + + + + + + + + + + + + + Anchor '' not found in source file ''. + + + + + + + + + + + + + + + internal link target for '' does not exist. + + + + + + + + + + + + + + + + + + + + + + + +
    + + .section. + + +
    +     + + + + + + + + + + + + + + + + + + + + + + + ERROR: unknown BCP14 keyword: + + + + + + + + + +
    + + .section. + + + + + +
    +     + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + 0 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + should not get here + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + 2D + 2F + 30 + 31 + 32 + 33 + 34 + 35 + 36 + 37 + 38 + 39 + 41 + 42 + 43 + 44 + 45 + 46 + 47 + 48 + 49 + 4A + 4B + 4C + 4D + 4E + 4F + 50 + 51 + 52 + 53 + 54 + 55 + 56 + 57 + 58 + 59 + 5A + 61 + 62 + 63 + 64 + 65 + 66 + 67 + 68 + 69 + 6A + 6B + 6C + 6D + 6E + 6F + 70 + 71 + 72 + 73 + 74 + 75 + 76 + 77 + 78 + 79 + 7A + + ?? + + + + + + + + . + + + + + + + + + + + + + + + + %x + + + + + + + + + + + + + + + ┌ + + ┐ + + + + + + + + + + + ├ + + ┤ + + + + + + │ + + + + + │ + + + + + + + + + │ + + │ + + + + + + + + └ + + ┘ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Dangling ed:issueref: + + + + + + + + + + closedissue + openissue + + + + + + + + + + + + + + + + + +
    + + + + closed-issue + + + editor-issue + + + open-issue + + +  I  + +   + + + + + + [alternate link] + + + + + +   + (type: , status: ) +
    + Associated changes in this document: + + + + + + + + + <> + + + , + + . +
    + +     + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Resolution: + + + + + + + + + + + + + + + + + + Unexpected node in issue HTML: + + + + + + + + + + +
    +     + + + + + + + + + + + + + < + + > + + + + +

    Issues list

    + + + + + + + + + + + + + + + + + + + + + + + +
    IdTypeStatusDateRaised By
    + +     + + + + + + + + + The following anchor names may collide with internally generated anchors because of their prefix "": + + , + + + + + + + + + + + + document uses HTTP-style ABNF syntax, but doesn't reference RFC 2068 or 2616. + + + + + + + document uses ABNF syntax, but doesn't reference RFC 2234, 4234 or 5234. + + + + + + + + + The following target names do not exist: + + + (@target attribute missing) + + + , + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + .change.. + + + + +
    + + + + + ↑ + + + + + closed-issue + + + editor-issue + + + open-issue + + +  I  + + + ↓ + +   +
    +     + + + ↑ + + + + + + + + closed-issue noprint + + + editor-issue noprint + + + open-issue noprint + + +  I  + + + ↓ + + +     +     +     + + + + + + + + + + + + + + + +  i  + + + + + + + + + + + + + + + + + + + + + + + + + + + + + del + + + ins + + + + + + + + del- + + + + + + + unnumbered- + + + + + + + + . + + + + + + + + + + + + + . + + + + + . + + + + + + + + + + + + + . + + + + + + + + + + + + + + + + + + TRACE + + + + + + + + + + + WARNING + + + + + + + + + + + + WARNING + + + + + + + + + + + + INFO + + + + + + + + + + + + ERROR + + + + + + + + + + + + : + + +
    +     + + + + +     + +     + + + + + + + + + +
    + + +
    + + + + tt + + + + + full + + + left + right + center + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    Table :
    + + + + + + + + + + + + + + + left + + + + Unknown align attribute on ttcol: + + + + +
    + +
    + + + + + + + + + + + + + + + Unknown align attribute on ttcol: + + + + + width: ; + + + + + + + + + + + + + + + + .comment. + + + + + + + + + + + + + + + + + + [ + + + + : + + -- + ] + + + + : + + + + + + [ + + + + ] + + + + + + + + + + +

    + + Editorial Comments +

    + +
    + + + + + + + + + .comment. + + + + +
    + [] +
    +
    + + -- +
    +     +
    +     + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Expires + + + + + + + + + + + + Best Current Practice + Historic + Informational + Standards Track + Experimental + (category unknown) + + + + + + + + + + + + + + + + + + + Internet-Draft + RFC + + + + + + http://greenbytes.de/tech/webdav/rfc2629.xslt, + + + + + + + + + + + + + + + + + + + + + keyword element appears to contain a comma-separated list, split into multiple elements instead. + + + + , + + + + + + + + en + + + + + + + + + + + unnumbered- + + + + + + + + + + + + + + . + + + + + + + + + + + . + + + + + + + + + + + + + + + + + + + + + + + + + . + + + + + + Appendix + Section + + + + + + .table. + + + + + + u. + + + + + + + + .figure. + + + + + + u. + + + + + + + + + + + + + + + + @initials '': did you mean ''? + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + excessive whitespace in : '' + + + + + missing text in + + + + + + + + + + + excessive whitespace in email address: '' + + + + + + + + email should not include URI scheme: '' + + + + + + + + + + + + + + + + + + excessive whitespace in URI: '' + + + + + URI is empty + + + + + + + + + np + + + + + +
    +     +     + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + bad PI syntax: + + + + + + + + + bad PI value syntax: + + + + + + + + + + '" + + + + + + pseudo-attribute value needs to be quoted: + + + + + + unmatched quote in: + + + + + + + + + + + + + + + + + + + + + + + unsupported rfc-ext pseudo-attribute '' + + + + + + + + + + the rfc include pseudo-attribute is not supported by this processor, see http://greenbytes.de/tech/webdav/rfc2629xslt/rfc2629xslt.html#examples.internalsubset for help. + + + + + + + + + + + + + + + + + + + + + duplicate pseudo-attribute , overwriting value + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + (at line + + + + + + + + + of + + + + ) + + + + + (at line + + + + + + + + + of + + + + ) + + + + + + + this['node-set'] = function (x) { + return x; + } + + + + + + function twodigits(s) { + return s < 10 ? "0" + s : s; + } + + this['date-time'] = function (x) { + var now = new Date(); + var offs = now.getTimezoneOffset(); + return now.getFullYear() + "-" + + twodigits(1 + now.getMonth()) + "-" + + twodigits(now.getDate()) + "T" + + twodigits(now.getHours()) + ":" + + twodigits(now.getMinutes()) + ":" + + twodigits(now.getSeconds()) + + (offs >= 0 ? "-" : "+") + + twodigits(Math.abs(offs) / 60) + ":" + + twodigits(Math.abs(offs) % 60); + } + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Specified year does not match system date () + Specified month does not match system date () + Specified day does not match system date + Can't default year when month or day is specified + Can't default month when day is specified + yes + + + + yes + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + 0000 + + + + + + + 00 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +