Changeset 446 for draft-ietf-httpbis/latest-roy/p2-semantics.html
- Timestamp:
- 20/02/09 14:59:11 (14 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest-roy/p2-semantics.html
r445 r446 62 62 page-break-after: avoid; 63 63 } 64 h2 a { 65 color: black; 66 } 67 h3 { 64 h3, h4, h5, h6 { 68 65 font-size: 10pt; 69 66 page-break-after: avoid; 70 67 } 71 h3 a { 72 color: black; 73 } 74 h4 { 75 font-size: 10pt; 76 page-break-after: avoid; 77 } 78 h4 a { 79 color: black; 80 } 81 h5 { 82 font-size: 10pt; 83 page-break-after: avoid; 84 } 85 h5 a { 68 h2 a, h3 a, h4 a, h5 a, h6 a { 86 69 color: black; 87 70 } … … 381 364 <link rel="Appendix" title="B Collected ABNF" href="#rfc.section.B"> 382 365 <link rel="Appendix" title="C Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.C"> 383 <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.4 15, 2009-01-29 15:06:08, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">366 <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.421, 2009-02-20 13:12:03, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/"> 384 367 <link rel="schema.DC" href="http://purl.org/dc/elements/1.1/"> 385 368 <meta name="DC.Creator" content="Fielding, R."> … … 478 461 <tr> 479 462 <td class="header left"></td> 480 <td class="header right">February 3, 2009</td>463 <td class="header right">February 20, 2009</td> 481 464 </tr> 482 465 </table> 483 466 <p class="title">HTTP/1.1, part 2: Message Semantics<br><span class="filename">draft-ietf-httpbis-p2-semantics-latest</span></p> 484 467 <h1><a id="rfc.status" href="#rfc.status">Status of this Memo</a></h1> 485 <p>By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she 486 is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section 487 6 of BCP 79. 468 <p>This Internet-Draft is submitted to IETF pursuant to, and in full conformance with, the provisions of BCP 78 and BCP 79. This 469 document may contain material from IETF Documents or IETF Contributions published or made publicly available before November 470 10, 2008. The person(s) controlling the copyright in some of this material may not have granted the IETF Trust the right to 471 allow modifications of such material outside the IETF Standards Process. Without obtaining an adequate license from the person(s) 472 controlling the copyright in such materials, this document may not be modified outside the IETF Standards Process, and derivative 473 works of it may not be created outside the IETF Standards Process, except to format it for publication as an RFC or to translate 474 it into languages other than English. 488 475 </p> 489 476 <p>Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note … … 499 486 </p> 500 487 <p>This Internet-Draft will expire in August 2009.</p> 488 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 489 <p>Copyright © 2009 IETF Trust and the persons identified as the document authors. All rights reserved.</p> 490 <p>This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents in effect on the date 491 of publication of this document (<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>). Please review these documents carefully, as they describe your rights and restrictions with respect to this document. 492 </p> 501 493 <h1 id="rfc.abstract"><a href="#rfc.abstract">Abstract</a></h1> 502 494 <p>The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information … … 657 649 </ul> 658 650 </li> 659 <li class="tocline0"><a href="#rfc.ipr">Intellectual Property and Copyright Statements</a></li>660 651 <li class="tocline0"><a href="#rfc.index">Index</a></li> 661 652 </ul> … … 2475 2466 <li>Add appendix containing collected and expanded ABNF, reorganize ABNF introduction.</li> 2476 2467 </ul> 2477 <h1><a id="rfc.copyright" href="#rfc.copyright">Full Copyright Statement</a></h1>2478 <p>This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the2479 authors retain all their rights.2480 </p>2481 <p>This document and the information contained herein are provided on an “AS IS” basis and THE CONTRIBUTOR, THE ORGANIZATION2482 HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE2483 DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN2484 WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.2485 </p>2486 <h1><a id="rfc.ipr" href="#rfc.ipr">Intellectual Property</a></h1>2487 <p>The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might2488 be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any2489 license under such rights might or might not be available; nor does it represent that it has made any independent effort to2490 identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and2491 BCP 79.2492 </p>2493 <p>Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result2494 of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users2495 of this specification can be obtained from the IETF on-line IPR repository at <<a href="http://www.ietf.org/ipr">http://www.ietf.org/ipr</a>>.2496 </p>2497 <p>The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary2498 rights that may cover technology that may be required to implement this standard. Please address the information to the IETF2499 at <a href="mailto:ietf-ipr@ietf.org">ietf-ipr@ietf.org</a>.2500 </p>2501 2468 <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1> 2502 2469 <p class="noprint"><a href="#rfc.index.1">1</a> <a href="#rfc.index.2">2</a> <a href="#rfc.index.3">3</a> <a href="#rfc.index.4">4</a> <a href="#rfc.index.5">5</a> <a href="#rfc.index.A">A</a> <a href="#rfc.index.C">C</a> <a href="#rfc.index.D">D</a> <a href="#rfc.index.E">E</a> <a href="#rfc.index.F">F</a> <a href="#rfc.index.G">G</a> <a href="#rfc.index.H">H</a> <a href="#rfc.index.I">I</a> <a href="#rfc.index.L">L</a> <a href="#rfc.index.M">M</a> <a href="#rfc.index.O">O</a> <a href="#rfc.index.P">P</a> <a href="#rfc.index.R">R</a> <a href="#rfc.index.S">S</a> <a href="#rfc.index.T">T</a> <a href="#rfc.index.U">U</a>
Note: See TracChangeset
for help on using the changeset viewer.