Jan 1, 2008, 8:07:37 AM (12 years ago)

Upgrade from RFC822 to RFC2822 where possible, leading to an interim state where we cite RFC822 (date format), RFC822ABNF (to be replaced by RFC5234 - see issue #36), and RFC2822 (addresses #65).

1 edited


  • draft-ietf-httpbis/latest/p1-messaging.xml

    r132 r133  
    257257   (URL) <xref target="RFC1738"/> or name (URN) <xref target="RFC1737"/>, for indicating the resource to which a
    258258   method is to be applied. Messages are passed in a format similar to
    259    that used by Internet mail <xref target="RFC822"/> as defined by the Multipurpose
     259   that used by Internet mail <xref target="RFC2822"/> as defined by the Multipurpose
    260260   Internet Mail Extensions (MIME) <xref target="RFC2045"/>.
    13151315   Request (<xref target="request"/>) and Response (<xref target="response"/>) messages use the generic
    1316    message format of <xref target="RFC822"/> for transferring entities (the payload
     1316   message format of <xref target="RFC2822"/> for transferring entities (the payload
    13171317   of the message). Both types of message consist of a start-line, zero
    13181318   or more header fields (also known as "headers"), an empty line (i.e.,
    13461346   request-header (&request-header-fields;), response-header (&response-header-fields;), and
    13471347   entity-header (&entity-header-fields;) fields, follow the same generic format as
    1348    that given in <xref target="RFC822" x:fmt="of" x:sec="3.1"/>. Each header field consists
     1348   that given in <xref target="RFC2822" x:fmt="of" x:sec="2.1"/>. Each header field consists
    13491349   of a name followed by a colon (":") and the field value. Field names
    13501350   are case-insensitive. The field value &MAY; be preceded by any amount
    26172617   agent and the server on requests, and between the origin server and
    26182618   the client on responses. It is analogous to the "Received" field of
    2619    <xref target="RFC822"/> and is intended to be used for tracking message forwards,
     2619   <xref target="RFC2822"/> and is intended to be used for tracking message forwards,
    26202620   avoiding request loops, and identifying the protocol capabilities of
    26212621   all senders along the request/response chain.
    28522852   This specification makes heavy use of the augmented BNF and generic
    2853    constructs defined by David H. Crocker for <xref target="RFC822"/>. Similarly, it
     2853   constructs defined by David H. Crocker for <xref target="RFC822ABNF"/>. Similarly, it
    28542854   reuses many of the definitions provided by Nathaniel Borenstein and
    28552855   Ned Freed for MIME <xref target="RFC2045"/>. We hope that their inclusion in this
    34663466  </front>
    34673467  <seriesInfo name="RFC" value="2821"/>
     3470<reference anchor="RFC2822">
     3471  <front>
     3472    <title>Internet Message Format</title>
     3473    <author initials="P." surname="Resnick" fullname="P. Resnick">
     3474      <organization>QUALCOMM Incorporated</organization>
     3475    </author>
     3476    <date year="2001" month="April"/>
     3477  </front>
     3478  <seriesInfo name="RFC" value="2822"/>
Note: See TracChangeset for help on using the changeset viewer.