Changeset 212 for draft-ietf-httpbis/latest/p2-semantics.html
- Timestamp:
- 14/02/08 12:46:46 (13 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p2-semantics.html
r210 r212 637 637 </div> 638 638 <div id="rfc.figure.u.3"></div><pre class="inline"> absoluteURI = <absoluteURI, defined in <a href="#Part1" id="rfc.xref.Part1.8"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#general.syntax" title="General Syntax">Section 3.2.1</a>> 639 delta-seconds = <delta-seconds, defined in <a href="#Part1" id="rfc.xref.Part1.9"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#time.spans" title="Time Spans">Section 3.3.2</a>> 640 fragment = <fragment, defined in <a href="#Part1" id="rfc.xref.Part1.10"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#general.syntax" title="General Syntax">Section 3.2.1</a>> 641 Host = <Host, defined in <a href="#Part1" id="rfc.xref.Part1.11"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#header.host" title="Host">Section 8.4</a>> 642 HTTP-date = <HTTP-date, defined in <a href="#Part1" id="rfc.xref.Part1.12"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#full.date" title="Full Date">Section 3.3.1</a>> 643 product = <product, defined in <a href="#Part1" id="rfc.xref.Part1.13"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#product.tokens" title="Product Tokens">Section 3.5</a>> 644 relativeURI = <relativeURI, defined in <a href="#Part1" id="rfc.xref.Part1.14"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#general.syntax" title="General Syntax">Section 3.2.1</a>> 645 TE = <TE, defined in <a href="#Part1" id="rfc.xref.Part1.15"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#header.upgrade" title="Upgrade">Section 8.8</a>> 639 fragment = <fragment, defined in <a href="#Part1" id="rfc.xref.Part1.9"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#general.syntax" title="General Syntax">Section 3.2.1</a>> 640 Host = <Host, defined in <a href="#Part1" id="rfc.xref.Part1.10"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#header.host" title="Host">Section 8.4</a>> 641 HTTP-date = <HTTP-date, defined in <a href="#Part1" id="rfc.xref.Part1.11"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#full.date" title="Full Date">Section 3.3.1</a>> 642 product = <product, defined in <a href="#Part1" id="rfc.xref.Part1.12"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#product.tokens" title="Product Tokens">Section 3.5</a>> 643 relativeURI = <relativeURI, defined in <a href="#Part1" id="rfc.xref.Part1.13"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#general.syntax" title="General Syntax">Section 3.2.1</a>> 644 TE = <TE, defined in <a href="#Part1" id="rfc.xref.Part1.14"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#header.upgrade" title="Upgrade">Section 8.8</a>> 646 645 </pre><div id="rfc.figure.u.4"></div><pre class="inline"> Accept = <Accept, defined in <a href="#Part3" id="rfc.xref.Part3.1"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="p3-payload.html#header.accept" title="Accept">Section 6.1</a>> 647 646 Accept-Charset = … … 699 698 | Expect ; <a href="#header.expect" id="rfc.xref.header.expect.1" title="Expect">Section 10.2</a> 700 699 | From ; <a href="#header.from" id="rfc.xref.header.from.1" title="From">Section 10.3</a> 701 | Host ; <a href="#Part1" id="rfc.xref.Part1.1 6"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#header.host" title="Host">Section 8.4</a>700 | Host ; <a href="#Part1" id="rfc.xref.Part1.15"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#header.host" title="Host">Section 8.4</a> 702 701 | If-Match ; <a href="#Part4" id="rfc.xref.Part4.6"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>, <a href="p4-conditional.html#header.if-match" title="If-Match">Section 7.2</a> 703 702 | If-Modified-Since ; <a href="#Part4" id="rfc.xref.Part4.7"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>, <a href="p4-conditional.html#header.if-modified-since" title="If-Modified-Since">Section 7.3</a> … … 709 708 | Range ; <a href="#Part5" id="rfc.xref.Part5.5"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>, <a href="p5-range.html#header.range" title="Range">Section 6.4</a> 710 709 | Referer ; <a href="#header.referer" id="rfc.xref.header.referer.1" title="Referer">Section 10.6</a> 711 | TE ; <a href="#Part1" id="rfc.xref.Part1.1 7"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#header.upgrade" title="Upgrade">Section 8.8</a>710 | TE ; <a href="#Part1" id="rfc.xref.Part1.16"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#header.upgrade" title="Upgrade">Section 8.8</a> 712 711 | User-Agent ; <a href="#header.user-agent" id="rfc.xref.header.user-agent.1" title="User-Agent">Section 10.9</a> 713 712 </pre><p id="rfc.section.4.p.3">Request-header field names can be extended reliably only in combination with a change in the protocol version. However, new … … 797 796 fields are defined in <a href="#Part3" id="rfc.xref.Part3.9"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>. 798 797 </p> 799 <p id="rfc.section.7.p.2">An entity-body is only present in a message when a message-body is present, as described in <a href="p1-messaging.html#message.body" title="Message Body">Section 4.3</a> of <a href="#Part1" id="rfc.xref.Part1.1 8"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>. The entity-body is obtained from the message-body by decoding any Transfer-Encoding that might have been applied to ensure798 <p id="rfc.section.7.p.2">An entity-body is only present in a message when a message-body is present, as described in <a href="p1-messaging.html#message.body" title="Message Body">Section 4.3</a> of <a href="#Part1" id="rfc.xref.Part1.17"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>. The entity-body is obtained from the message-body by decoding any Transfer-Encoding that might have been applied to ensure 800 799 safe and proper transfer of the message. 801 800 </p> … … 961 960 </p> 962 961 <p id="rfc.section.8.8.p.2">TRACE allows the client to see what is being received at the other end of the request chain and use that data for testing 963 or diagnostic information. The value of the Via header field (<a href="p1-messaging.html#header.via" title="Via">Section 8.9</a> of <a href="#Part1" id="rfc.xref.Part1.1 9"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) is of particular interest, since it acts as a trace of the request chain. Use of the Max-Forwards header field allows the962 or diagnostic information. The value of the Via header field (<a href="p1-messaging.html#header.via" title="Via">Section 8.9</a> of <a href="#Part1" id="rfc.xref.Part1.18"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) is of particular interest, since it acts as a trace of the request chain. Use of the Max-Forwards header field allows the 964 963 client to limit the length of the request chain, which is useful for testing a chain of proxies forwarding messages in an 965 964 infinite loop. … … 994 993 <p id="rfc.section.9.1.1.p.1">The client <em class="bcp14">SHOULD</em> continue with its request. This interim response is used to inform the client that the initial part of the request has been 995 994 received and has not yet been rejected by the server. The client <em class="bcp14">SHOULD</em> continue by sending the remainder of the request or, if the request has already been completed, ignore this response. The 996 server <em class="bcp14">MUST</em> send a final response after the request has been completed. See <a href="p1-messaging.html#use.of.the.100.status" title="Use of the 100 (Continue) Status">Section 7.2.3</a> of <a href="#Part1" id="rfc.xref.Part1. 20"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a> for detailed discussion of the use and handling of this status code.995 server <em class="bcp14">MUST</em> send a final response after the request has been completed. See <a href="p1-messaging.html#use.of.the.100.status" title="Use of the 100 (Continue) Status">Section 7.2.3</a> of <a href="#Part1" id="rfc.xref.Part1.19"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a> for detailed discussion of the use and handling of this status code. 997 996 </p> 998 997 <div id="rfc.iref.24"></div> … … 1376 1375 <p id="rfc.section.9.5.6.p.1">The server does not support, or refuses to support, the protocol version that was used in the request message. The server 1377 1376 is indicating that it is unable or unwilling to complete the request using the same major version as the client, as described 1378 in <a href="p1-messaging.html#http.version" title="HTTP Version">Section 3.1</a> of <a href="#Part1" id="rfc.xref.Part1.2 1"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, other than with this error message. The response <em class="bcp14">SHOULD</em> contain an entity describing why that version is not supported and what other protocols are supported by that server.1377 in <a href="p1-messaging.html#http.version" title="HTTP Version">Section 3.1</a> of <a href="#Part1" id="rfc.xref.Part1.20"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, other than with this error message. The response <em class="bcp14">SHOULD</em> contain an entity describing why that version is not supported and what other protocols are supported by that server. 1379 1378 </p> 1380 1379 <h1 id="rfc.section.10"><a href="#rfc.section.10">10.</a> <a id="header.fields" href="#header.fields">Header Field Definitions</a></h1> … … 1423 1422 </p> 1424 1423 <p id="rfc.section.10.2.p.7">Many older HTTP/1.0 and HTTP/1.1 applications do not understand the Expect header.</p> 1425 <p id="rfc.section.10.2.p.8">See <a href="p1-messaging.html#use.of.the.100.status" title="Use of the 100 (Continue) Status">Section 7.2.3</a> of <a href="#Part1" id="rfc.xref.Part1.2 2"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a> for the use of the 100 (Continue) status.1424 <p id="rfc.section.10.2.p.8">See <a href="p1-messaging.html#use.of.the.100.status" title="Use of the 100 (Continue) Status">Section 7.2.3</a> of <a href="#Part1" id="rfc.xref.Part1.21"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a> for the use of the 100 (Continue) status. 1426 1425 </p> 1427 1426 <div id="rfc.iref.f.1"></div> … … 1505 1504 the time of the response. 1506 1505 </p> 1507 <div id="rfc.figure.u.23"></div><pre class="inline"><span id="rfc.iref.g.18"></span> Retry-After = "Retry-After" ":" ( HTTP-date | delta-seconds ) 1508 </pre><p id="rfc.section.10.7.p.3">Two examples of its use are</p> 1509 <div id="rfc.figure.u.24"></div><pre class="text"> Retry-After: Fri, 31 Dec 1999 23:59:59 GMT 1506 <div id="rfc.figure.u.23"></div><pre class="inline"><span id="rfc.iref.g.18"></span> Retry-After = "Retry-After" ":" ( HTTP-date | delta-seconds ) 1507 </pre><p id="rfc.section.10.7.p.3">Time spans are non-negative decimal integers, representing time in seconds.</p> 1508 <div id="rfc.figure.u.24"></div><pre class="inline"><span id="rfc.iref.g.19"></span> delta-seconds = 1*DIGIT 1509 </pre><p id="rfc.section.10.7.p.5">Two examples of its use are</p> 1510 <div id="rfc.figure.u.25"></div><pre class="text"> Retry-After: Fri, 31 Dec 1999 23:59:59 GMT 1510 1511 Retry-After: 120 1511 </pre><p id="rfc.section.10.7.p. 5">In the latter example, the delay is 2 minutes.</p>1512 </pre><p id="rfc.section.10.7.p.7">In the latter example, the delay is 2 minutes.</p> 1512 1513 <div id="rfc.iref.s.42"></div> 1513 1514 <div id="rfc.iref.h.9"></div> 1514 1515 <h2 id="rfc.section.10.8"><a href="#rfc.section.10.8">10.8</a> <a id="header.server" href="#header.server">Server</a></h2> 1515 1516 <p id="rfc.section.10.8.p.1">The Server response-header field contains information about the software used by the origin server to handle the request. 1516 The field can contain multiple product tokens (<a href="p1-messaging.html#product.tokens" title="Product Tokens">Section 3.5</a> of <a href="#Part1" id="rfc.xref.Part1.2 3"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) and comments identifying the server and any significant subproducts. The product tokens are listed in order of their significance1517 The field can contain multiple product tokens (<a href="p1-messaging.html#product.tokens" title="Product Tokens">Section 3.5</a> of <a href="#Part1" id="rfc.xref.Part1.22"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) and comments identifying the server and any significant subproducts. The product tokens are listed in order of their significance 1517 1518 for identifying the application. 1518 1519 </p> 1519 <div id="rfc.figure.u.2 5"></div><pre class="inline"><span id="rfc.iref.g.19"></span> Server = "Server" ":" 1*( product | comment )1520 <div id="rfc.figure.u.26"></div><pre class="inline"><span id="rfc.iref.g.20"></span> Server = "Server" ":" 1*( product | comment ) 1520 1521 </pre><p id="rfc.section.10.8.p.3">Example:</p> 1521 <div id="rfc.figure.u.2 6"></div><pre class="text"> Server: CERN/3.0 libwww/2.171522 </pre><p id="rfc.section.10.8.p.5">If the response is being forwarded through a proxy, the proxy application <em class="bcp14">MUST NOT</em> modify the Server response-header. Instead, it <em class="bcp14">MUST</em> include a Via field (as described in <a href="p1-messaging.html#header.via" title="Via">Section 8.9</a> of <a href="#Part1" id="rfc.xref.Part1.2 4"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>).1522 <div id="rfc.figure.u.27"></div><pre class="text"> Server: CERN/3.0 libwww/2.17 1523 </pre><p id="rfc.section.10.8.p.5">If the response is being forwarded through a proxy, the proxy application <em class="bcp14">MUST NOT</em> modify the Server response-header. Instead, it <em class="bcp14">MUST</em> include a Via field (as described in <a href="p1-messaging.html#header.via" title="Via">Section 8.9</a> of <a href="#Part1" id="rfc.xref.Part1.23"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>). 1523 1524 </p> 1524 1525 <dl class="empty"> … … 1533 1534 <p id="rfc.section.10.9.p.1">The User-Agent request-header field contains information about the user agent originating the request. This is for statistical 1534 1535 purposes, the tracing of protocol violations, and automated recognition of user agents for the sake of tailoring responses 1535 to avoid particular user agent limitations. User agents <em class="bcp14">SHOULD</em> include this field with requests. The field can contain multiple product tokens (<a href="p1-messaging.html#product.tokens" title="Product Tokens">Section 3.5</a> of <a href="#Part1" id="rfc.xref.Part1.2 5"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) and comments identifying the agent and any subproducts which form a significant part of the user agent. By convention, the1536 to avoid particular user agent limitations. User agents <em class="bcp14">SHOULD</em> include this field with requests. The field can contain multiple product tokens (<a href="p1-messaging.html#product.tokens" title="Product Tokens">Section 3.5</a> of <a href="#Part1" id="rfc.xref.Part1.24"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) and comments identifying the agent and any subproducts which form a significant part of the user agent. By convention, the 1536 1537 product tokens are listed in order of their significance for identifying the application. 1537 1538 </p> 1538 <div id="rfc.figure.u.2 7"></div><pre class="inline"><span id="rfc.iref.g.20"></span> User-Agent = "User-Agent" ":" 1*( product | comment )1539 <div id="rfc.figure.u.28"></div><pre class="inline"><span id="rfc.iref.g.21"></span> User-Agent = "User-Agent" ":" 1*( product | comment ) 1539 1540 </pre><p id="rfc.section.10.9.p.3">Example:</p> 1540 <div id="rfc.figure.u.2 8"></div><pre class="text"> User-Agent: CERN-LineMode/2.15 libwww/2.17b31541 <div id="rfc.figure.u.29"></div><pre class="text"> User-Agent: CERN-LineMode/2.15 libwww/2.17b3 1541 1542 </pre><h1 id="rfc.section.11"><a href="#rfc.section.11">11.</a> <a id="IANA.considerations" href="#IANA.considerations">IANA Considerations</a></h1> 1542 1543 <p id="rfc.section.11.p.1"> <span class="comment">[rfc.comment.1: TBD.]</span> … … 1714 1715 </p> 1715 1716 <p id="rfc.section.A.2.p.4">In the description of the Server header, the Via field was described as a SHOULD. The requirement was and is stated correctly 1716 in the description of the Via header in <a href="p1-messaging.html#header.via" title="Via">Section 8.9</a> of <a href="#Part1" id="rfc.xref.Part1.2 6"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>. (<a href="#header.server" id="rfc.xref.header.server.3" title="Server">Section 10.8</a>)1717 in the description of the Via header in <a href="p1-messaging.html#header.via" title="Via">Section 8.9</a> of <a href="#Part1" id="rfc.xref.Part1.25"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>. (<a href="#header.server" id="rfc.xref.header.server.3" title="Server">Section 10.8</a>) 1717 1718 </p> 1718 1719 <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a> Change Log (to be removed by RFC Editor before publication) … … 1762 1763 <li>Move "Product Tokens" section (back) into Part 1, as "token" is used in the definition of the Upgrade header.</li> 1763 1764 <li>Add explicit references to BNF syntax and rules imported from other parts of the specification.</li> 1764 <li> Move definition of "delta-seconds" into Part1 as a common BNF element.</li>1765 <li>Copy definition of delta-seconds from Part6 instead of referencing it.</li> 1765 1766 </ul> 1766 1767 <h1><a id="rfc.copyright" href="#rfc.copyright">Full Copyright Statement</a></h1> … … 1877 1878 <ul class="ind"> 1878 1879 <li class="indline1"><tt>Allow</tt> <a class="iref" href="#rfc.iref.g.9"><b>10.1</b></a></li> 1880 <li class="indline1"><tt>delta-seconds</tt> <a class="iref" href="#rfc.iref.g.19"><b>10.7</b></a></li> 1879 1881 <li class="indline1"><tt>Expect</tt> <a class="iref" href="#rfc.iref.g.10"><b>10.2</b></a></li> 1880 1882 <li class="indline1"><tt>expect-params</tt> <a class="iref" href="#rfc.iref.g.13"><b>10.2</b></a></li> … … 1892 1894 <li class="indline1"><tt>response-header</tt> <a class="iref" href="#rfc.iref.g.7"><b>6</b></a></li> 1893 1895 <li class="indline1"><tt>Retry-After</tt> <a class="iref" href="#rfc.iref.g.18"><b>10.7</b></a></li> 1894 <li class="indline1"><tt>Server</tt> <a class="iref" href="#rfc.iref.g. 19"><b>10.8</b></a></li>1896 <li class="indline1"><tt>Server</tt> <a class="iref" href="#rfc.iref.g.20"><b>10.8</b></a></li> 1895 1897 <li class="indline1"><tt>Status-Code</tt> <a class="iref" href="#rfc.iref.g.4"><b>5</b></a></li> 1896 <li class="indline1"><tt>User-Agent</tt> <a class="iref" href="#rfc.iref.g.2 0"><b>10.9</b></a></li>1898 <li class="indline1"><tt>User-Agent</tt> <a class="iref" href="#rfc.iref.g.21"><b>10.9</b></a></li> 1897 1899 </ul> 1898 1900 </li> … … 1946 1948 </li> 1947 1949 <li class="indline0"><a id="rfc.index.P" href="#rfc.index.P"><b>P</b></a><ul class="ind"> 1948 <li class="indline1"><em>Part1</em> <a class="iref" href="#rfc.xref.Part1.1">1</a>, <a class="iref" href="#rfc.xref.Part1.2">2</a>, <a class="iref" href="#rfc.xref.Part1.3">2</a>, <a class="iref" href="#rfc.xref.Part1.4">2</a>, <a class="iref" href="#rfc.xref.Part1.5">2</a>, <a class="iref" href="#rfc.xref.Part1.6">2</a>, <a class="iref" href="#rfc.xref.Part1.7">2</a>, <a class="iref" href="#rfc.xref.Part1.8">2</a>, <a class="iref" href="#rfc.xref.Part1.9">2</a>, <a class="iref" href="#rfc.xref.Part1.10">2</a>, <a class="iref" href="#rfc.xref.Part1.11">2</a>, <a class="iref" href="#rfc.xref.Part1.12">2</a>, <a class="iref" href="#rfc.xref.Part1.13">2</a>, <a class="iref" href="#rfc.xref.Part1.14">2</a>, <a class="iref" href="#rfc.xref.Part1.15"> 2</a>, <a class="iref" href="#rfc.xref.Part1.16">4</a>, <a class="iref" href="#rfc.xref.Part1.17">4</a>, <a class="iref" href="#rfc.xref.Part1.18">7</a>, <a class="iref" href="#rfc.xref.Part1.19">8.8</a>, <a class="iref" href="#rfc.xref.Part1.20">9.1.1</a>, <a class="iref" href="#rfc.xref.Part1.21">9.5.6</a>, <a class="iref" href="#rfc.xref.Part1.22">10.2</a>, <a class="iref" href="#rfc.xref.Part1.23">10.8</a>, <a class="iref" href="#rfc.xref.Part1.24">10.8</a>, <a class="iref" href="#rfc.xref.Part1.25">10.9</a>, <a class="iref" href="#Part1"><b>14.1</b></a>, <a class="iref" href="#rfc.xref.Part1.26">A.2</a><ul class="ind">1950 <li class="indline1"><em>Part1</em> <a class="iref" href="#rfc.xref.Part1.1">1</a>, <a class="iref" href="#rfc.xref.Part1.2">2</a>, <a class="iref" href="#rfc.xref.Part1.3">2</a>, <a class="iref" href="#rfc.xref.Part1.4">2</a>, <a class="iref" href="#rfc.xref.Part1.5">2</a>, <a class="iref" href="#rfc.xref.Part1.6">2</a>, <a class="iref" href="#rfc.xref.Part1.7">2</a>, <a class="iref" href="#rfc.xref.Part1.8">2</a>, <a class="iref" href="#rfc.xref.Part1.9">2</a>, <a class="iref" href="#rfc.xref.Part1.10">2</a>, <a class="iref" href="#rfc.xref.Part1.11">2</a>, <a class="iref" href="#rfc.xref.Part1.12">2</a>, <a class="iref" href="#rfc.xref.Part1.13">2</a>, <a class="iref" href="#rfc.xref.Part1.14">2</a>, <a class="iref" href="#rfc.xref.Part1.15">4</a>, <a class="iref" href="#rfc.xref.Part1.16">4</a>, <a class="iref" href="#rfc.xref.Part1.17">7</a>, <a class="iref" href="#rfc.xref.Part1.18">8.8</a>, <a class="iref" href="#rfc.xref.Part1.19">9.1.1</a>, <a class="iref" href="#rfc.xref.Part1.20">9.5.6</a>, <a class="iref" href="#rfc.xref.Part1.21">10.2</a>, <a class="iref" href="#rfc.xref.Part1.22">10.8</a>, <a class="iref" href="#rfc.xref.Part1.23">10.8</a>, <a class="iref" href="#rfc.xref.Part1.24">10.9</a>, <a class="iref" href="#Part1"><b>14.1</b></a>, <a class="iref" href="#rfc.xref.Part1.25">A.2</a><ul class="ind"> 1949 1951 <li class="indline1"><em>Section 2.1</em> <a class="iref" href="#rfc.xref.Part1.2">2</a></li> 1950 1952 <li class="indline1"><em>Section 2.2</em> <a class="iref" href="#rfc.xref.Part1.3">2</a>, <a class="iref" href="#rfc.xref.Part1.4">2</a>, <a class="iref" href="#rfc.xref.Part1.5">2</a>, <a class="iref" href="#rfc.xref.Part1.6">2</a>, <a class="iref" href="#rfc.xref.Part1.7">2</a></li> 1951 <li class="indline1"><em>Section 3.1</em> <a class="iref" href="#rfc.xref.Part1.21">9.5.6</a></li> 1952 <li class="indline1"><em>Section 3.2.1</em> <a class="iref" href="#rfc.xref.Part1.8">2</a>, <a class="iref" href="#rfc.xref.Part1.10">2</a>, <a class="iref" href="#rfc.xref.Part1.14">2</a></li> 1953 <li class="indline1"><em>Section 3.3.1</em> <a class="iref" href="#rfc.xref.Part1.12">2</a></li> 1954 <li class="indline1"><em>Section 3.3.2</em> <a class="iref" href="#rfc.xref.Part1.9">2</a></li> 1955 <li class="indline1"><em>Section 3.5</em> <a class="iref" href="#rfc.xref.Part1.13">2</a>, <a class="iref" href="#rfc.xref.Part1.23">10.8</a>, <a class="iref" href="#rfc.xref.Part1.25">10.9</a></li> 1956 <li class="indline1"><em>Section 4.3</em> <a class="iref" href="#rfc.xref.Part1.18">7</a></li> 1957 <li class="indline1"><em>Section 7.2.3</em> <a class="iref" href="#rfc.xref.Part1.20">9.1.1</a>, <a class="iref" href="#rfc.xref.Part1.22">10.2</a></li> 1958 <li class="indline1"><em>Section 8.4</em> <a class="iref" href="#rfc.xref.Part1.11">2</a>, <a class="iref" href="#rfc.xref.Part1.16">4</a></li> 1959 <li class="indline1"><em>Section 8.8</em> <a class="iref" href="#rfc.xref.Part1.15">2</a>, <a class="iref" href="#rfc.xref.Part1.17">4</a></li> 1960 <li class="indline1"><em>Section 8.9</em> <a class="iref" href="#rfc.xref.Part1.19">8.8</a>, <a class="iref" href="#rfc.xref.Part1.24">10.8</a>, <a class="iref" href="#rfc.xref.Part1.26">A.2</a></li> 1953 <li class="indline1"><em>Section 3.1</em> <a class="iref" href="#rfc.xref.Part1.20">9.5.6</a></li> 1954 <li class="indline1"><em>Section 3.2.1</em> <a class="iref" href="#rfc.xref.Part1.8">2</a>, <a class="iref" href="#rfc.xref.Part1.9">2</a>, <a class="iref" href="#rfc.xref.Part1.13">2</a></li> 1955 <li class="indline1"><em>Section 3.3.1</em> <a class="iref" href="#rfc.xref.Part1.11">2</a></li> 1956 <li class="indline1"><em>Section 3.5</em> <a class="iref" href="#rfc.xref.Part1.12">2</a>, <a class="iref" href="#rfc.xref.Part1.22">10.8</a>, <a class="iref" href="#rfc.xref.Part1.24">10.9</a></li> 1957 <li class="indline1"><em>Section 4.3</em> <a class="iref" href="#rfc.xref.Part1.17">7</a></li> 1958 <li class="indline1"><em>Section 7.2.3</em> <a class="iref" href="#rfc.xref.Part1.19">9.1.1</a>, <a class="iref" href="#rfc.xref.Part1.21">10.2</a></li> 1959 <li class="indline1"><em>Section 8.4</em> <a class="iref" href="#rfc.xref.Part1.10">2</a>, <a class="iref" href="#rfc.xref.Part1.15">4</a></li> 1960 <li class="indline1"><em>Section 8.8</em> <a class="iref" href="#rfc.xref.Part1.14">2</a>, <a class="iref" href="#rfc.xref.Part1.16">4</a></li> 1961 <li class="indline1"><em>Section 8.9</em> <a class="iref" href="#rfc.xref.Part1.18">8.8</a>, <a class="iref" href="#rfc.xref.Part1.23">10.8</a>, <a class="iref" href="#rfc.xref.Part1.25">A.2</a></li> 1961 1962 </ul> 1962 1963 </li>
Note: See TracChangeset
for help on using the changeset viewer.