Changeset 129


Ignore:
Timestamp:
Jan 1, 2008, 6:06:30 AM (12 years ago)
Author:
julian.reschke@…
Message:

Resolve #65: categorize many references as "informative", update some of them.

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

Legend:

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

    r128 r129  
    635635      </p>
    636636      <p id="rfc.section.1.1.p.4">HTTP is also used as a generic protocol for communication between user agents and proxies/gateways to other Internet systems,
    637          including those supported by the SMTP <a href="#RFC821" id="rfc.xref.RFC821.1"><cite title="Simple Mail Transfer Protocol">[RFC821]</cite></a>, NNTP <a href="#RFC3977" id="rfc.xref.RFC3977.1"><cite title="Network News Transfer Protocol (NNTP)">[RFC3977]</cite></a>, FTP <a href="#RFC959" id="rfc.xref.RFC959.1"><cite title="File Transfer Protocol">[RFC959]</cite></a>, Gopher <a href="#RFC1436" id="rfc.xref.RFC1436.1"><cite title="The Internet Gopher Protocol (a distributed document search and retrieval protocol)">[RFC1436]</cite></a>, and WAIS <a href="#WAIS" id="rfc.xref.WAIS.1"><cite title="WAIS Interface Protocol Prototype Functional Specification (v1.5)">[WAIS]</cite></a> protocols. In this way, HTTP allows basic hypermedia access to resources available from diverse applications.
     637         including those supported by the SMTP <a href="#RFC2821" id="rfc.xref.RFC2821.1"><cite title="Simple Mail Transfer Protocol">[RFC2821]</cite></a>, NNTP <a href="#RFC3977" id="rfc.xref.RFC3977.1"><cite title="Network News Transfer Protocol (NNTP)">[RFC3977]</cite></a>, FTP <a href="#RFC959" id="rfc.xref.RFC959.1"><cite title="File Transfer Protocol">[RFC959]</cite></a>, Gopher <a href="#RFC1436" id="rfc.xref.RFC1436.1"><cite title="The Internet Gopher Protocol (a distributed document search and retrieval protocol)">[RFC1436]</cite></a>, and WAIS <a href="#WAIS" id="rfc.xref.WAIS.1"><cite title="WAIS Interface Protocol Prototype Functional Specification (v1.5)">[WAIS]</cite></a> protocols. In this way, HTTP allows basic hypermedia access to resources available from diverse applications.
    638638      </p>
    639639      <h2 id="rfc.section.1.2"><a href="#rfc.section.1.2">1.2</a>&nbsp;<a id="intro.requirements" href="#intro.requirements">Requirements</a></h2>
     
    843843      <h2 id="rfc.section.2.1"><a href="#rfc.section.2.1">2.1</a>&nbsp;<a id="notation.abnf" href="#notation.abnf">Augmented BNF</a></h2>
    844844      <p id="rfc.section.2.1.p.1">All of the mechanisms specified in this document are described in both prose and an augmented Backus-Naur Form (BNF) similar
    845          to that used by <a href="#RFC822" id="rfc.xref.RFC822.2"><cite title="Standard for the format of ARPA Internet text messages">[RFC822]</cite></a>. Implementors will need to be familiar with the notation in order to understand this specification. The augmented BNF includes
     845         to that used by <a href="#RFC822ABNF" id="rfc.xref.RFC822ABNF.1"><cite title="Standard for the format of ARPA Internet text messages">[RFC822ABNF]</cite></a>. Implementors will need to be familiar with the notation in order to understand this specification. The augmented BNF includes
    846846         the following constructs:
    847847      </p>
     
    10481048   Sunday, 06-Nov-94 08:49:37 GMT ; obsolete RFC 850 format
    10491049   Sun Nov  6 08:49:37 1994       ; ANSI C's asctime() format
    1050 </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.3"><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
     1050</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.2"><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
    10511051         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;B</a> for further information.
    10521052      </p>
     
    11731173      <p id="rfc.section.4.1.p.1">HTTP messages consist of requests from client to server and responses from server to client.</p>
    11741174      <div id="rfc.figure.u.22"></div><pre class="inline"><span id="rfc.iref.g.51"></span>    HTTP-message   = Request | Response     ; HTTP/1.1 messages
    1175 </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="#RFC822" id="rfc.xref.RFC822.4"><cite title="Standard for the format of ARPA Internet text messages">[RFC822]</cite></a> for transferring entities (the payload of the message). Both types of message consist of a start-line, zero or more header
     1175</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="#RFC822" id="rfc.xref.RFC822.3"><cite title="Standard for the format of ARPA Internet text messages">[RFC822]</cite></a> for transferring entities (the payload of the message). Both types of message consist of a start-line, zero or more header
    11761176         fields (also known as "headers"), an empty line (i.e., a line with nothing preceding the CRLF) indicating the end of the header
    11771177         fields, and possibly a message-body.
     
    11891189      </p>
    11901190      <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>
    1191       <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.2"><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.3"><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 3.1</a> of <a href="#Part3" id="rfc.xref.Part3.8"><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/rfc822#section-3.1">Section 3.1</a> of <a href="#RFC822" id="rfc.xref.RFC822.5"><cite title="Standard for the format of ARPA Internet text messages">[RFC822]</cite></a>. Each header field consists of a name followed by a colon (":") and the field value. Field names are case-insensitive. The
     1191      <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.2"><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.3"><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 3.1</a> of <a href="#Part3" id="rfc.xref.Part3.8"><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/rfc822#section-3.1">Section 3.1</a> of <a href="#RFC822" id="rfc.xref.RFC822.4"><cite title="Standard for the format of ARPA Internet text messages">[RFC822]</cite></a>. Each header field consists of a name followed by a colon (":") and the field value. Field names are case-insensitive. The
    11921192         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
    11931193         each extra line with at least one SP or HT. Applications ought to follow "common form", where one is known or indicated, when
     
    16401640      <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>
    16411641      <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
    1642          as orig-date in <a href="#RFC822" id="rfc.xref.RFC822.6"><cite title="Standard for the format of ARPA Internet text messages">[RFC822]</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.
     1642         as orig-date in <a href="#RFC822" id="rfc.xref.RFC822.5"><cite title="Standard for the format of ARPA Internet text messages">[RFC822]</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.
    16431643      </p>
    16441644      <div id="rfc.figure.u.41"></div><pre class="inline"><span id="rfc.iref.g.73"></span>    Date  = "Date" ":" HTTP-date
     
    18031803      <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>
    18041804      <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
    1805          on requests, and between the origin server and the client on responses. It is analogous to the "Received" field of <a href="#RFC822" id="rfc.xref.RFC822.7"><cite title="Standard for the format of ARPA Internet text messages">[RFC822]</cite></a> and is intended to be used for tracking message forwards, avoiding request loops, and identifying the protocol capabilities
     1805         on requests, and between the origin server and the client on responses. It is analogous to the "Received" field of <a href="#RFC822" id="rfc.xref.RFC822.6"><cite title="Standard for the format of ARPA Internet text messages">[RFC822]</cite></a> and is intended to be used for tracking message forwards, avoiding request loops, and identifying the protocol capabilities
    18061806         of all senders along the request/response chain.
    18071807      </p>
     
    19111911      <p id="rfc.section.10.6.p.1">They exist. They are hard to defend against. Research continues. Beware.</p>
    19121912      <h1 id="rfc.section.11"><a href="#rfc.section.11">11.</a>&nbsp;<a id="ack" href="#ack">Acknowledgments</a></h1>
    1913       <p id="rfc.section.11.p.1">This specification makes heavy use of the augmented BNF and generic constructs defined by David H. Crocker for <a href="#RFC822" id="rfc.xref.RFC822.8"><cite title="Standard for the format of ARPA Internet text messages">[RFC822]</cite></a>. Similarly, it reuses many of the definitions provided by Nathaniel Borenstein and Ned Freed for MIME <a href="#RFC2045" id="rfc.xref.RFC2045.3"><cite title="Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies">[RFC2045]</cite></a>. We hope that their inclusion in this specification will help reduce past confusion over the relationship between HTTP and
     1913      <p id="rfc.section.11.p.1">This specification makes heavy use of the augmented BNF and generic constructs defined by David H. Crocker for <a href="#RFC822" id="rfc.xref.RFC822.7"><cite title="Standard for the format of ARPA Internet text messages">[RFC822]</cite></a>. Similarly, it reuses many of the definitions provided by Nathaniel Borenstein and Ned Freed for MIME <a href="#RFC2045" id="rfc.xref.RFC2045.3"><cite title="Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies">[RFC2045]</cite></a>. We hope that their inclusion in this specification will help reduce past confusion over the relationship between HTTP and
    19141914         Internet mail message formats.
    19151915      </p>
     
    19431943      <h2 id="rfc.references.1"><a href="#rfc.section.12.1" id="rfc.section.12.1">12.1</a> Normative References
    19441944      </h2>
    1945       <table summary="Normative References">         
     1945      <table summary="Normative References">           
    19461946         <tr>
    19471947            <td class="reference"><b id="ISO-8859-1">[ISO-8859-1]</b></td>
     
    19711971            </td>
    19721972         </tr>
     1973         <tr>
     1974            <td class="reference"><b id="RFC822ABNF">[RFC822ABNF]</b></td>
     1975            <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.
     1976            </td>
     1977         </tr>
    19731978      </table>
    19741979      <h2 id="rfc.references.2"><a href="#rfc.section.12.2" id="rfc.section.12.2">12.2</a> Informative References
    19751980      </h2>
    1976       <table summary="Informative References">     
     1981      <table summary="Informative References">                                         
     1982         <tr>
     1983            <td class="reference"><b id="Nie1997">[Nie1997]</b></td>
     1984            <td class="top">Nielsen, H.F.., Gettys, J., Prud'hommeaux, E., Lie, H., and C. Lilley, “<a href="http://doi.acm.org/10.1145/263105.263157">Network Performance Effects of HTTP/1.1, CSS1, and PNG</a>”, ACM&nbsp;Proceedings of the ACM SIGCOMM '97 conference on Applications, technologies, architectures, and protocols for computer communication
     1985               SIGCOMM '97, September&nbsp;1997, &lt;<a href="http://doi.acm.org/10.1145/263105.263157">http://doi.acm.org/10.1145/263105.263157</a>&gt;.
     1986            </td>
     1987         </tr>
     1988         <tr>
     1989            <td class="reference"><b id="Pad1995">[Pad1995]</b></td>
     1990            <td class="top">Padmanabhan, V.N. and J.C. Mogul, “Improving HTTP Latency”, Computer Networks and ISDN Systems&nbsp;v. 28, pp. 25-35, December&nbsp;1995.<br>Slightly revised version of paper in Proc. 2nd International WWW Conference '94: Mosaic and the Web, Oct. 1994, which is available
     1991               at &lt;<a href="http://www.ncsa.uiuc.edu/SDG/IT94/Proceedings/DDay/mogul/HTTPLatency.html">http://www.ncsa.uiuc.edu/SDG/IT94/Proceedings/DDay/mogul/HTTPLatency.html</a>&gt;.
     1992            </td>
     1993         </tr>
     1994         <tr>
     1995            <td class="reference"><b id="RFC1123">[RFC1123]</b></td>
     1996            <td class="top"><a title="University of Southern California (USC), Information Sciences Institute">Braden, R.</a>, “<a href="http://tools.ietf.org/html/rfc1123">Requirements for Internet Hosts - Application and Support</a>”, STD&nbsp;3, RFC&nbsp;1123, October&nbsp;1989.
     1997            </td>
     1998         </tr>
     1999         <tr>
     2000            <td class="reference"><b id="RFC1305">[RFC1305]</b></td>
     2001            <td class="top"><a title="University of Delaware, Electrical Engineering Department">Mills, D.</a>, “<a href="http://tools.ietf.org/html/rfc1305">Network Time Protocol (Version 3) Specification, Implementation</a>”, RFC&nbsp;1305, March&nbsp;1992.
     2002            </td>
     2003         </tr>
     2004         <tr>
     2005            <td class="reference"><b id="RFC1436">[RFC1436]</b></td>
     2006            <td class="top"><a title="University of Minnesota, Computer and Information Services">Anklesaria, F.</a>, <a title="University of Minnesota, Computer and Information Services">McCahill, M.</a>, <a title="University of Minnesota, Computer and Information Services">Lindner, P.</a>, <a title="University of Minnesota, Computer and Information Services">Johnson, D.</a>, <a title="University of Minnesota, Computer and Information Services">Torrey, D.</a>, and <a title="University of Minnesota, Computer and Information Services">B. Alberti</a>, “<a href="http://tools.ietf.org/html/rfc1436">The Internet Gopher Protocol (a distributed document search and retrieval protocol)</a>”, RFC&nbsp;1436, March&nbsp;1993.
     2007            </td>
     2008         </tr>
     2009         <tr>
     2010            <td class="reference"><b id="RFC1630">[RFC1630]</b></td>
     2011            <td class="top"><a title="CERN, World-Wide Web project">Berners-Lee, T.</a>, “<a href="http://tools.ietf.org/html/rfc1630">Universal Resource Identifiers in WWW: A Unifying Syntax for the Expression of Names and Addresses of Objects on the Network
     2012                  as used in the World-Wide Web</a>”, RFC&nbsp;1630, June&nbsp;1994.
     2013            </td>
     2014         </tr>
     2015         <tr>
     2016            <td class="reference"><b id="RFC1738">[RFC1738]</b></td>
     2017            <td class="top"><a title="CERN, World-Wide Web project">Berners-Lee, T.</a>, <a title="Xerox PARC">Masinter, L.</a>, and <a title="University of Minnesota, Computer and Information Services">M. McCahill</a>, “<a href="http://tools.ietf.org/html/rfc1738">Uniform Resource Locators (URL)</a>”, RFC&nbsp;1738, December&nbsp;1994.
     2018            </td>
     2019         </tr>
     2020         <tr>
     2021            <td class="reference"><b id="RFC1808">[RFC1808]</b></td>
     2022            <td class="top"><a title="University of California Irvine, Department of Information and Computer Science">Fielding, R.</a>, “<a href="http://tools.ietf.org/html/rfc1808">Relative Uniform Resource Locators</a>”, RFC&nbsp;1808, June&nbsp;1995.
     2023            </td>
     2024         </tr>
     2025         <tr>
     2026            <td class="reference"><b id="RFC1900">[RFC1900]</b></td>
     2027            <td class="top"><a title="CERN, Computing and Networks Division">Carpenter, B.</a> and <a title="cisco Systems">Y. Rekhter</a>, “<a href="http://tools.ietf.org/html/rfc1900">Renumbering Needs Work</a>”, RFC&nbsp;1900, February&nbsp;1996.
     2028            </td>
     2029         </tr>
     2030         <tr>
     2031            <td class="reference"><b id="RFC1945">[RFC1945]</b></td>
     2032            <td class="top"><a title="MIT, Laboratory for Computer Science">Berners-Lee, T.</a>, <a title="University of California, Irvine, Department of Information and Computer Science">Fielding, R.T.</a>, and <a title="W3 Consortium, MIT Laboratory for Computer Science">H.F. Nielsen</a>, “<a href="http://tools.ietf.org/html/rfc1945">Hypertext Transfer Protocol -- HTTP/1.0</a>”, RFC&nbsp;1945, May&nbsp;1996.
     2033            </td>
     2034         </tr>
    19772035         <tr>
    19782036            <td class="reference"><b id="RFC2068">[RFC2068]</b></td>
     
    19812039         </tr>
    19822040         <tr>
     2041            <td class="reference"><b id="RFC2145">[RFC2145]</b></td>
     2042            <td class="top"><a title="Western Research Laboratory">Mogul, J.C.</a>, <a title="Department of Information and Computer Science">Fielding, R.T.</a>, <a title="MIT Laboratory for Computer Science">Gettys, J.</a>, and <a title="W3 Consortium">H.F. Nielsen</a>, “<a href="http://tools.ietf.org/html/rfc2145">Use and Interpretation of HTTP Version Numbers</a>”, RFC&nbsp;2145, May&nbsp;1997.
     2043            </td>
     2044         </tr>
     2045         <tr>
     2046            <td class="reference"><b id="RFC2324">[RFC2324]</b></td>
     2047            <td class="top"><a title="Xerox Palo Alto Research Center">Masinter, L.</a>, “<a href="http://tools.ietf.org/html/rfc2324">Hyper Text Coffee Pot Control Protocol (HTCPCP/1.0)</a>”, RFC&nbsp;2324, April&nbsp;1998.
     2048            </td>
     2049         </tr>
     2050         <tr>
    19832051            <td class="reference"><b id="RFC2616">[RFC2616]</b></td>
    19842052            <td class="top"><a title="University of California, Irvine">Fielding, R.</a>, <a title="W3C">Gettys, J.</a>, <a title="Compaq Computer Corporation">Mogul, J.</a>, <a title="MIT Laboratory for Computer Science">Frystyk, H.</a>, <a title="Xerox Corporation">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, and <a title="W3C">T. Berners-Lee</a>, “<a href="http://tools.ietf.org/html/rfc2616">Hypertext Transfer Protocol -- HTTP/1.1</a>”, RFC&nbsp;2616, June&nbsp;1999.
     
    19862054         </tr>
    19872055         <tr>
     2056            <td class="reference"><b id="RFC2821">[RFC2821]</b></td>
     2057            <td class="top"><a title="AT&amp;T Laboratories">Klensin, J.</a>, “<a href="http://tools.ietf.org/html/rfc2821">Simple Mail Transfer Protocol</a>”, RFC&nbsp;2821, April&nbsp;2001.
     2058            </td>
     2059         </tr>
     2060         <tr>
    19882061            <td class="reference"><b id="RFC3977">[RFC3977]</b></td>
    19892062            <td class="top"><a title="THUS plc">Feather, C.</a>, “<a href="http://tools.ietf.org/html/rfc3977">Network News Transfer Protocol (NNTP)</a>”, RFC&nbsp;3977, October&nbsp;2006.
    19902063            </td>
     2064         </tr>
     2065         <tr>
     2066            <td class="reference"><b id="RFC822">[RFC822]</b></td>
     2067            <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.
     2068            </td>
     2069         </tr>
     2070         <tr>
     2071            <td class="reference"><b id="RFC959">[RFC959]</b></td>
     2072            <td class="top">Postel, J. and J. Reynolds, “<a href="http://tools.ietf.org/html/rfc959">File Transfer Protocol</a>”, STD&nbsp;9, RFC&nbsp;959, October&nbsp;1985.
     2073            </td>
     2074         </tr>
     2075         <tr>
     2076            <td class="reference"><b id="Spe">[Spe]</b></td>
     2077            <td class="top">Spero, S., “<a href="http://sunsite.unc.edu/mdma-release/http-prob.html">Analysis of HTTP Performance Problems</a>”, &lt;<a href="http://sunsite.unc.edu/mdma-release/http-prob.html">http://sunsite.unc.edu/mdma-release/http-prob.html</a>&gt;.
     2078            </td>
     2079         </tr>
     2080         <tr>
     2081            <td class="reference"><b id="Tou1998">[Tou1998]</b></td>
     2082            <td class="top"><a title="USC/Information Sciences Institute">Touch, J.</a>, <a title="USC/Information Sciences Institute">Heidemann, J.</a>, and <a title="USC/Information Sciences Institute">K. Obraczka</a>, “<a href="http://www.isi.edu/touch/pubs/http-perf96/">Analysis of HTTP Performance</a>”, ISI Research Report&nbsp;ISI/RR-98-463, Aug&nbsp;1998, &lt;<a href="http://www.isi.edu/touch/pubs/http-perf96/">http://www.isi.edu/touch/pubs/http-perf96/</a>&gt;.<br>(original report dated Aug. 1996)
     2083            </td>
     2084         </tr>
     2085         <tr>
     2086            <td class="reference"><b id="WAIS">[WAIS]</b></td>
     2087            <td class="top">Davis, F., Kahle, B., Morris, H., Salem, J., Shen, T., Wang, R., Sui, J., and M. Grinbaum, “WAIS Interface Protocol Prototype Functional Specification (v1.5)”, Thinking Machines Corporation, April&nbsp;1990.</td>
    19912088         </tr>
    19922089      </table>
    19932090      <h2 id="rfc.references.3"><a href="#rfc.section.12.3" id="rfc.section.12.3">12.3</a> References (to be categorized)
    19942091      </h2>
    1995       <table summary="References (to be categorized)">                                               
    1996          <tr>
    1997             <td class="reference"><b id="Nie1997">[Nie1997]</b></td>
    1998             <td class="top">Nielsen, H.F.., Gettys, J., Prud'hommeaux, E., Lie, H., and C. Lilley, “Network Performance Effects of HTTP/1.1, CSS1, and PNG”, Proceedings of ACM SIGCOMM '97, Cannes France, Sep&nbsp;1997.</td>
    1999          </tr>
    2000          <tr>
    2001             <td class="reference"><b id="Pad1995">[Pad1995]</b></td>
    2002             <td class="top">Padmanabhan, V.N. and J.C. Mogul, “Improving HTTP Latency”, Computer Networks and ISDN Systems&nbsp;v. 28, pp. 25-35, Dec&nbsp;1995.<br>Slightly revised version of paper in Proc. 2nd International WWW Conference '94: Mosaic and the Web, Oct. 1994, which is available
    2003                at &lt;<a href="http://www.ncsa.uiuc.edu/SDG/IT94/Proceedings/DDay/mogul/HTTPLatency.html">http://www.ncsa.uiuc.edu/SDG/IT94/Proceedings/DDay/mogul/HTTPLatency.html</a>&gt;.
    2004             </td>
    2005          </tr>
    2006          <tr>
    2007             <td class="reference"><b id="RFC1123">[RFC1123]</b></td>
    2008             <td class="top"><a title="University of Southern California (USC), Information Sciences Institute">Braden, R.</a>, “<a href="http://tools.ietf.org/html/rfc1123">Requirements for Internet Hosts - Application and Support</a>”, STD&nbsp;3, RFC&nbsp;1123, October&nbsp;1989.
    2009             </td>
    2010          </tr>
    2011          <tr>
    2012             <td class="reference"><b id="RFC1305">[RFC1305]</b></td>
    2013             <td class="top"><a title="University of Delaware, Electrical Engineering Department">Mills, D.</a>, “<a href="http://tools.ietf.org/html/rfc1305">Network Time Protocol (Version 3) Specification, Implementation</a>”, RFC&nbsp;1305, March&nbsp;1992.
    2014             </td>
    2015          </tr>
    2016          <tr>
    2017             <td class="reference"><b id="RFC1436">[RFC1436]</b></td>
    2018             <td class="top"><a title="University of Minnesota, Computer and Information Services">Anklesaria, F.</a>, <a title="University of Minnesota, Computer and Information Services">McCahill, M.</a>, <a title="University of Minnesota, Computer and Information Services">Lindner, P.</a>, <a title="University of Minnesota, Computer and Information Services">Johnson, D.</a>, <a title="University of Minnesota, Computer and Information Services">Torrey, D.</a>, and <a title="University of Minnesota, Computer and Information Services">B. Alberti</a>, “<a href="http://tools.ietf.org/html/rfc1436">The Internet Gopher Protocol (a distributed document search and retrieval protocol)</a>”, RFC&nbsp;1436, March&nbsp;1993.
    2019             </td>
    2020          </tr>
    2021          <tr>
    2022             <td class="reference"><b id="RFC1630">[RFC1630]</b></td>
    2023             <td class="top"><a title="CERN, World-Wide Web project">Berners-Lee, T.</a>, “<a href="http://tools.ietf.org/html/rfc1630">Universal Resource Identifiers in WWW: A Unifying Syntax for the Expression of Names and Addresses of Objects on the Network
    2024                   as used in the World-Wide Web</a>”, RFC&nbsp;1630, June&nbsp;1994.
    2025             </td>
    2026          </tr>
     2092      <table summary="References (to be categorized)">           
    20272093         <tr>
    20282094            <td class="reference"><b id="RFC1737">[RFC1737]</b></td>
     
    20312097         </tr>
    20322098         <tr>
    2033             <td class="reference"><b id="RFC1738">[RFC1738]</b></td>
    2034             <td class="top"><a title="CERN, World-Wide Web project">Berners-Lee, T.</a>, <a title="Xerox PARC">Masinter, L.</a>, and <a title="University of Minnesota, Computer and Information Services">M. McCahill</a>, “<a href="http://tools.ietf.org/html/rfc1738">Uniform Resource Locators (URL)</a>”, RFC&nbsp;1738, December&nbsp;1994.
    2035             </td>
    2036          </tr>
    2037          <tr>
    2038             <td class="reference"><b id="RFC1808">[RFC1808]</b></td>
    2039             <td class="top"><a title="University of California Irvine, Department of Information and Computer Science">Fielding, R.</a>, “<a href="http://tools.ietf.org/html/rfc1808">Relative Uniform Resource Locators</a>”, RFC&nbsp;1808, June&nbsp;1995.
    2040             </td>
    2041          </tr>
    2042          <tr>
    2043             <td class="reference"><b id="RFC1900">[RFC1900]</b></td>
    2044             <td class="top"><a title="CERN, Computing and Networks Division">Carpenter, B.</a> and <a title="cisco Systems">Y. Rekhter</a>, “<a href="http://tools.ietf.org/html/rfc1900">Renumbering Needs Work</a>”, RFC&nbsp;1900, February&nbsp;1996.
    2045             </td>
    2046          </tr>
    2047          <tr>
    2048             <td class="reference"><b id="RFC1945">[RFC1945]</b></td>
    2049             <td class="top"><a title="MIT, Laboratory for Computer Science">Berners-Lee, T.</a>, <a title="University of California, Irvine, Department of Information and Computer Science">Fielding, R.T.</a>, and <a title="W3 Consortium, MIT Laboratory for Computer Science">H.F. Nielsen</a>, “<a href="http://tools.ietf.org/html/rfc1945">Hypertext Transfer Protocol -- HTTP/1.0</a>”, RFC&nbsp;1945, May&nbsp;1996.
    2050             </td>
    2051          </tr>
    2052          <tr>
    20532099            <td class="reference"><b id="RFC2045">[RFC2045]</b></td>
    20542100            <td class="top"><a title="Innosoft International, Inc.">Freed, N.</a> and <a title="First Virtual Holdings">N.S. Borenstein</a>, “<a href="http://tools.ietf.org/html/rfc2045">Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies</a>”, RFC&nbsp;2045, November&nbsp;1996.
     
    20612107         </tr>
    20622108         <tr>
    2063             <td class="reference"><b id="RFC2145">[RFC2145]</b></td>
    2064             <td class="top"><a title="Western Research Laboratory">Mogul, J.C.</a>, <a title="Department of Information and Computer Science">Fielding, R.T.</a>, <a title="MIT Laboratory for Computer Science">Gettys, J.</a>, and <a title="W3 Consortium">H.F. Nielsen</a>, “<a href="http://tools.ietf.org/html/rfc2145">Use and Interpretation of HTTP Version Numbers</a>”, RFC&nbsp;2145, May&nbsp;1997.
    2065             </td>
    2066          </tr>
    2067          <tr>
    2068             <td class="reference"><b id="RFC2324">[RFC2324]</b></td>
    2069             <td class="top"><a title="Xerox Palo Alto Research Center">Masinter, L.</a>, “<a href="http://tools.ietf.org/html/rfc2324">Hyper Text Coffee Pot Control Protocol (HTCPCP/1.0)</a>”, RFC&nbsp;2324, April&nbsp;1998.
    2070             </td>
    2071          </tr>
    2072          <tr>
    20732109            <td class="reference"><b id="RFC2396">[RFC2396]</b></td>
    20742110            <td class="top"><a title="World Wide Web Consortium">Berners-Lee, T.</a>, <a title="Department of Information and Computer Science">Fielding, R.T.</a>, and <a title="Xerox PARC">L. Masinter</a>, “<a href="http://tools.ietf.org/html/rfc2396">Uniform Resource Identifiers (URI): Generic Syntax</a>”, RFC&nbsp;2396, August&nbsp;1998.
     
    20812117         </tr>
    20822118         <tr>
    2083             <td class="reference"><b id="RFC821">[RFC821]</b></td>
    2084             <td class="top">Postel, J.B., “<a href="http://tools.ietf.org/html/rfc821">Simple Mail Transfer Protocol</a>”, STD&nbsp;10, RFC&nbsp;821, August&nbsp;1982.
    2085             </td>
    2086          </tr>
    2087          <tr>
    2088             <td class="reference"><b id="RFC822">[RFC822]</b></td>
    2089             <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.
    2090             </td>
    2091          </tr>
    2092          <tr>
    2093             <td class="reference"><b id="RFC959">[RFC959]</b></td>
    2094             <td class="top">Postel, J. and J. Reynolds, “<a href="http://tools.ietf.org/html/rfc959">File Transfer Protocol</a>”, STD&nbsp;9, RFC&nbsp;959, October&nbsp;1985.
    2095             </td>
    2096          </tr>
    2097          <tr>
    2098             <td class="reference"><b id="Spe">[Spe]</b></td>
    2099             <td class="top">Spero, S., “<a href="http://sunsite.unc.edu/mdma-release/http-prob.html">Analysis of HTTP Performance Problems</a>”, &lt;<a href="http://sunsite.unc.edu/mdma-release/http-prob.html">http://sunsite.unc.edu/mdma-release/http-prob.html</a>&gt;.
    2100             </td>
    2101          </tr>
    2102          <tr>
    2103             <td class="reference"><b id="Tou1998">[Tou1998]</b></td>
    2104             <td class="top"><a title="USC/Information Sciences Institute">Touch, J.</a>, <a title="USC/Information Sciences Institute">Heidemann, J.</a>, and <a title="USC/Information Sciences Institute">K. Obraczka</a>, “<a href="http://www.isi.edu/touch/pubs/http-perf96/">Analysis of HTTP Performance</a>”, ISI Research Report&nbsp;ISI/RR-98-463 (original report dated Aug.1996), Aug&nbsp;1998, &lt;<a href="http://www.isi.edu/touch/pubs/http-perf96/">http://www.isi.edu/touch/pubs/http-perf96/</a>&gt;.
    2105             </td>
    2106          </tr>
    2107          <tr>
    21082119            <td class="reference"><b id="USASCII">[USASCII]</b></td>
    21092120            <td class="top">American National Standards Institute, “Coded Character Set -- 7-bit American Standard Code for Information Interchange”, ANSI&nbsp;X3.4, 1986.</td>
    2110          </tr>
    2111          <tr>
    2112             <td class="reference"><b id="WAIS">[WAIS]</b></td>
    2113             <td class="top">Davis, F., Kahle, B., Morris, H., Salem, J., Shen, T., Wang, R., Sui, J., and M. Grinbaum, “WAIS Interface Protocol Prototype Functional Specification (v1.5)”, Thinking Machines Corporation, April&nbsp;1990.</td>
    21142121         </tr>
    21152122      </table>
     
    23472354         </li>
    23482355         <li> &lt;<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/48">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/48</a>&gt;: "Date reference typo"
     2356         </li>
     2357         <li> &lt;<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/65">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/65</a>&gt;: "Informative references"
    23492358         </li>
    23502359         <li> &lt;<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/66">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/66</a>&gt;: "ISO-8859-1 Reference"
     
    25362545            </li>
    25372546            <li class="indline0"><a id="rfc.index.N" href="#rfc.index.N"><b>N</b></a><ul class="ind">
    2538                   <li class="indline1"><em>Nie1997</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Nie1997.1">7.1.1</a>, <a class="iref" href="#Nie1997"><b>12.3</b></a>, <a class="iref" href="#rfc.xref.Nie1997.2">D.3</a></li>
     2547                  <li class="indline1"><em>Nie1997</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Nie1997.1">7.1.1</a>, <a class="iref" href="#Nie1997"><b>12.2</b></a>, <a class="iref" href="#rfc.xref.Nie1997.2">D.3</a></li>
    25392548               </ul>
    25402549            </li>
     
    25452554            </li>
    25462555            <li class="indline0"><a id="rfc.index.P" href="#rfc.index.P"><b>P</b></a><ul class="ind">
    2547                   <li class="indline1"><em>Pad1995</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Pad1995.1">7.1.1</a>, <a class="iref" href="#Pad1995"><b>12.3</b></a></li>
     2556                  <li class="indline1"><em>Pad1995</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Pad1995.1">7.1.1</a>, <a class="iref" href="#Pad1995"><b>12.2</b></a></li>
    25482557                  <li class="indline1"><em>Part2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part2.1">3.2.1</a>, <a class="iref" href="#rfc.xref.Part2.2">4.2</a>, <a class="iref" href="#rfc.xref.Part2.3">4.2</a>, <a class="iref" href="#rfc.xref.Part2.4">4.3</a>, <a class="iref" href="#rfc.xref.Part2.5">5</a>, <a class="iref" href="#rfc.xref.Part2.6">5.1.2</a>, <a class="iref" href="#rfc.xref.Part2.7">6</a>, <a class="iref" href="#rfc.xref.Part2.8">6.1.1</a>, <a class="iref" href="#rfc.xref.Part2.9">7.1.2.2</a>, <a class="iref" href="#rfc.xref.Part2.10">7.1.4</a>, <a class="iref" href="#rfc.xref.Part2.11">7.2.3</a>, <a class="iref" href="#rfc.xref.Part2.12">7.2.3</a>, <a class="iref" href="#rfc.xref.Part2.13">7.2.3</a>, <a class="iref" href="#rfc.xref.Part2.14">7.2.3</a>, <a class="iref" href="#Part2"><b>12.1</b></a><ul class="ind">
    25492558                        <li class="indline1"><em>Section 3</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part2.4">4.3</a></li>
     
    25842593                  <li class="indline1">resource&nbsp;&nbsp;<a class="iref" href="#rfc.iref.r.3">1.3</a></li>
    25852594                  <li class="indline1">response&nbsp;&nbsp;<a class="iref" href="#rfc.iref.r.2">1.3</a></li>
    2586                   <li class="indline1"><em>RFC1123</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC1123.1">3.3.1</a>, <a class="iref" href="#RFC1123"><b>12.3</b></a></li>
    2587                   <li class="indline1"><em>RFC1305</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC1305.1">8.3</a>, <a class="iref" href="#RFC1305"><b>12.3</b></a></li>
    2588                   <li class="indline1"><em>RFC1436</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC1436.1">1.1</a>, <a class="iref" href="#RFC1436"><b>12.3</b></a></li>
    2589                   <li class="indline1"><em>RFC1630</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC1630.1">1.1</a>, <a class="iref" href="#rfc.xref.RFC1630.2">3.2</a>, <a class="iref" href="#RFC1630"><b>12.3</b></a></li>
     2595                  <li class="indline1"><em>RFC1123</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC1123.1">3.3.1</a>, <a class="iref" href="#RFC1123"><b>12.2</b></a></li>
     2596                  <li class="indline1"><em>RFC1305</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC1305.1">8.3</a>, <a class="iref" href="#RFC1305"><b>12.2</b></a></li>
     2597                  <li class="indline1"><em>RFC1436</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC1436.1">1.1</a>, <a class="iref" href="#RFC1436"><b>12.2</b></a></li>
     2598                  <li class="indline1"><em>RFC1630</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC1630.1">1.1</a>, <a class="iref" href="#rfc.xref.RFC1630.2">3.2</a>, <a class="iref" href="#RFC1630"><b>12.2</b></a></li>
    25902599                  <li class="indline1"><em>RFC1737</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC1737.1">1.1</a>, <a class="iref" href="#rfc.xref.RFC1737.2">3.2</a>, <a class="iref" href="#RFC1737"><b>12.3</b></a></li>
    2591                   <li class="indline1"><em>RFC1738</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC1738.1">1.1</a>, <a class="iref" href="#rfc.xref.RFC1738.2">3.2</a>, <a class="iref" href="#rfc.xref.RFC1738.3">3.2.1</a>, <a class="iref" href="#RFC1738"><b>12.3</b></a></li>
    2592                   <li class="indline1"><em>RFC1808</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC1808.1">3.2.1</a>, <a class="iref" href="#rfc.xref.RFC1808.2">3.2.1</a>, <a class="iref" href="#RFC1808"><b>12.3</b></a></li>
    2593                   <li class="indline1"><em>RFC1900</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC1900.1">3.2.2</a>, <a class="iref" href="#rfc.xref.RFC1900.2">10.4</a>, <a class="iref" href="#RFC1900"><b>12.3</b></a></li>
    2594                   <li class="indline1"><em>RFC1945</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC1945.1">1.1</a>, <a class="iref" href="#RFC1945"><b>12.3</b></a></li>
     2600                  <li class="indline1"><em>RFC1738</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC1738.1">1.1</a>, <a class="iref" href="#rfc.xref.RFC1738.2">3.2</a>, <a class="iref" href="#rfc.xref.RFC1738.3">3.2.1</a>, <a class="iref" href="#RFC1738"><b>12.2</b></a></li>
     2601                  <li class="indline1"><em>RFC1808</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC1808.1">3.2.1</a>, <a class="iref" href="#rfc.xref.RFC1808.2">3.2.1</a>, <a class="iref" href="#RFC1808"><b>12.2</b></a></li>
     2602                  <li class="indline1"><em>RFC1900</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC1900.1">3.2.2</a>, <a class="iref" href="#rfc.xref.RFC1900.2">10.4</a>, <a class="iref" href="#RFC1900"><b>12.2</b></a></li>
     2603                  <li class="indline1"><em>RFC1945</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC1945.1">1.1</a>, <a class="iref" href="#RFC1945"><b>12.2</b></a></li>
    25952604                  <li class="indline1"><em>RFC2045</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2045.1">1.1</a>, <a class="iref" href="#rfc.xref.RFC2045.2">3.4</a>, <a class="iref" href="#rfc.xref.RFC2045.3">11</a>, <a class="iref" href="#RFC2045"><b>12.3</b></a></li>
    25962605                  <li class="indline1"><em>RFC2047</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2047.1">2.2</a>, <a class="iref" href="#RFC2047"><b>12.3</b></a></li>
     
    26002609                  </li>
    26012610                  <li class="indline1"><em>RFC2119</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2119.1">1.2</a>, <a class="iref" href="#RFC2119"><b>12.1</b></a>, <a class="iref" href="#rfc.xref.RFC2119.2">D.3</a></li>
    2602                   <li class="indline1"><em>RFC2145</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2145.1">3.1</a>, <a class="iref" href="#rfc.xref.RFC2145.2">3.1</a>, <a class="iref" href="#RFC2145"><b>12.3</b></a>, <a class="iref" href="#rfc.xref.RFC2145.3">D.3</a></li>
    2603                   <li class="indline1"><em>RFC2324</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2324.1">1.1</a>, <a class="iref" href="#RFC2324"><b>12.3</b></a></li>
     2611                  <li class="indline1"><em>RFC2145</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2145.1">3.1</a>, <a class="iref" href="#rfc.xref.RFC2145.2">3.1</a>, <a class="iref" href="#RFC2145"><b>12.2</b></a>, <a class="iref" href="#rfc.xref.RFC2145.3">D.3</a></li>
     2612                  <li class="indline1"><em>RFC2324</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2324.1">1.1</a>, <a class="iref" href="#RFC2324"><b>12.2</b></a></li>
    26042613                  <li class="indline1"><em>RFC2396</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2396.1">3.2.1</a>, <a class="iref" href="#rfc.xref.RFC2396.2">3.2.3</a>, <a class="iref" href="#rfc.xref.RFC2396.3">5.1.2</a>, <a class="iref" href="#RFC2396"><b>12.3</b></a>, <a class="iref" href="#rfc.xref.RFC2396.4">D.4</a><ul class="ind">
    26052614                        <li class="indline1"><em>Section 3</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2396.4">D.4</a></li>
     
    26072616                  </li>
    26082617                  <li class="indline1"><em>RFC2616</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2616.1">1</a>, <a class="iref" href="#rfc.xref.RFC2616.2">11</a>, <a class="iref" href="#RFC2616"><b>12.2</b></a>, <a class="iref" href="#rfc.xref.RFC2616.3">E.1</a></li>
     2618                  <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>
    26092619                  <li class="indline1"><em>RFC3977</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC3977.1">1.1</a>, <a class="iref" href="#RFC3977"><b>12.2</b></a></li>
    26102620                  <li class="indline1"><em>RFC4288</em>&nbsp;&nbsp;<a class="iref" href="#RFC4288"><b>12.3</b></a>, <a class="iref" href="#rfc.xref.RFC4288.1">A</a></li>
    2611                   <li class="indline1"><em>RFC821</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC821.1">1.1</a>, <a class="iref" href="#RFC821"><b>12.3</b></a></li>
    2612                   <li class="indline1"><em>RFC822</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC822.1">1.1</a>, <a class="iref" href="#rfc.xref.RFC822.2">2.1</a>, <a class="iref" href="#rfc.xref.RFC822.3">3.3.1</a>, <a class="iref" href="#rfc.xref.RFC822.4">4.1</a>, <a class="iref" href="#rfc.xref.RFC822.5">4.2</a>, <a class="iref" href="#rfc.xref.RFC822.6">8.3</a>, <a class="iref" href="#rfc.xref.RFC822.7">8.9</a>, <a class="iref" href="#rfc.xref.RFC822.8">11</a>, <a class="iref" href="#RFC822"><b>12.3</b></a><ul class="ind">
    2613                         <li class="indline1"><em>Section 3.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC822.5">4.2</a></li>
     2621                  <li class="indline1"><em>RFC822</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC822.1">1.1</a>, <a class="iref" href="#rfc.xref.RFC822.2">3.3.1</a>, <a class="iref" href="#rfc.xref.RFC822.3">4.1</a>, <a class="iref" href="#rfc.xref.RFC822.4">4.2</a>, <a class="iref" href="#rfc.xref.RFC822.5">8.3</a>, <a class="iref" href="#rfc.xref.RFC822.6">8.9</a>, <a class="iref" href="#rfc.xref.RFC822.7">11</a>, <a class="iref" href="#RFC822"><b>12.2</b></a><ul class="ind">
     2622                        <li class="indline1"><em>Section 3.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC822.4">4.2</a></li>
    26142623                     </ul>
    26152624                  </li>
    2616                   <li class="indline1"><em>RFC959</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC959.1">1.1</a>, <a class="iref" href="#RFC959"><b>12.3</b></a></li>
     2625                  <li class="indline1"><em>RFC822ABNF</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC822ABNF.1">2.1</a>, <a class="iref" href="#RFC822ABNF"><b>12.1</b></a></li>
     2626                  <li class="indline1"><em>RFC959</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC959.1">1.1</a>, <a class="iref" href="#RFC959"><b>12.2</b></a></li>
    26172627               </ul>
    26182628            </li>
    26192629            <li class="indline0"><a id="rfc.index.S" href="#rfc.index.S"><b>S</b></a><ul class="ind">
    26202630                  <li class="indline1">server&nbsp;&nbsp;<a class="iref" href="#rfc.iref.s.1">1.3</a></li>
    2621                   <li class="indline1"><em>Spe</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Spe.1">7.1.1</a>, <a class="iref" href="#Spe"><b>12.3</b></a></li>
     2631                  <li class="indline1"><em>Spe</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Spe.1">7.1.1</a>, <a class="iref" href="#Spe"><b>12.2</b></a></li>
    26222632               </ul>
    26232633            </li>
    26242634            <li class="indline0"><a id="rfc.index.T" href="#rfc.index.T"><b>T</b></a><ul class="ind">
    26252635                  <li class="indline1">TE header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.te.1">3.4</a>, <a class="iref" href="#rfc.xref.header.te.2">3.4.1</a>, <a class="iref" href="#rfc.iref.t.2"><b>8.5</b></a>, <a class="iref" href="#rfc.xref.header.te.3">D.3</a></li>
    2626                   <li class="indline1"><em>Tou1998</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Tou1998.1">7.1.1</a>, <a class="iref" href="#Tou1998"><b>12.3</b></a></li>
     2636                  <li class="indline1"><em>Tou1998</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Tou1998.1">7.1.1</a>, <a class="iref" href="#Tou1998"><b>12.2</b></a></li>
    26272637                  <li class="indline1">Trailer header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.trailer.1">3.4.1</a>, <a class="iref" href="#rfc.xref.header.trailer.2">4.5</a>, <a class="iref" href="#rfc.iref.t.3"><b>8.6</b></a></li>
    26282638                  <li class="indline1">Transfer-Encoding header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.transfer-encoding.1">3.4</a>, <a class="iref" href="#rfc.xref.header.transfer-encoding.2">4.3</a>, <a class="iref" href="#rfc.xref.header.transfer-encoding.3">4.4</a>, <a class="iref" href="#rfc.xref.header.transfer-encoding.4">4.5</a>, <a class="iref" href="#rfc.iref.t.4"><b>8.7</b></a></li>
     
    26432653            </li>
    26442654            <li class="indline0"><a id="rfc.index.W" href="#rfc.index.W"><b>W</b></a><ul class="ind">
    2645                   <li class="indline1"><em>WAIS</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.WAIS.1">1.1</a>, <a class="iref" href="#WAIS"><b>12.3</b></a></li>
     2655                  <li class="indline1"><em>WAIS</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.WAIS.1">1.1</a>, <a class="iref" href="#WAIS"><b>12.2</b></a></li>
    26462656               </ul>
    26472657            </li>
  • draft-ietf-httpbis/latest/p1-messaging.xml

    r128 r129  
    263263   HTTP is also used as a generic protocol for communication between
    264264   user agents and proxies/gateways to other Internet systems, including
    265    those supported by the SMTP <xref target="RFC821"/>, NNTP <xref target="RFC3977"/>, FTP <xref target="RFC959"/>, Gopher <xref target="RFC1436"/>,
     265   those supported by the SMTP <xref target="RFC2821"/>, NNTP <xref target="RFC3977"/>, FTP <xref target="RFC959"/>, Gopher <xref target="RFC1436"/>,
    266266   and WAIS <xref target="WAIS"/> protocols. In this way, HTTP allows basic hypermedia
    267267   access to resources available from diverse applications.
     
    651651   All of the mechanisms specified in this document are described in
    652652   both prose and an augmented Backus-Naur Form (BNF) similar to that
    653    used by <xref target="RFC822"/>. Implementors will need to be familiar with the
     653   used by <xref target="RFC822ABNF"/>. Implementors will need to be familiar with the
    654654   notation in order to understand this specification. The augmented BNF
    655655   includes the following constructs:
     
    30613061</reference>
    30623062
     3063<reference anchor="RFC822ABNF">
     3064  <front>
     3065    <title abbrev="Standard for ARPA Internet Text Messages">Standard for the format of ARPA Internet text messages</title>
     3066    <author initials="D.H." surname="Crocker" fullname="David H. Crocker">
     3067      <organization>University of Delaware, Dept. of Electrical Engineering</organization>
     3068      <address><email>DCrocker@UDel-Relay</email></address>
     3069    </author>
     3070    <date month="August" day="13" year="1982"/>
     3071  </front>
     3072  <seriesInfo name="STD" value="11"/>
     3073  <seriesInfo name="RFC" value="822"/>
     3074</reference>
     3075
    30633076<reference anchor="RFC2119">
    30643077  <front>
     
    30783091<references title="Informative References">
    30793092
     3093<reference anchor="Nie1997" target="http://doi.acm.org/10.1145/263105.263157">
     3094  <front>
     3095    <title>Network Performance Effects of HTTP/1.1, CSS1, and PNG</title>
     3096    <author initials="H.F.." surname="Nielsen" fullname="H.F. Nielsen">
     3097      <organization/>
     3098    </author>
     3099    <author initials="J." surname="Gettys" fullname="J. Gettys">
     3100      <organization/>
     3101    </author>
     3102    <author initials="E." surname="Prud'hommeaux" fullname="E. Prud'hommeaux">
     3103      <organization/>
     3104    </author>
     3105    <author initials="H." surname="Lie" fullname="H. Lie">
     3106      <organization/>
     3107    </author>
     3108    <author initials="C." surname="Lilley" fullname="C. Lilley">
     3109      <organization/>
     3110    </author>
     3111    <date year="1997" month="September"/>
     3112  </front>
     3113  <seriesInfo name="ACM" value="Proceedings of the ACM SIGCOMM '97 conference on Applications, technologies, architectures, and protocols for computer communication SIGCOMM '97"/>
     3114</reference>
     3115
     3116<reference anchor="Pad1995">
     3117  <front>
     3118    <title>Improving HTTP Latency</title>
     3119    <author initials="V.N." surname="Padmanabhan" fullname="Venkata N. Padmanabhan">
     3120      <organization/>
     3121    </author>
     3122    <author initials="J.C." surname="Mogul" fullname="Jeffrey C. Mogul">
     3123      <organization/>
     3124    </author>
     3125    <date year="1995" month="December"/>
     3126  </front>
     3127  <seriesInfo name="Computer Networks and ISDN Systems" value="v. 28, pp. 25-35"/>
     3128  <annotation>
     3129    Slightly revised version of paper in Proc. 2nd International WWW Conference '94: Mosaic and the Web, Oct. 1994,
     3130    which is available at <eref target="http://www.ncsa.uiuc.edu/SDG/IT94/Proceedings/DDay/mogul/HTTPLatency.html"/>.
     3131  </annotation>
     3132</reference>
     3133
     3134<reference anchor="RFC822">
     3135  <front>
     3136    <title abbrev="Standard for ARPA Internet Text Messages">Standard for the format of ARPA Internet text messages</title>
     3137    <author initials="D.H." surname="Crocker" fullname="David H. Crocker">
     3138      <organization>University of Delaware, Dept. of Electrical Engineering</organization>
     3139      <address><email>DCrocker@UDel-Relay</email></address>
     3140    </author>
     3141    <date month="August" day="13" year="1982"/>
     3142  </front>
     3143  <seriesInfo name="STD" value="11"/>
     3144  <seriesInfo name="RFC" value="822"/>
     3145</reference>
     3146
     3147<reference anchor="RFC959">
     3148  <front>
     3149    <title abbrev="File Transfer Protocol">File Transfer Protocol</title>
     3150    <author initials="J." surname="Postel" fullname="J. Postel">
     3151      <organization>Information Sciences Institute (ISI)</organization>
     3152    </author>
     3153    <author initials="J." surname="Reynolds" fullname="J. Reynolds">
     3154      <organization/>
     3155    </author>
     3156    <date month="October" year="1985"/>
     3157  </front>
     3158  <seriesInfo name="STD" value="9"/>
     3159  <seriesInfo name="RFC" value="959"/>
     3160</reference>
     3161
     3162<reference anchor="RFC1123">
     3163  <front>
     3164    <title>Requirements for Internet Hosts - Application and Support</title>
     3165    <author initials="R." surname="Braden" fullname="Robert Braden">
     3166      <organization>University of Southern California (USC), Information Sciences Institute</organization>
     3167      <address><email>Braden@ISI.EDU</email></address>
     3168    </author>
     3169    <date month="October" year="1989"/>
     3170  </front>
     3171  <seriesInfo name="STD" value="3"/>
     3172  <seriesInfo name="RFC" value="1123"/>
     3173</reference>
     3174
     3175<reference anchor="RFC1305">
     3176  <front>
     3177    <title>Network Time Protocol (Version 3) Specification, Implementation</title>
     3178    <author initials="D." surname="Mills" fullname="David L. Mills">
     3179      <organization>University of Delaware, Electrical Engineering Department</organization>
     3180      <address><email>mills@udel.edu</email></address>
     3181    </author>
     3182    <date month="March" year="1992"/>
     3183  </front>
     3184  <seriesInfo name="RFC" value="1305"/>
     3185</reference>
     3186
     3187<reference anchor="RFC1436">
     3188  <front>
     3189    <title abbrev="Gopher">The Internet Gopher Protocol (a distributed document search and retrieval protocol)</title>
     3190    <author initials="F." surname="Anklesaria" fullname="Farhad Anklesaria">
     3191      <organization>University of Minnesota, Computer and Information Services</organization>
     3192      <address><email>fxa@boombox.micro.umn.edu</email></address>
     3193    </author>
     3194    <author initials="M." surname="McCahill" fullname="Mark McCahill">
     3195      <organization>University of Minnesota, Computer and Information Services</organization>
     3196      <address><email>mpm@boombox.micro.umn.edu</email></address>
     3197    </author>
     3198    <author initials="P." surname="Lindner" fullname="Paul Lindner">
     3199      <organization>University of Minnesota, Computer and Information Services</organization>
     3200      <address><email>lindner@boombox.micro.umn.edu</email></address>
     3201    </author>
     3202    <author initials="D." surname="Johnson" fullname="David Johnson">
     3203      <organization>University of Minnesota, Computer and Information Services</organization>
     3204      <address><email>dmj@boombox.micro.umn.edu</email></address>
     3205    </author>
     3206    <author initials="D." surname="Torrey" fullname="Daniel Torrey">
     3207      <organization>University of Minnesota, Computer and Information Services</organization>
     3208      <address><email>daniel@boombox.micro.umn.edu</email></address>
     3209    </author>
     3210    <author initials="B." surname="Alberti" fullname="Bob Alberti">
     3211      <organization>University of Minnesota, Computer and Information Services</organization>
     3212      <address><email>alberti@boombox.micro.umn.edu</email></address>
     3213    </author>
     3214    <date month="March" year="1993"/>
     3215  </front>
     3216  <seriesInfo name="RFC" value="1436"/>
     3217</reference>
     3218
     3219<reference anchor="RFC1630">
     3220  <front>
     3221    <title abbrev="URIs in WWW">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</title>
     3222    <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
     3223      <organization>CERN, World-Wide Web project</organization>
     3224      <address><email>timbl@info.cern.ch</email></address>
     3225    </author>
     3226    <date month="June" year="1994"/>
     3227  </front>
     3228  <seriesInfo name="RFC" value="1630"/>
     3229</reference>
     3230
     3231<reference anchor="RFC1738">
     3232  <front>
     3233    <title>Uniform Resource Locators (URL)</title>
     3234    <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
     3235      <organization>CERN, World-Wide Web project</organization>
     3236      <address><email>timbl@info.cern.ch</email></address>
     3237    </author>
     3238    <author initials="L." surname="Masinter" fullname="Larry Masinter">
     3239      <organization>Xerox PARC</organization>
     3240      <address><email>masinter@parc.xerox.com</email></address>
     3241    </author>
     3242    <author initials="M." surname="McCahill" fullname="Mark McCahill">
     3243      <organization>University of Minnesota, Computer and Information Services</organization>
     3244      <address><email>mpm@boombox.micro.umn.edu</email></address>
     3245    </author>
     3246    <date month="December" year="1994"/>
     3247  </front>
     3248  <seriesInfo name="RFC" value="1738"/>
     3249</reference>
     3250
     3251<reference anchor="RFC1808">
     3252  <front>
     3253    <title>Relative Uniform Resource Locators</title>
     3254    <author initials="R." surname="Fielding" fullname="Roy T. Fielding">
     3255      <organization>University of California Irvine, Department of Information and Computer Science</organization>
     3256      <address><email>fielding@ics.uci.edu</email></address>
     3257    </author>
     3258    <date month="June" year="1995"/>
     3259  </front>
     3260  <seriesInfo name="RFC" value="1808"/>
     3261</reference>
     3262
     3263<reference anchor="RFC1900">
     3264  <front>
     3265    <title>Renumbering Needs Work</title>
     3266    <author initials="B." surname="Carpenter" fullname="Brian E. Carpenter">
     3267      <organization>CERN, Computing and Networks Division</organization>
     3268      <address><email>brian@dxcoms.cern.ch</email></address>
     3269    </author>
     3270    <author initials="Y." surname="Rekhter" fullname="Yakov Rekhter">
     3271      <organization>cisco Systems</organization>
     3272      <address><email>yakov@cisco.com</email></address>
     3273    </author>
     3274    <date month="February" year="1996"/>
     3275  </front>
     3276  <seriesInfo name="RFC" value="1900"/>
     3277</reference>
     3278
     3279<reference anchor="RFC1945">
     3280  <front>
     3281    <title abbrev="HTTP/1.0">Hypertext Transfer Protocol -- HTTP/1.0</title>
     3282    <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
     3283      <organization>MIT, Laboratory for Computer Science</organization>
     3284      <address><email>timbl@w3.org</email></address>
     3285    </author>
     3286    <author initials="R.T." surname="Fielding" fullname="Roy T. Fielding">
     3287      <organization>University of California, Irvine, Department of Information and Computer Science</organization>
     3288      <address><email>fielding@ics.uci.edu</email></address>
     3289    </author>
     3290    <author initials="H.F." surname="Nielsen" fullname="Henrik Frystyk Nielsen">
     3291      <organization>W3 Consortium, MIT Laboratory for Computer Science</organization>
     3292      <address><email>frystyk@w3.org</email></address>
     3293    </author>
     3294    <date month="May" year="1996"/>
     3295  </front>
     3296  <seriesInfo name="RFC" value="1945"/>
     3297</reference>
     3298
    30803299<reference anchor="RFC2068">
    30813300  <front>
     
    31063325</reference>
    31073326
     3327<reference anchor="RFC2145">
     3328  <front>
     3329    <title abbrev="HTTP Version Numbers">Use and Interpretation of HTTP Version Numbers</title>
     3330    <author initials="J.C." surname="Mogul" fullname="Jeffrey C. Mogul">
     3331      <organization>Western Research Laboratory</organization>
     3332      <address><email>mogul@wrl.dec.com</email></address>
     3333    </author>
     3334    <author initials="R.T." surname="Fielding" fullname="Roy T. Fielding">
     3335      <organization>Department of Information and Computer Science</organization>
     3336      <address><email>fielding@ics.uci.edu</email></address>
     3337    </author>
     3338    <author initials="J." surname="Gettys" fullname="Jim Gettys">
     3339      <organization>MIT Laboratory for Computer Science</organization>
     3340      <address><email>jg@w3.org</email></address>
     3341    </author>
     3342    <author initials="H.F." surname="Nielsen" fullname="Henrik Frystyk Nielsen">
     3343      <organization>W3 Consortium</organization>
     3344      <address><email>frystyk@w3.org</email></address>
     3345    </author>
     3346    <date month="May" year="1997"/>
     3347  </front>
     3348  <seriesInfo name="RFC" value="2145"/>
     3349</reference>
     3350
     3351<reference anchor="RFC2324">
     3352  <front>
     3353    <title abbrev="HTCPCP/1.0">Hyper Text Coffee Pot Control Protocol (HTCPCP/1.0)</title>
     3354    <author initials="L." surname="Masinter" fullname="Larry Masinter">
     3355      <organization>Xerox Palo Alto Research Center</organization>
     3356      <address><email>masinter@parc.xerox.com</email></address>
     3357    </author>
     3358    <date month="April" day="1" year="1998"/>
     3359  </front>
     3360  <seriesInfo name="RFC" value="2324"/>
     3361</reference>
     3362
    31083363<reference anchor="RFC2616">
    31093364  <front>
     
    31423397</reference>
    31433398
     3399<reference anchor="RFC2821">
     3400  <front>
     3401    <title>Simple Mail Transfer Protocol</title>
     3402    <author initials="J." surname="Klensin" fullname="J. Klensin">
     3403      <organization>AT&amp;T Laboratories</organization>
     3404      <address><email>klensin@research.att.com</email></address>
     3405    </author>
     3406    <date year="2001" month="April"/>
     3407  </front>
     3408  <seriesInfo name="RFC" value="2821"/>
     3409</reference>
     3410
    31443411<reference anchor='RFC3977'>
    31453412  <front>
     
    31543421</reference>
    31553422
     3423<reference anchor="Spe" target="http://sunsite.unc.edu/mdma-release/http-prob.html">
     3424  <front>
     3425  <title>Analysis of HTTP Performance Problems</title>
     3426  <author initials="S." surname="Spero" fullname="Simon E. Spero">
     3427    <organization/>
     3428  </author>
     3429  <date/>
     3430  </front>
     3431</reference>
     3432
     3433<reference anchor="Tou1998" target="http://www.isi.edu/touch/pubs/http-perf96/">
     3434  <front>
     3435  <title>Analysis of HTTP Performance</title>
     3436  <author initials="J." surname="Touch" fullname="Joe Touch">
     3437    <organization>USC/Information Sciences Institute</organization>
     3438    <address><email>touch@isi.edu</email></address>
     3439  </author>
     3440  <author initials="J." surname="Heidemann" fullname="John Heidemann">
     3441    <organization>USC/Information Sciences Institute</organization>
     3442    <address><email>johnh@isi.edu</email></address>
     3443  </author>
     3444  <author initials="K." surname="Obraczka" fullname="Katia Obraczka">
     3445    <organization>USC/Information Sciences Institute</organization>
     3446    <address><email>katia@isi.edu</email></address>
     3447  </author>
     3448  <date year="1998" month="Aug"/>
     3449  </front>
     3450  <seriesInfo name="ISI Research Report" value="ISI/RR-98-463"/>
     3451  <annotation>(original report dated Aug. 1996)</annotation>
     3452</reference>
     3453
     3454<reference anchor="WAIS">
     3455  <front>
     3456    <title>WAIS Interface Protocol Prototype Functional Specification (v1.5)</title>
     3457    <author initials="F." surname="Davis" fullname="F. Davis">
     3458      <organization>Thinking Machines Corporation</organization>
     3459    </author>
     3460    <author initials="B." surname="Kahle" fullname="B. Kahle">
     3461      <organization>Thinking Machines Corporation</organization>
     3462    </author>
     3463    <author initials="H." surname="Morris" fullname="H. Morris">
     3464      <organization>Thinking Machines Corporation</organization>
     3465    </author>
     3466    <author initials="J." surname="Salem" fullname="J. Salem">
     3467      <organization>Thinking Machines Corporation</organization>
     3468    </author>
     3469    <author initials="T." surname="Shen" fullname="T. Shen">
     3470      <organization>Thinking Machines Corporation</organization>
     3471    </author>
     3472    <author initials="R." surname="Wang" fullname="R. Wang">
     3473      <organization>Thinking Machines Corporation</organization>
     3474    </author>
     3475    <author initials="J." surname="Sui" fullname="J. Sui">
     3476      <organization>Thinking Machines Corporation</organization>
     3477    </author>
     3478    <author initials="M." surname="Grinbaum" fullname="M. Grinbaum">
     3479      <organization>Thinking Machines Corporation</organization>
     3480    </author>
     3481    <date month="April" year="1990"/>
     3482  </front>
     3483  <seriesInfo name="Thinking Machines Corporation" value=""/>
     3484</reference>
     3485
    31563486</references>
    31573487
    31583488<references title="References (to be categorized)">
    3159 
    3160 <reference anchor="RFC1436">
    3161 <front>
    3162 <title abbrev="Gopher">The Internet Gopher Protocol (a distributed document search and retrieval protocol)</title>
    3163 <author initials="F." surname="Anklesaria" fullname="Farhad Anklesaria">
    3164 <organization>University of Minnesota, Computer and Information Services</organization>
    3165 <address>
    3166 <postal>
    3167 <street>100 Union Street SE</street>
    3168 <street>Room 152 Shepherd Labs</street>
    3169 <city>Minneapolis</city>
    3170 <region>MN</region>
    3171 <code>55455</code>
    3172 <country>US</country></postal>
    3173 <phone>+1 612 625 1300</phone>
    3174 <email>fxa@boombox.micro.umn.edu</email></address></author>
    3175 <author initials="M." surname="McCahill" fullname="Mark McCahill">
    3176 <organization>University of Minnesota, Computer and Information Services</organization>
    3177 <address>
    3178 <postal>
    3179 <street>100 Union Street SE</street>
    3180 <street>Room 152 Shepherd Labs</street>
    3181 <city>Minneapolis</city>
    3182 <region>MN</region>
    3183 <code>55455</code>
    3184 <country>US</country></postal>
    3185 <phone>+1 612 625 1300</phone>
    3186 <email>mpm@boombox.micro.umn.edu</email></address></author>
    3187 <author initials="P." surname="Lindner" fullname="Paul Lindner">
    3188 <organization>University of Minnesota, Computer and Information Services</organization>
    3189 <address>
    3190 <postal>
    3191 <street>100 Union Street SE</street>
    3192 <street>Room 152 Shepherd Labs</street>
    3193 <city>Minneapolis</city>
    3194 <region>MN</region>
    3195 <code>55455</code>
    3196 <country>US</country></postal>
    3197 <phone>+1 612 625 1300</phone>
    3198 <email>lindner@boombox.micro.umn.edu</email></address></author>
    3199 <author initials="D." surname="Johnson" fullname="David Johnson">
    3200 <organization>University of Minnesota, Computer and Information Services</organization>
    3201 <address>
    3202 <postal>
    3203 <street>100 Union Street SE</street>
    3204 <street>Room 152 Shepherd Labs</street>
    3205 <city>Minneapolis</city>
    3206 <region>MN</region>
    3207 <code>55455</code>
    3208 <country>US</country></postal>
    3209 <phone>+1 612 625 1300</phone>
    3210 <email>dmj@boombox.micro.umn.edu</email></address></author>
    3211 <author initials="D." surname="Torrey" fullname="Daniel Torrey">
    3212 <organization>University of Minnesota, Computer and Information Services</organization>
    3213 <address>
    3214 <postal>
    3215 <street>100 Union Street SE</street>
    3216 <street>Room 152 Shepherd Labs</street>
    3217 <city>Minneapolis</city>
    3218 <region>MN</region>
    3219 <code>55455</code>
    3220 <country>US</country></postal>
    3221 <phone>+1 612 625 1300</phone>
    3222 <email>daniel@boombox.micro.umn.edu</email></address></author>
    3223 <author initials="B." surname="Alberti" fullname="Bob Alberti">
    3224 <organization>University of Minnesota, Computer and Information Services</organization>
    3225 <address>
    3226 <postal>
    3227 <street>100 Union Street SE</street>
    3228 <street>Room 152 Shepherd Labs</street>
    3229 <city>Minneapolis</city>
    3230 <region>MN</region>
    3231 <code>55455</code>
    3232 <country>US</country></postal>
    3233 <phone>+1 612 625 1300</phone>
    3234 <email>alberti@boombox.micro.umn.edu</email></address></author>
    3235 <date month="March" year="1993"/>
    3236 </front>
    3237 <seriesInfo name="RFC" value="1436"/>
    3238 </reference>
    3239 
    3240 <reference anchor="RFC1630">
    3241 <front>
    3242 <title abbrev="URIs in WWW">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</title>
    3243 <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
    3244 <organization>CERN, World-Wide Web project</organization>
    3245 <address>
    3246 <postal>
    3247 <street>1211 Geneva 23</street>
    3248 <city/>
    3249 <region/>
    3250 <code/>
    3251 <country>CH</country></postal>
    3252 <phone>+41 22 7673755</phone>
    3253 <facsimile>+41 22 7677155</facsimile>
    3254 <email>timbl@info.cern.ch</email></address></author>
    3255 <date month="June" year="1994"/></front>
    3256 <seriesInfo name="RFC" value="1630"/>
    3257 </reference>
    3258 
    3259 <reference anchor="RFC1738">
    3260   <front>
    3261     <title>Uniform Resource Locators (URL)</title>
    3262     <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
    3263       <organization>CERN, World-Wide Web project</organization>
    3264       <address><email>timbl@info.cern.ch</email></address>
    3265     </author>
    3266     <author initials="L." surname="Masinter" fullname="Larry Masinter">
    3267       <organization>Xerox PARC</organization>
    3268       <address><email>masinter@parc.xerox.com</email></address>
    3269     </author>
    3270     <author initials="M." surname="McCahill" fullname="Mark McCahill">
    3271       <organization>University of Minnesota, Computer and Information Services</organization>
    3272       <address><email>mpm@boombox.micro.umn.edu</email></address>
    3273     </author>
    3274     <date month="December" year="1994"/>
    3275   </front>
    3276   <seriesInfo name="RFC" value="1738"/>
    3277 </reference>
    3278 
    3279 <reference anchor="RFC1945">
    3280   <front>
    3281     <title abbrev="HTTP/1.0">Hypertext Transfer Protocol -- HTTP/1.0</title>
    3282     <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
    3283       <organization>MIT, Laboratory for Computer Science</organization>
    3284       <address><email>timbl@w3.org</email></address>
    3285     </author>
    3286     <author initials="R.T." surname="Fielding" fullname="Roy T. Fielding">
    3287       <organization>University of California, Irvine, Department of Information and Computer Science</organization>
    3288       <address><email>fielding@ics.uci.edu</email></address>
    3289     </author>
    3290     <author initials="H.F." surname="Nielsen" fullname="Henrik Frystyk Nielsen">
    3291       <organization>W3 Consortium, MIT Laboratory for Computer Science</organization>
    3292       <address><email>frystyk@w3.org</email></address>
    3293     </author>
    3294     <date month="May" year="1996"/>
    3295   </front>
    3296   <seriesInfo name="RFC" value="1945"/>
    3297 </reference>
    32983489
    32993490<reference anchor="RFC2045">
     
    33133504</reference>
    33143505
    3315 <reference anchor="RFC1123">
    3316   <front>
    3317     <title>Requirements for Internet Hosts - Application and Support</title>
    3318     <author initials="R." surname="Braden" fullname="Robert Braden">
    3319       <organization>University of Southern California (USC), Information Sciences Institute</organization>
    3320       <address><email>Braden@ISI.EDU</email></address>
    3321     </author>
    3322     <date month="October" year="1989"/>
    3323   </front>
    3324   <seriesInfo name="STD" value="3"/>
    3325   <seriesInfo name="RFC" value="1123"/>
    3326 </reference>
    3327 
    3328 <reference anchor="RFC822">
    3329   <front>
    3330     <title abbrev="Standard for ARPA Internet Text Messages">Standard for the format of ARPA Internet text messages</title>
    3331     <author initials="D.H." surname="Crocker" fullname="David H. Crocker">
    3332       <organization>University of Delaware, Dept. of Electrical Engineering</organization>
    3333       <address><email>DCrocker@UDel-Relay</email></address>
    3334     </author>
    3335     <date month="August" day="13" year="1982"/>
    3336   </front>
    3337   <seriesInfo name="STD" value="11"/>
    3338   <seriesInfo name="RFC" value="822"/>
    3339 </reference>
    3340 
    3341 <reference anchor="WAIS">
    3342 <front>
    3343 <title>WAIS Interface Protocol Prototype Functional Specification (v1.5)</title>
    3344 <author initials="F." surname="Davis" fullname="F. Davis">
    3345 <organization>Thinking Machines Corporation</organization>
    3346 </author>
    3347 <author initials="B." surname="Kahle" fullname="B. Kahle">
    3348 <organization>Thinking Machines Corporation</organization>
    3349 </author>
    3350 <author initials="H." surname="Morris" fullname="H. Morris">
    3351 <organization>Thinking Machines Corporation</organization>
    3352 </author>
    3353 <author initials="J." surname="Salem" fullname="J. Salem">
    3354 <organization>Thinking Machines Corporation</organization>
    3355 </author>
    3356 <author initials="T." surname="Shen" fullname="T. Shen">
    3357 <organization>Thinking Machines Corporation</organization>
    3358 </author>
    3359 <author initials="R." surname="Wang" fullname="R. Wang">
    3360 <organization>Thinking Machines Corporation</organization>
    3361 </author>
    3362 <author initials="J." surname="Sui" fullname="J. Sui">
    3363 <organization>Thinking Machines Corporation</organization>
    3364 </author>
    3365 <author initials="M." surname="Grinbaum" fullname="M. Grinbaum">
    3366 <organization>Thinking Machines Corporation</organization>
    3367 </author>
    3368 <date month="April" year="1990"/></front>
    3369 <seriesInfo name="Thinking Machines Corporation" value=""/>
    3370 </reference>
    3371 
    3372 <reference anchor="RFC1808">
    3373   <front>
    3374     <title>Relative Uniform Resource Locators</title>
    3375     <author initials="R." surname="Fielding" fullname="Roy T. Fielding">
    3376       <organization>University of California Irvine, Department of Information and Computer Science</organization>
    3377       <address><email>fielding@ics.uci.edu</email></address>
    3378     </author>
    3379     <date month="June" year="1995"/>
    3380   </front>
    3381   <seriesInfo name="RFC" value="1808"/>
    3382 </reference>
    3383 
    33843506<reference anchor="RFC2047">
    33853507  <front>
     
    33923514  </front>
    33933515  <seriesInfo name="RFC" value="2047"/>
    3394 </reference>
    3395 
    3396 <reference anchor="RFC821">
    3397 <front>
    3398 <title>Simple Mail Transfer Protocol</title>
    3399 <author initials="J.B." surname="Postel" fullname="Jonathan B. Postel">
    3400 <organization>University of Southern California (USC)/Information Sciences Institute</organization>
    3401 <address>
    3402 <postal>
    3403 <street>4676 Admiralty Way</street>
    3404 <city>Marina del Rey</city>
    3405 <region>CA</region>
    3406 <code>90291</code>
    3407 <country>US</country></postal>
    3408 <phone>+1 213 822 1511</phone></address></author>
    3409 <date month="August" year="1982"/></front>
    3410 <seriesInfo name="STD" value="10"/>
    3411 <seriesInfo name="RFC" value="821"/>
    34123516</reference>
    34133517
     
    34313535  <seriesInfo name="BCP" value="13"/>
    34323536  <seriesInfo name="RFC" value="4288"/>
    3433 </reference>
    3434 
    3435 <reference anchor="RFC959">
    3436 <front>
    3437 <title abbrev="File Transfer Protocol">File Transfer Protocol</title>
    3438 <author initials="J." surname="Postel" fullname="J. Postel">
    3439 <organization>Information Sciences Institute (ISI)</organization></author>
    3440 <author initials="J." surname="Reynolds" fullname="J. Reynolds">
    3441 <organization/></author>
    3442 <date month="October" year="1985"/></front>
    3443 <seriesInfo name="STD" value="9"/>
    3444 <seriesInfo name="RFC" value="959"/>
    34453537</reference>
    34463538
     
    34863578</reference>
    34873579
    3488 <reference anchor="RFC1900">
    3489   <front>
    3490     <title>Renumbering Needs Work</title>
    3491     <author initials="B." surname="Carpenter" fullname="Brian E. Carpenter">
    3492       <organization>CERN, Computing and Networks Division</organization>
    3493       <address><email>brian@dxcoms.cern.ch</email></address>
    3494     </author>
    3495     <author initials="Y." surname="Rekhter" fullname="Yakov Rekhter">
    3496       <organization>cisco Systems</organization>
    3497       <address><email>yakov@cisco.com</email></address>
    3498     </author>
    3499     <date month="February" year="1996"/>
    3500   </front>
    3501   <seriesInfo name="RFC" value="1900"/>
    3502 </reference>
    3503 
    3504 <reference anchor="Pad1995">
    3505 <front>
    3506 <title>Improving HTTP Latency</title>
    3507 <author initials="V.N." surname="Padmanabhan" fullname="Venkata N. Padmanabhan"><organization/></author>
    3508 <author initials="J.C." surname="Mogul" fullname="Jeffrey C. Mogul"><organization/></author>
    3509 <date year="1995" month="Dec"/>
    3510 </front>
    3511 <seriesInfo name="Computer Networks and ISDN Systems" value="v. 28, pp. 25-35"/>
    3512 <annotation>
    3513   Slightly revised version of paper in Proc. 2nd International WWW Conference '94: Mosaic and the Web, Oct. 1994,
    3514   which is available at <eref target="http://www.ncsa.uiuc.edu/SDG/IT94/Proceedings/DDay/mogul/HTTPLatency.html"/>.
    3515 </annotation>
    3516 </reference>
    3517 
    3518 <reference anchor="Tou1998" target="http://www.isi.edu/touch/pubs/http-perf96/">
    3519 <front>
    3520 <title>Analysis of HTTP Performance</title>
    3521 <author initials="J." surname="Touch" fullname="Joe Touch">
    3522   <organization>USC/Information Sciences Institute</organization>
    3523   <address><email>touch@isi.edu</email></address>
    3524 </author>
    3525 <author initials="J." surname="Heidemann" fullname="John Heidemann">
    3526   <organization>USC/Information Sciences Institute</organization>
    3527   <address><email>johnh@isi.edu</email></address>
    3528 </author>
    3529 <author initials="K." surname="Obraczka" fullname="Katia Obraczka">
    3530   <organization>USC/Information Sciences Institute</organization>
    3531   <address><email>katia@isi.edu</email></address>
    3532 </author>
    3533 <date year="1998" month="Aug"/>
    3534 </front>
    3535 <seriesInfo name="ISI Research Report" value="ISI/RR-98-463 (original report dated Aug.1996)"/>
    3536 </reference>
    3537 
    3538 <reference anchor="RFC1305">
    3539 <front>
    3540 <title>Network Time Protocol (Version 3) Specification, Implementation</title>
    3541 <author initials="D." surname="Mills" fullname="David L. Mills">
    3542 <organization>University of Delaware, Electrical Engineering Department</organization>
    3543 <address>
    3544 <postal>
    3545 <street/>
    3546 <city>Newark</city>
    3547 <region>DE</region>
    3548 <code>19716</code>
    3549 <country>US</country></postal>
    3550 <phone>+1 302 451 8247</phone>
    3551 <email>mills@udel.edu</email></address></author>
    3552 <date month="March" year="1992"/>
    3553 <abstract>
    3554 <t>This document describes the Network Time Protocol (NTP), specifies its normal structure and summarizes information useful for its implementation. NTP provides the mechanisms to synchronize time and coordinate time distribution in a large, diverse internet operating at rates from mundane to lightwave. It uses a returnable-time design in which a distributed subnet of time servers operating in a self-organizing, hierarchical-master-slave configuration synchronizes local clocks within the subnet and to national time standards via wire or radio. The servers can also redistribute reference time via local routing algorithms and time daemons.</t></abstract></front>
    3555 <seriesInfo name="RFC" value="1305"/>
    3556 </reference>
    3557 
    3558 <reference anchor="Spe" target="http://sunsite.unc.edu/mdma-release/http-prob.html">
    3559 <front>
    3560 <title>Analysis of HTTP Performance Problems</title>
    3561 <author initials="S." surname="Spero" fullname="Simon E. Spero">
    3562   <organization/>
    3563 </author>
    3564 <date/>
    3565 </front>
    3566 </reference>
    3567 
    3568 <reference anchor="RFC2145">
    3569   <front>
    3570     <title abbrev="HTTP Version Numbers">Use and Interpretation of HTTP Version Numbers</title>
    3571     <author initials="J.C." surname="Mogul" fullname="Jeffrey C. Mogul">
    3572       <organization>Western Research Laboratory</organization>
    3573       <address><email>mogul@wrl.dec.com</email></address>
    3574     </author>
    3575     <author initials="R.T." surname="Fielding" fullname="Roy T. Fielding">
    3576       <organization>Department of Information and Computer Science</organization>
    3577       <address><email>fielding@ics.uci.edu</email></address>
    3578     </author>
    3579     <author initials="J." surname="Gettys" fullname="Jim Gettys">
    3580       <organization>MIT Laboratory for Computer Science</organization>
    3581       <address><email>jg@w3.org</email></address>
    3582     </author>
    3583     <author initials="H.F." surname="Nielsen" fullname="Henrik Frystyk Nielsen">
    3584       <organization>W3 Consortium</organization>
    3585       <address><email>frystyk@w3.org</email></address>
    3586     </author>
    3587     <date month="May" year="1997"/>
    3588   </front>
    3589   <seriesInfo name="RFC" value="2145"/>
    3590 </reference>
    3591 
    3592 <reference anchor="Nie1997">
    3593 <front>
    3594 <title>Network Performance Effects of HTTP/1.1, CSS1, and PNG</title>
    3595 <author initials="H.F.." surname="Nielsen" fullname="H.F. Nielsen">
    3596   <organization/>
    3597 </author>
    3598 <author initials="J." surname="Gettys" fullname="J. Gettys">
    3599   <organization/>
    3600 </author>
    3601 <author initials="E." surname="Prud'hommeaux" fullname="E. Prud'hommeaux">
    3602   <organization/>
    3603 </author>
    3604 <author initials="H." surname="Lie" fullname="H. Lie">
    3605   <organization/>
    3606 </author>
    3607 <author initials="C." surname="Lilley" fullname="C. Lilley">
    3608   <organization/>
    3609 </author>
    3610 <date year="1997" month="Sep"/>
    3611 </front>
    3612 <seriesInfo name="Proceedings of ACM SIGCOMM '97, Cannes France" value=""/>
    3613 </reference>
    3614 
    36153580<reference anchor="RFC2396">
    36163581  <front>
     
    36313596  </front>
    36323597  <seriesInfo name="RFC" value="2396"/>
    3633 </reference>
    3634 
    3635 <reference anchor="RFC2324">
    3636 <front>
    3637 <title abbrev="HTCPCP/1.0">Hyper Text Coffee Pot Control Protocol (HTCPCP/1.0)</title>
    3638 <author initials="L." surname="Masinter" fullname="Larry Masinter">
    3639 <organization>Xerox Palo Alto Research Center</organization>
    3640 <address>
    3641 <postal>
    3642 <street>3333 Coyote Hill Road</street>
    3643 <city>Palo Alto</city>
    3644 <region>CA</region>
    3645 <code>94304</code></postal>
    3646 <email>masinter@parc.xerox.com</email></address></author>
    3647 <date month="April" day="1" year="1998"/>
    3648 <area>General</area>
    3649 <keyword>control protocol</keyword>
    3650 <keyword>coffee</keyword>
    3651 </front>
    3652 <seriesInfo name="RFC" value="2324"/>
    36533598</reference>
    36543599
     
    40584003    </t>
    40594004    <t>
     4005      <eref target="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/65"/>:
     4006      "Informative references"
     4007    </t>
     4008    <t>
    40604009      <eref target="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/66"/>:
    40614010      "ISO-8859-1 Reference"
  • draft-ietf-httpbis/latest/p2-semantics.html

    r124 r129  
    591591               <li class="tocline1">14.1&nbsp;&nbsp;&nbsp;<a href="#rfc.references.1">Normative References</a></li>
    592592               <li class="tocline1">14.2&nbsp;&nbsp;&nbsp;<a href="#rfc.references.2">Informative References</a></li>
    593                <li class="tocline1">14.3&nbsp;&nbsp;&nbsp;<a href="#rfc.references.3">References (to be categorized)</a></li>
    594593            </ul>
    595594         </li>
     
    16021601      <h2 id="rfc.references.2"><a href="#rfc.section.14.2" id="rfc.section.14.2">14.2</a> Informative References
    16031602      </h2>
    1604       <table summary="Informative References">   
     1603      <table summary="Informative References">           
     1604         <tr>
     1605            <td class="reference"><b id="Luo1998">[Luo1998]</b></td>
     1606            <td class="top">Luotonen, A., “<a href="http://tools.ietf.org/html/draft-luotonen-web-proxy-tunneling-01">Tunneling TCP based protocols through Web proxy servers</a>”, Internet-Draft&nbsp;draft-luotonen-web-proxy-tunneling-01 (work in progress), August&nbsp;1998.
     1607            </td>
     1608         </tr>
     1609         <tr>
     1610            <td class="reference"><b id="RFC1123">[RFC1123]</b></td>
     1611            <td class="top"><a title="University of Southern California (USC), Information Sciences Institute">Braden, R.</a>, “<a href="http://tools.ietf.org/html/rfc1123">Requirements for Internet Hosts - Application and Support</a>”, STD&nbsp;3, RFC&nbsp;1123, October&nbsp;1989.
     1612            </td>
     1613         </tr>
     1614         <tr>
     1615            <td class="reference"><b id="RFC1945">[RFC1945]</b></td>
     1616            <td class="top"><a title="MIT, Laboratory for Computer Science">Berners-Lee, T.</a>, <a title="University of California, Irvine, Department of Information and Computer Science">Fielding, R.T.</a>, and <a title="W3 Consortium, MIT Laboratory for Computer Science">H.F. Nielsen</a>, “<a href="http://tools.ietf.org/html/rfc1945">Hypertext Transfer Protocol -- HTTP/1.0</a>”, RFC&nbsp;1945, May&nbsp;1996.
     1617            </td>
     1618         </tr>
    16051619         <tr>
    16061620            <td class="reference"><b id="RFC2068">[RFC2068]</b></td>
     
    16111625            <td class="reference"><b id="RFC2616">[RFC2616]</b></td>
    16121626            <td class="top"><a title="University of California, Irvine">Fielding, R.</a>, <a title="W3C">Gettys, J.</a>, <a title="Compaq Computer Corporation">Mogul, J.</a>, <a title="MIT Laboratory for Computer Science">Frystyk, H.</a>, <a title="Xerox Corporation">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, and <a title="W3C">T. Berners-Lee</a>, “<a href="http://tools.ietf.org/html/rfc2616">Hypertext Transfer Protocol -- HTTP/1.1</a>”, RFC&nbsp;2616, June&nbsp;1999.
    1613             </td>
    1614          </tr>
    1615       </table>
    1616       <h2 id="rfc.references.3"><a href="#rfc.section.14.3" id="rfc.section.14.3">14.3</a> References (to be categorized)
    1617       </h2>
    1618       <table summary="References (to be categorized)">       
    1619          <tr>
    1620             <td class="reference"><b id="Luo1998">[Luo1998]</b></td>
    1621             <td class="top">Luotonen, A., “Tunneling TCP based protocols through Web proxy servers”, &nbsp;Work in Progress.</td>
    1622          </tr>
    1623          <tr>
    1624             <td class="reference"><b id="RFC1123">[RFC1123]</b></td>
    1625             <td class="top"><a title="University of Southern California (USC), Information Sciences Institute">Braden, R.</a>, “<a href="http://tools.ietf.org/html/rfc1123">Requirements for Internet Hosts - Application and Support</a>”, STD&nbsp;3, RFC&nbsp;1123, October&nbsp;1989.
    1626             </td>
    1627          </tr>
    1628          <tr>
    1629             <td class="reference"><b id="RFC1945">[RFC1945]</b></td>
    1630             <td class="top"><a title="MIT, Laboratory for Computer Science">Berners-Lee, T.</a>, <a title="University of California, Irvine, Department of Information and Computer Science">Fielding, R.T.</a>, and <a title="W3 Consortium, MIT Laboratory for Computer Science">H.F. Nielsen</a>, “<a href="http://tools.ietf.org/html/rfc1945">Hypertext Transfer Protocol -- HTTP/1.0</a>”, RFC&nbsp;1945, May&nbsp;1996.
    16311627            </td>
    16321628         </tr>
     
    17131709         <li> &lt;<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/42">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/42</a>&gt;: "RFC2606 Compliance"
    17141710         </li>
     1711         <li> &lt;<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/65">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/65</a>&gt;: "Informative references"
     1712         </li>
    17151713      </ul>
    17161714      <p id="rfc.section.B.2.p.2">Other changes: </p>
     
    17181716         <li>Move definitions of 304 and 412 condition codes to <a href="#Part4" id="rfc.xref.Part4.9"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>
    17191717         </li>
    1720          <li>Start work on categorizing references as "Normative" or "Informative".</li>
     1718         <li>Categorize references as "Normative" or "Informative".</li>
    17211719      </ul>
    17221720      <h1><a id="rfc.copyright" href="#rfc.copyright">Full Copyright Statement</a></h1>
     
    18771875                  <li class="indline1">LINK method&nbsp;&nbsp;<a class="iref" href="#rfc.iref.l.2"><b>A.1</b></a></li>
    18781876                  <li class="indline1">Location header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.location.1">6</a>, <a class="iref" href="#rfc.xref.header.location.2">8.5</a>, <a class="iref" href="#rfc.iref.l.1"><b>10.4</b></a>, <a class="iref" href="#rfc.xref.header.location.3">A.2</a></li>
    1879                   <li class="indline1"><em>Luo1998</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Luo1998.1">8.9</a>, <a class="iref" href="#Luo1998"><b>14.3</b></a></li>
     1877                  <li class="indline1"><em>Luo1998</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Luo1998.1">8.9</a>, <a class="iref" href="#Luo1998"><b>14.2</b></a></li>
    18801878               </ul>
    18811879            </li>
     
    19581956                  <li class="indline1">Referer header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.referer.1">4</a>, <a class="iref" href="#rfc.iref.r.1"><b>10.6</b></a></li>
    19591957                  <li class="indline1">Retry-After header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.retry-after.1">6</a>, <a class="iref" href="#rfc.iref.r.2"><b>10.7</b></a></li>
    1960                   <li class="indline1"><em>RFC1123</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC1123.1">10.3</a>, <a class="iref" href="#RFC1123"><b>14.3</b></a></li>
    1961                   <li class="indline1"><em>RFC1945</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC1945.1">9.3.3</a>, <a class="iref" href="#RFC1945"><b>14.3</b></a></li>
     1958                  <li class="indline1"><em>RFC1123</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC1123.1">10.3</a>, <a class="iref" href="#RFC1123"><b>14.2</b></a></li>
     1959                  <li class="indline1"><em>RFC1945</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC1945.1">9.3.3</a>, <a class="iref" href="#RFC1945"><b>14.2</b></a></li>
    19621960                  <li class="indline1"><em>RFC2068</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2068.1">9.3.3</a>, <a class="iref" href="#rfc.xref.RFC2068.2">9.3.6</a>, <a class="iref" href="#RFC2068"><b>14.2</b></a>, <a class="iref" href="#rfc.xref.RFC2068.3">A.1</a></li>
    19631961                  <li class="indline1"><em>RFC2119</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2119.1">1.1</a>, <a class="iref" href="#RFC2119"><b>14.1</b></a></li>
    19641962                  <li class="indline1"><em>RFC2616</em>&nbsp;&nbsp;<a class="iref" href="#RFC2616"><b>14.2</b></a>, <a class="iref" href="#rfc.xref.RFC2616.1">B.1</a></li>
    1965                   <li class="indline1"><em>RFC822</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC822.1">10.3</a>, <a class="iref" href="#RFC822"><b>14.3</b></a></li>
     1963                  <li class="indline1"><em>RFC822</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC822.1">10.3</a>, <a class="iref" href="#RFC822"><b>14.2</b></a></li>
    19661964               </ul>
    19671965            </li>
  • draft-ietf-httpbis/latest/p2-semantics.xml

    r124 r129  
    23762376<references title="Informative References">
    23772377
     2378<reference anchor="Luo1998">
     2379  <front>
     2380    <title>Tunneling TCP based protocols through Web proxy servers</title>
     2381    <author initials="A." surname="Luotonen" fullname="A. Luotonen">
     2382      <organization/>
     2383    </author>
     2384    <date year="1998" month="August"/>
     2385  </front>
     2386  <seriesInfo name="Internet-Draft" value="draft-luotonen-web-proxy-tunneling-01"/>
     2387</reference>
     2388
     2389<reference anchor="RFC822">
     2390  <front>
     2391    <title abbrev="Standard for ARPA Internet Text Messages">Standard for the format of ARPA Internet text messages</title>
     2392    <author initials="D.H." surname="Crocker" fullname="David H. Crocker">
     2393      <organization>University of Delaware, Dept. of Electrical Engineering</organization>
     2394      <address><email>DCrocker@UDel-Relay</email></address>
     2395    </author>
     2396    <date month="August" day="13" year="1982"/>
     2397  </front>
     2398  <seriesInfo name="STD" value="11"/>
     2399  <seriesInfo name="RFC" value="822"/>
     2400</reference>
     2401
     2402<reference anchor="RFC1123">
     2403  <front>
     2404    <title>Requirements for Internet Hosts - Application and Support</title>
     2405    <author initials="R." surname="Braden" fullname="Robert Braden">
     2406      <organization>University of Southern California (USC), Information Sciences Institute</organization>
     2407      <address><email>Braden@ISI.EDU</email></address>
     2408    </author>
     2409    <date month="October" year="1989"/>
     2410  </front>
     2411  <seriesInfo name="STD" value="3"/>
     2412  <seriesInfo name="RFC" value="1123"/>
     2413</reference>
     2414
     2415<reference anchor="RFC1945">
     2416  <front>
     2417    <title abbrev="HTTP/1.0">Hypertext Transfer Protocol -- HTTP/1.0</title>
     2418    <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
     2419      <organization>MIT, Laboratory for Computer Science</organization>
     2420      <address><email>timbl@w3.org</email></address>
     2421    </author>
     2422    <author initials="R.T." surname="Fielding" fullname="Roy T. Fielding">
     2423      <organization>University of California, Irvine, Department of Information and Computer Science</organization>
     2424      <address><email>fielding@ics.uci.edu</email></address>
     2425    </author>
     2426    <author initials="H.F." surname="Nielsen" fullname="Henrik Frystyk Nielsen">
     2427      <organization>W3 Consortium, MIT Laboratory for Computer Science</organization>
     2428      <address><email>frystyk@w3.org</email></address>
     2429    </author>
     2430    <date month="May" year="1996"/>
     2431  </front>
     2432  <seriesInfo name="RFC" value="1945"/>
     2433</reference>
     2434
    23782435<reference anchor="RFC2068">
    23792436  <front>
     
    24382495  </front>
    24392496  <seriesInfo name="RFC" value="2616"/>
    2440 </reference>
    2441 
    2442 </references>
    2443 
    2444 <references title="References (to be categorized)">
    2445 
    2446 <reference anchor="RFC1123">
    2447   <front>
    2448     <title>Requirements for Internet Hosts - Application and Support</title>
    2449     <author initials="R." surname="Braden" fullname="Robert Braden">
    2450       <organization>University of Southern California (USC), Information Sciences Institute</organization>
    2451       <address><email>Braden@ISI.EDU</email></address>
    2452     </author>
    2453     <date month="October" year="1989"/>
    2454   </front>
    2455   <seriesInfo name="STD" value="3"/>
    2456   <seriesInfo name="RFC" value="1123"/>
    2457 </reference>
    2458 
    2459 <reference anchor="RFC822">
    2460   <front>
    2461     <title abbrev="Standard for ARPA Internet Text Messages">Standard for the format of ARPA Internet text messages</title>
    2462     <author initials="D.H." surname="Crocker" fullname="David H. Crocker">
    2463       <organization>University of Delaware, Dept. of Electrical Engineering</organization>
    2464       <address><email>DCrocker@UDel-Relay</email></address>
    2465     </author>
    2466     <date month="August" day="13" year="1982"/>
    2467   </front>
    2468   <seriesInfo name="STD" value="11"/>
    2469   <seriesInfo name="RFC" value="822"/>
    2470 </reference>
    2471 
    2472 <reference anchor="RFC1945">
    2473   <front>
    2474     <title abbrev="HTTP/1.0">Hypertext Transfer Protocol -- HTTP/1.0</title>
    2475     <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
    2476       <organization>MIT, Laboratory for Computer Science</organization>
    2477       <address><email>timbl@w3.org</email></address>
    2478     </author>
    2479     <author initials="R.T." surname="Fielding" fullname="Roy T. Fielding">
    2480       <organization>University of California, Irvine, Department of Information and Computer Science</organization>
    2481       <address><email>fielding@ics.uci.edu</email></address>
    2482     </author>
    2483     <author initials="H.F." surname="Nielsen" fullname="Henrik Frystyk Nielsen">
    2484       <organization>W3 Consortium, MIT Laboratory for Computer Science</organization>
    2485       <address><email>frystyk@w3.org</email></address>
    2486     </author>
    2487     <date month="May" year="1996"/>
    2488   </front>
    2489   <seriesInfo name="RFC" value="1945"/>
    2490 </reference>
    2491 
    2492 <reference anchor="Luo1998">
    2493 <front>
    2494 <title>Tunneling TCP based protocols through Web proxy servers</title>
    2495 <author initials="A." surname="Luotonen" fullname="A. Luotonen">
    2496   <organization/>
    2497 </author>
    2498 <date/>
    2499 </front>
    2500 <seriesInfo name="" value="Work in Progress"/>
    25012497</reference>
    25022498
     
    26222618      "RFC2606 Compliance"
    26232619    </t>
     2620    <t>
     2621      <eref target="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/65"/>:
     2622      "Informative references"
     2623    </t>
    26242624  </list>
    26252625</t>
     
    26312631    </t>
    26322632    <t>
    2633       Start work on categorizing references as "Normative" or "Informative".
     2633      Categorize references as "Normative" or "Informative".
    26342634    </t>
    26352635  </list>
  • draft-ietf-httpbis/latest/p3-payload.html

    r126 r129  
    603603         of the charset parameter may be quoted.
    604604      </p>
    605       <p id="rfc.section.2.1.p.8">Implementors should be aware of IETF character set requirements <a href="#RFC2279" id="rfc.xref.RFC2279.1"><cite title="UTF-8, a transformation format of ISO 10646">[RFC2279]</cite></a>  <a href="#RFC2277" id="rfc.xref.RFC2277.1"><cite title="IETF Policy on Character Sets and Languages">[RFC2277]</cite></a>.
     605      <p id="rfc.section.2.1.p.8">Implementors should be aware of IETF character set requirements <a href="#RFC3629" id="rfc.xref.RFC3629.1"><cite title="UTF-8, a transformation format of ISO 10646">[RFC3629]</cite></a>  <a href="#RFC2277" id="rfc.xref.RFC2277.1"><cite title="IETF Policy on Character Sets and Languages">[RFC2277]</cite></a>.
    606606      </p>
    607607      <h3 id="rfc.section.2.1.1"><a href="#rfc.section.2.1.1">2.1.1</a>&nbsp;<a id="missing.charset" href="#missing.charset">Missing Charset</a></h3>
     
    712712      <dl class="empty">
    713713         <dd> <b>Note:</b> The "multipart/form-data" type has been specifically defined for carrying form data suitable for processing via the POST request
    714             method, as described in <a href="#RFC1867" id="rfc.xref.RFC1867.1"><cite title="Form-based File Upload in HTML">[RFC1867]</cite></a>.
     714            method, as described in <a href="#RFC2388" id="rfc.xref.RFC2388.1"><cite title="Returning Values from Forms: multipart/form-data">[RFC2388]</cite></a>.
    715715         </dd>
    716716      </dl>
     
    12631263      <h2 id="rfc.references.2"><a href="#rfc.section.9.2" id="rfc.section.9.2">9.2</a> Informative References
    12641264      </h2>
    1265       <table summary="Informative References">   
     1265      <table summary="Informative References">                       
     1266         <tr>
     1267            <td class="reference"><b id="RFC1806">[RFC1806]</b></td>
     1268            <td class="top"><a title="New Century Systems">Troost, R.</a> and <a title="QUALCOMM Incorporated">S. Dorner</a>, “<a href="http://tools.ietf.org/html/rfc1806">Communicating Presentation Information in Internet Messages: The Content-Disposition Header</a>”, RFC&nbsp;1806, June&nbsp;1995.
     1269            </td>
     1270         </tr>
     1271         <tr>
     1272            <td class="reference"><b id="RFC1945">[RFC1945]</b></td>
     1273            <td class="top"><a title="MIT, Laboratory for Computer Science">Berners-Lee, T.</a>, <a title="University of California, Irvine, Department of Information and Computer Science">Fielding, R.T.</a>, and <a title="W3 Consortium, MIT Laboratory for Computer Science">H.F. Nielsen</a>, “<a href="http://tools.ietf.org/html/rfc1945">Hypertext Transfer Protocol -- HTTP/1.0</a>”, RFC&nbsp;1945, May&nbsp;1996.
     1274            </td>
     1275         </tr>
     1276         <tr>
     1277            <td class="reference"><b id="RFC2049">[RFC2049]</b></td>
     1278            <td class="top"><a title="Innosoft International, Inc.">Freed, N.</a> and <a title="First Virtual Holdings">N.S. Borenstein</a>, “<a href="http://tools.ietf.org/html/rfc2049">Multipurpose Internet Mail Extensions (MIME) Part Five: Conformance Criteria and Examples</a>”, RFC&nbsp;2049, November&nbsp;1996.
     1279            </td>
     1280         </tr>
    12661281         <tr>
    12671282            <td class="reference"><b id="RFC2068">[RFC2068]</b></td>
     
    12701285         </tr>
    12711286         <tr>
     1287            <td class="reference"><b id="RFC2076">[RFC2076]</b></td>
     1288            <td class="top"><a title="Stockholm University/KTH">Palme, J.</a>, “<a href="http://tools.ietf.org/html/rfc2076">Common Internet Message Headers</a>”, RFC&nbsp;2076, February&nbsp;1997.
     1289            </td>
     1290         </tr>
     1291         <tr>
     1292            <td class="reference"><b id="RFC2183">[RFC2183]</b></td>
     1293            <td class="top"><a title="New Century Systems">Troost, R.</a>, <a title="QUALCOMM Incorporated">Dorner, S.</a>, and <a title="Department of Computer Science">K. Moore</a>, “<a href="http://tools.ietf.org/html/rfc2183">Communicating Presentation Information in Internet Messages: The Content-Disposition Header Field</a>”, RFC&nbsp;2183, August&nbsp;1997.
     1294            </td>
     1295         </tr>
     1296         <tr>
     1297            <td class="reference"><b id="RFC2277">[RFC2277]</b></td>
     1298            <td class="top"><a title="UNINETT">Alvestrand, H.T.</a>, “<a href="http://tools.ietf.org/html/rfc2277">IETF Policy on Character Sets and Languages</a>”, BCP&nbsp;18, RFC&nbsp;2277, January&nbsp;1998.
     1299            </td>
     1300         </tr>
     1301         <tr>
     1302            <td class="reference"><b id="RFC2388">[RFC2388]</b></td>
     1303            <td class="top"><a title="Xerox Palo Alto Research Center">Masinter, L.</a>, “<a href="http://tools.ietf.org/html/rfc2388">Returning Values from Forms:  multipart/form-data</a>”, RFC&nbsp;2388, August&nbsp;1998.
     1304            </td>
     1305         </tr>
     1306         <tr>
     1307            <td class="reference"><b id="RFC2557">[RFC2557]</b></td>
     1308            <td class="top"><a title="Stockholm University and KTH">Palme, F.</a>, <a title="Microsoft Corporation">Hopmann, A.</a>, <a title="Lotus Development Corporation">Shelness, N.</a>, and <a>E. Stefferud</a>, “<a href="http://tools.ietf.org/html/rfc2557">MIME Encapsulation of Aggregate Documents, such as HTML (MHTML)</a>”, RFC&nbsp;2557, March&nbsp;1999.
     1309            </td>
     1310         </tr>
     1311         <tr>
    12721312            <td class="reference"><b id="RFC2616">[RFC2616]</b></td>
    12731313            <td class="top"><a title="University of California, Irvine">Fielding, R.</a>, <a title="W3C">Gettys, J.</a>, <a title="Compaq Computer Corporation">Mogul, J.</a>, <a title="MIT Laboratory for Computer Science">Frystyk, H.</a>, <a title="Xerox Corporation">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, and <a title="W3C">T. Berners-Lee</a>, “<a href="http://tools.ietf.org/html/rfc2616">Hypertext Transfer Protocol -- HTTP/1.1</a>”, RFC&nbsp;2616, June&nbsp;1999.
     1314            </td>
     1315         </tr>
     1316         <tr>
     1317            <td class="reference"><b id="RFC3629">[RFC3629]</b></td>
     1318            <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.
     1319            </td>
     1320         </tr>
     1321         <tr>
     1322            <td class="reference"><b id="RFC822">[RFC822]</b></td>
     1323            <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.
    12741324            </td>
    12751325         </tr>
     
    12771327      <h2 id="rfc.references.3"><a href="#rfc.section.9.3" id="rfc.section.9.3">9.3</a> References (to be categorized)
    12781328      </h2>
    1279       <table summary="References (to be categorized)">                             
     1329      <table summary="References (to be categorized)">         
    12801330         <tr>
    12811331            <td class="reference"><b id="RFC1766">[RFC1766]</b></td>
     
    12841334         </tr>
    12851335         <tr>
    1286             <td class="reference"><b id="RFC1806">[RFC1806]</b></td>
    1287             <td class="top"><a title="New Century Systems">Troost, R.</a> and <a title="QUALCOMM Incorporated">S. Dorner</a>, “<a href="http://tools.ietf.org/html/rfc1806">Communicating Presentation Information in Internet Messages: The Content-Disposition Header</a>”, RFC&nbsp;1806, June&nbsp;1995.
    1288             </td>
    1289          </tr>
    1290          <tr>
    12911336            <td class="reference"><b id="RFC1864">[RFC1864]</b></td>
    12921337            <td class="top"><a title="Carnegie Mellon University">Myers, J.</a> and <a title="Dover Beach Consulting, Inc.">M. Rose</a>, “<a href="http://tools.ietf.org/html/rfc1864">The Content-MD5 Header Field</a>”, RFC&nbsp;1864, October&nbsp;1995.
     
    12941339         </tr>
    12951340         <tr>
    1296             <td class="reference"><b id="RFC1867">[RFC1867]</b></td>
    1297             <td class="top"><a title="Xerox Palo Alto Research Center">Masinter, L.</a> and <a title="XSoft, Xerox Corporation">E. Nebel</a>, “<a href="http://tools.ietf.org/html/rfc1867">Form-based File Upload in HTML</a>”, RFC&nbsp;1867, November&nbsp;1995.
    1298             </td>
    1299          </tr>
    1300          <tr>
    1301             <td class="reference"><b id="RFC1945">[RFC1945]</b></td>
    1302             <td class="top"><a title="MIT, Laboratory for Computer Science">Berners-Lee, T.</a>, <a title="University of California, Irvine, Department of Information and Computer Science">Fielding, R.T.</a>, and <a title="W3 Consortium, MIT Laboratory for Computer Science">H.F. Nielsen</a>, “<a href="http://tools.ietf.org/html/rfc1945">Hypertext Transfer Protocol -- HTTP/1.0</a>”, RFC&nbsp;1945, May&nbsp;1996.
    1303             </td>
    1304          </tr>
    1305          <tr>
    13061341            <td class="reference"><b id="RFC2045">[RFC2045]</b></td>
    13071342            <td class="top"><a title="Innosoft International, Inc.">Freed, N.</a> and <a title="First Virtual Holdings">N.S. Borenstein</a>, “<a href="http://tools.ietf.org/html/rfc2045">Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies</a>”, RFC&nbsp;2045, November&nbsp;1996.
     
    13141349         </tr>
    13151350         <tr>
    1316             <td class="reference"><b id="RFC2049">[RFC2049]</b></td>
    1317             <td class="top"><a title="Innosoft International, Inc.">Freed, N.</a> and <a title="First Virtual Holdings">N.S. Borenstein</a>, “<a href="http://tools.ietf.org/html/rfc2049">Multipurpose Internet Mail Extensions (MIME) Part Five: Conformance Criteria and Examples</a>”, RFC&nbsp;2049, November&nbsp;1996.
    1318             </td>
    1319          </tr>
    1320          <tr>
    1321             <td class="reference"><b id="RFC2076">[RFC2076]</b></td>
    1322             <td class="top"><a title="Stockholm University/KTH">Palme, J.</a>, “<a href="http://tools.ietf.org/html/rfc2076">Common Internet Message Headers</a>”, RFC&nbsp;2076, February&nbsp;1997.
    1323             </td>
    1324          </tr>
    1325          <tr>
    1326             <td class="reference"><b id="RFC2110">[RFC2110]</b></td>
    1327             <td class="top"><a title="Stockholm University and KTH">Palme, J.</a> and <a title="Microsoft Corporation">A. Hopmann</a>, “<a href="http://tools.ietf.org/html/rfc2110">MIME E-mail Encapsulation of Aggregate Documents, such as HTML (MHTML)</a>”, RFC&nbsp;2110, March&nbsp;1997.
    1328             </td>
    1329          </tr>
    1330          <tr>
    1331             <td class="reference"><b id="RFC2183">[RFC2183]</b></td>
    1332             <td class="top"><a title="New Century Systems">Troost, R.</a>, <a title="QUALCOMM Incorporated">Dorner, S.</a>, and <a title="Department of Computer Science">K. Moore</a>, “<a href="http://tools.ietf.org/html/rfc2183">Communicating Presentation Information in Internet Messages: The Content-Disposition Header Field</a>”, RFC&nbsp;2183, August&nbsp;1997.
    1333             </td>
    1334          </tr>
    1335          <tr>
    1336             <td class="reference"><b id="RFC2277">[RFC2277]</b></td>
    1337             <td class="top"><a title="UNINETT">Alvestrand, H.T.</a>, “<a href="http://tools.ietf.org/html/rfc2277">IETF Policy on Character Sets and Languages</a>”, BCP&nbsp;18, RFC&nbsp;2277, January&nbsp;1998.
    1338             </td>
    1339          </tr>
    1340          <tr>
    1341             <td class="reference"><b id="RFC2279">[RFC2279]</b></td>
    1342             <td class="top"><a title="Alis Technologies">Yergeau, F.</a>, “<a href="http://tools.ietf.org/html/rfc2279">UTF-8, a transformation format of ISO 10646</a>”, RFC&nbsp;2279, January&nbsp;1998.
    1343             </td>
    1344          </tr>
    1345          <tr>
    13461351            <td class="reference"><b id="RFC4288">[RFC4288]</b></td>
    13471352            <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.
    1348             </td>
    1349          </tr>
    1350          <tr>
    1351             <td class="reference"><b id="RFC822">[RFC822]</b></td>
    1352             <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.
    13531353            </td>
    13541354         </tr>
     
    14201420      </p>
    14211421      <h2 id="rfc.section.A.6"><a href="#rfc.section.A.6">A.6</a>&nbsp;<a id="mhtml.line.length" href="#mhtml.line.length">MHTML and Line Length Limitations</a></h2>
    1422       <p id="rfc.section.A.6.p.1">HTTP implementations which share code with MHTML <a href="#RFC2110" id="rfc.xref.RFC2110.1"><cite title="MIME E-mail Encapsulation of Aggregate Documents, such as HTML (MHTML)">[RFC2110]</cite></a> implementations need to be aware of MIME line length limitations. Since HTTP does not have this limitation, HTTP does not
     1422      <p id="rfc.section.A.6.p.1">HTTP implementations which share code with MHTML <a href="#RFC2557" id="rfc.xref.RFC2557.1"><cite title="MIME Encapsulation of Aggregate Documents, such as HTML (MHTML)">[RFC2557]</cite></a> implementations need to be aware of MIME line length limitations. Since HTTP does not have this limitation, HTTP does not
    14231423         fold long lines. MHTML messages being transported by HTTP follow all conventions of MHTML, including line length limitations
    14241424         and folding, canonicalization, etc., since HTTP transports all message-bodies as payload (see <a href="#multipart.types" title="Multipart Types">Section&nbsp;2.3.2</a>) and does not interpret the content or any MIME header lines that might be contained therein.
     
    14611461      </p>
    14621462      <p id="rfc.section.C.1.p.2">Content-Base was deleted from the specification: it was not implemented widely, and there is no simple, safe way to introduce
    1463          it without a robust extension mechanism. In addition, it is used in a similar, but not identical fashion in MHTML <a href="#RFC2110" id="rfc.xref.RFC2110.2"><cite title="MIME E-mail Encapsulation of Aggregate Documents, such as HTML (MHTML)">[RFC2110]</cite></a>.
     1463         it without a robust extension mechanism. In addition, it is used in a similar, but not identical fashion in MHTML <a href="#RFC2557" id="rfc.xref.RFC2557.2"><cite title="MIME Encapsulation of Aggregate Documents, such as HTML (MHTML)">[RFC2557]</cite></a>.
    14641464      </p>
    14651465      <p id="rfc.section.C.1.p.3">A content-coding of "identity" was introduced, to solve problems discovered in caching. (<a href="#content.codings" title="Content Codings">Section&nbsp;2.2</a>)
     
    14931493         </li>
    14941494         <li> &lt;<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/46">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/46</a>&gt;: "RFC1700 references"
     1495         </li>
     1496         <li> &lt;<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/65">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/65</a>&gt;: "Informative references"
    14951497         </li>
    14961498         <li> &lt;<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/66">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/66</a>&gt;: "ISO-8859-1 Reference"
     
    16711673            <li class="indline0"><a id="rfc.index.R" href="#rfc.index.R"><b>R</b></a><ul class="ind">
    16721674                  <li class="indline1"><em>RFC1766</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC1766.1">2.5</a>, <a class="iref" href="#RFC1766"><b>9.3</b></a></li>
    1673                   <li class="indline1"><em>RFC1806</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC1806.1">7.2</a>, <a class="iref" href="#rfc.xref.RFC1806.2">7.2</a>, <a class="iref" href="#RFC1806"><b>9.3</b></a>, <a class="iref" href="#rfc.xref.RFC1806.3">B.1</a></li>
     1675                  <li class="indline1"><em>RFC1806</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC1806.1">7.2</a>, <a class="iref" href="#rfc.xref.RFC1806.2">7.2</a>, <a class="iref" href="#RFC1806"><b>9.2</b></a>, <a class="iref" href="#rfc.xref.RFC1806.3">B.1</a></li>
    16741676                  <li class="indline1"><em>RFC1864</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC1864.1">5.8</a>, <a class="iref" href="#rfc.xref.RFC1864.2">5.8</a>, <a class="iref" href="#RFC1864"><b>9.3</b></a></li>
    1675                   <li class="indline1"><em>RFC1867</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC1867.1">2.3.2</a>, <a class="iref" href="#RFC1867"><b>9.3</b></a></li>
    1676                   <li class="indline1"><em>RFC1945</em>&nbsp;&nbsp;<a class="iref" href="#RFC1945"><b>9.3</b></a>, <a class="iref" href="#rfc.xref.RFC1945.1">B</a></li>
     1677                  <li class="indline1"><em>RFC1945</em>&nbsp;&nbsp;<a class="iref" href="#RFC1945"><b>9.2</b></a>, <a class="iref" href="#rfc.xref.RFC1945.1">B</a></li>
    16771678                  <li class="indline1"><em>RFC1950</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC1950.1">2.2</a>, <a class="iref" href="#RFC1950"><b>9.1</b></a></li>
    16781679                  <li class="indline1"><em>RFC1951</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC1951.1">2.2</a>, <a class="iref" href="#RFC1951"><b>9.1</b></a></li>
     
    16831684                     </ul>
    16841685                  </li>
    1685                   <li class="indline1"><em>RFC2049</em>&nbsp;&nbsp;<a class="iref" href="#RFC2049"><b>9.3</b></a>, <a class="iref" href="#rfc.xref.RFC2049.1">A.2</a><ul class="ind">
     1686                  <li class="indline1"><em>RFC2049</em>&nbsp;&nbsp;<a class="iref" href="#RFC2049"><b>9.2</b></a>, <a class="iref" href="#rfc.xref.RFC2049.1">A.2</a><ul class="ind">
    16861687                        <li class="indline1"><em>Section 4</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2049.1">A.2</a></li>
    16871688                     </ul>
    16881689                  </li>
    16891690                  <li class="indline1"><em>RFC2068</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2068.1">§</a>, <a class="iref" href="#rfc.xref.RFC2068.2">§</a>, <a class="iref" href="#rfc.xref.RFC2068.3">§</a>, <a class="iref" href="#RFC2068"><b>9.2</b></a>, <a class="iref" href="#rfc.xref.RFC2068.4">B</a>, <a class="iref" href="#rfc.xref.RFC2068.5">C.1</a></li>
    1690                   <li class="indline1"><em>RFC2076</em>&nbsp;&nbsp;<a class="iref" href="#RFC2076"><b>9.3</b></a>, <a class="iref" href="#rfc.xref.RFC2076.1">B</a></li>
    1691                   <li class="indline1"><em>RFC2110</em>&nbsp;&nbsp;<a class="iref" href="#RFC2110"><b>9.3</b></a>, <a class="iref" href="#rfc.xref.RFC2110.1">A.6</a>, <a class="iref" href="#rfc.xref.RFC2110.2">C.1</a></li>
     1691                  <li class="indline1"><em>RFC2076</em>&nbsp;&nbsp;<a class="iref" href="#RFC2076"><b>9.2</b></a>, <a class="iref" href="#rfc.xref.RFC2076.1">B</a></li>
    16921692                  <li class="indline1"><em>RFC2119</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2119.1">1.1</a>, <a class="iref" href="#RFC2119"><b>9.1</b></a></li>
    1693                   <li class="indline1"><em>RFC2183</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2183.1">7.2</a>, <a class="iref" href="#RFC2183"><b>9.3</b></a></li>
    1694                   <li class="indline1"><em>RFC2277</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2277.1">2.1</a>, <a class="iref" href="#RFC2277"><b>9.3</b></a></li>
    1695                   <li class="indline1"><em>RFC2279</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2279.1">2.1</a>, <a class="iref" href="#RFC2279"><b>9.3</b></a></li>
     1693                  <li class="indline1"><em>RFC2183</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2183.1">7.2</a>, <a class="iref" href="#RFC2183"><b>9.2</b></a></li>
     1694                  <li class="indline1"><em>RFC2277</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2277.1">2.1</a>, <a class="iref" href="#RFC2277"><b>9.2</b></a></li>
     1695                  <li class="indline1"><em>RFC2388</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2388.1">2.3.2</a>, <a class="iref" href="#RFC2388"><b>9.2</b></a></li>
     1696                  <li class="indline1"><em>RFC2557</em>&nbsp;&nbsp;<a class="iref" href="#RFC2557"><b>9.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>
    16961697                  <li class="indline1"><em>RFC2616</em>&nbsp;&nbsp;<a class="iref" href="#RFC2616"><b>9.2</b></a>, <a class="iref" href="#rfc.xref.RFC2616.1">D.1</a></li>
     1698                  <li class="indline1"><em>RFC3629</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC3629.1">2.1</a>, <a class="iref" href="#RFC3629"><b>9.2</b></a></li>
    16971699                  <li class="indline1"><em>RFC4288</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC4288.1">2.3</a>, <a class="iref" href="#rfc.xref.RFC4288.2">2.3</a>, <a class="iref" href="#RFC4288"><b>9.3</b></a></li>
    1698                   <li class="indline1"><em>RFC822</em>&nbsp;&nbsp;<a class="iref" href="#RFC822"><b>9.3</b></a>, <a class="iref" href="#rfc.xref.RFC822.1">A</a></li>
     1700                  <li class="indline1"><em>RFC822</em>&nbsp;&nbsp;<a class="iref" href="#RFC822"><b>9.2</b></a>, <a class="iref" href="#rfc.xref.RFC822.1">A</a></li>
    16991701               </ul>
    17001702            </li>
  • draft-ietf-httpbis/latest/p3-payload.xml

    r126 r129  
    283283</t>
    284284<t>
    285    Implementors should be aware of IETF character set requirements <xref target="RFC2279"/>
     285   Implementors should be aware of IETF character set requirements <xref target="RFC3629"/>
    286286   <xref target="RFC2277"/>.
    287287</t>
     
    499499      <x:h>Note:</x:h> The "multipart/form-data" type has been specifically defined
    500500      for carrying form data suitable for processing via the POST
    501       request method, as described in <xref target="RFC1867"/>.
     501      request method, as described in <xref target="RFC2388"/>.
    502502</t></list></t>
    503503</section>
     
    17821782<references title="Informative References">
    17831783
     1784<reference anchor="RFC822">
     1785  <front>
     1786    <title abbrev="Standard for ARPA Internet Text Messages">Standard for the format of ARPA Internet text messages</title>
     1787    <author initials="D.H." surname="Crocker" fullname="David H. Crocker">
     1788      <organization>University of Delaware, Dept. of Electrical Engineering</organization>
     1789      <address><email>DCrocker@UDel-Relay</email></address>
     1790    </author>
     1791    <date month="August" day="13" year="1982"/>
     1792  </front>
     1793  <seriesInfo name="STD" value="11"/>
     1794  <seriesInfo name="RFC" value="822"/>
     1795</reference>
     1796
     1797<reference anchor="RFC1806">
     1798  <front>
     1799    <title abbrev="Content-Disposition">Communicating Presentation Information in Internet Messages: The Content-Disposition Header</title>
     1800    <author initials="R." surname="Troost" fullname="Rens Troost">
     1801      <organization>New Century Systems</organization>
     1802      <address><email>rens@century.com</email></address>
     1803    </author>
     1804    <author initials="S." surname="Dorner" fullname="Steve Dorner">
     1805      <organization>QUALCOMM Incorporated</organization>
     1806      <address><email>sdorner@qualcomm.com</email></address>
     1807    </author>
     1808    <date month="June" year="1995"/>
     1809  </front>
     1810  <seriesInfo name="RFC" value="1806"/>
     1811</reference>
     1812
    17841813<reference anchor="RFC2068">
    17851814  <front>
     
    18101839</reference>
    18111840
     1841<reference anchor="RFC1945">
     1842  <front>
     1843    <title abbrev="HTTP/1.0">Hypertext Transfer Protocol -- HTTP/1.0</title>
     1844    <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
     1845      <organization>MIT, Laboratory for Computer Science</organization>
     1846      <address><email>timbl@w3.org</email></address>
     1847    </author>
     1848    <author initials="R.T." surname="Fielding" fullname="Roy T. Fielding">
     1849      <organization>University of California, Irvine, Department of Information and Computer Science</organization>
     1850      <address><email>fielding@ics.uci.edu</email></address>
     1851    </author>
     1852    <author initials="H.F." surname="Nielsen" fullname="Henrik Frystyk Nielsen">
     1853      <organization>W3 Consortium, MIT Laboratory for Computer Science</organization>
     1854      <address><email>frystyk@w3.org</email></address>
     1855    </author>
     1856    <date month="May" year="1996"/>
     1857  </front>
     1858  <seriesInfo name="RFC" value="1945"/>
     1859</reference>
     1860
     1861<reference anchor="RFC2049">
     1862  <front>
     1863    <title abbrev="MIME Conformance">Multipurpose Internet Mail Extensions (MIME) Part Five: Conformance Criteria and Examples</title>
     1864    <author initials="N." surname="Freed" fullname="Ned Freed">
     1865      <organization>Innosoft International, Inc.</organization>
     1866      <address><email>ned@innosoft.com</email></address>
     1867    </author>
     1868    <author initials="N.S." surname="Borenstein" fullname="Nathaniel S. Borenstein">
     1869      <organization>First Virtual Holdings</organization>
     1870      <address><email>nsb@nsb.fv.com</email></address>
     1871    </author>
     1872    <date month="November" year="1996"/>
     1873  </front>
     1874  <seriesInfo name="RFC" value="2049"/>
     1875</reference>
     1876
     1877<reference anchor="RFC2076">
     1878  <front>
     1879    <title abbrev="Internet Message Headers">Common Internet Message Headers</title>
     1880    <author initials="J." surname="Palme" fullname="Jacob Palme">
     1881      <organization>Stockholm University/KTH</organization>
     1882      <address><email>jpalme@dsv.su.se</email></address>
     1883    </author>
     1884    <date month="February" year="1997"/>
     1885  </front>
     1886  <seriesInfo name="RFC" value="2076"/>
     1887</reference>
     1888
     1889<reference anchor="RFC2183">
     1890  <front>
     1891    <title abbrev="Content-Disposition">Communicating Presentation Information in Internet Messages: The Content-Disposition Header Field</title>
     1892    <author initials="R." surname="Troost" fullname="Rens Troost">
     1893      <organization>New Century Systems</organization>
     1894      <address><email>rens@century.com</email></address>
     1895    </author>
     1896    <author initials="S." surname="Dorner" fullname="Steve Dorner">
     1897      <organization>QUALCOMM Incorporated</organization>
     1898      <address><email>sdorner@qualcomm.com</email></address>
     1899    </author>
     1900    <author initials="K." surname="Moore" fullname="Keith Moore">
     1901      <organization>Department of Computer Science</organization>
     1902      <address><email>moore@cs.utk.edu</email></address>
     1903    </author>
     1904    <date month="August" year="1997"/>
     1905  </front>
     1906  <seriesInfo name="RFC" value="2183"/>
     1907</reference>
     1908
     1909<reference anchor="RFC2277">
     1910  <front>
     1911    <title abbrev="Charset Policy">IETF Policy on Character Sets and Languages</title>
     1912    <author initials="H.T." surname="Alvestrand" fullname="Harald Tveit Alvestrand">
     1913      <organization>UNINETT</organization>
     1914      <address><email>Harald.T.Alvestrand@uninett.no</email></address>
     1915    </author>
     1916    <date month="January" year="1998"/>
     1917  </front>
     1918  <seriesInfo name="BCP" value="18"/>
     1919  <seriesInfo name="RFC" value="2277"/>
     1920</reference>
     1921
     1922<reference anchor="RFC2388">
     1923  <front>
     1924    <title abbrev="multipart/form-data">Returning Values from Forms:  multipart/form-data</title>
     1925    <author initials="L." surname="Masinter" fullname="Larry Masinter">
     1926      <organization>Xerox Palo Alto Research Center</organization>
     1927      <address><email>masinter@parc.xerox.com</email></address>
     1928    </author>
     1929    <date year="1998" month="August"/>
     1930  </front>
     1931  <seriesInfo name="RFC" value="2388"/>
     1932</reference>
     1933
     1934<reference anchor="RFC2557">
     1935  <front>
     1936    <title abbrev="MIME Encapsulation of Aggregate Documents">MIME Encapsulation of Aggregate Documents, such as HTML (MHTML)</title>
     1937    <author initials="F." surname="Palme" fullname="Jacob Palme">
     1938      <organization>Stockholm University and KTH</organization>
     1939      <address><email>jpalme@dsv.su.se</email></address>
     1940    </author>
     1941    <author initials="A." surname="Hopmann" fullname="Alex Hopmann">
     1942      <organization>Microsoft Corporation</organization>
     1943      <address><email>alexhop@microsoft.com</email></address>
     1944    </author>
     1945    <author initials="N." surname="Shelness" fullname="Nick Shelness">
     1946      <organization>Lotus Development Corporation</organization>
     1947      <address><email>Shelness@lotus.com</email></address>
     1948    </author>
     1949    <author initials="E." surname="Stefferud" fullname="Einar Stefferud">
     1950      <organization/>
     1951      <address><email>stef@nma.com</email></address>
     1952    </author>
     1953    <date year="1999" month="March"/>
     1954  </front>
     1955  <seriesInfo name="RFC" value="2557"/>
     1956</reference>
     1957
    18121958<reference anchor="RFC2616">
    18131959  <front>
     
    18441990  </front>
    18451991  <seriesInfo name="RFC" value="2616"/>
    1846   </reference>
     1992</reference>
     1993
     1994<reference anchor="RFC3629">
     1995  <front>
     1996    <title>UTF-8, a transformation format of ISO 10646</title>
     1997    <author initials="F." surname="Yergeau" fullname="F. Yergeau">
     1998      <organization>Alis Technologies</organization>
     1999      <address><email>fyergeau@alis.com</email></address>
     2000    </author>
     2001    <date month="November" year="2003"/>
     2002  </front>
     2003  <seriesInfo name="RFC" value="3629"/>
     2004  <seriesInfo name="STD" value="63"/>
     2005</reference>
    18472006
    18482007</references>
     
    18762035  </front>
    18772036  <seriesInfo name="RFC" value="2045"/>
    1878 </reference>
    1879 
    1880 <reference anchor="RFC822">
    1881   <front>
    1882     <title abbrev="Standard for ARPA Internet Text Messages">Standard for the format of ARPA Internet text messages</title>
    1883     <author initials="D.H." surname="Crocker" fullname="David H. Crocker">
    1884       <organization>University of Delaware, Dept. of Electrical Engineering</organization>
    1885       <address><email>DCrocker@UDel-Relay</email></address>
    1886     </author>
    1887     <date month="August" day="13" year="1982"/>
    1888   </front>
    1889   <seriesInfo name="STD" value="11"/>
    1890   <seriesInfo name="RFC" value="822"/>
    1891 </reference>
    1892 
    1893 <reference anchor="RFC1867">
    1894   <front>
    1895     <title>Form-based File Upload in HTML</title>
    1896     <author initials="L." surname="Masinter" fullname="Larry Masinter">
    1897       <organization>Xerox Palo Alto Research Center</organization>
    1898       <address><email>masinter@parc.xerox.com</email></address>
    1899     </author>
    1900     <author initials="E." surname="Nebel" fullname="Ernesto Nebel">
    1901       <organization>XSoft, Xerox Corporation</organization>
    1902       <address><email>nebel@xsoft.sd.xerox.com</email></address>
    1903     </author>
    1904     <date month="November" year="1995"/>
    1905   </front>
    1906   <seriesInfo name="RFC" value="1867"/>
    19072037</reference>
    19082038
     
    19442074</reference>
    19452075
    1946 <reference anchor="RFC1806">
    1947   <front>
    1948     <title abbrev="Content-Disposition">Communicating Presentation Information in Internet Messages: The Content-Disposition Header</title>
    1949     <author initials="R." surname="Troost" fullname="Rens Troost">
    1950       <organization>New Century Systems</organization>
    1951       <address><email>rens@century.com</email></address>
    1952     </author>
    1953     <author initials="S." surname="Dorner" fullname="Steve Dorner">
    1954       <organization>QUALCOMM Incorporated</organization>
    1955       <address><email>sdorner@qualcomm.com</email></address>
    1956     </author>
    1957     <date month="June" year="1995"/>
    1958   </front>
    1959   <seriesInfo name="RFC" value="1806"/>
    1960 </reference>
    1961 
    1962 <reference anchor="RFC1945">
    1963   <front>
    1964     <title abbrev="HTTP/1.0">Hypertext Transfer Protocol -- HTTP/1.0</title>
    1965     <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
    1966       <organization>MIT, Laboratory for Computer Science</organization>
    1967       <address><email>timbl@w3.org</email></address>
    1968     </author>
    1969     <author initials="R.T." surname="Fielding" fullname="Roy T. Fielding">
    1970       <organization>University of California, Irvine, Department of Information and Computer Science</organization>
    1971       <address><email>fielding@ics.uci.edu</email></address>
    1972     </author>
    1973     <author initials="H.F." surname="Nielsen" fullname="Henrik Frystyk Nielsen">
    1974       <organization>W3 Consortium, MIT Laboratory for Computer Science</organization>
    1975       <address><email>frystyk@w3.org</email></address>
    1976     </author>
    1977     <date month="May" year="1996"/>
    1978   </front>
    1979   <seriesInfo name="RFC" value="1945"/>
    1980 </reference>
    1981 
    1982 <reference anchor="RFC2076">
    1983   <front>
    1984     <title abbrev="Internet Message Headers">Common Internet Message Headers</title>
    1985     <author initials="J." surname="Palme" fullname="Jacob Palme">
    1986       <organization>Stockholm University/KTH</organization>
    1987       <address><email>jpalme@dsv.su.se</email></address>
    1988     </author>
    1989     <date month="February" year="1997"/>
    1990   </front>
    1991   <seriesInfo name="RFC" value="2076"/>
    1992 </reference>
    1993 
    1994 <reference anchor="RFC2279">
    1995 <front>
    1996 <title abbrev="UTF-8">UTF-8, a transformation format of ISO 10646</title>
    1997 <author initials="F." surname="Yergeau" fullname="Francois Yergeau">
    1998 <organization>Alis Technologies</organization>
    1999 <address>
    2000 <postal>
    2001 <street>100, boul. Alexis-Nihon</street>
    2002 <street>Suite 600</street>
    2003 <city>Montreal</city>
    2004 <region>Quebec</region>
    2005 <code>H4M 2P2</code>
    2006 <country>CA</country></postal>
    2007 <phone>+1 514 747 2547</phone>
    2008 <facsimile>+1 514 747 2561</facsimile>
    2009 <email>fyergeau@alis.com</email></address></author>
    2010 <date month="January" year="1998"/>
    2011 <abstract>
    2012 <t>ISO/IEC 10646-1 defines a multi-octet character set called the Universal Character Set (UCS) which encompasses most of the world's writing systems. Multi-octet characters, however, are not compatible with many current applications and protocols, and this has led to the development of a few so-called UCS transformation formats (UTF), each with different characteristics.  UTF-8, the object of this memo, has the characteristic of preserving the full US-ASCII range, providing compatibility with file systems, parsers and other software that rely on US-ASCII values but are transparent to other values. This memo updates and replaces RFC 2044, in particular addressing the question of versions of the relevant standards.</t></abstract></front>
    2013 <seriesInfo name="RFC" value="2279"/>
    2014 </reference>
    2015 
    20162076<reference anchor="RFC2046">
    20172077  <front>
     
    20282088  </front>
    20292089  <seriesInfo name="RFC" value="2046"/>
    2030 </reference>
    2031 
    2032 <reference anchor="RFC2277">
    2033 <front>
    2034 <title abbrev="Charset Policy">IETF Policy on Character Sets and Languages</title>
    2035 <author initials="H.T." surname="Alvestrand" fullname="Harald Tveit Alvestrand">
    2036 <organization>UNINETT</organization>
    2037 <address>
    2038 <postal>
    2039 <street>P.O.Box 6883 Elgeseter</street>
    2040 <street>N-7002 TRONDHEIM</street>
    2041 <country>NORWAY</country></postal>
    2042 <phone>+47 73 59 70 94</phone>
    2043 <email>Harald.T.Alvestrand@uninett.no</email></address></author>
    2044 <date month="January" year="1998"/>
    2045 <area>Applications</area>
    2046 <keyword>Internet Engineering Task Force</keyword>
    2047 <keyword>character encoding</keyword></front>
    2048 <seriesInfo name="BCP" value="18"/>
    2049 <seriesInfo name="RFC" value="2277"/>
    2050 </reference>
    2051 
    2052 <reference anchor="RFC2110">
    2053 <front>
    2054 <title abbrev="MHTML">MIME E-mail Encapsulation of Aggregate Documents, such as HTML (MHTML)</title>
    2055 <author initials="J." surname="Palme" fullname="Jacob Palme">
    2056 <organization>Stockholm University and KTH</organization>
    2057 <address>
    2058 <postal>
    2059 <street>Electrum 230</street>
    2060 <street>S-164 40 Kista</street>
    2061 <country>Sweden</country></postal>
    2062 <phone>+46-8-16 16 67</phone>
    2063 <facsimile>+46-8-783 08 29</facsimile>
    2064 <email>jpalme@dsv.su.se</email></address></author>
    2065 <author initials="A." surname="Hopmann" fullname="Alex Hopmann">
    2066 <organization>Microsoft Corporation</organization>
    2067 <address>
    2068 <postal>
    2069 <street>3590 North First Street</street>
    2070 <street>Suite 300</street>
    2071 <street>San Jose</street>
    2072 <street>CA 95134</street>
    2073 <street>Working group chairman:</street></postal>
    2074 <email>alexhop@microsoft.com</email></address></author>
    2075 <date month="March" year="1997"/>
    2076 <area>Applications</area>
    2077 <keyword>encapsulate</keyword>
    2078 <keyword>hypertext markup language</keyword>
    2079 <keyword>mail</keyword>
    2080 <keyword>multipurpose internet mail extensions</keyword>
    2081 </front>
    2082 <seriesInfo name="RFC" value="2110"/>
    2083 </reference>
    2084 
    2085 <reference anchor="RFC2049">
    2086   <front>
    2087     <title abbrev="MIME Conformance">Multipurpose Internet Mail Extensions (MIME) Part Five: Conformance Criteria and Examples</title>
    2088     <author initials="N." surname="Freed" fullname="Ned Freed">
    2089       <organization>Innosoft International, Inc.</organization>
    2090       <address><email>ned@innosoft.com</email></address>
    2091     </author>
    2092     <author initials="N.S." surname="Borenstein" fullname="Nathaniel S. Borenstein">
    2093       <organization>First Virtual Holdings</organization>
    2094       <address><email>nsb@nsb.fv.com</email></address>
    2095     </author>
    2096     <date month="November" year="1996"/>
    2097   </front>
    2098   <seriesInfo name="RFC" value="2049"/>
    2099 </reference>
    2100 
    2101 <reference anchor="RFC2183">
    2102   <front>
    2103     <title abbrev="Content-Disposition">Communicating Presentation Information in Internet Messages: The Content-Disposition Header Field</title>
    2104     <author initials="R." surname="Troost" fullname="Rens Troost">
    2105       <organization>New Century Systems</organization>
    2106       <address><email>rens@century.com</email></address>
    2107     </author>
    2108     <author initials="S." surname="Dorner" fullname="Steve Dorner">
    2109       <organization>QUALCOMM Incorporated</organization>
    2110       <address><email>sdorner@qualcomm.com</email></address>
    2111     </author>
    2112     <author initials="K." surname="Moore" fullname="Keith Moore">
    2113       <organization>Department of Computer Science</organization>
    2114       <address><email>moore@cs.utk.edu</email></address>
    2115     </author>
    2116     <date month="August" year="1997"/>
    2117   </front>
    2118   <seriesInfo name="RFC" value="2183"/>
    21192090</reference>
    21202091
     
    22332204<section title="MHTML and Line Length Limitations" anchor="mhtml.line.length">
    22342205<t>
    2235    HTTP implementations which share code with MHTML <xref target="RFC2110"/> implementations
     2206   HTTP implementations which share code with MHTML <xref target="RFC2557"/> implementations
    22362207   need to be aware of MIME line length limitations. Since HTTP does not
    22372208   have this limitation, HTTP does not fold long lines. MHTML messages
     
    23132284   implemented widely, and there is no simple, safe way to introduce it
    23142285   without a robust extension mechanism. In addition, it is used in a
    2315    similar, but not identical fashion in MHTML <xref target="RFC2110"/>.
     2286   similar, but not identical fashion in MHTML <xref target="RFC2557"/>.
    23162287</t>
    23172288<t>
     
    23792350    </t>
    23802351    <t>
     2352      <eref target="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/65"/>:
     2353      "Informative references"
     2354    </t>
     2355    <t>
    23812356      <eref target="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/66"/>:
    23822357      "ISO-8859-1 Reference"
  • draft-ietf-httpbis/latest/p4-conditional.html

    r124 r129  
    964964      <ul>
    965965         <li>Move definitions of 304 and 412 condition codes from Part2.</li>
    966          <li>Start work on categorizing references as "Normative" or "Informative".</li>
     966         <li>Categorize references as "Normative" or "Informative".</li>
    967967      </ul>
    968968      <h1><a id="rfc.copyright" href="#rfc.copyright">Full Copyright Statement</a></h1>
  • draft-ietf-httpbis/latest/p4-conditional.xml

    r124 r129  
    11701170    </t>
    11711171    <t>
    1172       Start work on categorizing references as "Normative" or "Informative".
     1172      Categorize references as "Normative" or "Informative".
    11731173    </t>
    11741174  </list>
  • draft-ietf-httpbis/latest/p6-cache.html

    r124 r129  
    17801780      <h2 id="rfc.references.2"><a href="#rfc.section.7.2" id="rfc.section.7.2">7.2</a> Informative References
    17811781      </h2>
    1782       <table summary="Informative References"> 
     1782      <table summary="Informative References">   
     1783         <tr>
     1784            <td class="reference"><b id="RFC1305">[RFC1305]</b></td>
     1785            <td class="top"><a title="University of Delaware, Electrical Engineering Department">Mills, D.</a>, “<a href="http://tools.ietf.org/html/rfc1305">Network Time Protocol (Version 3) Specification, Implementation</a>”, RFC&nbsp;1305, March&nbsp;1992.
     1786            </td>
     1787         </tr>
    17831788         <tr>
    17841789            <td class="reference"><b id="RFC2616">[RFC2616]</b></td>
     
    17891794      <h2 id="rfc.references.3"><a href="#rfc.section.7.3" id="rfc.section.7.3">7.3</a> References (to be categorized)
    17901795      </h2>
    1791       <table summary="References (to be categorized)">   
    1792          <tr>
    1793             <td class="reference"><b id="RFC1305">[RFC1305]</b></td>
    1794             <td class="top"><a title="University of Delaware, Electrical Engineering Department">Mills, D.</a>, “<a href="http://tools.ietf.org/html/rfc1305">Network Time Protocol (Version 3) Specification, Implementation</a>”, RFC&nbsp;1305, March&nbsp;1992.
    1795             </td>
    1796          </tr>
     1796      <table summary="References (to be categorized)"> 
    17971797         <tr>
    17981798            <td class="reference"><b id="RFC2047">[RFC2047]</b></td>
     
    18451845         </li>
    18461846         <li> &lt;<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/49">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/49</a>&gt;: "Connection header text"
     1847         </li>
     1848         <li> &lt;<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/65">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/65</a>&gt;: "Informative references"
    18471849         </li>
    18481850         <li> &lt;<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/66">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/66</a>&gt;: "ISO-8859-1 Reference"
     
    20692071            </li>
    20702072            <li class="indline0"><a id="rfc.index.R" href="#rfc.index.R"><b>R</b></a><ul class="ind">
    2071                   <li class="indline1"><em>RFC1305</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC1305.1">2.2.3</a>, <a class="iref" href="#RFC1305"><b>7.3</b></a></li>
     2073                  <li class="indline1"><em>RFC1305</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC1305.1">2.2.3</a>, <a class="iref" href="#RFC1305"><b>7.2</b></a></li>
    20722074                  <li class="indline1"><em>RFC2047</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2047.1">3.6</a>, <a class="iref" href="#RFC2047"><b>7.3</b></a></li>
    20732075                  <li class="indline1"><em>RFC2119</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2119.1">1.1</a>, <a class="iref" href="#RFC2119"><b>7.1</b></a></li>
  • draft-ietf-httpbis/latest/p6-cache.xml

    r124 r129  
    27512751<references title="Informative References">
    27522752
     2753<reference anchor="RFC1305">
     2754  <front>
     2755    <title>Network Time Protocol (Version 3) Specification, Implementation</title>
     2756    <author initials="D." surname="Mills" fullname="David L. Mills">
     2757      <organization>University of Delaware, Electrical Engineering Department</organization>
     2758      <address><email>mills@udel.edu</email></address>
     2759    </author>
     2760    <date month="March" year="1992"/>
     2761  </front>
     2762  <seriesInfo name="RFC" value="1305"/>
     2763</reference>
     2764
    27532765<reference anchor="RFC2616">
    27542766  <front>
     
    28012813  </front>
    28022814  <seriesInfo name="RFC" value="2047"/>
    2803 </reference>
    2804 
    2805 <reference anchor="RFC1305">
    2806 <front>
    2807 <title>Network Time Protocol (Version 3) Specification, Implementation</title>
    2808 <author initials="D." surname="Mills" fullname="David L. Mills">
    2809 <organization>University of Delaware, Electrical Engineering Department</organization>
    2810 <address>
    2811 <postal>
    2812 <street/>
    2813 <city>Newark</city>
    2814 <region>DE</region>
    2815 <code>19716</code>
    2816 <country>US</country></postal>
    2817 <phone>+1 302 451 8247</phone>
    2818 <email>mills@udel.edu</email></address></author>
    2819 <date month="March" year="1992"/>
    2820 <abstract>
    2821 <t>This document describes the Network Time Protocol (NTP), specifies its normal structure and summarizes information useful for its implementation. NTP provides the mechanisms to synchronize time and coordinate time distribution in a large, diverse internet operating at rates from mundane to lightwave. It uses a returnable-time design in which a distributed subnet of time servers operating in a self-organizing, hierarchical-master-slave configuration synchronizes local clocks within the subnet and to national time standards via wire or radio. The servers can also redistribute reference time via local routing algorithms and time daemons.</t></abstract></front>
    2822 <seriesInfo name="RFC" value="1305"/>
    28232815</reference>
    28242816
     
    28882880    </t>
    28892881    <t>
     2882      <eref target="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/65"/>:
     2883      "Informative references"
     2884    </t>
     2885    <t>
    28902886      <eref target="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/66"/>:
    28912887      "ISO-8859-1 Reference"
  • draft-ietf-httpbis/latest/p7-auth.html

    r124 r129  
    693693      <p id="rfc.section.B.2.p.1">Other changes: </p>
    694694      <ul>
    695          <li>Start work on categorizing references as "Normative" or "Informative".</li>
     695         <li>Categorize references as "Normative" or "Informative".</li>
    696696      </ul>
    697697      <h1><a id="rfc.copyright" href="#rfc.copyright">Full Copyright Statement</a></h1>
  • draft-ietf-httpbis/latest/p7-auth.xml

    r124 r129  
    614614  <list style="symbols">
    615615    <t>
    616       Start work on categorizing references as "Normative" or "Informative".
     616      Categorize references as "Normative" or "Informative".
    617617    </t>
    618618  </list>
Note: See TracChangeset for help on using the changeset viewer.