Changeset 790 for draft-ietf-httpbis-security-properties/05/draft-ietf-httpbis-security-properties-05.html
- Timestamp:
- 11/03/10 11:08:43 (13 years ago)
- Location:
- draft-ietf-httpbis-security-properties/05
- Files:
-
- 2 copied
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis-security-properties/05/draft-ietf-httpbis-security-properties-05.html
r789 r790 307 307 <meta name="dct.creator" content="Hodges, J."> 308 308 <meta name="dct.creator" content="Leiba, B."> 309 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-security-properties- latest">309 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-security-properties-05"> 310 310 <meta name="dct.issued" scheme="ISO8601" content="2010-03-11"> 311 311 <meta name="dct.abstract" content="Recent IESG practice dictates that IETF protocols must specify mandatory-to-implement (MTI) 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."> … … 337 337 </tbody> 338 338 </table> 339 <p class="title">Security Requirements for HTTP<br><span class="filename">draft-ietf-httpbis-security-properties- latest</span></p>339 <p class="title">Security Requirements for HTTP<br><span class="filename">draft-ietf-httpbis-security-properties-05</span></p> 340 340 <h1 id="rfc.abstract"><a href="#rfc.abstract">Abstract</a></h1> 341 341 <p>Recent IESG practice dictates that IETF protocols must specify mandatory-to-implement (MTI) security mechanisms, so that all
Note: See TracChangeset
for help on using the changeset viewer.