Ignore:
Timestamp:
04/10/13 11:13:22 (7 years ago)
Author:
julian.reschke@…
Message:

fix NTP reference (see #499)

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p2-semantics.html

    r2424 r2425  
    31053105                  <p id="rfc.section.7.1.1.1.p.6">An HTTP-date value represents time as an instance of Coordinated Universal Time (UTC). The first two formats indicate UTC
    31063106                     by the three-letter abbreviation for Greenwich Mean Time, "GMT", a predecessor of the UTC name; values in the asctime format
    3107                      are assumed to be in UTC. A sender that generates HTTP-date values from a local clock ought to use NTP (<a href="#RFC1305" id="rfc.xref.RFC1305.1"><cite title="Network Time Protocol (Version 3) Specification, Implementation">[RFC1305]</cite></a>) or some similar protocol to synchronize its clock to UTC.
     3107                     are assumed to be in UTC. A sender that generates HTTP-date values from a local clock ought to use NTP (<a href="#RFC5905" id="rfc.xref.RFC5905.1"><cite title="Network Time Protocol Version 4: Protocol and Algorithms Specification">[RFC5905]</cite></a>) or some similar protocol to synchronize its clock to UTC.
    31083108                  </p>
    31093109                  <div id="preferred.date.format">
     
    43544354         </tr>
    43554355         <tr>
    4356             <td class="reference"><b id="RFC1305">[RFC1305]</b></td>
    4357             <td class="top"><a href="mailto:mills@udel.edu" title="University of Delaware, Electrical Engineering Department">Mills, D.</a>, “<a href="http://tools.ietf.org/html/rfc1305">Network Time Protocol (Version 3) Specification, Implementation</a>”, RFC&nbsp;1305, March&nbsp;1992.
    4358             </td>
    4359          </tr>
    4360          <tr>
    43614356            <td class="reference"><b id="RFC1945">[RFC1945]</b></td>
    43624357            <td class="top"><a href="mailto:timbl@w3.org" title="MIT, Laboratory for Computer Science">Berners-Lee, T.</a>, <a href="mailto:fielding@ics.uci.edu" title="University of California, Irvine, Department of Information and Computer Science">Fielding, R.</a>, and <a href="mailto:frystyk@w3.org" title="W3 Consortium, MIT Laboratory for Computer Science">H. Nielsen</a>, “<a href="http://tools.ietf.org/html/rfc1945">Hypertext Transfer Protocol -- HTTP/1.0</a>”, RFC&nbsp;1945, May&nbsp;1996.
     
    44214416            <td class="reference"><b id="RFC5789">[RFC5789]</b></td>
    44224417            <td class="top">Dusseault, L. and J. Snell, “<a href="http://tools.ietf.org/html/rfc5789">PATCH Method for HTTP</a>”, RFC&nbsp;5789, March&nbsp;2010.
     4418            </td>
     4419         </tr>
     4420         <tr>
     4421            <td class="reference"><b id="RFC5905">[RFC5905]</b></td>
     4422            <td class="top">Mills, D., Martin, J., Ed., Burbank, J., and W. Kasch, “<a href="http://tools.ietf.org/html/rfc5905">Network Time Protocol Version 4: Protocol and Algorithms Specification</a>”, RFC&nbsp;5905, June&nbsp;2010.
    44234423            </td>
    44244424         </tr>
     
    48384838         <div id="changes.since.24">
    48394839            <h2 id="rfc.section.E.5"><a href="#rfc.section.E.5">E.5</a>&nbsp;<a href="#changes.since.24">Since draft-ietf-httpbis-p2-semantics-24</a></h2>
    4840             <p id="rfc.section.E.5.p.1">None yet.</p>
     4840            <p id="rfc.section.E.5.p.1">Closed issues: </p>
     4841            <ul>
     4842               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/499">http://tools.ietf.org/wg/httpbis/trac/ticket/499</a>&gt;: "RFC 1305 ref needs to be updated to 5905"
     4843               </li>
     4844            </ul>
    48414845         </div>
    48424846      </div>
     
    51195123                  <li><em>REST</em>&nbsp;&nbsp;<a href="#rfc.xref.REST.1">3</a>, <a href="#rfc.xref.REST.2">4.1</a>, <a href="#REST"><b>11.2</b></a></li>
    51205124                  <li>Retry-After header field&nbsp;&nbsp;<a href="#rfc.xref.header.retry-after.1">6.6.4</a>, <a href="#rfc.xref.header.retry-after.2">7.1</a>, <a href="#rfc.iref.r.3"><b>7.1.3</b></a>, <a href="#rfc.xref.header.retry-after.3">8.3.2</a></li>
    5121                   <li><em>RFC1305</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC1305.1">7.1.1.1</a>, <a href="#RFC1305"><b>11.2</b></a></li>
    51225125                  <li><em>RFC1945</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC1945.1">6.4</a>, <a href="#RFC1945"><b>11.2</b></a><ul>
    51235126                        <li><em>Section 9.3</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC1945.1">6.4</a></li>
     
    51895192                  </li>
    51905193                  <li><em>RFC5789</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5789.1">4.3.4</a>, <a href="#RFC5789"><b>11.2</b></a></li>
     5194                  <li><em>RFC5905</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5905.1">7.1.1.1</a>, <a href="#RFC5905"><b>11.2</b></a></li>
    51915195                  <li><em>RFC5987</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5987.1">8.3.1</a>, <a href="#RFC5987"><b>11.2</b></a></li>
    51925196                  <li><em>RFC5988</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5988.1">6.4.1</a>, <a href="#RFC5988"><b>11.2</b></a></li>
Note: See TracChangeset for help on using the changeset viewer.