Ignore:
Timestamp:
Aug 26, 2011, 7:08:10 AM (8 years ago)
Author:
julian.reschke@…
Message:

reduce verbosity in reference annotations

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

Legend:

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

    r1412 r1414  
    359359  }
    360360  @bottom-center {
    361        content: "Expires February 26, 2012";
     361       content: "Expires February 27, 2012";
    362362  }
    363363  @bottom-right {
     
    409409      <meta name="dct.creator" content="Reschke, J. F.">
    410410      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p1-messaging-latest">
    411       <meta name="dct.issued" scheme="ISO8601" content="2011-08-25">
     411      <meta name="dct.issued" scheme="ISO8601" content="2011-08-26">
    412412      <meta name="dct.replaces" content="urn:ietf:rfc:2145">
    413413      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
     
    441441            </tr>
    442442            <tr>
    443                <td class="left">Expires: February 26, 2012</td>
     443               <td class="left">Expires: February 27, 2012</td>
    444444               <td class="right">HP</td>
    445445            </tr>
     
    494494            <tr>
    495495               <td class="left"></td>
    496                <td class="right">August 25, 2011</td>
     496               <td class="right">August 26, 2011</td>
    497497            </tr>
    498498         </tbody>
     
    527527         in progress”.
    528528      </p>
    529       <p>This Internet-Draft will expire on February 26, 2012.</p>
     529      <p>This Internet-Draft will expire on February 27, 2012.</p>
    530530      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    531531      <p>Copyright © 2011 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
     
    28442844            <td class="reference"><b id="RFC1950">[RFC1950]</b></td>
    28452845            <td class="top"><a href="mailto:ghost@aladdin.com" title="Aladdin Enterprises">Deutsch, L.</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 might be less stable than this specification. On the other hand, this downward reference
    2846                was present since the publication of RFC 2068 in 1997 (<a href="#RFC2068" id="rfc.xref.RFC2068.5"><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>.
     2846               was present since the publication of <cite title="Hypertext Transfer Protocol -- HTTP/1.1" id="rfc.xref.RFC2068.5">RFC 2068</cite> in 1997, 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>.
    28472847            </td>
    28482848         </tr>
     
    28502850            <td class="reference"><b id="RFC1951">[RFC1951]</b></td>
    28512851            <td class="top"><a href="mailto:ghost@aladdin.com" 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 might be less stable than this specification. On the other hand, this downward reference
    2852                was present since the publication of RFC 2068 in 1997 (<a href="#RFC2068" id="rfc.xref.RFC2068.6"><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>.
     2852               was present since the publication of <cite title="Hypertext Transfer Protocol -- HTTP/1.1" id="rfc.xref.RFC2068.6">RFC 2068</cite> in 1997, 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>.
    28532853            </td>
    28542854         </tr>
     
    28562856            <td class="reference"><b id="RFC1952">[RFC1952]</b></td>
    28572857            <td class="top"><a href="mailto:ghost@aladdin.com" title="Aladdin Enterprises">Deutsch, P.</a>, <a href="mailto:gzip@prep.ai.mit.edu">Gailly, J-L.</a>, <a href="mailto:madler@alumni.caltech.edu">Adler, M.</a>, <a href="mailto:ghost@aladdin.com">Deutsch, L.</a>, and <a href="mailto:randeg@alumni.rpi.edu">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 might be less stable than this specification. On the other hand, this downward reference
    2858                was present since the publication of RFC 2068 in 1997 (<a href="#RFC2068" id="rfc.xref.RFC2068.7"><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>.
     2858               was present since the publication of <cite title="Hypertext Transfer Protocol -- HTTP/1.1" id="rfc.xref.RFC2068.7">RFC 2068</cite> in 1997, 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>.
    28592859            </td>
    28602860         </tr>
  • draft-ietf-httpbis/latest/p1-messaging.xml

    r1412 r1414  
    45934593    RFC 1950 is an Informational RFC, thus it might be less stable than
    45944594    this specification. On the other hand, this downward reference was
    4595     present since the publication of RFC 2068 in 1997 (<xref target="RFC2068"/>),
     4595    present since the publication of <xref target="RFC2068" x:fmt="none">RFC 2068</xref> in 1997,
    45964596    therefore it is unlikely to cause problems in practice. See also
    45974597    <xref target="BCP97"/>.
     
    46124612    RFC 1951 is an Informational RFC, thus it might be less stable than
    46134613    this specification. On the other hand, this downward reference was
    4614     present since the publication of RFC 2068 in 1997 (<xref target="RFC2068"/>),
     4614    present since the publication of <xref target="RFC2068" x:fmt="none">RFC 2068</xref> in 1997,
    46154615    therefore it is unlikely to cause problems in practice. See also
    46164616    <xref target="BCP97"/>.
     
    46434643    RFC 1952 is an Informational RFC, thus it might be less stable than
    46444644    this specification. On the other hand, this downward reference was
    4645     present since the publication of RFC 2068 in 1997 (<xref target="RFC2068"/>),
     4645    present since the publication of <xref target="RFC2068" x:fmt="none">RFC 2068</xref> in 1997,
    46464646    therefore it is unlikely to cause problems in practice. See also
    46474647    <xref target="BCP97"/>.
  • draft-ietf-httpbis/latest/p3-payload.html

    r1410 r1414  
    359359  }
    360360  @bottom-center {
    361        content: "Expires February 25, 2012";
     361       content: "Expires February 27, 2012";
    362362  }
    363363  @bottom-right {
     
    408408      <meta name="dct.creator" content="Reschke, J. F.">
    409409      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p3-payload-latest">
    410       <meta name="dct.issued" scheme="ISO8601" content="2011-08-24">
     410      <meta name="dct.issued" scheme="ISO8601" content="2011-08-26">
    411411      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    412412      <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 3 of the seven-part specification that defines the protocol referred to as &#34;HTTP/1.1&#34; and, taken together, obsoletes RFC 2616. Part 3 defines HTTP message content, metadata, and content negotiation.">
     
    434434            </tr>
    435435            <tr>
    436                <td class="left">Expires: February 25, 2012</td>
     436               <td class="left">Expires: February 27, 2012</td>
    437437               <td class="right">J. Mogul</td>
    438438            </tr>
     
    491491            <tr>
    492492               <td class="left"></td>
    493                <td class="right">August 24, 2011</td>
     493               <td class="right">August 26, 2011</td>
    494494            </tr>
    495495         </tbody>
     
    519519         in progress”.
    520520      </p>
    521       <p>This Internet-Draft will expire on February 25, 2012.</p>
     521      <p>This Internet-Draft will expire on February 27, 2012.</p>
    522522      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    523523      <p>Copyright © 2011 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
     
    15131513            <td class="reference"><b id="RFC1950">[RFC1950]</b></td>
    15141514            <td class="top"><a href="mailto:ghost@aladdin.com" title="Aladdin Enterprises">Deutsch, L.</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 might be less stable than this specification. On the other hand, this downward reference
    1515                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>.
     1515               was present since the publication of <cite title="Hypertext Transfer Protocol -- HTTP/1.1" id="rfc.xref.RFC2068.1">RFC 2068</cite> in 1997, 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>.
    15161516            </td>
    15171517         </tr>
     
    15191519            <td class="reference"><b id="RFC1951">[RFC1951]</b></td>
    15201520            <td class="top"><a href="mailto:ghost@aladdin.com" 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 might be less stable than this specification. On the other hand, this downward reference
    1521                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>.
     1521               was present since the publication of <cite title="Hypertext Transfer Protocol -- HTTP/1.1" id="rfc.xref.RFC2068.2">RFC 2068</cite> in 1997, 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>.
    15221522            </td>
    15231523         </tr>
     
    15251525            <td class="reference"><b id="RFC1952">[RFC1952]</b></td>
    15261526            <td class="top"><a href="mailto:ghost@aladdin.com" title="Aladdin Enterprises">Deutsch, P.</a>, <a href="mailto:gzip@prep.ai.mit.edu">Gailly, J-L.</a>, <a href="mailto:madler@alumni.caltech.edu">Adler, M.</a>, <a href="mailto:ghost@aladdin.com">Deutsch, L.</a>, and <a href="mailto:randeg@alumni.rpi.edu">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 might be less stable than this specification. On the other hand, this downward reference
    1527                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>.
     1527               was present since the publication of <cite title="Hypertext Transfer Protocol -- HTTP/1.1" id="rfc.xref.RFC2068.3">RFC 2068</cite> in 1997, 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>.
    15281528            </td>
    15291529         </tr>
  • draft-ietf-httpbis/latest/p3-payload.xml

    r1410 r1414  
    18681868    RFC 1950 is an Informational RFC, thus it might be less stable than
    18691869    this specification. On the other hand, this downward reference was
    1870     present since the publication of RFC 2068 in 1997 (<xref target="RFC2068"/>),
     1870    present since the publication of <xref target="RFC2068" x:fmt="none">RFC 2068</xref> in 1997,
    18711871    therefore it is unlikely to cause problems in practice. See also
    18721872    <xref target="BCP97"/>.
     
    18871887    RFC 1951 is an Informational RFC, thus it might be less stable than
    18881888    this specification. On the other hand, this downward reference was
    1889     present since the publication of RFC 2068 in 1997 (<xref target="RFC2068"/>),
     1889    present since the publication of <xref target="RFC2068" x:fmt="none">RFC 2068</xref> in 1997,
    18901890    therefore it is unlikely to cause problems in practice. See also
    18911891    <xref target="BCP97"/>.
     
    19181918    RFC 1952 is an Informational RFC, thus it might be less stable than
    19191919    this specification. On the other hand, this downward reference was
    1920     present since the publication of RFC 2068 in 1997 (<xref target="RFC2068"/>),
     1920    present since the publication of <xref target="RFC2068" x:fmt="none">RFC 2068</xref> in 1997,
    19211921    therefore it is unlikely to cause problems in practice. See also
    19221922    <xref target="BCP97"/>.
Note: See TracChangeset for help on using the changeset viewer.