Ignore:
Timestamp:
Sep 3, 2012, 5:07:11 PM (7 years ago)
Author:
fielding@…
Message:

(editorial) improve an xref

File:
1 edited

Legend:

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

    r1859 r1861  
    5353  <!ENTITY status-4xx             "<xref target='Part2' x:rel='#status.4xx' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    5454  <!ENTITY status-414             "<xref target='Part2' x:rel='#status.414' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    55   <!ENTITY cons-new-header-fields "<xref target='Part2' x:rel='#considerations.for.new.header.fields' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     55  <!ENTITY iana-header-registry   "<xref target='Part2' x:rel='#header.field.registry' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    5656]>
    5757<?rfc toc="yes" ?>
     
    12031203</t>
    12041204<t>
    1205    New HTTP header fields &SHOULD; be registered with IANA according
    1206    to the procedures in &cons-new-header-fields;.
     1205   New HTTP header fields &SHOULD; be registered with IANA in the
     1206   Message Header Field Registry, as described in &iana-header-registry;.
    12071207   Unrecognized header fields &MUST; be forwarded by a proxy unless the
    12081208   field-name is listed in the <x:ref>Connection</x:ref> header field
Note: See TracChangeset for help on using the changeset viewer.