Re: draft-ietf-httpbis-incremental-03 ietf last call Secdir review

On 06.12.2025 21:39, Chris Lonvick via Datatracker wrote:
> ...
> Overall, the document is readable and understandable. The nit that I found is
> that the document says that the implementation of the Increment field is
> "advisory" (bottom of page 3) even thought this is a Standards Track document.
> I believe that the authors are trying to say that implementation and deployment
> will take some time and that not all intermediaries will be provisioned
> immediately. If that is the case, the authors may want to consider something
> like the following:
> ...

Maybe HTTP is special with respect to this.

Most (all?) "extension" specs define something new, which, by 
definition, will stay optional. With new specs defined in 2025, we can't 
change what is required for HTTP.

So when we say "Standard" it does not mean "we expect everybody to 
implement this". It just means: "if you want to do this: there is a 
standard for this new functionality, and this is how it works".

 > ...
 > It is expected that there will be a transition period while 
implementations
 > ...

Yes, there will be a period while support grows, but I don't believe 
that there is an expectation that that support ever will be universal.

Best regards, Julian

Received on Sunday, 7 December 2025 07:18:22 UTC