Changeset 549 for draft-ietf-httpbis-security-properties/latest/draft-ietf-httpbis-security-properties.html
- Timestamp:
- 09/03/09 11:13:57 (14 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis-security-properties/latest/draft-ietf-httpbis-security-properties.html
r279 r549 62 62 page-break-after: avoid; 63 63 } 64 h2 a { 65 color: black; 66 } 67 h3 { 64 h3, h4, h5, h6 { 68 65 font-size: 10pt; 69 66 page-break-after: avoid; 70 67 } 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 { 68 h2 a, h3 a, h4 a, h5 a, h6 a { 86 69 color: black; 87 70 } … … 183 166 ul p { 184 167 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;203 168 } 204 169 … … 333 298 <link rel="Appendix" title="A Acknowledgements" href="#rfc.section.A"> 334 299 <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/"> 336 301 <link rel="schema.DC" href="http://purl.org/dc/elements/1.1/"> 337 302 <meta name="DC.Creator" content="Hoffman, P."> 338 303 <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"> 340 305 <meta name="DC.Date.Issued" scheme="ISO8601" content="2008-07"> 341 306 <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> 354 319 <td class="header left"> 355 <draft-ietf-httpbis-security-properties- 02>320 <draft-ietf-httpbis-security-properties-latest> 356 321 357 322 </td> … … 364 329 <tr> 365 330 <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> 367 332 </tr> 368 333 </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> 370 335 <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. 374 343 </p> 375 344 <p>Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note … … 385 354 </p> 386 355 <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> 387 361 <h1 id="rfc.abstract"><a href="#rfc.abstract">Abstract</a></h1> 388 362 <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> 695 669 <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, the698 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 ORGANIZATION701 HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE702 DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN703 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 might708 be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any709 license under such rights might or might not be available; nor does it represent that it has made any independent effort to710 identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and711 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 result714 of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users715 of this specification can be obtained from the IETF on-line IPR repository at <<a href="http://www.ietf.org/ipr">http://www.ietf.org/ipr</a>>.716 </p>717 <p>The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary718 rights that may cover technology that may be required to implement this standard. Please address the information to the IETF719 at <a href="mailto:ietf-ipr@ietf.org">ietf-ipr@ietf.org</a>.720 </p>721 670 </body> 722 671 </html>
Note: See TracChangeset
for help on using the changeset viewer.