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

Timestamp:

01/10/08 11:38:10 (14 years ago)

Author:

julian.reschke@…

Message:

Resolve #32: RFC 2822 was obsoleted by RFC 5322 (closes #132).

File:

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

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

@@ -277 +277 @@
    (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="RFC2822"/> as defined by the Multipurpose
+   that used by Internet mail <xref target="RFC5322"/> as defined by the Multipurpose
    Internet Mail Extensions (MIME) <xref target="RFC2045"/>.
 </t>
@@ -1503 +1503 @@
 <t>
    Request (<xref target="request"/>) and Response (<xref target="response"/>) messages use the generic
-   message format of <xref target="RFC2822"/> for transferring entities (the payload
+   message format of <xref target="RFC5322"/> 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.,
@@ -1539 +1539 @@
    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="RFC2822" x:fmt="of" x:sec="2.1"/>. Each header field consists
+   that given in <xref target="RFC5322" 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
@@ -2521 +2521 @@
    The Date general-header field represents the date and time at which
    the message was originated, having the same semantics as orig-date in
-   <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"/>;
+   <xref target="RFC5322" x:fmt="of" x:sec="3.6.1"/>. The field value is an
+   HTTP-date, as described in <xref target="full.date"/>;
    it &MUST; be sent in rfc1123-date format.
 </t>
@@ -2856 +2857 @@
    agent and the server on requests, and between the origin server and
    the client on responses. It is analogous to the "Received" field defined in
-   <xref target="RFC2822" x:fmt="of" x:sec="3.6.7"/> and is intended to be used for tracking message forwards,
+   <xref target="RFC5322" x:fmt="of" x:sec="3.6.7"/> 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.
@@ -4021 +4022 @@
 </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>
-
 <reference anchor='RFC2965'>
   <front>
@@ -4127 +4117 @@
   <seriesInfo name='BCP' value='115' />
   <seriesInfo name='RFC' value='4395' />
+</reference>
+
+<reference anchor="RFC5322">
+  <front>
+    <title>Internet Message Format</title>
+    <author initials="P." surname="Resnick" fullname="P. Resnick">
+      <organization>Qualcomm Incorporated</organization>
+    </author>
+    <date year="2008" month="October"/>
+  </front> 
+  <seriesInfo name="RFC" value="5322"/>
 </reference>
 
@@ -4699 +4700 @@
 <section title="Since draft-ietf-httpbis-p1-messaging-04" anchor="changes.since.04">
 <t>
+  Closed issues:
+  <list style="symbols"> 
+    <t>
+      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/132"/>:
+      "RFC 2822 is updated by RFC 5322"
+    </t>
+  </list>
 </t>
 </section>