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

make IANA policy definitions consistent (see #346)

File:
1 edited

Legend:

Unmodified
Added
Removed
  • 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>
Note: See TracChangeset for help on using the changeset viewer.