User defined SETTINGS frame extensions

Right now, the HTTP/2 spec reserves higher numbers SETTINGS identifiers 
for future revisions to the protocol. Would there be a benefit to 
allowing users to register/reserve identifiers for their own use? Or 
perhaps a weaker, more practical version of this: set aside a range of 
high numbered identifiers (ala ephemeral ports) that are reserved for 
internal use within controlled networks. It could be useful to allow two 
internal HTTP/2 endpoints to exchange information via SETTINGS that do 
not make sense for the internet at large.

Received on Friday, 7 February 2014 20:24:08 UTC