Changeset 384 for draft-ietf-httpbis


Ignore:
Timestamp:
Nov 14, 2008, 12:09:02 PM (11 years ago)
Author:
julian.reschke@…
Message:

Resolve #134: remove unneeded reference to RFC 822 (closes #134)

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

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p1-messaging.html

    r382 r384  
    933933      <h3 id="rfc.section.3.3.1"><a href="#rfc.section.3.3.1">3.3.1</a>&nbsp;<a id="full.date" href="#full.date">Full Date</a></h3>
    934934      <p id="rfc.section.3.3.1.p.1">HTTP applications have historically allowed three different formats for the representation of date/time stamps:</p>
    935       <div id="rfc.figure.u.19"></div><pre class="text">   Sun, 06 Nov 1994 08:49:37 GMT  ; RFC 822, updated by RFC 1123
     935      <div id="rfc.figure.u.19"></div><pre class="text">   Sun, 06 Nov 1994 08:49:37 GMT  ; RFC 1123
    936936   Sunday, 06-Nov-94 08:49:37 GMT ; obsolete RFC 850 format
    937937   Sun Nov  6 08:49:37 1994       ; ANSI C's asctime() format
    938 </pre><p id="rfc.section.3.3.1.p.3">The first format is preferred as an Internet standard and represents a fixed-length subset of that defined by <a href="#RFC1123" id="rfc.xref.RFC1123.1"><cite title="Requirements for Internet Hosts - Application and Support">[RFC1123]</cite></a> (an update to <a href="#RFC822" id="rfc.xref.RFC822.1"><cite title="Standard for the format of ARPA Internet text messages">[RFC822]</cite></a>). The other formats are described here only for compatibility with obsolete implementations. HTTP/1.1 clients and servers
     938</pre><p id="rfc.section.3.3.1.p.3">The first format is preferred as an Internet standard and represents a fixed-length subset of that defined by <a href="#RFC1123" id="rfc.xref.RFC1123.1"><cite title="Requirements for Internet Hosts - Application and Support">[RFC1123]</cite></a>. The other formats are described here only for compatibility with obsolete implementations. HTTP/1.1 clients and servers
    939939         that parse the date value <em class="bcp14">MUST</em> accept all three formats (for compatibility with HTTP/1.0), though they <em class="bcp14">MUST</em> only generate the RFC 1123 format for representing HTTP-date values in header fields. See <a href="#tolerant.applications" title="Tolerant Applications">Appendix&nbsp;A</a> for further information.
    940940      </p>
     
    21582158      <h2 id="rfc.references.2"><a href="#rfc.section.12.2" id="rfc.section.12.2">12.2</a> Informative References
    21592159      </h2>
    2160       <table summary="Informative References">                                               
     2160      <table summary="Informative References">                                             
    21612161         <tr>
    21622162            <td class="reference"><b id="Kri2001">[Kri2001]</b></td>
     
    22532253            <td class="reference"><b id="RFC5322">[RFC5322]</b></td>
    22542254            <td class="top">Resnick, P., “<a href="http://tools.ietf.org/html/rfc5322">Internet Message Format</a>”, RFC&nbsp;5322, October&nbsp;2008.
    2255             </td>
    2256          </tr>
    2257          <tr>
    2258             <td class="reference"><b id="RFC822">[RFC822]</b></td>
    2259             <td class="top"><a title="University of Delaware, Dept. of Electrical Engineering">Crocker, D.H.</a>, “<a href="http://tools.ietf.org/html/rfc822">Standard for the format of ARPA Internet text messages</a>”, STD&nbsp;11, RFC&nbsp;822, August&nbsp;1982.
    22602255            </td>
    22612256         </tr>
     
    27062701      </ul>
    27072702      <h2 id="rfc.section.E.7"><a href="#rfc.section.E.7">E.7</a>&nbsp;<a id="changes.since.05" href="#changes.since.05">Since draft-ietf-httpbis-p1-messaging-05</a></h2>
     2703      <p id="rfc.section.E.7.p.1">Closed issues: </p>
     2704      <ul>
     2705         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/134">http://tools.ietf.org/wg/httpbis/trac/ticket/134</a>&gt;: "RFC822 reference left in discussion of date formats"
     2706         </li>
     2707      </ul>
    27082708      <h1><a id="rfc.copyright" href="#rfc.copyright">Full Copyright Statement</a></h1>
    27092709      <p>This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the
     
    29972997                     </ul>
    29982998                  </li>
    2999                   <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>
    30002999                  <li class="indline1"><em>RFC959</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC959.1">1</a>, <a class="iref" href="#RFC959"><b>12.2</b></a></li>
    30013000               </ul>
  • draft-ietf-httpbis/latest/p1-messaging.xml

    r382 r384  
    814814</t>
    815815<figure><artwork type="example">
    816    Sun, 06 Nov 1994 08:49:37 GMT  ; RFC 822, updated by RFC 1123
     816   Sun, 06 Nov 1994 08:49:37 GMT  ; RFC 1123
    817817   Sunday, 06-Nov-94 08:49:37 GMT ; obsolete RFC 850 format
    818818   Sun Nov  6 08:49:37 1994       ; ANSI C's asctime() format
     
    820820<t>
    821821   The first format is preferred as an Internet standard and represents
    822    a fixed-length subset of that defined by <xref target="RFC1123"/> (an update to
    823    <xref target="RFC822"/>). The other formats are described here only for
     822   a fixed-length subset of that defined by <xref target="RFC1123"/>. The
     823   other formats are described here only for
    824824   compatibility with obsolete implementations.
    825825   HTTP/1.1 clients and servers that parse the date value &MUST; accept
     
    33683368</reference>
    33693369
    3370 <reference anchor="RFC822">
    3371   <front>
    3372     <title abbrev="Standard for ARPA Internet Text Messages">Standard for the format of ARPA Internet text messages</title>
    3373     <author initials="D.H." surname="Crocker" fullname="David H. Crocker">
    3374       <organization>University of Delaware, Dept. of Electrical Engineering</organization>
    3375       <address><email>DCrocker@UDel-Relay</email></address>
    3376     </author>
    3377     <date month="August" day="13" year="1982"/>
    3378   </front>
    3379   <seriesInfo name="STD" value="11"/>
    3380   <seriesInfo name="RFC" value="822"/>
    3381 </reference>
    3382 
    33833370<reference anchor="RFC959">
    33843371  <front>
     
    45954582<section title="Since draft-ietf-httpbis-p1-messaging-05" anchor="changes.since.05">
    45964583<t>
     4584  Closed issues:
     4585  <list style="symbols">
     4586    <t>
     4587      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/134"/>:
     4588      "RFC822 reference left in discussion of date formats"
     4589    </t>
     4590  </list>
    45974591</t>
    45984592</section>
Note: See TracChangeset for help on using the changeset viewer.