Changeset 549 for draft-ietf-httpbis-security-properties/latest/draft-ietf-httpbis-security-properties.html

Timestamp:

Mar 9, 2009, 4:13:57 AM (10 years ago)

Author:

julian.reschke@…

Message:

update boilerplate and Makefile

File:

• draft-ietf-httpbis-security-properties/latest/draft-ietf-httpbis-security-properties.html (modified) (7 diffs)

draft-ietf-httpbis-security-properties/latest/draft-ietf-httpbis-security-properties.html

@@ -62 +62 @@
   page-break-after: avoid;
 }
-h2 a {
-  color: black;
-}
-h3 {
+h3, h4, h5, h6 {
   font-size: 10pt;
   page-break-after: avoid;
 }
-h3 a {
-  color: black;
-}
-h4 {
-  font-size: 10pt;
-  page-break-after: avoid;
-}
-h4 a {
-  color: black;
-}
-h5 {
-  font-size: 10pt;
-  page-break-after: avoid;
-}
-h5 a {
+h2 a, h3 a, h4 a, h5 a, h6 a {
   color: black;
 }
@@ -183 +166 @@
 ul p {
   margin-left: 0em;
-}
-ul.ind {
-  list-style: none;
-  margin-left: 1.5em;
-  margin-right: 0em;
-  padding-left: 0em;
-}
-li.indline0 {
-  font-weight: bold;
-  line-height: 200%;
-  margin-left: 0em;
-  margin-right: 0em;
-}
-li.indline1 {
-  font-weight: normal;
-  line-height: 150%;
-  margin-left: 0em;
-  margin-right: 0em;
 }
 
@@ -333 +298 @@
       <link rel="Appendix" title="A Acknowledgements" href="#rfc.section.A">
       <link rel="Appendix" title="B Document History" href="#rfc.section.B">
-      <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/">
+      <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/">
       <link rel="schema.DC" href="http://purl.org/dc/elements/1.1/">
       <meta name="DC.Creator" content="Hoffman, P.">
       <meta name="DC.Creator" content="Melnikov, A.">
-      <meta name="DC.Identifier" content="urn:ietf:id:draft-ietf-httpbis-security-properties-02">
+      <meta name="DC.Identifier" content="urn:ietf:id:draft-ietf-httpbis-security-properties-latest">
       <meta name="DC.Date.Issued" scheme="ISO8601" content="2008-07">
       <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.">
@@ -353 +318 @@
          <tr>
             <td class="header left">
-               &lt;draft-ietf-httpbis-security-properties-02&gt;
+               &lt;draft-ietf-httpbis-security-properties-latest&gt;
                
             </td>
@@ -364 +329 @@
          <tr>
             <td class="header left">Expires: January 2009</td>
-            <td class="header right">July 14, 2008</td>
+            <td class="header right">July 2008</td>
          </tr>
       </table>
-      <p class="title">Security Requirements for HTTP<br><span class="filename">draft-ietf-httpbis-security-properties-02</span></p>
+      <p class="title">Security Requirements for HTTP<br><span class="filename">draft-ietf-httpbis-security-properties-latest</span></p>
       <h1><a id="rfc.status" href="#rfc.status">Status of this Memo</a></h1>
-      <p>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.
+      <p>This Internet-Draft is submitted to IETF pursuant to, and in full conformance with, the provisions of BCP 78 and BCP 79. 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.
       </p>
       <p>Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note
@@ -385 +354 @@
       </p>
       <p>This Internet-Draft will expire in January 2009.</p>
+      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
+      <p>Copyright © 2008 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
+      <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
+         and restrictions with respect to this document.
+      </p>
       <h1 id="rfc.abstract"><a href="#rfc.abstract">Abstract</a></h1> 
       <p>Recent IESG practice dictates that IETF protocols must specify mandatory-to-implement security mechanisms, so that all conformant
@@ -694 +668 @@
       <p id="rfc.section.B.3.p.2">Added the section on TLS for authentication.</p>
       <p id="rfc.section.B.3.p.3">Filled in section 2.5.</p>
-      <h1><a id="rfc.copyright" href="#rfc.copyright">Full Copyright Statement</a></h1>
-      <p>This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the
-         authors retain all their rights.
-      </p>
-      <p>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.
-      </p>
-      <hr class="noprint">
-      <h1 class="np"><a id="rfc.ipr" href="#rfc.ipr">Intellectual Property</a></h1>
-      <p>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.
-      </p>
-      <p>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 &lt;<a href="http://www.ietf.org/ipr">http://www.ietf.org/ipr</a>&gt;.
-      </p>
-      <p>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 <a href="mailto:ietf-ipr@ietf.org">ietf-ipr@ietf.org</a>.
-      </p>
    </body>
 </html>