Changeset 446 for draft-ietf-httpbis/latest
- Timestamp:
- 20/02/09 14:59:11 (13 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 15 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/Makefile
r425 r446 1 xml2rfc = " $(HOME)/bin/xml2rfc-1.33/xml2rfc.tcl"1 xml2rfc = "../../xml2rfc/xml2rfc.tcl" 2 2 saxpath = "$(HOME)/java/saxon-8-9-j/saxon8.jar" 3 3 saxon = java -classpath $(saxpath) net.sf.saxon.Transform -novw -l -
draft-ietf-httpbis/latest/p1-messaging.html
r443 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 } … … 382 365 <link rel="Appendix" title="D Collected ABNF" href="#rfc.section.D"> 383 366 <link rel="Appendix" title="E Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.E"> 384 <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/">367 <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/"> 385 368 <link rel="schema.DC" href="http://purl.org/dc/elements/1.1/"> 386 369 <meta name="DC.Creator" content="Fielding, R."> … … 478 461 <tr> 479 462 <td class="header left"></td> 480 <td class="header right">February 2 , 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 1: URIs, Connections, and Message Parsing<br><span class="filename">draft-ietf-httpbis-p1-messaging-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 … … 662 654 </ul> 663 655 </li> 664 <li class="tocline0"><a href="#rfc.ipr">Intellectual Property and Copyright Statements</a></li>665 656 <li class="tocline0"><a href="#rfc.index">Index</a></li> 666 657 </ul> … … 2168 2159 <tr> 2169 2160 <td class="reference"><b id="ISO-8859-1">[ISO-8859-1]</b></td> 2170 <td class="top">International Organization for Standardization, “ 2171 Information technology -- 8-bit single-byte coded graphic character sets -- Part 1: Latin alphabet No. 1 2172 ”, ISO/IEC 8859-1:1998, 1998. 2173 </td> 2161 <td class="top">International Organization for Standardization, “Information technology -- 8-bit single-byte coded graphic character sets -- Part 1: Latin alphabet No. 1”, ISO/IEC 8859-1:1998, 1998.</td> 2174 2162 </tr> 2175 2163 <tr> … … 2994 2982 <li>Rewrite introduction; add mostly new Architecture Section.</li> 2995 2983 </ul> 2996 <h1><a id="rfc.copyright" href="#rfc.copyright">Full Copyright Statement</a></h1>2997 <p>This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the2998 authors retain all their rights.2999 </p>3000 <p>This document and the information contained herein are provided on an “AS IS” basis and THE CONTRIBUTOR, THE ORGANIZATION3001 HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE3002 DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN3003 WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.3004 </p>3005 <h1><a id="rfc.ipr" href="#rfc.ipr">Intellectual Property</a></h1>3006 <p>The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might3007 be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any3008 license under such rights might or might not be available; nor does it represent that it has made any independent effort to3009 identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and3010 BCP 79.3011 </p>3012 <p>Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result3013 of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users3014 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>>.3015 </p>3016 <p>The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary3017 rights that may cover technology that may be required to implement this standard. Please address the information to the IETF3018 at <a href="mailto:ietf-ipr@ietf.org">ietf-ipr@ietf.org</a>.3019 </p>3020 2984 <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1> 3021 2985 <p class="noprint"><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.G">G</a> <a href="#rfc.index.H">H</a> <a href="#rfc.index.I">I</a> <a href="#rfc.index.K">K</a> <a href="#rfc.index.M">M</a> <a href="#rfc.index.N">N</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> <a href="#rfc.index.V">V</a> <a href="#rfc.index.W">W</a> -
draft-ietf-httpbis/latest/p1-messaging.xml
r443 r446 52 52 <?rfc-ext include-references-in-index="yes" ?> 53 53 <rfc obsoletes="2616" category="std" x:maturity-level="draft" 54 ipr=" full3978" docName="draft-ietf-httpbis-p1-messaging-&ID-VERSION;"54 ipr="pre5378Trust200902" docName="draft-ietf-httpbis-p1-messaging-&ID-VERSION;" 55 55 xmlns:x='http://purl.org/net/xml2rfc/ext'> 56 56 <front> -
draft-ietf-httpbis/latest/p2-semantics.html
r443 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 2 , 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> -
draft-ietf-httpbis/latest/p2-semantics.xml
r443 r446 75 75 <?rfc-ext include-references-in-index="yes" ?> 76 76 <rfc obsoletes="2616" updates="2817" category="std" x:maturity-level="draft" 77 ipr=" full3978" docName="draft-ietf-httpbis-p2-semantics-&ID-VERSION;"77 ipr="pre5378Trust200902" docName="draft-ietf-httpbis-p2-semantics-&ID-VERSION;" 78 78 xmlns:x='http://purl.org/net/xml2rfc/ext' 79 79 xmlns:rdf='http://www.w3.org/1999/02/22-rdf-syntax-ns#'> -
draft-ietf-httpbis/latest/p3-payload.html
r443 r446 69 69 page-break-after: avoid; 70 70 } 71 h2 a { 72 color: black; 73 } 74 h3 { 71 h3, h4, h5, h6 { 75 72 font-size: 10pt; 76 73 page-break-after: avoid; 77 74 } 78 h3 a { 79 color: black; 80 } 81 h4 { 82 font-size: 10pt; 83 page-break-after: avoid; 84 } 85 h4 a { 86 color: black; 87 } 88 h5 { 89 font-size: 10pt; 90 page-break-after: avoid; 91 } 92 h5 a { 75 h2 a, h3 a, h4 a, h5 a, h6 a { 93 76 color: black; 94 77 } … … 389 372 <link rel="Appendix" title="D Collected ABNF" href="#rfc.section.D"> 390 373 <link rel="Appendix" title="E Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.E"> 391 <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/">374 <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/"> 392 375 <link rel="schema.DC" href="http://purl.org/dc/elements/1.1/"> 393 376 <meta name="DC.Creator" content="Fielding, R."> … … 485 468 <tr> 486 469 <td class="header left"></td> 487 <td class="header right">February 2 , 2009</td>470 <td class="header right">February 20, 2009</td> 488 471 </tr> 489 472 </table> 490 473 <p class="title">HTTP/1.1, part 3: Message Payload and Content Negotiation<br><span class="filename">draft-ietf-httpbis-p3-payload-latest</span></p> 491 474 <h1><a id="rfc.status" href="#rfc.status">Status of this Memo</a></h1> 492 <p>By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she 493 is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section 494 6 of BCP 79. 475 <p>This Internet-Draft is submitted to IETF pursuant to, and in full conformance with, the provisions of BCP 78 and BCP 79. This 476 document may contain material from IETF Documents or IETF Contributions published or made publicly available before November 477 10, 2008. The person(s) controlling the copyright in some of this material may not have granted the IETF Trust the right to 478 allow modifications of such material outside the IETF Standards Process. Without obtaining an adequate license from the person(s) 479 controlling the copyright in such materials, this document may not be modified outside the IETF Standards Process, and derivative 480 works of it may not be created outside the IETF Standards Process, except to format it for publication as an RFC or to translate 481 it into languages other than English. 495 482 </p> 496 483 <p>Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note … … 506 493 </p> 507 494 <p>This Internet-Draft will expire in August 2009.</p> 495 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 496 <p>Copyright © 2009 IETF Trust and the persons identified as the document authors. All rights reserved.</p> 497 <p>This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents in effect on the date 498 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. 499 </p> 508 500 <h1 id="rfc.abstract"><a href="#rfc.abstract">Abstract</a></h1> 509 501 <p>The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information … … 618 610 </ul> 619 611 </li> 620 <li class="tocline0"><a href="#rfc.ipr">Intellectual Property and Copyright Statements</a></li>621 612 <li class="tocline0"><a href="#rfc.index">Index</a></li> 622 613 </ul> … … 1411 1402 <tr> 1412 1403 <td class="reference"><b id="ISO-8859-1">[ISO-8859-1]</b></td> 1413 <td class="top">International Organization for Standardization, “ 1414 Information technology -- 8-bit single-byte coded graphic character sets -- Part 1: Latin alphabet No. 1 1415 ”, ISO/IEC 8859-1:1998, 1998. 1416 </td> 1404 <td class="top">International Organization for Standardization, “Information technology -- 8-bit single-byte coded graphic character sets -- Part 1: Latin alphabet No. 1”, ISO/IEC 8859-1:1998, 1998.</td> 1417 1405 </tr> 1418 1406 <tr> … … 1535 1523 <tr> 1536 1524 <td class="reference"><b id="RFC2388">[RFC2388]</b></td> 1537 <td class="top"><a title="Xerox Palo Alto Research Center">Masinter, L.</a>, “<a href="http://tools.ietf.org/html/rfc2388">Returning Values from Forms: 1525 <td class="top"><a title="Xerox Palo Alto Research Center">Masinter, L.</a>, “<a href="http://tools.ietf.org/html/rfc2388">Returning Values from Forms: multipart/form-data</a>”, RFC 2388, August 1998. 1538 1526 </td> 1539 1527 </tr> … … 1893 1881 <li>Add appendix containing collected and expanded ABNF, reorganize ABNF introduction.</li> 1894 1882 </ul> 1895 <h1><a id="rfc.copyright" href="#rfc.copyright">Full Copyright Statement</a></h1>1896 <p>This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the1897 authors retain all their rights.1898 </p>1899 <p>This document and the information contained herein are provided on an “AS IS” basis and THE CONTRIBUTOR, THE ORGANIZATION1900 HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE1901 DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN1902 WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.1903 </p>1904 <h1><a id="rfc.ipr" href="#rfc.ipr">Intellectual Property</a></h1>1905 <p>The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might1906 be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any1907 license under such rights might or might not be available; nor does it represent that it has made any independent effort to1908 identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and1909 BCP 79.1910 </p>1911 <p>Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result1912 of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users1913 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>>.1914 </p>1915 <p>The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary1916 rights that may cover technology that may be required to implement this standard. Please address the information to the IETF1917 at <a href="mailto:ietf-ipr@ietf.org">ietf-ipr@ietf.org</a>.1918 </p>1919 1883 <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1> 1920 1884 <p class="noprint"><a href="#rfc.index.A">A</a> <a href="#rfc.index.B">B</a> <a href="#rfc.index.C">C</a> <a href="#rfc.index.D">D</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.P">P</a> <a href="#rfc.index.R">R</a> <a href="#rfc.index.U">U</a> -
draft-ietf-httpbis/latest/p3-payload.xml
r443 r446 45 45 <?rfc-ext include-references-in-index="yes" ?> 46 46 <rfc obsoletes="2616" category="std" x:maturity-level="draft" 47 ipr=" full3978" docName="draft-ietf-httpbis-p3-payload-&ID-VERSION;"47 ipr="pre5378Trust200902" docName="draft-ietf-httpbis-p3-payload-&ID-VERSION;" 48 48 xmlns:x='http://purl.org/net/xml2rfc/ext'> 49 49 <front> -
draft-ietf-httpbis/latest/p4-conditional.html
r443 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 } … … 378 361 <link rel="Appendix" title="B Collected ABNF" href="#rfc.section.B"> 379 362 <link rel="Appendix" title="C Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.C"> 380 <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/">363 <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/"> 381 364 <link rel="schema.DC" href="http://purl.org/dc/elements/1.1/"> 382 365 <meta name="DC.Creator" content="Fielding, R."> … … 474 457 <tr> 475 458 <td class="header left"></td> 476 <td class="header right">February 2 , 2009</td>459 <td class="header right">February 20, 2009</td> 477 460 </tr> 478 461 </table> 479 462 <p class="title">HTTP/1.1, part 4: Conditional Requests<br><span class="filename">draft-ietf-httpbis-p4-conditional-latest</span></p> 480 463 <h1><a id="rfc.status" href="#rfc.status">Status of this Memo</a></h1> 481 <p>By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she 482 is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section 483 6 of BCP 79. 464 <p>This Internet-Draft is submitted to IETF pursuant to, and in full conformance with, the provisions of BCP 78 and BCP 79. This 465 document may contain material from IETF Documents or IETF Contributions published or made publicly available before November 466 10, 2008. The person(s) controlling the copyright in some of this material may not have granted the IETF Trust the right to 467 allow modifications of such material outside the IETF Standards Process. Without obtaining an adequate license from the person(s) 468 controlling the copyright in such materials, this document may not be modified outside the IETF Standards Process, and derivative 469 works of it may not be created outside the IETF Standards Process, except to format it for publication as an RFC or to translate 470 it into languages other than English. 484 471 </p> 485 472 <p>Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note … … 495 482 </p> 496 483 <p>This Internet-Draft will expire in August 2009.</p> 484 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 485 <p>Copyright © 2009 IETF Trust and the persons identified as the document authors. All rights reserved.</p> 486 <p>This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents in effect on the date 487 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. 488 </p> 497 489 <h1 id="rfc.abstract"><a href="#rfc.abstract">Abstract</a></h1> 498 490 <p>The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information … … 563 555 </ul> 564 556 </li> 565 <li class="tocline0"><a href="#rfc.ipr">Intellectual Property and Copyright Statements</a></li>566 557 <li class="tocline0"><a href="#rfc.index">Index</a></li> 567 558 </ul> … … 1250 1241 <li>Add appendix containing collected and expanded ABNF, reorganize ABNF introduction.</li> 1251 1242 </ul> 1252 <h1><a id="rfc.copyright" href="#rfc.copyright">Full Copyright Statement</a></h1>1253 <p>This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the1254 authors retain all their rights.1255 </p>1256 <p>This document and the information contained herein are provided on an “AS IS” basis and THE CONTRIBUTOR, THE ORGANIZATION1257 HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE1258 DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN1259 WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.1260 </p>1261 <h1><a id="rfc.ipr" href="#rfc.ipr">Intellectual Property</a></h1>1262 <p>The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might1263 be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any1264 license under such rights might or might not be available; nor does it represent that it has made any independent effort to1265 identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and1266 BCP 79.1267 </p>1268 <p>Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result1269 of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users1270 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>>.1271 </p>1272 <p>The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary1273 rights that may cover technology that may be required to implement this standard. Please address the information to the IETF1274 at <a href="mailto:ietf-ipr@ietf.org">ietf-ipr@ietf.org</a>.1275 </p>1276 1243 <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1> 1277 1244 <p class="noprint"><a href="#rfc.index.3">3</a> <a href="#rfc.index.4">4</a> <a href="#rfc.index.E">E</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.P">P</a> <a href="#rfc.index.R">R</a> <a href="#rfc.index.S">S</a> -
draft-ietf-httpbis/latest/p4-conditional.xml
r443 r446 39 39 <?rfc-ext include-references-in-index="yes" ?> 40 40 <rfc obsoletes="2616" category="std" x:maturity-level="draft" 41 ipr=" full3978" docName="draft-ietf-httpbis-p4-conditional-&ID-VERSION;"41 ipr="pre5378Trust200902" docName="draft-ietf-httpbis-p4-conditional-&ID-VERSION;" 42 42 xmlns:x='http://purl.org/net/xml2rfc/ext'> 43 43 <front> -
draft-ietf-httpbis/latest/p5-range.html
r443 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 } … … 378 361 <link rel="Appendix" title="C Collected ABNF" href="#rfc.section.C"> 379 362 <link rel="Appendix" title="D Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.D"> 380 <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/">363 <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/"> 381 364 <link rel="schema.DC" href="http://purl.org/dc/elements/1.1/"> 382 365 <meta name="DC.Creator" content="Fielding, R."> … … 474 457 <tr> 475 458 <td class="header left"></td> 476 <td class="header right">February 2 , 2009</td>459 <td class="header right">February 20, 2009</td> 477 460 </tr> 478 461 </table> 479 462 <p class="title">HTTP/1.1, part 5: Range Requests and Partial Responses<br><span class="filename">draft-ietf-httpbis-p5-range-latest</span></p> 480 463 <h1><a id="rfc.status" href="#rfc.status">Status of this Memo</a></h1> 481 <p>By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she 482 is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section 483 6 of BCP 79. 464 <p>This Internet-Draft is submitted to IETF pursuant to, and in full conformance with, the provisions of BCP 78 and BCP 79. This 465 document may contain material from IETF Documents or IETF Contributions published or made publicly available before November 466 10, 2008. The person(s) controlling the copyright in some of this material may not have granted the IETF Trust the right to 467 allow modifications of such material outside the IETF Standards Process. Without obtaining an adequate license from the person(s) 468 controlling the copyright in such materials, this document may not be modified outside the IETF Standards Process, and derivative 469 works of it may not be created outside the IETF Standards Process, except to format it for publication as an RFC or to translate 470 it into languages other than English. 484 471 </p> 485 472 <p>Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note … … 495 482 </p> 496 483 <p>This Internet-Draft will expire in August 2009.</p> 484 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 485 <p>Copyright © 2009 IETF Trust and the persons identified as the document authors. All rights reserved.</p> 486 <p>This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents in effect on the date 487 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. 488 </p> 497 489 <h1 id="rfc.abstract"><a href="#rfc.abstract">Abstract</a></h1> 498 490 <p>The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information … … 566 558 </ul> 567 559 </li> 568 <li class="tocline0"><a href="#rfc.ipr">Intellectual Property and Copyright Statements</a></li>569 560 <li class="tocline0"><a href="#rfc.index">Index</a></li> 570 561 </ul> … … 1212 1203 <li>Add appendix containing collected and expanded ABNF, reorganize ABNF introduction.</li> 1213 1204 </ul> 1214 <h1><a id="rfc.copyright" href="#rfc.copyright">Full Copyright Statement</a></h1>1215 <p>This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the1216 authors retain all their rights.1217 </p>1218 <p>This document and the information contained herein are provided on an “AS IS” basis and THE CONTRIBUTOR, THE ORGANIZATION1219 HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE1220 DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN1221 WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.1222 </p>1223 <h1><a id="rfc.ipr" href="#rfc.ipr">Intellectual Property</a></h1>1224 <p>The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might1225 be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any1226 license under such rights might or might not be available; nor does it represent that it has made any independent effort to1227 identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and1228 BCP 79.1229 </p>1230 <p>Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result1231 of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users1232 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>>.1233 </p>1234 <p>The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary1235 rights that may cover technology that may be required to implement this standard. Please address the information to the IETF1236 at <a href="mailto:ietf-ipr@ietf.org">ietf-ipr@ietf.org</a>.1237 </p>1238 1205 <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1> 1239 1206 <p class="noprint"><a href="#rfc.index.2">2</a> <a href="#rfc.index.4">4</a> <a href="#rfc.index.A">A</a> <a href="#rfc.index.C">C</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.M">M</a> <a href="#rfc.index.P">P</a> <a href="#rfc.index.R">R</a> <a href="#rfc.index.S">S</a> -
draft-ietf-httpbis/latest/p5-range.xml
r443 r446 35 35 <?rfc-ext include-references-in-index="yes" ?> 36 36 <rfc obsoletes="2616" category="std" x:maturity-level="draft" 37 ipr=" full3978" docName="draft-ietf-httpbis-p5-range-&ID-VERSION;"37 ipr="pre5378Trust200902" docName="draft-ietf-httpbis-p5-range-&ID-VERSION;" 38 38 xmlns:x='http://purl.org/net/xml2rfc/ext'> 39 39 <front> -
draft-ietf-httpbis/latest/p6-cache.html
r444 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 } … … 390 373 <link rel="Appendix" title="B Collected ABNF" href="#rfc.section.B"> 391 374 <link rel="Appendix" title="C Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.C"> 392 <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/">375 <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/"> 393 376 <link rel="schema.DC" href="http://purl.org/dc/elements/1.1/"> 394 377 <meta name="DC.Creator" content="Fielding, R."> … … 486 469 <tr> 487 470 <td class="header left"></td> 488 <td class="header right">February 3, 2009</td>471 <td class="header right">February 20, 2009</td> 489 472 </tr> 490 473 </table> 491 474 <p class="title">HTTP/1.1, part 6: Caching<br><span class="filename">draft-ietf-httpbis-p6-cache-latest</span></p> 492 475 <h1><a id="rfc.status" href="#rfc.status">Status of this Memo</a></h1> 493 <p>By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she 494 is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section 495 6 of BCP 79. 476 <p>This Internet-Draft is submitted to IETF pursuant to, and in full conformance with, the provisions of BCP 78 and BCP 79. This 477 document may contain material from IETF Documents or IETF Contributions published or made publicly available before November 478 10, 2008. The person(s) controlling the copyright in some of this material may not have granted the IETF Trust the right to 479 allow modifications of such material outside the IETF Standards Process. Without obtaining an adequate license from the person(s) 480 controlling the copyright in such materials, this document may not be modified outside the IETF Standards Process, and derivative 481 works of it may not be created outside the IETF Standards Process, except to format it for publication as an RFC or to translate 482 it into languages other than English. 496 483 </p> 497 484 <p>Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note … … 507 494 </p> 508 495 <p>This Internet-Draft will expire in August 2009.</p> 496 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 497 <p>Copyright © 2009 IETF Trust and the persons identified as the document authors. All rights reserved.</p> 498 <p>This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents in effect on the date 499 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. 500 </p> 509 501 <h1 id="rfc.abstract"><a href="#rfc.abstract">Abstract</a></h1> 510 502 <p>The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information … … 613 605 </ul> 614 606 </li> 615 <li class="tocline0"><a href="#rfc.ipr">Intellectual Property and Copyright Statements</a></li>616 607 <li class="tocline0"><a href="#rfc.index">Index</a></li> 617 608 </ul> … … 1827 1818 <tr> 1828 1819 <td class="reference"><b id="ISO-8859-1">[ISO-8859-1]</b></td> 1829 <td class="top">International Organization for Standardization, “ 1830 Information technology -- 8-bit single-byte coded graphic character sets -- Part 1: Latin alphabet No. 1 1831 ”, ISO/IEC 8859-1:1998, 1998. 1832 </td> 1820 <td class="top">International Organization for Standardization, “Information technology -- 8-bit single-byte coded graphic character sets -- Part 1: Latin alphabet No. 1”, ISO/IEC 8859-1:1998, 1998.</td> 1833 1821 </tr> 1834 1822 <tr> … … 2076 2064 <li>Add appendix containing collected and expanded ABNF, reorganize ABNF introduction.</li> 2077 2065 </ul> 2078 <h1><a id="rfc.copyright" href="#rfc.copyright">Full Copyright Statement</a></h1>2079 <p>This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the2080 authors retain all their rights.2081 </p>2082 <p>This document and the information contained herein are provided on an “AS IS” basis and THE CONTRIBUTOR, THE ORGANIZATION2083 HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE2084 DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN2085 WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.2086 </p>2087 <h1><a id="rfc.ipr" href="#rfc.ipr">Intellectual Property</a></h1>2088 <p>The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might2089 be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any2090 license under such rights might or might not be available; nor does it represent that it has made any independent effort to2091 identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and2092 BCP 79.2093 </p>2094 <p>Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result2095 of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users2096 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>>.2097 </p>2098 <p>The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary2099 rights that may cover technology that may be required to implement this standard. Please address the information to the IETF2100 at <a href="mailto:ietf-ipr@ietf.org">ietf-ipr@ietf.org</a>.2101 </p>2102 2066 <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1> 2103 2067 <p class="noprint"><a href="#rfc.index.A">A</a> <a href="#rfc.index.C">C</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.M">M</a> <a href="#rfc.index.N">N</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.V">V</a> <a href="#rfc.index.W">W</a> -
draft-ietf-httpbis/latest/p6-cache.xml
r444 r446 45 45 <?rfc-ext include-references-in-index="yes" ?> 46 46 <rfc obsoletes="2616" category="std" x:maturity-level="draft" 47 ipr=" full3978" docName="draft-ietf-httpbis-p6-cache-&ID-VERSION;"47 ipr="pre5378Trust200902" docName="draft-ietf-httpbis-p6-cache-&ID-VERSION;" 48 48 xmlns:x='http://purl.org/net/xml2rfc/ext'> 49 49 <front> -
draft-ietf-httpbis/latest/p7-auth.html
r443 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 } … … 375 358 <link rel="Appendix" title="B Collected ABNF" href="#rfc.section.B"> 376 359 <link rel="Appendix" title="C Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.C"> 377 <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/">360 <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/"> 378 361 <link rel="schema.DC" href="http://purl.org/dc/elements/1.1/"> 379 362 <meta name="DC.Creator" content="Fielding, R."> … … 472 455 <tr> 473 456 <td class="header left"></td> 474 <td class="header right">February 2 , 2009</td>457 <td class="header right">February 20, 2009</td> 475 458 </tr> 476 459 </table> 477 460 <p class="title">HTTP/1.1, part 7: Authentication<br><span class="filename">draft-ietf-httpbis-p7-auth-latest</span></p> 478 461 <h1><a id="rfc.status" href="#rfc.status">Status of this Memo</a></h1> 479 <p>By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she 480 is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section 481 6 of BCP 79. 462 <p>This Internet-Draft is submitted to IETF pursuant to, and in full conformance with, the provisions of BCP 78 and BCP 79. This 463 document may contain material from IETF Documents or IETF Contributions published or made publicly available before November 464 10, 2008. The person(s) controlling the copyright in some of this material may not have granted the IETF Trust the right to 465 allow modifications of such material outside the IETF Standards Process. Without obtaining an adequate license from the person(s) 466 controlling the copyright in such materials, this document may not be modified outside the IETF Standards Process, and derivative 467 works of it may not be created outside the IETF Standards Process, except to format it for publication as an RFC or to translate 468 it into languages other than English. 482 469 </p> 483 470 <p>Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note … … 493 480 </p> 494 481 <p>This Internet-Draft will expire in August 2009.</p> 482 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 483 <p>Copyright © 2009 IETF Trust and the persons identified as the document authors. All rights reserved.</p> 484 <p>This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents in effect on the date 485 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. 486 </p> 495 487 <h1 id="rfc.abstract"><a href="#rfc.abstract">Abstract</a></h1> 496 488 <p>The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information … … 559 551 </ul> 560 552 </li> 561 <li class="tocline0"><a href="#rfc.ipr">Intellectual Property and Copyright Statements</a></li>562 553 <li class="tocline0"><a href="#rfc.index">Index</a></li> 563 554 </ul> … … 878 869 <li>Add appendix containing collected and expanded ABNF, reorganize ABNF introduction.</li> 879 870 </ul> 880 <h1><a id="rfc.copyright" href="#rfc.copyright">Full Copyright Statement</a></h1>881 <p>This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the882 authors retain all their rights.883 </p>884 <p>This document and the information contained herein are provided on an “AS IS” basis and THE CONTRIBUTOR, THE ORGANIZATION885 HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE886 DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN887 WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.888 </p>889 <h1><a id="rfc.ipr" href="#rfc.ipr">Intellectual Property</a></h1>890 <p>The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might891 be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any892 license under such rights might or might not be available; nor does it represent that it has made any independent effort to893 identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and894 BCP 79.895 </p>896 <p>Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result897 of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users898 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>>.899 </p>900 <p>The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary901 rights that may cover technology that may be required to implement this standard. Please address the information to the IETF902 at <a href="mailto:ietf-ipr@ietf.org">ietf-ipr@ietf.org</a>.903 </p>904 871 <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1> 905 872 <p class="noprint"><a href="#rfc.index.4">4</a> <a href="#rfc.index.A">A</a> <a href="#rfc.index.G">G</a> <a href="#rfc.index.H">H</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.W">W</a> -
draft-ietf-httpbis/latest/p7-auth.xml
r443 r446 32 32 <?rfc-ext include-references-in-index="yes" ?> 33 33 <rfc obsoletes="2616" updates="2617" category="std" x:maturity-level="draft" 34 ipr=" full3978" docName="draft-ietf-httpbis-p7-auth-&ID-VERSION;"34 ipr="pre5378Trust200902" docName="draft-ietf-httpbis-p7-auth-&ID-VERSION;" 35 35 xmlns:x='http://purl.org/net/xml2rfc/ext'> 36 36 <front>
Note: See TracChangeset
for help on using the changeset viewer.