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

update to what was submitted as draft 05

Location:
draft-ietf-httpbis-security-properties/latest
Files:
1 deleted
2 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis-security-properties/latest/draft-ietf-httpbis-security-properties.html

    r787 r789  
    266266  }
    267267  @top-right {
    268        content: "March 2009";
     268       content: "March 2010";
    269269  }
    270270  @top-center {
     
    308308      <meta name="dct.creator" content="Leiba, B.">
    309309      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-security-properties-latest">
    310       <meta name="dct.issued" scheme="ISO8601" content="2009-03">
     310      <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.">
    312312      <meta name="description" 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.">
     
    328328            </tr>
    329329            <tr>
    330                <td class="left">Expires: September 2009</td>
     330               <td class="left">Expires: September 12, 2010</td>
    331331               <td class="right">Huawei Technologies</td>
    332332            </tr>
    333333            <tr>
    334334               <td class="left"></td>
    335                <td class="right">March 2009</td>
     335               <td class="right">March 11, 2010</td>
    336336            </tr>
    337337         </tbody>
    338338      </table>
    339339      <p class="title">Security Requirements for HTTP<br><span class="filename">draft-ietf-httpbis-security-properties-latest</span></p>
    340       <h1><a id="rfc.status" href="#rfc.status">Status of this Memo</a></h1>
    341       <p>This Internet-Draft is submitted to IETF in full conformance with the provisions of BCP 78 and BCP 79. This document may contain
    342          material from IETF Documents or IETF Contributions published or made publicly available before November 10, 2008. The person(s)
    343          controlling the copyright in some of this material may not have granted the IETF Trust the right to allow modifications of
    344          such material outside the IETF Standards Process. Without obtaining an adequate license from the person(s) controlling the
    345          copyright in such materials, this document may not be modified outside the IETF Standards Process, and derivative works of
    346          it may not be created outside the IETF Standards Process, except to format it for publication as an RFC or to translate it
    347          into languages other than English.
    348       </p>
    349       <p>Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note
    350          that other groups may also distribute working documents as Internet-Drafts.
    351       </p>
    352       <p>Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other
    353          documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as “work
    354          in progress”.
    355       </p>
    356       <p>The list of current Internet-Drafts can be accessed at <a href="http://www.ietf.org/ietf/1id-abstracts.txt">http://www.ietf.org/ietf/1id-abstracts.txt</a>.
    357       </p>
    358       <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>.
    359       </p>
    360       <p>This Internet-Draft will expire in September 2009.</p>
    361       <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    362       <p>Copyright © 2009 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
    363       <p>This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents in effect on the date
    364          of publication of this document (<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>). Please review these documents carefully, as they describe your rights and restrictions with respect to this document.
    365       </p>
    366340      <h1 id="rfc.abstract"><a href="#rfc.abstract">Abstract</a></h1>
    367341      <p>Recent IESG practice dictates that IETF protocols must specify mandatory-to-implement (MTI) security mechanisms, so that all
     
    369343         and analyzes the trade-offs of each.
    370344      </p>
     345      <h1><a id="rfc.status" href="#rfc.status">Status of this Memo</a></h1>
     346      <p>This Internet-Draft is submitted to IETF in full conformance with the provisions of BCP 78 and BCP 79.</p>
     347      <p>Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note
     348         that other groups may also distribute working documents as Internet-Drafts.
     349      </p>
     350      <p>Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other
     351         documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as “work
     352         in progress”.
     353      </p>
     354      <p>The list of current Internet-Drafts can be accessed at <a href="http://www.ietf.org/ietf/1id-abstracts.txt">http://www.ietf.org/ietf/1id-abstracts.txt</a>.
     355      </p>
     356      <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>.
     357      </p>
     358      <p>This Internet-Draft will expire in September 12, 2010.</p>
     359      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
     360      <p>Copyright © 2010 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
     361      <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
     362         and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License
     363         text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the BSD License.
     364      </p>
     365      <p>This document may contain material from IETF Documents or IETF Contributions published or made publicly available before November
     366         10, 2008. The person(s) controlling the copyright in some of this material may not have granted the IETF Trust the right to
     367         allow modifications of such material outside the IETF Standards Process. Without obtaining an adequate license from the person(s)
     368         controlling the copyright in such materials, this document may not be modified outside the IETF Standards Process, and derivative
     369         works of it may not be created outside the IETF Standards Process, except to format it for publication as an RFC or to translate
     370         it into languages other than English.
     371      </p>
    371372      <hr class="noprint">
    372373      <h1 id="rfc.section.1" class="np"><a href="#rfc.section.1">1.</a>&nbsp;Introduction
     
    744745         to satisfy IDnits checking.
    745746      </p>
     747      <h2 id="rfc.section.B.6"><a href="#rfc.section.B.6">B.6</a>&nbsp;Changes between -04 and -05
     748      </h2>
     749      <p id="rfc.section.B.6.p.1">Fixed incorrect &lt;date&gt; year from 2009 to 2010. mea culpa.</p>
    746750   </body>
    747751</html>
  • draft-ietf-httpbis-security-properties/latest/draft-ietf-httpbis-security-properties.xml

    r787 r789  
    4545            </address>
    4646        </author>
    47         <date year="2009" month="March"/>
     47        <date year="2010" month="March"/>
    4848        <abstract>
    4949            <t>
     
    801801            </section>
    802802
     803            <section title="Changes between -04 and -05">
     804
     805                <t>
     806                    Fixed incorrect &lt;date&gt; year from 2009 to 2010. mea culpa.
     807                </t>
     808
     809            </section>
     810
    803811        </section>
    804812
Note: See TracChangeset for help on using the changeset viewer.