Re: [hybi] method of allocation of reserved bits to extensions

[Greg Wilkins <[e-mail]>]

On 28 April 2011 12:13, John Tamplin <[e-mail]> wrote:
> reserved bits, it seems reasonable to simply define that the Foo extension
> allocates RSV2.  If another extension also statically allocates RSV2, then
> obviously they couldn't be used together.

It might be reasonable if you are google, as you will have the market
share such that any decision you make to allocated a reserved bit for
your own extensions will effectively allocate that bit to you forever.

Imagine I'm an intermediary vender and I develop a private extension
for my WS aggregator to talk to the servers behind it that uses a
reserve bit.    If google chrome subsequently comes out with a very
popular extension that uses the same reserved bit, then my
intermediary product will have been badly impacted.  I will either
have to redeploy all my intermediaries using another reserved bit or
lose market share because I don't support googles latest extension.

it is not a level playing field.