Ignore:
Timestamp:
Mar 9, 2009, 4:13:57 AM (11 years ago)
Author:
julian.reschke@…
Message:

update boilerplate and Makefile

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis-security-properties/latest/draft-ietf-httpbis-security-properties.html

    r279 r549  
    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}
     
    183166ul p {
    184167  margin-left: 0em;
    185 }
    186 ul.ind {
    187   list-style: none;
    188   margin-left: 1.5em;
    189   margin-right: 0em;
    190   padding-left: 0em;
    191 }
    192 li.indline0 {
    193   font-weight: bold;
    194   line-height: 200%;
    195   margin-left: 0em;
    196   margin-right: 0em;
    197 }
    198 li.indline1 {
    199   font-weight: normal;
    200   line-height: 150%;
    201   margin-left: 0em;
    202   margin-right: 0em;
    203168}
    204169
     
    333298      <link rel="Appendix" title="A Acknowledgements" href="#rfc.section.A">
    334299      <link rel="Appendix" title="B Document History" href="#rfc.section.B">
    335       <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.379, 2008-07-06 13:38:32, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">
     300      <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.426, 2009-03-07 10:31:10, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">
    336301      <link rel="schema.DC" href="http://purl.org/dc/elements/1.1/">
    337302      <meta name="DC.Creator" content="Hoffman, P.">
    338303      <meta name="DC.Creator" content="Melnikov, A.">
    339       <meta name="DC.Identifier" content="urn:ietf:id:draft-ietf-httpbis-security-properties-02">
     304      <meta name="DC.Identifier" content="urn:ietf:id:draft-ietf-httpbis-security-properties-latest">
    340305      <meta name="DC.Date.Issued" scheme="ISO8601" content="2008-07">
    341306      <meta name="DC.Description.Abstract" content="Recent IESG practice dictates that IETF protocols must specify mandatory-to-implement security mechanisms, so that all conformant implementations share a common baseline. This document examines all widely deployed HTTP security technologies, and analyzes the trade-offs of each.">
     
    353318         <tr>
    354319            <td class="header left">
    355                &lt;draft-ietf-httpbis-security-properties-02&gt;
     320               &lt;draft-ietf-httpbis-security-properties-latest&gt;
    356321               
    357322            </td>
     
    364329         <tr>
    365330            <td class="header left">Expires: January 2009</td>
    366             <td class="header right">July 14, 2008</td>
     331            <td class="header right">July 2008</td>
    367332         </tr>
    368333      </table>
    369       <p class="title">Security Requirements for HTTP<br><span class="filename">draft-ietf-httpbis-security-properties-02</span></p>
     334      <p class="title">Security Requirements for HTTP<br><span class="filename">draft-ietf-httpbis-security-properties-latest</span></p>
    370335      <h1><a id="rfc.status" href="#rfc.status">Status of this Memo</a></h1>
    371       <p>By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she
    372          is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section
    373          6 of BCP 79.
     336      <p>This Internet-Draft is submitted to IETF pursuant to, and in full conformance with, the provisions of BCP 78 and BCP 79. This
     337         document may contain material from IETF Documents or IETF Contributions published or made publicly available before November
     338         10, 2008. The person(s) controlling the copyright in some of this material may not have granted the IETF Trust the right to
     339         allow modifications of such material outside the IETF Standards Process. Without obtaining an adequate license from the person(s)
     340         controlling the copyright in such materials, this document may not be modified outside the IETF Standards Process, and derivative
     341         works of it may not be created outside the IETF Standards Process, except to format it for publication as an RFC or to translate
     342         it into languages other than English.
    374343      </p>
    375344      <p>Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note
     
    385354      </p>
    386355      <p>This Internet-Draft will expire in January 2009.</p>
     356      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
     357      <p>Copyright © 2008 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
     358      <p>This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights
     359         and restrictions with respect to this document.
     360      </p>
    387361      <h1 id="rfc.abstract"><a href="#rfc.abstract">Abstract</a></h1>
    388362      <p>Recent IESG practice dictates that IETF protocols must specify mandatory-to-implement security mechanisms, so that all conformant
     
    694668      <p id="rfc.section.B.3.p.2">Added the section on TLS for authentication.</p>
    695669      <p id="rfc.section.B.3.p.3">Filled in section 2.5.</p>
    696       <h1><a id="rfc.copyright" href="#rfc.copyright">Full Copyright Statement</a></h1>
    697       <p>This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the
    698          authors retain all their rights.
    699       </p>
    700       <p>This document and the information contained herein are provided on an “AS IS” basis and THE CONTRIBUTOR, THE ORGANIZATION
    701          HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE
    702          DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN
    703          WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
    704       </p>
    705       <hr class="noprint">
    706       <h1 class="np"><a id="rfc.ipr" href="#rfc.ipr">Intellectual Property</a></h1>
    707       <p>The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might
    708          be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any
    709          license under such rights might or might not be available; nor does it represent that it has made any independent effort to
    710          identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and
    711          BCP 79.
    712       </p>
    713       <p>Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result
    714          of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users
    715          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;.
    716       </p>
    717       <p>The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary
    718          rights that may cover technology that may be required to implement this standard. Please address the information to the IETF
    719          at <a href="mailto:ietf-ipr@ietf.org">ietf-ipr@ietf.org</a>.
    720       </p>
    721670   </body>
    722671</html>
Note: See TracChangeset for help on using the changeset viewer.