Ticket #132: i132.diff

File i132.diff, 8.9 KB (added by julian.reschke@…, 15 years ago)

Proposed changes for P1, P2 and P3

  • p1-messaging.xml

     
    276276   provided by the Uniform Resource Identifier (URI) <xref target="RFC1630"/>, as a location
    277277   (URL) <xref target="RFC1738"/> or name (URN) <xref target="RFC1737"/>, for indicating the resource to which a
    278278   method is to be applied. Messages are passed in a format similar to
    279    that used by Internet mail <xref target="RFC2822"/> as defined by the Multipurpose
     279   that used by Internet mail <xref target="RFC5322"/> as defined by the Multipurpose
    280280   Internet Mail Extensions (MIME) <xref target="RFC2045"/>.
    281281</t>
    282282<t>
    … …  
    15021502</artwork></figure>
    15031503<t>
    15041504   Request (<xref target="request"/>) and Response (<xref target="response"/>) messages use the generic
    1505    message format of <xref target="RFC2822"/> for transferring entities (the payload
     1505   message format of <xref target="RFC5322"/> for transferring entities (the payload
    15061506   of the message). Both types of message consist of a start-line, zero
    15071507   or more header fields (also known as "headers"), an empty line (i.e.,
    15081508   a line with nothing preceding the CRLF) indicating the end of the
    … …  
    15381538   HTTP header fields, which include general-header (<xref target="general.header.fields"/>),
    15391539   request-header (&request-header-fields;), response-header (&response-header-fields;), and
    15401540   entity-header (&entity-header-fields;) fields, follow the same generic format as
    1541    that given in <xref target="RFC2822" x:fmt="of" x:sec="2.1"/>. Each header field consists
     1541   that given in <xref target="RFC5322" x:fmt="of" x:sec="2.1"/>. Each header field consists
    15421542   of a name followed by a colon (":") and the field value. Field names
    15431543   are case-insensitive. The field value &MAY; be preceded by any amount
    15441544   of LWS, though a single SP is preferred. Header fields can be
    … …  
    25202520<t>
    25212521   The Date general-header field represents the date and time at which
    25222522   the message was originated, having the same semantics as orig-date in
    2523    <xref target="RFC2822" x:fmt="of" x:sec="3.6.1"/>. The field value is an HTTP-date, as described in <xref target="full.date"/>;
     2523   <xref target="RFC5322" x:fmt="of" x:sec="3.6.1"/>. The field value is an
     2524   HTTP-date, as described in <xref target="full.date"/>;
    25242525   it &MUST; be sent in rfc1123-date format.
    25252526</t>
    25262527<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Date"/>
    … …  
    28552856   indicate the intermediate protocols and recipients between the user
    28562857   agent and the server on requests, and between the origin server and
    28572858   the client on responses. It is analogous to the "Received" field defined in
    2858    <xref target="RFC2822" x:fmt="of" x:sec="3.6.7"/> and is intended to be used for tracking message forwards,
     2859   <xref target="RFC5322" x:fmt="of" x:sec="3.6.7"/> and is intended to be used for tracking message forwards,
    28592860   avoiding request loops, and identifying the protocol capabilities of
    28602861   all senders along the request/response chain.
    28612862</t>
    … …  
    40204021  <seriesInfo name="RFC" value="2821"/>
    40214022</reference>
    40224023
    4023 <reference anchor="RFC2822">
    4024   <front>
    4025     <title>Internet Message Format</title>
    4026     <author initials="P." surname="Resnick" fullname="P. Resnick">
    4027       <organization>QUALCOMM Incorporated</organization>
    4028     </author>
    4029     <date year="2001" month="April"/>
    4030   </front>
    4031   <seriesInfo name="RFC" value="2822"/>
    4032 </reference>
    4033 
    40344024<reference anchor='RFC2965'>
    40354025  <front>
    40364026    <title>HTTP State Management Mechanism</title>
    … …  
    41284118  <seriesInfo name='RFC' value='4395' />
    41294119</reference>
    41304120
     4121<reference anchor="RFC5322">
     4122  <front>
     4123    <title>Internet Message Format</title>
     4124    <author initials="P." surname="Resnick" fullname="P. Resnick">
     4125      <organization>Qualcomm Incorporated</organization>
     4126    </author>
     4127    <date year="2008" month="September"/>
     4128  </front>
     4129  <seriesInfo name="RFC" value="5322"/>
     4130</reference>
     4131
    41314132<reference anchor="Kri2001" target="http://arxiv.org/abs/cs.SE/0105018">
    41324133  <front>
    41334134    <title>HTTP Cookies: Standards, Privacy, and Politics</title>
    … …  
    46984699
    46994700<section title="Since draft-ietf-httpbis-p1-messaging-04" anchor="changes.since.04">
    47004701<t>
     4702  Closed issues:
     4703  <list style="symbols">
     4704    <t>
     4705      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/132"/>:
     4706      "RFC 2822 is updated by RFC 5322"
     4707    </t>
     4708  </list>
    47014709</t>
    47024710</section>
    47034711

  • p2-semantics.xml

     
    18821882   The From request-header field, if given, &SHOULD; contain an Internet
    18831883   e-mail address for the human user who controls the requesting user
    18841884   agent. The address &SHOULD; be machine-usable, as defined by "mailbox"
    1885    in <xref x:sec="3.4" x:fmt="of" target="RFC2822"/>:
     1885   in <xref x:sec="3.4" x:fmt="of" target="RFC5322"/>:
    18861886</t>
    18871887<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="From"/>
    18881888  <x:ref>From</x:ref>    = "From" ":" <x:ref>mailbox</x:ref>
    18891889 
    1890   <x:ref>mailbox</x:ref> = &lt;mailbox, defined in <xref x:sec="3.4" x:fmt="," target="RFC2822"/>&gt;
     1890  <x:ref>mailbox</x:ref> = &lt;mailbox, defined in <xref x:sec="3.4" x:fmt="," target="RFC5322"/>&gt;
    18911891</artwork></figure>
    18921892<t>
    18931893   An example is:
    … …  
    29762976  <seriesInfo name='RFC' value='2817' />
    29772977</reference>
    29782978
    2979 <reference anchor="RFC2822">
    2980   <front>
    2981     <title>Internet Message Format</title>
    2982     <author initials="P." surname="Resnick" fullname="P. Resnick">
    2983       <organization>QUALCOMM Incorporated</organization>
    2984     </author>
    2985     <date year="2001" month="April"/>
    2986   </front>
    2987   <seriesInfo name="RFC" value="2822"/>
    2988 </reference>
    2989 
    29902979<reference anchor='RFC3864'>
    29912980  <front>
    29922981    <title>Registration Procedures for Message Header Fields</title>
    … …  
    30253014  <seriesInfo name='RFC' value='5226' />
    30263015</reference>
    30273016
     3017<reference anchor="RFC5322">
     3018  <front>
     3019    <title>Internet Message Format</title>
     3020    <author initials="P." surname="Resnick" fullname="P. Resnick">
     3021      <organization>Qualcomm Incorporated</organization>
     3022    </author>
     3023    <date year="2008" month="September"/>
     3024  </front>
     3025  <seriesInfo name="RFC" value="5322"/>
     3026</reference>
     3027
    30283028</references>
    30293029
    30303030<section title="Compatibility with Previous Versions" anchor="compatibility">
    … …  
    33043304
    33053305<section title="Since draft-ietf-httpbis-p2-semantics-04" anchor="changes.since.04">
    33063306<t>
     3307  Closed issues:
     3308  <list style="symbols">
     3309    <t>
     3310      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/132"/>:
     3311      "RFC 2822 is updated by RFC 5322"
     3312    </t>
     3313  </list>
    33073314</t>
    33083315</section>
    33093316

  • p3-payload.xml

     
    22402240  <seriesInfo name="RFC" value="2616"/>
    22412241</reference>
    22422242
    2243 <reference anchor="RFC2822">
    2244   <front>
    2245     <title>Internet Message Format</title>
    2246     <author initials="P." surname="Resnick" fullname="P. Resnick">
    2247       <organization>QUALCOMM Incorporated</organization>
    2248     </author>
    2249     <date year="2001" month="April"/>
    2250   </front>
    2251   <seriesInfo name="RFC" value="2822"/>
    2252 </reference>
    2253 
    22542243<reference anchor="RFC3629">
    22552244  <front>
    22562245    <title>UTF-8, a transformation format of ISO 10646</title>
    … …  
    23062295  <seriesInfo name="RFC" value="4288"/>
    23072296</reference>
    23082297
     2298<reference anchor="RFC5322">
     2299  <front>
     2300    <title>Internet Message Format</title>
     2301    <author initials="P." surname="Resnick" fullname="P. Resnick">
     2302      <organization>Qualcomm Incorporated</organization>
     2303    </author>
     2304    <date year="2008" month="September"/>
     2305  </front>
     2306  <seriesInfo name="RFC" value="5322"/>
     2307</reference>
     2308
    23092309<reference anchor='BCP97'>
    23102310  <front>
    23112311    <title>Handling Normative References to Standards-Track Documents</title>
    … …  
    23322332
    23332333<section title="Differences Between HTTP Entities and RFC 2045 Entities" anchor="differences.between.http.entities.and.rfc.2045.entities">
    23342334<t>
    2335    HTTP/1.1 uses many of the constructs defined for Internet Mail (<xref target="RFC2822"/>) and the Multipurpose Internet Mail Extensions (MIME <xref target="RFC2045"/>) to
     2335   HTTP/1.1 uses many of the constructs defined for Internet Mail (<xref target="RFC5322"/>) and the Multipurpose Internet Mail Extensions (MIME <xref target="RFC2045"/>) to
    23362336   allow entities to be transmitted in an open variety of
    23372337   representations and with extensible mechanisms. However, RFC 2045
    23382338   discusses mail, and HTTP has a few features that are different from
    … …  
    27052705
    27062706<section title="Since draft-ietf-httpbis-p3-payload-04" anchor="changes.since.04">
    27072707<t>
     2708  Closed issues:
     2709  <list style="symbols">
     2710    <t>
     2711      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/132"/>:
     2712      "RFC 2822 is updated by RFC 5322"
     2713    </t>
     2714  </list>
    27082715</t>
    27092716 </section>
    27102717