Changeset 363 for draft-ietf-httpbis/latest/p5-range.html
- Timestamp:
- 13/11/08 18:01:19 (14 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p5-range.html
r359 r363 589 589 <a href="#notation" class="smpl">SP</a> = <SP, defined in <a href="#Part1" id="rfc.xref.Part1.4"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#basic.rules" title="Basic Rules">Section 2.2</a>> 590 590 </pre><div id="rfc.figure.u.2"></div><pre class="inline"> <a href="#notation" class="smpl">token</a> = <token, defined in <a href="#Part1" id="rfc.xref.Part1.5"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#basic.rules" title="Basic Rules">Section 2.2</a>> 591 <a href="#notation" class="smpl">BWS</a> = <BWS, defined in <a href="#Part1" id="rfc.xref.Part1.6"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#basic.rules" title="Basic Rules">Section 2.2</a>> 592 <a href="#notation" class="smpl">OWS</a> = <OWS, defined in <a href="#Part1" id="rfc.xref.Part1.7"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#basic.rules" title="Basic Rules">Section 2.2</a>> 593 <a href="#notation" class="smpl">RWS</a> = <RWS, 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#basic.rules" title="Basic Rules">Section 2.2</a>> 591 594 </pre><div id="abnf.dependencies"> 592 595 <p id="rfc.section.2.p.4"> The ABNF rules below are defined in other parts:</p> 593 596 </div> 594 <div id="rfc.figure.u.3"></div><pre class="inline"> <a href="#abnf.dependencies" class="smpl">HTTP-date</a> = <HTTP-date, defined in <a href="#Part1" id="rfc.xref.Part1. 6"><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>>597 <div id="rfc.figure.u.3"></div><pre class="inline"> <a href="#abnf.dependencies" class="smpl">HTTP-date</a> = <HTTP-date, 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#full.date" title="Full Date">Section 3.3.1</a>> 595 598 </pre><div id="rfc.figure.u.4"></div><pre class="inline"> <a href="#abnf.dependencies" class="smpl">entity-tag</a> = <entity-tag, defined in <a href="#Part4" id="rfc.xref.Part4.1"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>, <a href="p4-conditional.html#entity.tags" title="Entity Tags">Section 3</a>> 596 599 </pre><h1 id="rfc.section.3"><a href="#rfc.section.3">3.</a> <a id="range.units" href="#range.units">Range Units</a></h1> … … 662 665 <div id="rfc.iref.h.1"></div> 663 666 <h2 id="rfc.section.6.1"><a href="#rfc.section.6.1">6.1</a> <a id="header.accept-ranges" href="#header.accept-ranges">Accept-Ranges</a></h2> 664 <p id="rfc.section.6.1.p.1">The Accept-Ranges response-header field allows the server to indicate its acceptance of range requests for a resource:</p> 665 <div id="rfc.figure.u.6"></div><pre class="inline"><span id="rfc.iref.g.4"></span><span id="rfc.iref.g.5"></span> <a href="#header.accept-ranges" class="smpl">Accept-Ranges</a> = "Accept-Ranges" ":" <a href="#header.accept-ranges" class="smpl">acceptable-ranges</a> 667 <p id="rfc.section.6.1.p.1">The response-header "Accept-Ranges" field allows the server to indicate its acceptance of range requests for a resource:</p> 668 <div id="rfc.figure.u.6"></div><pre class="inline"><span id="rfc.iref.g.4"></span><span id="rfc.iref.g.5"></span><span id="rfc.iref.g.6"></span> <a href="#header.accept-ranges" class="smpl">Accept-Ranges</a> = "Accept-Ranges" <a href="#notation" class="smpl">BWS</a> ":" <a href="#notation" class="smpl">OWS</a> <a href="#header.accept-ranges" class="smpl">Accept-Ranges-v</a> 669 <a href="#header.accept-ranges" class="smpl">Accept-Ranges-v</a> = <a href="#header.accept-ranges" class="smpl">acceptable-ranges</a> 666 670 <a href="#header.accept-ranges" class="smpl">acceptable-ranges</a> = 1#<a href="#range.units" class="smpl">range-unit</a> / "none" 667 671 </pre><p id="rfc.section.6.1.p.3">Origin servers that accept byte-range requests <em class="bcp14">MAY</em> send 668 672 </p> 669 <div id="rfc.figure.u.7"></div><pre class="text"> 673 <div id="rfc.figure.u.7"></div><pre class="text"> Accept-Ranges: bytes 670 674 </pre><p id="rfc.section.6.1.p.5">but are not required to do so. Clients <em class="bcp14">MAY</em> generate byte-range requests without having received this header for the resource involved. Range units are defined in <a href="#range.units" title="Range Units">Section 3</a>. 671 675 </p> 672 676 <p id="rfc.section.6.1.p.6">Servers that do not accept any kind of range request for a resource <em class="bcp14">MAY</em> send 673 677 </p> 674 <div id="rfc.figure.u.8"></div><pre class="text"> 678 <div id="rfc.figure.u.8"></div><pre class="text"> Accept-Ranges: none 675 679 </pre><p id="rfc.section.6.1.p.8">to advise the client not to attempt a range request.</p> 676 680 <div id="rfc.iref.c.1"></div> 677 681 <div id="rfc.iref.h.2"></div> 678 682 <h2 id="rfc.section.6.2"><a href="#rfc.section.6.2">6.2</a> <a id="header.content-range" href="#header.content-range">Content-Range</a></h2> 679 <p id="rfc.section.6.2.p.1">The Content-Range entity-header is sent with a partial entity-body to specify where in the full entity-body the partial body 680 should be applied. Range units are defined in <a href="#range.units" title="Range Units">Section 3</a>. 681 </p> 682 <div id="rfc.figure.u.9"></div><pre class="inline"><span id="rfc.iref.g.6"></span><span id="rfc.iref.g.7"></span><span id="rfc.iref.g.8"></span><span id="rfc.iref.g.9"></span><span id="rfc.iref.g.10"></span> <a href="#header.content-range" class="smpl">Content-Range</a> = "Content-Range" ":" <a href="#header.content-range" class="smpl">content-range-spec</a> 683 <p id="rfc.section.6.2.p.1">The entity-header "Content-Range" is sent with a partial entity-body to specify where in the full entity-body the partial 684 body should be applied. Range units are defined in <a href="#range.units" title="Range Units">Section 3</a>. 685 </p> 686 <div id="rfc.figure.u.9"></div><pre class="inline"><span id="rfc.iref.g.7"></span><span id="rfc.iref.g.8"></span><span id="rfc.iref.g.9"></span><span id="rfc.iref.g.10"></span><span id="rfc.iref.g.11"></span><span id="rfc.iref.g.12"></span> <a href="#header.content-range" class="smpl">Content-Range</a> = "Content-Range" <a href="#notation" class="smpl">BWS</a> ":" <a href="#notation" class="smpl">OWS</a> <a href="#header.content-range" class="smpl">Content-Range-v</a> 687 <a href="#header.content-range" class="smpl">Content-Range-v</a> = <a href="#header.content-range" class="smpl">content-range-spec</a> 683 688 684 689 <a href="#header.content-range" class="smpl">content-range-spec</a> = <a href="#header.content-range" class="smpl">byte-content-range-spec</a> … … 721 726 a Content-Length header showing the number of bytes actually transferred. For example, 722 727 </p> 723 <div id="rfc.figure.u.14"></div><pre class="text"> 724 725 726 727 728 728 <div id="rfc.figure.u.14"></div><pre class="text"> HTTP/1.1 206 Partial Content 729 Date: Wed, 15 Nov 1995 06:25:24 GMT 730 Last-Modified: Wed, 15 Nov 1995 04:58:08 GMT 731 Content-Range: bytes 21010-47021/47022 732 Content-Length: 26012 733 Content-Type: image/gif 729 734 </pre><p id="rfc.section.6.2.p.10">When an HTTP message includes the content of multiple ranges (for example, a response to a request for multiple non-overlapping 730 735 ranges), these are transmitted as a multipart message. The multipart media type used for this purpose is "multipart/byteranges" … … 755 760 to obtain the entire current entity-body. 756 761 </p> 757 <p id="rfc.section.6.3.p.2">The If-Range header allows a client to "short-circuit" the second request. Informally, its meaning is `if the entity is unchanged, 758 send me the part(s) that I am missing; otherwise, send me the entire new entity'. 759 </p> 760 <div id="rfc.figure.u.15"></div><pre class="inline"><span id="rfc.iref.g.11"></span> <a href="#header.if-range" class="smpl">If-Range</a> = "If-Range" ":" ( <a href="#abnf.dependencies" class="smpl">entity-tag</a> / <a href="#abnf.dependencies" class="smpl">HTTP-date</a> ) 762 <p id="rfc.section.6.3.p.2">The request header "If-Range" allows a client to "short-circuit" the second request. Informally, its meaning is `if the entity 763 is unchanged, send me the part(s) that I am missing; otherwise, send me the entire new entity'. 764 </p> 765 <div id="rfc.figure.u.15"></div><pre class="inline"><span id="rfc.iref.g.13"></span><span id="rfc.iref.g.14"></span> <a href="#header.if-range" class="smpl">If-Range</a> = "If-Range" <a href="#notation" class="smpl">BWS</a> ":" <a href="#notation" class="smpl">OWS</a> <a href="#header.if-range" class="smpl">If-Range-v</a> 766 <a href="#header.if-range" class="smpl">If-Range-v</a> = <a href="#abnf.dependencies" class="smpl">entity-tag</a> / <a href="#abnf.dependencies" class="smpl">HTTP-date</a> 761 767 </pre><p id="rfc.section.6.3.p.4">If the client has no entity tag for an entity, but does have a Last-Modified date, it <em class="bcp14">MAY</em> use that date in an If-Range header. (The server can distinguish between a valid HTTP-date and any form of entity-tag by examining 762 768 no more than two characters.) The If-Range header <em class="bcp14">SHOULD</em> only be used together with a Range header, and <em class="bcp14">MUST</em> be ignored if the request does not include a Range header, or if the server does not support the sub-range operation. … … 777 783 </p> 778 784 </div> 779 <div id="rfc.figure.u.16"></div><pre class="inline"><span id="rfc.iref.g.1 2"></span><span id="rfc.iref.g.13"></span><span id="rfc.iref.g.14"></span><span id="rfc.iref.g.15"></span><span id="rfc.iref.g.16"></span><span id="rfc.iref.g.17"></span> <a href="#rule.ranges-specifier" class="smpl">ranges-specifier</a> = <a href="#rule.ranges-specifier" class="smpl">byte-ranges-specifier</a>785 <div id="rfc.figure.u.16"></div><pre class="inline"><span id="rfc.iref.g.15"></span><span id="rfc.iref.g.16"></span><span id="rfc.iref.g.17"></span><span id="rfc.iref.g.18"></span><span id="rfc.iref.g.19"></span><span id="rfc.iref.g.20"></span> <a href="#rule.ranges-specifier" class="smpl">ranges-specifier</a> = <a href="#rule.ranges-specifier" class="smpl">byte-ranges-specifier</a> 780 786 <a href="#rule.ranges-specifier" class="smpl">byte-ranges-specifier</a> = <a href="#range.units" class="smpl">bytes-unit</a> "=" <a href="#rule.ranges-specifier" class="smpl">byte-range-set</a> 781 787 <a href="#rule.ranges-specifier" class="smpl">byte-range-set</a> = 1#( <a href="#rule.ranges-specifier" class="smpl">byte-range-spec</a> / <a href="#rule.ranges-specifier" class="smpl">suffix-byte-range-spec</a> ) … … 794 800 </p> 795 801 <p id="rfc.section.6.4.1.p.8">By its choice of last-byte-pos, a client can limit the number of bytes retrieved without knowing the size of the entity.</p> 796 <div id="rfc.figure.u.17"></div><pre class="inline"><span id="rfc.iref.g. 18"></span><span id="rfc.iref.g.19"></span> <a href="#rule.ranges-specifier" class="smpl">suffix-byte-range-spec</a> = "-" <a href="#rule.ranges-specifier" class="smpl">suffix-length</a>802 <div id="rfc.figure.u.17"></div><pre class="inline"><span id="rfc.iref.g.21"></span><span id="rfc.iref.g.22"></span> <a href="#rule.ranges-specifier" class="smpl">suffix-byte-range-spec</a> = "-" <a href="#rule.ranges-specifier" class="smpl">suffix-length</a> 797 803 <a href="#rule.ranges-specifier" class="smpl">suffix-length</a> = 1*<a href="#notation" class="smpl">DIGIT</a> 798 804 </pre><p id="rfc.section.6.4.1.p.10">A suffix-byte-range-spec is used to specify the suffix of the entity-body, of a length given by the suffix-length value. (That … … 818 824 to the entity returned as the result of the request: 819 825 </p> 820 <div id="rfc.figure.u.18"></div><pre class="inline"><span id="rfc.iref.g.20"></span> <a href="#range.retrieval.requests" class="smpl">Range</a> = "Range" ":" <a href="#rule.ranges-specifier" class="smpl">ranges-specifier</a> 826 <div id="rfc.figure.u.18"></div><pre class="inline"><span id="rfc.iref.g.23"></span><span id="rfc.iref.g.24"></span> <a href="#range.retrieval.requests" class="smpl">Range</a> = "Range" <a href="#notation" class="smpl">BWS</a> ":" <a href="#notation" class="smpl">OWS</a> <a href="#range.retrieval.requests" class="smpl">Range-v</a> 827 <a href="#range.retrieval.requests" class="smpl">Range-v</a> = <a href="#rule.ranges-specifier" class="smpl">ranges-specifier</a> 821 828 </pre><p id="rfc.section.6.4.2.p.3">A server <em class="bcp14">MAY</em> ignore the Range header. However, HTTP/1.1 origin servers and intermediate caches ought to support byte ranges when possible, 822 829 since Range supports efficient recovery from partially failed transfers, and supports efficient partial retrieval of large … … 887 894 <p id="rfc.section.7.1.p.2">The change controller is: "IETF (iesg@ietf.org) - Internet Engineering Task Force".</p> 888 895 <h1 id="rfc.section.8"><a href="#rfc.section.8">8.</a> <a id="security.considerations" href="#security.considerations">Security Considerations</a></h1> 889 <p id="rfc.section.8.p.1">No additional security considerations have been identified beyond those applicable to HTTP in general <a href="#Part1" id="rfc.xref.Part1. 7"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>.896 <p id="rfc.section.8.p.1">No additional security considerations have been identified beyond those applicable to HTTP in general <a href="#Part1" id="rfc.xref.Part1.10"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>. 890 897 </p> 891 898 <h1 id="rfc.section.9"><a href="#rfc.section.9">9.</a> <a id="ack" href="#ack">Acknowledgments</a></h1> … … 1043 1050 <p id="rfc.section.B.1.p.1">Transfer-coding and message lengths all interact in ways that required fixing exactly when chunked encoding is used (to allow 1044 1051 for transfer encoding that may not be self delimiting); it was important to straighten out exactly how message lengths are 1045 computed. (<a href="#header.content-range" id="rfc.xref.header.content-range.5" title="Content-Range">Section 6.2</a>, see also <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="#Part3" id="rfc.xref.Part3.1"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a> and <a href="#Part6" id="rfc.xref.Part6.1"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>)1052 computed. (<a href="#header.content-range" id="rfc.xref.header.content-range.5" title="Content-Range">Section 6.2</a>, see also <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="#Part3" id="rfc.xref.Part3.1"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a> and <a href="#Part6" id="rfc.xref.Part6.1"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>) 1046 1053 </p> 1047 1054 <p id="rfc.section.B.1.p.2">There are situations where a server (especially a proxy) does not know the full length of a response but is capable of serving … … 1106 1113 <ul> 1107 1114 <li>Use "/" instead of "|" for alternatives.</li> 1115 <li>Introduce new ABNF rules for "bad" whitespace ("BWS"), optional whitespace ("OWS") and required whitespace ("RWS").</li> 1116 <li>Rewrite ABNFs to spell out whitespace rules, factor out header value format definitions.</li> 1108 1117 </ul> 1109 1118 <h1><a id="rfc.copyright" href="#rfc.copyright">Full Copyright Statement</a></h1> … … 1156 1165 <ul class="ind"> 1157 1166 <li class="indline1"><tt>Accept-Ranges</tt> <a class="iref" href="#rfc.iref.g.4"><b>6.1</b></a></li> 1158 <li class="indline1"><tt>acceptable-ranges</tt> <a class="iref" href="#rfc.iref.g.5"><b>6.1</b></a></li> 1159 <li class="indline1"><tt>byte-content-range-spec</tt> <a class="iref" href="#rfc.iref.g.8"><b>6.2</b></a></li> 1160 <li class="indline1"><tt>byte-range-resp-spec</tt> <a class="iref" href="#rfc.iref.g.9"><b>6.2</b></a></li> 1161 <li class="indline1"><tt>byte-range-set</tt> <a class="iref" href="#rfc.iref.g.14"><b>6.4.1</b></a></li> 1162 <li class="indline1"><tt>byte-range-spec</tt> <a class="iref" href="#rfc.iref.g.15"><b>6.4.1</b></a></li> 1163 <li class="indline1"><tt>byte-ranges-specifier</tt> <a class="iref" href="#rfc.iref.g.13"><b>6.4.1</b></a></li> 1167 <li class="indline1"><tt>Accept-Ranges-v</tt> <a class="iref" href="#rfc.iref.g.5"><b>6.1</b></a></li> 1168 <li class="indline1"><tt>acceptable-ranges</tt> <a class="iref" href="#rfc.iref.g.6"><b>6.1</b></a></li> 1169 <li class="indline1"><tt>byte-content-range-spec</tt> <a class="iref" href="#rfc.iref.g.10"><b>6.2</b></a></li> 1170 <li class="indline1"><tt>byte-range-resp-spec</tt> <a class="iref" href="#rfc.iref.g.11"><b>6.2</b></a></li> 1171 <li class="indline1"><tt>byte-range-set</tt> <a class="iref" href="#rfc.iref.g.17"><b>6.4.1</b></a></li> 1172 <li class="indline1"><tt>byte-range-spec</tt> <a class="iref" href="#rfc.iref.g.18"><b>6.4.1</b></a></li> 1173 <li class="indline1"><tt>byte-ranges-specifier</tt> <a class="iref" href="#rfc.iref.g.16"><b>6.4.1</b></a></li> 1164 1174 <li class="indline1"><tt>bytes-unit</tt> <a class="iref" href="#rfc.iref.g.2"><b>3</b></a></li> 1165 <li class="indline1"><tt>Content-Range</tt> <a class="iref" href="#rfc.iref.g.6"><b>6.2</b></a></li> 1166 <li class="indline1"><tt>content-range-spec</tt> <a class="iref" href="#rfc.iref.g.7"><b>6.2</b></a></li> 1167 <li class="indline1"><tt>first-byte-pos</tt> <a class="iref" href="#rfc.iref.g.16"><b>6.4.1</b></a></li> 1168 <li class="indline1"><tt>If-Range</tt> <a class="iref" href="#rfc.iref.g.11"><b>6.3</b></a></li> 1169 <li class="indline1"><tt>instance-length</tt> <a class="iref" href="#rfc.iref.g.10"><b>6.2</b></a></li> 1170 <li class="indline1"><tt>last-byte-pos</tt> <a class="iref" href="#rfc.iref.g.17"><b>6.4.1</b></a></li> 1175 <li class="indline1"><tt>Content-Range</tt> <a class="iref" href="#rfc.iref.g.7"><b>6.2</b></a></li> 1176 <li class="indline1"><tt>content-range-spec</tt> <a class="iref" href="#rfc.iref.g.9"><b>6.2</b></a></li> 1177 <li class="indline1"><tt>Content-Range-v</tt> <a class="iref" href="#rfc.iref.g.8"><b>6.2</b></a></li> 1178 <li class="indline1"><tt>first-byte-pos</tt> <a class="iref" href="#rfc.iref.g.19"><b>6.4.1</b></a></li> 1179 <li class="indline1"><tt>If-Range</tt> <a class="iref" href="#rfc.iref.g.13"><b>6.3</b></a></li> 1180 <li class="indline1"><tt>If-Range-v</tt> <a class="iref" href="#rfc.iref.g.14"><b>6.3</b></a></li> 1181 <li class="indline1"><tt>instance-length</tt> <a class="iref" href="#rfc.iref.g.12"><b>6.2</b></a></li> 1182 <li class="indline1"><tt>last-byte-pos</tt> <a class="iref" href="#rfc.iref.g.20"><b>6.4.1</b></a></li> 1171 1183 <li class="indline1"><tt>other-range-unit</tt> <a class="iref" href="#rfc.iref.g.3"><b>3</b></a></li> 1172 <li class="indline1"><tt>Range</tt> <a class="iref" href="#rfc.iref.g.2 0"><b>6.4.2</b></a></li>1184 <li class="indline1"><tt>Range</tt> <a class="iref" href="#rfc.iref.g.23"><b>6.4.2</b></a></li> 1173 1185 <li class="indline1"><tt>range-unit</tt> <a class="iref" href="#rfc.iref.g.1"><b>3</b></a></li> 1174 <li class="indline1"><tt>ranges-specifier</tt> <a class="iref" href="#rfc.iref.g.12"><b>6.4.1</b></a></li> 1175 <li class="indline1"><tt>suffix-byte-range-spec</tt> <a class="iref" href="#rfc.iref.g.18"><b>6.4.1</b></a></li> 1176 <li class="indline1"><tt>suffix-length</tt> <a class="iref" href="#rfc.iref.g.19"><b>6.4.1</b></a></li> 1186 <li class="indline1"><tt>Range-v</tt> <a class="iref" href="#rfc.iref.g.24"><b>6.4.2</b></a></li> 1187 <li class="indline1"><tt>ranges-specifier</tt> <a class="iref" href="#rfc.iref.g.15"><b>6.4.1</b></a></li> 1188 <li class="indline1"><tt>suffix-byte-range-spec</tt> <a class="iref" href="#rfc.iref.g.21"><b>6.4.1</b></a></li> 1189 <li class="indline1"><tt>suffix-length</tt> <a class="iref" href="#rfc.iref.g.22"><b>6.4.1</b></a></li> 1177 1190 </ul> 1178 1191 </li> … … 1206 1219 </li> 1207 1220 <li class="indline0"><a id="rfc.index.P" href="#rfc.index.P"><b>P</b></a><ul class="ind"> 1208 <li class="indline1"><em>Part1</em> <a class="iref" href="#rfc.xref.Part1.1">2</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"> 8</a>, <a class="iref" href="#Part1"><b>10.1</b></a>, <a class="iref" href="#rfc.xref.Part1.8">B.1</a><ul class="ind">1221 <li class="indline1"><em>Part1</em> <a class="iref" href="#rfc.xref.Part1.1">2</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">8</a>, <a class="iref" href="#Part1"><b>10.1</b></a>, <a class="iref" href="#rfc.xref.Part1.11">B.1</a><ul class="ind"> 1209 1222 <li class="indline1"><em>Section 2.1</em> <a class="iref" href="#rfc.xref.Part1.1">2</a></li> 1210 <li class="indline1"><em>Section 2.2</em> <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> </li>1211 <li class="indline1"><em>Section 3.3.1</em> <a class="iref" href="#rfc.xref.Part1. 6">2</a></li>1223 <li class="indline1"><em>Section 2.2</em> <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></li> 1224 <li class="indline1"><em>Section 3.3.1</em> <a class="iref" href="#rfc.xref.Part1.9">2</a></li> 1212 1225 </ul> 1213 1226 </li>
Note: See TracChangeset
for help on using the changeset viewer.