Ignore:
Timestamp:
Jun 23, 2012, 5:01:38 AM (7 years ago)
Author:
julian.reschke@…
Message:

Simplify use of "Note:", make upper/lowercase of sentence start consistent; use "—" where appropriate

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

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p0-introduction.html

    • Property svn:eol-style set to native
    • Property svn:mime-type set to text/html;charset=utf-8
    r1689 r1692  
    374374  }
    375375  @bottom-center {
    376        content: "Expires December 24, 2012";
     376       content: "Expires December 25, 2012";
    377377  }
    378378  @bottom-right {
     
    405405      <meta name="dct.creator" content="Reschke, J. F.">
    406406      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p0-introduction-latest">
    407       <meta name="dct.issued" scheme="ISO8601" content="2012-06-22">
     407      <meta name="dct.issued" scheme="ISO8601" content="2012-06-23">
    408408      <meta name="dct.abstract" content="TODO">
    409409      <meta name="description" content="TODO">
     
    425425            </tr>
    426426            <tr>
    427                <td class="left">Expires: December 24, 2012</td>
     427               <td class="left">Expires: December 25, 2012</td>
    428428               <td class="right">W3C</td>
    429429            </tr>
     
    446446            <tr>
    447447               <td class="left"></td>
    448                <td class="right">June 22, 2012</td>
     448               <td class="right">June 23, 2012</td>
    449449            </tr>
    450450         </tbody>
     
    469469         in progress”.
    470470      </p>
    471       <p>This Internet-Draft will expire on December 24, 2012.</p>
     471      <p>This Internet-Draft will expire on December 25, 2012.</p>
    472472      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    473473      <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
  • draft-ietf-httpbis/latest/p1-messaging.html

    r1689 r1692  
    449449  }
    450450  @bottom-center {
    451        content: "Expires December 24, 2012";
     451       content: "Expires December 25, 2012";
    452452  }
    453453  @bottom-right {
     
    491491      <meta name="dct.creator" content="Reschke, J. F.">
    492492      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p1-messaging-latest">
    493       <meta name="dct.issued" scheme="ISO8601" content="2012-06-22">
     493      <meta name="dct.issued" scheme="ISO8601" content="2012-06-23">
    494494      <meta name="dct.replaces" content="urn:ietf:rfc:2145">
    495495      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
     
    523523            </tr>
    524524            <tr>
    525                <td class="left">Expires: December 24, 2012</td>
     525               <td class="left">Expires: December 25, 2012</td>
    526526               <td class="right">greenbytes</td>
    527527            </tr>
    528528            <tr>
    529529               <td class="left"></td>
    530                <td class="right">June 22, 2012</td>
     530               <td class="right">June 23, 2012</td>
    531531            </tr>
    532532         </tbody>
     
    561561         in progress”.
    562562      </p>
    563       <p>This Internet-Draft will expire on December 24, 2012.</p>
     563      <p>This Internet-Draft will expire on December 25, 2012.</p>
    564564      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    565565      <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
  • draft-ietf-httpbis/latest/p1-messaging.xml

    r1689 r1692  
    1616  <!ENTITY ID-YEAR "2012">
    1717  <!ENTITY mdash "&#8212;">
     18  <!ENTITY Note "<x:h xmlns:x='http://purl.org/net/xml2rfc/ext'>Note:</x:h>">
    1819  <!ENTITY caching-overview       "<xref target='Part6' x:rel='#caching.overview' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    1920  <!ENTITY cache-incomplete       "<xref target='Part6' x:rel='#response.cacheability' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     
    308309<x:note>
    309310  <t>
    310     <x:h>Note:</x:h> The term 'user agent' covers both those situations where
     311    &Note; The term 'user agent' covers both those situations where
    311312    there is a user (human) interacting with the software agent (and for which
    312313    user interface or interactive suggestions might be made, e.g., warning the
     
    11871188<x:note>
    11881189  <t>
    1189    <x:h>Note:</x:h> The "Set-Cookie" header field as implemented in
     1190   &Note; The "Set-Cookie" header field as implemented in
    11901191   practice can occur multiple times, but does not use the list syntax, and
    11911192   thus cannot be combined into a single line (<xref target="RFC6265"/>). (See Appendix A.2.3 of <xref target="Kri2001"/>
     
    19781979</t>
    19791980<x:note><t>
    1980    <x:h>Note:</x:h> Use of program names for the identification of encoding formats
     1981   &Note; Use of program names for the identification of encoding formats
    19811982   is not desirable and is discouraged for future encodings. Their
    19821983   use here is representative of historical practice, not good
     
    19841985</t></x:note>
    19851986<x:note><t>
    1986    <x:h>Note:</x:h> For compatibility with previous implementations of HTTP,
     1987   &Note; For compatibility with previous implementations of HTTP,
    19871988   applications &SHOULD; consider "x-gzip" and "x-compress" to be
    19881989   equivalent to "gzip" and "compress" respectively.
     
    20092010<x:note>
    20102011  <t>
    2011     <x:h>Note:</x:h> Some incorrect implementations send the "deflate"
     2012    &Note; Some incorrect implementations send the "deflate"
    20122013    compressed data without the zlib wrapper.
    20132014   </t>
     
    20842085         response on behalf of downstream recipients.
    20852086      </t><t>
    2086          <x:h>Note:</x:h> HTTP/1.1 does not define any means to limit the size of a
     2087         &Note; HTTP/1.1 does not define any means to limit the size of a
    20872088         chunked response such that a client can be assured of buffering
    20882089         the entire response.</t>
     
    21282129<x:note>
    21292130  <t>
    2130      <x:h>Note:</x:h> "Quality values" is a misnomer, since these values merely represent
     2131     &Note; "Quality values" is a misnomer, since these values merely represent
    21312132     relative degradation in desired quality.
    21322133  </t>
  • draft-ietf-httpbis/latest/p2-semantics.html

    r1689 r1692  
    449449  }
    450450  @bottom-center {
    451        content: "Expires December 24, 2012";
     451       content: "Expires December 25, 2012";
    452452  }
    453453  @bottom-right {
     
    497497      <meta name="dct.creator" content="Reschke, J. F.">
    498498      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p2-semantics-latest">
    499       <meta name="dct.issued" scheme="ISO8601" content="2012-06-22">
     499      <meta name="dct.issued" scheme="ISO8601" content="2012-06-23">
    500500      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    501501      <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 2 of the seven-part specification that defines the protocol referred to as &#34;HTTP/1.1&#34; and, taken together, obsoletes RFC 2616. Part 2 defines the semantics of HTTP messages as expressed by request methods, request header fields, response status codes, and response header fields. Furthermore, it defines HTTP message content, metadata, and content negotiation.">
     
    528528            </tr>
    529529            <tr>
    530                <td class="left">Expires: December 24, 2012</td>
     530               <td class="left">Expires: December 25, 2012</td>
    531531               <td class="right">greenbytes</td>
    532532            </tr>
    533533            <tr>
    534534               <td class="left"></td>
    535                <td class="right">June 22, 2012</td>
     535               <td class="right">June 23, 2012</td>
    536536            </tr>
    537537         </tbody>
     
    563563         in progress”.
    564564      </p>
    565       <p>This Internet-Draft will expire on December 24, 2012.</p>
     565      <p>This Internet-Draft will expire on December 25, 2012.</p>
    566566      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    567567      <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
  • draft-ietf-httpbis/latest/p2-semantics.xml

    r1689 r1692  
    1616  <!ENTITY ID-YEAR "2012">
    1717  <!ENTITY mdash "&#8212;">
     18  <!ENTITY Note "<x:h xmlns:x='http://purl.org/net/xml2rfc/ext'>Note:</x:h>">
    1819  <!ENTITY architecture               "<xref target='Part1' x:rel='#architecture' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    1920  <!ENTITY notation                   "<xref target='Part1' x:rel='#notation' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     
    15421543<x:note>
    15431544  <t>
    1544     <x:h>Note:</x:h> In HTTP/1.0, only the status codes 301 (Moved Permanently)
     1545    &Note; In HTTP/1.0, only the status codes 301 (Moved Permanently)
    15451546    and 302 (Found) were defined for the first type of redirect, and the second
    15461547    type did not exist at all (<xref target="RFC1945" x:fmt="," x:sec="9.3"/>).
     
    15731574<x:note>
    15741575  <t>
    1575     <x:h>Note:</x:h> An earlier version of this specification recommended a
     1576    &Note; An earlier version of this specification recommended a
    15761577    maximum of five redirections (<xref target="RFC2068" x:fmt="," x:sec="10.3"/>).
    15771578    Content developers need to be aware that some clients might
     
    16331634<x:note>
    16341635  <t>
    1635     <x:h>Note:</x:h> For historic reasons, user agents &MAY; change the
     1636    &Note; For historic reasons, user agents &MAY; change the
    16361637    request method from POST to GET for the subsequent request. If this
    16371638    behavior is undesired, status code 307 (Temporary Redirect) can be used
     
    16561657<x:note>
    16571658  <t>
    1658     <x:h>Note:</x:h> For historic reasons, user agents &MAY; change the
     1659    &Note; For historic reasons, user agents &MAY; change the
    16591660    request method from POST to GET for the subsequent request. If this
    16601661    behavior is undesired, status code 307 (Temporary Redirect) can be used
     
    17391740<x:note>
    17401741  <t>
    1741     <x:h>Note:</x:h> This status code is similar to 302 Found, except that
     1742    &Note; This status code is similar to 302 Found, except that
    17421743    it does not allow rewriting the request method from POST to GET. This
    17431744    specification defines no equivalent counterpart for 301 Moved Permanently
     
    18381839<x:note>
    18391840  <t>
    1840     <x:h>Note:</x:h> HTTP/1.1 servers are allowed to return responses which are
     1841    &Note; HTTP/1.1 servers are allowed to return responses which are
    18411842    not acceptable according to the accept header fields sent in the
    18421843    request. In some cases, this might even be preferable to sending a
     
    20632064<x:note>
    20642065  <t>
    2065     <x:h>Note:</x:h> The existence of the 503 status code does not imply that a
     2066    &Note; The existence of the 503 status code does not imply that a
    20662067    server has to use it when becoming overloaded. Some servers might wish
    20672068    to simply refuse the connection.
     
    22342235<x:note>
    22352236  <t>
    2236     <x:h>Note:</x:h> Recipients of date values are encouraged to be robust in
     2237    &Note; Recipients of date values are encouraged to be robust in
    22372238    accepting date values that might have been sent by non-HTTP
    22382239    applications, as is sometimes the case when retrieving or posting
     
    22422243<x:note>
    22432244  <t>
    2244     <x:h>Note:</x:h> HTTP requirements for the date/time stamp format apply only
     2245    &Note; HTTP requirements for the date/time stamp format apply only
    22452246    to their usage within the protocol stream. Clients and servers are
    22462247    not required to use these formats for user presentation, request
     
    25002501<x:note>
    25012502  <t>
    2502     <x:h>Note:</x:h> The "multipart/form-data" type has been specifically defined
     2503    &Note; The "multipart/form-data" type has been specifically defined
    25032504    for carrying form data suitable for processing via the POST
    25042505    request method, as described in <xref target="RFC2388"/>.
     
    28672868<x:note>
    28682869  <t>
    2869     <x:h>Note:</x:h> In practice, User-Agent based negotiation is fragile,
     2870    &Note; In practice, User-Agent based negotiation is fragile,
    28702871    because new clients might not be recognized.
    28712872  </t>
     
    29622963<x:note>
    29632964  <t>
    2964     <x:h>Note:</x:h> Use of the "q" parameter name to separate media type
     2965    &Note; Use of the "q" parameter name to separate media type
    29652966    parameters from Accept extension parameters is due to historical
    29662967    practice. Although this prevents any media type parameter named
     
    30443045</texttable>
    30453046<t>
    3046       <x:h>Note:</x:h> A user agent might be provided with a default set of quality
    3047       values for certain media ranges. However, unless the user agent is
    3048       a closed system which cannot interact with other rendering agents,
    3049       this default set ought to be configurable by the user.
     3047   &Note; A user agent might be provided with a default set of quality
     3048   values for certain media ranges. However, unless the user agent is
     3049   a closed system which cannot interact with other rendering agents,
     3050   this default set ought to be configurable by the user.
    30503051</t>
    30513052</section>
     
    31613162<x:note>
    31623163  <t>
    3163     <x:h>Note:</x:h> Most HTTP/1.0 applications do not recognize or obey qvalues
     3164    &Note; Most HTTP/1.0 applications do not recognize or obey qvalues
    31643165    associated with content-codings. This means that qvalues will not
    31653166    work and are not permitted with x-gzip or x-compress.
     
    32053206<x:note>
    32063207  <t>
    3207     <x:h>Note:</x:h> The "Basic Filtering" scheme (<xref target="RFC4647"
     3208    &Note; The "Basic Filtering" scheme (<xref target="RFC4647"
    32083209    x:fmt="," x:sec="3.3.1"/>) is identical to the matching scheme that was
    32093210    previously defined in <xref target="RFC2616" x:fmt="of" x:sec="14.4"/>.
     
    32253226<x:note>
    32263227  <t>
    3227     <x:h>Note:</x:h> When making the choice of linguistic preference available to
     3228    &Note; When making the choice of linguistic preference available to
    32283229    the user, we remind implementors of  the fact that users are not
    32293230    familiar with the details of language matching as described above,
     
    36933694<x:note>
    36943695  <t>
    3695     <x:h>Note:</x:h> Some recipients attempt to recover from Location fields
     3696    &Note; Some recipients attempt to recover from Location fields
    36963697    that are not valid URI references. This specification does not mandate or
    36973698    define such processing, but does allow it (see <xref target="intro.conformance.and.error.handling"/>).
     
    37063707<x:note>
    37073708  <t>
    3708     <x:h>Note:</x:h> The Content-Location header field (&header-content-location;) differs
     3709    &Note; The Content-Location header field (&header-content-location;) differs
    37093710    from Location in that the Content-Location identifies the most specific
    37103711    resource corresponding to the enclosed representation.
     
    38563857<x:note>
    38573858  <t>
    3858     <x:h>Note:</x:h> Revealing the specific software version of the server might
     3859    &Note; Revealing the specific software version of the server might
    38593860    allow the server machine to become more vulnerable to attacks
    38603861    against software that is known to contain security holes. Server
  • draft-ietf-httpbis/latest/p3-payload.html

    r1689 r1692  
    374374  }
    375375  @bottom-center {
    376        content: "Expires December 24, 2012";
     376       content: "Expires December 25, 2012";
    377377  }
    378378  @bottom-right {
     
    404404      <meta name="dct.creator" content="Reschke, J. F.">
    405405      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p3-payload-latest">
    406       <meta name="dct.issued" scheme="ISO8601" content="2012-06-22">
     406      <meta name="dct.issued" scheme="ISO8601" content="2012-06-23">
    407407      <meta name="dct.abstract" content="This part is now obsolete. Please see HTTPbis, Part 2.">
    408408      <meta name="description" content="This part is now obsolete. Please see HTTPbis, Part 2.">
     
    424424            </tr>
    425425            <tr>
    426                <td class="left">Expires: December 24, 2012</td>
     426               <td class="left">Expires: December 25, 2012</td>
    427427               <td class="right">W3C</td>
    428428            </tr>
     
    437437            <tr>
    438438               <td class="left"></td>
    439                <td class="right">June 22, 2012</td>
     439               <td class="right">June 23, 2012</td>
    440440            </tr>
    441441         </tbody>
     
    453453         in progress”.
    454454      </p>
    455       <p>This Internet-Draft will expire on December 24, 2012.</p>
     455      <p>This Internet-Draft will expire on December 25, 2012.</p>
    456456      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    457457      <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
  • draft-ietf-httpbis/latest/p4-conditional.xml

    r1691 r1692  
    1515  <!ENTITY ID-MONTH "June">
    1616  <!ENTITY ID-YEAR "2012">
     17  <!ENTITY Note "<x:h xmlns:x='http://purl.org/net/xml2rfc/ext'>Note:</x:h>">
    1718  <!ENTITY architecture               "<xref target='Part1' x:rel='#architecture' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    1819  <!ENTITY notation                   "<xref target='Part1' x:rel='#notation' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     
    484485<x:note>
    485486  <t>
    486     <x:h>Note:</x:h> Previously, opaque-tag was defined to be a quoted-string
     487    &Note; Previously, opaque-tag was defined to be a quoted-string
    487488    (<xref target="RFC2616" x:fmt="," x:sec="3.11"/>), thus some recipients
    488489    might perform backslash unescaping. Servers therefore ought to avoid
     
    635636<x:note>
    636637  <t>
    637     <x:h>Note:</x:h> Content codings are a property of the representation,
     638    &Note; Content codings are a property of the representation,
    638639    so therefore an entity-tag of an encoded representation has to be distinct
    639640    from an unencoded representation to prevent conflicts during cache updates
     
    706707   conditional header fields in the request.
    707708  <list><t>
    708       <x:h>Note:</x:h> The general principle behind these rules is that HTTP/1.1
     709      &Note; The general principle behind these rules is that HTTP/1.1
    709710      servers and clients ought to transmit as much non-redundant
    710711      information as is available in their responses and requests.
     
    897898   information with a minimum amount of transaction overhead.
    898899  <list><t>
    899       <x:h>Note:</x:h> The Range header field modifies the meaning of If-Modified-Since;
     900      &Note; The Range header field modifies the meaning of If-Modified-Since;
    900901      see &header-range; for full details.
    901902    </t><t>
    902       <x:h>Note:</x:h> If-Modified-Since times are interpreted by the server, whose
     903      &Note; If-Modified-Since times are interpreted by the server, whose
    903904      clock might not be synchronized with the client.
    904905    </t><t>
    905       <x:h>Note:</x:h> When handling an If-Modified-Since header field, some
     906      &Note; When handling an If-Modified-Since header field, some
    906907      servers will use an exact date comparison function, rather than a
    907908      less-than function, for deciding whether to send a 304 (Not
     
    911912      header field whenever possible.
    912913    </t><t>
    913       <x:h>Note:</x:h> If a client uses an arbitrary date in the If-Modified-Since
     914      &Note; If a client uses an arbitrary date in the If-Modified-Since
    914915      header field instead of a date taken from the Last-Modified header field for
    915916      the same request, the client needs to be aware that this
  • draft-ietf-httpbis/latest/p5-range.html

    r1689 r1692  
    449449  }
    450450  @bottom-center {
    451        content: "Expires December 24, 2012";
     451       content: "Expires December 25, 2012";
    452452  }
    453453  @bottom-right {
     
    492492      <meta name="dct.creator" content="Reschke, J. F.">
    493493      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p5-range-latest">
    494       <meta name="dct.issued" scheme="ISO8601" content="2012-06-22">
     494      <meta name="dct.issued" scheme="ISO8601" content="2012-06-23">
    495495      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    496496      <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 5 of the seven-part specification that defines the protocol referred to as &#34;HTTP/1.1&#34; and, taken together, obsoletes RFC 2616. Part 5 defines range requests and the rules for constructing and combining responses to those requests.">
     
    518518            </tr>
    519519            <tr>
    520                <td class="left">Expires: December 24, 2012</td>
     520               <td class="left">Expires: December 25, 2012</td>
    521521               <td class="right">J. Reschke, Editor</td>
    522522            </tr>
     
    527527            <tr>
    528528               <td class="left"></td>
    529                <td class="right">June 22, 2012</td>
     529               <td class="right">June 23, 2012</td>
    530530            </tr>
    531531         </tbody>
     
    555555         in progress”.
    556556      </p>
    557       <p>This Internet-Draft will expire on December 24, 2012.</p>
     557      <p>This Internet-Draft will expire on December 25, 2012.</p>
    558558      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    559559      <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
  • draft-ietf-httpbis/latest/p5-range.xml

    r1689 r1692  
    1515  <!ENTITY ID-MONTH "June">
    1616  <!ENTITY ID-YEAR "2012">
     17  <!ENTITY Note "<x:h xmlns:x='http://purl.org/net/xml2rfc/ext'>Note:</x:h>">
    1718  <!ENTITY architecture               "<xref target='Part1' x:rel='#architecture' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    1819  <!ENTITY notation                   "<xref target='Part1' x:rel='#notation' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     
    376377<x:note>
    377378  <t>
    378     <x:h>Note:</x:h> Clients cannot depend on servers to send a 416 (Requested
     379    &Note; Clients cannot depend on servers to send a 416 (Requested
    379380    range not satisfiable) response instead of a 200 (OK) response for
    380381    an unsatisfiable Range header field, since not all servers
     
    12281229<x:note>
    12291230  <t>
    1230     <x:h>Note:</x:h> Despite the name "multipart/byteranges" is not limited to the byte ranges only.
     1231    &Note; Despite the name "multipart/byteranges" is not limited to the byte ranges only.
    12311232  </t>
    12321233</x:note>
  • draft-ietf-httpbis/latest/p6-cache.html

    r1689 r1692  
    452452  }
    453453  @bottom-center {
    454        content: "Expires December 24, 2012";
     454       content: "Expires December 25, 2012";
    455455  }
    456456  @bottom-right {
     
    494494      <meta name="dct.creator" content="Reschke, J. F.">
    495495      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p6-cache-latest">
    496       <meta name="dct.issued" scheme="ISO8601" content="2012-06-22">
     496      <meta name="dct.issued" scheme="ISO8601" content="2012-06-23">
    497497      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    498498      <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 6 of the seven-part specification that defines the protocol referred to as &#34;HTTP/1.1&#34; and, taken together, obsoletes RFC 2616. Part 6 defines requirements on HTTP caches and the associated header fields that control cache behavior or indicate cacheable response messages.">
     
    520520            </tr>
    521521            <tr>
    522                <td class="left">Expires: December 24, 2012</td>
     522               <td class="left">Expires: December 25, 2012</td>
    523523               <td class="right">M. Nottingham, Editor</td>
    524524            </tr>
     
    537537            <tr>
    538538               <td class="left"></td>
    539                <td class="right">June 22, 2012</td>
     539               <td class="right">June 23, 2012</td>
    540540            </tr>
    541541         </tbody>
     
    567567         in progress”.
    568568      </p>
    569       <p>This Internet-Draft will expire on December 24, 2012.</p>
     569      <p>This Internet-Draft will expire on December 25, 2012.</p>
    570570      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    571571      <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
     
    923923</pre> <p id="rfc.section.2.3.p.6">The freshness_lifetime is defined in <a href="#calculating.freshness.lifetime" title="Calculating Freshness Lifetime">Section&nbsp;2.3.1</a>; the current_age is defined in <a href="#age.calculations" title="Calculating Age">Section&nbsp;2.3.2</a>.
    924924      </p>
    925       <p id="rfc.section.2.3.p.7">Additionally, clients can influence freshness calculation -- either constraining it relaxing it -- by using the max-age and
     925      <p id="rfc.section.2.3.p.7">Additionally, clients can influence freshness calculation — either constraining it relaxing it — by using the max-age and
    926926         min-fresh request cache directives. See <a href="#cache-request-directive" title="Request Cache-Control Directives">Section&nbsp;3.2.1</a> for details.
    927927      </p>
     
    13261326            case-insensitive.
    13271327         </li>
    1328          <li> <b>Note:</b> This usage of the word "private" only controls where the response can be stored; it cannot ensure the privacy of the message
     1328         <li><b>Note:</b> This usage of the word "private" only controls where the response can be stored; it cannot ensure the privacy of the message
    13291329            content. Also, private response directives with field-names are often handled by implementations as if an unqualified private
    13301330            directive was received; i.e., the special handling for the qualified form is not widely implemented.
     
    13451345            case-insensitive.
    13461346         </li>
    1347          <li> <b>Note:</b> Most HTTP/1.0 caches will not recognize or obey this directive. Also, no-cache response directives with field-names are often
     1347         <li><b>Note:</b> Most HTTP/1.0 caches will not recognize or obey this directive. Also, no-cache response directives with field-names are often
    13481348            handled by implementations as if an unqualified no-cache directive was received; i.e., the special handling for the qualified
    13491349            form is not widely implemented.
  • draft-ietf-httpbis/latest/p6-cache.xml

    r1689 r1692  
    1515  <!ENTITY ID-MONTH "June">
    1616  <!ENTITY ID-YEAR "2012">
     17  <!ENTITY mdash "&#8212;">
     18  <!ENTITY Note "<x:h xmlns:x='http://purl.org/net/xml2rfc/ext'>Note:</x:h>">
    1719  <!ENTITY architecture                "<xref target='Part1' x:rel='#architecture' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    1820  <!ENTITY notation                    "<xref target='Part1' x:rel='#notation' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     
    635637</t>
    636638<t>
    637    Additionally, clients can influence freshness calculation -- either
    638    constraining it relaxing it -- by using the max-age and min-fresh
     639   Additionally, clients can influence freshness calculation &mdash; either
     640   constraining it relaxing it &mdash; by using the max-age and min-fresh
    639641   request cache directives. See <xref target="cache-request-directive" />
    640642   for details.
     
    694696<x:note>
    695697   <t>
    696       <x:h>Note:</x:h> RFC 2616 (<xref target="RFC2616" x:fmt=","
     698      &Note; RFC 2616 (<xref target="RFC2616" x:fmt=","
    697699      x:sec="13.9"/>) required that caches do not calculate heuristic
    698700      freshness for URIs with query components (i.e., those containing '?').
     
    12011203<x:note>
    12021204   <t>
    1203        <x:h>Note:</x:h> HTTP/1.0 caches might not implement Cache-Control and
     1205       &Note; HTTP/1.0 caches might not implement Cache-Control and
    12041206       might only implement Pragma: no-cache (see <xref target="header.pragma"
    12051207       />).
     
    13791381      fields defined by this specification. Field names are case-insensitive.
    13801382      </t>
    1381       <t> <x:h>Note:</x:h> This usage of the word "private" only controls
     1383      <t>&Note; This usage of the word "private" only controls
    13821384      where the response can be stored; it cannot ensure the privacy of the
    13831385      message content. Also, private response directives with field-names are
     
    14081410      fields defined by this specification. Field names are case-insensitive.
    14091411      </t>
    1410       <t> <x:h>Note:</x:h> Most HTTP/1.0 caches will not recognize or obey
     1412      <t>&Note; Most HTTP/1.0 caches will not recognize or obey
    14111413      this directive. Also, no-cache response directives with field-names are
    14121414      often handled by implementations as if an unqualified no-cache directive
     
    15981600<x:note>
    15991601   <t>
    1600        <x:h>Note:</x:h> If a response includes a Cache-Control field with the
     1602       &Note; If a response includes a Cache-Control field with the
    16011603       max-age directive (see <xref target="cache-response-directive" />),
    16021604       that directive overrides the Expires field. Likewise, the s-maxage
     
    16741676<x:note>
    16751677   <t>
    1676       <x:h>Note:</x:h> Because the meaning of "Pragma: no-cache" in responses is not
     1678      &Note; Because the meaning of "Pragma: no-cache" in responses is not
    16771679      specified, it does not provide a reliable replacement for
    16781680      "Cache-Control: no-cache" in them.
  • draft-ietf-httpbis/latest/p7-auth.html

    r1689 r1692  
    449449  }
    450450  @bottom-center {
    451        content: "Expires December 24, 2012";
     451       content: "Expires December 25, 2012";
    452452  }
    453453  @bottom-right {
     
    489489      <meta name="dct.creator" content="Reschke, J. F.">
    490490      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p7-auth-latest">
    491       <meta name="dct.issued" scheme="ISO8601" content="2012-06-22">
     491      <meta name="dct.issued" scheme="ISO8601" content="2012-06-23">
    492492      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    493493      <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 7 of the seven-part specification that defines the protocol referred to as &#34;HTTP/1.1&#34; and, taken together, obsoletes RFC 2616. Part 7 defines the HTTP Authentication framework.">
     
    520520            </tr>
    521521            <tr>
    522                <td class="left">Expires: December 24, 2012</td>
     522               <td class="left">Expires: December 25, 2012</td>
    523523               <td class="right">greenbytes</td>
    524524            </tr>
    525525            <tr>
    526526               <td class="left"></td>
    527                <td class="right">June 22, 2012</td>
     527               <td class="right">June 23, 2012</td>
    528528            </tr>
    529529         </tbody>
     
    553553         in progress”.
    554554      </p>
    555       <p>This Internet-Draft will expire on December 24, 2012.</p>
     555      <p>This Internet-Draft will expire on December 25, 2012.</p>
    556556      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    557557      <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
     
    784784               can use a generic parser that applies to all authentication schemes.
    785785            </p>
    786             <p> <b>Note:</b> the fact that the value syntax for the "realm" parameter is restricted to quoted-string was a bad design choice not to be
     786            <p> <b>Note:</b> The fact that the value syntax for the "realm" parameter is restricted to quoted-string was a bad design choice not to be
    787787               repeated for new parameters.
    788788            </p>
  • draft-ietf-httpbis/latest/p7-auth.xml

    r1689 r1692  
    1616  <!ENTITY ID-YEAR "2012">
    1717  <!ENTITY mdash "&#8212;">
     18  <!ENTITY Note "<x:h xmlns:x='http://purl.org/net/xml2rfc/ext'>Note:</x:h>">
    1819  <!ENTITY architecture                 "<xref target='Part1' x:rel='#architecture' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    1920  <!ENTITY notation                     "<xref target='Part1' x:rel='#notation' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     
    272273<x:note>
    273274  <t>
    274      <x:h>Note:</x:h> User agents will need to take special care in parsing the
     275     &Note; User agents will need to take special care in parsing the
    275276     WWW-Authenticate and Proxy-Authenticate header field values because they
    276277     can contain more than one challenge, or if more than one of each is
     
    281282<x:note>
    282283  <t>
    283      <x:h>Note:</x:h> Many clients fail to parse challenges containing unknown
     284     &Note; Many clients fail to parse challenges containing unknown
    284285     schemes. A workaround for this problem is to list well-supported schemes
    285286     (such as "basic") first.<!-- see http://greenbytes.de/tech/tc/httpauth/#multibasicunknown2 -->
     
    447448    </t>
    448449    <t>
    449       <x:h>Note:</x:h> the fact that the value syntax for the "realm" parameter
     450      &Note; The fact that the value syntax for the "realm" parameter
    450451      is restricted to quoted-string was a bad design choice not to be repeated
    451452      for new parameters.
     
    675676<x:note>
    676677  <t>
    677     <x:h>Note:</x:h> The challenge grammar production uses the list syntax as
     678    &Note; The challenge grammar production uses the list syntax as
    678679    well. Therefore, a sequence of comma, whitespace, and comma can be
    679680    considered both as applying to the preceding challenge, or to be an
Note: See TracChangeset for help on using the changeset viewer.