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

[Cory Benfield <[e-mail]>]

As with Willy and Martin, I think it would be good for this draft to
explicitly allow fuzziness in the field value. Otherwise, the draft
seems reasonable, and I'd implement it.

On Wed, 18 Mar 2020 at 01:33, Mark Nottingham <[e-mail]> 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/
>