On Sep 30, 10:05 pm, Nelson B Bolyard <nel...@bolyard.me> wrote: > These issues need to be brought up to the IETF TLS mailing list, ASAP. > The last thing we want, IMO, is to have to implement a bunch of > slightly-different incompatible extractor functions. :-/
It seems to be somewhat late to go through the IETF WG at this point of the RFC process (after IESG approval), but I'm in the process of confirming with the draft author and the IESG contact persons that they agree with my interpretation of the issue and if so, figuring out what is the best mechanism to handle this in IETF. I agree that the current situation is not exactly ideal and unfortunately no one seems to have noticed this issue before. > If you would like to contribute your patch to mozilla for consideration > for inclusion into NSS, please file an enhancement request "bug" in > bugzilla.mozilla.org and attach your patch to it. Thanks. I'll do that (or just add the patch as a modification request for the existing case) once the IETF part gets resolved one way or another. - Jouni -- dev-tech-crypto mailing list dev-tech-crypto@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-tech-crypto
