Ignore:
Timestamp:
Mar 11, 2010, 3:08:43 AM (10 years ago)
Author:
julian.reschke@…
Message:

snapshot draft-ietf-httpbis-security-properties-05

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  
    307307      <meta name="dct.creator" content="Hodges, J.">
    308308      <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">
    310310      <meta name="dct.issued" scheme="ISO8601" content="2010-03-11">
    311311      <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.">
     
    337337         </tbody>
    338338      </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>
    340340      <h1 id="rfc.abstract"><a href="#rfc.abstract">Abstract</a></h1>
    341341      <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.