Changeset 163 for draft-ietf-httpbis/latest/p1-messaging.xml

Timestamp:

12/01/08 05:09:10 (15 years ago)

Author:

fielding@…

Message:

editorial: make introductions more active and consistent

File:

• draft-ietf-httpbis/latest/p1-messaging.xml (modified) (1 diff)

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

@@ -227 +227 @@
 <section title="Introduction" anchor="introduction">
 <t>
-   This document will define aspects of HTTP related to overall network
-   operation, message framing, interaction with transport protocols, and
-   URI schemes. Right now it only includes the extracted relevant sections
-   of <xref target="RFC2616"/>.
-</t>
-<section title="Purpose" anchor="intro.purpose">
-<t>
    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. The first version of HTTP,
+   information initiative since 1990. The first version of HTTP, commonly
    referred to as HTTP/0.9, was a simple protocol for raw data transfer
-   across the Internet. HTTP/1.0, as defined by <xref target="RFC1945"/>, improved
+   across the Internet with only a single method and no metadata.
+   HTTP/1.0, as defined by <xref target="RFC1945"/>, improved
    the protocol by allowing messages to be in the format of MIME-like
-   messages, containing metainformation about the data transferred and
-   modifiers on the request/response semantics. However, HTTP/1.0 does
+   messages, containing metadata about the data transferred and
+   modifiers on the request/response semantics. However, HTTP/1.0 did
    not sufficiently take into consideration the effects of hierarchical
-   proxies, caching, the need for persistent connections, or virtual
-   hosts. In addition, the proliferation of incompletely-implemented
-   applications calling themselves "HTTP/1.0" has necessitated a
+   proxies, caching, the need for persistent connections, or name-based
+   virtual hosts. In addition, the proliferation of incompletely-implemented
+   applications calling themselves "HTTP/1.0" necessitated a
    protocol version change in order for two communicating applications
    to determine each other's true capabilities.
 </t>
 <t>
-   This specification defines the protocol referred to as "HTTP/1.1".
-   This protocol includes more stringent requirements than HTTP/1.0 in
-   order to ensure reliable implementation of its features.
-</t>
+   This document is Part 1 of the seven-part specification that defines
+   the protocol referred to as "HTTP/1.1", obsoleting <xref target="RFC2616"/>.
+   HTTP/1.1 remains compatible with HTTP/1.0 by including more stringent
+   requirements that enable reliable implementations and adding only
+   those new features that will either be safely ignored by an HTTP/1.0
+   recipient or only sent when communicating with a party advertising
+   compliance with HTTP/1.1.
+   Part 1 defines those aspects of HTTP/1.1 related to overall network
+   operation, message framing, interaction with transport protocols, and
+   URI schemes.
+</t>
+<t>
+   This document is currently disorganized in order to minimize the changes
+   between drafts and enable reviewers to see the smaller errata changes.
+   The next draft will reorganize the sections to better reflect the content.
+   In particular, the sections will be organized according to the typical
+   process of deciding when to use HTTP (URI schemes), overall network operation,
+   connection management, message framing, and generic message parsing.
+   The current mess reflects how widely dispersed these topics and associated
+   requirements had become in <xref target="RFC2616"/>.
+</t>
+
+<section title="Purpose" anchor="intro.purpose">
 <t>
    Practical information systems require more functionality than simple