- From: Roberto Polli <robipolli@gmail.com>
- Date: Tue, 18 Aug 2020 18:39:21 +0200
- To: Poul-Henning Kamp <phk@phk.freebsd.dk>
- Cc: Amos Jeffries <squid3@treenet.co.nz>, Lucas Pardue <lucaspardue.24.7@gmail.com>, HTTP Working Group <ietf-http-wg@w3.org>
Il giorno mar 18 ago 2020 alle ore 18:20 Poul-Henning Kamp <phk@phk.freebsd.dk> ha scritto: > > -------- > Roberto Polli writes: > > > While I like sf-binary, actual digest-algorithms define their own serialization > > method (in this case it's accidentally the same of structured headers) but other > > algorithms use eg. integer. > > > > To support SF we could say that digest-algorithms like sha-256 and > > sha-512 should be supported > > in both sf-binary and the traditional token format. > > The most sensible way (IMO) is to define that *all* digests are *always* sf-binary. I certainly agree on all your statements, but we cannot break current implementations of sha-256 and sha-512 for fixing the parameters issue. So: - ok to prepare Digest to be SF-ready - ok if there's a way do describe the current Digest syntax with SF, so that we can later obsolete non sf-binary algoritms - not sure that fixing the parameters issue is a valid reason to introduce SF now My 2c, R.
Received on Tuesday, 18 August 2020 16:39:44 UTC