Re: [MMUSIC] Review of draft-ietf-mmusic-sdp-bundle-negotiation-32 - Magnus' comments - MID security

[Christer Holmberg <[e-mail]>]

Hi,

Based on the discussions, and input that has been provided, are people ok
with adding the text Magnus suggested (see below) to the Security
Considerations of BUNDLE?

Regards,

Christer


>>> The identfication-tag when included in the RTP MID SDES item,
>>> independent of transport, RTCP SDES packet or RTP header extension,
>>> can expose the value to parties beyond the signaling chain.
>>> Therefore, the identification-tag MUST NOT contain any user related
>>> information. However, the implementation's method for generating
>>> identfication-tags combined with hardware configuration can enable
>>> fingerprinting of the endpoint device and thus its user. As the
>>> identification-tag is also used to route the media stream to the
>>> right application functionality it is also important that the value
>>> received is the one intended by the sender, thus integrity and the
>>> authenticity of the source are important to prevent denial of
>>> service on the application. At least to prevent third parties from
>>> modifying the identification-tag value.
>>>
>>> Due to the security risks associated with the MID values in RTP and
>>> RTCP it is strongly RECOMMENDED that the MID SDES item is both
>>> confidentiality protected as well as source authenticated when
>>> transported in either RTCP or RTP header extensions. The security
>>> mechanisms used SHALL provide corresponding levels of security for
>>> both RTP header extensions and RTCP. Confidentiality mechanisms for
>>> RTP/RTCP are discussed in Options for Securing RTP Sessions
>>> [RFC7201], for example SRTP [RFC3711] with SRTCP encryption enabled
>>> combined with [RFC6904] can provide the necessary security
>>> functions.