Ignore:
Timestamp:
20/02/09 14:59:11 (13 years ago)
Author:
julian.reschke@…
Message:

Update to latest version of rfc2629.xslt, and add experimental version of xml2rfc.tcl (supporting the new IPR escape clause), use that clause in P1..P7 (but not for the method registrations).

File:
1 edited

Legend:

Unmodified
Added
Removed

  • draft-ietf-httpbis/latest/p7-auth.html

    r443 r446  
    6262  page-break-after: avoid;
    6363}
    64 h2 a {
    65   color: black;
    66 }
    67 h3 {
     64h3, h4, h5, h6 {
    6865  font-size: 10pt;
    6966  page-break-after: avoid;
    7067}
    71 h3 a {
    72   color: black;
    73 }
    74 h4 {
    75   font-size: 10pt;
    76   page-break-after: avoid;
    77 }
    78 h4 a {
    79   color: black;
    80 }
    81 h5 {
    82   font-size: 10pt;
    83   page-break-after: avoid;
    84 }
    85 h5 a {
     68h2 a, h3 a, h4 a, h5 a, h6 a {
    8669  color: black;
    8770}
    … …  
    375358      <link rel="Appendix" title="B Collected ABNF" href="#rfc.section.B">
    376359      <link rel="Appendix" title="C Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.C">
    377       <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.415, 2009-01-29 15:06:08, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">
     360      <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.421, 2009-02-20 13:12:03, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">
    378361      <link rel="schema.DC" href="http://purl.org/dc/elements/1.1/">
    379362      <meta name="DC.Creator" content="Fielding, R.">
    … …  
    472455         <tr>
    473456            <td class="header left"></td>
    474             <td class="header right">February 2, 2009</td>
     457            <td class="header right">February 20, 2009</td>
    475458         </tr>
    476459      </table>
    477460      <p class="title">HTTP/1.1, part 7: Authentication<br><span class="filename">draft-ietf-httpbis-p7-auth-latest</span></p>
    478461      <h1><a id="rfc.status" href="#rfc.status">Status of this Memo</a></h1>
    479       <p>By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she
    480          is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section
    481          6 of BCP 79.
     462      <p>This Internet-Draft is submitted to IETF pursuant to, and in full conformance with, the provisions of BCP 78 and BCP 79. This
     463         document may contain material from IETF Documents or IETF Contributions published or made publicly available before November
     464         10, 2008. The person(s) controlling the copyright in some of this material may not have granted the IETF Trust the right to
     465         allow modifications of such material outside the IETF Standards Process. Without obtaining an adequate license from the person(s)
     466         controlling the copyright in such materials, this document may not be modified outside the IETF Standards Process, and derivative
     467         works of it may not be created outside the IETF Standards Process, except to format it for publication as an RFC or to translate
     468         it into languages other than English.
    482469      </p>
    483470      <p>Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note
    … …  
    493480      </p>
    494481      <p>This Internet-Draft will expire in August 2009.</p>
     482      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
     483      <p>Copyright © 2009 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
     484      <p>This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents in effect on the date
     485         of publication of this document (<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>). Please review these documents carefully, as they describe your rights and restrictions with respect to this document.
     486      </p>
    495487      <h1 id="rfc.abstract"><a href="#rfc.abstract">Abstract</a></h1>
    496488      <p>The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information
    … …  
    559551            </ul>
    560552         </li>
    561          <li class="tocline0"><a href="#rfc.ipr">Intellectual Property and Copyright Statements</a></li>
    562553         <li class="tocline0"><a href="#rfc.index">Index</a></li>
    563554      </ul>
    … …  
    878869         <li>Add appendix containing collected and expanded ABNF, reorganize ABNF introduction.</li>
    879870      </ul>
    880       <h1><a id="rfc.copyright" href="#rfc.copyright">Full Copyright Statement</a></h1>
    881       <p>This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the
    882          authors retain all their rights.
    883       </p>
    884       <p>This document and the information contained herein are provided on an “AS IS” basis and THE CONTRIBUTOR, THE ORGANIZATION
    885          HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE
    886          DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN
    887          WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
    888       </p>
    889       <h1><a id="rfc.ipr" href="#rfc.ipr">Intellectual Property</a></h1>
    890       <p>The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might
    891          be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any
    892          license under such rights might or might not be available; nor does it represent that it has made any independent effort to
    893          identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and
    894          BCP 79.
    895       </p>
    896       <p>Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result
    897          of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users
    898          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;.
    899       </p>
    900       <p>The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary
    901          rights that may cover technology that may be required to implement this standard. Please address the information to the IETF
    902          at <a href="mailto:ietf-ipr@ietf.org">ietf-ipr@ietf.org</a>.
    903       </p>
    904871      <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1>
    905872      <p class="noprint"><a href="#rfc.index.4">4</a> <a href="#rfc.index.A">A</a> <a href="#rfc.index.G">G</a> <a href="#rfc.index.H">H</a> <a href="#rfc.index.P">P</a> <a href="#rfc.index.R">R</a> <a href="#rfc.index.S">S</a> <a href="#rfc.index.W">W</a>
Note: See TracChangeset for help on using the changeset viewer.