Changeset 452

Timestamp:

Feb 27, 2009, 8:29:00 PM (11 years ago)

Author:

fielding@…

Message:

editorial: Fix typos and leftovers noted by Julian.
Added a TBD section for https.
Moved RFC 2045 to Informational References.
Specifically reference percent-encoding in RFC3986.

File:

• draft-ietf-httpbis/latest/p1-messaging.xml (modified) (8 diffs)

draft-ietf-httpbis/latest/p1-messaging.xml

@@ -568 +568 @@
 <t>
    The "http" scheme is used to locate network resources via the HTTP
-   protocol. This section defines the syntax and semantics for identifiers
-   using the http or https URI schemes.
+   protocol.
 </t>
 <figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="http-URI"/>
@@ -587 +586 @@
    name.
 </t>
+</section>
+
+<section title="https URI scheme" anchor="https.uri">
+   <iref item="https URI scheme"/>
+   <iref item="URI scheme" subitem="https"/>
+<t>
+   <cref>TBD: Define and explain purpose of https scheme.</cref>
+</t>
 <t><list><t>
-  <iref item="https URI scheme"/>
-  <iref item="URI scheme" subitem="https"/>
   <x:h>Note:</x:h> the "https" scheme is defined in <xref target="RFC2818"/>.
 </t></list></t>
@@ -604 +609 @@
     <t>Comparisons of host names &MUST; be case-insensitive;</t>
     <t>Comparisons of scheme names &MUST; be case-insensitive;</t>
-    <t>An empty path-absolute is equivalent to an path-absolute of "/".</t>
-  </list>
-</t>
-<t>
-   Characters other than those in the "reserved" set (see
-   <xref target="RFC3986" x:fmt="," x:sec="2.2"/>) are equivalent to their
-   ""%" <x:ref>HEXDIG</x:ref> <x:ref>HEXDIG</x:ref>" encoding.
+    <t>An empty path-absolute is equivalent to a path-absolute of "/".</t>
+    <t>Characters other than those in the "reserved" set are equivalent to their
+       percent-encoded octets (see <xref target="RFC3986" x:fmt="," x:sec="2.1"/>).
+    </t>
+  </list>
 </t>
 <t>
@@ -1500 +1503 @@
   <x:anchor-alias value="request-target"/>
 <t>
-   The request-target is a Uniform Resource Identifier (<xref target="uri"/>) and
+   The request-target
    identifies the resource upon which to apply the request.
 </t>
@@ -1583 +1586 @@
 <t>
    The request-target is transmitted in the format specified in 
-   <xref target="http.uri"/>. If the request-target is encoded using the
-   "% <x:ref>HEXDIG</x:ref> <x:ref>HEXDIG</x:ref>" encoding
-   (<xref target="RFC3986" x:fmt="," x:sec="2.4"/>), the origin server
+   <xref target="http.uri"/>. If the request-target is percent-encoded
+   (<xref target="RFC3986" x:fmt="," x:sec="2.1"/>), the origin server
    &MUST; decode the request-target in order to
    properly interpret the request. Servers &SHOULD; respond to invalid
@@ -1607 +1609 @@
    HTTP does not place a pre-defined limit on the length of a request-target.
    A server &MUST; be prepared to receive URIs of unbounded length and
-   respond with the 414 (Request-target too Long) status if the received
+   respond with the 414 (URI Too Long) status if the received
    request-target would be longer than the server wishes to handle
    (see &status-414;).
@@ -3355 +3357 @@
 </reference>
 
-<reference anchor="RFC2045">
-  <front>
-    <title abbrev="Internet Message Bodies">Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies</title>
-    <author initials="N." surname="Freed" fullname="Ned Freed">
-      <organization>Innosoft International, Inc.</organization>
-      <address><email>ned@innosoft.com</email></address>
-    </author>
-    <author initials="N.S." surname="Borenstein" fullname="Nathaniel S. Borenstein">
-      <organization>First Virtual Holdings</organization>
-      <address><email>nsb@nsb.fv.com</email></address>
-    </author>
-    <date month="November" year="1996"/>
-  </front>
-  <seriesInfo name="RFC" value="2045"/>
-</reference>
-
 <reference anchor="RFC2119">
   <front>
@@ -3574 +3560 @@
 </reference>
 
+<reference anchor="RFC2045">
+  <front>
+    <title abbrev="Internet Message Bodies">Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies</title>
+    <author initials="N." surname="Freed" fullname="Ned Freed">
+      <organization>Innosoft International, Inc.</organization>
+      <address><email>ned@innosoft.com</email></address>
+    </author>
+    <author initials="N.S." surname="Borenstein" fullname="Nathaniel S. Borenstein">
+      <organization>First Virtual Holdings</organization>
+      <address><email>nsb@nsb.fv.com</email></address>
+    </author>
+    <date month="November" year="1996"/>
+  </front>
+  <seriesInfo name="RFC" value="2045"/>
+</reference>
+
 <reference anchor="RFC2047">
   <front>