W3C home > Mailing lists > Public > ietf-http-wg@w3.org > October to December 2021

Re: New Version Notification for draft-nottingham-http-structure-retrofit-00.txt

From: Mark Nottingham <mnot@mnot.net>
Date: Thu, 7 Oct 2021 10:55:09 +1100
Cc: HTTP Working Group <ietf-http-wg@w3.org>
Message-Id: <371DD60B-5DB2-4DD9-8E1F-790C3F9711B1@mnot.net>
To: Lucas Pardue <lucaspardue.24.7@gmail.com>
On 7 Oct 2021, at 10:48 am, Lucas Pardue <lucaspardue.24.7@gmail.com> wrote:
> 
> Interesting!
> 
> Question: is the intent that this is a one-shot pass or do you intend to set a methodology for how other headers can be mapped? For instance, we could keep the digest field in ABNF and use a similar methodology to define SF-digest alongside it in the digest spec.

That's a good question, and I'm punting on covering it in-spec for now.

One approach is to assume that new headers will be defined as SF, so there's no need. As long as this spec carves off the top n% (n~80-90), it's adequate for most purposes.

Another is to allow further specs to retrofit additional headers in the same fashion.

Another is to let specs retrofit themselves, as you suggest for Digest.

Cheers,


--
Mark Nottingham   https://www.mnot.net/
Received on Wednesday, 6 October 2021 23:55:30 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 6 October 2021 23:55:31 UTC