Ignore:
Timestamp:
Dec 8, 2012, 9:47:57 AM (7 years ago)
Author:
julian.reschke@…
Message:

record recent changes done by Roy

File:
1 edited

Legend:

Unmodified
Added
Removed

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

    r2035 r2045  
    449449  }
    450450  @bottom-center {
    451        content: "Expires June 10, 2013";
     451       content: "Expires June 11, 2013";
    452452  }
    453453  @bottom-right {
    … …  
    472472      <link rel="Index" href="#rfc.index">
    473473      <link rel="Chapter" title="1 Introduction" href="#rfc.section.1">
    474       <link rel="Chapter" title="2 Resource" href="#rfc.section.2">
    475       <link rel="Chapter" title="3 Representation" href="#rfc.section.3">
     474      <link rel="Chapter" title="2 Resources" href="#rfc.section.2">
     475      <link rel="Chapter" title="3 Representations" href="#rfc.section.3">
    476476      <link rel="Chapter" title="4 Product Tokens" href="#rfc.section.4">
    477477      <link rel="Chapter" title="5 Request Methods" href="#rfc.section.5">
    … …  
    496496      <meta name="dct.creator" content="Reschke, J. F.">
    497497      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p2-semantics-latest">
    498       <meta name="dct.issued" scheme="ISO8601" content="2012-12-07">
     498      <meta name="dct.issued" scheme="ISO8601" content="2012-12-08">
    499499      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    500500      <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.">
    … …  
    524524            <tr>
    525525               <td class="left">Intended status: Standards Track</td>
    526                <td class="right">December 7, 2012</td>
     526               <td class="right">December 8, 2012</td>
    527527            </tr>
    528528            <tr>
    529                <td class="left">Expires: June 10, 2013</td>
     529               <td class="left">Expires: June 11, 2013</td>
    530530               <td class="right"></td>
    531531            </tr>
    … …  
    555555         in progress”.
    556556      </p>
    557       <p>This Internet-Draft will expire on June 10, 2013.</p>
     557      <p>This Internet-Draft will expire on June 11, 2013.</p>
    558558      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    559559      <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
    … …  
    578578            </ul>
    579579         </li>
    580          <li><a href="#rfc.section.2">2.</a>&nbsp;&nbsp;&nbsp;<a href="#resource">Resource</a></li>
    581          <li><a href="#rfc.section.3">3.</a>&nbsp;&nbsp;&nbsp;<a href="#representation">Representation</a><ul>
     580         <li><a href="#rfc.section.2">2.</a>&nbsp;&nbsp;&nbsp;<a href="#resources">Resources</a></li>
     581         <li><a href="#rfc.section.3">3.</a>&nbsp;&nbsp;&nbsp;<a href="#representations">Representations</a><ul>
    582582               <li><a href="#rfc.section.3.1">3.1</a>&nbsp;&nbsp;&nbsp;<a href="#representation.metadata">Representation Metadata</a><ul>
    583583                     <li><a href="#rfc.section.3.1.1">3.1.1</a>&nbsp;&nbsp;&nbsp;<a href="#data.type">Data Type</a><ul>
    … …  
    809809         This document defines HTTP/1.1 request and response semantics in terms of the architecture defined in <a href="#Part1" id="rfc.xref.Part1.1"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>.
    810810      </p>
    811       <p id="rfc.section.1.p.2">HTTP provides a uniform interface for interacting with a resource (<a href="#resource" title="Resource">Section&nbsp;2</a>), regardless of its type, nature, or implementation, and for transferring content in message payloads in the form of a representation
    812          (<a href="#representation" title="Representation">Section&nbsp;3</a>).
     811      <p id="rfc.section.1.p.2">HTTP provides a uniform interface for interacting with a resource (<a href="#resources" title="Resources">Section&nbsp;2</a>), regardless of its type, nature, or implementation, and for transferring content in message payloads in the form of a representation
     812         (<a href="#representations" title="Representations">Section&nbsp;3</a>).
    813813      </p>
    814814      <p id="rfc.section.1.p.3">HTTP semantics include the intentions defined by each request method (<a href="#methods" title="Request Methods">Section&nbsp;5</a>), extensions to those semantics that might be described in request header fields (<a href="#request.header.fields" title="Request Header Fields">Section&nbsp;6</a>), the meaning of status codes to indicate a machine-readable response (<a href="#status.codes" title="Response Status Codes">Section&nbsp;7</a>), and the meaning of other control data and resource metadata that might be given in response header fields (<a href="#response.header.fields" title="Response Header Fields">Section&nbsp;8</a>).
    … …  
    830830         defined in <a href="#RFC6365" id="rfc.xref.RFC6365.1"><cite title="Terminology Used in Internationalization in the IETF">[RFC6365]</cite></a>.
    831831      </p>
    832       <h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a>&nbsp;<a id="resource" href="#resource">Resource</a></h1>
     832      <h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a>&nbsp;<a id="resources" href="#resources">Resources</a></h1>
    833833      <p id="rfc.section.2.p.1">The target of each HTTP request is called a resource. HTTP does not limit the nature of a resource; it merely defines an interface
    834834         that might be used to interact with resources. Each resource is identified by a Uniform Resource Identifier (URI), as described
    … …  
    842842      </p>
    843843      <div id="rfc.iref.r.1"></div>
    844       <h1 id="rfc.section.3"><a href="#rfc.section.3">3.</a>&nbsp;<a id="representation" href="#representation">Representation</a></h1>
     844      <h1 id="rfc.section.3"><a href="#rfc.section.3">3.</a>&nbsp;<a id="representations" href="#representations">Representations</a></h1>
    845845      <p id="rfc.section.3.p.1">If we consider that a resource could be anything, and that the uniform interface provided by HTTP is similar to a window through
    846846         which one can observe and act upon such a thing only through the communication of messages to some independent actor on the
    … …  
    10111011         definition. Typically, the representation is only decoded just prior to rendering or analogous usage.
    10121012      </p>
    1013       <p id="rfc.section.3.1.2.2.p.7">A transforming proxy <em class="bcp14">MAY</em> modify the content coding if the new coding is known to be acceptable to the recipient, unless the "no-transform" cache-control
    1014          directive is present in the message.
    1015       </p>
    1016       <p id="rfc.section.3.1.2.2.p.8">If the media type includes an inherent encoding, such as a data format that is always compressed, then that encoding would
     1013      <p id="rfc.section.3.1.2.2.p.7">If the media type includes an inherent encoding, such as a data format that is always compressed, then that encoding would
    10171014         not be restated as a Content-Encoding even if it happens to be the same algorithm as one of the content codings. Such a content
    10181015         coding would only be listed if, for some bizarre reason, it is applied a second time to form the representation. Likewise,
    … …  
    10211018         as ..." dialog instead of automatic decompression and rendering of content).
    10221019      </p>
    1023       <p id="rfc.section.3.1.2.2.p.9">If the content-coding of a representation in a request message is not acceptable to the origin server, the server <em class="bcp14">SHOULD</em> respond with a status code of 415 (Unsupported Media Type).
     1020      <p id="rfc.section.3.1.2.2.p.8">If the content-coding of a representation in a request message is not acceptable to the origin server, the server <em class="bcp14">SHOULD</em> respond with a status code of 415 (Unsupported Media Type).
    10241021      </p>
    10251022      <h3 id="rfc.section.3.1.3"><a href="#rfc.section.3.1.3">3.1.3</a>&nbsp;<a id="audience.language" href="#audience.language">Audience Language</a></h3>
    … …  
    24442441      <div id="rfc.iref.72"></div>
    24452442      <h3 id="rfc.section.7.3.4"><a href="#rfc.section.7.3.4">7.3.4</a>&nbsp;<a id="status.203" href="#status.203">203 Non-Authoritative Information</a></h3>
    2446       <p id="rfc.section.7.3.4.p.1">The representation in the response has been transformed or otherwise modified by a transforming proxy (<a href="p1-messaging.html#intermediaries" title="Intermediaries">Section 2.3</a> of <a href="#Part1" id="rfc.xref.Part1.23"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>). Note that the behavior of transforming intermediaries is controlled by the no-transform Cache-Control directive (<a href="p6-cache.html#header.cache-control" title="Cache-Control">Section 7.2</a> of <a href="#Part6" id="rfc.xref.Part6.9"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>).
    2447       </p>
    2448       <p id="rfc.section.7.3.4.p.2">This status code is only appropriate when the response status code would have been <a href="#status.200" class="smpl">200 (OK)</a> otherwise. When the status code before transformation would have been different, the 214 Transformation Applied warn-code
    2449          (<a href="p6-cache.html#header.warning" title="Warning">Section 7.5</a> of <a href="#Part6" id="rfc.xref.Part6.10"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>) is appropriate.
    2450       </p>
    2451       <p id="rfc.section.7.3.4.p.3">Caches <em class="bcp14">MAY</em> use a heuristic (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.11"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>) to determine freshness for 203 responses.
     2443      <p id="rfc.section.7.3.4.p.1">The request was successful but the enclosed payload has been modified from that of the origin server's <a href="#status.200" class="smpl">200 (OK)</a> response by a transforming proxy (<a href="p1-messaging.html#message.transformations" title="Transformations">Section 5.7.2</a> of <a href="#Part1" id="rfc.xref.Part1.23"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>). This status code allows the proxy to notify recipients when a transformation has been applied, since that knowledge might
     2444         impact later decisions regarding the content. For example, future cache validation requests for the content might only be
     2445         applicable along the same request path (through the same proxies).
     2446      </p>
     2447      <p id="rfc.section.7.3.4.p.2">The 203 response is similar to the Warning code of 214 Transformation Applied (<a href="p6-cache.html#header.warning" title="Warning">Section 7.5</a> of <a href="#Part6" id="rfc.xref.Part6.9"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>), which has the advantage of being applicable to responses with any status code.
    24522448      </p>
    24532449      <div id="rfc.iref.72"></div>
    … …  
    25352531      <p id="rfc.section.7.4.1.p.3">If the server has a preferred choice of representation, it <em class="bcp14">SHOULD</em> include the specific URI for that representation in the <a href="#header.location" class="smpl">Location</a> field; user agents <em class="bcp14">MAY</em> use the Location field value for automatic redirection.
    25362532      </p>
    2537       <p id="rfc.section.7.4.1.p.4">Caches <em class="bcp14">MAY</em> use a heuristic (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.12"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>) to determine freshness for 300 responses.
     2533      <p id="rfc.section.7.4.1.p.4">Caches <em class="bcp14">MAY</em> use a heuristic (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.10"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>) to determine freshness for 300 responses.
    25382534      </p>
    25392535      <div id="rfc.iref.73"></div>
    … …  
    25422538         request URI to one or more of the new references returned by the server, where possible.
    25432539      </p>
    2544       <p id="rfc.section.7.4.2.p.2">Caches <em class="bcp14">MAY</em> use a heuristic (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.13"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>) to determine freshness for 301 responses.
     2540      <p id="rfc.section.7.4.2.p.2">Caches <em class="bcp14">MAY</em> use a heuristic (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.11"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>) to determine freshness for 301 responses.
    25452541      </p>
    25462542      <p id="rfc.section.7.4.2.p.3">The new permanent URI <em class="bcp14">SHOULD</em> be given by the <a href="#header.location" class="smpl">Location</a> field in the response. A response payload can contain a short hypertext note with a hyperlink to the new URI(s).
    … …  
    26772673         — that is left to the discretion of the server owner.
    26782674      </p>
    2679       <p id="rfc.section.7.5.9.p.3">Caches <em class="bcp14">MAY</em> use a heuristic (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>) to determine freshness for 410 responses.
     2675      <p id="rfc.section.7.5.9.p.3">Caches <em class="bcp14">MAY</em> use a heuristic (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.12"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>) to determine freshness for 410 responses.
    26802676      </p>
    26812677      <div id="rfc.iref.74"></div>
    … …  
    27892785               <tr>
    27902786                  <td class="left">Age</td>
    2791                   <td class="left"><a href="p6-cache.html#header.age" title="Age">Section 7.1</a> of <a href="#Part6" id="rfc.xref.Part6.15"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a></td>
     2787                  <td class="left"><a href="p6-cache.html#header.age" title="Age">Section 7.1</a> of <a href="#Part6" id="rfc.xref.Part6.13"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a></td>
    27922788               </tr>
    27932789               <tr>
    … …  
    30022998      <h3 id="rfc.section.8.2.1"><a href="#rfc.section.8.2.1">8.2.1</a>&nbsp;<a id="header.vary" href="#header.vary">Vary</a></h3>
    30032999      <p id="rfc.section.8.2.1.p.1">The "Vary" header field conveys the set of header fields that were used to select the representation.</p>
    3004       <p id="rfc.section.8.2.1.p.2">Caches use this information as part of determining whether a stored response can be used to satisfy a given 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.16"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>).
     3000      <p id="rfc.section.8.2.1.p.2">Caches use this information as part of determining whether a stored response can be used to satisfy a given 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.14"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>).
    30053001      </p>
    30063002      <p id="rfc.section.8.2.1.p.3">In uncacheable or stale responses, the Vary field value advises the user agent about the criteria that were used to select
    … …  
    32253221         code (e.g., combinations of request header fields and/or method(s)) along with any dependencies on response header fields
    32263222         (e.g., what fields are required and what fields can modify the semantics). A response that can transfer a payload ought to
    3227          specify expected cache behavior (e.g., cacheability and freshness criteria, as described in <a href="#Part6" id="rfc.xref.Part6.17"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>) and whether the payload has any implied association with an identified resource (<a href="#identifying.payload" title="Identifying a Representation">Section&nbsp;3.1.4.1</a>).
     3223         specify expected cache behavior (e.g., cacheability and freshness criteria, as described in <a href="#Part6" id="rfc.xref.Part6.15"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>) and whether the payload has any implied association with an identified resource (<a href="#identifying.payload" title="Identifying a Representation">Section&nbsp;3.1.4.1</a>).
    32283224      </p>
    32293225      <h3 id="rfc.section.9.2.3"><a href="#rfc.section.9.2.3">9.2.3</a>&nbsp;<a id="status.code.registration" href="#status.code.registration">Registrations</a></h3>
    … …  
    35153511         </li>
    35163512         <li>
    3517             <p>How the header field might interact with caching (see <a href="#Part6" id="rfc.xref.Part6.18"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>).
     3513            <p>How the header field might interact with caching (see <a href="#Part6" id="rfc.xref.Part6.16"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>).
    35183514            </p>
    35193515         </li>
    … …  
    40884084      </p>
    40894085      <h1 id="rfc.section.C"><a href="#rfc.section.C">C.</a>&nbsp;<a id="changes.from.rfc.2616" href="#changes.from.rfc.2616">Changes from RFC 2616</a></h1>
    4090       <p id="rfc.section.C.p.1">The term "representation" is introduced, replacing both "entity" and "variant." (<a href="#representation" title="Representation">Section&nbsp;3</a>)
     4086      <p id="rfc.section.C.p.1">The term "representation" is introduced, replacing both "entity" and "variant." (<a href="#representations" title="Representations">Section&nbsp;3</a>)
    40914087      </p>
    40924088      <p id="rfc.section.C.p.2">"Server-Driven" and "agent-driven" content negotiation are now called "proactive" and "reactive" content negotiation (respectively).
    … …  
    43404336      <ul>
    43414337         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/388">http://tools.ietf.org/wg/httpbis/trac/ticket/388</a>&gt;: "User confirmation for unsafe methods"
     4338         </li>
     4339         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/418">http://tools.ietf.org/wg/httpbis/trac/ticket/418</a>&gt;: "No-Transform"
     4340         </li>
     4341         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/419">http://tools.ietf.org/wg/httpbis/trac/ticket/419</a>&gt;: "p2 editorial feedback"
    43424342         </li>
    43434343      </ul>
    … …  
    45374537                  <li><em>Part1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.1">1</a>, <a href="#rfc.xref.Part1.2">1.1</a>, <a href="#rfc.xref.Part1.3">1.2</a>, <a href="#rfc.xref.Part1.4">2</a>, <a href="#rfc.xref.Part1.5">2</a>, <a href="#rfc.xref.Part1.6">2</a>, <a href="#rfc.xref.Part1.7">3.1.2.1</a>, <a href="#rfc.xref.Part1.8">3.1.2.1</a>, <a href="#rfc.xref.Part1.9">3.1.2.1</a>, <a href="#rfc.xref.Part1.10">3.1.2.2</a>, <a href="#rfc.xref.Part1.11">3.1.4.1</a>, <a href="#rfc.xref.Part1.12">3.1.4.2</a>, <a href="#rfc.xref.Part1.13">3.3</a>, <a href="#rfc.xref.Part1.14">3.3</a>, <a href="#rfc.xref.Part1.15">5.3.6</a>, <a href="#rfc.xref.Part1.16">5.3.7</a>, <a href="#rfc.xref.Part1.17">5.3.8</a>, <a href="#rfc.xref.Part1.18">5.3.8</a>, <a href="#rfc.xref.Part1.19">6.1</a>, <a href="#rfc.xref.Part1.20">6.5</a>, <a href="#rfc.xref.Part1.21">6.5.3</a>, <a href="#rfc.xref.Part1.22">7.2.2</a>, <a href="#rfc.xref.Part1.23">7.3.4</a>, <a href="#rfc.xref.Part1.24">7.3.6</a>, <a href="#rfc.xref.Part1.25">7.5.15</a>, <a href="#rfc.xref.Part1.26">7.6.6</a>, <a href="#rfc.xref.Part1.27">8</a>, <a href="#rfc.xref.Part1.28">8.4.2</a>, <a href="#rfc.xref.Part1.29">8.4.2</a>, <a href="#rfc.xref.Part1.30">9.1.2</a>, <a href="#rfc.xref.Part1.31">9.3.1</a>, <a href="#rfc.xref.Part1.32">9.3.1</a>, <a href="#rfc.xref.Part1.33">9.3.1</a>, <a href="#rfc.xref.Part1.34">9.3.1</a>, <a href="#rfc.xref.Part1.35">9.3.1</a>, <a href="#rfc.xref.Part1.36">9.3.1</a>, <a href="#rfc.xref.Part1.37">9.4</a>, <a href="#rfc.xref.Part1.38">9.4.1</a>, <a href="#rfc.xref.Part1.39">9.4.1</a>, <a href="#rfc.xref.Part1.40">9.4.2</a>, <a href="#rfc.xref.Part1.41">9.4.2</a>, <a href="#rfc.xref.Part1.42">9.4.2</a>, <a href="#rfc.xref.Part1.43">11</a>, <a href="#Part1"><b>12.1</b></a>, <a href="#rfc.xref.Part1.44">C</a>, <a href="#rfc.xref.Part1.45">D</a>, <a href="#rfc.xref.Part1.46">D</a>, <a href="#rfc.xref.Part1.47">D</a>, <a href="#rfc.xref.Part1.48">D</a>, <a href="#rfc.xref.Part1.49">D</a>, <a href="#rfc.xref.Part1.50">D</a>, <a href="#rfc.xref.Part1.51">D</a>, <a href="#rfc.xref.Part1.52">D</a>, <a href="#rfc.xref.Part1.53">D</a>, <a href="#rfc.xref.Part1.54">D</a>, <a href="#rfc.xref.Part1.55">D</a>, <a href="#rfc.xref.Part1.56">D</a><ul>
    45384538                        <li><em>Section 1.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.3">1.2</a></li>
    4539                         <li><em>Section 2.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.23">7.3.4</a></li>
    45404539                        <li><em>Section 2.5</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.2">1.1</a></li>
    45414540                        <li><em>Section 2.6</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.26">7.6.6</a></li>
    … …  
    45584557                        <li><em>Section 5.5</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.6">2</a>, <a href="#rfc.xref.Part1.11">3.1.4.1</a>, <a href="#rfc.xref.Part1.12">3.1.4.2</a>, <a href="#rfc.xref.Part1.27">8</a></li>
    45594558                        <li><em>Section 5.7.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.17">5.3.8</a>, <a href="#rfc.xref.Part1.29">8.4.2</a>, <a href="#rfc.xref.Part1.44">C</a></li>
     4559                        <li><em>Section 5.7.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.23">7.3.4</a></li>
    45604560                        <li><em>Section 6.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.35">9.3.1</a></li>
    45614561                        <li><em>Section 6.7</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.22">7.2.2</a>, <a href="#rfc.xref.Part1.25">7.5.15</a></li>
    … …  
    45874587                     </ul>
    45884588                  </li>
    4589                   <li><em>Part6</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.1">3.1</a>, <a href="#rfc.xref.Part6.2">5.2.3</a>, <a href="#rfc.xref.Part6.3">5.3.1</a>, <a href="#rfc.xref.Part6.4">5.3.2</a>, <a href="#rfc.xref.Part6.5">5.3.3</a>, <a href="#rfc.xref.Part6.6">5.3.4</a>, <a href="#rfc.xref.Part6.7">5.3.5</a>, <a href="#rfc.xref.Part6.8">7.3.1</a>, <a href="#rfc.xref.Part6.9">7.3.4</a>, <a href="#rfc.xref.Part6.10">7.3.4</a>, <a href="#rfc.xref.Part6.11">7.3.4</a>, <a href="#rfc.xref.Part6.12">7.4.1</a>, <a href="#rfc.xref.Part6.13">7.4.2</a>, <a href="#rfc.xref.Part6.14">7.5.9</a>, <a href="#rfc.xref.Part6.15">8.1</a>, <a href="#rfc.xref.Part6.16">8.2.1</a>, <a href="#rfc.xref.Part6.17">9.2.2</a>, <a href="#rfc.xref.Part6.18">9.3.1</a>, <a href="#Part6"><b>12.1</b></a><ul>
     4589                  <li><em>Part6</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.1">3.1</a>, <a href="#rfc.xref.Part6.2">5.2.3</a>, <a href="#rfc.xref.Part6.3">5.3.1</a>, <a href="#rfc.xref.Part6.4">5.3.2</a>, <a href="#rfc.xref.Part6.5">5.3.3</a>, <a href="#rfc.xref.Part6.6">5.3.4</a>, <a href="#rfc.xref.Part6.7">5.3.5</a>, <a href="#rfc.xref.Part6.8">7.3.1</a>, <a href="#rfc.xref.Part6.9">7.3.4</a>, <a href="#rfc.xref.Part6.10">7.4.1</a>, <a href="#rfc.xref.Part6.11">7.4.2</a>, <a href="#rfc.xref.Part6.12">7.5.9</a>, <a href="#rfc.xref.Part6.13">8.1</a>, <a href="#rfc.xref.Part6.14">8.2.1</a>, <a href="#rfc.xref.Part6.15">9.2.2</a>, <a href="#rfc.xref.Part6.16">9.3.1</a>, <a href="#Part6"><b>12.1</b></a><ul>
    45904590                        <li><em>Section 4.1.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.5">5.3.3</a></li>
    4591                         <li><em>Section 4.1.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.8">7.3.1</a>, <a href="#rfc.xref.Part6.11">7.3.4</a>, <a href="#rfc.xref.Part6.12">7.4.1</a>, <a href="#rfc.xref.Part6.13">7.4.2</a>, <a href="#rfc.xref.Part6.14">7.5.9</a></li>
    4592                         <li><em>Section 4.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.16">8.2.1</a></li>
     4591                        <li><em>Section 4.1.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.8">7.3.1</a>, <a href="#rfc.xref.Part6.10">7.4.1</a>, <a href="#rfc.xref.Part6.11">7.4.2</a>, <a href="#rfc.xref.Part6.12">7.5.9</a></li>
     4592                        <li><em>Section 4.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.14">8.2.1</a></li>
    45934593                        <li><em>Section 5</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.4">5.3.2</a></li>
    45944594                        <li><em>Section 6</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.6">5.3.4</a>, <a href="#rfc.xref.Part6.7">5.3.5</a></li>
    4595                         <li><em>Section 7.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.15">8.1</a></li>
    4596                         <li><em>Section 7.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.9">7.3.4</a></li>
     4595                        <li><em>Section 7.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.13">8.1</a></li>
    45974596                        <li><em>Section 7.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.1">3.1</a></li>
    4598                         <li><em>Section 7.5</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.10">7.3.4</a></li>
     4597                        <li><em>Section 7.5</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.9">7.3.4</a></li>
    45994598                     </ul>
    46004599                  </li>
Note: See TracChangeset for help on using the changeset viewer.