Changeset 327 for draft-ietf-httpbis/latest/p3-payload.html
- Timestamp:
- 01/10/08 11:38:10 (14 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p3-payload.html
r326 r327 484 484 <tr> 485 485 <td class="header left"></td> 486 <td class="header right">October 2008</td>486 <td class="header right">October 1, 2008</td> 487 487 </tr> 488 488 </table> … … 1521 1521 </tr> 1522 1522 <tr> 1523 <td class="reference"><b id="RFC2822">[RFC2822]</b></td>1524 <td class="top">Resnick, P., “<a href="http://tools.ietf.org/html/rfc2822">Internet Message Format</a>”, RFC 2822, April 2001.1525 </td>1526 </tr>1527 <tr>1528 1523 <td class="reference"><b id="RFC3629">[RFC3629]</b></td> 1529 1524 <td class="top"><a title="Alis Technologies">Yergeau, F.</a>, “<a href="http://tools.ietf.org/html/rfc3629">UTF-8, a transformation format of ISO 10646</a>”, RFC 3629, STD 63, November 2003. … … 1538 1533 <td class="reference"><b id="RFC4288">[RFC4288]</b></td> 1539 1534 <td class="top"><a title="Sun Microsystems">Freed, N.</a> and <a>J. Klensin</a>, “<a href="http://tools.ietf.org/html/rfc4288">Media Type Specifications and Registration Procedures</a>”, BCP 13, RFC 4288, December 2005. 1535 </td> 1536 </tr> 1537 <tr> 1538 <td class="reference"><b id="RFC5322">[RFC5322]</b></td> 1539 <td class="top">Resnick, P., “<a href="http://tools.ietf.org/html/rfc5322">Internet Message Format</a>”, RFC 5322, October 2008. 1540 1540 </td> 1541 1541 </tr> … … 1558 1558 <span class="n hidden"><span class="family-name">Reschke</span><span class="given-name">Julian F.</span></span></span><span class="org vcardline">greenbytes GmbH</span><span class="adr"><span class="street-address vcardline">Hafenweg 16</span><span class="vcardline"><span class="locality">Muenster</span>, <span class="region">NW</span> <span class="postal-code">48155</span></span><span class="country-name vcardline">Germany</span></span><span class="vcardline tel">Phone: <a href="tel:+492512807760"><span class="value">+49 251 2807760</span></a></span><span class="vcardline tel"><span class="type">Fax</span>: <a href="fax:+492512807761"><span class="value">+49 251 2807761</span></a></span><span class="vcardline">EMail: <a><span class="email">julian.reschke@greenbytes.de</span></a></span><span class="vcardline">URI: <a href="http://greenbytes.de/tech/webdav/" class="url">http://greenbytes.de/tech/webdav/</a></span></address> 1559 1559 <h1 id="rfc.section.A"><a href="#rfc.section.A">A.</a> <a id="differences.between.http.entities.and.rfc.2045.entities" href="#differences.between.http.entities.and.rfc.2045.entities">Differences Between HTTP Entities and RFC 2045 Entities</a></h1> 1560 <p id="rfc.section.A.p.1">HTTP/1.1 uses many of the constructs defined for Internet Mail (<a href="#RFC 2822" id="rfc.xref.RFC2822.1"><cite title="Internet Message Format">[RFC2822]</cite></a>) and the Multipurpose Internet Mail Extensions (MIME <a href="#RFC2045" id="rfc.xref.RFC2045.1"><cite title="Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies">[RFC2045]</cite></a>) to allow entities to be transmitted in an open variety of representations and with extensible mechanisms. However, RFC 20451560 <p id="rfc.section.A.p.1">HTTP/1.1 uses many of the constructs defined for Internet Mail (<a href="#RFC5322" id="rfc.xref.RFC5322.1"><cite title="Internet Message Format">[RFC5322]</cite></a>) and the Multipurpose Internet Mail Extensions (MIME <a href="#RFC2045" id="rfc.xref.RFC2045.1"><cite title="Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies">[RFC2045]</cite></a>) to allow entities to be transmitted in an open variety of representations and with extensible mechanisms. However, RFC 2045 1561 1561 discusses mail, and HTTP has a few features that are different from those described in RFC 2045. These differences were carefully 1562 1562 chosen to optimize performance over binary connections, to allow greater freedom in the use of new media types, to make date … … 1737 1737 </ul> 1738 1738 <h2 id="rfc.section.D.6"><a href="#rfc.section.D.6">D.6</a> <a id="changes.since.04" href="#changes.since.04">Since draft-ietf-httpbis-p3-payload-04</a></h2> 1739 <p id="rfc.section.D.6.p.1">Closed issues: </p> 1740 <ul> 1741 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/132">http://tools.ietf.org/wg/httpbis/trac/ticket/132</a>>: "RFC 2822 is updated by RFC 5322" 1742 </li> 1743 </ul> 1739 1744 <h1><a id="rfc.copyright" href="#rfc.copyright">Full Copyright Statement</a></h1> 1740 1745 <p>This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the … … 1942 1947 <li class="indline1"><em>RFC2557</em> <a class="iref" href="#RFC2557"><b>10.2</b></a>, <a class="iref" href="#rfc.xref.RFC2557.1">A.6</a>, <a class="iref" href="#rfc.xref.RFC2557.2">C.1</a></li> 1943 1948 <li class="indline1"><em>RFC2616</em> <a class="iref" href="#rfc.xref.RFC2616.1">1</a>, <a class="iref" href="#RFC2616"><b>10.2</b></a>, <a class="iref" href="#rfc.xref.RFC2616.2">D.1</a></li> 1944 <li class="indline1"><em>RFC2822</em> <a class="iref" href="#RFC2822"><b>10.2</b></a>, <a class="iref" href="#rfc.xref.RFC2822.1">A</a></li>1945 1949 <li class="indline1"><em>RFC3629</em> <a class="iref" href="#rfc.xref.RFC3629.1">3.1</a>, <a class="iref" href="#RFC3629"><b>10.2</b></a></li> 1946 1950 <li class="indline1"><em>RFC3864</em> <a class="iref" href="#rfc.xref.RFC3864.1">7.1</a>, <a class="iref" href="#RFC3864"><b>10.2</b></a></li> … … 1951 1955 </ul> 1952 1956 </li> 1957 <li class="indline1"><em>RFC5322</em> <a class="iref" href="#RFC5322"><b>10.2</b></a>, <a class="iref" href="#rfc.xref.RFC5322.1">A</a></li> 1953 1958 </ul> 1954 1959 </li>
Note: See TracChangeset
for help on using the changeset viewer.