Changeset 327


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

Location:
draft-ietf-httpbis/latest
Files:
6 edited

Legend:

Unmodified
Added
Removed

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

    r326 r327  
    476476         <tr>
    477477            <td class="header left"></td>
    478             <td class="header right">October 2008</td>
     478            <td class="header right">October 1, 2008</td>
    479479         </tr>
    480480      </table>
    … …  
    680680      <p id="rfc.section.1.1.p.1">Practical information systems require more functionality than simple retrieval, including search, front-end update, and annotation.
    681681         HTTP allows an open-ended set of methods and headers that indicate the purpose of a request <a href="#RFC2324" id="rfc.xref.RFC2324.1"><cite title="Hyper Text Coffee Pot Control Protocol (HTCPCP/1.0)">[RFC2324]</cite></a>. It builds on the discipline of reference provided by the Uniform Resource Identifier (URI) <a href="#RFC1630" id="rfc.xref.RFC1630.1"><cite title="Universal Resource Identifiers in WWW: A Unifying Syntax for the Expression of Names and Addresses of Objects on the Network as used in the World-Wide Web">[RFC1630]</cite></a>, as a location (URL) <a href="#RFC1738" id="rfc.xref.RFC1738.1"><cite title="Uniform Resource Locators (URL)">[RFC1738]</cite></a> or name (URN) <a href="#RFC1737" id="rfc.xref.RFC1737.1"><cite title="Functional Requirements for Uniform Resource Names">[RFC1737]</cite></a>, for indicating the resource to which a method is to be applied. Messages are passed in a format similar to that used by
    682          Internet mail <a href="#RFC2822" id="rfc.xref.RFC2822.1"><cite title="Internet Message Format">[RFC2822]</cite></a> as defined by 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>.
     682         Internet mail <a href="#RFC5322" id="rfc.xref.RFC5322.1"><cite title="Internet Message Format">[RFC5322]</cite></a> as defined by 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>.
    683683      </p>
    684684      <p id="rfc.section.1.1.p.2">HTTP is also used as a generic protocol for communication between user agents and proxies/gateways to other Internet systems,
    … …  
    13291329      <p id="rfc.section.4.1.p.1">HTTP messages consist of requests from client to server and responses from server to client.</p>
    13301330      <div id="rfc.figure.u.30"></div><pre class="inline"><span id="rfc.iref.g.63"></span>  <a href="#message.types" class="smpl">HTTP-message</a>   = <a href="#request" class="smpl">Request</a> | <a href="#response" class="smpl">Response</a>     ; HTTP/1.1 messages
    1331 </pre><p id="rfc.section.4.1.p.3">Request (<a href="#request" title="Request">Section&nbsp;5</a>) and Response (<a href="#response" title="Response">Section&nbsp;6</a>) messages use the generic message format of <a href="#RFC2822" id="rfc.xref.RFC2822.2"><cite title="Internet Message Format">[RFC2822]</cite></a> for transferring entities (the payload of the message). Both types of message consist of a start-line, zero or more header
     1331</pre><p id="rfc.section.4.1.p.3">Request (<a href="#request" title="Request">Section&nbsp;5</a>) and Response (<a href="#response" title="Response">Section&nbsp;6</a>) messages use the generic message format of <a href="#RFC5322" id="rfc.xref.RFC5322.2"><cite title="Internet Message Format">[RFC5322]</cite></a> for transferring entities (the payload of the message). Both types of message consist of a start-line, zero or more header
    13321332         fields (also known as "headers"), an empty line (i.e., a line with nothing preceding the CRLF) indicating the end of the header
    13331333         fields, and possibly a message-body.
    … …  
    13451345      </p>
    13461346      <h2 id="rfc.section.4.2"><a href="#rfc.section.4.2">4.2</a>&nbsp;<a id="message.headers" href="#message.headers">Message Headers</a></h2>
    1347       <p id="rfc.section.4.2.p.1">HTTP header fields, which include general-header (<a href="#general.header.fields" title="General Header Fields">Section&nbsp;4.5</a>), request-header (<a href="p2-semantics.html#request.header.fields" title="Request Header Fields">Section 4</a> of <a href="#Part2" id="rfc.xref.Part2.4"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>), response-header (<a href="p2-semantics.html#response.header.fields" title="Response Header Fields">Section 6</a> of <a href="#Part2" id="rfc.xref.Part2.5"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>), and entity-header (<a href="p3-payload.html#entity.header.fields" title="Entity Header Fields">Section 4.1</a> of <a href="#Part3" id="rfc.xref.Part3.11"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>) fields, follow the same generic format as that given in <a href="http://tools.ietf.org/html/rfc2822#section-2.1">Section 2.1</a> of <a href="#RFC2822" id="rfc.xref.RFC2822.3"><cite title="Internet Message Format">[RFC2822]</cite></a>. Each header field consists of a name followed by a colon (":") and the field value. Field names are case-insensitive. The
     1347      <p id="rfc.section.4.2.p.1">HTTP header fields, which include general-header (<a href="#general.header.fields" title="General Header Fields">Section&nbsp;4.5</a>), request-header (<a href="p2-semantics.html#request.header.fields" title="Request Header Fields">Section 4</a> of <a href="#Part2" id="rfc.xref.Part2.4"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>), response-header (<a href="p2-semantics.html#response.header.fields" title="Response Header Fields">Section 6</a> of <a href="#Part2" id="rfc.xref.Part2.5"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>), and entity-header (<a href="p3-payload.html#entity.header.fields" title="Entity Header Fields">Section 4.1</a> of <a href="#Part3" id="rfc.xref.Part3.11"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>) fields, follow the same generic format as that given in <a href="http://tools.ietf.org/html/rfc5322#section-2.1">Section 2.1</a> of <a href="#RFC5322" id="rfc.xref.RFC5322.3"><cite title="Internet Message Format">[RFC5322]</cite></a>. Each header field consists of a name followed by a colon (":") and the field value. Field names are case-insensitive. The
    13481348         field value <em class="bcp14">MAY</em> be preceded by any amount of LWS, though a single SP is preferred. Header fields can be extended over multiple lines by preceding
    13491349         each extra line with at least one SP or HTAB. Applications ought to follow "common form", where one is known or indicated,
    … …  
    18071807      <h2 id="rfc.section.8.3"><a href="#rfc.section.8.3">8.3</a>&nbsp;<a id="header.date" href="#header.date">Date</a></h2>
    18081808      <p id="rfc.section.8.3.p.1">The Date general-header field represents the date and time at which the message was originated, having the same semantics
    1809          as orig-date in <a href="http://tools.ietf.org/html/rfc2822#section-3.6.1">Section 3.6.1</a> of <a href="#RFC2822" id="rfc.xref.RFC2822.4"><cite title="Internet Message Format">[RFC2822]</cite></a>. The field value is an HTTP-date, as described in <a href="#full.date" title="Full Date">Section&nbsp;3.3.1</a>; it <em class="bcp14">MUST</em> be sent in rfc1123-date format.
     1809         as orig-date in <a href="http://tools.ietf.org/html/rfc5322#section-3.6.1">Section 3.6.1</a> of <a href="#RFC5322" id="rfc.xref.RFC5322.4"><cite title="Internet Message Format">[RFC5322]</cite></a>. The field value is an HTTP-date, as described in <a href="#full.date" title="Full Date">Section&nbsp;3.3.1</a>; it <em class="bcp14">MUST</em> be sent in rfc1123-date format.
    18101810      </p>
    18111811      <div id="rfc.figure.u.49"></div><pre class="inline"><span id="rfc.iref.g.85"></span>  <a href="#header.date" class="smpl">Date</a>  = "Date" ":" <a href="#full.date" class="smpl">HTTP-date</a>
    … …  
    19701970      <h2 id="rfc.section.8.9"><a href="#rfc.section.8.9">8.9</a>&nbsp;<a id="header.via" href="#header.via">Via</a></h2>
    19711971      <p id="rfc.section.8.9.p.1">The Via general-header field <em class="bcp14">MUST</em> be used by gateways and proxies to indicate the intermediate protocols and recipients between the user agent and the server
    1972          on requests, and between the origin server and the client on responses. It is analogous to the "Received" field defined in <a href="http://tools.ietf.org/html/rfc2822#section-3.6.7">Section 3.6.7</a> of <a href="#RFC2822" id="rfc.xref.RFC2822.5"><cite title="Internet Message Format">[RFC2822]</cite></a> and is intended to be used for tracking message forwards, avoiding request loops, and identifying the protocol capabilities
     1972         on requests, and between the origin server and the client on responses. It is analogous to the "Received" field defined in <a href="http://tools.ietf.org/html/rfc5322#section-3.6.7">Section 3.6.7</a> of <a href="#RFC5322" id="rfc.xref.RFC5322.5"><cite title="Internet Message Format">[RFC5322]</cite></a> and is intended to be used for tracking message forwards, avoiding request loops, and identifying the protocol capabilities
    19731973         of all senders along the request/response chain.
    19741974      </p>
    … …  
    24672467         </tr>
    24682468         <tr>
    2469             <td class="reference"><b id="RFC2822">[RFC2822]</b></td>
    2470             <td class="top">Resnick, P., “<a href="http://tools.ietf.org/html/rfc2822">Internet Message Format</a>”, RFC&nbsp;2822, April&nbsp;2001.
    2471             </td>
    2472          </tr>
    2473          <tr>
    24742469            <td class="reference"><b id="RFC2965">[RFC2965]</b></td>
    24752470            <td class="top"><a title="Bell Laboratories, Lucent Technologies">Kristol, D. M.</a> and <a title="Epinions.com, Inc.">L. Montulli</a>, “<a href="http://tools.ietf.org/html/rfc2965">HTTP State Management Mechanism</a>”, RFC&nbsp;2965, October&nbsp;2000.
    … …  
    24942489            <td class="reference"><b id="RFC4395">[RFC4395]</b></td>
    24952490            <td class="top"><a title="AT&amp;T Laboratories">Hansen, T.</a>, <a title="Qualcomm, Inc.">Hardie, T.</a>, and <a title="Adobe Systems">L. Masinter</a>, “<a href="http://tools.ietf.org/html/rfc4395">Guidelines and Registration Procedures for New URI Schemes</a>”, BCP&nbsp;115, RFC&nbsp;4395, February&nbsp;2006.
     2491            </td>
     2492         </tr>
     2493         <tr>
     2494            <td class="reference"><b id="RFC5322">[RFC5322]</b></td>
     2495            <td class="top">Resnick, P., “<a href="http://tools.ietf.org/html/rfc5322">Internet Message Format</a>”, RFC&nbsp;5322, October&nbsp;2008.
    24962496            </td>
    24972497         </tr>
    … …  
    27792779      </ul>
    27802780      <h2 id="rfc.section.D.6"><a href="#rfc.section.D.6">D.6</a>&nbsp;<a id="changes.since.04" href="#changes.since.04">Since draft-ietf-httpbis-p1-messaging-04</a></h2>
     2781      <p id="rfc.section.D.6.p.1">Closed issues: </p>
     2782      <ul>
     2783         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/132">http://tools.ietf.org/wg/httpbis/trac/ticket/132</a>&gt;: "RFC 2822 is updated by RFC 5322"
     2784         </li>
     2785      </ul>
    27812786      <h1><a id="rfc.copyright" href="#rfc.copyright">Full Copyright Statement</a></h1>
    27822787      <p>This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the
    … …  
    30603065                  <li class="indline1"><em>RFC2818</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2818.1">3.2.2</a>, <a class="iref" href="#RFC2818"><b>12.2</b></a></li>
    30613066                  <li class="indline1"><em>RFC2821</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2821.1">1.1</a>, <a class="iref" href="#RFC2821"><b>12.2</b></a></li>
    3062                   <li class="indline1"><em>RFC2822</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2822.1">1.1</a>, <a class="iref" href="#rfc.xref.RFC2822.2">4.1</a>, <a class="iref" href="#rfc.xref.RFC2822.3">4.2</a>, <a class="iref" href="#rfc.xref.RFC2822.4">8.3</a>, <a class="iref" href="#rfc.xref.RFC2822.5">8.9</a>, <a class="iref" href="#RFC2822"><b>12.2</b></a><ul class="ind">
    3063                         <li class="indline1"><em>Section 2.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2822.3">4.2</a></li>
    3064                         <li class="indline1"><em>Section 3.6.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2822.4">8.3</a></li>
    3065                         <li class="indline1"><em>Section 3.6.7</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2822.5">8.9</a></li>
    3066                      </ul>
    3067                   </li>
    30683067                  <li class="indline1"><em>RFC2965</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2965.1">4.2</a>, <a class="iref" href="#RFC2965"><b>12.2</b></a></li>
    30693068                  <li class="indline1"><em>RFC3864</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC3864.1">9.1</a>, <a class="iref" href="#RFC3864"><b>12.2</b></a></li>
    … …  
    30713070                  <li class="indline1"><em>RFC4288</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC4288.1">9.3</a>, <a class="iref" href="#RFC4288"><b>12.2</b></a></li>
    30723071                  <li class="indline1"><em>RFC4395</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC4395.1">9.2</a>, <a class="iref" href="#RFC4395"><b>12.2</b></a></li>
     3072                  <li class="indline1"><em>RFC5322</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC5322.1">1.1</a>, <a class="iref" href="#rfc.xref.RFC5322.2">4.1</a>, <a class="iref" href="#rfc.xref.RFC5322.3">4.2</a>, <a class="iref" href="#rfc.xref.RFC5322.4">8.3</a>, <a class="iref" href="#rfc.xref.RFC5322.5">8.9</a>, <a class="iref" href="#RFC5322"><b>12.2</b></a><ul class="ind">
     3073                        <li class="indline1"><em>Section 2.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC5322.3">4.2</a></li>
     3074                        <li class="indline1"><em>Section 3.6.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC5322.4">8.3</a></li>
     3075                        <li class="indline1"><em>Section 3.6.7</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC5322.5">8.9</a></li>
     3076                     </ul>
     3077                  </li>
    30733078                  <li class="indline1"><em>RFC822</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC822.1">3.3.1</a>, <a class="iref" href="#RFC822"><b>12.2</b></a></li>
    30743079                  <li class="indline1"><em>RFC822ABNF</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC822ABNF.1">2.1</a>, <a class="iref" href="#rfc.xref.RFC822ABNF.2">11</a>, <a class="iref" href="#RFC822ABNF"><b>12.1</b></a></li>

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

    r326 r327  
    277277   (URL) <xref target="RFC1738"/> or name (URN) <xref target="RFC1737"/>, for indicating the resource to which a
    278278   method is to be applied. Messages are passed in a format similar to
    279    that used by Internet mail <xref target="RFC2822"/> as defined by the Multipurpose
     279   that used by Internet mail <xref target="RFC5322"/> as defined by the Multipurpose
    280280   Internet Mail Extensions (MIME) <xref target="RFC2045"/>.
    281281</t>
    … …  
    15031503<t>
    15041504   Request (<xref target="request"/>) and Response (<xref target="response"/>) messages use the generic
    1505    message format of <xref target="RFC2822"/> for transferring entities (the payload
     1505   message format of <xref target="RFC5322"/> for transferring entities (the payload
    15061506   of the message). Both types of message consist of a start-line, zero
    15071507   or more header fields (also known as "headers"), an empty line (i.e.,
    … …  
    15391539   request-header (&request-header-fields;), response-header (&response-header-fields;), and
    15401540   entity-header (&entity-header-fields;) fields, follow the same generic format as
    1541    that given in <xref target="RFC2822" x:fmt="of" x:sec="2.1"/>. Each header field consists
     1541   that given in <xref target="RFC5322" x:fmt="of" x:sec="2.1"/>. Each header field consists
    15421542   of a name followed by a colon (":") and the field value. Field names
    15431543   are case-insensitive. The field value &MAY; be preceded by any amount
    … …  
    25212521   The Date general-header field represents the date and time at which
    25222522   the message was originated, having the same semantics as orig-date in
    2523    <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"/>;
     2523   <xref target="RFC5322" x:fmt="of" x:sec="3.6.1"/>. The field value is an
     2524   HTTP-date, as described in <xref target="full.date"/>;
    25242525   it &MUST; be sent in rfc1123-date format.
    25252526</t>
    … …  
    28562857   agent and the server on requests, and between the origin server and
    28572858   the client on responses. It is analogous to the "Received" field defined in
    2858    <xref target="RFC2822" x:fmt="of" x:sec="3.6.7"/> and is intended to be used for tracking message forwards,
     2859   <xref target="RFC5322" x:fmt="of" x:sec="3.6.7"/> and is intended to be used for tracking message forwards,
    28592860   avoiding request loops, and identifying the protocol capabilities of
    28602861   all senders along the request/response chain.
    … …  
    40214022</reference>
    40224023
    4023 <reference anchor="RFC2822">
    4024   <front>
    4025     <title>Internet Message Format</title>
    4026     <author initials="P." surname="Resnick" fullname="P. Resnick">
    4027       <organization>QUALCOMM Incorporated</organization>
    4028     </author>
    4029     <date year="2001" month="April"/>
    4030   </front>
    4031   <seriesInfo name="RFC" value="2822"/>
    4032 </reference>
    4033 
    40344024<reference anchor='RFC2965'>
    40354025  <front>
    … …  
    41274117  <seriesInfo name='BCP' value='115' />
    41284118  <seriesInfo name='RFC' value='4395' />
     4119</reference>
     4120
     4121<reference anchor="RFC5322">
     4122  <front>
     4123    <title>Internet Message Format</title>
     4124    <author initials="P." surname="Resnick" fullname="P. Resnick">
     4125      <organization>Qualcomm Incorporated</organization>
     4126    </author>
     4127    <date year="2008" month="October"/>
     4128  </front>
     4129  <seriesInfo name="RFC" value="5322"/>
    41294130</reference>
    41304131
    … …  
    46994700<section title="Since draft-ietf-httpbis-p1-messaging-04" anchor="changes.since.04">
    47004701<t>
     4702  Closed issues:
     4703  <list style="symbols">
     4704    <t>
     4705      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/132"/>:
     4706      "RFC 2822 is updated by RFC 5322"
     4707    </t>
     4708  </list>
    47014709</t>
    47024710</section>

  • draft-ietf-httpbis/latest/p2-semantics.html

    r326 r327  
    477477         <tr>
    478478            <td class="header left"></td>
    479             <td class="header right">October 2008</td>
     479            <td class="header right">October 1, 2008</td>
    480480         </tr>
    481481      </table>
    … …  
    14951495      <div id="rfc.iref.h.4"></div>
    14961496      <h2 id="rfc.section.10.3"><a href="#rfc.section.10.3">10.3</a>&nbsp;<a id="header.from" href="#header.from">From</a></h2>
    1497       <p id="rfc.section.10.3.p.1">The From request-header field, if given, <em class="bcp14">SHOULD</em> contain an Internet e-mail address for the human user who controls the requesting user agent. The address <em class="bcp14">SHOULD</em> be machine-usable, as defined by "mailbox" in <a href="http://tools.ietf.org/html/rfc2822#section-3.4">Section 3.4</a> of <a href="#RFC2822" id="rfc.xref.RFC2822.1"><cite title="Internet Message Format">[RFC2822]</cite></a>:
     1497      <p id="rfc.section.10.3.p.1">The From request-header field, if given, <em class="bcp14">SHOULD</em> contain an Internet e-mail address for the human user who controls the requesting user agent. The address <em class="bcp14">SHOULD</em> be machine-usable, as defined by "mailbox" in <a href="http://tools.ietf.org/html/rfc5322#section-3.4">Section 3.4</a> of <a href="#RFC5322" id="rfc.xref.RFC5322.1"><cite title="Internet Message Format">[RFC5322]</cite></a>:
    14981498      </p>
    14991499      <div id="rfc.figure.u.16"></div><pre class="inline"><span id="rfc.iref.g.14"></span>  <a href="#header.from" class="smpl">From</a>    = "From" ":" <a href="#header.from" class="smpl">mailbox</a>
    15001500 
    1501   <a href="#header.from" class="smpl">mailbox</a> = &lt;mailbox, defined in <a href="#RFC2822" id="rfc.xref.RFC2822.2"><cite title="Internet Message Format">[RFC2822]</cite></a>, <a href="http://tools.ietf.org/html/rfc2822#section-3.4">Section 3.4</a>&gt;
     1501  <a href="#header.from" class="smpl">mailbox</a> = &lt;mailbox, defined in <a href="#RFC5322" id="rfc.xref.RFC5322.2"><cite title="Internet Message Format">[RFC5322]</cite></a>, <a href="http://tools.ietf.org/html/rfc5322#section-3.4">Section 3.4</a>&gt;
    15021502</pre><p id="rfc.section.10.3.p.3">An example is:</p>
    15031503      <div id="rfc.figure.u.17"></div><pre class="text">    From: webmaster@example.org
    … …  
    21382138         </tr>
    21392139         <tr>
    2140             <td class="reference"><b id="RFC2822">[RFC2822]</b></td>
    2141             <td class="top">Resnick, P., “<a href="http://tools.ietf.org/html/rfc2822">Internet Message Format</a>”, RFC&nbsp;2822, April&nbsp;2001.
    2142             </td>
    2143          </tr>
    2144          <tr>
    21452140            <td class="reference"><b id="RFC3864">[RFC3864]</b></td>
    21462141            <td class="top"><a title="Nine by Nine">Klyne, G.</a>, <a title="BEA Systems">Nottingham, M.</a>, and <a title="HP Labs">J. Mogul</a>, “<a href="http://tools.ietf.org/html/rfc3864">Registration Procedures for Message Header Fields</a>”, BCP&nbsp;90, RFC&nbsp;3864, September&nbsp;2004.
    … …  
    21502145            <td class="reference"><b id="RFC5226">[RFC5226]</b></td>
    21512146            <td class="top"><a title="IBM">Narten, T.</a> and <a title="Google">H. Alvestrand</a>, “<a href="http://tools.ietf.org/html/rfc5226">Guidelines for Writing an IANA Considerations Section in RFCs</a>”, BCP&nbsp;26, RFC&nbsp;5226, May&nbsp;2008.
     2147            </td>
     2148         </tr>
     2149         <tr>
     2150            <td class="reference"><b id="RFC5322">[RFC5322]</b></td>
     2151            <td class="top">Resnick, P., “<a href="http://tools.ietf.org/html/rfc5322">Internet Message Format</a>”, RFC&nbsp;5322, October&nbsp;2008.
    21522152            </td>
    21532153         </tr>
    … …  
    23092309      </ul>
    23102310      <h2 id="rfc.section.B.6"><a href="#rfc.section.B.6">B.6</a>&nbsp;<a id="changes.since.04" href="#changes.since.04">Since draft-ietf-httpbis-p2-semantics-04</a></h2>
     2311      <p id="rfc.section.B.6.p.1">Closed issues: </p>
     2312      <ul>
     2313         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/132">http://tools.ietf.org/wg/httpbis/trac/ticket/132</a>&gt;: "RFC 2822 is updated by RFC 5322"
     2314         </li>
     2315      </ul>
    23112316      <h1><a id="rfc.copyright" href="#rfc.copyright">Full Copyright Statement</a></h1>
    23122317      <p>This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the
    … …  
    25612566                     </ul>
    25622567                  </li>
    2563                   <li class="indline1"><em>RFC2822</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2822.1">10.3</a>, <a class="iref" href="#rfc.xref.RFC2822.2">10.3</a>, <a class="iref" href="#RFC2822"><b>14.2</b></a><ul class="ind">
    2564                         <li class="indline1"><em>Section 3.4</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2822.1">10.3</a>, <a class="iref" href="#rfc.xref.RFC2822.2">10.3</a></li>
    2565                      </ul>
    2566                   </li>
    25672568                  <li class="indline1"><em>RFC3864</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC3864.1">11.3</a>, <a class="iref" href="#RFC3864"><b>14.2</b></a></li>
    25682569                  <li class="indline1"><em>RFC5226</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC5226.1">3.1</a>, <a class="iref" href="#rfc.xref.RFC5226.2">5.1</a>, <a class="iref" href="#RFC5226"><b>14.2</b></a><ul class="ind">
    25692570                        <li class="indline1"><em>Section 4.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC5226.1">3.1</a>, <a class="iref" href="#rfc.xref.RFC5226.2">5.1</a></li>
     2571                     </ul>
     2572                  </li>
     2573                  <li class="indline1"><em>RFC5322</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC5322.1">10.3</a>, <a class="iref" href="#rfc.xref.RFC5322.2">10.3</a>, <a class="iref" href="#RFC5322"><b>14.2</b></a><ul class="ind">
     2574                        <li class="indline1"><em>Section 3.4</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC5322.1">10.3</a>, <a class="iref" href="#rfc.xref.RFC5322.2">10.3</a></li>
    25702575                     </ul>
    25712576                  </li>

  • draft-ietf-httpbis/latest/p2-semantics.xml

    r326 r327  
    18831883   e-mail address for the human user who controls the requesting user
    18841884   agent. The address &SHOULD; be machine-usable, as defined by "mailbox"
    1885    in <xref x:sec="3.4" x:fmt="of" target="RFC2822"/>:
     1885   in <xref x:sec="3.4" x:fmt="of" target="RFC5322"/>:
    18861886</t>
    18871887<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="From"/>
    18881888  <x:ref>From</x:ref>    = "From" ":" <x:ref>mailbox</x:ref>
    18891889 
    1890   <x:ref>mailbox</x:ref> = &lt;mailbox, defined in <xref x:sec="3.4" x:fmt="," target="RFC2822"/>&gt;
     1890  <x:ref>mailbox</x:ref> = &lt;mailbox, defined in <xref x:sec="3.4" x:fmt="," target="RFC5322"/>&gt;
    18911891</artwork></figure>
    18921892<t>
    … …  
    29772977</reference>
    29782978
    2979 <reference anchor="RFC2822">
    2980   <front>
    2981     <title>Internet Message Format</title>
    2982     <author initials="P." surname="Resnick" fullname="P. Resnick">
    2983       <organization>QUALCOMM Incorporated</organization>
    2984     </author>
    2985     <date year="2001" month="April"/>
    2986   </front>
    2987   <seriesInfo name="RFC" value="2822"/>
    2988 </reference>
    2989 
    29902979<reference anchor='RFC3864'>
    29912980  <front>
    … …  
    30243013  <seriesInfo name='BCP' value='26' />
    30253014  <seriesInfo name='RFC' value='5226' />
     3015</reference>
     3016
     3017<reference anchor="RFC5322">
     3018  <front>
     3019    <title>Internet Message Format</title>
     3020    <author initials="P." surname="Resnick" fullname="P. Resnick">
     3021      <organization>Qualcomm Incorporated</organization>
     3022    </author>
     3023    <date year="2008" month="October"/>
     3024  </front>
     3025  <seriesInfo name="RFC" value="5322"/>
    30263026</reference>
    30273027
    … …  
    33053305<section title="Since draft-ietf-httpbis-p2-semantics-04" anchor="changes.since.04">
    33063306<t>
     3307  Closed issues:
     3308  <list style="symbols">
     3309    <t>
     3310      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/132"/>:
     3311      "RFC 2822 is updated by RFC 5322"
     3312    </t>
     3313  </list>
    33073314</t>
    33083315</section>

  • draft-ietf-httpbis/latest/p3-payload.html

    r326 r327  
    484484         <tr>
    485485            <td class="header left"></td>
    486             <td class="header right">October 2008</td>
     486            <td class="header right">October 1, 2008</td>
    487487         </tr>
    488488      </table>
    … …  
    15211521         </tr>
    15221522         <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&nbsp;2822, April&nbsp;2001.
    1525             </td>
    1526          </tr>
    1527          <tr>
    15281523            <td class="reference"><b id="RFC3629">[RFC3629]</b></td>
    15291524            <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&nbsp;3629, STD&nbsp;63, November&nbsp;2003.
    … …  
    15381533            <td class="reference"><b id="RFC4288">[RFC4288]</b></td>
    15391534            <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&nbsp;13, RFC&nbsp;4288, December&nbsp;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&nbsp;5322, October&nbsp;2008.
    15401540            </td>
    15411541         </tr>
    … …  
    15581558            <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>&nbsp;<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>
    15591559      <h1 id="rfc.section.A"><a href="#rfc.section.A">A.</a>&nbsp;<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="#RFC2822" 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 2045
     1560      <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
    15611561         discusses mail, and HTTP has a few features that are different from those described in RFC 2045. These differences were carefully
    15621562         chosen to optimize performance over binary connections, to allow greater freedom in the use of new media types, to make date
    … …  
    17371737      </ul>
    17381738      <h2 id="rfc.section.D.6"><a href="#rfc.section.D.6">D.6</a>&nbsp;<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> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/132">http://tools.ietf.org/wg/httpbis/trac/ticket/132</a>&gt;: "RFC 2822 is updated by RFC 5322"
     1742         </li>
     1743      </ul>
    17391744      <h1><a id="rfc.copyright" href="#rfc.copyright">Full Copyright Statement</a></h1>
    17401745      <p>This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the
    … …  
    19421947                  <li class="indline1"><em>RFC2557</em>&nbsp;&nbsp;<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>
    19431948                  <li class="indline1"><em>RFC2616</em>&nbsp;&nbsp;<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>&nbsp;&nbsp;<a class="iref" href="#RFC2822"><b>10.2</b></a>, <a class="iref" href="#rfc.xref.RFC2822.1">A</a></li>
    19451949                  <li class="indline1"><em>RFC3629</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC3629.1">3.1</a>, <a class="iref" href="#RFC3629"><b>10.2</b></a></li>
    19461950                  <li class="indline1"><em>RFC3864</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC3864.1">7.1</a>, <a class="iref" href="#RFC3864"><b>10.2</b></a></li>
    … …  
    19511955                     </ul>
    19521956                  </li>
     1957                  <li class="indline1"><em>RFC5322</em>&nbsp;&nbsp;<a class="iref" href="#RFC5322"><b>10.2</b></a>, <a class="iref" href="#rfc.xref.RFC5322.1">A</a></li>
    19531958               </ul>
    19541959            </li>

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

    r326 r327  
    22412241</reference>
    22422242
    2243 <reference anchor="RFC2822">
    2244   <front>
    2245     <title>Internet Message Format</title>
    2246     <author initials="P." surname="Resnick" fullname="P. Resnick">
    2247       <organization>QUALCOMM Incorporated</organization>
    2248     </author>
    2249     <date year="2001" month="April"/>
    2250   </front>
    2251   <seriesInfo name="RFC" value="2822"/>
    2252 </reference>
    2253 
    22542243<reference anchor="RFC3629">
    22552244  <front>
    … …  
    23072296</reference>
    23082297
     2298<reference anchor="RFC5322">
     2299  <front>
     2300    <title>Internet Message Format</title>
     2301    <author initials="P." surname="Resnick" fullname="P. Resnick">
     2302      <organization>Qualcomm Incorporated</organization>
     2303    </author>
     2304    <date year="2008" month="October"/>
     2305  </front>
     2306  <seriesInfo name="RFC" value="5322"/>
     2307</reference>
     2308
    23092309<reference anchor='BCP97'>
    23102310  <front>
    … …  
    23332333<section title="Differences Between HTTP Entities and RFC 2045 Entities" anchor="differences.between.http.entities.and.rfc.2045.entities">
    23342334<t>
    2335    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
     2335   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
    23362336   allow entities to be transmitted in an open variety of
    23372337   representations and with extensible mechanisms. However, RFC 2045
    … …  
    27062706<section title="Since draft-ietf-httpbis-p3-payload-04" anchor="changes.since.04">
    27072707<t>
     2708  Closed issues:
     2709  <list style="symbols">
     2710    <t>
     2711      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/132"/>:
     2712      "RFC 2822 is updated by RFC 5322"
     2713    </t>
     2714  </list>
    27082715</t>
    27092716 </section>
Note: See TracChangeset for help on using the changeset viewer.