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)

Author:

julian.reschke@…

Message:

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

Location:

draft-ietf-httpbis-security-properties/05

Files:

• . (copied) (copied from draft-ietf-httpbis-security-properties/latest)
• draft-ietf-httpbis-security-properties-05.html (copied) (copied from draft-ietf-httpbis-security-properties/latest/draft-ietf-httpbis-security-properties.html) (2 diffs)

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

@@ -307 +307 @@
       <meta name="dct.creator" content="Hodges, J.">
       <meta name="dct.creator" content="Leiba, B.">
-      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-security-properties-latest">
+      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-security-properties-05">
       <meta name="dct.issued" scheme="ISO8601" content="2010-03-11">
       <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>
       </table>
-      <p class="title">Security Requirements for HTTP<br><span class="filename">draft-ietf-httpbis-security-properties-latest</span></p>
+      <p class="title">Security Requirements for HTTP<br><span class="filename">draft-ietf-httpbis-security-properties-05</span></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 (MTI) security mechanisms, so that all