Opened 7 years ago

Closed 6 years ago

#447 closed editorial (incorporated)

HTTP and TCP name delegation

Reported by: mnot@… Owned by: draft-ietf-httpbis-p1-messaging@…
Priority: normal Milestone: 23
Component: p1-messaging Severity: In WG Last Call
Keywords: Cc:

Description

p1 2.7.1 says:

Although HTTP is independent of the transport protocol, the "http" scheme is specific to TCP-based services because the name delegation process depends on TCP for establishing authority. 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 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 specific to TCP.

I made a previous editorial comment that this should be clarified as follows:

"...because the name delegation process depends on the TCP port for establishing authority." (note "port")

However, that wasn't integrated. Is that incorrect, or was there another reason?

Also, no such statement is made in the definition of the HTTPS URI scheme (2.7.2); it should be.

Change History (4)

comment:1 Changed 7 years ago by ht@…

Wrt the same paragraph quoted above, a related point: The only prior use of 'namespace' (in section 2.7.1) covers more than authority:

"The 'http' 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 TCP connections on a given port."

So here, saying "it is only the authoritative interface used for mapping the authority that is specific to TCP" would be a bit linguistically awkward, but more correct, would it not?

comment:2 Changed 6 years ago by fielding@…

It is incorrect to say that the name delegation process depends on the TCP port because it depends on all of TCP (including TCP's use of IP in some cases): the port is just one aspect.

I will attempt to clarify the other bits.

comment:3 Changed 6 years ago by fielding@…

From [2278]:

(editorial) clarify that name delegation for http and https URIs depend on TCP and TLS/TCP, respectively; addresses #447

comment:4 Changed 6 years ago by fielding@…

  • Milestone changed from unassigned to 23
  • Resolution set to incorporated
  • Status changed from new to closed
  • Type changed from design to editorial
Note: See TracTickets for help on using tickets.