Changeset 133 for draft-ietf-httpbis/latest/p1-messaging.xml

Timestamp:

01/01/08 16:07:37 (13 years ago)

Author:

julian.reschke@…

Message:

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).

File:

• draft-ietf-httpbis/latest/p1-messaging.xml (modified) (6 diffs)

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

@@ -257 +257 @@
    (URL) <xref target="RFC1738"/> or name (URN) <xref target="RFC1737"/>, for indicating the resource to which a
    method is to be applied. Messages are passed in a format similar to
-   that used by Internet mail <xref target="RFC822"/> as defined by the Multipurpose
+   that used by Internet mail <xref target="RFC2822"/> as defined by the Multipurpose
    Internet Mail Extensions (MIME) <xref target="RFC2045"/>.
 </t>
@@ -1314 +1314 @@
 <t>
    Request (<xref target="request"/>) and Response (<xref target="response"/>) messages use the generic
-   message format of <xref target="RFC822"/> for transferring entities (the payload
+   message format of <xref target="RFC2822"/> for transferring entities (the payload
    of the message). Both types of message consist of a start-line, zero
    or more header fields (also known as "headers"), an empty line (i.e.,
@@ -1346 +1346 @@
    request-header (&request-header-fields;), response-header (&response-header-fields;), and
    entity-header (&entity-header-fields;) fields, follow the same generic format as
-   that given in <xref target="RFC822" x:fmt="of" x:sec="3.1"/>. Each header field consists
+   that given in <xref target="RFC2822" x:fmt="of" x:sec="2.1"/>. Each header field consists
    of a name followed by a colon (":") and the field value. Field names
    are case-insensitive. The field value &MAY; be preceded by any amount
@@ -2617 +2617 @@
    agent and the server on requests, and between the origin server and
    the client on responses. It is analogous to the "Received" field of
-   <xref target="RFC822"/> and is intended to be used for tracking message forwards,
+   <xref target="RFC2822"/> and is intended to be used for tracking message forwards,
    avoiding request loops, and identifying the protocol capabilities of
    all senders along the request/response chain.
@@ -2851 +2851 @@
 <t>
    This specification makes heavy use of the augmented BNF and generic
-   constructs defined by David H. Crocker for <xref target="RFC822"/>. Similarly, it
+   constructs defined by David H. Crocker for <xref target="RFC822ABNF"/>. Similarly, it
    reuses many of the definitions provided by Nathaniel Borenstein and
    Ned Freed for MIME <xref target="RFC2045"/>. We hope that their inclusion in this
@@ -3466 +3466 @@
   </front>
   <seriesInfo name="RFC" value="2821"/>
+</reference>
+
+<reference anchor="RFC2822">
+  <front>
+    <title>Internet Message Format</title>
+    <author initials="P." surname="Resnick" fullname="P. Resnick">
+      <organization>QUALCOMM Incorporated</organization>
+    </author>
+    <date year="2001" month="April"/>
+  </front> 
+  <seriesInfo name="RFC" value="2822"/>
 </reference>