Changeset 1567


Ignore:
Timestamp:
Mar 8, 2012, 2:01:34 AM (8 years ago)
Author:
julian.reschke@…
Message:

make IANA policy definitions consistent (see #346)

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

Legend:

Unmodified
Added
Removed

  • draft-ietf-httpbis/latest/p1-messaging.html

    r1566 r1567  
    460460  }
    461461  @bottom-center {
    462        content: "Expires September 8, 2012";
     462       content: "Expires September 9, 2012";
    463463  }
    464464  @bottom-right {
    … …  
    510510      <meta name="dct.creator" content="Reschke, J. F.">
    511511      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p1-messaging-latest">
    512       <meta name="dct.issued" scheme="ISO8601" content="2012-03-07">
     512      <meta name="dct.issued" scheme="ISO8601" content="2012-03-08">
    513513      <meta name="dct.replaces" content="urn:ietf:rfc:2145">
    514514      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    … …  
    542542            </tr>
    543543            <tr>
    544                <td class="left">Expires: September 8, 2012</td>
     544               <td class="left">Expires: September 9, 2012</td>
    545545               <td class="right">HP</td>
    546546            </tr>
    … …  
    595595            <tr>
    596596               <td class="left"></td>
    597                <td class="right">March 7, 2012</td>
     597               <td class="right">March 8, 2012</td>
    598598            </tr>
    599599         </tbody>
    … …  
    628628         in progress”.
    629629      </p>
    630       <p>This Internet-Draft will expire on September 8, 2012.</p>
     630      <p>This Internet-Draft will expire on September 9, 2012.</p>
    631631      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    632632      <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
    … …  
    801801               </li>
    802802               <li>A.2&nbsp;&nbsp;&nbsp;<a href="#changes.from.rfc.2616">Changes from RFC 2616</a></li>
     803               <li>A.3&nbsp;&nbsp;&nbsp;<a href="#changes.from.rfc.2817">Changes from RFC 2817</a></li>
    803804            </ul>
    804805         </li>
    … …  
    18801881      <p id="rfc.section.5.3.p.3">Names of transfer codings <em class="bcp14">MUST NOT</em> overlap with names of content codings (<a href="p3-payload.html#content.codings" title="Content Codings">Section 2.2</a> of <a href="#Part3" id="rfc.xref.Part3.3"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>), unless the encoding transformation is identical (as it is the case for the compression codings defined in <a href="#compression.codings" title="Compression Codings">Section&nbsp;5.2</a>).
    18811882      </p>
    1882       <p id="rfc.section.5.3.p.4">Values to be added to this name space require a specification (see "Specification Required" in <a href="http://tools.ietf.org/html/rfc5226#section-4.1">Section 4.1</a> of <a href="#RFC5226" id="rfc.xref.RFC5226.1"><cite title="Guidelines for Writing an IANA Considerations Section in RFCs">[RFC5226]</cite></a>), and <em class="bcp14">MUST</em> conform to the purpose of transfer coding defined in this section.
     1883      <p id="rfc.section.5.3.p.4">Values to be added to this name space require IETF Review (see <a href="http://tools.ietf.org/html/rfc5226#section-4.1">Section 4.1</a> of <a href="#RFC5226" id="rfc.xref.RFC5226.1"><cite title="Guidelines for Writing an IANA Considerations Section in RFCs">[RFC5226]</cite></a>), and <em class="bcp14">MUST</em> conform to the purpose of transfer coding defined in this section.
    18831884      </p>
    18841885      <p id="rfc.section.5.3.p.5">The registry itself is maintained at &lt;<a href="http://www.iana.org/assignments/http-parameters">http://www.iana.org/assignments/http-parameters</a>&gt;.
    … …  
    23652366         details how the connection will be processed after it has been upgraded.
    23662367      </p>
    2367       <p id="rfc.section.8.3.1.p.2">Registrations are allowed on a First Come First Served basis as described in <a href="http://tools.ietf.org/html/rfc5226#section-4.1">Section 4.1</a> of <a href="#RFC5226" id="rfc.xref.RFC5226.2"><cite title="Guidelines for Writing an IANA Considerations Section in RFCs">[RFC5226]</cite></a>. The specifications need not be IETF documents or be subject to IESG review. Registrations are subject to the following rules:
     2368      <p id="rfc.section.8.3.1.p.2">Registrations require IETF Review (see <a href="http://tools.ietf.org/html/rfc5226#section-4.1">Section 4.1</a> of <a href="#RFC5226" id="rfc.xref.RFC5226.2"><cite title="Guidelines for Writing an IANA Considerations Section in RFCs">[RFC5226]</cite></a>) and are subject to the following rules:
    23682369      </p>
    23692370      <ol>
    … …  
    30913092         disallowed line folding in chunk extensions, and deprecate their use. (<a href="#chunked.encoding" title="Chunked Transfer Coding">Section&nbsp;5.1</a>)
    30923093      </p>
    3093       <p id="rfc.section.A.2.p.10">Remove hard limit of two connections per server. Remove requirement to retry a sequence of requests as long it was idempotent.
     3094      <p id="rfc.section.A.2.p.10">Registration of Transfer Codings now requires IETF Review (<a href="#transfer.coding.registry" title="Transfer Coding Registry">Section&nbsp;5.3</a>)
     3095      </p>
     3096      <p id="rfc.section.A.2.p.11">Remove hard limit of two connections per server. Remove requirement to retry a sequence of requests as long it was idempotent.
    30943097         Remove requirements about when servers are allowed to close connections prematurely. (<a href="#persistent.practical" title="Practical Considerations">Section&nbsp;6.1.4</a>)
    30953098      </p>
    3096       <p id="rfc.section.A.2.p.11">Remove requirement to retry requests under certain cirumstances when the server prematurely closes the connection. (<a href="#message.transmission.requirements" title="Message Transmission Requirements">Section&nbsp;6.2</a>)
    3097       </p>
    3098       <p id="rfc.section.A.2.p.12">Change ABNF productions for header fields to only define the field value. (<a href="#header.field.definitions" title="Header Field Definitions">Section&nbsp;8</a>)
    3099       </p>
    3100       <p id="rfc.section.A.2.p.13">Clarify exactly when close connection options must be sent. (<a href="#header.connection" id="rfc.xref.header.connection.12" title="Connection">Section&nbsp;8.1</a>)
    3101       </p>
    3102       <p id="rfc.section.A.2.p.14">Define the semantics of the "Upgrade" header field in responses other than 101 (this was incorporated from <a href="#RFC2817" id="rfc.xref.RFC2817.3"><cite title="Upgrading to TLS Within HTTP/1.1">[RFC2817]</cite></a>). (<a href="#header.upgrade" id="rfc.xref.header.upgrade.3" title="Upgrade">Section&nbsp;8.3</a>)
     3099      <p id="rfc.section.A.2.p.12">Remove requirement to retry requests under certain cirumstances when the server prematurely closes the connection. (<a href="#message.transmission.requirements" title="Message Transmission Requirements">Section&nbsp;6.2</a>)
     3100      </p>
     3101      <p id="rfc.section.A.2.p.13">Change ABNF productions for header fields to only define the field value. (<a href="#header.field.definitions" title="Header Field Definitions">Section&nbsp;8</a>)
     3102      </p>
     3103      <p id="rfc.section.A.2.p.14">Clarify exactly when close connection options must be sent. (<a href="#header.connection" id="rfc.xref.header.connection.12" title="Connection">Section&nbsp;8.1</a>)
     3104      </p>
     3105      <p id="rfc.section.A.2.p.15">Define the semantics of the "Upgrade" header field in responses other than 101 (this was incorporated from <a href="#RFC2817" id="rfc.xref.RFC2817.3"><cite title="Upgrading to TLS Within HTTP/1.1">[RFC2817]</cite></a>). (<a href="#header.upgrade" id="rfc.xref.header.upgrade.3" title="Upgrade">Section&nbsp;8.3</a>)
     3106      </p>
     3107      <h2 id="rfc.section.A.3"><a href="#rfc.section.A.3">A.3</a>&nbsp;<a id="changes.from.rfc.2817" href="#changes.from.rfc.2817">Changes from RFC 2817</a></h2>
     3108      <p id="rfc.section.A.3.p.1">Registration of Upgrade tokens now requires IETF Review (<a href="#upgrade.token.registry" title="Upgrade Token Registry">Section&nbsp;8.3.1</a>)
    31033109      </p>
    31043110      <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a>&nbsp;<a id="collected.abnf" href="#collected.abnf">Collected ABNF</a></h1>
    … …  
    36143620         </li>
    36153621         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/343">http://tools.ietf.org/wg/httpbis/trac/ticket/343</a>&gt;: "chunk-extensions"
     3622         </li>
     3623         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/346">http://tools.ietf.org/wg/httpbis/trac/ticket/346</a>&gt;: "make IANA policy definitions consistent"
    36163624         </li>
    36173625      </ul>

  • draft-ietf-httpbis/latest/p1-messaging.xml

    r1566 r1567  
    23922392</t>
    23932393<t>
    2394    Values to be added to this name space require a specification
    2395    (see "Specification Required" in <xref target="RFC5226" x:fmt="of" x:sec="4.1"/>), and &MUST;
     2394   Values to be added to this name space require IETF Review (see
     2395   <xref target="RFC5226" x:fmt="of" x:sec="4.1"/>), and &MUST;
    23962396   conform to the purpose of transfer coding defined in this section.
    23972397</t>
    … …  
    33223322</t>
    33233323<t>
    3324    Registrations are allowed on a First Come First Served basis as
    3325    described in <xref target="RFC5226" x:sec="4.1" x:fmt="of"/>. The
    3326    specifications need not be IETF documents or be subject to IESG review.
    3327    Registrations are subject to the following rules:
     3324   Registrations require IETF Review (see
     3325   <xref target="RFC5226" x:sec="4.1" x:fmt="of"/>) and are subject to the
     3326   following rules:
    33283327  <list style="numbers">
    33293328    <t>A protocol-name token, once registered, stays registered forever.</t>
    … …  
    50075006</t>
    50085007<t>
     5008  Registration of Transfer Codings now requires IETF Review
     5009  (<xref target="transfer.coding.registry"/>)
     5010</t>
     5011<t>
    50095012  Remove hard limit of two connections per server.
    50105013  Remove requirement to retry a sequence of requests as long it was idempotent.
    … …  
    50305033  101 (this was incorporated from <xref target="RFC2817"/>).
    50315034  (<xref target="header.upgrade"/>)
     5035</t>
     5036</section>
     5037
     5038<section title="Changes from RFC 2817" anchor="changes.from.rfc.2817">
     5039<t>
     5040  Registration of Upgrade tokens now requires IETF Review
     5041  (<xref target="upgrade.token.registry"/>)
    50325042</t>
    50335043</section>
    … …  
    59375947      "chunk-extensions"
    59385948    </t>
     5949    <t>
     5950      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/346"/>:
     5951      "make IANA policy definitions consistent"
     5952    </t>
    59395953  </list>
    59405954</t>

  • draft-ietf-httpbis/latest/p2-semantics.html

    r1561 r1567  
    460460  }
    461461  @bottom-center {
    462        content: "Expires September 5, 2012";
     462       content: "Expires September 9, 2012";
    463463  }
    464464  @bottom-right {
    … …  
    513513      <meta name="dct.creator" content="Reschke, J. F.">
    514514      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p2-semantics-latest">
    515       <meta name="dct.issued" scheme="ISO8601" content="2012-03-04">
     515      <meta name="dct.issued" scheme="ISO8601" content="2012-03-08">
    516516      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    517517      <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.">
    … …  
    544544            </tr>
    545545            <tr>
    546                <td class="left">Expires: September 5, 2012</td>
     546               <td class="left">Expires: September 9, 2012</td>
    547547               <td class="right">HP</td>
    548548            </tr>
    … …  
    597597            <tr>
    598598               <td class="left"></td>
    599                <td class="right">March 4, 2012</td>
     599               <td class="right">March 8, 2012</td>
    600600            </tr>
    601601         </tbody>
    … …  
    627627         in progress”.
    628628      </p>
    629       <p>This Internet-Draft will expire on September 5, 2012.</p>
     629      <p>This Internet-Draft will expire on September 9, 2012.</p>
    630630      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    631631      <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
    … …  
    935935         <li>Pointer to specification text</li>
    936936      </ul>
    937       <p id="rfc.section.2.2.p.3">Values to be added to this name space are subject to IETF review (<a href="#RFC5226" id="rfc.xref.RFC5226.1"><cite title="Guidelines for Writing an IANA Considerations Section in RFCs">[RFC5226]</cite></a>, <a href="http://tools.ietf.org/html/rfc5226#section-4.1">Section 4.1</a>).
     937      <p id="rfc.section.2.2.p.3">Values to be added to this name space require IETF Review (see <a href="#RFC5226" id="rfc.xref.RFC5226.1"><cite title="Guidelines for Writing an IANA Considerations Section in RFCs">[RFC5226]</cite></a>, <a href="http://tools.ietf.org/html/rfc5226#section-4.1">Section 4.1</a>).
    938938      </p>
    939939      <p id="rfc.section.2.2.p.4">The registry itself is maintained at &lt;<a href="http://www.iana.org/assignments/http-methods">http://www.iana.org/assignments/http-methods</a>&gt;.
    … …  
    14121412      <h2 id="rfc.section.4.2"><a href="#rfc.section.4.2">4.2</a>&nbsp;<a id="status.code.registry" href="#status.code.registry">Status Code Registry</a></h2>
    14131413      <p id="rfc.section.4.2.p.1">The HTTP Status Code Registry defines the name space for the status-code token in the status-line of an HTTP response.</p>
    1414       <p id="rfc.section.4.2.p.2">Values to be added to this name space are subject to IETF review (<a href="#RFC5226" id="rfc.xref.RFC5226.2"><cite title="Guidelines for Writing an IANA Considerations Section in RFCs">[RFC5226]</cite></a>, <a href="http://tools.ietf.org/html/rfc5226#section-4.1">Section 4.1</a>).
     1414      <p id="rfc.section.4.2.p.2">Values to be added to this name space require IETF Review (see <a href="#RFC5226" id="rfc.xref.RFC5226.2"><cite title="Guidelines for Writing an IANA Considerations Section in RFCs">[RFC5226]</cite></a>, <a href="http://tools.ietf.org/html/rfc5226#section-4.1">Section 4.1</a>).
    14151415      </p>
    14161416      <p id="rfc.section.4.2.p.3">The registry itself is maintained at &lt;<a href="http://www.iana.org/assignments/http-status-codes">http://www.iana.org/assignments/http-status-codes</a>&gt;.

  • draft-ietf-httpbis/latest/p2-semantics.xml

    r1561 r1567  
    461461</t>
    462462<t>
    463   Values to be added to this name space are subject to IETF review
    464   (<xref target="RFC5226" x:fmt="," x:sec="4.1"/>).
     463  Values to be added to this name space require IETF Review
     464  (see <xref target="RFC5226" x:fmt="," x:sec="4.1"/>).
    465465</t>
    466466<t>
    … …  
    756756</t>
    757757<t>
    758   Values to be added to this name space are subject to IETF review
    759   (<xref target="RFC5226" x:fmt="," x:sec="4.1"/>).
     758  Values to be added to this name space require IETF Review
     759  (see <xref target="RFC5226" x:fmt="," x:sec="4.1"/>).
    760760</t>
    761761<t>

  • draft-ietf-httpbis/latest/p3-payload.html

    r1566 r1567  
    460460  }
    461461  @bottom-center {
    462        content: "Expires September 8, 2012";
     462       content: "Expires September 9, 2012";
    463463  }
    464464  @bottom-right {
    … …  
    511511      <meta name="dct.creator" content="Reschke, J. F.">
    512512      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p3-payload-latest">
    513       <meta name="dct.issued" scheme="ISO8601" content="2012-03-07">
     513      <meta name="dct.issued" scheme="ISO8601" content="2012-03-08">
    514514      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    515515      <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.">
    … …  
    537537            </tr>
    538538            <tr>
    539                <td class="left">Expires: September 8, 2012</td>
     539               <td class="left">Expires: September 9, 2012</td>
    540540               <td class="right">J. Mogul</td>
    541541            </tr>
    … …  
    594594            <tr>
    595595               <td class="left"></td>
    596                <td class="right">March 7, 2012</td>
     596               <td class="right">March 8, 2012</td>
    597597            </tr>
    598598         </tbody>
    … …  
    622622         in progress”.
    623623      </p>
    624       <p>This Internet-Draft will expire on September 8, 2012.</p>
     624      <p>This Internet-Draft will expire on September 9, 2012.</p>
    625625      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    626626      <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
    … …  
    857857      <p id="rfc.section.2.2.1.p.3">Names of content codings <em class="bcp14">MUST NOT</em> overlap with names of transfer codings (<a href="p1-messaging.html#transfer.codings" title="Transfer Codings">Section 5</a> of <a href="#Part1" id="rfc.xref.Part1.13"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>), unless the encoding transformation is identical (as is the case for the compression codings defined in <a href="p1-messaging.html#compression.codings" title="Compression Codings">Section 5.2</a> of <a href="#Part1" id="rfc.xref.Part1.14"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>).
    858858      </p>
    859       <p id="rfc.section.2.2.1.p.4">Values to be added to this name space require a specification (see "Specification Required" in <a href="http://tools.ietf.org/html/rfc5226#section-4.1">Section 4.1</a> of <a href="#RFC5226" id="rfc.xref.RFC5226.1"><cite title="Guidelines for Writing an IANA Considerations Section in RFCs">[RFC5226]</cite></a>), and <em class="bcp14">MUST</em> conform to the purpose of content coding defined in this section.
     859      <p id="rfc.section.2.2.1.p.4">Values to be added to this name space require IETF Review (see <a href="http://tools.ietf.org/html/rfc5226#section-4.1">Section 4.1</a> of <a href="#RFC5226" id="rfc.xref.RFC5226.1"><cite title="Guidelines for Writing an IANA Considerations Section in RFCs">[RFC5226]</cite></a>), and <em class="bcp14">MUST</em> conform to the purpose of content coding defined in this section.
    860860      </p>
    861861      <p id="rfc.section.2.2.1.p.5">The registry itself is maintained at &lt;<a href="http://www.iana.org/assignments/http-parameters">http://www.iana.org/assignments/http-parameters</a>&gt;.
    … …  
    18471847      <p id="rfc.section.C.p.1">Clarify contexts that charset is used in. (<a href="#character.sets" title="Character Encodings (charset)">Section&nbsp;2.1</a>)
    18481848      </p>
    1849       <p id="rfc.section.C.p.2">Remove the default character encoding for text media types; the default now is whatever the media type definition says. (<a href="#canonicalization.and.text.defaults" title="Canonicalization and Text Defaults">Section&nbsp;2.3.1</a>)
    1850       </p>
    1851       <p id="rfc.section.C.p.3">Change ABNF productions for header fields to only define the field value. (<a href="#header.field.definitions" title="Header Field Definitions">Section&nbsp;6</a>)
    1852       </p>
    1853       <p id="rfc.section.C.p.4">Remove definition of Content-MD5 header field because it was inconsistently implemented with respect to partial responses,
     1849      <p id="rfc.section.C.p.2">Registration of Content Codings now requires IETF Review (<a href="#content.coding.registry" title="Content Coding Registry">Section&nbsp;2.2.1</a>)
     1850      </p>
     1851      <p id="rfc.section.C.p.3">Remove the default character encoding for text media types; the default now is whatever the media type definition says. (<a href="#canonicalization.and.text.defaults" title="Canonicalization and Text Defaults">Section&nbsp;2.3.1</a>)
     1852      </p>
     1853      <p id="rfc.section.C.p.4">Change ABNF productions for header fields to only define the field value. (<a href="#header.field.definitions" title="Header Field Definitions">Section&nbsp;6</a>)
     1854      </p>
     1855      <p id="rfc.section.C.p.5">Remove definition of Content-MD5 header field because it was inconsistently implemented with respect to partial responses,
    18541856         and also because of known deficiencies in the hash algorithm itself (see <a href="#RFC6151" id="rfc.xref.RFC6151.1"><cite title="Updated Security Considerations for the MD5 Message-Digest and the HMAC-MD5 Algorithms">[RFC6151]</cite></a> for details). (<a href="#header.field.definitions" title="Header Field Definitions">Section&nbsp;6</a>)
    18551857      </p>
    1856       <p id="rfc.section.C.p.5">Remove ISO-8859-1 special-casing in Accept-Charset. (<a href="#header.accept-charset" id="rfc.xref.header.accept-charset.3" title="Accept-Charset">Section&nbsp;6.2</a>)
    1857       </p>
    1858       <p id="rfc.section.C.p.6">Remove base URI setting semantics for Content-Location due to poor implementation support, which was caused by too many broken
     1858      <p id="rfc.section.C.p.6">Remove ISO-8859-1 special-casing in Accept-Charset. (<a href="#header.accept-charset" id="rfc.xref.header.accept-charset.3" title="Accept-Charset">Section&nbsp;6.2</a>)
     1859      </p>
     1860      <p id="rfc.section.C.p.7">Remove base URI setting semantics for Content-Location due to poor implementation support, which was caused by too many broken
    18591861         servers emitting bogus Content-Location header fields, and also the potentially undesirable effect of potentially breaking
    18601862         relative links in content-negotiated resources. (<a href="#header.content-location" id="rfc.xref.header.content-location.3" title="Content-Location">Section&nbsp;6.7</a>)
    18611863      </p>
    1862       <p id="rfc.section.C.p.7">Remove reference to non-existant identity transfer-coding value tokens. (<a href="#no.content-transfer-encoding" id="rfc.xref.no.content-transfer-encoding.1" title="No Content-Transfer-Encoding">Appendix&nbsp;A.5</a>)
    1863       </p>
    1864       <p id="rfc.section.C.p.8">Remove discussion of Content-Disposition header field, it is now defined by <a href="#RFC6266" id="rfc.xref.RFC6266.2"><cite title="Use of the Content-Disposition Header Field in the Hypertext Transfer Protocol (HTTP)">[RFC6266]</cite></a>. (<a href="#additional.features" title="Additional Features">Appendix&nbsp;B</a>)
     1864      <p id="rfc.section.C.p.8">Remove reference to non-existant identity transfer-coding value tokens. (<a href="#no.content-transfer-encoding" id="rfc.xref.no.content-transfer-encoding.1" title="No Content-Transfer-Encoding">Appendix&nbsp;A.5</a>)
     1865      </p>
     1866      <p id="rfc.section.C.p.9">Remove discussion of Content-Disposition header field, it is now defined by <a href="#RFC6266" id="rfc.xref.RFC6266.2"><cite title="Use of the Content-Disposition Header Field in the Hypertext Transfer Protocol (HTTP)">[RFC6266]</cite></a>. (<a href="#additional.features" title="Additional Features">Appendix&nbsp;B</a>)
    18651867      </p>
    18661868      <h1 id="rfc.section.D"><a href="#rfc.section.D">D.</a>&nbsp;<a id="collected.abnf" href="#collected.abnf">Collected ABNF</a></h1>
    … …  
    21532155      </ul>
    21542156      <h2 id="rfc.section.E.20"><a href="#rfc.section.E.20">E.20</a>&nbsp;<a id="changes.since.18" href="#changes.since.18">Since draft-ietf-httpbis-p3-payload-18</a></h2>
    2155       <p id="rfc.section.E.20.p.1">None yet.</p>
     2157      <p id="rfc.section.E.20.p.1">Closed issues: </p>
     2158      <ul>
     2159         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/346">http://tools.ietf.org/wg/httpbis/trac/ticket/346</a>&gt;: "make IANA policy definitions consistent"
     2160         </li>
     2161      </ul>
    21562162      <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1>
    21572163      <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>

  • draft-ietf-httpbis/latest/p3-payload.xml

    r1566 r1567  
    462462</t>
    463463<t>
    464    Values to be added to this name space require a specification
    465    (see "Specification Required" in
    466    <xref target="RFC5226" x:fmt="of" x:sec="4.1"/>), and &MUST;
     464   Values to be added to this name space require IETF Review
     465   (see <xref target="RFC5226" x:fmt="of" x:sec="4.1"/>), and &MUST;
    467466   conform to the purpose of content coding defined in this section.
    468467</t>
    … …  
    25262525</t>
    25272526<t>
     2527  Registration of Content Codings now requires IETF Review
     2528  (<xref target="content.coding.registry"/>)
     2529</t>
     2530<t>
    25282531  Remove the default character encoding for text media types; the default
    25292532  now is whatever the media type definition says.
    … …  
    30823085<section title="Since draft-ietf-httpbis-p3-payload-18" anchor="changes.since.18">
    30833086<t>
    3084   None yet.
     3087  Closed issues:
     3088  <list style="symbols">
     3089    <t>
     3090      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/346"/>:
     3091      "make IANA policy definitions consistent"
     3092    </t>
     3093  </list>
    30853094</t>
    30863095</section>

  • draft-ietf-httpbis/latest/p5-range.html

    r1566 r1567  
    460460  }
    461461  @bottom-center {
    462        content: "Expires September 8, 2012";
     462       content: "Expires September 9, 2012";
    463463  }
    464464  @bottom-right {
    … …  
    509509      <meta name="dct.creator" content="Reschke, J. F.">
    510510      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p5-range-latest">
    511       <meta name="dct.issued" scheme="ISO8601" content="2012-03-07">
     511      <meta name="dct.issued" scheme="ISO8601" content="2012-03-08">
    512512      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    513513      <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.">
    … …  
    535535            </tr>
    536536            <tr>
    537                <td class="left">Expires: September 8, 2012</td>
     537               <td class="left">Expires: September 9, 2012</td>
    538538               <td class="right">J. Mogul</td>
    539539            </tr>
    … …  
    592592            <tr>
    593593               <td class="left"></td>
    594                <td class="right">March 7, 2012</td>
     594               <td class="right">March 8, 2012</td>
    595595            </tr>
    596596         </tbody>
    … …  
    620620         in progress”.
    621621      </p>
    622       <p>This Internet-Draft will expire on September 8, 2012.</p>
     622      <p>This Internet-Draft will expire on September 9, 2012.</p>
    623623      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    624624      <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
    … …  
    789789         <li>Pointer to specification text</li>
    790790      </ul>
    791       <p id="rfc.section.2.1.p.3">Values to be added to this name space are subject to IETF review (<a href="#RFC5226" id="rfc.xref.RFC5226.1"><cite title="Guidelines for Writing an IANA Considerations Section in RFCs">[RFC5226]</cite></a>, <a href="http://tools.ietf.org/html/rfc5226#section-4.1">Section 4.1</a>).
     791      <p id="rfc.section.2.1.p.3">Values to be added to this name space require IETF Review (see <a href="#RFC5226" id="rfc.xref.RFC5226.1"><cite title="Guidelines for Writing an IANA Considerations Section in RFCs">[RFC5226]</cite></a>, <a href="http://tools.ietf.org/html/rfc5226#section-4.1">Section 4.1</a>).
    792792      </p>
    793793      <p id="rfc.section.2.1.p.4">The registry itself is maintained at &lt;<a href="http://www.iana.org/assignments/http-range-specifiers">http://www.iana.org/assignments/http-range-specifiers</a>&gt;.

  • draft-ietf-httpbis/latest/p5-range.xml

    r1566 r1567  
    386386</t>
    387387<t>
    388   Values to be added to this name space are subject to IETF review
    389   (<xref target="RFC5226" x:fmt="," x:sec="4.1"/>).
     388  Values to be added to this name space require IETF Review
     389  (see <xref target="RFC5226" x:fmt="," x:sec="4.1"/>).
    390390</t>
    391391<t>

  • draft-ietf-httpbis/latest/p6-cache.html

    r1564 r1567  
    463463  }
    464464  @bottom-center {
    465        content: "Expires September 7, 2012";
     465       content: "Expires September 9, 2012";
    466466  }
    467467  @bottom-right {
    … …  
    511511      <meta name="dct.creator" content="Reschke, J. F.">
    512512      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p6-cache-latest">
    513       <meta name="dct.issued" scheme="ISO8601" content="2012-03-06">
     513      <meta name="dct.issued" scheme="ISO8601" content="2012-03-08">
    514514      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    515515      <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.">
    … …  
    537537            </tr>
    538538            <tr>
    539                <td class="left">Expires: September 7, 2012</td>
     539               <td class="left">Expires: September 9, 2012</td>
    540540               <td class="right">J. Mogul</td>
    541541            </tr>
    … …  
    602602            <tr>
    603603               <td class="left"></td>
    604                <td class="right">March 6, 2012</td>
     604               <td class="right">March 8, 2012</td>
    605605            </tr>
    606606         </tbody>
    … …  
    632632         in progress”.
    633633      </p>
    634       <p>This Internet-Draft will expire on September 7, 2012.</p>
     634      <p>This Internet-Draft will expire on September 9, 2012.</p>
    635635      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    636636      <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
    … …  
    15101510         <li>Pointer to specification text</li>
    15111511      </ul>
    1512       <p id="rfc.section.3.2.3.p.9">Values to be added to this name space are subject to IETF review (<a href="#RFC5226" id="rfc.xref.RFC5226.1"><cite title="Guidelines for Writing an IANA Considerations Section in RFCs">[RFC5226]</cite></a>, <a href="http://tools.ietf.org/html/rfc5226#section-4.1">Section 4.1</a>).
     1512      <p id="rfc.section.3.2.3.p.9">Values to be added to this name space require IETF Review (see <a href="#RFC5226" id="rfc.xref.RFC5226.1"><cite title="Guidelines for Writing an IANA Considerations Section in RFCs">[RFC5226]</cite></a>, <a href="http://tools.ietf.org/html/rfc5226#section-4.1">Section 4.1</a>).
    15131513      </p>
    15141514      <p id="rfc.section.3.2.3.p.10">The registry itself is maintained at &lt;<a href="http://www.iana.org/assignments/http-cache-directives">http://www.iana.org/assignments/http-cache-directives</a>&gt;.
    … …  
    16961696         <li>Pointer to specification text</li>
    16971697      </ul>
    1698       <p id="rfc.section.3.6.8.p.3">Values to be added to this name space are subject to IETF review (<a href="#RFC5226" id="rfc.xref.RFC5226.2"><cite title="Guidelines for Writing an IANA Considerations Section in RFCs">[RFC5226]</cite></a>, <a href="http://tools.ietf.org/html/rfc5226#section-4.1">Section 4.1</a>).
     1698      <p id="rfc.section.3.6.8.p.3">Values to be added to this name space require IETF Review (see <a href="#RFC5226" id="rfc.xref.RFC5226.2"><cite title="Guidelines for Writing an IANA Considerations Section in RFCs">[RFC5226]</cite></a>, <a href="http://tools.ietf.org/html/rfc5226#section-4.1">Section 4.1</a>).
    16991699      </p>
    17001700      <p id="rfc.section.3.6.8.p.4">The registry itself is maintained at &lt;<a href="http://www.iana.org/assignments/http-warn-codes">http://www.iana.org/assignments/http-warn-codes</a>&gt;.

  • draft-ietf-httpbis/latest/p6-cache.xml

    r1564 r1567  
    16391639</t>
    16401640<t>
    1641    Values to be added to this name space are subject to IETF review (<xref
     1641   Values to be added to this name space require IETF Review (see <xref
    16421642   target="RFC5226" x:fmt="," x:sec="4.1"/>).
    16431643</t>
    … …  
    19831983</t>
    19841984<t>
    1985    Values to be added to this name space are subject to IETF review (<xref
     1985   Values to be added to this name space require IETF Review (see <xref
    19861986   target="RFC5226" x:fmt="," x:sec="4.1"/>).
    19871987</t>

  • draft-ietf-httpbis/latest/p7-auth.html

    r1562 r1567  
    460460  }
    461461  @bottom-center {
    462        content: "Expires September 5, 2012";
     462       content: "Expires September 9, 2012";
    463463  }
    464464  @bottom-right {
    … …  
    506506      <meta name="dct.creator" content="Reschke, J. F.">
    507507      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p7-auth-latest">
    508       <meta name="dct.issued" scheme="ISO8601" content="2012-03-04">
     508      <meta name="dct.issued" scheme="ISO8601" content="2012-03-08">
    509509      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    510510      <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.">
    … …  
    537537            </tr>
    538538            <tr>
    539                <td class="left">Expires: September 5, 2012</td>
     539               <td class="left">Expires: September 9, 2012</td>
    540540               <td class="right">HP</td>
    541541            </tr>
    … …  
    590590            <tr>
    591591               <td class="left"></td>
    592                <td class="right">March 4, 2012</td>
     592               <td class="right">March 8, 2012</td>
    593593            </tr>
    594594         </tbody>
    … …  
    618618         in progress”.
    619619      </p>
    620       <p>This Internet-Draft will expire on September 5, 2012.</p>
     620      <p>This Internet-Draft will expire on September 9, 2012.</p>
    621621      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    622622      <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
    … …  
    830830         <li>Notes (optional)</li>
    831831      </ul>
    832       <p id="rfc.section.2.3.p.3">Values to be added to this name space are subject to IETF review (<a href="#RFC5226" id="rfc.xref.RFC5226.1"><cite title="Guidelines for Writing an IANA Considerations Section in RFCs">[RFC5226]</cite></a>, <a href="http://tools.ietf.org/html/rfc5226#section-4.1">Section 4.1</a>).
     832      <p id="rfc.section.2.3.p.3">Values to be added to this name space require IETF Review (see <a href="#RFC5226" id="rfc.xref.RFC5226.1"><cite title="Guidelines for Writing an IANA Considerations Section in RFCs">[RFC5226]</cite></a>, <a href="http://tools.ietf.org/html/rfc5226#section-4.1">Section 4.1</a>).
    833833      </p>
    834834      <p id="rfc.section.2.3.p.4">The registry itself is maintained at &lt;<a href="http://www.iana.org/assignments/http-authschemes">http://www.iana.org/assignments/http-authschemes</a>&gt;.

  • draft-ietf-httpbis/latest/p7-auth.xml

    r1562 r1567  
    477477</t>
    478478<t>
    479   Values to be added to this name space are subject to IETF review
    480   (<xref target="RFC5226" x:fmt="," x:sec="4.1"/>).
     479  Values to be added to this name space require IETF Review
     480  (see <xref target="RFC5226" x:fmt="," x:sec="4.1"/>).
    481481</t>
    482482<t>
Note: See TracChangeset for help on using the changeset viewer.