Re: Fwd: New Version Notification for draft-nottingham-bikeshed-length-00.txt

[Martin Thomson <[e-mail]>]

I think that the expectation that this ultimately be accurate makes it no different than Content-Length.  Then you might be allowed to be different, with some appropriately loose definition that allows being off either a proportion of the overall or a fixed amount. Then it could be used to (for example) indicate the length of something that is being decompressed/compressed on the fly.  In a world with midders, the estimate could even be updated over time and converge on the actual length.

I agree with Willy about special rules for trailers.

I have opinions about the name, but I will refrain because the author clearly asked for that kind of restraint.

On Wed, Mar 18, 2020, at 12:29, Mark Nottingham wrote:
> FYI, as discussed in <https://github.com/httpwg/http-core/issues/276>.
> 
> Prettier version at <https://mnot.github.io/I-D/bikeshed-length/>.
> 
> 
> > Begin forwarded message:
> > 
> > *From: *[e-mail]
> > *Subject: **New Version Notification for draft-nottingham-bikeshed-length-00.txt*
> > *Date: *18 March 2020 at 12:27:39 pm AEDT
> > *To: *"Mark Nottingham" <[e-mail]>
> > 
> > 
> > A new version of I-D, draft-nottingham-bikeshed-length-00.txt
> > has been successfully submitted by Mark Nottingham and posted to the
> > IETF repository.
> > 
> > Name: draft-nottingham-bikeshed-length
> > Revision: 00
> > Title: Advisory Content-Length for HTTP
> > Document date: 2020-03-18
> > Group: Individual Submission
> > Pages: 6
> > URL: https://www.ietf.org/internet-drafts/draft-nottingham-bikeshed-length-00.txt
> > Status: https://datatracker.ietf.org/doc/draft-nottingham-bikeshed-length/
> > Htmlized: https://tools.ietf.org/html/draft-nottingham-bikeshed-length-00
> > Htmlized: https://datatracker.ietf.org/doc/html/draft-nottingham-bikeshed-length
> > 
> > 
> > Abstract:
> >  The HTTP Content-Length header field is overloaded with (at least)
> >  two duties: message delimitation in HTTP/1, and metadata about the
> >  length of an incoming request body to the software handling it.
> > 
> >  This causes confusion, and sometimes problems. This document
> >  proposes a new header to untangle these semantics (at least
> >  partially).
> > 
> > 
> > 
> > 
> > Please note that it may take a couple of minutes from the time of submission
> > until the htmlized version and diff are available at tools.ietf.org.
> > 
> > The IETF Secretariat
> > 
> > 
> 
> --
> Mark Nottingham https://www.mnot.net/
>