Which value do they want? As we have previously established in relation to the discussion on connection IDs and handshake types, there are values that would be sent in the clear in (D)TLS 1.3, which have very tight constraints, and those that would be sent under encryption, which might not need so close scrutiny.
I get the impression that there are constraints here. This will likely be multiplexed in an RFC 7983 sense in DTLS 1.2, so the range of values here is narrow. But not as narrow as to require access to the prime space between 20 and 31 that we are using for handshake types that need to be sent in the clear. I think that we should encourage the use of a value >= 32 in this case. On Sat, Aug 31, 2019, at 08: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". > > -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
