On Fri, Aug 30, 2019 at 3:24 PM Benjamin Kaduk <ka...@mit.edu> 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".
Design issues: Am I reading the doc right, that this handshake message goes after the finished? And then contains a key that is used to decrypt another key that is then used to decrypt (some) traffic, but doesn't change the DTLS keys? Why is this a handshake message and not some protocol framing in the protocol carried over DTLS? It just seems funny to make it be a handshake type and not something else. It's entirely possible this makes more sense if you know about DTLS-SRTP which I do not very much. > > -Ben > > _______________________________________________ > TLS mailing list > TLS@ietf.org > https://www.ietf.org/mailman/listinfo/tls _______________________________________________ TLS mailing list TLS@ietf.org https://www.ietf.org/mailman/listinfo/tls
