Ignore:
Timestamp:
Jul 12, 2008, 3:20:09 AM (11 years ago)
Author:
julian.reschke@…
Message:

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

File:
1 edited

Legend:

Unmodified
Added
Removed
  • 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.