Changeset 2198 for draft-ietf-httpbis
- Timestamp:
- 07/03/13 13:50:06 (10 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p1-messaging.html
r2197 r2198 449 449 } 450 450 @bottom-center { 451 content: "Expires September 4, 2013";451 content: "Expires September 8, 2013"; 452 452 } 453 453 @bottom-right { … … 491 491 <meta name="dct.creator" content="Reschke, J. F."> 492 492 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p1-messaging-latest"> 493 <meta name="dct.issued" scheme="ISO8601" content="2013-03-0 3">493 <meta name="dct.issued" scheme="ISO8601" content="2013-03-07"> 494 494 <meta name="dct.replaces" content="urn:ietf:rfc:2145"> 495 495 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> … … 520 520 <tr> 521 521 <td class="left">Intended status: Standards Track</td> 522 <td class="right">March 3, 2013</td>522 <td class="right">March 7, 2013</td> 523 523 </tr> 524 524 <tr> 525 <td class="left">Expires: September 4, 2013</td>525 <td class="left">Expires: September 8, 2013</td> 526 526 <td class="right"></td> 527 527 </tr> … … 551 551 in progress”. 552 552 </p> 553 <p>This Internet-Draft will expire on September 4, 2013.</p>553 <p>This Internet-Draft will expire on September 8, 2013.</p> 554 554 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 555 555 <p>Copyright © 2013 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 1038 1038 <div id="rfc.iref.u.3"></div> 1039 1039 <p id="rfc.section.2.7.1.p.1">The "http" URI scheme is hereby defined for the purpose of minting identifiers according to their association with the hierarchical 1040 namespace governed by a potential HTTP origin server listening for TCP connections on a given port.1040 namespace governed by a potential HTTP origin server listening for TCP (<a href="#RFC0793" id="rfc.xref.RFC0793.1"><cite title="Transmission Control Protocol">[RFC0793]</cite></a>) connections on a given port. 1041 1041 </p> 1042 1042 <div id="rfc.figure.u.8"></div><pre class="inline"><span id="rfc.iref.g.25"></span> <a href="#http.uri" class="smpl">http-URI</a> = "http:" "//" <a href="#uri" class="smpl">authority</a> <a href="#uri" class="smpl">path-abempty</a> [ "?" <a href="#uri" class="smpl">query</a> ] … … 1074 1074 <div id="rfc.iref.u.4"></div> 1075 1075 <p id="rfc.section.2.7.2.p.1">The "https" URI scheme is hereby defined for the purpose of minting identifiers according to their association with the hierarchical 1076 namespace governed by a potential HTTP origin server listening to a given TCP port for TLS-secured connections <a href="#RFC5246" id="rfc.xref.RFC5246.2"><cite title="The Transport Layer Security (TLS) Protocol Version 1.2">[RFC5246]</cite></a>.1076 namespace governed by a potential HTTP origin server listening to a given TCP port for TLS-secured connections (<a href="#RFC0793" id="rfc.xref.RFC0793.2"><cite title="Transmission Control Protocol">[RFC0793]</cite></a>, <a href="#RFC5246" id="rfc.xref.RFC5246.2"><cite title="The Transport Layer Security (TLS) Protocol Version 1.2">[RFC5246]</cite></a>). 1077 1077 </p> 1078 1078 <p id="rfc.section.2.7.2.p.2">All of the requirements listed above for the "http" scheme are also requirements for the "https" scheme, except that a default … … 2600 2600 <h2 id="rfc.references.1"><a href="#rfc.section.10.1" id="rfc.section.10.1">10.1</a> Normative References 2601 2601 </h2> 2602 <table> 2602 <table> 2603 2603 <tr> 2604 2604 <td class="reference"><b id="Part2">[Part2]</b></td> … … 2624 2624 <td class="reference"><b id="Part7">[Part7]</b></td> 2625 2625 <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p7-auth-latest">Hypertext Transfer Protocol (HTTP/1.1): Authentication</a>”, Internet-Draft draft-ietf-httpbis-p7-auth-latest (work in progress), March 2013. 2626 </td> 2627 </tr> 2628 <tr> 2629 <td class="reference"><b id="RFC0793">[RFC0793]</b></td> 2630 <td class="top">Postel, J., “<a href="http://tools.ietf.org/html/rfc793">Transmission Control Protocol</a>”, STD 7, RFC 793, September 1981. 2626 2631 </td> 2627 2632 </tr> … … 3116 3121 </ul> 3117 3122 <h2 id="rfc.section.D.3"><a href="#rfc.section.D.3">D.3</a> <a id="changes.since.22" href="#changes.since.22">Since draft-ietf-httpbis-p1-messaging-22</a></h2> 3118 <p id="rfc.section.D.3.p.1">None yet.</p> 3123 <p id="rfc.section.D.3.p.1">Closed issues: </p> 3124 <ul> 3125 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/435">http://tools.ietf.org/wg/httpbis/trac/ticket/435</a>>: "Part1 should have a reference to TCP (RFC 793)" 3126 </li> 3127 </ul> 3119 3128 <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1> 3120 3129 <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.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> … … 3349 3358 <li>response <a href="#rfc.iref.r.3"><b>2.1</b></a></li> 3350 3359 <li>reverse proxy <a href="#rfc.iref.r.4"><b>2.3</b></a></li> 3360 <li><em>RFC0793</em> <a href="#rfc.xref.RFC0793.1">2.7.1</a>, <a href="#rfc.xref.RFC0793.2">2.7.2</a>, <a href="#RFC0793"><b>10.1</b></a></li> 3351 3361 <li><em>RFC1919</em> <a href="#rfc.xref.RFC1919.1">2.3</a>, <a href="#RFC1919"><b>10.2</b></a></li> 3352 3362 <li><em>RFC1945</em> <a href="#rfc.xref.RFC1945.1">2.6</a>, <a href="#rfc.xref.RFC1945.2">9</a>, <a href="#RFC1945"><b>10.2</b></a>, <a href="#rfc.xref.RFC1945.3">A</a></li> -
draft-ietf-httpbis/latest/p1-messaging.xml
r2197 r2198 830 830 identifiers according to their association with the hierarchical 831 831 namespace governed by a potential HTTP origin server listening for 832 TCP connections on a given port.832 TCP (<xref target="RFC0793"/>) connections on a given port. 833 833 </t> 834 834 <figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="http-URI"><!--terminal production--></iref> … … 913 913 identifiers according to their association with the hierarchical 914 914 namespace governed by a potential HTTP origin server listening to a 915 given TCP port for TLS-secured connections <xref target="RFC5246"/>. 915 given TCP port for TLS-secured connections 916 (<xref target="RFC0793"/>, <xref target="RFC5246"/>). 916 917 </t> 917 918 <t> … … 4154 4155 </reference> 4155 4156 4157 <reference anchor="RFC0793"> 4158 <front> 4159 <title>Transmission Control Protocol</title> 4160 <author initials='J.' surname='Postel' fullname='Jon Postel'> 4161 <organization>University of Southern California (USC)/Information Sciences Institute</organization> 4162 </author> 4163 <date year='1981' month='September' /> 4164 </front> 4165 <seriesInfo name='STD' value='7' /> 4166 <seriesInfo name='RFC' value='793' /> 4167 </reference> 4168 4156 4169 <reference anchor="USASCII"> 4157 4170 <front> … … 5227 5240 <section title="Since draft-ietf-httpbis-p1-messaging-22" anchor="changes.since.22"> 5228 5241 <t> 5229 None yet. 5242 Closed issues: 5243 <list style="symbols"> 5244 <t> 5245 <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/435"/>: 5246 "Part1 should have a reference to TCP (RFC 793)" 5247 </t> 5248 </list> 5230 5249 </t> 5231 5250 </section>
Note: See TracChangeset
for help on using the changeset viewer.