Ignore:
Timestamp:
Dec 9, 2012, 7:44:14 AM (7 years ago)
Author:
fielding@…
Message:

Reference BCP numbers when informative and not section specific; Note added requirement on URI consistency with method semantics; partly addresses #419

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p5-range.xml

    r2045 r2046  
    826826<t>
    827827   The Message Header Field Registry located at <eref target="http://www.iana.org/assignments/message-headers/message-header-index.html"/> shall be updated
    828    with the permanent registrations below (see <xref target="RFC3864"/>):
     828   with the permanent registrations below (see <xref target="BCP90"/>):
    829829</t>
    830830<?BEGININC p5-range.iana-headers ?>
     
    11051105</reference>
    11061106
    1107 <reference anchor='RFC3864'>
     1107<reference anchor='BCP90'>
    11081108  <front>
    11091109    <title>Registration Procedures for Message Header Fields</title>
     
    11261126</reference>
    11271127
    1128 <reference anchor="RFC4288">
     1128<reference anchor="BCP13">
    11291129  <front>
    11301130    <title>Media Type Specifications and Registration Procedures</title>
     
    11731173   non-overlapping ranges), these are transmitted as a multipart
    11741174   message body (<xref target="RFC2046" x:fmt="," x:sec="5.1"/>). The media type for this purpose is called
    1175    "multipart/byteranges".  The following is to be registered with IANA <xref target="RFC4288"/>.
     1175   "multipart/byteranges".  The following is to be registered with IANA <xref target="BCP13"/>.
    11761176</t>
    11771177<t>
Note: See TracChangeset for help on using the changeset viewer.