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

Ticket #346: 346.diff

File 346.diff, 6.5 KB (added by julian.reschke@gmx.de, 2 years ago)

Proposed patch

  • p1-messaging.xml

     
    23912391   <xref target="compression.codings"/>). 
    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> 
    23982398<t> 
     
    33213321   will be processed after it has been upgraded. 
    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> 
    33303329    <t>The registration &MUST; name a responsible party for the 
     
    50055004  (<xref target="chunked.encoding"/>) 
    50065005</t> 
    50075006<t> 
     5007  Registration of Transfer Codings now requires IETF Review 
     5008  (<xref target="transfer.coding.registry"/>) 
     5009</t> 
     5010<t> 
    50085011  Remove hard limit of two connections per server. 
    50095012  Remove requirement to retry a sequence of requests as long it was idempotent. 
    50105013  Remove requirements about when servers are allowed to close connections 
     
    50305033  (<xref target="header.upgrade"/>) 
    50315034</t> 
    50325035</section> 
     5036 
     5037<section title="Changes from RFC 2817" anchor="changes.from.rfc.2817"> 
     5038<t> 
     5039  Registration of Upgrade tokens now requires IETF Review 
     5040  (<xref target="upgrade.token.registry"/>) 
     5041</t> 
    50335042</section> 
     5043</section> 
    50345044 
    50355045<?BEGININC p1-messaging.abnf-appendix ?> 
    50365046<section xmlns:x="http://purl.org/net/xml2rfc/ext" title="Collected ABNF" anchor="collected.abnf"> 
     
    59355945      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/343"/>: 
    59365946      "chunk-extensions" 
    59375947    </t> 
     5948    <t> 
     5949      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/346"/>: 
     5950      "make IANA policy definitions consistent" 
     5951    </t> 
    59385952  </list> 
    59395953</t> 
    59405954</section> 
  • p2-semantics.xml

     
    460460  </list> 
    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> 
    467467  The registry itself is maintained at <eref target="http://www.iana.org/assignments/http-methods"/>. 
     
    755755  token in the status-line of an HTTP response. 
    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> 
    762762  The registry itself is maintained at <eref target="http://www.iana.org/assignments/http-status-codes"/>. 
  • p3-payload.xml

     
    461461   &compression-codings;). 
    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> 
    469468<t> 
     
    25252524  (<xref target="character.sets"/>) 
    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. 
    25302533  (<xref target="canonicalization.and.text.defaults"/>) 
     
    30813084 
    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> 
    30873096 
  • p5-range.xml

     
    385385   </list> 
    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> 
    392392   The registry itself is maintained at 
  • p6-cache.xml

     
    16381638   </list> 
    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> 
    16441644<t> 
     
    19821982   </list> 
    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> 
    19881988<t> 
  • p7-auth.xml

     
    476476  </list> 
    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> 
    483483  The registry itself is maintained at <eref target="http://www.iana.org/assignments/http-authschemes"/>.