On Sat, Jun 13, 2020 at 10:20 AM Yoav Nir <ynir.i...@gmail.com> wrote:
> > To re-iterate, the policy for the registry is “Specification Required” and > a specification is available. Unless we hear convincing arguments to the > contrary, we will approve this allocation. We just prefer to have the > kerfuffle before the assignment rather than afterwards. > If the IANA experts feel the 99 page PDF is "sufficiently clear and technically sound" [1], then it should appear in the registry. [2] It seems like it should appear with a "Recommended" value of "No", and no value in the TLS 1.3 column, since the document says "The Middlebox Security Protocol builds on TLS 1.2". [3] Is that what's being proposed? thanks, Rob [1] https://tools.ietf.org/html/rfc8126#section-4.6 [2] https://www.iana.org/assignments/tls-extensiontype-values/tls-extensiontype-values.xhtml#tls-extensiontype-values-1 [3] https://docbox.etsi.org/CYBER/CYBER/Open/Latest_Drafts/CYBER-0027-2v020-TLMSP-Transport-Layer-Middlebox-Security-Protocol.pdf (Section 1, scope)
_______________________________________________ TLS mailing list TLS@ietf.org https://www.ietf.org/mailman/listinfo/tls
