- From: Martin Thomson <mt@lowentropy.net>
- Date: Thu, 08 Jan 2026 20:51:59 +1100
- To: "Dick Hardt" <Dick.Hardt@gmail.com>, "Lucas Pardue" <lucas@lucaspardue.com>
- Cc: "HTTP Working Group" <ietf-http-wg@w3.org>, "Thibault Meunier" <ot-ietf@thibault.uk>, "Richard Backman, Annabelle" <richanna@amazon.com>, ietf@justin.richer.org, "Manu Sporny" <msporny@digitalbazaar.com>
On Thu, Jan 8, 2026, at 20:24, Dick Hardt wrote: > I've just published -01 to clarify that all parameter values are > strings. While some parameters could be tokens, my view is consistency > of having all parameters be strings is simpler for implementers. It's not tokens (RFC 9651 recommends strings over tokens in most cases), but byte sequences. You have a lot of base64, which could very easily use : instead of " as a delimiter and get the benefit of syntax checking and other facilities in structured fields. Yes, I know that you might prefer the URL safe base64 variant, as I do, but the difference is pretty minor.
Received on Thursday, 8 January 2026 09:52:24 UTC