Re: draft-reschke-http-cice vs discussions in Toronto @ IETF 90: use as response header field

On 2015-02-10 01:17, Mark Nottingham wrote:
> ...
>>> There are a number of subtle differences there, especially about the scope of applicability -- one of the most ill-defined areas in HTTP metadata.
>> Anything besides the freshness issue?
> It's also a certainty issue -- if you send Accept-Encoding as a client, the server knows it can select one of those encodings, and doesn't have to worry about failure. If the server sends it and the client uses it, the client needs to be able to recover from failure gracefully.
> Let's flip it around -- what does reusing A-E buy us here? Are we trying to conserve registry space or something? :)

I think having "almost the same" functionality in two different header 
fields is confusing as well...

Received on Tuesday, 10 February 2015 06:49:50 UTC