Changeset 220 for draft-ietf-httpbis-security-properties/latest
- Timestamp:
- 22/02/08 20:33:43 (15 years ago)
- Location:
- draft-ietf-httpbis-security-properties/latest
- Files:
-
- 4 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis-security-properties/latest/draft-ietf-httpbis-security-properties.html
r216 r220 297 297 } 298 298 @top-right { 299 content: " 2008";299 content: "February 2008"; 300 300 } 301 301 @top-center { … … 337 337 <meta name="DC.Creator" content="Hoffman, P."> 338 338 <meta name="DC.Creator" content="Melnikov, A."> 339 <meta name="DC.Identifier" content="urn:ietf:id:draft-ietf-httpbis-security-properties-01 .txt">340 <meta name="DC.Date.Issued" scheme="ISO8601" content="2008- WRONG SYNTAX FOR MONTH">339 <meta name="DC.Identifier" content="urn:ietf:id:draft-ietf-httpbis-security-properties-01"> 340 <meta name="DC.Date.Issued" scheme="ISO8601" content="2008-02"> 341 341 <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."> 342 342 </head> … … 353 353 <tr> 354 354 <td class="header left"> 355 <draft-ietf-httpbis-security-properties-01 .txt>355 <draft-ietf-httpbis-security-properties-01> 356 356 357 357 </td> … … 363 363 </tr> 364 364 <tr> 365 <td class="header left">Expires: WRONG SYNTAX FOR MONTH</td>366 <td class="header right"> 2008</td>365 <td class="header left">Expires: August 2008</td> 366 <td class="header right">February 2008</td> 367 367 </tr> 368 368 </table> 369 <p class="title">Security Requirements for HTTP<br><span class="filename">draft-ietf-httpbis-security-properties-01.txt</span><div class="error">WARNING: The @docName attribute should contain the base name, not the filename (thus no file extension).</div> 370 </p> 369 <p class="title">Security Requirements for HTTP<br><span class="filename">draft-ietf-httpbis-security-properties-01</span></p> 371 370 <h1><a id="rfc.status" href="#rfc.status">Status of this Memo</a></h1> 372 371 <p>By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she … … 385 384 <p>The list of Internet-Draft Shadow Directories can be accessed at <<a href="http://www.ietf.org/shadow.html">http://www.ietf.org/shadow.html</a>>. 386 385 </p> 387 <p>This Internet-Draft will expire in WRONG SYNTAX FOR MONTH.</p>386 <p>This Internet-Draft will expire in August 2008.</p> 388 387 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 389 388 <p>Copyright © The IETF Trust (2008). All Rights Reserved.</p> -
draft-ietf-httpbis-security-properties/latest/draft-ietf-httpbis-security-properties.redxml
r216 r220 6 6 <!DOCTYPE rfc 7 7 PUBLIC "" "rfc2629.dtd"> 8 <rfc category="info" ipr="full3978" docName="draft-ietf-httpbis-security-properties-01 .txt">8 <rfc category="info" ipr="full3978" docName="draft-ietf-httpbis-security-properties-01"> 9 9 10 10 … … 40 40 <address><email>alexey.melnikov@isode.com</email> </address> 41 41 </author> 42 <date year="2008" />42 <date year="2008" month="February"/> 43 43 <abstract> 44 44 <t>Recent IESG practice dictates that IETF protocols must specify … … 854 854 <organization/> 855 855 </author> 856 <date year="" month=""/> 856 857 </front> 857 858 </reference> -
draft-ietf-httpbis-security-properties/latest/draft-ietf-httpbis-security-properties.txt
r216 r220 10 10 11 11 Security Requirements for HTTP 12 draft-ietf-httpbis-security-properties-01.txt12 draft-ietf-httpbis-security-properties-01 13 13 14 14 Status of this Memo -
draft-ietf-httpbis-security-properties/latest/draft-ietf-httpbis-security-properties.xml
r216 r220 14 14 15 15 <rfc category="info" ipr="full3978" 16 docName="draft-ietf-httpbis-security-properties-01 .txt">16 docName="draft-ietf-httpbis-security-properties-01"> 17 17 18 18 <?xml-stylesheet type='text/xsl' href='rfc2629xslt/rfc2629.xslt' ?> … … 38 38 <address><email>alexey.melnikov@isode.com</email> </address> 39 39 </author> 40 <date year="2008" />40 <date year="2008" month="February"/> 41 41 <abstract> 42 42 <t>Recent IESG practice dictates that IETF protocols must specify … … 336 336 <organization /> 337 337 </author> 338 <date year='' month='' /> 338 339 </front> 339 340 </reference>
Note: See TracChangeset
for help on using the changeset viewer.