Ignore:
Timestamp:
Dec 17, 2007, 11:04:17 PM (12 years ago)
Author:
fielding@…
Message:

Switch to ID mode and add an editorial note so that
rfcdiff doesn't freak out on the first two pages of diffs.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/orig/rfc2616-symrefs.html

    r17 r50  
    298298@page {
    299299  @top-left {
    300        content: "RFC 2616";
     300       content: "INTERNET DRAFT";
    301301  }
    302302  @top-right {
     
    351351      <link rel="Appendix" title="19 Appendices" href="#rfc.section.19">
    352352      <link rel="Appendix" title="20 Index" href="#rfc.section.20">
    353       <link rel="Alternate" title="Authorative ASCII version" href="http://www.ietf.org/rfc/rfc2616.txt">
    354       <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.352, 2007/12/09 19:23:50, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">
     353      <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.353, 2007/12/11 23:20:44, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">
    355354      <link rel="schema.DC" href="http://purl.org/dc/elements/1.1/">
    356355      <meta name="DC.Creator" content="Fielding, R.">
     
    361360      <meta name="DC.Creator" content="Leach, P.">
    362361      <meta name="DC.Creator" content="Berners-Lee, T.">
    363       <meta name="DC.Identifier" content="urn:ietf:rfc:2616">
     362      <meta name="DC.Identifier" content="urn:ietf:id:rfc2616-symrefs">
    364363      <meta name="DC.Date.Issued" scheme="ISO8601" content="1999-06">
    365364      <meta name="DC.Relation.Replaces" content="urn:ietf:rfc:2068">
     
    373372         </tr>
    374373         <tr>
    375             <td class="header left">Request for Comments: 2616</td>
     374            <td class="header left">Internet Draft</td>
    376375            <td class="header right">UC Irvine</td>
    377376         </tr>
    378377         <tr>
    379             <td class="header left">Obsoletes: <a href="http://tools.ietf.org/html/rfc2068">2068</a></td>
     378            <td class="header left">
     379               &lt;rfc2616-symrefs&gt;
     380               
     381            </td>
    380382            <td class="header right">J. Gettys</td>
    381383         </tr>
    382384         <tr>
    383             <td class="header left">Category: Standards Track</td>
     385            <td class="header left">Obsoletes: <a href="http://tools.ietf.org/html/rfc2068">2068</a> (if approved)
     386            </td>
    384387            <td class="header right">Compaq/W3C</td>
    385388         </tr>
    386389         <tr>
    387             <td class="header left"></td>
     390            <td class="header left">Intended status: Standards Track</td>
    388391            <td class="header right">J. Mogul</td>
    389392         </tr>
    390393         <tr>
    391             <td class="header left"></td>
     394            <td class="header left">Expires: December 1999</td>
    392395            <td class="header right">Compaq</td>
    393396         </tr>
     
    429432         </tr>
    430433      </table>
    431       <p class="title">Hypertext Transfer Protocol -- HTTP/1.1</p>
     434      <p class="title">Hypertext Transfer Protocol -- HTTP/1.1<br><span class="filename">rfc2616-symrefs</span></p>
    432435      <h1><a id="rfc.status" href="#rfc.status">Status of this Memo</a></h1>
    433       <p>This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions
    434          for improvements. Please refer to the current edition of the “Internet Official Protocol Standards” (STD 1) for the standardization
    435          state and status of this protocol. Distribution of this memo is unlimited.
    436       </p>
     436      <p>By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she
     437         is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section
     438         6 of BCP 79.
     439      </p>
     440      <p>Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note
     441         that other groups may also distribute working documents as Internet-Drafts.
     442      </p>
     443      <p>Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other
     444         documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as “work
     445         in progress”.
     446      </p>
     447      <p>The list of current Internet-Drafts can be accessed at &lt;<a href="http://www.ietf.org/ietf/1id-abstracts.txt">http://www.ietf.org/ietf/1id-abstracts.txt</a>&gt;.
     448      </p>
     449      <p>The list of Internet-Draft Shadow Directories can be accessed at &lt;<a href="http://www.ietf.org/shadow.html">http://www.ietf.org/shadow.html</a>&gt;.
     450      </p>
     451      <p>This Internet-Draft will expire in December 1999.</p>
    437452      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    438453      <p>Copyright © The Internet Society (1999). All Rights Reserved.</p>
     
    445460      <p>HTTP has been in use by the World-Wide Web global information initiative since 1990. This specification defines the protocol
    446461         referred to as "HTTP/1.1", and is an update to RFC 2068 <a href="#RFC2068" id="rfc.xref.RFC2068.1"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a>.
     462      </p>
     463      <h1 id="rfc.note.1"><a href="#rfc.note.1">Editorial Note (To be removed by RFC Editor)</a></h1>
     464      <p>This version of the HTTP specification contains only XML processing changes from [RFC2616] in internet-draft form for use
     465         in creating diffs.
    447466      </p>
    448467      <hr class="noprint">
     
    60496068      <p id="rfc.section.20.p.1">Please see the PostScript version of this RFC for the INDEX.</p>
    60506069      <h1><a id="rfc.copyright" href="#rfc.copyright">Full Copyright Statement</a></h1>
    6051       <p>Copyright © The Internet Society (1999). All Rights Reserved.</p>
    6052       <p>This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise
    6053          explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without
    6054          restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative
    6055          works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references
    6056          to the Internet Society or other Internet organizations, except as needed for the purpose of developing Internet standards
    6057          in which case the procedures for copyrights defined in the Internet Standards process must be followed, or as required to
    6058          translate it into languages other than English.
    6059       </p>
    6060       <p>The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assignees.</p>
    6061       <p>This document and the information contained herein is provided on an “;AS IS” basis and THE INTERNET SOCIETY AND THE INTERNET
    6062          ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE
    6063          OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR
    6064          PURPOSE.
     6070      <p>Copyright © The Internet Society (1999).</p>
     6071      <p>This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the
     6072         authors retain all their rights.
     6073      </p>
     6074      <p>This document and the information contained herein are provided on an “AS IS” basis and THE CONTRIBUTOR, THE ORGANIZATION
     6075         HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES,
     6076         EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY
     6077         RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
    60656078      </p>
    60666079      <h1><a id="rfc.ipr" href="#rfc.ipr">Intellectual Property</a></h1>
    6067       <p>The IETF takes no position regarding the validity or scope of any intellectual property or other rights that might be claimed
    6068          to pertain to the implementation or use of the technology described in this document or the extent to which any license under
    6069          such rights might or might not be available; neither does it represent that it has made any effort to identify any such rights.
    6070          Information on the IETF's procedures with respect to rights in standards-track and standards-related documentation can be
    6071          found in BCP-11. Copies of claims of rights made available for publication and any assurances of licenses to be made available,
    6072          or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementors
    6073          or users of this specification can be obtained from the IETF Secretariat.
     6080      <p>The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might
     6081         be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any
     6082         license under such rights might or might not be available; nor does it represent that it has made any independent effort to
     6083         identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and
     6084         BCP 79.
     6085      </p>
     6086      <p>Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result
     6087         of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users
     6088         of this specification can be obtained from the IETF on-line IPR repository at &lt;<a href="http://www.ietf.org/ipr">http://www.ietf.org/ipr</a>&gt;.
    60746089      </p>
    60756090      <p>The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary
    6076          rights which may cover technology that may be required to practice this standard. Please address the information to the IETF
    6077          Executive Director.
     6091         rights that may cover technology that may be required to implement this standard. Please address the information to the IETF
     6092         at <a href="mailto:ietf-ipr@ietf.org">ietf-ipr@ietf.org</a>.
    60786093      </p>
    60796094      <h1>Acknowledgement</h1>
Note: See TracChangeset for help on using the changeset viewer.