Changeset 2184

Timestamp:

Feb 19, 2013, 4:38:12 AM (7 years ago)

Author:

julian.reschke@…

Message:

restore consistency in section names

Location:

draft-ietf-httpbis/latest

Files:

• p2-semantics.html (modified) (8 diffs)
• p2-semantics.xml (modified) (1 diff)

draft-ietf-httpbis/latest/p2-semantics.html

@@ -449 +449 @@
   } 
   @bottom-center {
-       content: "Expires August 15, 2013"; 
+       content: "Expires August 23, 2013"; 
   } 
   @bottom-right {
@@ -483 +483 @@
       <link rel="Chapter" href="#rfc.section.11" title="11 References">
       <link rel="Appendix" title="A Differences between HTTP and MIME" href="#rfc.section.A">
-      <link rel="Appendix" title="B Significant changes from RFC 2616" href="#rfc.section.B">
+      <link rel="Appendix" title="B Changes from RFC 2616" href="#rfc.section.B">
       <link rel="Appendix" title="C Imported ABNF" href="#rfc.section.C">
       <link rel="Appendix" title="D Collected ABNF" href="#rfc.section.D">
@@ -494 +494 @@
       <meta name="dct.creator" content="Reschke, J. F.">
       <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p2-semantics-latest">
-      <meta name="dct.issued" scheme="ISO8601" content="2013-02-11">
+      <meta name="dct.issued" scheme="ISO8601" content="2013-02-19">
       <meta name="dct.replaces" content="urn:ietf:rfc:2616">
       <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. This document defines the semantics of HTTP/1.1 messages, as expressed by request methods, request header fields, response status codes, and response header fields, along with the payload of messages (metadata and body content) and mechanisms for content negotiation.">
@@ -522 +522 @@
             <tr>
                <td class="left">Intended status: Standards Track</td>
-               <td class="right">February 11, 2013</td>
+               <td class="right">February 19, 2013</td>
             </tr>
             <tr>
-               <td class="left">Expires: August 15, 2013</td>
+               <td class="left">Expires: August 23, 2013</td>
                <td class="right"></td>
             </tr>
@@ -553 +553 @@
          in progress”.
       </p>
-      <p>This Internet-Draft will expire on August 15, 2013.</p>
+      <p>This Internet-Draft will expire on August 23, 2013.</p>
       <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
       <p>Copyright © 2013 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
@@ -787 +787 @@
             </ul>
          </li>
-         <li><a href="#rfc.section.B">B.</a>&nbsp;&nbsp;&nbsp;<a href="#changes.from.rfc.2616">Significant changes from RFC 2616</a></li>
+         <li><a href="#rfc.section.B">B.</a>&nbsp;&nbsp;&nbsp;<a href="#changes.from.rfc.2616">Changes from RFC 2616</a></li>
          <li><a href="#rfc.section.C">C.</a>&nbsp;&nbsp;&nbsp;<a href="#imported.abnf">Imported ABNF</a></li>
          <li><a href="#rfc.section.D">D.</a>&nbsp;&nbsp;&nbsp;<a href="#collected.abnf">Collected ABNF</a></li>
@@ -2630 +2630 @@
       <div id="rfc.iref.75"></div>
       <h3 id="rfc.section.6.4.5"><a href="#rfc.section.6.4.5">6.4.5</a>&nbsp;<a id="status.305" href="#status.305">305 Use Proxy</a></h3>
-      <p id="rfc.section.6.4.5.p.1">The <dfn>305 (Use Proxy)</dfn> status code was defined in a previous version of this specification and is now deprecated (<a href="#changes.from.rfc.2616" title="Significant changes from RFC 2616">Appendix&nbsp;B</a>).
+      <p id="rfc.section.6.4.5.p.1">The <dfn>305 (Use Proxy)</dfn> status code was defined in a previous version of this specification and is now deprecated (<a href="#changes.from.rfc.2616" title="Changes from RFC 2616">Appendix&nbsp;B</a>).
       </p>
       <div id="rfc.iref.75"></div>
@@ -4173 +4173 @@
          type (<a href="p5-range.html#internet.media.type.multipart.byteranges" title="Internet Media Type multipart/byteranges">Appendix A</a> of <a href="#Part5" id="rfc.xref.Part5.12"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Range Requests">[Part5]</cite></a>), does not interpret the content or any MIME header lines that might be contained therein.
       </p>
-      <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a>&nbsp;<a id="changes.from.rfc.2616" href="#changes.from.rfc.2616">Significant changes from RFC 2616</a></h1>
+      <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a>&nbsp;<a id="changes.from.rfc.2616" href="#changes.from.rfc.2616">Changes from RFC 2616</a></h1>
       <p id="rfc.section.B.p.1">The primary changes in this revision have been editorial in nature: extracting the messaging syntax and partitioning HTTP
          semantics into separate documents for the core features, conditional requests, partial requests, caching, and authentication.

draft-ietf-httpbis/latest/p2-semantics.xml

@@ -5823 +5823 @@
 </section>
 
-<section title="Significant changes from RFC 2616" anchor="changes.from.rfc.2616">
+<section title="Changes from RFC 2616" anchor="changes.from.rfc.2616">
 <t>
    The primary changes in this revision have been editorial in nature: