Ignore:
Timestamp:
Sep 1, 2012, 12:03:26 AM (7 years ago)
Author:
fielding@…
Message:

(editorial) clean up xrefs and redundancies after the registry move

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p2-semantics.xml

    r1843 r1844  
    39443944<section title="Method Registry" anchor="method.registry">
    39453945<t>
    3946   The HTTP Method Registry defines the name space for the method token in the
    3947   Request line of an HTTP request.
    3948 </t>
     3946  The HTTP Method Registry defines the name space for the request method
     3947  token (<xref target="methods"/>).
     3948  The method registry is maintained at
     3949  <eref target="http://www.iana.org/assignments/http-methods"/>.
     3950</t>
     3951
    39493952<section title="Procedure" anchor="method.procedure">
    39503953<t>
    3951   Registrations &MUST; include the following fields:
     3954  HTTP method registrations &MUST; include the following fields:
    39523955  <list style="symbols">
    39533956    <t>Method Name (see <xref target="methods"/>)</t>
     
    39603963  Values to be added to this name space require IETF Review
    39613964  (see <xref target="RFC5226" x:fmt="," x:sec="4.1"/>).
    3962 </t>
    3963 <t>
    3964   The registry itself is maintained at <eref target="http://www.iana.org/assignments/http-methods"/>.
    39653965</t>
    39663966</section>
     
    39863986   New method definitions need to indicate whether they are safe (<xref
    39873987   target="safe.methods"/>), idempotent (<xref target="idempotent.methods"/>),
    3988    or cacheable (<xref target="cacheable.methods"/>), and what
     3988   cacheable (<xref target="cacheable.methods"/>), and what
    39893989   semantics are to be associated with the request body if any is present
    39903990   in the request.  If a method is cacheable, the method definition ought
     
    39963996<section title="Registrations" anchor="method.registration">
    39973997<t>
    3998    The HTTP Method Registry shall be created at <eref target="http://www.iana.org/assignments/http-methods"/>
    3999    and be populated with the registrations below:
     3998   The HTTP Method Registry shall be populated with the registrations below:
    40003999</t>
    40014000<?BEGININC p2-semantics.iana-methods ?>
     
    40624061<section title="Status Code Registry" anchor="status.code.registry">
    40634062<t>
    4064   The HTTP Status Code Registry defines the name space for the status-code
    4065   token in the status-line of an HTTP response (<xref target="status.codes"/>).
     4063   The HTTP Status Code Registry defines the name space for the response
     4064   status-code token (<xref target="status.codes"/>).
     4065   The status code registry is maintained at
     4066   <eref target="http://www.iana.org/assignments/http-status-codes"/>.
     4067</t>
     4068<t>
     4069   This section replaces the registration procedure for HTTP Status Codes
     4070   previously defined in <xref target="RFC2817" x:fmt="of" x:sec="7.1"/>.
    40664071</t>
    40674072
    40684073<section title="Procedure" anchor="status.code.procedure">
    40694074<t>
    4070   Values to be added to this name space require IETF Review
    4071   (see <xref target="RFC5226" x:fmt="," x:sec="4.1"/>).
    4072 </t>
    4073 <t>
    4074   The registry itself is maintained at <eref target="http://www.iana.org/assignments/http-status-codes"/>.
     4075   Values to be added to the HTTP status code name space require IETF Review
     4076   (see <xref target="RFC5226" x:fmt="," x:sec="4.1"/>).
    40754077</t>
    40764078</section>
     
    41154117<section title="Registrations" anchor="status.code.registration">
    41164118<t>
    4117    The registration procedure for HTTP Status Codes &mdash; previously defined
    4118    in <xref target="RFC2817" x:fmt="of" x:sec="7.1"/> &mdash; is now defined
    4119    by <xref target="status.code.registry"/> of this document.
    4120 </t>
    4121 <t>
    4122    The HTTP Status Code Registry located at <eref target="http://www.iana.org/assignments/http-status-codes"/>
    4123    shall be updated with the registrations below:
     4119   The HTTP Status Code Registry shall be updated with the registrations below:
    41244120</t>
    41254121<?BEGININC p2-semantics.iana-status-codes ?>
     
    43174313<section title="Header Field Registration" anchor="header.field.registration">
    43184314<t>
    4319    The Message Header Field Registry located at <eref target="http://www.iana.org/assignments/message-headers/message-header-index.html"/> shall be updated
    4320    with the permanent registrations below (see <xref target="RFC3864"/>):
     4315   HTTP header fields are registered within the Message Header Field Registry
     4316   located at <eref target="http://www.iana.org/assignments/message-headers/message-header-index.html"/>
     4317   (see <xref target="RFC3864"/>).  The Message Header Field Registry
     4318   shall be updated with the permanent registrations below:
    43214319</t>
    43224320<?BEGININC p2-semantics.iana-headers ?>
     
    44464444<?ENDINC p2-semantics.iana-headers ?>
    44474445<t>
    4448    The change controller is: "IETF (iesg@ietf.org) - Internet Engineering Task Force".
     4446   The change controller for the above registrations is:
     4447   "IETF (iesg@ietf.org) - Internet Engineering Task Force".
    44494448</t>
    44504449</section>
     
    44524451<section title="Content Coding Registry" anchor="content.coding.registry">
    44534452<t>
    4454    The HTTP Content Coding Registry defines the name space for the content
    4455    coding names.
     4453   The HTTP Content Coding Registry defines the name space for content
     4454   coding names (&compression-codings;).
     4455   The content coding registry is maintained at
     4456   <eref target="http://www.iana.org/assignments/http-parameters"/>.
    44564457</t>
    44574458
    44584459<section title="Procedure" anchor="content.coding.procedure">
    44594460<t>
    4460    Registrations &MUST; include the following fields:
     4461   Content Coding registrations &MUST; include the following fields:
    44614462   <list style="symbols">
    44624463     <t>Name</t>
     
    44764477   conform to the purpose of content coding defined in this section.
    44774478</t>
    4478 <t>
    4479    The registry itself is maintained at
    4480    <eref target="http://www.iana.org/assignments/http-parameters"/>.
    4481 </t>
    44824479</section>
    44834480
    44844481<section title="Registrations" anchor="content.coding.registration">
    44854482<t>
    4486    The registration procedure for HTTP Content Codings is now defined
    4487    by <xref target="content.coding.registry"/> of this document.
    4488 </t>
    4489 <t>
    4490    The HTTP Content Codings Registry located at <eref target="http://www.iana.org/assignments/http-parameters"/>
    4491    shall be updated with the registration below:
     4483   The HTTP Content Codings Registry shall be updated with the registrations
     4484   below:
    44924485</t>
    44934486<texttable align="left" suppress-title="true" anchor="iana.content.coding.registration.table">
Note: See TracChangeset for help on using the changeset viewer.