RTP Control Protocol (RTCP) Port for Source-Specific Multicast (SSM) Sessions
updates
- rfc-5760 — RTP Control Protocol (RTCP) Extensions for Single-Source Multicast Sessions with Unicast Feedback
Extracted elements (7)
The existing 'rtcp' attribute could not be reused to specify the SSM session's RTCP port because it was already used for the Feedback Target address and port, creating potential ambiguity. A new attribute 'multicast-rtcp' was introduced to remove the unnecessary restriction imposed by the +1 rule.
This document updates RFC 5760. The distribution source may alternatively use RTP/RTCP port muxing per RFC 5761, in which case RTP and RTCP packets share the same destination port in the SSM session.
In the absence of the 'multicast-rtcp' attribute, the +1 rule applies following RFC 5760, meaning the RTCP port is derived from the 'm=' line of the media description.
The 'multicast-rtcp' SDP attribute specifies the RTCP port for an SSM session, allowing the distribution source to use a desired port rather than deriving it from the 'm=' line via the +1 rule. It is defined as both a media-level and session-level attribute.
This document registers a new SDP attribute named 'multicast-rtcp' in the SDP att-field registry. It is a media or session level attribute that specifies the port for the SSM RTCP session and is not subject to charset.
A malevolent third party could use the 'multicast-rtcp' attribute to redirect RTCP traffic by intercepting and rewriting SDP packets. To mitigate this, the SDP description should be integrity protected and source authenticated, using mechanisms such as S/MIME, HTTPS, or SAP authentication.
The ABNF syntax for the 'multicast-rtcp' attribute is: `rtcp-attribute = "a=multicast-rtcp:" port CRLF`, where 'port' is defined as specified in Section 9 of RFC 4566.