Re: Giving the Framing Layer a real name

On Wed, Feb 27, 2013 at 04:12:32PM +1100, Mark Nottingham wrote:
> I've been a bit uncomfortable with our current nomenclature for a little while.
> 
> Right now we have:
>   - a spec called "Hypertext Transfer Protocol version 2.0"
>   - ... that does " HTTP Layering over HTTP/2.0"
>   - ... onto a framing layer that we also call "HTTP/2.0"
> 
> I'm very tempted to propose that we:
>   - Give the framing layer a distinct name. I don't care what it is.
>   - Section 4 becomes "Layering HTTP Semantics onto XXXX."
>   - "HTTP/2.0" is the name of the package of doing so -- i.e., HTTP semantics
>   on a new framing layer.
> 
> I think this would make our discussions somewhat less confusing, especially
> around things like the upgrade process, and make our documentation clearer.
> It would also help clarify when it's appropriate to put something in a header
> (HTTP stuff) vs. in the framing layer (connection-specific stuff).
> 
> However, I recognise that naming things is hard, and I don't want this to
> become the bikeshed that kills us all. I'm also aware that doing so may
> encourage people to treat the framing layer as a substrate, but I don't see
> any way to avoid that, and won't mind, as long as we don't exceed our
> charter.

It's not a problem if people see the two parts as distinct. After all, if
we come up with something which later can be reused to transport other
protocols (eg: WebSocket) without the need for HTTP semantics, it will
be a good thing.

> Any concerns in doing so? Suggestions for a name?

I'm wondering whether we don't already have such things : 
  - HTTP holds the semantics
  - SPDY is the framing layer.

And if would 1) emphasize the fact that we don't want to change semantics,
and 2) acknowledge the work done by the SPDY team.

Regards,
Willy

Received on Wednesday, 27 February 2013 06:23:54 UTC