Re: encoding and other h2 extensions

On 21 November 2014 13:31, Matthew Kerwin <matthew@kerwin.net.au> wrote:
> To my mind, the initial registry is of secondary importance to getting the
> machinery right in the first place. If the extension mechanism itself works,
> and issues like fragmentation are significantly addressed, *then* I'd want
> to focus on seeding the registry (in a way that will promote adoption and
> interop). This list was pulled straight from RFC 7230 S4.2, plus a little
> splash of paint, because that involved the least thought on my part.

There is another way of tackling the problem, which might be better.
If your proposal requires an extension, then make it a simple
extension: if negotiated, then X is used (be that gzip or whatever you
choose).  If a new thing comes along, then that is a completely
different extension that is incompatible with the first (you can't
have both).  That way, no registry or extension mechanism other than
the one you rely on.  Registries are expensive.

(Not an endorsement, just an observation.)

Received on Saturday, 22 November 2014 00:45:00 UTC