Ignore:
Timestamp:
Nov 18, 2008, 8:53:23 AM (11 years ago)
Author:
julian.reschke@…
Message:

Resolve #52: Sort Terminology entries (closes #52)

File:
1 edited

Legend:

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

    r404 r413  
    476476         <tr>
    477477            <td class="header left"></td>
    478             <td class="header right">November 15, 2008</td>
     478            <td class="header right">November 18, 2008</td>
    479479         </tr>
    480480      </table>
     
    24872487      <h1 id="rfc.section.C"><a href="#rfc.section.C">C.</a>&nbsp;<a id="terminology" href="#terminology">Terminology</a></h1>
    24882488      <p id="rfc.section.C.p.1">This specification uses a number of terms to refer to the roles played by participants in, and objects of, the HTTP communication.</p>
    2489       <p id="rfc.section.C.p.2"> <span id="rfc.iref.c.3"></span>  <dfn>connection</dfn> 
     2489      <p id="rfc.section.C.p.2"> <span id="rfc.iref.c.3"></span>  <dfn>cache</dfn> 
     2490      </p>
     2491      <dl class="empty">
     2492         <dd>A program's local store of response messages and the subsystem that controls its message storage, retrieval, and deletion.
     2493            A cache stores cacheable responses in order to reduce the response time and network bandwidth consumption on future, equivalent
     2494            requests. Any client or server may include a cache, though a cache cannot be used by a server that is acting as a tunnel.
     2495         </dd>
     2496      </dl>
     2497      <p id="rfc.section.C.p.3"> <span id="rfc.iref.c.4"></span>  <dfn>cacheable</dfn> 
     2498      </p>
     2499      <dl class="empty">
     2500         <dd>A response is cacheable if a cache is allowed to store a copy of the response message for use in answering subsequent requests.
     2501            The rules for determining the cacheability of HTTP responses are defined in <a href="p6-cache.html#caching" title="Introduction">Section 1</a> of <a href="#Part6" id="rfc.xref.Part6.9"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>. Even if a resource is cacheable, there may be additional constraints on whether a cache can use the cached copy for a particular
     2502            request.
     2503         </dd>
     2504      </dl>
     2505      <p id="rfc.section.C.p.4"> <span id="rfc.iref.c.5"></span>  <dfn>client</dfn> 
     2506      </p>
     2507      <dl class="empty">
     2508         <dd>A program that establishes connections for the purpose of sending requests.</dd>
     2509      </dl>
     2510      <p id="rfc.section.C.p.5"> <span id="rfc.iref.c.6"></span>  <dfn>connection</dfn> 
    24902511      </p>
    24912512      <dl class="empty">
    24922513         <dd>A transport layer virtual circuit established between two programs for the purpose of communication.</dd>
    24932514      </dl>
    2494       <p id="rfc.section.C.p.3"> <span id="rfc.iref.m.4"></span>  <dfn>message</dfn> 
     2515      <p id="rfc.section.C.p.6"> <span id="rfc.iref.c.7"></span>  <dfn>content negotiation</dfn> 
     2516      </p>
     2517      <dl class="empty">
     2518         <dd>The mechanism for selecting the appropriate representation when servicing a request, as described in <a href="p3-payload.html#content.negotiation" title="Content Negotiation">Section 5</a> of <a href="#Part3" id="rfc.xref.Part3.13"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>. The representation of entities in any response can be negotiated (including error responses).
     2519         </dd>
     2520      </dl>
     2521      <p id="rfc.section.C.p.7"> <span id="rfc.iref.e.1"></span>  <dfn>entity</dfn> 
     2522      </p>
     2523      <dl class="empty">
     2524         <dd>The information transferred as the payload of a request or response. An entity consists of metainformation in the form of
     2525            entity-header fields and content in the form of an entity-body, as described in <a href="p3-payload.html#entity" title="Entity">Section 4</a> of <a href="#Part3" id="rfc.xref.Part3.14"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>.
     2526         </dd>
     2527      </dl>
     2528      <p id="rfc.section.C.p.8"> <span id="rfc.iref.g.107"></span>  <dfn>gateway</dfn> 
     2529      </p>
     2530      <dl class="empty">
     2531         <dd>A server which acts as an intermediary for some other server. Unlike a proxy, a gateway receives requests as if it were the
     2532            origin server for the requested resource; the requesting client may not be aware that it is communicating with a gateway.
     2533         </dd>
     2534      </dl>
     2535      <p id="rfc.section.C.p.9"> <span id="rfc.iref.i.1"></span>  <span id="rfc.iref.o.1"></span>  <dfn>inbound</dfn>/<dfn>outbound</dfn> 
     2536      </p>
     2537      <dl class="empty">
     2538         <dd>Inbound and outbound refer to the request and response paths for messages: "inbound" means "traveling toward the origin server",
     2539            and "outbound" means "traveling toward the user agent"
     2540         </dd>
     2541      </dl>
     2542      <p id="rfc.section.C.p.10"> <span id="rfc.iref.m.4"></span>  <dfn>message</dfn> 
    24952543      </p>
    24962544      <dl class="empty">
     
    24982546         </dd>
    24992547      </dl>
    2500       <p id="rfc.section.C.p.4"> <span id="rfc.iref.r.1"></span>  <dfn>request</dfn> 
    2501       </p>
    2502       <dl class="empty">
    2503          <dd>An HTTP request message, as defined in <a href="#request" title="Request">Section&nbsp;5</a>.
    2504          </dd>
    2505       </dl>
    2506       <p id="rfc.section.C.p.5"> <span id="rfc.iref.r.2"></span>  <dfn>response</dfn> 
    2507       </p>
    2508       <dl class="empty">
    2509          <dd>An HTTP response message, as defined in <a href="#response" title="Response">Section&nbsp;6</a>.
    2510          </dd>
    2511       </dl>
    2512       <p id="rfc.section.C.p.6"> <span id="rfc.iref.r.3"></span>  <dfn>resource</dfn> 
    2513       </p>
    2514       <dl class="empty">
    2515          <dd>A network data object or service that can be identified by a URI, as defined in <a href="#uri" title="Uniform Resource Identifiers">Section&nbsp;2.1</a>. Resources may be available in multiple representations (e.g. multiple languages, data formats, size, and resolutions) or
    2516             vary in other ways.
    2517          </dd>
    2518       </dl>
    2519       <p id="rfc.section.C.p.7"> <span id="rfc.iref.e.1"></span>  <dfn>entity</dfn> 
    2520       </p>
    2521       <dl class="empty">
    2522          <dd>The information transferred as the payload of a request or response. An entity consists of metainformation in the form of
    2523             entity-header fields and content in the form of an entity-body, as described in <a href="p3-payload.html#entity" title="Entity">Section 4</a> of <a href="#Part3" id="rfc.xref.Part3.13"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>.
    2524          </dd>
    2525       </dl>
    2526       <p id="rfc.section.C.p.8"> <span id="rfc.iref.r.4"></span>  <dfn>representation</dfn> 
    2527       </p>
    2528       <dl class="empty">
    2529          <dd>An entity included with a response that is subject to content negotiation, as described in <a href="p3-payload.html#content.negotiation" title="Content Negotiation">Section 5</a> of <a href="#Part3" id="rfc.xref.Part3.14"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>. There may exist multiple representations associated with a particular response status.
    2530          </dd>
    2531       </dl>
    2532       <p id="rfc.section.C.p.9"> <span id="rfc.iref.c.4"></span>  <dfn>content negotiation</dfn> 
    2533       </p>
    2534       <dl class="empty">
    2535          <dd>The mechanism for selecting the appropriate representation when servicing a request, as described in <a href="p3-payload.html#content.negotiation" title="Content Negotiation">Section 5</a> of <a href="#Part3" id="rfc.xref.Part3.15"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>. The representation of entities in any response can be negotiated (including error responses).
    2536          </dd>
    2537       </dl>
    2538       <p id="rfc.section.C.p.10"> <span id="rfc.iref.v.2"></span>  <dfn>variant</dfn> 
    2539       </p>
    2540       <dl class="empty">
    2541          <dd>A resource may have one, or more than one, representation(s) associated with it at any given instant. Each of these representations
    2542             is termed a `variant'. Use of the term `variant' does not necessarily imply that the resource is subject to content negotiation.
    2543          </dd>
    2544       </dl>
    2545       <p id="rfc.section.C.p.11"> <span id="rfc.iref.c.5"></span>  <dfn>client</dfn> 
    2546       </p>
    2547       <dl class="empty">
    2548          <dd>A program that establishes connections for the purpose of sending requests.</dd>
    2549       </dl>
    2550       <p id="rfc.section.C.p.12"> <span id="rfc.iref.u.4"></span>  <dfn>user agent</dfn> 
    2551       </p>
    2552       <dl class="empty">
    2553          <dd>The client which initiates a request. These are often browsers, editors, spiders (web-traversing robots), or other end user
    2554             tools.
    2555          </dd>
    2556       </dl>
    2557       <p id="rfc.section.C.p.13"> <span id="rfc.iref.s.1"></span>  <dfn>server</dfn> 
    2558       </p>
    2559       <dl class="empty">
    2560          <dd>An application program that accepts connections in order to service requests by sending back responses. Any given program
    2561             may be capable of being both a client and a server; our use of these terms refers only to the role being performed by the
    2562             program for a particular connection, rather than to the program's capabilities in general. Likewise, any server may act as
    2563             an origin server, proxy, gateway, or tunnel, switching behavior based on the nature of each request.
    2564          </dd>
    2565       </dl>
    2566       <p id="rfc.section.C.p.14"> <span id="rfc.iref.o.1"></span>  <dfn>origin server</dfn> 
     2548      <p id="rfc.section.C.p.11"> <span id="rfc.iref.o.2"></span>  <dfn>origin server</dfn> 
    25672549      </p>
    25682550      <dl class="empty">
    25692551         <dd>The server on which a given resource resides or is to be created.</dd>
    25702552      </dl>
    2571       <p id="rfc.section.C.p.15"> <span id="rfc.iref.p.1"></span>  <dfn>proxy</dfn> 
     2553      <p id="rfc.section.C.p.12"> <span id="rfc.iref.p.1"></span>  <dfn>proxy</dfn> 
    25722554      </p>
    25732555      <dl class="empty">
     
    25802562         </dd>
    25812563      </dl>
    2582       <p id="rfc.section.C.p.16"> <span id="rfc.iref.g.107"></span>  <dfn>gateway</dfn> 
     2564      <p id="rfc.section.C.p.13"> <span id="rfc.iref.r.1"></span>  <dfn>request</dfn> 
    25832565      </p>
    25842566      <dl class="empty">
    2585          <dd>A server which acts as an intermediary for some other server. Unlike a proxy, a gateway receives requests as if it were the
    2586             origin server for the requested resource; the requesting client may not be aware that it is communicating with a gateway.
     2567         <dd>An HTTP request message, as defined in <a href="#request" title="Request">Section&nbsp;5</a>.
    25872568         </dd>
    25882569      </dl>
    2589       <p id="rfc.section.C.p.17"> <span id="rfc.iref.t.4"></span>  <dfn>tunnel</dfn> 
     2570      <p id="rfc.section.C.p.14"> <span id="rfc.iref.r.2"></span>  <dfn>resource</dfn> 
     2571      </p>
     2572      <dl class="empty">
     2573         <dd>A network data object or service that can be identified by a URI, as defined in <a href="#uri" title="Uniform Resource Identifiers">Section&nbsp;2.1</a>. Resources may be available in multiple representations (e.g. multiple languages, data formats, size, and resolutions) or
     2574            vary in other ways.
     2575         </dd>
     2576      </dl>
     2577      <p id="rfc.section.C.p.15"> <span id="rfc.iref.r.3"></span>  <dfn>response</dfn> 
     2578      </p>
     2579      <dl class="empty">
     2580         <dd>An HTTP response message, as defined in <a href="#response" title="Response">Section&nbsp;6</a>.
     2581         </dd>
     2582      </dl>
     2583      <p id="rfc.section.C.p.16"> <span id="rfc.iref.r.4"></span>  <dfn>representation</dfn> 
     2584      </p>
     2585      <dl class="empty">
     2586         <dd>An entity included with a response that is subject to content negotiation, as described in <a href="p3-payload.html#content.negotiation" title="Content Negotiation">Section 5</a> of <a href="#Part3" id="rfc.xref.Part3.15"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>. There may exist multiple representations associated with a particular response status.
     2587         </dd>
     2588      </dl>
     2589      <p id="rfc.section.C.p.17"> <span id="rfc.iref.s.1"></span>  <dfn>server</dfn> 
     2590      </p>
     2591      <dl class="empty">
     2592         <dd>An application program that accepts connections in order to service requests by sending back responses. Any given program
     2593            may be capable of being both a client and a server; our use of these terms refers only to the role being performed by the
     2594            program for a particular connection, rather than to the program's capabilities in general. Likewise, any server may act as
     2595            an origin server, proxy, gateway, or tunnel, switching behavior based on the nature of each request.
     2596         </dd>
     2597      </dl>
     2598      <p id="rfc.section.C.p.18"> <span id="rfc.iref.t.4"></span>  <dfn>tunnel</dfn> 
    25902599      </p>
    25912600      <dl class="empty">
     
    25952604         </dd>
    25962605      </dl>
    2597       <p id="rfc.section.C.p.18"> <span id="rfc.iref.c.6"></span>  <dfn>cache</dfn> 
    2598       </p>
    2599       <dl class="empty">
    2600          <dd>A program's local store of response messages and the subsystem that controls its message storage, retrieval, and deletion.
    2601             A cache stores cacheable responses in order to reduce the response time and network bandwidth consumption on future, equivalent
    2602             requests. Any client or server may include a cache, though a cache cannot be used by a server that is acting as a tunnel.
    2603          </dd>
    2604       </dl>
    2605       <p id="rfc.section.C.p.19"> <span id="rfc.iref.c.7"></span>  <dfn>cacheable</dfn> 
    2606       </p>
    2607       <dl class="empty">
    2608          <dd>A response is cacheable if a cache is allowed to store a copy of the response message for use in answering subsequent requests.
    2609             The rules for determining the cacheability of HTTP responses are defined in <a href="p6-cache.html#caching" title="Introduction">Section 1</a> of <a href="#Part6" id="rfc.xref.Part6.9"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>. Even if a resource is cacheable, there may be additional constraints on whether a cache can use the cached copy for a particular
    2610             request.
    2611          </dd>
    2612       </dl>
    2613       <p id="rfc.section.C.p.20"> <span id="rfc.iref.u.5"></span>  <span id="rfc.iref.d.2"></span>  <dfn>upstream</dfn>/<dfn>downstream</dfn> 
     2606      <p id="rfc.section.C.p.19"> <span id="rfc.iref.u.4"></span>  <span id="rfc.iref.d.2"></span>  <dfn>upstream</dfn>/<dfn>downstream</dfn> 
    26142607      </p>
    26152608      <dl class="empty">
    26162609         <dd>Upstream and downstream describe the flow of a message: all messages flow from upstream to downstream.</dd>
    26172610      </dl>
    2618       <p id="rfc.section.C.p.21"> <span id="rfc.iref.i.1"></span>  <span id="rfc.iref.o.2"></span>  <dfn>inbound</dfn>/<dfn>outbound</dfn> 
     2611      <p id="rfc.section.C.p.20"> <span id="rfc.iref.u.5"></span>  <dfn>user agent</dfn> 
    26192612      </p>
    26202613      <dl class="empty">
    2621          <dd>Inbound and outbound refer to the request and response paths for messages: "inbound" means "traveling toward the origin server",
    2622             and "outbound" means "traveling toward the user agent"
     2614         <dd>The client which initiates a request. These are often browsers, editors, spiders (web-traversing robots), or other end user
     2615            tools.
     2616         </dd>
     2617      </dl>
     2618      <p id="rfc.section.C.p.21"> <span id="rfc.iref.v.2"></span>  <dfn>variant</dfn> 
     2619      </p>
     2620      <dl class="empty">
     2621         <dd>A resource may have one, or more than one, representation(s) associated with it at any given instant. Each of these representations
     2622            is termed a `variant'. Use of the term `variant' does not necessarily imply that the resource is subject to content negotiation.
    26232623         </dd>
    26242624      </dl>
     
    27672767         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/30">http://tools.ietf.org/wg/httpbis/trac/ticket/30</a>&gt;: "Header LWS"
    27682768         </li>
     2769         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/52">http://tools.ietf.org/wg/httpbis/trac/ticket/52</a>&gt;: "Sort 1.3 Terminology"
     2770         </li>
    27692771         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/63">http://tools.ietf.org/wg/httpbis/trac/ticket/63</a>&gt;: "RFC2047 encoded words"
    27702772         </li>
     
    28272829            </li>
    28282830            <li class="indline0"><a id="rfc.index.C" href="#rfc.index.C"><b>C</b></a><ul class="ind">
    2829                   <li class="indline1">cache&nbsp;&nbsp;<a class="iref" href="#rfc.iref.c.6">C</a></li>
    2830                   <li class="indline1">cacheable&nbsp;&nbsp;<a class="iref" href="#rfc.iref.c.7">C</a></li>
     2831                  <li class="indline1">cache&nbsp;&nbsp;<a class="iref" href="#rfc.iref.c.3">C</a></li>
     2832                  <li class="indline1">cacheable&nbsp;&nbsp;<a class="iref" href="#rfc.iref.c.4">C</a></li>
    28312833                  <li class="indline1">client&nbsp;&nbsp;<a class="iref" href="#rfc.iref.c.5">C</a></li>
    2832                   <li class="indline1">connection&nbsp;&nbsp;<a class="iref" href="#rfc.iref.c.3">C</a></li>
     2834                  <li class="indline1">connection&nbsp;&nbsp;<a class="iref" href="#rfc.iref.c.6">C</a></li>
    28332835                  <li class="indline1">Connection header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.connection.1">4.5</a>, <a class="iref" href="#rfc.xref.header.connection.2">7.1.2</a>, <a class="iref" href="#rfc.xref.header.connection.3">7.1.3</a>, <a class="iref" href="#rfc.iref.c.1"><b>8.1</b></a>, <a class="iref" href="#rfc.xref.header.connection.4">8.5</a>, <a class="iref" href="#rfc.xref.header.connection.5">8.8</a>, <a class="iref" href="#rfc.xref.header.connection.6">9.1</a>, <a class="iref" href="#rfc.xref.header.connection.7">B.2</a>, <a class="iref" href="#rfc.xref.header.connection.8">B.4</a></li>
    2834                   <li class="indline1">content negotiation&nbsp;&nbsp;<a class="iref" href="#rfc.iref.c.4">C</a></li>
     2836                  <li class="indline1">content negotiation&nbsp;&nbsp;<a class="iref" href="#rfc.iref.c.7">C</a></li>
    28352837                  <li class="indline1">Content-Length header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.content-length.1">4.4</a>, <a class="iref" href="#rfc.iref.c.2"><b>8.2</b></a>, <a class="iref" href="#rfc.xref.header.content-length.2">9.1</a>, <a class="iref" href="#rfc.xref.header.content-length.3">B.3</a></li>
    28362838               </ul>
     
    30033005            </li>
    30043006            <li class="indline0"><a id="rfc.index.O" href="#rfc.index.O"><b>O</b></a><ul class="ind">
    3005                   <li class="indline1">origin server&nbsp;&nbsp;<a class="iref" href="#rfc.iref.o.1">C</a></li>
    3006                   <li class="indline1">outbound&nbsp;&nbsp;<a class="iref" href="#rfc.iref.o.2">C</a></li>
     3007                  <li class="indline1">origin server&nbsp;&nbsp;<a class="iref" href="#rfc.iref.o.2">C</a></li>
     3008                  <li class="indline1">outbound&nbsp;&nbsp;<a class="iref" href="#rfc.iref.o.1">C</a></li>
    30073009               </ul>
    30083010            </li>
     
    30273029                        <li class="indline1"><em>Section 3.4</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.10">8.5</a></li>
    30283030                        <li class="indline1"><em>Section 4.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.5">1.2.3</a>, <a class="iref" href="#rfc.xref.Part3.8">5</a>, <a class="iref" href="#rfc.xref.Part3.9">6</a></li>
    3029                         <li class="indline1"><em>Section 4</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.13">C</a></li>
     3031                        <li class="indline1"><em>Section 4</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.14">C</a></li>
    30303032                        <li class="indline1"><em>Section 4.2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.4">1.2.3</a></li>
    3031                         <li class="indline1"><em>Section 5</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.14">C</a>, <a class="iref" href="#rfc.xref.Part3.15">C</a></li>
     3033                        <li class="indline1"><em>Section 5</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.13">C</a>, <a class="iref" href="#rfc.xref.Part3.15">C</a></li>
    30323034                        <li class="indline1"><em>Section 6.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.3">1.2.3</a></li>
    30333035                        <li class="indline1"><em>Appendix A</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.1">1</a></li>
     
    30483050                  <li class="indline1">representation&nbsp;&nbsp;<a class="iref" href="#rfc.iref.r.4">C</a></li>
    30493051                  <li class="indline1">request&nbsp;&nbsp;<a class="iref" href="#rfc.iref.r.1">C</a></li>
    3050                   <li class="indline1">resource&nbsp;&nbsp;<a class="iref" href="#rfc.iref.r.3">C</a></li>
    3051                   <li class="indline1">response&nbsp;&nbsp;<a class="iref" href="#rfc.iref.r.2">C</a></li>
     3052                  <li class="indline1">resource&nbsp;&nbsp;<a class="iref" href="#rfc.iref.r.2">C</a></li>
     3053                  <li class="indline1">response&nbsp;&nbsp;<a class="iref" href="#rfc.iref.r.3">C</a></li>
    30523054                  <li class="indline1"><em>RFC1123</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC1123.1">3.2.1</a>, <a class="iref" href="#RFC1123"><b>12.2</b></a></li>
    30533055                  <li class="indline1"><em>RFC1305</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC1305.1">8.3</a>, <a class="iref" href="#RFC1305"><b>12.2</b></a></li>
     
    31143116            <li class="indline0"><a id="rfc.index.U" href="#rfc.index.U"><b>U</b></a><ul class="ind">
    31153117                  <li class="indline1">Upgrade header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.upgrade.1">4.5</a>, <a class="iref" href="#rfc.iref.u.3"><b>8.8</b></a>, <a class="iref" href="#rfc.xref.header.upgrade.2">9.1</a></li>
    3116                   <li class="indline1">upstream&nbsp;&nbsp;<a class="iref" href="#rfc.iref.u.5">C</a></li>
     3118                  <li class="indline1">upstream&nbsp;&nbsp;<a class="iref" href="#rfc.iref.u.4">C</a></li>
    31173119                  <li class="indline1">URI scheme&nbsp;&nbsp;
    31183120                     <ul class="ind">
     
    31223124                  </li>
    31233125                  <li class="indline1"><em>USASCII</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.USASCII.1">1.2</a>, <a class="iref" href="#rfc.xref.USASCII.2">4.2</a>, <a class="iref" href="#USASCII"><b>12.1</b></a></li>
    3124                   <li class="indline1">user agent&nbsp;&nbsp;<a class="iref" href="#rfc.iref.u.4">C</a></li>
     3126                  <li class="indline1">user agent&nbsp;&nbsp;<a class="iref" href="#rfc.iref.u.5">C</a></li>
    31253127               </ul>
    31263128            </li>
Note: See TracChangeset for help on using the changeset viewer.