Ignore:
Timestamp:
May 7, 2013, 9:47:33 AM (7 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/p5-range.xml

    r2232 r2246  
    844844   The HTTP Range Unit Registry defines the name space for the range
    845845   unit names and refers to their corresponding specifications.
    846    The registry is maintained at
     846   The registry will be created and maintained at
    847847   <eref target="http://www.iana.org/assignments/http-parameters"/>.
    848848</t>
     
    915915<section title="Header Field Registration" anchor="header.field.registration">
    916916<t>
    917    The Message Header Field Registry located at <eref target="http://www.iana.org/assignments/message-headers/message-header-index.html"/> shall be updated
    918    with the permanent registrations below (see <xref target="BCP90"/>):
     917   HTTP header fields are registered within the Message Header Field Registry
     918   maintained at
     919   <eref target="http://www.iana.org/assignments/message-headers/message-header-index.html"/>.
     920</t>
     921<t>
     922   This document defines the following HTTP header fields, so their
     923   associated registry entries shall be updated according to the permanent
     924   registrations below (see <xref target="BCP90"/>):
    919925</t>
    920926<?BEGININC p5-range.iana-headers ?>
Note: See TracChangeset for help on using the changeset viewer.