Ignore:
Timestamp:
Mar 30, 2012, 7:38:53 AM (8 years ago)
Author:
julian.reschke@…
Message:

Step 2 of p2/p3-merge (see #351)

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p3-payload.xml

    r1639 r1640  
    117117<abstract>
    118118<t>
    119    The Hypertext Transfer Protocol (HTTP) is an application-level protocol for
    120    distributed, collaborative, hypertext information systems. HTTP has been in
    121    use by the World Wide Web global information initiative since 1990. This
    122    document is Part 3 of the seven-part specification that defines the protocol
    123    referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616.
    124 </t>
    125 <t>
    126    Part 3 defines HTTP message content, metadata, and content negotiation.
     119  This part is now obsolete. Please see HTTPbis, Part 2.
    127120</t>
    128121</abstract>
    129 
    130 <note title="Editorial Note (To be removed by RFC Editor)">
    131   <t>
    132     Discussion of this draft should take place on the HTTPBIS working group
    133     mailing list (ietf-http-wg@w3.org), which is archived at
    134     <eref target="http://lists.w3.org/Archives/Public/ietf-http-wg/"/>.
    135   </t>
    136   <t>
    137     The current issues list is at
    138     <eref target="http://tools.ietf.org/wg/httpbis/trac/report/3"/> and related
    139     documents (including fancy diffs) can be found at
    140     <eref target="http://tools.ietf.org/wg/httpbis/"/>.
    141   </t>
    142   <t>
    143     The changes in this draft are summarized in <xref target="changes.since.19"/>.
    144   </t>
    145 </note>
    146122</front>
    147123<middle>
    148124<section title="Introduction" anchor="introduction">
    149125<t>
    150    This document defines HTTP/1.1 message payloads (a.k.a., content), the
    151    associated metadata header fields that define how the payload is intended
    152    to be interpreted by a recipient, the request header fields that
    153    might influence content selection, and the various selection algorithms
    154    that are collectively referred to as HTTP content negotiation.
    155 </t>
    156 <t>
    157    This document is currently disorganized in order to minimize the changes
    158    between drafts and enable reviewers to see the smaller errata changes.
    159    A future draft will reorganize the sections to better reflect the content.
    160    In particular, the sections on entities will be renamed payload and moved
    161    to the first half of the document, while the sections on content negotiation
    162    and associated request header fields will be moved to the second half.  The
    163    current mess reflects how widely dispersed these topics and associated
    164    requirements had become in <xref target="RFC2616"/>.
     126  This part is now obsolete. Please see HTTPbis, Part 2.
    165127</t>
    166128
Note: See TracChangeset for help on using the changeset viewer.