Changeset 277


Ignore:
Timestamp:
12/07/08 10:20:09 (14 years ago)
Author:
julian.reschke@…
Message:

Rephrase RFC1950-52 downref annotations, reference BCP97 (related to #68)

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

Legend:

Unmodified
Added
Removed

  • draft-ietf-httpbis/latest/p3-payload.html

    r272 r277  
    474474         <tr>
    475475            <td class="header left"></td>
    476             <td class="header right">July 6, 2008</td>
     476            <td class="header right">July 12, 2008</td>
    477477         </tr>
    478478      </table>
    … …  
    14031403         <tr>
    14041404            <td class="reference"><b id="RFC1950">[RFC1950]</b></td>
    1405             <td class="top"><a title="Aladdin Enterprises">Deutsch, L.P.</a> and J-L. Gailly, “<a href="http://tools.ietf.org/html/rfc1950">ZLIB Compressed Data Format Specification version 3.3</a>”, RFC&nbsp;1950, May&nbsp;1996.<br>RFC1950 is an Informational RFC, thus it may be less stable than this specification. On the other hand, this downward reference
    1406                was present since <a href="#RFC2068" id="rfc.xref.RFC2068.1"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a> (published in 1997), therefore it is unlikely to cause problems in practice.
     1405            <td class="top"><a title="Aladdin Enterprises">Deutsch, L.P.</a> and J-L. Gailly, “<a href="http://tools.ietf.org/html/rfc1950">ZLIB Compressed Data Format Specification version 3.3</a>”, RFC&nbsp;1950, May&nbsp;1996.<br>RFC 1950 is an Informational RFC, thus it may be less stable than this specification. On the other hand, this downward reference
     1406               was present since the publication of RFC 2068 in 1997 (<a href="#RFC2068" id="rfc.xref.RFC2068.1"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a>), therefore it is unlikely to cause problems in practice. See also <a href="#BCP97" id="rfc.xref.BCP97.1"><cite title="Handling Normative References to Standards-Track Documents">[BCP97]</cite></a>.
    14071407            </td>
    14081408         </tr>
    14091409         <tr>
    14101410            <td class="reference"><b id="RFC1951">[RFC1951]</b></td>
    1411             <td class="top"><a title="Aladdin Enterprises">Deutsch, P.</a>, “<a href="http://tools.ietf.org/html/rfc1951">DEFLATE Compressed Data Format Specification version 1.3</a>”, RFC&nbsp;1951, May&nbsp;1996.<br>RFC1951 is an Informational RFC, thus it may be less stable than this specification. On the other hand, this downward reference
    1412                was present since <a href="#RFC2068" id="rfc.xref.RFC2068.2"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a> (published in 1997), therefore it is unlikely to cause problems in practice.
     1411            <td class="top"><a title="Aladdin Enterprises">Deutsch, P.</a>, “<a href="http://tools.ietf.org/html/rfc1951">DEFLATE Compressed Data Format Specification version 1.3</a>”, RFC&nbsp;1951, May&nbsp;1996.<br>RFC 1951 is an Informational RFC, thus it may be less stable than this specification. On the other hand, this downward reference
     1412               was present since the publication of RFC 2068 in 1997 (<a href="#RFC2068" id="rfc.xref.RFC2068.2"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a>), therefore it is unlikely to cause problems in practice. See also <a href="#BCP97" id="rfc.xref.BCP97.2"><cite title="Handling Normative References to Standards-Track Documents">[BCP97]</cite></a>.
    14131413            </td>
    14141414         </tr>
    14151415         <tr>
    14161416            <td class="reference"><b id="RFC1952">[RFC1952]</b></td>
    1417             <td class="top"><a title="Aladdin Enterprises">Deutsch, P.</a>, <a>Gailly, J-L.</a>, <a>Adler, M.</a>, <a>Deutsch, L.P.</a>, and <a>G. Randers-Pehrson</a>, “<a href="http://tools.ietf.org/html/rfc1952">GZIP file format specification version 4.3</a>”, RFC&nbsp;1952, May&nbsp;1996.<br>RFC1952 is an Informational RFC, thus it may be less stable than this specification. On the other hand, this downward reference
    1418                was present since <a href="#RFC2068" id="rfc.xref.RFC2068.3"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a> (published in 1997), therefore it is unlikely to cause problems in practice.
     1417            <td class="top"><a title="Aladdin Enterprises">Deutsch, P.</a>, <a>Gailly, J-L.</a>, <a>Adler, M.</a>, <a>Deutsch, L.P.</a>, and <a>G. Randers-Pehrson</a>, “<a href="http://tools.ietf.org/html/rfc1952">GZIP file format specification version 4.3</a>”, RFC&nbsp;1952, May&nbsp;1996.<br>RFC 1952 is an Informational RFC, thus it may be less stable than this specification. On the other hand, this downward reference
     1418               was present since the publication of RFC 2068 in 1997 (<a href="#RFC2068" id="rfc.xref.RFC2068.3"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a>), therefore it is unlikely to cause problems in practice. See also <a href="#BCP97" id="rfc.xref.BCP97.3"><cite title="Handling Normative References to Standards-Track Documents">[BCP97]</cite></a>.
    14191419            </td>
    14201420         </tr>
    … …  
    14371437      <h2 id="rfc.references.2"><a href="#rfc.section.10.2" id="rfc.section.10.2">10.2</a> Informative References
    14381438      </h2>
    1439       <table summary="Informative References">                         
     1439      <table summary="Informative References">                           
     1440         <tr>
     1441            <td class="reference"><b id="BCP97">[BCP97]</b></td>
     1442            <td class="top"><a>Klensin, J.</a> and <a title="MIT">S. Hartman</a>, “<a href="http://tools.ietf.org/html/rfc4897">Handling Normative References to Standards-Track Documents</a>”, BCP&nbsp;97, RFC&nbsp;4897, June&nbsp;2007.
     1443            </td>
     1444         </tr>
    14401445         <tr>
    14411446            <td class="reference"><b id="RFC1945">[RFC1945]</b></td>
    … …  
    16851690      <p id="rfc.section.D.5.p.1">Closed issues: </p>
    16861691      <ul>
    1687          <li> &lt;<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/121">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/121</a>&gt;: "RFC 1806 has been replaced by RFC2183"
     1692         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/121">http://tools.ietf.org/wg/httpbis/trac/ticket/121</a>&gt;: "RFC 1806 has been replaced by RFC2183"
     1693         </li>
     1694      </ul>
     1695      <p id="rfc.section.D.5.p.2">Other changes: </p>
     1696      <ul>
     1697         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/68">http://tools.ietf.org/wg/httpbis/trac/ticket/68</a>&gt;: "Encoding References Normative" -- rephrase the annotation and reference <a href="#BCP97" id="rfc.xref.BCP97.4"><cite title="Handling Normative References to Standards-Track Documents">[BCP97]</cite></a>.
    16881698         </li>
    16891699      </ul>
    … …  
    17131723      </p>
    17141724      <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1>
    1715       <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.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.U">U</a>
     1725      <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.P">P</a> <a href="#rfc.index.R">R</a> <a href="#rfc.index.U">U</a>
    17161726      </p>
    17171727      <div class="print2col">
    … …  
    17231733                  <li class="indline1">Accept-Language header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.accept-language.1">5.1</a>, <a class="iref" href="#rfc.iref.a.4"><b>6.4</b></a>, <a class="iref" href="#rfc.xref.header.accept-language.2">7.1</a></li>
    17241734                  <li class="indline1">Alternates header&nbsp;&nbsp;<a class="iref" href="#rfc.iref.a.5"><b>C.1</b></a></li>
     1735               </ul>
     1736            </li>
     1737            <li class="indline0"><a id="rfc.index.B" href="#rfc.index.B"><b>B</b></a><ul class="ind">
     1738                  <li class="indline1"><em>BCP97</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.BCP97.1">§</a>, <a class="iref" href="#rfc.xref.BCP97.2">§</a>, <a class="iref" href="#rfc.xref.BCP97.3">§</a>, <a class="iref" href="#BCP97"><b>10.2</b></a>, <a class="iref" href="#rfc.xref.BCP97.4">D.5</a></li>
    17251739               </ul>
    17261740            </li>

  • draft-ietf-httpbis/latest/p3-payload.xml

    r271 r277  
    19221922  <seriesInfo name="RFC" value="1950"/>
    19231923  <annotation>
    1924     RFC1950 is an Informational RFC, thus it may be less stable than
     1924    RFC 1950 is an Informational RFC, thus it may be less stable than
    19251925    this specification. On the other hand, this downward reference was
    1926     present since <xref target="RFC2068"/> (published in 1997), therefore it is unlikely
    1927     to cause problems in practice.
     1926    present since the publication of RFC 2068 in 1997 (<xref target="RFC2068"/>),
     1927    therefore it is unlikely to cause problems in practice. See also
     1928    <xref target="BCP97"/>.
    19281929  </annotation>
    19291930</reference>
    … …  
    19401941  <seriesInfo name="RFC" value="1951"/>
    19411942  <annotation>
    1942     RFC1951 is an Informational RFC, thus it may be less stable than
     1943    RFC 1951 is an Informational RFC, thus it may be less stable than
    19431944    this specification. On the other hand, this downward reference was
    1944     present since <xref target="RFC2068"/> (published in 1997), therefore it is unlikely
    1945     to cause problems in practice.
     1945    present since the publication of RFC 2068 in 1997 (<xref target="RFC2068"/>),
     1946    therefore it is unlikely to cause problems in practice. See also
     1947    <xref target="BCP97"/>.
    19461948  </annotation>
    19471949</reference>
    … …  
    19741976  <seriesInfo name="RFC" value="1952"/>
    19751977  <annotation>
    1976     RFC1952 is an Informational RFC, thus it may be less stable than
     1978    RFC 1952 is an Informational RFC, thus it may be less stable than
    19771979    this specification. On the other hand, this downward reference was
    1978     present since <xref target="RFC2068"/> (published in 1997), therefore it is unlikely
    1979     to cause problems in practice.
     1980    present since the publication of RFC 2068 in 1997 (<xref target="RFC2068"/>),
     1981    therefore it is unlikely to cause problems in practice. See also
     1982    <xref target="BCP97"/>.
    19801983  </annotation>
    19811984</reference>
    … …  
    22762279  <seriesInfo name="RFC" value="4288"/>
    22772280</reference>
     2281
     2282<reference anchor='BCP97'>
     2283  <front>
     2284    <title>Handling Normative References to Standards-Track Documents</title>
     2285    <author initials='J.' surname='Klensin' fullname='J. Klensin'>
     2286      <organization />
     2287      <address>
     2288        <email>klensin+ietf@jck.com</email>
     2289      </address>
     2290    </author>
     2291    <author initials='S.' surname='Hartman' fullname='S. Hartman'>
     2292      <organization>MIT</organization>
     2293      <address>
     2294        <email>hartmans-ietf@mit.edu</email>
     2295      </address>
     2296    </author>
     2297    <date year='2007' month='June' />
     2298  </front>
     2299  <seriesInfo name='BCP' value='97' />
     2300  <seriesInfo name='RFC' value='4897' />
     2301</reference>
     2302
    22782303
    22792304</references>
    … …  
    26252650  <list style="symbols">
    26262651    <t>
    2627       <eref target="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/121"/>:
     2652      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/121"/>:
    26282653      "RFC 1806 has been replaced by RFC2183"
    26292654    </t>
    26302655  </list>
    26312656</t>
     2657<t>
     2658  Other changes:
     2659  <list style="symbols">
     2660    <t>
     2661      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/68"/>:
     2662      "Encoding References Normative" -- rephrase the annotation and reference
     2663      <xref target="BCP97"/>.
     2664    </t>
     2665  </list>
     2666</t>
    26322667 </section>
    26332668
Note: See TracChangeset for help on using the changeset viewer.