![(please configure the [header_logo] section in trac.ini)](https://www.ietf.org/images/ietflogotrans.gif)
Changeset 1414 for draft-ietf-httpbis
- Timestamp:
- 26/08/11 14:08:10 (11 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 4 edited
-
p1-messaging.html (modified) (8 diffs)
-
p1-messaging.xml (modified) (3 diffs)
-
p3-payload.html (modified) (8 diffs)
-
p3-payload.xml (modified) (3 diffs)
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p1-messaging.html
r1412 r1414 359 359 } 360 360 @bottom-center { 361 content: "Expires February 2 6, 2012";361 content: "Expires February 27, 2012"; 362 362 } 363 363 @bottom-right { … … 409 409 <meta name="dct.creator" content="Reschke, J. F."> 410 410 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p1-messaging-latest"> 411 <meta name="dct.issued" scheme="ISO8601" content="2011-08-2 5">411 <meta name="dct.issued" scheme="ISO8601" content="2011-08-26"> 412 412 <meta name="dct.replaces" content="urn:ietf:rfc:2145"> 413 413 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> … … 441 441 </tr> 442 442 <tr> 443 <td class="left">Expires: February 2 6, 2012</td>443 <td class="left">Expires: February 27, 2012</td> 444 444 <td class="right">HP</td> 445 445 </tr> … … 494 494 <tr> 495 495 <td class="left"></td> 496 <td class="right">August 2 5, 2011</td>496 <td class="right">August 26, 2011</td> 497 497 </tr> 498 498 </tbody> … … 527 527 in progress”. 528 528 </p> 529 <p>This Internet-Draft will expire on February 2 6, 2012.</p>529 <p>This Internet-Draft will expire on February 27, 2012.</p> 530 530 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 531 531 <p>Copyright © 2011 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 2844 2844 <td class="reference"><b id="RFC1950">[RFC1950]</b></td> 2845 2845 <td class="top"><a href="mailto:ghost@aladdin.com" title="Aladdin Enterprises">Deutsch, L.</a> and J-L. Gailly, “<a href="http://tools.ietf.org/html/rfc1950">ZLIB Compressed Data Format Specification version 3.3</a>”, RFC 1950, May 1996.<br>RFC 1950 is an Informational RFC, thus it might be less stable than this specification. On the other hand, this downward reference 2846 was present since the publication of RFC 2068 in 1997 (<a href="#RFC2068" id="rfc.xref.RFC2068.5"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a>), therefore it is unlikely to cause problems in practice. See also <a href="#BCP97" id="rfc.xref.BCP97.1"><cite title="Handling Normative References to Standards-Track Documents">[BCP97]</cite></a>.2846 was present since the publication of <cite title="Hypertext Transfer Protocol -- HTTP/1.1" id="rfc.xref.RFC2068.5">RFC 2068</cite> in 1997, therefore it is unlikely to cause problems in practice. See also <a href="#BCP97" id="rfc.xref.BCP97.1"><cite title="Handling Normative References to Standards-Track Documents">[BCP97]</cite></a>. 2847 2847 </td> 2848 2848 </tr> … … 2850 2850 <td class="reference"><b id="RFC1951">[RFC1951]</b></td> 2851 2851 <td class="top"><a href="mailto:ghost@aladdin.com" title="Aladdin Enterprises">Deutsch, P.</a>, “<a href="http://tools.ietf.org/html/rfc1951">DEFLATE Compressed Data Format Specification version 1.3</a>”, RFC 1951, May 1996.<br>RFC 1951 is an Informational RFC, thus it might be less stable than this specification. On the other hand, this downward reference 2852 was present since the publication of RFC 2068 in 1997 (<a href="#RFC2068" id="rfc.xref.RFC2068.6"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a>), therefore it is unlikely to cause problems in practice. See also <a href="#BCP97" id="rfc.xref.BCP97.2"><cite title="Handling Normative References to Standards-Track Documents">[BCP97]</cite></a>.2852 was present since the publication of <cite title="Hypertext Transfer Protocol -- HTTP/1.1" id="rfc.xref.RFC2068.6">RFC 2068</cite> in 1997, therefore it is unlikely to cause problems in practice. See also <a href="#BCP97" id="rfc.xref.BCP97.2"><cite title="Handling Normative References to Standards-Track Documents">[BCP97]</cite></a>. 2853 2853 </td> 2854 2854 </tr> … … 2856 2856 <td class="reference"><b id="RFC1952">[RFC1952]</b></td> 2857 2857 <td class="top"><a href="mailto:ghost@aladdin.com" title="Aladdin Enterprises">Deutsch, P.</a>, <a href="mailto:gzip@prep.ai.mit.edu">Gailly, J-L.</a>, <a href="mailto:madler@alumni.caltech.edu">Adler, M.</a>, <a href="mailto:ghost@aladdin.com">Deutsch, L.</a>, and <a href="mailto:randeg@alumni.rpi.edu">G. Randers-Pehrson</a>, “<a href="http://tools.ietf.org/html/rfc1952">GZIP file format specification version 4.3</a>”, RFC 1952, May 1996.<br>RFC 1952 is an Informational RFC, thus it might be less stable than this specification. On the other hand, this downward reference 2858 was present since the publication of RFC 2068 in 1997 (<a href="#RFC2068" id="rfc.xref.RFC2068.7"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a>), therefore it is unlikely to cause problems in practice. See also <a href="#BCP97" id="rfc.xref.BCP97.3"><cite title="Handling Normative References to Standards-Track Documents">[BCP97]</cite></a>.2858 was present since the publication of <cite title="Hypertext Transfer Protocol -- HTTP/1.1" id="rfc.xref.RFC2068.7">RFC 2068</cite> in 1997, therefore it is unlikely to cause problems in practice. See also <a href="#BCP97" id="rfc.xref.BCP97.3"><cite title="Handling Normative References to Standards-Track Documents">[BCP97]</cite></a>. 2859 2859 </td> 2860 2860 </tr> -
draft-ietf-httpbis/latest/p1-messaging.xml
r1412 r1414 4593 4593 RFC 1950 is an Informational RFC, thus it might be less stable than 4594 4594 this specification. On the other hand, this downward reference was 4595 present since the publication of RFC 2068 in 1997 (<xref target="RFC2068"/>),4595 present since the publication of <xref target="RFC2068" x:fmt="none">RFC 2068</xref> in 1997, 4596 4596 therefore it is unlikely to cause problems in practice. See also 4597 4597 <xref target="BCP97"/>. … … 4612 4612 RFC 1951 is an Informational RFC, thus it might be less stable than 4613 4613 this specification. On the other hand, this downward reference was 4614 present since the publication of RFC 2068 in 1997 (<xref target="RFC2068"/>),4614 present since the publication of <xref target="RFC2068" x:fmt="none">RFC 2068</xref> in 1997, 4615 4615 therefore it is unlikely to cause problems in practice. See also 4616 4616 <xref target="BCP97"/>. … … 4643 4643 RFC 1952 is an Informational RFC, thus it might be less stable than 4644 4644 this specification. On the other hand, this downward reference was 4645 present since the publication of RFC 2068 in 1997 (<xref target="RFC2068"/>),4645 present since the publication of <xref target="RFC2068" x:fmt="none">RFC 2068</xref> in 1997, 4646 4646 therefore it is unlikely to cause problems in practice. See also 4647 4647 <xref target="BCP97"/>. -
draft-ietf-httpbis/latest/p3-payload.html
r1410 r1414 359 359 } 360 360 @bottom-center { 361 content: "Expires February 2 5, 2012";361 content: "Expires February 27, 2012"; 362 362 } 363 363 @bottom-right { … … 408 408 <meta name="dct.creator" content="Reschke, J. F."> 409 409 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p3-payload-latest"> 410 <meta name="dct.issued" scheme="ISO8601" content="2011-08-2 4">410 <meta name="dct.issued" scheme="ISO8601" content="2011-08-26"> 411 411 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 412 412 <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 3 of the seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 3 defines HTTP message content, metadata, and content negotiation."> … … 434 434 </tr> 435 435 <tr> 436 <td class="left">Expires: February 2 5, 2012</td>436 <td class="left">Expires: February 27, 2012</td> 437 437 <td class="right">J. Mogul</td> 438 438 </tr> … … 491 491 <tr> 492 492 <td class="left"></td> 493 <td class="right">August 2 4, 2011</td>493 <td class="right">August 26, 2011</td> 494 494 </tr> 495 495 </tbody> … … 519 519 in progress”. 520 520 </p> 521 <p>This Internet-Draft will expire on February 2 5, 2012.</p>521 <p>This Internet-Draft will expire on February 27, 2012.</p> 522 522 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 523 523 <p>Copyright © 2011 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 1513 1513 <td class="reference"><b id="RFC1950">[RFC1950]</b></td> 1514 1514 <td class="top"><a href="mailto:ghost@aladdin.com" title="Aladdin Enterprises">Deutsch, L.</a> and J-L. Gailly, “<a href="http://tools.ietf.org/html/rfc1950">ZLIB Compressed Data Format Specification version 3.3</a>”, RFC 1950, May 1996.<br>RFC 1950 is an Informational RFC, thus it might be less stable than this specification. On the other hand, this downward reference 1515 was present since the publication of RFC 2068 in 1997 (<a href="#RFC2068" id="rfc.xref.RFC2068.1"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a>), therefore it is unlikely to cause problems in practice. See also <a href="#BCP97" id="rfc.xref.BCP97.1"><cite title="Handling Normative References to Standards-Track Documents">[BCP97]</cite></a>.1515 was present since the publication of <cite title="Hypertext Transfer Protocol -- HTTP/1.1" id="rfc.xref.RFC2068.1">RFC 2068</cite> in 1997, therefore it is unlikely to cause problems in practice. See also <a href="#BCP97" id="rfc.xref.BCP97.1"><cite title="Handling Normative References to Standards-Track Documents">[BCP97]</cite></a>. 1516 1516 </td> 1517 1517 </tr> … … 1519 1519 <td class="reference"><b id="RFC1951">[RFC1951]</b></td> 1520 1520 <td class="top"><a href="mailto:ghost@aladdin.com" title="Aladdin Enterprises">Deutsch, P.</a>, “<a href="http://tools.ietf.org/html/rfc1951">DEFLATE Compressed Data Format Specification version 1.3</a>”, RFC 1951, May 1996.<br>RFC 1951 is an Informational RFC, thus it might be less stable than this specification. On the other hand, this downward reference 1521 was present since the publication of RFC 2068 in 1997 (<a href="#RFC2068" id="rfc.xref.RFC2068.2"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a>), therefore it is unlikely to cause problems in practice. See also <a href="#BCP97" id="rfc.xref.BCP97.2"><cite title="Handling Normative References to Standards-Track Documents">[BCP97]</cite></a>.1521 was present since the publication of <cite title="Hypertext Transfer Protocol -- HTTP/1.1" id="rfc.xref.RFC2068.2">RFC 2068</cite> in 1997, therefore it is unlikely to cause problems in practice. See also <a href="#BCP97" id="rfc.xref.BCP97.2"><cite title="Handling Normative References to Standards-Track Documents">[BCP97]</cite></a>. 1522 1522 </td> 1523 1523 </tr> … … 1525 1525 <td class="reference"><b id="RFC1952">[RFC1952]</b></td> 1526 1526 <td class="top"><a href="mailto:ghost@aladdin.com" title="Aladdin Enterprises">Deutsch, P.</a>, <a href="mailto:gzip@prep.ai.mit.edu">Gailly, J-L.</a>, <a href="mailto:madler@alumni.caltech.edu">Adler, M.</a>, <a href="mailto:ghost@aladdin.com">Deutsch, L.</a>, and <a href="mailto:randeg@alumni.rpi.edu">G. Randers-Pehrson</a>, “<a href="http://tools.ietf.org/html/rfc1952">GZIP file format specification version 4.3</a>”, RFC 1952, May 1996.<br>RFC 1952 is an Informational RFC, thus it might be less stable than this specification. On the other hand, this downward reference 1527 was present since the publication of RFC 2068 in 1997 (<a href="#RFC2068" id="rfc.xref.RFC2068.3"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a>), therefore it is unlikely to cause problems in practice. See also <a href="#BCP97" id="rfc.xref.BCP97.3"><cite title="Handling Normative References to Standards-Track Documents">[BCP97]</cite></a>.1527 was present since the publication of <cite title="Hypertext Transfer Protocol -- HTTP/1.1" id="rfc.xref.RFC2068.3">RFC 2068</cite> in 1997, therefore it is unlikely to cause problems in practice. See also <a href="#BCP97" id="rfc.xref.BCP97.3"><cite title="Handling Normative References to Standards-Track Documents">[BCP97]</cite></a>. 1528 1528 </td> 1529 1529 </tr> -
draft-ietf-httpbis/latest/p3-payload.xml
r1410 r1414 1868 1868 RFC 1950 is an Informational RFC, thus it might be less stable than 1869 1869 this specification. On the other hand, this downward reference was 1870 present since the publication of RFC 2068 in 1997 (<xref target="RFC2068"/>),1870 present since the publication of <xref target="RFC2068" x:fmt="none">RFC 2068</xref> in 1997, 1871 1871 therefore it is unlikely to cause problems in practice. See also 1872 1872 <xref target="BCP97"/>. … … 1887 1887 RFC 1951 is an Informational RFC, thus it might be less stable than 1888 1888 this specification. On the other hand, this downward reference was 1889 present since the publication of RFC 2068 in 1997 (<xref target="RFC2068"/>),1889 present since the publication of <xref target="RFC2068" x:fmt="none">RFC 2068</xref> in 1997, 1890 1890 therefore it is unlikely to cause problems in practice. See also 1891 1891 <xref target="BCP97"/>. … … 1918 1918 RFC 1952 is an Informational RFC, thus it might be less stable than 1919 1919 this specification. On the other hand, this downward reference was 1920 present since the publication of RFC 2068 in 1997 (<xref target="RFC2068"/>),1920 present since the publication of <xref target="RFC2068" x:fmt="none">RFC 2068</xref> in 1997, 1921 1921 therefore it is unlikely to cause problems in practice. See also 1922 1922 <xref target="BCP97"/>.
Note: See TracChangeset
for help on using the changeset viewer.
