![(please configure the [header_logo] section in trac.ini)](https://www.ietf.org/images/ietflogotrans.gif)
Changeset 307 for draft-ietf-httpbis/latest
- Timestamp:
- Aug 6, 2008, 3:22:35 AM (11 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 2 edited
-
p1-messaging.html (modified) (12 diffs)
-
p1-messaging.xml (modified) (4 diffs)
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p1-messaging.html
r301 r307 476 476 <tr> 477 477 <td class="header left"></td> 478 <td class="header right">August 1, 2008</td>478 <td class="header right">August 6, 2008</td> 479 479 </tr> 480 480 </table> … … 608 608 <li class="tocline0">9. <a href="#IANA.considerations">IANA Considerations</a><ul class="toc"> 609 609 <li class="tocline1">9.1 <a href="#message.header.registration">Message Header Registration</a></li> 610 <li class="tocline1">9.2 <a href="#internet.media.type.http">Internet Media Type Registrations</a><ul class="toc"> 611 <li class="tocline1">9.2.1 <a href="#internet.media.type.message.http">Internet Media Type message/http</a></li> 612 <li class="tocline1">9.2.2 <a href="#internet.media.type.application.http">Internet Media Type application/http</a></li> 610 <li class="tocline1">9.2 <a href="#uri.scheme.registration">URI Scheme Registration</a></li> 611 <li class="tocline1">9.3 <a href="#internet.media.type.http">Internet Media Type Registrations</a><ul class="toc"> 612 <li class="tocline1">9.3.1 <a href="#internet.media.type.message.http">Internet Media Type message/http</a></li> 613 <li class="tocline1">9.3.2 <a href="#internet.media.type.application.http">Internet Media Type application/http</a></li> 613 614 </ul> 614 615 </li> … … 2077 2078 </div> 2078 2079 <p id="rfc.section.9.1.p.2">The change controller is: "IETF (iesg@ietf.org) - Internet Engineering Task Force".</p> 2079 <h2 id="rfc.section.9.2"><a href="#rfc.section.9.2">9.2</a> <a id="internet.media.type.http" href="#internet.media.type.http">Internet Media Type Registrations</a></h2> 2080 <p id="rfc.section.9.2.p.1">This document serves as the specification for the Internet media types "message/http" and "application/http". The following 2080 <h2 id="rfc.section.9.2"><a href="#rfc.section.9.2">9.2</a> <a id="uri.scheme.registration" href="#uri.scheme.registration">URI Scheme Registration</a></h2> 2081 <p id="rfc.section.9.2.p.1">The entry for the "http" URI Scheme in the registry located at <<a href="http://www.iana.org/assignments/uri-schemes.html">http://www.iana.org/assignments/uri-schemes.html</a>> should be updated to point to <a href="#http.url" title="http URL">Section 3.2.2</a> of this document (see <a href="#RFC4395" id="rfc.xref.RFC4395.1"><cite title="Guidelines and Registration Procedures for New URI Schemes">[RFC4395]</cite></a>). 2082 </p> 2083 <h2 id="rfc.section.9.3"><a href="#rfc.section.9.3">9.3</a> <a id="internet.media.type.http" href="#internet.media.type.http">Internet Media Type Registrations</a></h2> 2084 <p id="rfc.section.9.3.p.1">This document serves as the specification for the Internet media types "message/http" and "application/http". The following 2081 2085 is to be registered with IANA (see <a href="#RFC4288" id="rfc.xref.RFC4288.1"><cite title="Media Type Specifications and Registration Procedures">[RFC4288]</cite></a>). 2082 2086 </p> 2083 2087 <div id="rfc.iref.m.2"></div> 2084 2088 <div id="rfc.iref.m.3"></div> 2085 <h3 id="rfc.section.9. 2.1"><a href="#rfc.section.9.2.1">9.2.1</a> <a id="internet.media.type.message.http" href="#internet.media.type.message.http">Internet Media Type message/http</a></h3>2086 <p id="rfc.section.9. 2.1.p.1">The message/http type can be used to enclose a single HTTP request or response message, provided that it obeys the MIME restrictions2089 <h3 id="rfc.section.9.3.1"><a href="#rfc.section.9.3.1">9.3.1</a> <a id="internet.media.type.message.http" href="#internet.media.type.message.http">Internet Media Type message/http</a></h3> 2090 <p id="rfc.section.9.3.1.p.1">The message/http type can be used to enclose a single HTTP request or response message, provided that it obeys the MIME restrictions 2087 2091 for all "message" types regarding line length and encodings. 2088 2092 </p> 2089 <p id="rfc.section.9. 2.1.p.2"> </p>2093 <p id="rfc.section.9.3.1.p.2"> </p> 2090 2094 <dl> 2091 2095 <dt>Type name:</dt> … … 2113 2117 <dd>none</dd> 2114 2118 <dt>Published specification:</dt> 2115 <dd>This specification (see <a href="#internet.media.type.message.http" title="Internet Media Type message/http">Section 9. 2.1</a>).2119 <dd>This specification (see <a href="#internet.media.type.message.http" title="Internet Media Type message/http">Section 9.3.1</a>). 2116 2120 </dd> 2117 2121 <dt>Applications that use this media type:</dt> … … 2138 2142 <div id="rfc.iref.m.4"></div> 2139 2143 <div id="rfc.iref.a.1"></div> 2140 <h3 id="rfc.section.9. 2.2"><a href="#rfc.section.9.2.2">9.2.2</a> <a id="internet.media.type.application.http" href="#internet.media.type.application.http">Internet Media Type application/http</a></h3>2141 <p id="rfc.section.9. 2.2.p.1">The application/http type can be used to enclose a pipeline of one or more HTTP request or response messages (not intermixed).</p>2142 <p id="rfc.section.9. 2.2.p.2"> </p>2144 <h3 id="rfc.section.9.3.2"><a href="#rfc.section.9.3.2">9.3.2</a> <a id="internet.media.type.application.http" href="#internet.media.type.application.http">Internet Media Type application/http</a></h3> 2145 <p id="rfc.section.9.3.2.p.1">The application/http type can be used to enclose a pipeline of one or more HTTP request or response messages (not intermixed).</p> 2146 <p id="rfc.section.9.3.2.p.2"> </p> 2143 2147 <dl> 2144 2148 <dt>Type name:</dt> … … 2168 2172 <dd>none</dd> 2169 2173 <dt>Published specification:</dt> 2170 <dd>This specification (see <a href="#internet.media.type.application.http" title="Internet Media Type application/http">Section 9. 2.2</a>).2174 <dd>This specification (see <a href="#internet.media.type.application.http" title="Internet Media Type application/http">Section 9.3.2</a>). 2171 2175 </dd> 2172 2176 <dt>Applications that use this media type:</dt> … … 2351 2355 <h2 id="rfc.references.2"><a href="#rfc.section.12.2" id="rfc.section.12.2">12.2</a> Informative References 2352 2356 </h2> 2353 <table summary="Informative References"> 2357 <table summary="Informative References"> 2354 2358 <tr> 2355 2359 <td class="reference"><b id="Nie1997">[Nie1997]</b></td> … … 2452 2456 <td class="reference"><b id="RFC4288">[RFC4288]</b></td> 2453 2457 <td class="top"><a title="Sun Microsystems">Freed, N.</a> and <a>J. Klensin</a>, “<a href="http://tools.ietf.org/html/rfc4288">Media Type Specifications and Registration Procedures</a>”, BCP 13, RFC 4288, December 2005. 2458 </td> 2459 </tr> 2460 <tr> 2461 <td class="reference"><b id="RFC4395">[RFC4395]</b></td> 2462 <td class="top"><a title="AT&T Laboratories">Hansen, T.</a>, <a title="Qualcomm, Inc.">Hardie, T.</a>, and <a title="Adobe Systems">L. Masinter</a>, “<a href="http://tools.ietf.org/html/rfc4395">Guidelines and Registration Procedures for New URI Schemes</a>”, BCP 115, RFC 4395, February 2006. 2454 2463 </td> 2455 2464 </tr> … … 2723 2732 <li> <<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/120">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/120</a>>: "need new URL for PAD1995 reference" 2724 2733 </li> 2734 <li> <<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/127">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/127</a>>: "IANA Considerations: update HTTP URI scheme registration" 2735 </li> 2725 2736 </ul> 2726 2737 <p id="rfc.section.D.5.p.2">Ongoing work on ABNF conversion (<<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/36">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/36</a>>): … … 2759 2770 <ul class="ind"> 2760 2771 <li class="indline0"><a id="rfc.index.A" href="#rfc.index.A"><b>A</b></a><ul class="ind"> 2761 <li class="indline1">application/http Media Type <a class="iref" href="#rfc.iref.a.1"><b>9. 2.2</b></a></li>2772 <li class="indline1">application/http Media Type <a class="iref" href="#rfc.iref.a.1"><b>9.3.2</b></a></li> 2762 2773 </ul> 2763 2774 </li> … … 2911 2922 <li class="indline1">Media Type 2912 2923 <ul class="ind"> 2913 <li class="indline1">application/http <a class="iref" href="#rfc.iref.m.4"><b>9. 2.2</b></a></li>2914 <li class="indline1">message/http <a class="iref" href="#rfc.iref.m.2"><b>9. 2.1</b></a></li>2924 <li class="indline1">application/http <a class="iref" href="#rfc.iref.m.4"><b>9.3.2</b></a></li> 2925 <li class="indline1">message/http <a class="iref" href="#rfc.iref.m.2"><b>9.3.1</b></a></li> 2915 2926 </ul> 2916 2927 </li> 2917 2928 <li class="indline1">message <a class="iref" href="#rfc.iref.m.1">1.3</a></li> 2918 <li class="indline1">message/http Media Type <a class="iref" href="#rfc.iref.m.3"><b>9. 2.1</b></a></li>2929 <li class="indline1">message/http Media Type <a class="iref" href="#rfc.iref.m.3"><b>9.3.1</b></a></li> 2919 2930 </ul> 2920 2931 </li> … … 3008 3019 <li class="indline1"><em>RFC3864</em> <a class="iref" href="#rfc.xref.RFC3864.1">9.1</a>, <a class="iref" href="#RFC3864"><b>12.2</b></a></li> 3009 3020 <li class="indline1"><em>RFC3977</em> <a class="iref" href="#rfc.xref.RFC3977.1">1.1</a>, <a class="iref" href="#RFC3977"><b>12.2</b></a></li> 3010 <li class="indline1"><em>RFC4288</em> <a class="iref" href="#rfc.xref.RFC4288.1">9.2</a>, <a class="iref" href="#RFC4288"><b>12.2</b></a></li> 3021 <li class="indline1"><em>RFC4288</em> <a class="iref" href="#rfc.xref.RFC4288.1">9.3</a>, <a class="iref" href="#RFC4288"><b>12.2</b></a></li> 3022 <li class="indline1"><em>RFC4395</em> <a class="iref" href="#rfc.xref.RFC4395.1">9.2</a>, <a class="iref" href="#RFC4395"><b>12.2</b></a></li> 3011 3023 <li class="indline1"><em>RFC822</em> <a class="iref" href="#rfc.xref.RFC822.1">3.3.1</a>, <a class="iref" href="#RFC822"><b>12.2</b></a></li> 3012 3024 <li class="indline1"><em>RFC822ABNF</em> <a class="iref" href="#rfc.xref.RFC822ABNF.1">2.1</a>, <a class="iref" href="#rfc.xref.RFC822ABNF.2">11</a>, <a class="iref" href="#RFC822ABNF"><b>12.1</b></a></li> -
draft-ietf-httpbis/latest/p1-messaging.xml
r301 r307 2993 2993 </t> 2994 2994 </section> 2995 2996 <section title="URI Scheme Registration" anchor="uri.scheme.registration"> 2997 <t> 2998 The entry for the "http" URI Scheme in the registry located at 2999 <eref target="http://www.iana.org/assignments/uri-schemes.html"/> 3000 should be updated to point to <xref target="http.url"/> of this document 3001 (see <xref target="RFC4395"/>). 3002 </t> 3003 </section> 3004 2995 3005 <section title="Internet Media Type Registrations" anchor="internet.media.type.http"> 2996 3006 <t> … … 3142 3152 </section> 3143 3153 </section> 3154 3144 3155 </section> 3145 3156 … … 4024 4035 <seriesInfo name="BCP" value="13"/> 4025 4036 <seriesInfo name="RFC" value="4288"/> 4037 </reference> 4038 4039 <reference anchor='RFC4395'> 4040 <front> 4041 <title>Guidelines and Registration Procedures for New URI Schemes</title> 4042 <author initials='T.' surname='Hansen' fullname='T. Hansen'> 4043 <organization>AT&T Laboratories</organization> 4044 <address> 4045 <email>tony+urireg@maillennium.att.com</email> 4046 </address> 4047 </author> 4048 <author initials='T.' surname='Hardie' fullname='T. Hardie'> 4049 <organization>Qualcomm, Inc.</organization> 4050 <address> 4051 <email>hardie@qualcomm.com</email> 4052 </address> 4053 </author> 4054 <author initials='L.' surname='Masinter' fullname='L. Masinter'> 4055 <organization>Adobe Systems</organization> 4056 <address> 4057 <email>LMM@acm.org</email> 4058 </address> 4059 </author> 4060 <date year='2006' month='February' /> 4061 </front> 4062 <seriesInfo name='BCP' value='115' /> 4063 <seriesInfo name='RFC' value='4395' /> 4026 4064 </reference> 4027 4065 … … 4556 4594 "need new URL for PAD1995 reference" 4557 4595 </t> 4596 <t> 4597 <eref target="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/127"/>: 4598 "IANA Considerations: update HTTP URI scheme registration" 4599 </t> 4558 4600 </list> 4559 4601 </t>
Note: See TracChangeset
for help on using the changeset viewer.
