Hiya, On 30/08/2019 23:24, Benjamin Kaduk wrote: > Hi all, > > New values for core types like TLS HandshakeType and ContentType don't > happen very often, so I thought people might be interested to know that > draft-ietf-perc-srtp-ekt-diet (currently in IESG evaluation) is allocating > a HandshakeType, to carry key information used to encrypt SRTP media key > material. > Obviously "it's never too late to change until the RFC is published", but I > think there would need to be some pretty serious issues in order to change > it at this point, so this is expected to just be an "FYI".
I guess I ought read the draft properly, but a scan of the draft doesn't seem to show any references to the kind of analyses that were done for tls1.3. I'm not clear why that's ok. Is there a reason why that is ok? It was great that many people worked to do security proofs for tls1.3. It'd be a shame to lose that via extensions that are less well analysed. Thanks, S. > > -Ben > > _______________________________________________ > TLS mailing list > TLS@ietf.org > https://www.ietf.org/mailman/listinfo/tls >
0x5AB2FAF17B172BEA.asc
Description: application/pgp-keys
signature.asc
Description: OpenPGP digital signature
_______________________________________________ TLS mailing list TLS@ietf.org https://www.ietf.org/mailman/listinfo/tls
