Changeset 2598

Timestamp:

28/01/14 08:25:27 (8 years ago)

Author:

fielding@…

Message:

(editorial) remove a redundant reference to improve readability; see #531

Location:

draft-ietf-httpbis/latest

Files:

• p1-messaging.html (modified) (2 diffs)
• p1-messaging.xml (modified) (1 diff)

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

@@ -1138 +1138 @@
                <div id="rfc.iref.u.4"></div>
                <p id="rfc.section.2.7.2.p.1">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 to a given TCP port for TLS-secured connections (<a href="#RFC0793" id="rfc.xref.RFC0793.2"><cite title="Transmission Control Protocol">[RFC0793]</cite></a>, <a href="#RFC5246" id="rfc.xref.RFC5246.2"><cite title="The Transport Layer Security (TLS) Protocol Version 1.2">[RFC5246]</cite></a>).
-               </p>
-               <p id="rfc.section.2.7.2.p.2">All of the requirements listed above for the "http" scheme are also 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 user agent <em class="bcp14">MUST</em> ensure that its connection to the origin server is secured through the use of strong encryption, end-to-end, prior to sending
+                  namespace governed by a potential HTTP origin server listening to a given TCP port for TLS-secured connections (<a href="#RFC5246" id="rfc.xref.RFC5246.2"><cite title="The Transport Layer Security (TLS) Protocol Version 1.2">[RFC5246]</cite></a>).
+               </p>
+               <p id="rfc.section.2.7.2.p.2">All of the requirements listed above for the "http" scheme are also requirements for the "https" scheme, except that TCP port
+                  443 is the default if the port subcomponent is empty or not given, and the user agent <em class="bcp14">MUST</em> ensure that its connection to the origin server is secured through the use of strong encryption, end-to-end, prior to sending
                   the first HTTP request.
                </p>
@@ -3697 +3697 @@
                   <li>response&nbsp;&nbsp;<a href="#rfc.iref.r.3"><b>2.1</b></a></li>
                   <li>reverse proxy&nbsp;&nbsp;<a href="#rfc.iref.r.4"><b>2.3</b></a></li>
-                  <li><em>RFC0793</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC0793.1">2.7.1</a>, <a href="#rfc.xref.RFC0793.2">2.7.2</a>, <a href="#RFC0793"><b>11.1</b></a></li>
+                  <li><em>RFC0793</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC0793.1">2.7.1</a>, <a href="#RFC0793"><b>11.1</b></a></li>
                   <li><em>RFC1919</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC1919.1">2.3</a>, <a href="#RFC1919"><b>11.2</b></a></li>
                   <li><em>RFC1945</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC1945.1">2.6</a>, <a href="#rfc.xref.RFC1945.2">10</a>, <a href="#RFC1945"><b>11.2</b></a>, <a href="#rfc.xref.RFC1945.3">A</a></li>

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

@@ -949 +949 @@
    identifiers according to their association with the hierarchical
    namespace governed by a potential HTTP origin server listening to a
-   given TCP port for TLS-secured connections
-   (<xref target="RFC0793"/>, <xref target="RFC5246"/>).
+   given TCP port for TLS-secured connections (<xref target="RFC5246"/>).
 </t>
 <t>
    All of the requirements listed above for the "http" scheme are also
-   requirements for the "https" scheme, except that a default TCP port
-   of 443 is assumed if the port subcomponent is empty or not given,
+   requirements for the "https" scheme, except that TCP port 443 is the
+   default if the port subcomponent is empty or not given,
    and the user agent &MUST; ensure that its connection to the origin
    server is secured through the use of strong encryption, end-to-end,