* WGs marked with an * asterisk has had at least one new draft made available during the last 5 days

Changeset 1477


Ignore:
Timestamp:
2011-11-14 02:27:42 (3 years ago)
Author:
julian.reschke@gmx.de
Message:

Target maturity level is 'proposed', no need to discuss RFC1950-2 as downrefs (see #323)

Location:
draft-ietf-httpbis/latest
Files:
14 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p1-messaging.html

    r1476 r1477  
    359359  }  
    360360  @bottom-center { 
    361        content: "Expires May 14, 2012";  
     361       content: "Expires May 17, 2012";  
    362362  }  
    363363  @bottom-right { 
     
    409409      <meta name="dct.creator" content="Reschke, J. F."> 
    410410      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p1-messaging-latest"> 
    411       <meta name="dct.issued" scheme="ISO8601" content="2011-11-11"> 
     411      <meta name="dct.issued" scheme="ISO8601" content="2011-11-14"> 
    412412      <meta name="dct.replaces" content="urn:ietf:rfc:2145"> 
    413413      <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 
     
    441441            </tr> 
    442442            <tr> 
    443                <td class="left">Expires: May 14, 2012</td> 
     443               <td class="left">Expires: May 17, 2012</td> 
    444444               <td class="right">HP</td> 
    445445            </tr> 
     
    494494            <tr> 
    495495               <td class="left"></td> 
    496                <td class="right">November 11, 2011</td> 
     496               <td class="right">November 14, 2011</td> 
    497497            </tr> 
    498498         </tbody> 
     
    527527         in progress”. 
    528528      </p> 
    529       <p>This Internet-Draft will expire on May 14, 2012.</p> 
     529      <p>This Internet-Draft will expire on May 17, 2012.</p> 
    530530      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 
    531531      <p>Copyright © 2011 IETF Trust and the persons identified as the document authors. All rights reserved.</p> 
     
    27112711         <tr> 
    27122712            <td class="reference"><b id="RFC1950">[RFC1950]</b></td> 
    2713             <td class="top"><a href="mailto:ghost@aladdin.com" title="Aladdin Enterprises">Deutsch, L.</a> and J-L. Gailly, “<a href="http://tools.ietf.org/html/rfc1950">ZLIB Compressed Data Format Specification version 3.3</a>”, RFC&nbsp;1950, May&nbsp;1996.<br>RFC 1950 is an Informational RFC, thus it might be less stable than this specification. On the other hand, this downward reference 
    2714                was present since the publication of <cite title="Hypertext Transfer Protocol -- HTTP/1.1" id="rfc.xref.RFC2068.5">RFC 2068</cite> in 1997, therefore it is unlikely to cause problems in practice. See also <a href="#BCP97" id="rfc.xref.BCP97.1"><cite title="Handling Normative References to Standards-Track Documents">[BCP97]</cite></a>. 
     2713            <td class="top"><a href="mailto:ghost@aladdin.com" title="Aladdin Enterprises">Deutsch, L.</a> and J-L. Gailly, “<a href="http://tools.ietf.org/html/rfc1950">ZLIB Compressed Data Format Specification version 3.3</a>”, RFC&nbsp;1950, May&nbsp;1996. 
    27152714            </td> 
    27162715         </tr> 
    27172716         <tr> 
    27182717            <td class="reference"><b id="RFC1951">[RFC1951]</b></td> 
    2719             <td class="top"><a href="mailto:ghost@aladdin.com" title="Aladdin Enterprises">Deutsch, P.</a>, “<a href="http://tools.ietf.org/html/rfc1951">DEFLATE Compressed Data Format Specification version 1.3</a>”, RFC&nbsp;1951, May&nbsp;1996.<br>RFC 1951 is an Informational RFC, thus it might be less stable than this specification. On the other hand, this downward reference 
    2720                was present since the publication of <cite title="Hypertext Transfer Protocol -- HTTP/1.1" id="rfc.xref.RFC2068.6">RFC 2068</cite> in 1997, therefore it is unlikely to cause problems in practice. See also <a href="#BCP97" id="rfc.xref.BCP97.2"><cite title="Handling Normative References to Standards-Track Documents">[BCP97]</cite></a>. 
     2718            <td class="top"><a href="mailto:ghost@aladdin.com" title="Aladdin Enterprises">Deutsch, P.</a>, “<a href="http://tools.ietf.org/html/rfc1951">DEFLATE Compressed Data Format Specification version 1.3</a>”, RFC&nbsp;1951, May&nbsp;1996. 
    27212719            </td> 
    27222720         </tr> 
    27232721         <tr> 
    27242722            <td class="reference"><b id="RFC1952">[RFC1952]</b></td> 
    2725             <td class="top"><a href="mailto:ghost@aladdin.com" title="Aladdin Enterprises">Deutsch, P.</a>, <a href="mailto:gzip@prep.ai.mit.edu">Gailly, J-L.</a>, <a href="mailto:madler@alumni.caltech.edu">Adler, M.</a>, <a href="mailto:ghost@aladdin.com">Deutsch, L.</a>, and <a href="mailto:randeg@alumni.rpi.edu">G. Randers-Pehrson</a>, “<a href="http://tools.ietf.org/html/rfc1952">GZIP file format specification version 4.3</a>”, RFC&nbsp;1952, May&nbsp;1996.<br>RFC 1952 is an Informational RFC, thus it might be less stable than this specification. On the other hand, this downward reference 
    2726                was present since the publication of <cite title="Hypertext Transfer Protocol -- HTTP/1.1" id="rfc.xref.RFC2068.7">RFC 2068</cite> in 1997, therefore it is unlikely to cause problems in practice. See also <a href="#BCP97" id="rfc.xref.BCP97.3"><cite title="Handling Normative References to Standards-Track Documents">[BCP97]</cite></a>. 
     2723            <td class="top"><a href="mailto:ghost@aladdin.com" title="Aladdin Enterprises">Deutsch, P.</a>, <a href="mailto:gzip@prep.ai.mit.edu">Gailly, J-L.</a>, <a href="mailto:madler@alumni.caltech.edu">Adler, M.</a>, <a href="mailto:ghost@aladdin.com">Deutsch, L.</a>, and <a href="mailto:randeg@alumni.rpi.edu">G. Randers-Pehrson</a>, “<a href="http://tools.ietf.org/html/rfc1952">GZIP file format specification version 4.3</a>”, RFC&nbsp;1952, May&nbsp;1996. 
    27272724            </td> 
    27282725         </tr> 
     
    27502747      </h2> 
    27512748      <table>                                                   
    2752          <tr> 
    2753             <td class="reference"><b id="BCP97">[BCP97]</b></td> 
    2754             <td class="top"><a href="mailto:klensin+ietf@jck.com">Klensin, J.</a> and <a href="mailto:hartmans-ietf@mit.edu" title="MIT">S. Hartman</a>, “<a href="http://tools.ietf.org/html/rfc4897">Handling Normative References to Standards-Track Documents</a>”, BCP&nbsp;97, RFC&nbsp;4897, June&nbsp;2007. 
    2755             </td> 
    2756          </tr> 
    27572749         <tr> 
    27582750            <td class="reference"><b id="Kri2001">[Kri2001]</b></td> 
     
    29322924      <p id="rfc.section.A.1.2.p.1">For most implementations of HTTP/1.0, each connection is established by the client prior to the request and closed by the 
    29332925         server after sending the response. However, some implementations implement the Keep-Alive version of persistent connections 
    2934          described in <a href="http://tools.ietf.org/html/rfc2068#section-19.7.1">Section 19.7.1</a> of <a href="#RFC2068" id="rfc.xref.RFC2068.8"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a>. 
     2926         described in <a href="http://tools.ietf.org/html/rfc2068#section-19.7.1">Section 19.7.1</a> of <a href="#RFC2068" id="rfc.xref.RFC2068.5"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a>. 
    29352927      </p> 
    29362928      <p id="rfc.section.A.1.2.p.2">Some clients and servers might wish to be compatible with some previous implementations of persistent connections in HTTP/1.0 
     
    34813473         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/300">http://tools.ietf.org/wg/httpbis/trac/ticket/300</a>&gt;: "Define non-final responses" 
    34823474         </li> 
     3475         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/323">http://tools.ietf.org/wg/httpbis/trac/ticket/323</a>&gt;: "intended maturity level vs normative references" 
     3476         </li> 
    34833477      </ul> 
    34843478      <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1> 
     
    34963490            </li> 
    34973491            <li><a id="rfc.index.B" href="#rfc.index.B"><b>B</b></a><ul> 
    3498                   <li><em>BCP97</em>&nbsp;&nbsp;<a href="#rfc.xref.BCP97.1">12.1</a>, <a href="#rfc.xref.BCP97.2">12.1</a>, <a href="#rfc.xref.BCP97.3">12.1</a>, <a href="#BCP97"><b>12.2</b></a></li> 
    34993492                  <li>browser&nbsp;&nbsp;<a href="#rfc.iref.b.1"><b>2.1</b></a></li> 
    35003493               </ul> 
     
    37303723                  </li> 
    37313724                  <li><em>RFC2047</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2047.1">3.2.1</a>, <a href="#RFC2047"><b>12.2</b></a></li> 
    3732                   <li><em>RFC2068</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2068.1">§</a>, <a href="#rfc.xref.RFC2068.2">2.6</a>, <a href="#rfc.xref.RFC2068.3">6.1.3</a>, <a href="#rfc.xref.RFC2068.4">6.2.3</a>, <a href="#rfc.xref.RFC2068.5">12.1</a>, <a href="#rfc.xref.RFC2068.6">12.1</a>, <a href="#rfc.xref.RFC2068.7">12.1</a>, <a href="#RFC2068"><b>12.2</b></a>, <a href="#rfc.xref.RFC2068.8">A.1.2</a><ul> 
    3733                         <li><em>Section 19.7.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2068.3">6.1.3</a>, <a href="#rfc.xref.RFC2068.8">A.1.2</a></li> 
     3725                  <li><em>RFC2068</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2068.1">§</a>, <a href="#rfc.xref.RFC2068.2">2.6</a>, <a href="#rfc.xref.RFC2068.3">6.1.3</a>, <a href="#rfc.xref.RFC2068.4">6.2.3</a>, <a href="#RFC2068"><b>12.2</b></a>, <a href="#rfc.xref.RFC2068.5">A.1.2</a><ul> 
     3726                        <li><em>Section 19.7.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2068.3">6.1.3</a>, <a href="#rfc.xref.RFC2068.5">A.1.2</a></li> 
    37343727                     </ul> 
    37353728                  </li> 
  • draft-ietf-httpbis/latest/p1-messaging.xml

    r1476 r1477  
    5555<?rfc-ext allow-markup-in-artwork="yes" ?> 
    5656<?rfc-ext include-references-in-index="yes" ?> 
    57 <rfc obsoletes="2145,2616" updates="2817" category="std" x:maturity-level="draft" 
     57<rfc obsoletes="2145,2616" updates="2817" category="std" x:maturity-level="proposed" 
    5858     ipr="pre5378Trust200902" docName="draft-ietf-httpbis-p1-messaging-&ID-VERSION;" 
    5959     xmlns:x='http://purl.org/net/xml2rfc/ext'> 
     
    43254325  </front> 
    43264326  <seriesInfo name="RFC" value="1950"/> 
    4327   <annotation> 
     4327  <!--<annotation> 
    43284328    RFC 1950 is an Informational RFC, thus it might be less stable than 
    43294329    this specification. On the other hand, this downward reference was  
     
    43314331    therefore it is unlikely to cause problems in practice. See also 
    43324332    <xref target="BCP97"/>. 
    4333   </annotation> 
     4333  </annotation>--> 
    43344334</reference> 
    43354335 
     
    43444344  </front> 
    43454345  <seriesInfo name="RFC" value="1951"/> 
    4346   <annotation> 
     4346  <!--<annotation> 
    43474347    RFC 1951 is an Informational RFC, thus it might be less stable than 
    43484348    this specification. On the other hand, this downward reference was  
     
    43504350    therefore it is unlikely to cause problems in practice. See also 
    43514351    <xref target="BCP97"/>. 
    4352   </annotation> 
     4352  </annotation>--> 
    43534353</reference> 
    43544354 
     
    43754375  </front> 
    43764376  <seriesInfo name="RFC" value="1952"/> 
    4377   <annotation> 
     4377  <!--<annotation> 
    43784378    RFC 1952 is an Informational RFC, thus it might be less stable than 
    43794379    this specification. On the other hand, this downward reference was  
     
    43814381    therefore it is unlikely to cause problems in practice. See also 
    43824382    <xref target="BCP97"/>. 
    4383   </annotation> 
     4383  </annotation>--> 
    43844384</reference> 
    43854385 
     
    47534753</reference> 
    47544754 
    4755 <reference anchor='BCP97'> 
     4755<!--<reference anchor='BCP97'> 
    47564756  <front> 
    47574757    <title>Handling Normative References to Standards-Track Documents</title> 
     
    47714771  <seriesInfo name='BCP' value='97' /> 
    47724772  <seriesInfo name='RFC' value='4897' /> 
    4773 </reference> 
     4773</reference>--> 
    47744774 
    47754775<reference anchor="Kri2001" target="http://arxiv.org/abs/cs.SE/0105018"> 
     
    58685868      "Define non-final responses" 
    58695869    </t> 
     5870    <t> 
     5871      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/323"/>: 
     5872      "intended maturity level vs normative references" 
     5873    </t> 
    58705874  </list> 
    58715875</t> 
  • draft-ietf-httpbis/latest/p2-semantics.html

    r1475 r1477  
    359359  }  
    360360  @bottom-center { 
    361        content: "Expires May 14, 2012";  
     361       content: "Expires May 17, 2012";  
    362362  }  
    363363  @bottom-right { 
     
    411411      <meta name="dct.creator" content="Reschke, J. F."> 
    412412      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p2-semantics-latest"> 
    413       <meta name="dct.issued" scheme="ISO8601" content="2011-11-11"> 
     413      <meta name="dct.issued" scheme="ISO8601" content="2011-11-14"> 
    414414      <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 
    415415      <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 2 of the seven-part specification that defines the protocol referred to as &#34;HTTP/1.1&#34; and, taken together, obsoletes RFC 2616. Part 2 defines the semantics of HTTP messages as expressed by request methods, request header fields, response status codes, and response header fields."> 
     
    442442            </tr> 
    443443            <tr> 
    444                <td class="left">Expires: May 14, 2012</td> 
     444               <td class="left">Expires: May 17, 2012</td> 
    445445               <td class="right">HP</td> 
    446446            </tr> 
     
    495495            <tr> 
    496496               <td class="left"></td> 
    497                <td class="right">November 11, 2011</td> 
     497               <td class="right">November 14, 2011</td> 
    498498            </tr> 
    499499         </tbody> 
     
    525525         in progress”. 
    526526      </p> 
    527       <p>This Internet-Draft will expire on May 14, 2012.</p> 
     527      <p>This Internet-Draft will expire on May 17, 2012.</p> 
    528528      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 
    529529      <p>Copyright © 2011 IETF Trust and the persons identified as the document authors. All rights reserved.</p> 
  • draft-ietf-httpbis/latest/p2-semantics.xml

    r1475 r1477  
    100100<?rfc-ext allow-markup-in-artwork="yes" ?> 
    101101<?rfc-ext include-references-in-index="yes" ?> 
    102 <rfc obsoletes="2616" updates="2817" category="std" x:maturity-level="draft" 
     102<rfc obsoletes="2616" updates="2817" category="std" x:maturity-level="proposed" 
    103103     ipr="pre5378Trust200902" docName="draft-ietf-httpbis-p2-semantics-&ID-VERSION;" 
    104104     xmlns:x='http://purl.org/net/xml2rfc/ext' 
  • draft-ietf-httpbis/latest/p3-payload.html

    r1472 r1477  
    359359  }  
    360360  @bottom-center { 
    361        content: "Expires May 8, 2012";  
     361       content: "Expires May 17, 2012";  
    362362  }  
    363363  @bottom-right { 
     
    410410      <meta name="dct.creator" content="Reschke, J. F."> 
    411411      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p3-payload-latest"> 
    412       <meta name="dct.issued" scheme="ISO8601" content="2011-11-05"> 
     412      <meta name="dct.issued" scheme="ISO8601" content="2011-11-14"> 
    413413      <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 
    414414      <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 3 of the seven-part specification that defines the protocol referred to as &#34;HTTP/1.1&#34; and, taken together, obsoletes RFC 2616. Part 3 defines HTTP message content, metadata, and content negotiation."> 
     
    436436            </tr> 
    437437            <tr> 
    438                <td class="left">Expires: May 8, 2012</td> 
     438               <td class="left">Expires: May 17, 2012</td> 
    439439               <td class="right">J. Mogul</td> 
    440440            </tr> 
     
    493493            <tr> 
    494494               <td class="left"></td> 
    495                <td class="right">November 5, 2011</td> 
     495               <td class="right">November 14, 2011</td> 
    496496            </tr> 
    497497         </tbody> 
     
    521521         in progress”. 
    522522      </p> 
    523       <p>This Internet-Draft will expire on May 8, 2012.</p> 
     523      <p>This Internet-Draft will expire on May 17, 2012.</p> 
    524524      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 
    525525      <p>Copyright © 2011 IETF Trust and the persons identified as the document authors. All rights reserved.</p> 
     
    15281528         <tr> 
    15291529            <td class="reference"><b id="RFC1950">[RFC1950]</b></td> 
    1530             <td class="top"><a href="mailto:ghost@aladdin.com" title="Aladdin Enterprises">Deutsch, L.</a> and J-L. Gailly, “<a href="http://tools.ietf.org/html/rfc1950">ZLIB Compressed Data Format Specification version 3.3</a>”, RFC&nbsp;1950, May&nbsp;1996.<br>RFC 1950 is an Informational RFC, thus it might be less stable than this specification. On the other hand, this downward reference 
    1531                was present since the publication of <cite title="Hypertext Transfer Protocol -- HTTP/1.1" id="rfc.xref.RFC2068.1">RFC 2068</cite> in 1997, therefore it is unlikely to cause problems in practice. See also <a href="#BCP97" id="rfc.xref.BCP97.1"><cite title="Handling Normative References to Standards-Track Documents">[BCP97]</cite></a>. 
     1530            <td class="top"><a href="mailto:ghost@aladdin.com" title="Aladdin Enterprises">Deutsch, L.</a> and J-L. Gailly, “<a href="http://tools.ietf.org/html/rfc1950">ZLIB Compressed Data Format Specification version 3.3</a>”, RFC&nbsp;1950, May&nbsp;1996. 
    15321531            </td> 
    15331532         </tr> 
    15341533         <tr> 
    15351534            <td class="reference"><b id="RFC1951">[RFC1951]</b></td> 
    1536             <td class="top"><a href="mailto:ghost@aladdin.com" title="Aladdin Enterprises">Deutsch, P.</a>, “<a href="http://tools.ietf.org/html/rfc1951">DEFLATE Compressed Data Format Specification version 1.3</a>”, RFC&nbsp;1951, May&nbsp;1996.<br>RFC 1951 is an Informational RFC, thus it might be less stable than this specification. On the other hand, this downward reference 
    1537                was present since the publication of <cite title="Hypertext Transfer Protocol -- HTTP/1.1" id="rfc.xref.RFC2068.2">RFC 2068</cite> in 1997, therefore it is unlikely to cause problems in practice. See also <a href="#BCP97" id="rfc.xref.BCP97.2"><cite title="Handling Normative References to Standards-Track Documents">[BCP97]</cite></a>. 
     1535            <td class="top"><a href="mailto:ghost@aladdin.com" title="Aladdin Enterprises">Deutsch, P.</a>, “<a href="http://tools.ietf.org/html/rfc1951">DEFLATE Compressed Data Format Specification version 1.3</a>”, RFC&nbsp;1951, May&nbsp;1996. 
    15381536            </td> 
    15391537         </tr> 
    15401538         <tr> 
    15411539            <td class="reference"><b id="RFC1952">[RFC1952]</b></td> 
    1542             <td class="top"><a href="mailto:ghost@aladdin.com" title="Aladdin Enterprises">Deutsch, P.</a>, <a href="mailto:gzip@prep.ai.mit.edu">Gailly, J-L.</a>, <a href="mailto:madler@alumni.caltech.edu">Adler, M.</a>, <a href="mailto:ghost@aladdin.com">Deutsch, L.</a>, and <a href="mailto:randeg@alumni.rpi.edu">G. Randers-Pehrson</a>, “<a href="http://tools.ietf.org/html/rfc1952">GZIP file format specification version 4.3</a>”, RFC&nbsp;1952, May&nbsp;1996.<br>RFC 1952 is an Informational RFC, thus it might be less stable than this specification. On the other hand, this downward reference 
    1543                was present since the publication of <cite title="Hypertext Transfer Protocol -- HTTP/1.1" id="rfc.xref.RFC2068.3">RFC 2068</cite> in 1997, therefore it is unlikely to cause problems in practice. See also <a href="#BCP97" id="rfc.xref.BCP97.3"><cite title="Handling Normative References to Standards-Track Documents">[BCP97]</cite></a>. 
     1540            <td class="top"><a href="mailto:ghost@aladdin.com" title="Aladdin Enterprises">Deutsch, P.</a>, <a href="mailto:gzip@prep.ai.mit.edu">Gailly, J-L.</a>, <a href="mailto:madler@alumni.caltech.edu">Adler, M.</a>, <a href="mailto:ghost@aladdin.com">Deutsch, L.</a>, and <a href="mailto:randeg@alumni.rpi.edu">G. Randers-Pehrson</a>, “<a href="http://tools.ietf.org/html/rfc1952">GZIP file format specification version 4.3</a>”, RFC&nbsp;1952, May&nbsp;1996. 
    15441541            </td> 
    15451542         </tr> 
     
    15781575      </h2> 
    15791576      <table>                                   
    1580          <tr> 
    1581             <td class="reference"><b id="BCP97">[BCP97]</b></td> 
    1582             <td class="top"><a href="mailto:klensin+ietf@jck.com">Klensin, J.</a> and <a href="mailto:hartmans-ietf@mit.edu" title="MIT">S. Hartman</a>, “<a href="http://tools.ietf.org/html/rfc4897">Handling Normative References to Standards-Track Documents</a>”, BCP&nbsp;97, RFC&nbsp;4897, June&nbsp;2007. 
    1583             </td> 
    1584          </tr> 
    15851577         <tr> 
    15861578            <td class="reference"><b id="RFC1945">[RFC1945]</b></td> 
     
    17401732      </p> 
    17411733      <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a>&nbsp;<a id="additional.features" href="#additional.features">Additional Features</a></h1> 
    1742       <p id="rfc.section.B.p.1"> <a href="#RFC1945" id="rfc.xref.RFC1945.1"><cite title="Hypertext Transfer Protocol -- HTTP/1.0">[RFC1945]</cite></a> and <a href="#RFC2068" id="rfc.xref.RFC2068.4"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a> document protocol elements used by some existing HTTP implementations, but not consistently and correctly across most HTTP/1.1 
     1734      <p id="rfc.section.B.p.1"> <a href="#RFC1945" id="rfc.xref.RFC1945.1"><cite title="Hypertext Transfer Protocol -- HTTP/1.0">[RFC1945]</cite></a> and <a href="#RFC2068" id="rfc.xref.RFC2068.1"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a> document protocol elements used by some existing HTTP implementations, but not consistently and correctly across most HTTP/1.1 
    17431735         applications. Implementors are advised to be aware of these features, but cannot rely upon their presence in, or interoperability 
    17441736         with, other HTTP/1.1 applications. Some of these describe proposed experimental features, and some describe features that 
     
    18951887      <p id="rfc.section.E.5.p.2">Other changes: </p> 
    18961888      <ul> 
    1897          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/68">http://tools.ietf.org/wg/httpbis/trac/ticket/68</a>&gt;: "Encoding References Normative" — rephrase the annotation and reference <a href="#BCP97" id="rfc.xref.BCP97.4"><cite title="Handling Normative References to Standards-Track Documents">[BCP97]</cite></a>. 
     1889         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/68">http://tools.ietf.org/wg/httpbis/trac/ticket/68</a>&gt;: "Encoding References Normative" — rephrase the annotation and reference BCP97. 
    18981890         </li> 
    18991891      </ul> 
     
    20502042      </ul> 
    20512043      <h2 id="rfc.section.E.19"><a href="#rfc.section.E.19">E.19</a>&nbsp;<a id="changes.since.17" href="#changes.since.17">Since draft-ietf-httpbis-p3-payload-17</a></h2> 
    2052       <p id="rfc.section.E.19.p.1">No changes yet.</p> 
     2044      <p id="rfc.section.E.19.p.1">Closed issues: </p> 
     2045      <ul> 
     2046         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/323">http://tools.ietf.org/wg/httpbis/trac/ticket/323</a>&gt;: "intended maturity level vs normative references" 
     2047         </li> 
     2048      </ul> 
    20532049      <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1> 
    2054       <p class="noprint"><a href="#rfc.index.A">A</a> <a href="#rfc.index.B">B</a> <a href="#rfc.index.C">C</a> <a href="#rfc.index.D">D</a> <a href="#rfc.index.G">G</a> <a href="#rfc.index.H">H</a> <a href="#rfc.index.M">M</a> <a href="#rfc.index.P">P</a> <a href="#rfc.index.R">R</a>  
     2050      <p class="noprint"><a href="#rfc.index.A">A</a> <a href="#rfc.index.C">C</a> <a href="#rfc.index.D">D</a> <a href="#rfc.index.G">G</a> <a href="#rfc.index.H">H</a> <a href="#rfc.index.M">M</a> <a href="#rfc.index.P">P</a> <a href="#rfc.index.R">R</a>  
    20552051      </p> 
    20562052      <div class="print2col"> 
     
    20612057                  <li>Accept-Encoding header field&nbsp;&nbsp;<a href="#rfc.xref.header.accept-encoding.1">2.2</a>, <a href="#rfc.xref.header.accept-encoding.2">5.1</a>, <a href="#rfc.iref.a.3"><b>6.3</b></a>, <a href="#rfc.xref.header.accept-encoding.3">7.1</a>, <a href="#rfc.xref.header.accept-encoding.4">7.2</a></li> 
    20622058                  <li>Accept-Language header field&nbsp;&nbsp;<a href="#rfc.xref.header.accept-language.1">5.1</a>, <a href="#rfc.iref.a.4"><b>6.4</b></a>, <a href="#rfc.xref.header.accept-language.2">7.1</a></li> 
    2063                </ul> 
    2064             </li> 
    2065             <li><a id="rfc.index.B" href="#rfc.index.B"><b>B</b></a><ul> 
    2066                   <li><em>BCP97</em>&nbsp;&nbsp;<a href="#rfc.xref.BCP97.1">10.1</a>, <a href="#rfc.xref.BCP97.2">10.1</a>, <a href="#rfc.xref.BCP97.3">10.1</a>, <a href="#BCP97"><b>10.2</b></a>, <a href="#rfc.xref.BCP97.4">E.5</a></li> 
    20672059               </ul> 
    20682060            </li> 
     
    21952187                     </ul> 
    21962188                  </li> 
    2197                   <li><em>RFC2068</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2068.1">10.1</a>, <a href="#rfc.xref.RFC2068.2">10.1</a>, <a href="#rfc.xref.RFC2068.3">10.1</a>, <a href="#RFC2068"><b>10.2</b></a>, <a href="#rfc.xref.RFC2068.4">B</a></li> 
     2189                  <li><em>RFC2068</em>&nbsp;&nbsp;<a href="#RFC2068"><b>10.2</b></a>, <a href="#rfc.xref.RFC2068.1">B</a></li> 
    21982190                  <li><em>RFC2076</em>&nbsp;&nbsp;<a href="#RFC2076"><b>10.2</b></a>, <a href="#rfc.xref.RFC2076.1">B</a></li> 
    21992191                  <li><em>RFC2119</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2119.1">1.2</a>, <a href="#RFC2119"><b>10.1</b></a></li> 
  • draft-ietf-httpbis/latest/p3-payload.xml

    r1472 r1477  
    5555<?rfc-ext allow-markup-in-artwork="yes" ?> 
    5656<?rfc-ext include-references-in-index="yes" ?> 
    57 <rfc obsoletes="2616" category="std" x:maturity-level="draft" 
     57<rfc obsoletes="2616" category="std" x:maturity-level="proposed" 
    5858     ipr="pre5378Trust200902" docName="draft-ietf-httpbis-p3-payload-&ID-VERSION;" 
    5959     xmlns:x='http://purl.org/net/xml2rfc/ext'> 
     
    18871887  </front> 
    18881888  <seriesInfo name="RFC" value="1950"/> 
    1889   <annotation> 
     1889  <!--<annotation> 
    18901890    RFC 1950 is an Informational RFC, thus it might be less stable than 
    18911891    this specification. On the other hand, this downward reference was  
     
    18931893    therefore it is unlikely to cause problems in practice. See also 
    18941894    <xref target="BCP97"/>. 
    1895   </annotation> 
     1895  </annotation>--> 
    18961896</reference> 
    18971897 
     
    19061906  </front> 
    19071907  <seriesInfo name="RFC" value="1951"/> 
    1908   <annotation> 
     1908  <!--<annotation> 
    19091909    RFC 1951 is an Informational RFC, thus it might be less stable than 
    19101910    this specification. On the other hand, this downward reference was  
     
    19121912    therefore it is unlikely to cause problems in practice. See also 
    19131913    <xref target="BCP97"/>. 
    1914   </annotation> 
     1914  </annotation>--> 
    19151915</reference> 
    19161916 
     
    19371937  </front> 
    19381938  <seriesInfo name="RFC" value="1952"/> 
    1939   <annotation> 
     1939  <!--<annotation> 
    19401940    RFC 1952 is an Informational RFC, thus it might be less stable than 
    19411941    this specification. On the other hand, this downward reference was  
     
    19431943    therefore it is unlikely to cause problems in practice. See also 
    19441944    <xref target="BCP97"/>. 
    1945   </annotation> 
     1945  </annotation>--> 
    19461946</reference> 
    19471947 
     
    23222322</reference> 
    23232323 
    2324 <reference anchor='BCP97'> 
     2324<!--<reference anchor='BCP97'> 
    23252325  <front> 
    23262326    <title>Handling Normative References to Standards-Track Documents</title> 
     
    23402340  <seriesInfo name='BCP' value='97' /> 
    23412341  <seriesInfo name='RFC' value='4897' /> 
    2342 </reference> 
     2342</reference>--> 
    23432343 
    23442344<reference anchor="RFC6266"> 
     
    27562756      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/68"/>: 
    27572757      "Encoding References Normative" &mdash; rephrase the annotation and reference 
    2758       <xref target="BCP97"/>. 
     2758      BCP97. 
    27592759    </t> 
    27602760  </list> 
     
    30673067<section title="Since draft-ietf-httpbis-p3-payload-17" anchor="changes.since.17"> 
    30683068<t> 
    3069   No changes yet. 
     3069  Closed issues: 
     3070  <list style="symbols">  
     3071    <t> 
     3072      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/323"/>: 
     3073      "intended maturity level vs normative references" 
     3074    </t> 
     3075  </list> 
    30703076</t> 
    30713077</section> 
  • draft-ietf-httpbis/latest/p4-conditional.html

    r1472 r1477  
    359359  }  
    360360  @bottom-center { 
    361        content: "Expires May 8, 2012";  
     361       content: "Expires May 17, 2012";  
    362362  }  
    363363  @bottom-right { 
     
    406406      <meta name="dct.creator" content="Reschke, J. F."> 
    407407      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p4-conditional-latest"> 
    408       <meta name="dct.issued" scheme="ISO8601" content="2011-11-05"> 
     408      <meta name="dct.issued" scheme="ISO8601" content="2011-11-14"> 
    409409      <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 
    410410      <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 4 of the seven-part specification that defines the protocol referred to as &#34;HTTP/1.1&#34; and, taken together, obsoletes RFC 2616. Part 4 defines request header fields for indicating conditional requests and the rules for constructing responses to those requests."> 
     
    432432            </tr> 
    433433            <tr> 
    434                <td class="left">Expires: May 8, 2012</td> 
     434               <td class="left">Expires: May 17, 2012</td> 
    435435               <td class="right">J. Mogul</td> 
    436436            </tr> 
     
    489489            <tr> 
    490490               <td class="left"></td> 
    491                <td class="right">November 5, 2011</td> 
     491               <td class="right">November 14, 2011</td> 
    492492            </tr> 
    493493         </tbody> 
     
    519519         in progress”. 
    520520      </p> 
    521       <p>This Internet-Draft will expire on May 8, 2012.</p> 
     521      <p>This Internet-Draft will expire on May 17, 2012.</p> 
    522522      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 
    523523      <p>Copyright © 2011 IETF Trust and the persons identified as the document authors. All rights reserved.</p> 
  • draft-ietf-httpbis/latest/p4-conditional.xml

    r1472 r1477  
    4444<?rfc-ext allow-markup-in-artwork="yes" ?> 
    4545<?rfc-ext include-references-in-index="yes" ?> 
    46 <rfc obsoletes="2616" category="std" x:maturity-level="draft" 
     46<rfc obsoletes="2616" category="std" x:maturity-level="proposed" 
    4747     ipr="pre5378Trust200902" docName="draft-ietf-httpbis-p4-conditional-&ID-VERSION;" 
    4848     xmlns:x='http://purl.org/net/xml2rfc/ext'> 
  • draft-ietf-httpbis/latest/p5-range.html

    r1472 r1477  
    359359  }  
    360360  @bottom-center { 
    361        content: "Expires May 8, 2012";  
     361       content: "Expires May 17, 2012";  
    362362  }  
    363363  @bottom-right { 
     
    408408      <meta name="dct.creator" content="Reschke, J. F."> 
    409409      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p5-range-latest"> 
    410       <meta name="dct.issued" scheme="ISO8601" content="2011-11-05"> 
     410      <meta name="dct.issued" scheme="ISO8601" content="2011-11-14"> 
    411411      <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 
    412412      <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 5 of the seven-part specification that defines the protocol referred to as &#34;HTTP/1.1&#34; and, taken together, obsoletes RFC 2616. Part 5 defines range-specific requests and the rules for constructing and combining responses to those requests."> 
     
    434434            </tr> 
    435435            <tr> 
    436                <td class="left">Expires: May 8, 2012</td> 
     436               <td class="left">Expires: May 17, 2012</td> 
    437437               <td class="right">J. Mogul</td> 
    438438            </tr> 
     
    491491            <tr> 
    492492               <td class="left"></td> 
    493                <td class="right">November 5, 2011</td> 
     493               <td class="right">November 14, 2011</td> 
    494494            </tr> 
    495495         </tbody> 
     
    519519         in progress”. 
    520520      </p> 
    521       <p>This Internet-Draft will expire on May 8, 2012.</p> 
     521      <p>This Internet-Draft will expire on May 17, 2012.</p> 
    522522      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 
    523523      <p>Copyright © 2011 IETF Trust and the persons identified as the document authors. All rights reserved.</p> 
  • draft-ietf-httpbis/latest/p5-range.xml

    r1472 r1477  
    3939<?rfc-ext allow-markup-in-artwork="yes" ?> 
    4040<?rfc-ext include-references-in-index="yes" ?> 
    41 <rfc obsoletes="2616" category="std" x:maturity-level="draft" 
    42      ipr="pre5378Trust200902" docName="draft-ietf-httpbis-p5-range-&ID-VERSION;"     xmlns:x='http://purl.org/net/xml2rfc/ext'> 
     41<rfc obsoletes="2616" category="std" x:maturity-level="proposed" 
     42     ipr="pre5378Trust200902" docName="draft-ietf-httpbis-p5-range-&ID-VERSION;" 
     43     xmlns:x='http://purl.org/net/xml2rfc/ext'> 
    4344<x:link rel="prev" basename="p4-conditional"/> 
    4445<x:link rel="next" basename="p6-cache"/> 
  • draft-ietf-httpbis/latest/p6-cache.html

    r1472 r1477  
    362362  }  
    363363  @bottom-center { 
    364        content: "Expires May 8, 2012";  
     364       content: "Expires May 17, 2012";  
    365365  }  
    366366  @bottom-right { 
     
    410410      <meta name="dct.creator" content="Reschke, J. F."> 
    411411      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p6-cache-latest"> 
    412       <meta name="dct.issued" scheme="ISO8601" content="2011-11-05"> 
     412      <meta name="dct.issued" scheme="ISO8601" content="2011-11-14"> 
    413413      <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 
    414414      <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 6 of the seven-part specification that defines the protocol referred to as &#34;HTTP/1.1&#34; and, taken together, obsoletes RFC 2616. Part 6 defines requirements on HTTP caches and the associated header fields that control cache behavior or indicate cacheable response messages."> 
     
    436436            </tr> 
    437437            <tr> 
    438                <td class="left">Expires: May 8, 2012</td> 
     438               <td class="left">Expires: May 17, 2012</td> 
    439439               <td class="right">J. Mogul</td> 
    440440            </tr> 
     
    501501            <tr> 
    502502               <td class="left"></td> 
    503                <td class="right">November 5, 2011</td> 
     503               <td class="right">November 14, 2011</td> 
    504504            </tr> 
    505505         </tbody> 
     
    531531         in progress”. 
    532532      </p> 
    533       <p>This Internet-Draft will expire on May 8, 2012.</p> 
     533      <p>This Internet-Draft will expire on May 17, 2012.</p> 
    534534      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 
    535535      <p>Copyright © 2011 IETF Trust and the persons identified as the document authors. All rights reserved.</p> 
  • draft-ietf-httpbis/latest/p6-cache.xml

    r1472 r1477  
    5454<?rfc-ext include-references-in-index="yes" ?> 
    5555<rfc category="std" docName="draft-ietf-httpbis-p6-cache-&ID-VERSION;" ipr="pre5378Trust200902" 
    56   obsoletes="2616" x:maturity-level="draft" xmlns:x="http://purl.org/net/xml2rfc/ext"> 
     56  obsoletes="2616" x:maturity-level="proposed" xmlns:x="http://purl.org/net/xml2rfc/ext"> 
    5757<x:link rel="prev" basename="p5-range"/> 
    5858<x:link rel="next" basename="p7-auth"/> 
  • draft-ietf-httpbis/latest/p7-auth.html

    r1473 r1477  
    359359  }  
    360360  @bottom-center { 
    361        content: "Expires May 13, 2012";  
     361       content: "Expires May 17, 2012";  
    362362  }  
    363363  @bottom-right { 
     
    405405      <meta name="dct.creator" content="Reschke, J. F."> 
    406406      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p7-auth-latest"> 
    407       <meta name="dct.issued" scheme="ISO8601" content="2011-11-10"> 
     407      <meta name="dct.issued" scheme="ISO8601" content="2011-11-14"> 
    408408      <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 
    409409      <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 7 of the seven-part specification that defines the protocol referred to as &#34;HTTP/1.1&#34; and, taken together, obsoletes RFC 2616. Part 7 defines the HTTP Authentication framework."> 
     
    436436            </tr> 
    437437            <tr> 
    438                <td class="left">Expires: May 13, 2012</td> 
     438               <td class="left">Expires: May 17, 2012</td> 
    439439               <td class="right">HP</td> 
    440440            </tr> 
     
    489489            <tr> 
    490490               <td class="left"></td> 
    491                <td class="right">November 10, 2011</td> 
     491               <td class="right">November 14, 2011</td> 
    492492            </tr> 
    493493         </tbody> 
     
    517517         in progress”. 
    518518      </p> 
    519       <p>This Internet-Draft will expire on May 13, 2012.</p> 
     519      <p>This Internet-Draft will expire on May 17, 2012.</p> 
    520520      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 
    521521      <p>Copyright © 2011 IETF Trust and the persons identified as the document authors. All rights reserved.</p> 
  • draft-ietf-httpbis/latest/p7-auth.xml

    r1473 r1477  
    3939<?rfc-ext allow-markup-in-artwork="yes" ?> 
    4040<?rfc-ext include-references-in-index="yes" ?> 
    41 <rfc obsoletes="2616" updates="2617" category="std" x:maturity-level="draft" 
     41<rfc obsoletes="2616" updates="2617" category="std" x:maturity-level="proposed" 
    4242     ipr="pre5378Trust200902" docName="draft-ietf-httpbis-p7-auth-&ID-VERSION;" 
    4343     xmlns:x='http://purl.org/net/xml2rfc/ext'> 
Note: See TracChangeset for help on using the changeset viewer.