Changeset 152


Ignore:
Timestamp:
Jan 5, 2008, 4:30:12 AM (12 years ago)
Author:
julian.reschke@…
Message:

Resolve #35: categorize RFC1737 (URN) as informative, RFC4288 (media type registration procedure) as normative (closes #35). Also update and re-organize media type registration for application/http and message/http to use RFC4288 template (relates to #8).

Location:
draft-ietf-httpbis/latest
Files:
14 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p1-messaging.html

    r151 r152  
    344344      <link rel="Chapter" title="11 Acknowledgments" href="#rfc.section.11">
    345345      <link rel="Chapter" href="#rfc.section.12" title="12 References">
    346       <link rel="Appendix" title="A Internet Media Type message/http and application/http" href="#rfc.section.A">
     346      <link rel="Appendix" title="A Internet Media Types" href="#rfc.section.A">
    347347      <link rel="Appendix" title="B Tolerant Applications" href="#rfc.section.B">
    348348      <link rel="Appendix" title="C Conversion of Date Formats" href="#rfc.section.C">
     
    587587               <li class="tocline1">12.1&nbsp;&nbsp;&nbsp;<a href="#rfc.references.1">Normative References</a></li>
    588588               <li class="tocline1">12.2&nbsp;&nbsp;&nbsp;<a href="#rfc.references.2">Informative References</a></li>
    589                <li class="tocline1">12.3&nbsp;&nbsp;&nbsp;<a href="#rfc.references.3">References (to be categorized)</a></li>
    590589            </ul>
    591590         </li>
    592591         <li class="tocline0"><a href="#rfc.authors">Authors' Addresses</a></li>
    593          <li class="tocline0">A.&nbsp;&nbsp;&nbsp;<a href="#internet.media.type.http">Internet Media Type message/http and application/http</a></li>
     592         <li class="tocline0">A.&nbsp;&nbsp;&nbsp;<a href="#internet.media.type.http">Internet Media Types</a><ul class="toc">
     593               <li class="tocline1">A.1&nbsp;&nbsp;&nbsp;<a href="#internet.media.type.message.http">Internet Media Type message/http</a></li>
     594               <li class="tocline1">A.2&nbsp;&nbsp;&nbsp;<a href="#internet.media.type.application.http">Internet Media Type application/http</a></li>
     595            </ul>
     596         </li>
    594597         <li class="tocline0">B.&nbsp;&nbsp;&nbsp;<a href="#tolerant.applications">Tolerant Applications</a></li>
    595598         <li class="tocline0">C.&nbsp;&nbsp;&nbsp;<a href="#conversion.of.date.formats">Conversion of Date Formats</a></li>
     
    19411944      <h2 id="rfc.references.1"><a href="#rfc.section.12.1" id="rfc.section.12.1">12.1</a> Normative References
    19421945      </h2>
    1943       <table summary="Normative References">                     
     1946      <table summary="Normative References">                       
    19441947         <tr>
    19451948            <td class="reference"><b id="ISO-8859-1">[ISO-8859-1]</b></td>
     
    19901993         </tr>
    19911994         <tr>
     1995            <td class="reference"><b id="RFC4288">[RFC4288]</b></td>
     1996            <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&nbsp;13, RFC&nbsp;4288, December&nbsp;2005.
     1997            </td>
     1998         </tr>
     1999         <tr>
    19922000            <td class="reference"><b id="RFC822ABNF">[RFC822ABNF]</b></td>
    19932001            <td class="top"><a title="University of Delaware, Dept. of Electrical Engineering">Crocker, D.H.</a>, “<a href="http://tools.ietf.org/html/rfc822">Standard for the format of ARPA Internet text messages</a>”, STD&nbsp;11, RFC&nbsp;822, August&nbsp;1982.
     
    21182126            <td class="reference"><b id="WAIS">[WAIS]</b></td>
    21192127            <td class="top">Davis, F., Kahle, B., Morris, H., Salem, J., Shen, T., Wang, R., Sui, J., and M. Grinbaum, “WAIS Interface Protocol Prototype Functional Specification (v1.5)”, Thinking Machines Corporation, April&nbsp;1990.</td>
    2120          </tr>
    2121       </table>
    2122       <h2 id="rfc.references.3"><a href="#rfc.section.12.3" id="rfc.section.12.3">12.3</a> References (to be categorized)
    2123       </h2>
    2124       <table summary="References (to be categorized)"> 
    2125          <tr>
    2126             <td class="reference"><b id="RFC4288">[RFC4288]</b></td>
    2127             <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&nbsp;13, RFC&nbsp;4288, December&nbsp;2005.
    2128             </td>
    21292128         </tr>
    21302129      </table>
     
    21452144            (editor)
    21462145            <span class="n hidden"><span class="family-name">Reschke</span><span class="given-name">Julian F.</span></span></span><span class="org vcardline">greenbytes GmbH</span><span class="adr"><span class="street-address vcardline">Hafenweg 16</span><span class="vcardline"><span class="locality">Muenster</span>, <span class="region">NW</span>&nbsp;<span class="postal-code">48155</span></span><span class="country-name vcardline">Germany</span></span><span class="vcardline tel">Phone: <a href="tel:+492512807760"><span class="value">+49 251 2807760</span></a></span><span class="vcardline tel"><span class="type">Fax</span>: <a href="fax:+492512807761"><span class="value">+49 251 2807761</span></a></span><span class="vcardline">EMail: <a><span class="email">julian.reschke@greenbytes.de</span></a></span><span class="vcardline">URI: <a href="http://greenbytes.de/tech/webdav/" class="url">http://greenbytes.de/tech/webdav/</a></span></address>
     2146      <h1 id="rfc.section.A"><a href="#rfc.section.A">A.</a>&nbsp;<a id="internet.media.type.http" href="#internet.media.type.http">Internet Media Types</a></h1>
     2147      <p id="rfc.section.A.p.1">In addition to defining the HTTP/1.1 protocol, this document serves as the specification for the Internet media type "message/http"
     2148         and "application/http". The following is to be registered with IANA <a href="#RFC4288" id="rfc.xref.RFC4288.1"><cite title="Media Type Specifications and Registration Procedures">[RFC4288]</cite></a>.
     2149      </p>
    21472150      <div id="rfc.iref.m.2"></div>
    21482151      <div id="rfc.iref.m.3"></div>
    2149       <div id="rfc.iref.m.4"></div>
    2150       <div id="rfc.iref.a.1"></div>
    2151       <h1 id="rfc.section.A"><a href="#rfc.section.A">A.</a>&nbsp;<a id="internet.media.type.http" href="#internet.media.type.http">Internet Media Type message/http and application/http</a></h1>
    2152       <p id="rfc.section.A.p.1">In addition to defining the HTTP/1.1 protocol, this document serves as the specification for the Internet media type "message/http"
    2153          and "application/http". The message/http type can be used to enclose a single HTTP request or response message, provided that
    2154          it obeys the MIME restrictions for all "message" types regarding line length and encodings. The application/http type can
    2155          be used to enclose a pipeline of one or more HTTP request or response messages (not intermixed). The following is to be registered
    2156          with IANA <a href="#RFC4288" id="rfc.xref.RFC4288.1"><cite title="Media Type Specifications and Registration Procedures">[RFC4288]</cite></a>.
    2157       </p>
    2158       <p id="rfc.section.A.p.2"> </p>
     2152      <h2 id="rfc.section.A.1"><a href="#rfc.section.A.1">A.1</a>&nbsp;<a id="internet.media.type.message.http" href="#internet.media.type.message.http">Internet Media Type message/http</a></h2>
     2153      <p id="rfc.section.A.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
     2154         for all "message" types regarding line length and encodings.
     2155      </p>
     2156      <p id="rfc.section.A.1.p.2"> </p>
    21592157      <dl>
    2160          <dt>Media Type name:</dt>
     2158         <dt>Type name:</dt>
    21612159         <dd>message</dd>
    2162          <dt>Media subtype name:</dt>
     2160         <dt>Subtype name:</dt>
    21632161         <dd>http</dd>
    21642162         <dt>Required parameters:</dt>
     
    21792177         <dt>Security considerations:</dt>
    21802178         <dd>none</dd>
    2181       </dl>
    2182       <p id="rfc.section.A.p.3"> </p>
     2179         <dt>Interoperability considerations:</dt>
     2180         <dd>none</dd>
     2181         <dt>Published specification:</dt>
     2182         <dd>This specification (see <a href="#internet.media.type.message.http" title="Internet Media Type message/http">Appendix&nbsp;A.1</a>).
     2183         </dd>
     2184         <dt>Applications that use this media type:</dt>
     2185         <dt>Additional information:</dt>
     2186         <dd>
     2187            <dl>
     2188               <dt>Magic number(s):</dt>
     2189               <dd>none</dd>
     2190               <dt>File extension(s):</dt>
     2191               <dd>none</dd>
     2192               <dt>Macintosh file type code(s):</dt>
     2193               <dd>none</dd>
     2194            </dl>
     2195         </dd>
     2196         <dt>Person and email address to contact for further information:</dt>
     2197         <dd>See Authors Section.</dd>
     2198         <dt>Intended usage:</dt>
     2199         <dd>COMMON</dd>
     2200         <dt>Restrictions on usage:</dt>
     2201         <dd>none</dd>
     2202         <dt>Author/Change controller:</dt>
     2203         <dd>IESG</dd>
     2204      </dl>
     2205      <div id="rfc.iref.m.4"></div>
     2206      <div id="rfc.iref.a.1"></div>
     2207      <h2 id="rfc.section.A.2"><a href="#rfc.section.A.2">A.2</a>&nbsp;<a id="internet.media.type.application.http" href="#internet.media.type.application.http">Internet Media Type application/http</a></h2>
     2208      <p id="rfc.section.A.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>
     2209      <p id="rfc.section.A.2.p.2"> </p>
    21832210      <dl>
    2184          <dt>Media Type name:</dt>
     2211         <dt>Type name:</dt>
    21852212         <dd>application</dd>
    2186          <dt>Media subtype name:</dt>
     2213         <dt>Subtype name:</dt>
    21872214         <dd>http</dd>
    21882215         <dt>Required parameters:</dt>
     
    22052232         <dt>Security considerations:</dt>
    22062233         <dd>none</dd>
     2234         <dt>Interoperability considerations:</dt>
     2235         <dd>none</dd>
     2236         <dt>Published specification:</dt>
     2237         <dd>This specification (see <a href="#internet.media.type.application.http" title="Internet Media Type application/http">Appendix&nbsp;A.2</a>).
     2238         </dd>
     2239         <dt>Applications that use this media type:</dt>
     2240         <dt>Additional information:</dt>
     2241         <dd>
     2242            <dl>
     2243               <dt>Magic number(s):</dt>
     2244               <dd>none</dd>
     2245               <dt>File extension(s):</dt>
     2246               <dd>none</dd>
     2247               <dt>Macintosh file type code(s):</dt>
     2248               <dd>none</dd>
     2249            </dl>
     2250         </dd>
     2251         <dt>Person and email address to contact for further information:</dt>
     2252         <dd>See Authors Section.</dd>
     2253         <dt>Intended usage:</dt>
     2254         <dd>COMMON</dd>
     2255         <dt>Restrictions on usage:</dt>
     2256         <dd>none</dd>
     2257         <dt>Author/Change controller:</dt>
     2258         <dd>IESG</dd>
    22072259      </dl>
    22082260      <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a>&nbsp;<a id="tolerant.applications" href="#tolerant.applications">Tolerant Applications</a></h1>
     
    23522404         <li> &lt;<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/31">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/31</a>&gt;: "qdtext BNF"
    23532405         </li>
     2406         <li> &lt;<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/35">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/35</a>&gt;: "Normative and Informative references"
     2407         </li>
    23542408         <li> &lt;<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/42">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/42</a>&gt;: "RFC2606 Compliance"
    23552409         </li>
     
    23712425      <p id="rfc.section.E.2.p.2">Other changes: </p>
    23722426      <ul>
    2373          <li>Start work on categorizing references as "Normative" or "Informative".</li>
     2427         <li>Update media type registrations to use RFC4288 template.</li>
    23742428      </ul>
    23752429      <h1><a id="rfc.copyright" href="#rfc.copyright">Full Copyright Statement</a></h1>
     
    24062460         <ul class="ind">
    24072461            <li class="indline0"><a id="rfc.index.A" href="#rfc.index.A"><b>A</b></a><ul class="ind">
    2408                   <li class="indline1">application/http Media Type&nbsp;&nbsp;<a class="iref" href="#rfc.iref.a.1"><b>A</b></a></li>
     2462                  <li class="indline1">application/http Media Type&nbsp;&nbsp;<a class="iref" href="#rfc.iref.a.1"><b>A.2</b></a></li>
    24092463               </ul>
    24102464            </li>
     
    25452599                  <li class="indline1">Media Type&nbsp;&nbsp;
    25462600                     <ul class="ind">
    2547                         <li class="indline1">application/http&nbsp;&nbsp;<a class="iref" href="#rfc.iref.m.4"><b>A</b></a></li>
    2548                         <li class="indline1">message/http&nbsp;&nbsp;<a class="iref" href="#rfc.iref.m.2"><b>A</b></a></li>
     2601                        <li class="indline1">application/http&nbsp;&nbsp;<a class="iref" href="#rfc.iref.m.4"><b>A.2</b></a></li>
     2602                        <li class="indline1">message/http&nbsp;&nbsp;<a class="iref" href="#rfc.iref.m.2"><b>A.1</b></a></li>
    25492603                     </ul>
    25502604                  </li>
    25512605                  <li class="indline1">message&nbsp;&nbsp;<a class="iref" href="#rfc.iref.m.1">1.3</a></li>
    2552                   <li class="indline1">message/http Media Type&nbsp;&nbsp;<a class="iref" href="#rfc.iref.m.3"><b>A</b></a></li>
     2606                  <li class="indline1">message/http Media Type&nbsp;&nbsp;<a class="iref" href="#rfc.iref.m.3"><b>A.1</b></a></li>
    25532607               </ul>
    25542608            </li>
     
    26332687                  </li>
    26342688                  <li class="indline1"><em>RFC3977</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC3977.1">1.1</a>, <a class="iref" href="#RFC3977"><b>12.2</b></a></li>
    2635                   <li class="indline1"><em>RFC4288</em>&nbsp;&nbsp;<a class="iref" href="#RFC4288"><b>12.3</b></a>, <a class="iref" href="#rfc.xref.RFC4288.1">A</a></li>
     2689                  <li class="indline1"><em>RFC4288</em>&nbsp;&nbsp;<a class="iref" href="#RFC4288"><b>12.1</b></a>, <a class="iref" href="#rfc.xref.RFC4288.1">A</a></li>
    26362690                  <li class="indline1"><em>RFC822</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC822.1">3.3.1</a>, <a class="iref" href="#RFC822"><b>12.2</b></a></li>
    26372691                  <li class="indline1"><em>RFC822ABNF</em>&nbsp;&nbsp;<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

    r151 r152  
    31803180</reference>
    31813181
     3182<reference anchor="RFC4288">
     3183  <front>
     3184    <title>Media Type Specifications and Registration Procedures</title>
     3185    <author initials="N." surname="Freed" fullname="N. Freed">
     3186      <organization>Sun Microsystems</organization>
     3187      <address>
     3188        <email>ned.freed@mrochek.com</email>
     3189      </address>
     3190    </author>
     3191    <author initials="J." surname="Klensin" fullname="J. Klensin">
     3192      <organization/>
     3193      <address>
     3194        <email>klensin+ietf@jck.com</email>
     3195      </address>
     3196    </author>
     3197    <date year="2005" month="December"/>
     3198  </front>
     3199  <seriesInfo name="BCP" value="13"/>
     3200  <seriesInfo name="RFC" value="4288"/>
     3201</reference>
     3202
    31823203<reference anchor="USASCII">
    31833204  <front>
     
    36173638</references>
    36183639
    3619 <references title="References (to be categorized)">
    3620 
    3621 <reference anchor="RFC4288">
    3622   <front>
    3623     <title>Media Type Specifications and Registration Procedures</title>
    3624     <author initials="N." surname="Freed" fullname="N. Freed">
    3625       <organization>Sun Microsystems</organization>
    3626       <address>
    3627         <email>ned.freed@mrochek.com</email>
    3628       </address>
    3629     </author>
    3630     <author initials="J." surname="Klensin" fullname="J. Klensin">
    3631       <organization/>
    3632       <address>
    3633         <email>klensin+ietf@jck.com</email>
    3634       </address>
    3635     </author>
    3636     <date year="2005" month="December"/>
    3637   </front>
    3638   <seriesInfo name="BCP" value="13"/>
    3639   <seriesInfo name="RFC" value="4288"/>
    3640 </reference>
    3641 
    3642 
    3643 </references>
    3644 
    3645 <section title="Internet Media Type message/http and application/http" anchor="internet.media.type.http">
     3640
     3641<section title="Internet Media Types" anchor="internet.media.type.http">
     3642<t>
     3643   In addition to defining the HTTP/1.1 protocol, this document serves
     3644   as the specification for the Internet media type "message/http" and
     3645   "application/http". The following is to be registered with IANA <xref target="RFC4288"/>.
     3646</t>
     3647<section title="Internet Media Type message/http" anchor="internet.media.type.message.http">
    36463648<iref item="Media Type" subitem="message/http" primary="true"/>
    36473649<iref item="message/http Media Type" primary="true"/>
    3648 <iref item="Media Type" subitem="application/http" primary="true"/>
    3649 <iref item="application/http Media Type" primary="true"/>
    3650 <t>
    3651    In addition to defining the HTTP/1.1 protocol, this document serves
    3652    as the specification for the Internet media type "message/http" and
    3653    "application/http". The message/http type can be used to enclose a
    3654    single HTTP request or response message, provided that it obeys the
    3655    MIME restrictions for all "message" types regarding line length and
    3656    encodings. The application/http type can be used to enclose a
    3657    pipeline of one or more HTTP request or response messages (not
    3658    intermixed). The following is to be registered with IANA <xref target="RFC4288"/>.
     3650<t>
     3651   The message/http type can be used to enclose a single HTTP request or
     3652   response message, provided that it obeys the MIME restrictions for all
     3653   "message" types regarding line length and encodings.
    36593654</t>
    36603655<t>
    36613656  <list style="hanging" x:indent="12em">
    3662     <t hangText="Media Type name:">
     3657    <t hangText="Type name:">
    36633658      message
    36643659    </t>
    3665     <t hangText="Media subtype name:">
     3660    <t hangText="Subtype name:">
    36663661      http
    36673662    </t>
     
    36903685      none
    36913686    </t>
    3692   </list>
     3687    <t hangText="Interoperability considerations:">
     3688      none
     3689    </t>
     3690    <t hangText="Published specification:">
     3691      This specification (see <xref target="internet.media.type.message.http"/>).
     3692    </t>
     3693    <t hangText="Applications that use this media type:">
     3694    </t>
     3695    <t hangText="Additional information:">
     3696      <list style="hanging">
     3697        <t hangText="Magic number(s):">none</t>
     3698        <t hangText="File extension(s):">none</t>
     3699        <t hangText="Macintosh file type code(s):">none</t>
     3700      </list>
     3701    </t>
     3702    <t hangText="Person and email address to contact for further information:">
     3703      See Authors Section.
     3704    </t>
     3705                <t hangText="Intended usage:">
     3706                  COMMON
     3707    </t>
     3708                <t hangText="Restrictions on usage:">
     3709                  none
     3710    </t>
     3711    <t hangText="Author/Change controller:">
     3712      IESG
     3713    </t>
     3714  </list>
     3715</t>
     3716</section>
     3717<section title="Internet Media Type application/http" anchor="internet.media.type.application.http">
     3718<iref item="Media Type" subitem="application/http" primary="true"/>
     3719<iref item="application/http Media Type" primary="true"/>
     3720<t>
     3721   The application/http type can be used to enclose a pipeline of one or more
     3722   HTTP request or response messages (not intermixed).
    36933723</t>
    36943724<t>
    36953725  <list style="hanging" x:indent="12em">
    3696     <t hangText="Media Type name:">
     3726    <t hangText="Type name:">
    36973727      application
    36983728    </t>
    3699     <t hangText="Media subtype name:">
     3729    <t hangText="Subtype name:">
    37003730      http
    37013731    </t>
     
    37273757      none
    37283758    </t>
    3729   </list>
    3730 </t>
     3759    <t hangText="Interoperability considerations:">
     3760      none
     3761    </t>
     3762    <t hangText="Published specification:">
     3763      This specification (see <xref target="internet.media.type.application.http"/>).
     3764    </t>
     3765    <t hangText="Applications that use this media type:">
     3766    </t>
     3767    <t hangText="Additional information:">
     3768      <list style="hanging">
     3769        <t hangText="Magic number(s):">none</t>
     3770        <t hangText="File extension(s):">none</t>
     3771        <t hangText="Macintosh file type code(s):">none</t>
     3772      </list>
     3773    </t>
     3774    <t hangText="Person and email address to contact for further information:">
     3775      See Authors Section.
     3776    </t>
     3777                <t hangText="Intended usage:">
     3778                  COMMON
     3779    </t>
     3780                <t hangText="Restrictions on usage:">
     3781                  none
     3782    </t>
     3783    <t hangText="Author/Change controller:">
     3784      IESG
     3785    </t>
     3786  </list>
     3787</t>
     3788</section>
    37313789</section>
    37323790
     
    40264084    </t>
    40274085    <t>
     4086      <eref target="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/35"/>:
     4087      "Normative and Informative references"
     4088    </t>
     4089    <t>
    40284090      <eref target="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/42"/>:
    40294091      "RFC2606 Compliance"
     
    40614123<t>
    40624124  Other changes:
    4063   <list style="symbols">
    4064     <t>
    4065       Start work on categorizing references as "Normative" or "Informative".
     4125  <list style="symbols"> 
     4126    <t>
     4127      Update media type registrations to use RFC4288 template.
    40664128    </t>
    40674129  </list>
  • draft-ietf-httpbis/latest/p2-semantics.html

    r150 r152  
    16941694         <li> &lt;<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/17">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/17</a>&gt;: "Revise description of the POST method" (&lt;<a href="http://purl.org/NET/http-errata#post">http://purl.org/NET/http-errata#post</a>&gt;)
    16951695         </li>
     1696         <li> &lt;<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/35">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/35</a>&gt;: "Normative and Informative references"
     1697         </li>
    16961698         <li> &lt;<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/42">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/42</a>&gt;: "RFC2606 Compliance"
    16971699         </li>
     
    17051707         <li>Move definitions of 304 and 412 condition codes to <a href="#Part4" id="rfc.xref.Part4.9"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>
    17061708         </li>
    1707          <li>Categorize references as "Normative" or "Informative".</li>
    17081709      </ul>
    17091710      <h1><a id="rfc.copyright" href="#rfc.copyright">Full Copyright Statement</a></h1>
  • draft-ietf-httpbis/latest/p2-semantics.xml

    r150 r152  
    25892589    </t>
    25902590    <t>
     2591      <eref target="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/35"/>:
     2592      "Normative and Informative references"
     2593    </t>
     2594    <t>
    25912595      <eref target="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/42"/>:
    25922596      "RFC2606 Compliance"
     
    26082612      Move definitions of 304 and 412 condition codes to <xref target="Part4"/>
    26092613    </t>
    2610     <t>
    2611       Categorize references as "Normative" or "Informative".
    2612     </t>
    26132614  </list>
    26142615</t>
  • draft-ietf-httpbis/latest/p3-payload.html

    r150 r152  
    533533               <li class="tocline1">9.1&nbsp;&nbsp;&nbsp;<a href="#rfc.references.1">Normative References</a></li>
    534534               <li class="tocline1">9.2&nbsp;&nbsp;&nbsp;<a href="#rfc.references.2">Informative References</a></li>
    535                <li class="tocline1">9.3&nbsp;&nbsp;&nbsp;<a href="#rfc.references.3">References (to be categorized)</a></li>
    536535            </ul>
    537536         </li>
     
    658657      </p>
    659658      <h2 id="rfc.section.2.3"><a href="#rfc.section.2.3">2.3</a>&nbsp;<a id="media.types" href="#media.types">Media Types</a></h2>
    660       <p id="rfc.section.2.3.p.1">HTTP uses Internet Media Types <a href="#RFC4288" id="rfc.xref.RFC4288.1"><cite title="Media Type Specifications and Registration Procedures">[RFC4288]</cite></a> in the Content-Type (<a href="#header.content-type" id="rfc.xref.header.content-type.1" title="Content-Type">Section&nbsp;5.9</a>) and Accept (<a href="#header.accept" id="rfc.xref.header.accept.1" title="Accept">Section&nbsp;5.1</a>) header fields in order to provide open and extensible data typing and type negotiation.
     659      <p id="rfc.section.2.3.p.1">HTTP uses Internet Media Types <a href="#RFC2046" id="rfc.xref.RFC2046.1"><cite title="Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types">[RFC2046]</cite></a> in the Content-Type (<a href="#header.content-type" id="rfc.xref.header.content-type.1" title="Content-Type">Section&nbsp;5.9</a>) and Accept (<a href="#header.accept" id="rfc.xref.header.accept.1" title="Accept">Section&nbsp;5.1</a>) header fields in order to provide open and extensible data typing and type negotiation.
    661660      </p>
    662661      <div id="rfc.figure.u.3"></div><pre class="inline"><span id="rfc.iref.g.4"></span><span id="rfc.iref.g.5"></span><span id="rfc.iref.g.6"></span>  media-type     = type "/" subtype *( ";" parameter )
     
    676675      </p>
    677676      <p id="rfc.section.2.3.p.7">Media-type values are registered with the Internet Assigned Number Authority (IANA). The media type registration process is
    678          outlined in <a href="#RFC4288" id="rfc.xref.RFC4288.2"><cite title="Media Type Specifications and Registration Procedures">[RFC4288]</cite></a>. Use of non-registered media types is discouraged.
     677         outlined in <a href="#RFC4288" id="rfc.xref.RFC4288.1"><cite title="Media Type Specifications and Registration Procedures">[RFC4288]</cite></a>. Use of non-registered media types is discouraged.
    679678      </p>
    680679      <h3 id="rfc.section.2.3.1"><a href="#rfc.section.2.3.1">2.3.1</a>&nbsp;<a id="canonicalization.and.text.defaults" href="#canonicalization.and.text.defaults">Canonicalization and Text Defaults</a></h3>
     
    698697      <h3 id="rfc.section.2.3.2"><a href="#rfc.section.2.3.2">2.3.2</a>&nbsp;<a id="multipart.types" href="#multipart.types">Multipart Types</a></h3>
    699698      <p id="rfc.section.2.3.2.p.1">MIME provides for a number of "multipart" types -- encapsulations of one or more entities within a single message-body. All
    700          multipart types share a common syntax, as defined in <a href="http://tools.ietf.org/html/rfc2046#section-5.1.1">Section 5.1.1</a> of <a href="#RFC2046" id="rfc.xref.RFC2046.1"><cite title="Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types">[RFC2046]</cite></a>, and <em class="bcp14">MUST</em> include a boundary parameter as part of the media type value. The message body is itself a protocol element and <em class="bcp14">MUST</em> therefore use only CRLF to represent line breaks between body-parts. Unlike in RFC 2046, the epilogue of any multipart message <em class="bcp14">MUST</em> be empty; HTTP applications <em class="bcp14">MUST NOT</em> transmit the epilogue (even if the original multipart contains an epilogue). These restrictions exist in order to preserve
     699         multipart types share a common syntax, as defined in <a href="http://tools.ietf.org/html/rfc2046#section-5.1.1">Section 5.1.1</a> of <a href="#RFC2046" id="rfc.xref.RFC2046.2"><cite title="Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types">[RFC2046]</cite></a>, and <em class="bcp14">MUST</em> include a boundary parameter as part of the media type value. The message body is itself a protocol element and <em class="bcp14">MUST</em> therefore use only CRLF to represent line breaks between body-parts. Unlike in RFC 2046, the epilogue of any multipart message <em class="bcp14">MUST</em> be empty; HTTP applications <em class="bcp14">MUST NOT</em> transmit the epilogue (even if the original multipart contains an epilogue). These restrictions exist in order to preserve
    701700         the self-delimiting nature of a multipart message-body, wherein the "end" of the message-body is indicated by the ending multipart
    702701         boundary.
     
    12021201      <h2 id="rfc.references.1"><a href="#rfc.section.9.1" id="rfc.section.9.1">9.1</a> Normative References
    12031202      </h2>
    1204       <table summary="Normative References">                           
     1203      <table summary="Normative References">                             
    12051204         <tr>
    12061205            <td class="reference"><b id="ISO-8859-1">[ISO-8859-1]</b></td>
     
    12781277            </td>
    12791278         </tr>
     1279         <tr>
     1280            <td class="reference"><b id="RFC4288">[RFC4288]</b></td>
     1281            <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&nbsp;13, RFC&nbsp;4288, December&nbsp;2005.
     1282            </td>
     1283         </tr>
    12801284      </table>
    12811285      <h2 id="rfc.references.2"><a href="#rfc.section.9.2" id="rfc.section.9.2">9.2</a> Informative References
     
    13401344            <td class="reference"><b id="RFC3629">[RFC3629]</b></td>
    13411345            <td class="top"><a title="Alis Technologies">Yergeau, F.</a>, “<a href="http://tools.ietf.org/html/rfc3629">UTF-8, a transformation format of ISO 10646</a>”, RFC&nbsp;3629, STD&nbsp;63, November&nbsp;2003.
    1342             </td>
    1343          </tr>
    1344       </table>
    1345       <h2 id="rfc.references.3"><a href="#rfc.section.9.3" id="rfc.section.9.3">9.3</a> References (to be categorized)
    1346       </h2>
    1347       <table summary="References (to be categorized)"> 
    1348          <tr>
    1349             <td class="reference"><b id="RFC4288">[RFC4288]</b></td>
    1350             <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&nbsp;13, RFC&nbsp;4288, December&nbsp;2005.
    13511346            </td>
    13521347         </tr>
     
    13881383      </p>
    13891384      <h2 id="rfc.section.A.2"><a href="#rfc.section.A.2">A.2</a>&nbsp;<a id="conversion.to.canonical.form" href="#conversion.to.canonical.form">Conversion to Canonical Form</a></h2>
    1390       <p id="rfc.section.A.2.p.1"> <a href="#RFC2045" id="rfc.xref.RFC2045.3"><cite title="Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies">[RFC2045]</cite></a> requires that an Internet mail entity be converted to canonical form prior to being transferred, as described in <a href="http://tools.ietf.org/html/rfc2049#section-4">Section 4</a> of <a href="#RFC2049" id="rfc.xref.RFC2049.1"><cite title="Multipurpose Internet Mail Extensions (MIME) Part Five: Conformance Criteria and Examples">[RFC2049]</cite></a>. <a href="#canonicalization.and.text.defaults" title="Canonicalization and Text Defaults">Section&nbsp;2.3.1</a> of this document describes the forms allowed for subtypes of the "text" media type when transmitted over HTTP. <a href="#RFC2046" id="rfc.xref.RFC2046.2"><cite title="Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types">[RFC2046]</cite></a> requires that content with a type of "text" represent line breaks as CRLF and forbids the use of CR or LF outside of line
     1385      <p id="rfc.section.A.2.p.1"> <a href="#RFC2045" id="rfc.xref.RFC2045.3"><cite title="Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies">[RFC2045]</cite></a> requires that an Internet mail entity be converted to canonical form prior to being transferred, as described in <a href="http://tools.ietf.org/html/rfc2049#section-4">Section 4</a> of <a href="#RFC2049" id="rfc.xref.RFC2049.1"><cite title="Multipurpose Internet Mail Extensions (MIME) Part Five: Conformance Criteria and Examples">[RFC2049]</cite></a>. <a href="#canonicalization.and.text.defaults" title="Canonicalization and Text Defaults">Section&nbsp;2.3.1</a> of this document describes the forms allowed for subtypes of the "text" media type when transmitted over HTTP. <a href="#RFC2046" id="rfc.xref.RFC2046.3"><cite title="Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types">[RFC2046]</cite></a> requires that content with a type of "text" represent line breaks as CRLF and forbids the use of CR or LF outside of line
    13911386         break sequences. HTTP allows CRLF, bare CR, and bare LF to indicate a line break within text content when a message is transmitted
    13921387         over HTTP.
     
    14941489         <li> &lt;<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/25">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/25</a>&gt;: "Accept-Encoding BNF"
    14951490         </li>
     1491         <li> &lt;<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/35">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/35</a>&gt;: "Normative and Informative references"
     1492         </li>
    14961493         <li> &lt;<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/46">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/46</a>&gt;: "RFC1700 references"
    14971494         </li>
     
    15041501         <li> &lt;<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/86">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/86</a>&gt;: "Normative up-to-date references"
    15051502         </li>
    1506       </ul>
    1507       <p id="rfc.section.D.2.p.2">Other changes: </p>
    1508       <ul>
    1509          <li>Start work on categorizing references as "Normative" or "Informative".</li>
    15101503      </ul>
    15111504      <h1><a id="rfc.copyright" href="#rfc.copyright">Full Copyright Statement</a></h1>
     
    16841677                  <li class="indline1"><em>RFC1952</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC1952.1">2.2</a>, <a class="iref" href="#RFC1952"><b>9.1</b></a></li>
    16851678                  <li class="indline1"><em>RFC2045</em>&nbsp;&nbsp;<a class="iref" href="#RFC2045"><b>9.1</b></a>, <a class="iref" href="#rfc.xref.RFC2045.1">A</a>, <a class="iref" href="#rfc.xref.RFC2045.2">A.1</a>, <a class="iref" href="#rfc.xref.RFC2045.3">A.2</a></li>
    1686                   <li class="indline1"><em>RFC2046</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2046.1">2.3.2</a>, <a class="iref" href="#RFC2046"><b>9.1</b></a>, <a class="iref" href="#rfc.xref.RFC2046.2">A.2</a><ul class="ind">
    1687                         <li class="indline1"><em>Section 5.1.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2046.1">2.3.2</a></li>
     1679                  <li class="indline1"><em>RFC2046</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2046.1">2.3</a>, <a class="iref" href="#rfc.xref.RFC2046.2">2.3.2</a>, <a class="iref" href="#RFC2046"><b>9.1</b></a>, <a class="iref" href="#rfc.xref.RFC2046.3">A.2</a><ul class="ind">
     1680                        <li class="indline1"><em>Section 5.1.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2046.2">2.3.2</a></li>
    16881681                     </ul>
    16891682                  </li>
     
    17021695                  <li class="indline1"><em>RFC2822</em>&nbsp;&nbsp;<a class="iref" href="#RFC2822"><b>9.2</b></a>, <a class="iref" href="#rfc.xref.RFC2822.1">A</a></li>
    17031696                  <li class="indline1"><em>RFC3629</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC3629.1">2.1</a>, <a class="iref" href="#RFC3629"><b>9.2</b></a></li>
    1704                   <li class="indline1"><em>RFC4288</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC4288.1">2.3</a>, <a class="iref" href="#rfc.xref.RFC4288.2">2.3</a>, <a class="iref" href="#RFC4288"><b>9.3</b></a></li>
     1697                  <li class="indline1"><em>RFC4288</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC4288.1">2.3</a>, <a class="iref" href="#RFC4288"><b>9.1</b></a></li>
    17051698               </ul>
    17061699            </li>
  • draft-ietf-httpbis/latest/p3-payload.xml

    r150 r152  
    384384<section title="Media Types" anchor="media.types">
    385385<t>
    386    HTTP uses Internet Media Types <xref target="RFC4288"/> in the Content-Type (<xref target="header.content-type"/>)
     386   HTTP uses Internet Media Types <xref target="RFC2046"/> in the Content-Type (<xref target="header.content-type"/>)
    387387   and Accept (<xref target="header.accept"/>) header fields in order to provide
    388388   open and extensible data typing and type negotiation.
     
    18361836</reference>
    18371837
    1838 </references>
    1839 
    1840 <references title="Informative References">
    1841 
    1842 <reference anchor="RFC1806">
    1843   <front>
    1844     <title abbrev="Content-Disposition">Communicating Presentation Information in Internet Messages: The Content-Disposition Header</title>
    1845     <author initials="R." surname="Troost" fullname="Rens Troost">
    1846       <organization>New Century Systems</organization>
    1847       <address><email>rens@century.com</email></address>
    1848     </author>
    1849     <author initials="S." surname="Dorner" fullname="Steve Dorner">
    1850       <organization>QUALCOMM Incorporated</organization>
    1851       <address><email>sdorner@qualcomm.com</email></address>
    1852     </author>
    1853     <date month="June" year="1995"/>
    1854   </front>
    1855   <seriesInfo name="RFC" value="1806"/>
    1856 </reference>
    1857 
    1858 <reference anchor="RFC1945">
    1859   <front>
    1860     <title abbrev="HTTP/1.0">Hypertext Transfer Protocol -- HTTP/1.0</title>
    1861     <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
    1862       <organization>MIT, Laboratory for Computer Science</organization>
    1863       <address><email>timbl@w3.org</email></address>
    1864     </author>
    1865     <author initials="R.T." surname="Fielding" fullname="Roy T. Fielding">
    1866       <organization>University of California, Irvine, Department of Information and Computer Science</organization>
    1867       <address><email>fielding@ics.uci.edu</email></address>
    1868     </author>
    1869     <author initials="H.F." surname="Nielsen" fullname="Henrik Frystyk Nielsen">
    1870       <organization>W3 Consortium, MIT Laboratory for Computer Science</organization>
    1871       <address><email>frystyk@w3.org</email></address>
    1872     </author>
    1873     <date month="May" year="1996"/>
    1874   </front>
    1875   <seriesInfo name="RFC" value="1945"/>
    1876 </reference>
    1877 
    1878 <reference anchor="RFC2049">
    1879   <front>
    1880     <title abbrev="MIME Conformance">Multipurpose Internet Mail Extensions (MIME) Part Five: Conformance Criteria and Examples</title>
    1881     <author initials="N." surname="Freed" fullname="Ned Freed">
    1882       <organization>Innosoft International, Inc.</organization>
    1883       <address><email>ned@innosoft.com</email></address>
    1884     </author>
    1885     <author initials="N.S." surname="Borenstein" fullname="Nathaniel S. Borenstein">
    1886       <organization>First Virtual Holdings</organization>
    1887       <address><email>nsb@nsb.fv.com</email></address>
    1888     </author>
    1889     <date month="November" year="1996"/>
    1890   </front>
    1891   <seriesInfo name="RFC" value="2049"/>
    1892 </reference>
    1893 
    1894 <reference anchor="RFC2068">
    1895   <front>
    1896     <title abbrev="HTTP/1.1">Hypertext Transfer Protocol -- HTTP/1.1</title>
    1897     <author initials="R." surname="Fielding" fullname="Roy T. Fielding">
    1898       <organization>University of California, Irvine, Department of Information and Computer Science</organization>
    1899       <address><email>fielding@ics.uci.edu</email></address>
    1900     </author>
    1901     <author initials="J." surname="Gettys" fullname="Jim Gettys">
    1902       <organization>MIT Laboratory for Computer Science</organization>
    1903       <address><email>jg@w3.org</email></address>
    1904     </author>
    1905     <author initials="J." surname="Mogul" fullname="Jeffrey C. Mogul">
    1906       <organization>Digital Equipment Corporation, Western Research Laboratory</organization>
    1907       <address><email>mogul@wrl.dec.com</email></address>
    1908     </author>
    1909     <author initials="H." surname="Nielsen" fullname="Henrik Frystyk Nielsen">
    1910       <organization>MIT Laboratory for Computer Science</organization>
    1911       <address><email>frystyk@w3.org</email></address>
    1912     </author>
    1913     <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
    1914       <organization>MIT Laboratory for Computer Science</organization>
    1915       <address><email>timbl@w3.org</email></address>
    1916     </author>
    1917     <date month="January" year="1997"/>
    1918   </front>
    1919   <seriesInfo name="RFC" value="2068"/>
    1920 </reference>
    1921 
    1922 <reference anchor="RFC2076">
    1923   <front>
    1924     <title abbrev="Internet Message Headers">Common Internet Message Headers</title>
    1925     <author initials="J." surname="Palme" fullname="Jacob Palme">
    1926       <organization>Stockholm University/KTH</organization>
    1927       <address><email>jpalme@dsv.su.se</email></address>
    1928     </author>
    1929     <date month="February" year="1997"/>
    1930   </front>
    1931   <seriesInfo name="RFC" value="2076"/>
    1932 </reference>
    1933 
    1934 <reference anchor="RFC2183">
    1935   <front>
    1936     <title abbrev="Content-Disposition">Communicating Presentation Information in Internet Messages: The Content-Disposition Header Field</title>
    1937     <author initials="R." surname="Troost" fullname="Rens Troost">
    1938       <organization>New Century Systems</organization>
    1939       <address><email>rens@century.com</email></address>
    1940     </author>
    1941     <author initials="S." surname="Dorner" fullname="Steve Dorner">
    1942       <organization>QUALCOMM Incorporated</organization>
    1943       <address><email>sdorner@qualcomm.com</email></address>
    1944     </author>
    1945     <author initials="K." surname="Moore" fullname="Keith Moore">
    1946       <organization>Department of Computer Science</organization>
    1947       <address><email>moore@cs.utk.edu</email></address>
    1948     </author>
    1949     <date month="August" year="1997"/>
    1950   </front>
    1951   <seriesInfo name="RFC" value="2183"/>
    1952 </reference>
    1953 
    1954 <reference anchor="RFC2277">
    1955   <front>
    1956     <title abbrev="Charset Policy">IETF Policy on Character Sets and Languages</title>
    1957     <author initials="H.T." surname="Alvestrand" fullname="Harald Tveit Alvestrand">
    1958       <organization>UNINETT</organization>
    1959       <address><email>Harald.T.Alvestrand@uninett.no</email></address>
    1960     </author>
    1961     <date month="January" year="1998"/>
    1962   </front>
    1963   <seriesInfo name="BCP" value="18"/>
    1964   <seriesInfo name="RFC" value="2277"/>
    1965 </reference>
    1966 
    1967 <reference anchor="RFC2388">
    1968   <front>
    1969     <title abbrev="multipart/form-data">Returning Values from Forms:  multipart/form-data</title>
    1970     <author initials="L." surname="Masinter" fullname="Larry Masinter">
    1971       <organization>Xerox Palo Alto Research Center</organization>
    1972       <address><email>masinter@parc.xerox.com</email></address>
    1973     </author>
    1974     <date year="1998" month="August"/>
    1975   </front>
    1976   <seriesInfo name="RFC" value="2388"/>
    1977 </reference>
    1978 
    1979 <reference anchor="RFC2557">
    1980   <front>
    1981     <title abbrev="MIME Encapsulation of Aggregate Documents">MIME Encapsulation of Aggregate Documents, such as HTML (MHTML)</title>
    1982     <author initials="F." surname="Palme" fullname="Jacob Palme">
    1983       <organization>Stockholm University and KTH</organization>
    1984       <address><email>jpalme@dsv.su.se</email></address>
    1985     </author>
    1986     <author initials="A." surname="Hopmann" fullname="Alex Hopmann">
    1987       <organization>Microsoft Corporation</organization>
    1988       <address><email>alexhop@microsoft.com</email></address>
    1989     </author>
    1990     <author initials="N." surname="Shelness" fullname="Nick Shelness">
    1991       <organization>Lotus Development Corporation</organization>
    1992       <address><email>Shelness@lotus.com</email></address>
    1993     </author>
    1994     <author initials="E." surname="Stefferud" fullname="Einar Stefferud">
    1995       <organization/>
    1996       <address><email>stef@nma.com</email></address>
    1997     </author>
    1998     <date year="1999" month="March"/>
    1999   </front>
    2000   <seriesInfo name="RFC" value="2557"/>
    2001 </reference>
    2002 
    2003 <reference anchor="RFC2616">
    2004   <front>
    2005     <title>Hypertext Transfer Protocol -- HTTP/1.1</title>
    2006     <author initials="R." surname="Fielding" fullname="R. Fielding">
    2007       <organization>University of California, Irvine</organization>
    2008       <address><email>fielding@ics.uci.edu</email></address>
    2009     </author>
    2010     <author initials="J." surname="Gettys" fullname="J. Gettys">
    2011       <organization>W3C</organization>
    2012       <address><email>jg@w3.org</email></address>
    2013     </author>
    2014     <author initials="J." surname="Mogul" fullname="J. Mogul">
    2015       <organization>Compaq Computer Corporation</organization>
    2016       <address><email>mogul@wrl.dec.com</email></address>
    2017     </author>
    2018     <author initials="H." surname="Frystyk" fullname="H. Frystyk">
    2019       <organization>MIT Laboratory for Computer Science</organization>
    2020       <address><email>frystyk@w3.org</email></address>
    2021     </author>
    2022     <author initials="L." surname="Masinter" fullname="L. Masinter">
    2023       <organization>Xerox Corporation</organization>
    2024       <address><email>masinter@parc.xerox.com</email></address>
    2025     </author>
    2026     <author initials="P." surname="Leach" fullname="P. Leach">
    2027       <organization>Microsoft Corporation</organization>
    2028       <address><email>paulle@microsoft.com</email></address>
    2029     </author>
    2030     <author initials="T." surname="Berners-Lee" fullname="T. Berners-Lee">
    2031       <organization>W3C</organization>
    2032       <address><email>timbl@w3.org</email></address>
    2033     </author>
    2034     <date month="June" year="1999"/>
    2035   </front>
    2036   <seriesInfo name="RFC" value="2616"/>
    2037 </reference>
    2038 
    2039 <reference anchor="RFC2822">
    2040   <front>
    2041     <title>Internet Message Format</title>
    2042     <author initials="P." surname="Resnick" fullname="P. Resnick">
    2043       <organization>QUALCOMM Incorporated</organization>
    2044     </author>
    2045     <date year="2001" month="April"/>
    2046   </front>
    2047   <seriesInfo name="RFC" value="2822"/>
    2048 </reference>
    2049 
    2050 <reference anchor="RFC3629">
    2051   <front>
    2052     <title>UTF-8, a transformation format of ISO 10646</title>
    2053     <author initials="F." surname="Yergeau" fullname="F. Yergeau">
    2054       <organization>Alis Technologies</organization>
    2055       <address><email>fyergeau@alis.com</email></address>
    2056     </author>
    2057     <date month="November" year="2003"/>
    2058   </front>
    2059   <seriesInfo name="RFC" value="3629"/>
    2060   <seriesInfo name="STD" value="63"/>
    2061 </reference>
    2062 
    2063 </references>
    2064 
    2065 <references title="References (to be categorized)">
    2066 
    20671838<reference anchor="RFC4288">
    20681839  <front>
     
    20841855  <seriesInfo name="BCP" value="13"/>
    20851856  <seriesInfo name="RFC" value="4288"/>
     1857</reference>
     1858
     1859</references>
     1860
     1861<references title="Informative References">
     1862
     1863<reference anchor="RFC1806">
     1864  <front>
     1865    <title abbrev="Content-Disposition">Communicating Presentation Information in Internet Messages: The Content-Disposition Header</title>
     1866    <author initials="R." surname="Troost" fullname="Rens Troost">
     1867      <organization>New Century Systems</organization>
     1868      <address><email>rens@century.com</email></address>
     1869    </author>
     1870    <author initials="S." surname="Dorner" fullname="Steve Dorner">
     1871      <organization>QUALCOMM Incorporated</organization>
     1872      <address><email>sdorner@qualcomm.com</email></address>
     1873    </author>
     1874    <date month="June" year="1995"/>
     1875  </front>
     1876  <seriesInfo name="RFC" value="1806"/>
     1877</reference>
     1878
     1879<reference anchor="RFC1945">
     1880  <front>
     1881    <title abbrev="HTTP/1.0">Hypertext Transfer Protocol -- HTTP/1.0</title>
     1882    <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
     1883      <organization>MIT, Laboratory for Computer Science</organization>
     1884      <address><email>timbl@w3.org</email></address>
     1885    </author>
     1886    <author initials="R.T." surname="Fielding" fullname="Roy T. Fielding">
     1887      <organization>University of California, Irvine, Department of Information and Computer Science</organization>
     1888      <address><email>fielding@ics.uci.edu</email></address>
     1889    </author>
     1890    <author initials="H.F." surname="Nielsen" fullname="Henrik Frystyk Nielsen">
     1891      <organization>W3 Consortium, MIT Laboratory for Computer Science</organization>
     1892      <address><email>frystyk@w3.org</email></address>
     1893    </author>
     1894    <date month="May" year="1996"/>
     1895  </front>
     1896  <seriesInfo name="RFC" value="1945"/>
     1897</reference>
     1898
     1899<reference anchor="RFC2049">
     1900  <front>
     1901    <title abbrev="MIME Conformance">Multipurpose Internet Mail Extensions (MIME) Part Five: Conformance Criteria and Examples</title>
     1902    <author initials="N." surname="Freed" fullname="Ned Freed">
     1903      <organization>Innosoft International, Inc.</organization>
     1904      <address><email>ned@innosoft.com</email></address>
     1905    </author>
     1906    <author initials="N.S." surname="Borenstein" fullname="Nathaniel S. Borenstein">
     1907      <organization>First Virtual Holdings</organization>
     1908      <address><email>nsb@nsb.fv.com</email></address>
     1909    </author>
     1910    <date month="November" year="1996"/>
     1911  </front>
     1912  <seriesInfo name="RFC" value="2049"/>
     1913</reference>
     1914
     1915<reference anchor="RFC2068">
     1916  <front>
     1917    <title abbrev="HTTP/1.1">Hypertext Transfer Protocol -- HTTP/1.1</title>
     1918    <author initials="R." surname="Fielding" fullname="Roy T. Fielding">
     1919      <organization>University of California, Irvine, Department of Information and Computer Science</organization>
     1920      <address><email>fielding@ics.uci.edu</email></address>
     1921    </author>
     1922    <author initials="J." surname="Gettys" fullname="Jim Gettys">
     1923      <organization>MIT Laboratory for Computer Science</organization>
     1924      <address><email>jg@w3.org</email></address>
     1925    </author>
     1926    <author initials="J." surname="Mogul" fullname="Jeffrey C. Mogul">
     1927      <organization>Digital Equipment Corporation, Western Research Laboratory</organization>
     1928      <address><email>mogul@wrl.dec.com</email></address>
     1929    </author>
     1930    <author initials="H." surname="Nielsen" fullname="Henrik Frystyk Nielsen">
     1931      <organization>MIT Laboratory for Computer Science</organization>
     1932      <address><email>frystyk@w3.org</email></address>
     1933    </author>
     1934    <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
     1935      <organization>MIT Laboratory for Computer Science</organization>
     1936      <address><email>timbl@w3.org</email></address>
     1937    </author>
     1938    <date month="January" year="1997"/>
     1939  </front>
     1940  <seriesInfo name="RFC" value="2068"/>
     1941</reference>
     1942
     1943<reference anchor="RFC2076">
     1944  <front>
     1945    <title abbrev="Internet Message Headers">Common Internet Message Headers</title>
     1946    <author initials="J." surname="Palme" fullname="Jacob Palme">
     1947      <organization>Stockholm University/KTH</organization>
     1948      <address><email>jpalme@dsv.su.se</email></address>
     1949    </author>
     1950    <date month="February" year="1997"/>
     1951  </front>
     1952  <seriesInfo name="RFC" value="2076"/>
     1953</reference>
     1954
     1955<reference anchor="RFC2183">
     1956  <front>
     1957    <title abbrev="Content-Disposition">Communicating Presentation Information in Internet Messages: The Content-Disposition Header Field</title>
     1958    <author initials="R." surname="Troost" fullname="Rens Troost">
     1959      <organization>New Century Systems</organization>
     1960      <address><email>rens@century.com</email></address>
     1961    </author>
     1962    <author initials="S." surname="Dorner" fullname="Steve Dorner">
     1963      <organization>QUALCOMM Incorporated</organization>
     1964      <address><email>sdorner@qualcomm.com</email></address>
     1965    </author>
     1966    <author initials="K." surname="Moore" fullname="Keith Moore">
     1967      <organization>Department of Computer Science</organization>
     1968      <address><email>moore@cs.utk.edu</email></address>
     1969    </author>
     1970    <date month="August" year="1997"/>
     1971  </front>
     1972  <seriesInfo name="RFC" value="2183"/>
     1973</reference>
     1974
     1975<reference anchor="RFC2277">
     1976  <front>
     1977    <title abbrev="Charset Policy">IETF Policy on Character Sets and Languages</title>
     1978    <author initials="H.T." surname="Alvestrand" fullname="Harald Tveit Alvestrand">
     1979      <organization>UNINETT</organization>
     1980      <address><email>Harald.T.Alvestrand@uninett.no</email></address>
     1981    </author>
     1982    <date month="January" year="1998"/>
     1983  </front>
     1984  <seriesInfo name="BCP" value="18"/>
     1985  <seriesInfo name="RFC" value="2277"/>
     1986</reference>
     1987
     1988<reference anchor="RFC2388">
     1989  <front>
     1990    <title abbrev="multipart/form-data">Returning Values from Forms:  multipart/form-data</title>
     1991    <author initials="L." surname="Masinter" fullname="Larry Masinter">
     1992      <organization>Xerox Palo Alto Research Center</organization>
     1993      <address><email>masinter@parc.xerox.com</email></address>
     1994    </author>
     1995    <date year="1998" month="August"/>
     1996  </front>
     1997  <seriesInfo name="RFC" value="2388"/>
     1998</reference>
     1999
     2000<reference anchor="RFC2557">
     2001  <front>
     2002    <title abbrev="MIME Encapsulation of Aggregate Documents">MIME Encapsulation of Aggregate Documents, such as HTML (MHTML)</title>
     2003    <author initials="F." surname="Palme" fullname="Jacob Palme">
     2004      <organization>Stockholm University and KTH</organization>
     2005      <address><email>jpalme@dsv.su.se</email></address>
     2006    </author>
     2007    <author initials="A." surname="Hopmann" fullname="Alex Hopmann">
     2008      <organization>Microsoft Corporation</organization>
     2009      <address><email>alexhop@microsoft.com</email></address>
     2010    </author>
     2011    <author initials="N." surname="Shelness" fullname="Nick Shelness">
     2012      <organization>Lotus Development Corporation</organization>
     2013      <address><email>Shelness@lotus.com</email></address>
     2014    </author>
     2015    <author initials="E." surname="Stefferud" fullname="Einar Stefferud">
     2016      <organization/>
     2017      <address><email>stef@nma.com</email></address>
     2018    </author>
     2019    <date year="1999" month="March"/>
     2020  </front>
     2021  <seriesInfo name="RFC" value="2557"/>
     2022</reference>
     2023
     2024<reference anchor="RFC2616">
     2025  <front>
     2026    <title>Hypertext Transfer Protocol -- HTTP/1.1</title>
     2027    <author initials="R." surname="Fielding" fullname="R. Fielding">
     2028      <organization>University of California, Irvine</organization>
     2029      <address><email>fielding@ics.uci.edu</email></address>
     2030    </author>
     2031    <author initials="J." surname="Gettys" fullname="J. Gettys">
     2032      <organization>W3C</organization>
     2033      <address><email>jg@w3.org</email></address>
     2034    </author>
     2035    <author initials="J." surname="Mogul" fullname="J. Mogul">
     2036      <organization>Compaq Computer Corporation</organization>
     2037      <address><email>mogul@wrl.dec.com</email></address>
     2038    </author>
     2039    <author initials="H." surname="Frystyk" fullname="H. Frystyk">
     2040      <organization>MIT Laboratory for Computer Science</organization>
     2041      <address><email>frystyk@w3.org</email></address>
     2042    </author>
     2043    <author initials="L." surname="Masinter" fullname="L. Masinter">
     2044      <organization>Xerox Corporation</organization>
     2045      <address><email>masinter@parc.xerox.com</email></address>
     2046    </author>
     2047    <author initials="P." surname="Leach" fullname="P. Leach">
     2048      <organization>Microsoft Corporation</organization>
     2049      <address><email>paulle@microsoft.com</email></address>
     2050    </author>
     2051    <author initials="T." surname="Berners-Lee" fullname="T. Berners-Lee">
     2052      <organization>W3C</organization>
     2053      <address><email>timbl@w3.org</email></address>
     2054    </author>
     2055    <date month="June" year="1999"/>
     2056  </front>
     2057  <seriesInfo name="RFC" value="2616"/>
     2058</reference>
     2059
     2060<reference anchor="RFC2822">
     2061  <front>
     2062    <title>Internet Message Format</title>
     2063    <author initials="P." surname="Resnick" fullname="P. Resnick">
     2064      <organization>QUALCOMM Incorporated</organization>
     2065    </author>
     2066    <date year="2001" month="April"/>
     2067  </front>
     2068  <seriesInfo name="RFC" value="2822"/>
     2069</reference>
     2070
     2071<reference anchor="RFC3629">
     2072  <front>
     2073    <title>UTF-8, a transformation format of ISO 10646</title>
     2074    <author initials="F." surname="Yergeau" fullname="F. Yergeau">
     2075      <organization>Alis Technologies</organization>
     2076      <address><email>fyergeau@alis.com</email></address>
     2077    </author>
     2078    <date month="November" year="2003"/>
     2079  </front>
     2080  <seriesInfo name="RFC" value="3629"/>
     2081  <seriesInfo name="STD" value="63"/>
    20862082</reference>
    20872083
     
    23502346    </t>
    23512347    <t>
     2348      <eref target="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/35"/>:
     2349      "Normative and Informative references"
     2350    </t>
     2351    <t>
    23522352      <eref target="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/46"/>:
    23532353      "RFC1700 references"
     
    23712371  </list>
    23722372</t>
    2373 <t>
    2374   Other changes:
    2375   <list style="symbols">
    2376     <t>
    2377       Start work on categorizing references as "Normative" or "Informative".
    2378     </t>
    2379   </list>
    2380 </t>
    23812373</section>
    23822374
  • draft-ietf-httpbis/latest/p4-conditional.html

    r150 r152  
    959959      <h2 id="rfc.section.B.2"><a href="#rfc.section.B.2">B.2</a>&nbsp;Since draft-ietf-httpbis-p4-conditional-00
    960960      </h2>
    961       <p id="rfc.section.B.2.p.1">Other changes: </p>
     961      <p id="rfc.section.B.2.p.1">Closed issues: </p>
     962      <ul>
     963         <li> &lt;<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/35">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/35</a>&gt;: "Normative and Informative references"
     964         </li>
     965      </ul>
     966      <p id="rfc.section.B.2.p.2">Other changes: </p>
    962967      <ul>
    963968         <li>Move definitions of 304 and 412 condition codes from Part2.</li>
    964          <li>Categorize references as "Normative" or "Informative".</li>
    965969      </ul>
    966970      <h1><a id="rfc.copyright" href="#rfc.copyright">Full Copyright Statement</a></h1>
  • draft-ietf-httpbis/latest/p4-conditional.xml

    r150 r152  
    11641164<section title="Since draft-ietf-httpbis-p4-conditional-00">
    11651165<t>
     1166  Closed issues:
     1167  <list style="symbols">
     1168    <t>
     1169      <eref target="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/35"/>:
     1170      "Normative and Informative references"
     1171    </t>
     1172  </list>
     1173</t>
     1174<t>
    11661175  Other changes:
    11671176  <list style="symbols">
     
    11691178      Move definitions of 304 and 412 condition codes from Part2.
    11701179    </t>
    1171     <t>
    1172       Categorize references as "Normative" or "Informative".
    1173     </t>
    11741180  </list>
    11751181</t>
  • draft-ietf-httpbis/latest/p5-range.html

    r150 r152  
    923923         <li> &lt;<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/18">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/18</a>&gt;: "Cache validators in 206 responses" (&lt;<a href="http://purl.org/NET/http-errata#ifrange206">http://purl.org/NET/http-errata#ifrange206</a>&gt;)
    924924         </li>
     925         <li> &lt;<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/35">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/35</a>&gt;: "Normative and Informative references"
     926         </li>
    925927         <li> &lt;<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/86">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/86</a>&gt;: "Normative up-to-date references"
    926928         </li>
    927       </ul>
    928       <p id="rfc.section.C.2.p.2">Other changes: </p>
    929       <ul>
    930          <li>Categorize references as "Normative" or "Informative".</li>
    931929      </ul>
    932930      <h1><a id="rfc.copyright" href="#rfc.copyright">Full Copyright Statement</a></h1>
  • draft-ietf-httpbis/latest/p5-range.xml

    r150 r152  
    11191119    </t>
    11201120    <t>
     1121      <eref target="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/35"/>:
     1122      "Normative and Informative references"
     1123    </t>
     1124    <t>
    11211125      <eref target="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/86"/>:
    11221126      "Normative up-to-date references"
     
    11241128  </list>
    11251129</t>
    1126 <t>
    1127   Other changes:
    1128   <list style="symbols">
    1129     <t>
    1130       Categorize references as "Normative" or "Informative".
    1131     </t>
    1132   </list>
    1133 </t>
    11341130</section>
    11351131
  • draft-ietf-httpbis/latest/p6-cache.html

    r150 r152  
    18441844         <li> &lt;<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/12">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/12</a>&gt;: "Invalidation after Update or Delete" (&lt;<a href="http://purl.org/NET/http-errata#invalidupd">http://purl.org/NET/http-errata#invalidupd</a>&gt;)
    18451845         </li>
     1846         <li> &lt;<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/35">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/35</a>&gt;: "Normative and Informative references"
     1847         </li>
    18461848         <li> &lt;<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/48">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/48</a>&gt;: "Date reference typo"
    18471849         </li>
     
    18561858         <li> &lt;<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/87">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/87</a>&gt;: "typo in 13.2.2"
    18571859         </li>
    1858       </ul>
    1859       <p id="rfc.section.B.2.p.2">Other changes: </p>
    1860       <ul>
    1861          <li>Categorize references as "Normative" or "Informative".</li>
    18621860      </ul>
    18631861      <h1><a id="rfc.copyright" href="#rfc.copyright">Full Copyright Statement</a></h1>
  • draft-ietf-httpbis/latest/p6-cache.xml

    r150 r152  
    28862886    </t>
    28872887    <t>
     2888      <eref target="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/35"/>:
     2889      "Normative and Informative references"
     2890    </t>
     2891    <t>
    28882892      <eref target="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/48"/>:
    28892893      "Date reference typo"
     
    29112915  </list>
    29122916</t>
    2913 <t>
    2914   Other changes:
    2915   <list style="symbols">
    2916     <t>
    2917       Categorize references as "Normative" or "Informative".
    2918     </t>
    2919   </list>
    2920 </t>
    29212917</section>
    29222918
  • draft-ietf-httpbis/latest/p7-auth.html

    r150 r152  
    689689      <h2 id="rfc.section.B.2"><a href="#rfc.section.B.2">B.2</a>&nbsp;Since draft-ietf-httpbis-p7-auth-00
    690690      </h2>
    691       <p id="rfc.section.B.2.p.1">Other changes: </p>
     691      <p id="rfc.section.B.2.p.1">Closed issues: </p>
    692692      <ul>
    693          <li>Categorize references as "Normative" or "Informative".</li>
     693         <li> &lt;<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/35">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/35</a>&gt;: "Normative and Informative references"
     694         </li>
    694695      </ul>
    695696      <h1><a id="rfc.copyright" href="#rfc.copyright">Full Copyright Statement</a></h1>
  • draft-ietf-httpbis/latest/p7-auth.xml

    r150 r152  
    611611<section title="Since draft-ietf-httpbis-p7-auth-00">
    612612<t>
    613   Other changes:
    614   <list style="symbols">
     613  Closed issues:
     614  <list style="symbols"> 
    615615    <t>
    616       Categorize references as "Normative" or "Informative".
     616      <eref target="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/35"/>:
     617      "Normative and Informative references"
    617618    </t>
    618619  </list>
Note: See TracChangeset for help on using the changeset viewer.