Source: https://trac.ietf.org/trac/httpbis/browser/draft-ietf-httpbis/20/p6-cache.html?rev=2726
Timestamp: 2020-02-28 15:52:51
Document Index: 66117860

Matched Legal Cases: ['art1', 'art1', 'art 1', 'art1', 'art 1', 'art 2', 'art 4', 'art 5', 'art 7']

source: draft-ietf-httpbis/20/p6-cache.html @ 2726
<li><a href="#rfc.section.7.2.1">7.2.1</a>&nbsp;&nbsp;&nbsp;<a href="#cache-request-directive">Request Cache-Control Directives</a></li>
<li><a href="#rfc.section.7.2.2">7.2.2</a>&nbsp;&nbsp;&nbsp;<a href="#cache-response-directive">Response Cache-Control Directives</a></li>
<li><a href="#rfc.section.C.1">C.1</a>&nbsp;&nbsp;&nbsp;<a href="#changes.since.19">Since draft-ietf-httpbis-p6-cache-19</a></li>
<p id="rfc.section.1.2.p.14"><span id="rfc.iref.s.3"></span> <span id="rfc.iref.v.2"></span> <dfn>strong validator</dfn>
<h2 id="rfc.section.1.3"><a href="#rfc.section.1.3">1.3</a>&nbsp;<a href="#intro.conformance.and.error.handling">Conformance and Error Handling</a></h2>
<p id="rfc.section.1.4.p.1">This specification uses the Augmented Backus-Naur Form (ABNF) notation of <a href="#RFC5234" id="rfc.xref.RFC5234.1"><cite title="Augmented BNF for Syntax Specifications: ABNF">[RFC5234]</cite></a> with the list rule extension defined in <a href="p1-messaging.html#notation" title="Syntax Notation">Section 1.2</a> of <a href="#Part1" id="rfc.xref.Part1.2"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>. <a href="#imported.abnf" title="Imported ABNF">Appendix&nbsp;B</a> describes rules imported from other documents.
<div class="error">ERROR: Undefined target: collected.abnf (at line 353)</div> shows the collected ABNF with the list rule expanded.
<h3 id="rfc.section.1.4.1"><a href="#rfc.section.1.4.1">1.4.1</a>&nbsp;<a href="#delta-seconds">Delta Seconds</a></h3>
<h2 id="rfc.section.4.1"><a href="#rfc.section.4.1">4.1</a>&nbsp;<a href="#expiration.model">Freshness Model</a></h2>
<h3 id="rfc.section.4.1.1"><a href="#rfc.section.4.1.1">4.1.1</a>&nbsp;<a href="#calculating.freshness.lifetime">Calculating Freshness Lifetime</a></h3>
<h3 id="rfc.section.4.1.2"><a href="#rfc.section.4.1.2">4.1.2</a>&nbsp;<a href="#heuristic.freshness">Calculating Heuristic Freshness</a></h3>
<h3 id="rfc.section.4.1.3"><a href="#rfc.section.4.1.3">4.1.3</a>&nbsp;<a href="#age.calculations">Calculating Age</a></h3>
<p id="rfc.section.4.1.3.p.15"></p>
<h3 id="rfc.section.4.1.4"><a href="#rfc.section.4.1.4">4.1.4</a>&nbsp;<a href="#serving.stale.responses">Serving Stale Responses</a></h3>
<h2 id="rfc.section.4.2"><a href="#rfc.section.4.2">4.2</a>&nbsp;<a href="#validation.model">Validation Model</a></h2>
<p id="rfc.section.4.2.p.5"></p>
<h3 id="rfc.section.4.2.1"><a href="#rfc.section.4.2.1">4.2.1</a>&nbsp;<a href="#freshening.responses">Freshening Responses with 304 Not Modified</a></h3>
<h2 id="rfc.section.4.3"><a href="#rfc.section.4.3">4.3</a>&nbsp;<a href="#caching.negotiated.responses">Using Negotiated Responses</a></h2>
<h2 id="rfc.section.4.4"><a href="#rfc.section.4.4">4.4</a>&nbsp;<a href="#combining.responses">Combining Partial Content</a></h2>
<h1 id="rfc.section.5"><a href="#rfc.section.5">5.</a>&nbsp;<a href="#head.effects">Updating Caches with HEAD Responses</a></h1>
<h1 id="rfc.section.6"><a href="#rfc.section.6">6.</a>&nbsp;<a href="#invalidation.after.updates.or.deletions">Request Methods that Invalidate</a></h1>
<h1 id="rfc.section.7"><a href="#rfc.section.7">7.</a>&nbsp;<a href="#header.field.definitions">Header Field Definitions</a></h1>
<h2 id="rfc.section.7.1"><a href="#rfc.section.7.1">7.1</a>&nbsp;<a href="#header.age">Age</a></h2>
<h2 id="rfc.section.7.2"><a href="#rfc.section.7.2">7.2</a>&nbsp;<a href="#header.cache-control">Cache-Control</a></h2>
<p><b>Note:</b> HTTP/1.0 caches might not implement Cache-Control and might only implement Pragma: no-cache (see <a href="#header.pragma" id="rfc.xref.header.pragma.2" title="Pragma">Section&nbsp;7.4</a>).
<h3 id="rfc.section.7.2.1"><a href="#rfc.section.7.2.1">7.2.1</a>&nbsp;<a href="#cache-request-directive">Request Cache-Control Directives</a></h3>
<h4 id="rfc.section.7.2.1.1"><a href="#rfc.section.7.2.1.1">7.2.1.1</a>&nbsp;<a href="#cache-request-directive.no-cache">no-cache</a></h4>
<h4 id="rfc.section.7.2.1.2"><a href="#rfc.section.7.2.1.2">7.2.1.2</a>&nbsp;<a href="#cache-request-directive.no-store">no-store</a></h4>
<h4 id="rfc.section.7.2.1.3"><a href="#rfc.section.7.2.1.3">7.2.1.3</a>&nbsp;<a href="#cache-request-directive.max-age">max-age</a></h4>
<li><a href="#delta-seconds" class="smpl">delta-seconds</a> (see <a href="#delta-seconds" title="Delta Seconds">Section&nbsp;1.4.1</a>)
<p id="rfc.section.7.2.1.3.p.3"><b>Note:</b> This directive uses the token form of the argument syntax; e.g., 'max-age=5', not 'max-age="5"'. Senders <em class="bcp14">SHOULD NOT</em> use the quoted-string form.
<h4 id="rfc.section.7.2.1.4"><a href="#rfc.section.7.2.1.4">7.2.1.4</a>&nbsp;<a href="#cache-request-directive.max-stale">max-stale</a></h4>
<p id="rfc.section.7.2.1.4.p.3"><b>Note:</b> This directive uses the token form of the argument syntax; e.g., 'max-stale=10', not 'max-stale="10"'. Senders <em class="bcp14">SHOULD NOT</em> use the quoted-string form.
<h4 id="rfc.section.7.2.1.5"><a href="#rfc.section.7.2.1.5">7.2.1.5</a>&nbsp;<a href="#cache-request-directive.min-fresh">min-fresh</a></h4>
<p id="rfc.section.7.2.1.5.p.3"><b>Note:</b> This directive uses the token form of the argument syntax; e.g., 'min-fresh=20', not 'min-fresh="20"'. Senders <em class="bcp14">SHOULD NOT</em> use the quoted-string form.
<h4 id="rfc.section.7.2.1.6"><a href="#rfc.section.7.2.1.6">7.2.1.6</a>&nbsp;<a href="#cache-request-directive.no-transform">no-transform</a></h4>
<h4 id="rfc.section.7.2.1.7"><a href="#rfc.section.7.2.1.7">7.2.1.7</a>&nbsp;<a href="#cache-request-directive.only-if-cached">only-if-cached</a></h4>
<h3 id="rfc.section.7.2.2"><a href="#rfc.section.7.2.2">7.2.2</a>&nbsp;<a href="#cache-response-directive">Response Cache-Control Directives</a></h3>
<div id="cache-response-directive.only-if-cached">
<h4 id="rfc.section.7.2.2.1"><a href="#rfc.section.7.2.2.1">7.2.2.1</a>&nbsp;<a href="#cache-response-directive.only-if-cached">public</a></h4>
<h4 id="rfc.section.7.2.2.2"><a href="#rfc.section.7.2.2.2">7.2.2.2</a>&nbsp;<a href="#cache-response-directive.private">private</a></h4>
<p id="rfc.section.7.2.2.2.p.5"><b>Note:</b> This usage of the word "private" only controls where the response can be stored; it cannot ensure the privacy of the message
<h4 id="rfc.section.7.2.2.3"><a href="#rfc.section.7.2.2.3">7.2.2.3</a>&nbsp;<a href="#cache-response-directive.no-cache">no-cache</a></h4>
<p id="rfc.section.7.2.2.3.p.5"><b>Note:</b> Many HTTP/1.0 caches will not recognize or obey this directive. Also, no-cache response directives with field-names are often
<p id="rfc.section.7.2.2.3.p.6"><b>Note:</b> This directive uses the quoted-string form of the argument syntax. Senders <em class="bcp14">SHOULD NOT</em> use the token form (even if quoting appears not to be needed for single-entry lists).
<h4 id="rfc.section.7.2.2.4"><a href="#rfc.section.7.2.2.4">7.2.2.4</a>&nbsp;<a href="#cache-response-directive.no-store">no-store</a></h4>
<h4 id="rfc.section.7.2.2.5"><a href="#rfc.section.7.2.2.5">7.2.2.5</a>&nbsp;<a href="#cache-response-directive.must-revalidate">must-revalidate</a></h4>
<h4 id="rfc.section.7.2.2.6"><a href="#rfc.section.7.2.2.6">7.2.2.6</a>&nbsp;<a href="#cache-response-directive.proxy-revalidate">proxy-revalidate</a></h4>
<h4 id="rfc.section.7.2.2.7"><a href="#rfc.section.7.2.2.7">7.2.2.7</a>&nbsp;<a href="#cache-response-directive.max-age">max-age</a></h4>
<p id="rfc.section.7.2.2.7.p.3"><b>Note:</b> This directive uses the token form of the argument syntax; e.g., 'max-age=5', not 'max-age="5"'. Senders <em class="bcp14">SHOULD NOT</em> use the quoted-string form.
<h4 id="rfc.section.7.2.2.8"><a href="#rfc.section.7.2.2.8">7.2.2.8</a>&nbsp;<a href="#cache-response-directive.s-maxage">s-maxage</a></h4>
<p id="rfc.section.7.2.2.8.p.3"><b>Note:</b> This directive uses the token form of the argument syntax; e.g., 's-maxage=10', not 's-maxage="10"'. Senders <em class="bcp14">SHOULD NOT</em> use the quoted-string form.
<h4 id="rfc.section.7.2.2.9"><a href="#rfc.section.7.2.2.9">7.2.2.9</a>&nbsp;<a href="#cache-response-directive.no-transform">no-transform</a></h4>
<h3 id="rfc.section.7.2.3"><a href="#rfc.section.7.2.3">7.2.3</a>&nbsp;<a href="#cache.control.extensions">Cache Control Extensions</a></h3>
<p id="rfc.section.7.2.3.p.8"></p>
<p id="rfc.section.7.2.3.p.11">Values to be added to this name space require IETF Review (see <a href="#RFC5226" id="rfc.xref.RFC5226.1"><cite title="Guidelines for Writing an IANA Considerations Section in RFCs">[RFC5226]</cite></a>, <a href="https://tools.ietf.org/html/rfc5226#section-4.1">Section 4.1</a>).
<h2 id="rfc.section.7.3"><a href="#rfc.section.7.3">7.3</a>&nbsp;<a href="#header.expires">Expires</a></h2>
<p><b>Note:</b> If a response includes a <a href="#header.cache-control" class="smpl">Cache-Control</a> field with the max-age directive (see <a href="#cache-response-directive.max-age" title="max-age">Section&nbsp;7.2.2.7</a>), that directive overrides the Expires field. Likewise, the s-maxage directive (<a href="#cache-response-directive.s-maxage" title="s-maxage">Section&nbsp;7.2.2.8</a>) overrides the <a href="#header.expires" class="smpl">Expires</a> header fieldin shared caches.
<h2 id="rfc.section.7.4"><a href="#rfc.section.7.4">7.4</a>&nbsp;<a href="#header.pragma">Pragma</a></h2>
<h2 id="rfc.section.7.5"><a href="#rfc.section.7.5">7.5</a>&nbsp;<a href="#header.vary">Vary</a></h2>
<h2 id="rfc.section.7.6"><a href="#rfc.section.7.6">7.6</a>&nbsp;<a href="#header.warning">Warning</a></h2>
<h3 id="rfc.section.7.6.1"><a href="#rfc.section.7.6.1">7.6.1</a>&nbsp;<a href="#warn.110">110 Response is Stale</a></h3>
<h3 id="rfc.section.7.6.2"><a href="#rfc.section.7.6.2">7.6.2</a>&nbsp;<a href="#warn.111">111 Revalidation Failed</a></h3>
<h3 id="rfc.section.7.6.3"><a href="#rfc.section.7.6.3">7.6.3</a>&nbsp;<a href="#warn.112">112 Disconnected Operation</a></h3>
<h3 id="rfc.section.7.6.4"><a href="#rfc.section.7.6.4">7.6.4</a>&nbsp;<a href="#warn.113">113 Heuristic Expiration</a></h3>
<h3 id="rfc.section.7.6.5"><a href="#rfc.section.7.6.5">7.6.5</a>&nbsp;<a href="#warn.199">199 Miscellaneous Warning</a></h3>
<h3 id="rfc.section.7.6.6"><a href="#rfc.section.7.6.6">7.6.6</a>&nbsp;<a href="#warn.214">214 Transformation Applied</a></h3>
<p id="rfc.section.7.6.6.p.1"><em class="bcp14">MUST</em> be added by a proxy if it applies any transformation to the representation, such as changing the content-coding, media-type,
<h3 id="rfc.section.7.6.7"><a href="#rfc.section.7.6.7">7.6.7</a>&nbsp;<a href="#warn.299">299 Miscellaneous Persistent Warning</a></h3>
<div id="warn.code.extensions">
<h3 id="rfc.section.7.6.8"><a href="#rfc.section.7.6.8">7.6.8</a>&nbsp;<a href="#warn.code.extensions">Warn Code Extensions</a></h3>
<p id="rfc.section.7.6.8.p.3">Values to be added to this name space require IETF Review (see <a href="#RFC5226" id="rfc.xref.RFC5226.2"><cite title="Guidelines for Writing an IANA Considerations Section in RFCs">[RFC5226]</cite></a>, <a href="https://tools.ietf.org/html/rfc5226#section-4.1">Section 4.1</a>).
<h1 id="rfc.section.8"><a href="#rfc.section.8">8.</a>&nbsp;<a href="#history.lists">History Lists</a></h1>
<h1 id="rfc.section.9"><a href="#rfc.section.9">9.</a>&nbsp;<a href="#IANA.considerations">IANA Considerations</a></h1>
<h2 id="rfc.section.9.1"><a href="#rfc.section.9.1">9.1</a>&nbsp;<a href="#cache.directive.registration">Cache Directive Registry</a></h2>
<h2 id="rfc.section.9.2"><a href="#rfc.section.9.2">9.2</a>&nbsp;<a href="#warn.code.registration">Warn Code Registry</a></h2>
<h2 id="rfc.section.9.3"><a href="#rfc.section.9.3">9.3</a>&nbsp;<a href="#header.field.registration">Header Field Registration</a></h2>
<h1 id="rfc.section.10"><a href="#rfc.section.10">10.</a>&nbsp;<a href="#security.considerations">Security Considerations</a></h1>
<h1 id="rfc.section.11"><a href="#rfc.section.11">11.</a>&nbsp;<a href="#acks">Acknowledgments</a></h1>
<td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="https://tools.ietf.org/html/draft-ietf-httpbis-p1-messaging-20">HTTP/1.1, part 1: Message Routing and Syntax"</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p1-messaging-20 (work in progress), July&nbsp;2012.
<td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="https://tools.ietf.org/html/draft-ietf-httpbis-p2-semantics-20">HTTP/1.1, part 2: Semantics and Payloads</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p2-semantics-20 (work in progress), July&nbsp;2012.
<td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="https://tools.ietf.org/html/draft-ietf-httpbis-p4-conditional-20">HTTP/1.1, part 4: Conditional Requests</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p4-conditional-20 (work in progress), July&nbsp;2012.
<td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="https://tools.ietf.org/html/draft-ietf-httpbis-p5-range-20">HTTP/1.1, part 5: Range Requests</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p5-range-20 (work in progress), July&nbsp;2012.
<td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="https://tools.ietf.org/html/draft-ietf-httpbis-p7-auth-20">HTTP/1.1, part 7: Authentication</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p7-auth-20 (work in progress), July&nbsp;2012.
<p id="rfc.section.A.p.5">Do not mention RFC 2047 encoding and multiple languages in <a href="#header.warning" class="smpl">Warning</a> header fields anymore, as these aspects never were implemented. (<a href="#header.warning" id="rfc.xref.header.warning.5" title="Warning">Section&nbsp;7.6</a>)
<h2 id="rfc.section.C.1"><a href="#rfc.section.C.1">C.1</a>&nbsp;<a href="#changes.since.19">Since draft-ietf-httpbis-p6-cache-19</a></h2>
<li>110 Response is Stale (warn code)&nbsp;&nbsp;<a href="#rfc.iref.1.1"><b>7.6.1</b></a></li>
<li>111 Revalidation Failed (warn code)&nbsp;&nbsp;<a href="#rfc.iref.1.2"><b>7.6.2</b></a></li>
<li>112 Disconnected Operation (warn code)&nbsp;&nbsp;<a href="#rfc.iref.1.3"><b>7.6.3</b></a></li>
<li>113 Heuristic Expiration (warn code)&nbsp;&nbsp;<a href="#rfc.iref.1.4"><b>7.6.4</b></a></li>
<li>199 Miscellaneous Warning (warn code)&nbsp;&nbsp;<a href="#rfc.iref.1.5"><b>7.6.5</b></a></li>
<li>214 Transformation Applied (warn code)&nbsp;&nbsp;<a href="#rfc.iref.2.1"><b>7.6.6</b></a></li>
<li>299 Miscellaneous Persistent Warning (warn code)&nbsp;&nbsp;<a href="#rfc.iref.2.2"><b>7.6.7</b></a></li>
<li>Age header field&nbsp;&nbsp;<a href="#rfc.xref.header.age.1">4</a>, <a href="#rfc.xref.header.age.2">4.1.3</a>, <a href="#rfc.iref.a.2"><b>7.1</b></a></li>
<li>Cache-Control header field&nbsp;&nbsp;<a href="#rfc.xref.header.cache-control.1">3</a>, <a href="#rfc.iref.c.6"><b>7.2</b></a></li>
<li>Expires header field&nbsp;&nbsp;<a href="#rfc.xref.header.expires.1">3</a>, <a href="#rfc.xref.header.expires.2">4.1</a>, <a href="#rfc.xref.header.expires.3">4.1.1</a>, <a href="#rfc.iref.e.2"><b>7.3</b></a></li>
<li>Age&nbsp;&nbsp;<a href="#rfc.xref.header.age.1">4</a>, <a href="#rfc.xref.header.age.2">4.1.3</a>, <a href="#rfc.iref.h.2"><b>7.1</b></a></li>
<li>Cache-Control&nbsp;&nbsp;<a href="#rfc.xref.header.cache-control.1">3</a>, <a href="#rfc.iref.h.3"><b>7.2</b></a></li>
<li>Expires&nbsp;&nbsp;<a href="#rfc.xref.header.expires.1">3</a>, <a href="#rfc.xref.header.expires.2">4.1</a>, <a href="#rfc.xref.header.expires.3">4.1.1</a>, <a href="#rfc.iref.h.4"><b>7.3</b></a></li>
<li>Pragma&nbsp;&nbsp;<a href="#rfc.xref.header.pragma.1">4</a>, <a href="#rfc.xref.header.pragma.2">7.2</a>, <a href="#rfc.iref.h.5"><b>7.4</b></a></li>
<li>Vary&nbsp;&nbsp;<a href="#rfc.xref.header.vary.1">4.3</a>, <a href="#rfc.iref.h.6"><b>7.5</b></a></li>
<li>Warning&nbsp;&nbsp;<a href="#rfc.xref.header.warning.1">4.1.4</a>, <a href="#rfc.xref.header.warning.2">4.2.1</a>, <a href="#rfc.xref.header.warning.3">4.4</a>, <a href="#rfc.xref.header.warning.4">5</a>, <a href="#rfc.iref.h.7"><b>7.6</b></a>, <a href="#rfc.xref.header.warning.5">A</a></li>
<li>Pragma header field&nbsp;&nbsp;<a href="#rfc.xref.header.pragma.1">4</a>, <a href="#rfc.xref.header.pragma.2">7.2</a>, <a href="#rfc.iref.p.5"><b>7.4</b></a></li>
<li><em>RFC5861</em>&nbsp;&nbsp;<a href="#RFC5861"><b>12.2</b></a></li>
<li>Vary header field&nbsp;&nbsp;<a href="#rfc.xref.header.vary.1">4.3</a>, <a href="#rfc.iref.v.3"><b>7.5</b></a></li>
<li>110 Response is Stale&nbsp;&nbsp;<a href="#rfc.iref.w.2"><b>7.6.1</b></a></li>
<li>111 Revalidation Failed&nbsp;&nbsp;<a href="#rfc.iref.w.3"><b>7.6.2</b></a></li>
<li>112 Disconnected Operation&nbsp;&nbsp;<a href="#rfc.iref.w.4"><b>7.6.3</b></a></li>
<li>113 Heuristic Expiration&nbsp;&nbsp;<a href="#rfc.iref.w.5"><b>7.6.4</b></a></li>
<li>199 Miscellaneous Warning&nbsp;&nbsp;<a href="#rfc.iref.w.6"><b>7.6.5</b></a></li>
<li>214 Transformation Applied&nbsp;&nbsp;<a href="#rfc.iref.w.7"><b>7.6.6</b></a></li>
<li>299 Miscellaneous Persistent Warning&nbsp;&nbsp;<a href="#rfc.iref.w.8"><b>7.6.7</b></a></li>
<li>Warning header field&nbsp;&nbsp;<a href="#rfc.xref.header.warning.1">4.1.4</a>, <a href="#rfc.xref.header.warning.2">4.2.1</a>, <a href="#rfc.xref.header.warning.3">4.4</a>, <a href="#rfc.xref.header.warning.4">5</a>, <a href="#rfc.iref.w.1"><b>7.6</b></a>, <a href="#rfc.xref.header.warning.5">A</a></li>
<br>Rackspace<br>Email: <a href="mailto:mnot@mnot.net">mnot@mnot.net</a><br>URI: <a href="http://www.mnot.net/">http://www.mnot.net/</a></p>