[] (0) Add IANA considerations sections for HTTP headers.

git-svn-id: http://svn.whatwg.org/webapps@4091 340c8d12-0b0e-0410-8428-c7bf67bfef74

index

@@ -1041,7 +1041,10 @@
   <li><a href=#application/xhtml+xml><span class=secno>12.2 </span><code>application/xhtml+xml</code></a></li>
   <li><a href=#text/cache-manifest><span class=secno>12.3 </span><code>text/cache-manifest</code></a></li>
   <li><a href=#text/ping><span class=secno>12.4 </span><code>text/ping</code></a></li>
   <li><a href=#application/microdata+json><span class=secno>12.5 </span><code>application/microdata+json</code></a></ol></li>
   <li><a href=#application/microdata+json><span class=secno>12.5 </span><code>application/microdata+json</code></a>
    <ol>
     <li><a href=#ping-from><span class=secno>12.5.1 </span><code>Ping-From</code></a></li>
     <li><a href=#ping-to><span class=secno>12.5.2 </span><code>Ping-To</code></a></ol></ol></li>
 <li><a class=no-num href=#index>Index</a></li>
 <li><a class=no-num href=#references>References</a></li>
 <li><a class=no-num href=#acknowledgements>Acknowledgements</a></ol>
@@ -6901,10 +6904,10 @@ interface <dfn id=htmldocument>HTMLDocument</dfn> {

  <p>The <code>Document</code>'s source file's last modification date
  and time must be derived from relevant features of the networking
  protocols used, e.g. from the value of the HTTP <code title="">Last-Modified</code> header of the document, or from
  metadata in the file system for local files. If the last
  modification date and time are not known, the attribute must return
  the current date and time in the above format.</p>
  protocols used, e.g. from the value of the HTTP <code title=http-last-modified>Last-Modified</code> header of the
  document, or from metadata in the file system for local files. If
  the last modification date and time are not known, the attribute
  must return the current date and time in the above format.</p>

  <hr></div>

   of the <code>Document</code> object containing the hyperlink being
   audited and the ping URL have the <a href=#same-origin>same origin</a></dt>

   <dd>The request must include a <code title=http-ping-from>Ping-From</code> HTTP header with, as its
   <dd>The request must include a <code title=http-ping-from><a href=#ping-from>Ping-From</a></code> HTTP header with, as its
   value, the <a href="#the-document's-address" title="the document's address">address</a> of
   the document containing the hyperlink, and a <code title=http-ping-to>Ping-To</code> HTTP header with, as its value,
   the document containing the hyperlink, and a <code title=http-ping-to><a href=#ping-to>Ping-To</a></code> HTTP header with, as its value,
   the address of the <a href=#absolute-url>absolute URL</a> of the target of the
   hyperlink. The request must not include a <code title=http-referer>Referer</code> (sic) HTTP header. <!-- because
   otherwise it would look like a trustable same-origin POST --></dd>
   <dd>The request must include a <code title="">Referer</code> (sic)
   HTTP header [sic] with, as its value, the <a href="#the-document's-current-address" title="the
   document's current address">current address</a> of the document
   containing the hyperlink, a <code title=http-ping-from>Ping-From</code> HTTP header with the same
   value, and a <code title=http-ping-to>Ping-To</code> HTTP header
   containing the hyperlink, a <code title=http-ping-from><a href=#ping-from>Ping-From</a></code> HTTP header with the same
   value, and a <code title=http-ping-to><a href=#ping-to>Ping-To</a></code> HTTP header
   with, as its value, the address of the target of the
   hyperlink.</dd>

   <dt>Otherwise, the origins are different and the document
   containing the hyperlink being audited was retrieved over an
   encrypted connection</dt>

   <dd>The request must include a <code title=http-ping-to>Ping-To</code> HTTP header with, as its value,
   <dd>The request must include a <code title=http-ping-to><a href=#ping-to>Ping-To</a></code> HTTP header with, as its value,
   the address of the target of the hyperlink. The request must
   neither include a <code title="">Referer</code> (sic) HTTP header
   nor include a <code title=http-ping-from>Ping-From</code> HTTP
   nor include a <code title=http-ping-from><a href=#ping-from>Ping-From</a></code> HTTP
   header.</dd>

  </dl><p class=note>To save bandwidth, implementors might also wish to

  <!-- http://www.w3.org/2002/06/registering-mediatype.html -->

  <h3 id=text/html><span class=secno>12.1 </span><dfn><code>text/html</code></dfn></h3>

  <p>This registration is for community review and will be submitted
  to the IESG for review, approval, and registration with IANA.</p>

  <h3 id=text/html><span class=secno>12.1 </span><dfn><code>text/html</code></dfn></h3>

  <!--
   To: ietf-types@iana.org
   Subject: Registration of media type text/html

  <h3 id=application/xhtml+xml><span class=secno>12.2 </span><dfn><code>application/xhtml+xml</code></dfn></h3>

  <p>This registration is for community review and will be submitted
  to the IESG for review, approval, and registration with IANA.</p>

  <!--
   To: ietf-types@iana.org
   Subject: Registration of media type application/xhtml+xml

  <h3 id=text/cache-manifest><span class=secno>12.3 </span><dfn><code>text/cache-manifest</code></dfn></h3>

  <p>This registration is for community review and will be submitted
  to the IESG for review, approval, and registration with IANA.</p>

  <!--
   To: ietf-types@iana.org
   Subject: Registration of media type text/cache-manifest

  <h3 id=text/ping><span class=secno>12.4 </span><dfn><code>text/ping</code></dfn></h3>

  <p>This registration is for community review and will be submitted
  to the IESG for review, approval, and registration with IANA.</p>

  <!--
   To: ietf-types@iana.org
   Subject: Registration of media type text/ping

  <h3 id=application/microdata+json><span class=secno>12.5 </span><dfn><code>application/microdata+json</code></dfn></h3>

  <p>This registration is for community review and will be submitted
  to the IESG for review, approval, and registration with IANA.</p>

  <!--
   To: ietf-types@iana.org
   Subject: Registration of media type application/microdata+json
  semantics as when used with <code>application/json</code>. <a href=#refsJSON>[JSON]</a></p>


  <h6 id=ping-from><span class=secno>12.5.1 </span><dfn title=http-ping-from><code>Ping-From</code></dfn></h6>

  <p>This section describes a header field for registration in the
  Permanent Message Header Field Registry.  <a href=#refsRFC3864>[RFC3864]</a></p>

  <dl><dt>Header field name</dt>
   <dd>Ping-From</dd>
   <dt>Applicable protocol</dt>
   <dd>http</dd>
   <dt>Status</dt>
   <dd>standard</dd>
   <dt>Author/Change controller</dt>
   <dd>W3C and WHATWG</dd>
   <dt>Specification document(s)</dt>
   <dd>
    This document is the relevant specification.
   </dd>
   <dt>Related information</dt>
   <dd>None.</dd>   
  </dl><h6 id=ping-to><span class=secno>12.5.2 </span><dfn title=http-ping-to><code>Ping-To</code></dfn></h6>

  <h2 class=no-num id=index>Index</h2>
  <p>This section describes a header field for registration in the
  Permanent Message Header Field Registry.  <a href=#refsRFC3864>[RFC3864]</a></p>

  <dl><dt>Header field name</dt>
   <dd>Ping-To</dd>
   <dt>Applicable protocol</dt>
   <dd>http</dd>
   <dt>Status</dt>
   <dd>standard</dd>
   <dt>Author/Change controller</dt>
   <dd>W3C and WHATWG</dd>
   <dt>Specification document(s)</dt>
   <dd>
    This document is the relevant specification.
   </dd>
   <dt>Related information</dt>
   <dd>None.</dd>   
  </dl><h2 class=no-num id=index>Index</h2>

  <p><i>This section is non-normative.</i></p>

   and Base64 Data Encodings</a></cite>, S. Josefsson. IETF, July
   2003.</dd>

   <dt id=refsRFC3864>[RFC3864]</dt>
   <dd><cite><a href=http://www.ietf.org/rfc/rfc3864.txt>Registration Procedures
   for Message Header Fields</a></cite>, G. Klyne, M. Nottingham,
   J. Mogul. IETF, September 2004.</dd>

   <dt id=refsRFC3986>[RFC3986]</dt>
   <dd><cite><a href=http://www.ietf.org/rfc/rfc3986.txt>Uniform Resource
   Identifier (URI): Generic Syntax</a></cite>, T. Berners-Lee, R. Fielding, L.