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

Timestamp:

Sep 18, 2012, 12:53:38 AM (7 years ago)

Author:

fielding@…

Message:

https requires and end-to-end secured connection. Addresses #383

Refer just to TLS, not SSL/TLS.

File:

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

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

@@ -886 +886 @@
    An HTTP service based on some other underlying connection protocol
    would presumably be identified using a different URI scheme, just as
-   the "https" scheme (below) is used for servers that require an SSL/TLS
-   transport layer on a connection. Other protocols might also be used to
+   the "https" scheme (below) is used for resources that require an
+   end-to-end secured connection. Other protocols might also be used to
    provide access to "http" identified resources — it is only the
    authoritative interface used for mapping the namespace that is
@@ -916 +916 @@
    The "https" URI scheme is hereby defined for the purpose of minting
    identifiers according to their association with the hierarchical
-   namespace governed by a potential HTTP origin server listening for
-   SSL/TLS-secured connections on a given TCP port.
+   namespace governed by a potential HTTP origin server listening to a
+   given TCP port for TLS-secured connections <xref target="RFC5246"/>.
 </t>
 <t>
@@ -923 +923 @@
    requirements for the "https" scheme, except that a default TCP port
    of 443 is assumed if the port subcomponent is empty or not given,
-   and the TCP connection &MUST; be secured through the
+   and the TCP connection &MUST; be secured, end-to-end, through the
    use of strong encryption prior to sending the first HTTP request.
 </t>
@@ -2362 +2362 @@
 </t>
 <t>
-   If the request is received over an SSL/TLS-secured TCP connection,
+   If the request is received over a TLS-secured TCP connection,
    then the effective request URI's scheme is "https"; otherwise, the
    scheme is "http".
@@ -2405 +2405 @@
 <figure>
 <preamble>
-   Example 2: the following message received over an SSL/TLS-secured TCP
-   connection
+   Example 2: the following message received over a TLS-secured TCP connection
 </preamble> 
 <artwork type="example" x:indent-with="  ">