Changeset 2187 for draft-ietf-httpbis/latest/p2-semantics.html
- Timestamp:
- 22/02/13 03:32:08 (8 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p2-semantics.html
r2186 r2187 449 449 } 450 450 @bottom-center { 451 content: "Expires August 2 5, 2013";451 content: "Expires August 26, 2013"; 452 452 } 453 453 @bottom-right { … … 489 489 <link href="p1-messaging.html" rel="prev"> 490 490 <link href="p4-conditional.html" rel="next"> 491 <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.590, 2013/01/23 17:59:36, XSLT vendor: SAXON 8.9from Saxonica http://www.saxonica.com/">491 <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.590, 2013/01/23 17:59:36, XSLT vendor: SAXON 9.1.0.8 from Saxonica http://www.saxonica.com/"> 492 492 <link rel="schema.dct" href="http://purl.org/dc/terms/"> 493 493 <meta name="dct.creator" content="Fielding, R."> 494 494 <meta name="dct.creator" content="Reschke, J. F."> 495 495 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p2-semantics-latest"> 496 <meta name="dct.issued" scheme="ISO8601" content="2013-02-2 1">496 <meta name="dct.issued" scheme="ISO8601" content="2013-02-22"> 497 497 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 498 498 <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. This document defines the semantics of HTTP/1.1 messages, as expressed by request methods, request header fields, response status codes, and response header fields, along with the payload of messages (metadata and body content) and mechanisms for content negotiation."> … … 522 522 <tr> 523 523 <td class="left">Intended status: Standards Track</td> 524 <td class="right">February 2 1, 2013</td>524 <td class="right">February 22, 2013</td> 525 525 </tr> 526 526 <tr> 527 <td class="left">Expires: August 2 5, 2013</td>527 <td class="left">Expires: August 26, 2013</td> 528 528 <td class="right"></td> 529 529 </tr> … … 553 553 in progress”. 554 554 </p> 555 <p>This Internet-Draft will expire on August 2 5, 2013.</p>555 <p>This Internet-Draft will expire on August 26, 2013.</p> 556 556 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 557 557 <p>Copyright © 2013 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 2510 2510 </p> 2511 2511 <p id="rfc.section.6.3.5.p.5">A 204 response is terminated by the first empty line after the header fields because it cannot contain a message body.</p> 2512 <p id="rfc.section.6.3.5.p.6">A 204 response is cacheable unless otherwise indicated by the method definition or explicit cache controls (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 4.1.2</a> of <a href="#Part6" id="rfc.xref.Part6.14"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>). 2513 </p> 2512 2514 <div id="rfc.iref.74"></div> 2513 2515 <h3 id="rfc.section.6.3.6"><a href="#rfc.section.6.3.6">6.3.6</a> <a id="status.205" href="#status.205">205 Reset Content</a></h3> … … 2573 2575 for such automatic selection. 2574 2576 </p> 2575 <p id="rfc.section.6.4.1.p.4">A 300 response is cacheable unless otherwise indicated by the method definition or explicit cache controls (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 4.1.2</a> of <a href="#Part6" id="rfc.xref.Part6.1 4"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>).2577 <p id="rfc.section.6.4.1.p.4">A 300 response is cacheable unless otherwise indicated by the method definition or explicit cache controls (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 4.1.2</a> of <a href="#Part6" id="rfc.xref.Part6.15"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>). 2576 2578 </p> 2577 2579 <div class="note" id="rfc.section.6.4.1.p.5"> … … 2595 2597 </p> 2596 2598 </div> 2597 <p id="rfc.section.6.4.2.p.4">A 301 response is cacheable unless otherwise indicated by the method definition or explicit cache controls (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 4.1.2</a> of <a href="#Part6" id="rfc.xref.Part6.1 5"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>).2599 <p id="rfc.section.6.4.2.p.4">A 301 response is cacheable unless otherwise indicated by the method definition or explicit cache controls (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 4.1.2</a> of <a href="#Part6" id="rfc.xref.Part6.16"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>). 2598 2600 </p> 2599 2601 <div id="rfc.iref.75"></div> … … 2679 2681 is likely to be permanent. 2680 2682 </p> 2683 <p id="rfc.section.6.5.4.p.2">A 404 response is cacheable unless otherwise indicated by the method definition or explicit cache controls (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 4.1.2</a> of <a href="#Part6" id="rfc.xref.Part6.17"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>). 2684 </p> 2681 2685 <div id="rfc.iref.76"></div> 2682 2686 <h3 id="rfc.section.6.5.5"><a href="#rfc.section.6.5.5">6.5.5</a> <a id="status.405" href="#status.405">405 Method Not Allowed</a></h3> 2683 2687 <p id="rfc.section.6.5.5.p.1">The <dfn>405 (Method Not Allowed)</dfn> status code indicates that the method specified in the request-line is known by the origin server but not supported by the <a href="#resources" class="smpl">target resource</a>. The origin server <em class="bcp14">MUST</em> generate an <a href="#header.allow" class="smpl">Allow</a> header field in a 405 response containing a list of the target resource's currently supported methods. 2688 </p> 2689 <p id="rfc.section.6.5.5.p.2">A 405 response is cacheable unless otherwise indicated by the method definition or explicit cache controls (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 4.1.2</a> of <a href="#Part6" id="rfc.xref.Part6.18"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>). 2684 2690 </p> 2685 2691 <div id="rfc.iref.76"></div> … … 2718 2724 any length of time — that is left to the discretion of the server owner. 2719 2725 </p> 2720 <p id="rfc.section.6.5.9.p.3">A 410 response is cacheable unless otherwise indicated by the method definition or explicit cache controls (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 4.1.2</a> of <a href="#Part6" id="rfc.xref.Part6.1 6"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>).2726 <p id="rfc.section.6.5.9.p.3">A 410 response is cacheable unless otherwise indicated by the method definition or explicit cache controls (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 4.1.2</a> of <a href="#Part6" id="rfc.xref.Part6.19"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>). 2721 2727 </p> 2722 2728 <div id="rfc.iref.76"></div> … … 2738 2744 redirection (e.g., a redirected URI prefix that points to a suffix of itself), or when the server is under attack by a client 2739 2745 attempting to exploit potential security holes. 2746 </p> 2747 <p id="rfc.section.6.5.12.p.2">A 414 response is cacheable unless otherwise indicated by the method definition or explicit cache controls (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 4.1.2</a> of <a href="#Part6" id="rfc.xref.Part6.20"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>). 2740 2748 </p> 2741 2749 <div id="rfc.iref.76"></div> … … 2776 2784 <p id="rfc.section.6.6.2.p.1">The <dfn>501 (Not Implemented)</dfn> status code indicates that the server does not support the functionality required to fulfill the request. This is the appropriate 2777 2785 response when the server does not recognize the request method and is not capable of supporting it for any resource. 2786 </p> 2787 <p id="rfc.section.6.6.2.p.2">A 501 response is cacheable unless otherwise indicated by the method definition or explicit cache controls (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 4.1.2</a> of <a href="#Part6" id="rfc.xref.Part6.21"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>). 2778 2788 </p> 2779 2789 <div id="rfc.iref.77"></div> … … 2826 2836 <tr> 2827 2837 <td class="left">Age</td> 2828 <td class="left"><a href="p6-cache.html#header.age" title="Age">Section 7.1</a> of <a href="#Part6" id="rfc.xref.Part6. 17"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a></td>2838 <td class="left"><a href="p6-cache.html#header.age" title="Age">Section 7.1</a> of <a href="#Part6" id="rfc.xref.Part6.22"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a></td> 2829 2839 </tr> 2830 2840 <tr> 2831 2841 <td class="left">Cache-Control</td> 2832 <td class="left"><a href="p6-cache.html#header.cache-control" title="Cache-Control">Section 7.2</a> of <a href="#Part6" id="rfc.xref.Part6. 18"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a></td>2842 <td class="left"><a href="p6-cache.html#header.cache-control" title="Cache-Control">Section 7.2</a> of <a href="#Part6" id="rfc.xref.Part6.23"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a></td> 2833 2843 </tr> 2834 2844 <tr> 2835 2845 <td class="left">Expires</td> 2836 <td class="left"><a href="p6-cache.html#header.expires" title="Expires">Section 7.3</a> of <a href="#Part6" id="rfc.xref.Part6. 19"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a></td>2846 <td class="left"><a href="p6-cache.html#header.expires" title="Expires">Section 7.3</a> of <a href="#Part6" id="rfc.xref.Part6.24"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a></td> 2837 2847 </tr> 2838 2848 <tr> … … 2854 2864 <tr> 2855 2865 <td class="left">Warning</td> 2856 <td class="left"><a href="p6-cache.html#header.warning" title="Warning">Section 7.5</a> of <a href="#Part6" id="rfc.xref.Part6.2 0"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a></td>2866 <td class="left"><a href="p6-cache.html#header.warning" title="Warning">Section 7.5</a> of <a href="#Part6" id="rfc.xref.Part6.25"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a></td> 2857 2867 </tr> 2858 2868 </tbody> … … 3048 3058 <li> 3049 3059 <p>To inform cache recipients that they <em class="bcp14">MUST NOT</em> use this response to satisfy a later request unless the later request has the same values for the listed fields as the original 3050 request (<a href="p6-cache.html#caching.negotiated.responses" title="Using Negotiated Responses">Section 4.3</a> of <a href="#Part6" id="rfc.xref.Part6.2 1"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>). In other words, Vary expands the cache key required to match a new request to the stored cache entry.3060 request (<a href="p6-cache.html#caching.negotiated.responses" title="Using Negotiated Responses">Section 4.3</a> of <a href="#Part6" id="rfc.xref.Part6.26"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>). In other words, Vary expands the cache key required to match a new request to the stored cache entry. 3051 3061 </p> 3052 3062 </li> … … 3060 3070 other than the method and request target, unless the variance cannot be crossed or the origin server has been deliberately 3061 3071 configured to prevent cache transparency. For example, there is no need to send the Authorization field name in Vary because 3062 reuse across users is constrained by the field definition (<a href="p7-auth.html#header.authorization" title="Authorization">Section 4.1</a> of <a href="#Part7" id="rfc.xref.Part7.8"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Authentication">[Part7]</cite></a>). Likewise, an origin server might use Cache-Control directives (<a href="p6-cache.html#header.cache-control" title="Cache-Control">Section 7.2</a> of <a href="#Part6" id="rfc.xref.Part6.2 2"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>) to supplant Vary if it considers the variance less significant than the performance cost of Vary's impact on caching.3072 reuse across users is constrained by the field definition (<a href="p7-auth.html#header.authorization" title="Authorization">Section 4.1</a> of <a href="#Part7" id="rfc.xref.Part7.8"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Authentication">[Part7]</cite></a>). Likewise, an origin server might use Cache-Control directives (<a href="p6-cache.html#header.cache-control" title="Cache-Control">Section 7.2</a> of <a href="#Part6" id="rfc.xref.Part6.27"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>) to supplant Vary if it considers the variance less significant than the performance cost of Vary's impact on caching. 3063 3073 </p> 3064 3074 <div id="rfc.iref.s.8"></div> … … 3310 3320 if the response they occur in has explicit freshness information; however, status codes that are defined as being cacheable 3311 3321 are allowed to be cached without explicit freshness information. Likewise, the definition of a status code can place constraints 3312 upon cache behaviour. See <a href="#Part6" id="rfc.xref.Part6.2 3"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a> for more information.3322 upon cache behaviour. See <a href="#Part6" id="rfc.xref.Part6.28"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a> for more information. 3313 3323 </p> 3314 3324 <p id="rfc.section.8.2.2.p.6">Finally, the definition of a new status code ought to indicate whether the payload has any implied association with an identified … … 3612 3622 </li> 3613 3623 <li> 3614 <p>How the header field might interact with caching (see <a href="#Part6" id="rfc.xref.Part6.2 4"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>).3624 <p>How the header field might interact with caching (see <a href="#Part6" id="rfc.xref.Part6.29"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>). 3615 3625 </p> 3616 3626 </li> … … 4231 4241 <p id="rfc.section.B.p.22">The <a href="#status.426" class="smpl">426 (Upgrade Required)</a> status code has been incorporated from <a href="#RFC2817" id="rfc.xref.RFC2817.3"><cite title="Upgrading to TLS Within HTTP/1.1">[RFC2817]</cite></a> (<a href="#status.426" id="rfc.xref.status.426.3" title="426 Upgrade Required">Section 6.5.15</a>). 4232 4242 </p> 4233 <p id="rfc.section.B.p.23"> <a href="#header.allow" class="smpl">Allow</a> has been reclassified as a response header field, removing the option to specify it in a PUT request. Requirements relating 4243 <p id="rfc.section.B.p.23">The following status codes are now cacheable (that is, they can be stored and reused by a cache without explicit freshness 4244 information present): 204, 404, 405, 414, 501. 4245 </p> 4246 <p id="rfc.section.B.p.24"> <a href="#header.allow" class="smpl">Allow</a> has been reclassified as a response header field, removing the option to specify it in a PUT request. Requirements relating 4234 4247 to the content of Allow have been relaxed; correspondingly, clients are not required to always trust its value (<a href="#header.allow" id="rfc.xref.header.allow.4" title="Allow">Section 7.4.1</a>). 4235 4248 </p> 4236 <p id="rfc.section.B.p.2 4">The target of requirements on HTTP-date and the Date header field have been reduced to those systems generating the date,4249 <p id="rfc.section.B.p.25">The target of requirements on HTTP-date and the Date header field have been reduced to those systems generating the date, 4237 4250 rather than all systems sending a date (<a href="#origination.date" title="Origination Date">Section 7.1.1</a>). 4238 4251 </p> 4239 <p id="rfc.section.B.p.2 5">The syntax of the <a href="#header.location" class="smpl">Location</a> header field has been changed to allow all URI references, including relative references and fragments, along with some clarifications4252 <p id="rfc.section.B.p.26">The syntax of the <a href="#header.location" class="smpl">Location</a> header field has been changed to allow all URI references, including relative references and fragments, along with some clarifications 4240 4253 as to when use of fragments would not be appropriate (<a href="#header.location" id="rfc.xref.header.location.6" title="Location">Section 7.1.2</a>). 4241 4254 </p> 4242 <p id="rfc.section.B.p.2 6">A Method Registry has been defined (<a href="#method.registry" title="Method Registry">Section 8.1</a>).4243 </p> 4244 <p id="rfc.section.B.p.2 7">The Status Code Registry (<a href="#status.code.registry" title="Status Code Registry">Section 8.2</a>) has been redefined by this specification; previously, it was defined in <a href="http://tools.ietf.org/html/rfc2817#section-7.1">Section 7.1</a> of <a href="#RFC2817" id="rfc.xref.RFC2817.4"><cite title="Upgrading to TLS Within HTTP/1.1">[RFC2817]</cite></a>.4245 </p> 4246 <p id="rfc.section.B.p.2 8">Registration of Content Codings has been changed to require IETF Review (<a href="#content.coding.registry" title="Content Coding Registry">Section 8.4</a>).4255 <p id="rfc.section.B.p.27">A Method Registry has been defined (<a href="#method.registry" title="Method Registry">Section 8.1</a>). 4256 </p> 4257 <p id="rfc.section.B.p.28">The Status Code Registry (<a href="#status.code.registry" title="Status Code Registry">Section 8.2</a>) has been redefined by this specification; previously, it was defined in <a href="http://tools.ietf.org/html/rfc2817#section-7.1">Section 7.1</a> of <a href="#RFC2817" id="rfc.xref.RFC2817.4"><cite title="Upgrading to TLS Within HTTP/1.1">[RFC2817]</cite></a>. 4258 </p> 4259 <p id="rfc.section.B.p.29">Registration of Content Codings has been changed to require IETF Review (<a href="#content.coding.registry" title="Content Coding Registry">Section 8.4</a>). 4247 4260 </p> 4248 4261 <h1 id="rfc.section.C"><a href="#rfc.section.C">C.</a> <a id="imported.abnf" href="#imported.abnf">Imported ABNF</a></h1> … … 4433 4446 </li> 4434 4447 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/434">http://tools.ietf.org/wg/httpbis/trac/ticket/434</a>>: "mention in header field considerations that leading/trailing WS is lossy" 4448 </li> 4449 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/432">http://tools.ietf.org/wg/httpbis/trac/ticket/432</a>>: "Identify additional status codes as cacheable by default" 4435 4450 </li> 4436 4451 </ul> … … 4688 4703 </ul> 4689 4704 </li> 4690 <li><em>Part6</em> <a href="#rfc.xref.Part6.1">4.2.3</a>, <a href="#rfc.xref.Part6.2">4.3.1</a>, <a href="#rfc.xref.Part6.3">4.3.2</a>, <a href="#rfc.xref.Part6.4">4.3.2</a>, <a href="#rfc.xref.Part6.5">4.3.3</a>, <a href="#rfc.xref.Part6.6">4.3.4</a>, <a href="#rfc.xref.Part6.7">4.3.5</a>, <a href="#rfc.xref.Part6.8">5.1</a>, <a href="#rfc.xref.Part6.9">5.1</a>, <a href="#rfc.xref.Part6.10">6.1</a>, <a href="#rfc.xref.Part6.11">6.3.1</a>, <a href="#rfc.xref.Part6.12">6.3.4</a>, <a href="#rfc.xref.Part6.13">6.3.4</a>, <a href="#rfc.xref.Part6.14">6. 4.1</a>, <a href="#rfc.xref.Part6.15">6.4.2</a>, <a href="#rfc.xref.Part6.16">6.5.9</a>, <a href="#rfc.xref.Part6.17">7.1</a>, <a href="#rfc.xref.Part6.18">7.1</a>, <a href="#rfc.xref.Part6.19">7.1</a>, <a href="#rfc.xref.Part6.20">7.1</a>, <a href="#rfc.xref.Part6.21">7.1.4</a>, <a href="#rfc.xref.Part6.22">7.1.4</a>, <a href="#rfc.xref.Part6.23">8.2.2</a>, <a href="#rfc.xref.Part6.24">8.3.1</a>, <a href="#Part6"><b>11.1</b></a><ul>4705 <li><em>Part6</em> <a href="#rfc.xref.Part6.1">4.2.3</a>, <a href="#rfc.xref.Part6.2">4.3.1</a>, <a href="#rfc.xref.Part6.3">4.3.2</a>, <a href="#rfc.xref.Part6.4">4.3.2</a>, <a href="#rfc.xref.Part6.5">4.3.3</a>, <a href="#rfc.xref.Part6.6">4.3.4</a>, <a href="#rfc.xref.Part6.7">4.3.5</a>, <a href="#rfc.xref.Part6.8">5.1</a>, <a href="#rfc.xref.Part6.9">5.1</a>, <a href="#rfc.xref.Part6.10">6.1</a>, <a href="#rfc.xref.Part6.11">6.3.1</a>, <a href="#rfc.xref.Part6.12">6.3.4</a>, <a href="#rfc.xref.Part6.13">6.3.4</a>, <a href="#rfc.xref.Part6.14">6.3.5</a>, <a href="#rfc.xref.Part6.15">6.4.1</a>, <a href="#rfc.xref.Part6.16">6.4.2</a>, <a href="#rfc.xref.Part6.17">6.5.4</a>, <a href="#rfc.xref.Part6.18">6.5.5</a>, <a href="#rfc.xref.Part6.19">6.5.9</a>, <a href="#rfc.xref.Part6.20">6.5.12</a>, <a href="#rfc.xref.Part6.21">6.6.2</a>, <a href="#rfc.xref.Part6.22">7.1</a>, <a href="#rfc.xref.Part6.23">7.1</a>, <a href="#rfc.xref.Part6.24">7.1</a>, <a href="#rfc.xref.Part6.25">7.1</a>, <a href="#rfc.xref.Part6.26">7.1.4</a>, <a href="#rfc.xref.Part6.27">7.1.4</a>, <a href="#rfc.xref.Part6.28">8.2.2</a>, <a href="#rfc.xref.Part6.29">8.3.1</a>, <a href="#Part6"><b>11.1</b></a><ul> 4691 4706 <li><em>Section 4.1.1</em> <a href="#rfc.xref.Part6.5">4.3.3</a></li> 4692 <li><em>Section 4.1.2</em> <a href="#rfc.xref.Part6.11">6.3.1</a>, <a href="#rfc.xref.Part6.13">6.3.4</a>, <a href="#rfc.xref.Part6.14">6. 4.1</a>, <a href="#rfc.xref.Part6.15">6.4.2</a>, <a href="#rfc.xref.Part6.16">6.5.9</a></li>4693 <li><em>Section 4.3</em> <a href="#rfc.xref.Part6.2 1">7.1.4</a></li>4707 <li><em>Section 4.1.2</em> <a href="#rfc.xref.Part6.11">6.3.1</a>, <a href="#rfc.xref.Part6.13">6.3.4</a>, <a href="#rfc.xref.Part6.14">6.3.5</a>, <a href="#rfc.xref.Part6.15">6.4.1</a>, <a href="#rfc.xref.Part6.16">6.4.2</a>, <a href="#rfc.xref.Part6.17">6.5.4</a>, <a href="#rfc.xref.Part6.18">6.5.5</a>, <a href="#rfc.xref.Part6.19">6.5.9</a>, <a href="#rfc.xref.Part6.20">6.5.12</a>, <a href="#rfc.xref.Part6.21">6.6.2</a></li> 4708 <li><em>Section 4.3</em> <a href="#rfc.xref.Part6.26">7.1.4</a></li> 4694 4709 <li><em>Section 5</em> <a href="#rfc.xref.Part6.4">4.3.2</a></li> 4695 4710 <li><em>Section 6</em> <a href="#rfc.xref.Part6.6">4.3.4</a>, <a href="#rfc.xref.Part6.7">4.3.5</a></li> 4696 <li><em>Section 7.1</em> <a href="#rfc.xref.Part6. 17">7.1</a></li>4697 <li><em>Section 7.2</em> <a href="#rfc.xref.Part6.2">4.3.1</a>, <a href="#rfc.xref.Part6.3">4.3.2</a>, <a href="#rfc.xref.Part6.8">5.1</a>, <a href="#rfc.xref.Part6. 18">7.1</a>, <a href="#rfc.xref.Part6.22">7.1.4</a></li>4698 <li><em>Section 7.3</em> <a href="#rfc.xref.Part6. 19">7.1</a></li>4711 <li><em>Section 7.1</em> <a href="#rfc.xref.Part6.22">7.1</a></li> 4712 <li><em>Section 7.2</em> <a href="#rfc.xref.Part6.2">4.3.1</a>, <a href="#rfc.xref.Part6.3">4.3.2</a>, <a href="#rfc.xref.Part6.8">5.1</a>, <a href="#rfc.xref.Part6.23">7.1</a>, <a href="#rfc.xref.Part6.27">7.1.4</a></li> 4713 <li><em>Section 7.3</em> <a href="#rfc.xref.Part6.24">7.1</a></li> 4699 4714 <li><em>Section 7.4</em> <a href="#rfc.xref.Part6.9">5.1</a></li> 4700 <li><em>Section 7.5</em> <a href="#rfc.xref.Part6.12">6.3.4</a>, <a href="#rfc.xref.Part6.2 0">7.1</a></li>4715 <li><em>Section 7.5</em> <a href="#rfc.xref.Part6.12">6.3.4</a>, <a href="#rfc.xref.Part6.25">7.1</a></li> 4701 4716 </ul> 4702 4717 </li>
Note: See TracChangeset
for help on using the changeset viewer.