RFC 6128
RTP Control Protocol (RTCP) Port for Source-Specific Multicast (SSM) Sessions, February 2011
- File formats:
- Status:
- PROPOSED STANDARD
- Updates:
- RFC 5760
- Author:
- A. Begen
- Stream:
- IETF
- Source:
- avt (rai)
Cite this RFC: TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC6128
Discuss this RFC: Send questions or comments to the mailing list avt@ietf.org
Other actions: Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 6128
Abstract
The Session Description Protocol (SDP) has an attribute that allows RTP applications to specify an address and a port associated with the RTP Control Protocol (RTCP) traffic. In RTP-based source-specific multicast (SSM) sessions, the same attribute is used to designate the address and the RTCP port of the Feedback Target in the SDP description. However, the RTCP port associated with the SSM session itself cannot be specified by the same attribute to avoid ambiguity, and thus, is required to be derived from the "m=" line of the media description. Deriving the RTCP port from the "m=" line imposes an unnecessary restriction. This document removes this restriction by introducing a new SDP attribute. [STANDARDS-TRACK]
For the definition of Status, see RFC 2026.
For the definition of Stream, see RFC 8729.