Ignore:
Timestamp:
May 7, 2013, 9:47:33 AM (6 years ago)
Author:
julian.reschke@…
Message:

Consistency in registration descriptions, also add required fields for status code registrations (related to #464).

File:
1 edited

Legend:

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

    r2233 r2246  
    31603160<t>
    31613161   HTTP header fields are registered within the Message Header Field Registry
    3162    <xref target="BCP90"/> maintained by IANA at
     3162   maintained at
    31633163   <eref target="http://www.iana.org/assignments/message-headers/message-header-index.html"/>.
    31643164</t>
     
    31663166   This document defines the following HTTP header fields, so their
    31673167   associated registry entries shall be updated according to the permanent
    3168    registrations below:
     3168   registrations below (see <xref target="BCP90"/>):
    31693169</t>
    31703170<?BEGININC p1-messaging.iana-headers ?>
     
    34353435<t>
    34363436   The HTTP Transfer Coding Registry defines the name space for transfer
    3437    coding names.
    3438 </t>
     3437   coding names. It is maintained at <eref target="http://www.iana.org/assignments/http-parameters"/>.
     3438</t>
     3439
     3440<section title="Procedure" anchor="transfer.coding.registry.procedure">
    34393441<t>
    34403442   Registrations &MUST; include the following fields:
     
    34543456   Values to be added to this name space require IETF Review (see
    34553457   <xref target="RFC5226" x:fmt="of" x:sec="4.1"/>), and &MUST;
    3456    conform to the purpose of transfer coding defined in this section.
     3458   conform to the purpose of transfer coding defined in this specification.
     3459</t>
     3460<t>
    34573461   Use of program names for the identification of encoding formats
    34583462   is not desirable and is discouraged for future encodings.
    34593463</t>
    3460 <t>
    3461    The registry itself is maintained at
    3462    <eref target="http://www.iana.org/assignments/http-parameters"/>.
    3463 </t>
    3464 </section>
    3465 
    3466 <section title="Transfer Coding Registration" anchor="transfer.coding.registration">
     3464</section>
     3465
     3466<section title="Registration" anchor="transfer.coding.registration">
    34673467<t>
    34683468   The HTTP Transfer Coding Registry shall be updated with the registrations
     
    34973497</texttable>
    34983498</section>
     3499</section>
    34993500
    35003501<section title="Upgrade Token Registry" anchor="upgrade.token.registry">
     
    35023503   The HTTP Upgrade Token Registry defines the name space for protocol-name
    35033504   tokens used to identify protocols in the <x:ref>Upgrade</x:ref> header
    3504    field. Each registered protocol name is associated with contact information
     3505   field. The registry is maintained at <eref target="http://www.iana.org/assignments/http-upgrade-tokens"/>.
     3506</t>
     3507
     3508<section title="Procedure" anchor="upgrade.token.registry.procedure">   
     3509<t>
     3510   Each registered protocol name is associated with contact information
    35053511   and an optional set of specifications that details how the connection
    35063512   will be processed after it has been upgraded.
     
    35523558   The responsible party is: "IETF (iesg@ietf.org) - Internet Engineering Task Force".
    35533559</t>
     3560</section>
    35543561</section>
    35553562
Note: See TracChangeset for help on using the changeset viewer.