Changeset 327 for draft-ietf-httpbis/latest/p3-payload.xml

Timestamp:

Oct 1, 2008, 4:38:10 AM (11 years ago)

Author:

julian.reschke@…

Message:

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

File:

• draft-ietf-httpbis/latest/p3-payload.xml (modified) (4 diffs)

draft-ietf-httpbis/latest/p3-payload.xml

@@ -2241 +2241 @@
 </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="RFC3629">
   <front>
@@ -2307 +2296 @@
 </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>
+
 <reference anchor='BCP97'>
   <front>
@@ -2333 +2333 @@
 <section title="Differences Between HTTP Entities and RFC 2045 Entities" anchor="differences.between.http.entities.and.rfc.2045.entities">
 <t>
-   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
+   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
    allow entities to be transmitted in an open variety of
    representations and with extensible mechanisms. However, RFC 2045
@@ -2706 +2706 @@
 <section title="Since draft-ietf-httpbis-p3-payload-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>