Re: Updating Digest header RFC3230 using "selected representation"

[Rob Sayre <[e-mail]>]

This draft looks good to me.

One issue that prevented the adoption of this header and related ones (e.g.
Content-MD5) was that HTTP/1.1 trailers had a lot of interoperability
problems. This made it expensive for large files, or impossible to use for
message bodies that couldn't be pre-calculated.

I think using trailers should work these days, right? From what I
understand, this might be implied in the header model of HTTP2+, but I
think addressing this issue in the draft might be helpful.

At first glance, this header looks redundant given that HTTP is now done
over TLS, but I've seen this kind of feature catch bugs behind TLS
termination many times.

thanks,
Rob




On Tue, Apr 16, 2019 at 2:57 AM Lucas Pardue <[e-mail]>
wrote:

> I think you're on the right track.
>
> Present a salient problem statement, seek others also interested, prepare
> some text that address the problem (Google doc is ok to start with,
> focusing on content not formatting). At some point we can get an individual
> Internet Draft prepared (markdown GitHub workflow is relatively
> straightforward) and see if a working group like HTTPbis has interest in
> adopting it for further work / publication.
>
> Lucas
>
> On Tue, 16 Apr 2019, 10:44 Roberto Polli, <[e-mail]>
> wrote:
>
>> Hi Lucas,
>>
>>
>> Il giorno mar 16 apr 2019 alle ore 11:33 Lucas Pardue
>> <[e-mail]> ha scritto:
>> > On Tue, 16 Apr 2019, 10:29 Roberto Polli, <
>> [e-mail]> wrote:
>> >> as the Digest header is still used, I'm willing to refresh the old spec
>> >>
>> >> - https://tools.ietf.org/html/rfc3230
>> >>
>> >> using the new definitions of RFC723x (eg. selected representation)
>> >> and untagling it from delta-encoding.
>>
>> > Yes I would like to see an update.
>> > This spec is no longer consistent with other HTTP docs, and leads to
>> some circular arguments.
>> > Despite that I think it still has a valid use.
>> Great! Here's an editable google docs:
>>
>>   -
>> https://docs.google.com/document/d/1p8KBR_dQKfh7PgLTOYXg_htMAME8nnEblKRC0DSH5_o/edit
>>
>> > I'd like to see the document updated to align with the current HTTP
>> core work, I'm happy to help if I can.
>> I need some guidance on the ietf workflow (Eg. proposing the draft,
>> ..) as it's the first time
>> I'm doing that :D
>>
>> I hope that the technical side can converge quic-ly :D
>>
>> Have a nice day,
>> R:
>>
>>
>>
>>
>> >>
>> >> Hi @all,
>> >>
>> >>
>> >> Is there somebody interested in supporting that effort?
>> >>
>> >> Thanks and have a nice day,
>> >> R.
>> >>
>> >> --
>> >> Roberto Polli
>> >> Full Stack Developer
>> >> M. [phone]
>> >> ·D
>> >> TEAM PER LA
>> >> TRASFORMAZIONE
>> >> DIGITALE
>> >> Presidenza del Consiglio dei Ministri
>> >> teamdigitale.governo.it
>> >>
>> >> Il Team per la Trasformazione Digitale, salvo eccezioni, comunica con
>> >> le altre Amministrazioni via posta elettronica ordinaria e non posta
>> >> elettronica certificata, in conformità a quanto previsto dall’art.47
>> >> del Codice dell’Amministrazione Digitale.
>> >>
>>
>>
>> --
>> Roberto Polli
>> Full Stack Developer
>> M. [phone]
>> ·D
>> TEAM PER LA
>> TRASFORMAZIONE
>> DIGITALE
>> Presidenza del Consiglio dei Ministri
>> teamdigitale.governo.it
>>
>> Il Team per la Trasformazione Digitale, salvo eccezioni, comunica con
>> le altre Amministrazioni via posta elettronica ordinaria e non posta
>> elettronica certificata, in conformità a quanto previsto dall’art.47
>> del Codice dell’Amministrazione Digitale.
>>
>