- From: Martin Thomson <mt@lowentropy.net>
- Date: Thu, 10 Aug 2023 12:21:58 +1000
- To: "Mark Nottingham" <mnot@mnot.net>, "ietf-http-wg@w3.org Group" <ietf-http-wg@w3.org>
- Cc: "Tommy Pauly" <tpauly@apple.com>
I'm supportive of adoption. Something that came when I checked in on the document: 1. I don't understand how a client determines which dictionary was used by the server. It seems like the response depends on the request, which is fragile (and doesn't allow clients to advertise multiple dictionaries, which seems likely with Use-As-Dictionary as it is). 2. The Sec- prefix seems entirely unjustified. Yes, JS that can inject the field into a fetch might spoil a response (see above), but that's already true. I'd prefer not to include Sec- prefixes unless there is clear justification. On Thu, Aug 10, 2023, at 11:58, Mark Nottingham wrote: > Everyone, > > Discussion at IETF117 seemed to indicate strong support for, and no > significant pushback against, restarting work on dictionary > compression, based on this draft: > > https://datatracker.ietf.org/doc/draft-meenan-httpbis-compression-dictionary/ > > So, this e-mail begins its Call for Adoption; please indicate your > support or lack thereof (ideally, with reasons). The CfA will end on > 2023-08-24 , after which the Chairs will make a determination. > > Cheers, > > > -- > Mark Nottingham https://www.mnot.net/
Received on Thursday, 10 August 2023 02:22:23 UTC