Hiya,
On 24/02/2021 18:07, Christopher Wood wrote:
The WG previously decided to make draft-ietf-tls-esni-09 the official target
for interop. The diff between this version and the current editor's copy of the
draft is below:
https://tools.ietf.org/rfcdiff?url1=https://tools.ietf.org/id/draft-ietf-tls-esni.txt&url2=https://tlswg.github.io/draft-ietf-tls-esni/draft-ietf-tls-esni.txt
Given the size of the diff, and the recent update to HPKE to prepare it for
IRSG review, I'd like to propose that we cut -10 (when the datatracker opens)
and use that as the new interop target. This will resolve the moving HPKE
target going forward and let that part of the protocol stabilize.
What do other implementers think?
That's generally ok, but from my POV it would be better to give it another week or two before we do that, e.g. maybe just after IETF-110 or so. Reason is I've nearly but not quite got -09 interop between (currently mega-hacked;-) OpenSSL code and the NSS client, and then hopefully the CF server and would prefer have that done before we start moving the target again. OTOH, if the CF -09 server were to remain available for a bit, then I'd be fine with this change at any time. Cheers, S.
Thanks, Chris (no hat) _______________________________________________ TLS mailing list [email protected] https://www.ietf.org/mailman/listinfo/tls
OpenPGP_0x5AB2FAF17B172BEA.asc
Description: application/pgp-keys
OpenPGP_signature
Description: OpenPGP digital signature
_______________________________________________ TLS mailing list [email protected] https://www.ietf.org/mailman/listinfo/tls
