Re: Suggestions for HTTP/2, RFC 9113, Section 2.

Hi Rupinder,

I think that perhaps you are looking at this more broadly than the document intends.

HTTP/2 is a protocol between an HTTP client and server, as opposed to user agent or origin server or proxy or intermediary (or any of those terms that HTTP uses).  As a definition of a single "hop", using connection-oriented is entirely appropriate.  For instance, while HTTP itself is stateless, HTTP/2 uses a connection-oriented method to convey HTTP semantics.

A lot of the older HTTP literature did not properly distinguish between HTTP in general and the specific HTTP/1.1 protocol.  A lot of that has been carefully cleaned up with the publication of RFC 9110, so I'd encourage you to read the document with that in mind.

Cheers,
Martin

On Sat, Dec 30, 2023, at 04:56, Rupinder Singh wrote:
> Hello,
>
> Most respectfully. I've the following suggestions w.r.t.  HTTP/2, RFC 
> 9113, Section 2. 
>
> 1. "HTTP/2 is a connection-oriented application-layer protocol..."
>
> HTTP/2 is a stateless application-layer protocol...
>
> 2. Sub-section 2..2. The term "endpoint" may not be equated with a 
> client or server. The term endpoint refers specifically to a URI at the 
> application layer. By extension/overloading, it also refers to the 
> proxy software ( e.g., class) abstracting the endpoint. It can't refer 
> to the client IP address + port  or to the server IP address+port that 
> actually sets up the TCP connection at the transport layer. And  a 
> typical web client like a user agent/client (e.g. browser) doesn't have 
> a  URI.  Yes, maybe, the term endpoint can be used for the addresses of 
> the other stateless protocols, e.g., simply, an IP address at the IP 
> layer.
>
> 3. In the traditional HTTP 1.1 literature as well as software 
> documentation, the term HTTP connection or HTTP session are used. 
> However, from the context, it is clear that they refer to the 
> connection/session at the TCP layer, not at the the HTTP/application 
> layer itself, where communication exchange is 
> stateless/connectioness/sesssionless (simply Request-Response; or 
> additionally a Server push as in HTTP/2). We may clarify the 
> terminology in this RFC accordingly.
>
>
> Kind regards,
> Rupinder Singh

Received on Thursday, 4 January 2024 04:12:55 UTC