Subject: [clue] New version of draft-ietf-clue-signaling

From: "Rob Hanton (rohanse2)" <[email-masked]>
Date: Tue, 10 Dec 2019 02:42:14 +0000

A new version of draft-ietf-clue-signaling is now up, dealing with the points raised in https://datatracker.ietf.org/doc/draft-ietf-clue-signaling/ballot/ - thanks very much to those who provided some excellent feedback.

While almost all the changes are just tweaks to clarify intent or make it more readable, there is one meaningful change. One issue raised in the ballot was that previously DTLS-SRTP was only mandatory to support, not use. When we first did the security section and discussed the vulnerability of CLUE to a video hammer attack we made DTLS-SRTP mandatory to use, but at a subsequent IETF session that was changed to support as there were concerns about needing to do DTLS-SRTP in proprietary environments where other mechanisms are available for receiver intent assurance. To resolve this, I've made the change I previously proposed on the list, making DTLS-SRTP mandatory to support (as before) and now mandatory to use *unless* some other mechanism is providing receiver intent assurance.

Apologies for the delay in producing the new version, and thanks once again to some very diligent reviews.

Rob