RTP Control Protocol Port for Source-Specific Multicast Sessions
RFC 6128, “RTP Control Protocol Port for Source-Specific Multicast Sessions”, is a Proposed Standard document published in February 2011 by A. Begen. It updates RFC 5760. The canonical text is published by the RFC Editor.
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]
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
The canonical text of RFC 6128 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 6127 IPv4 Run-Out and IPv4-IPv6 Co-Existence Scenarios
- RFC 6129 The 'application/tei+xml' Media Type
- RFC 6126 The Babel Routing Protocol
- RFC 6130 Mobile Ad Hoc Network Neighborhood Discovery Protocol
- RFC 6125 Representation and Verification of Domain-Based Application Service Identity within Internet Public Key Infrastructure Using X.509 Certificates in the Context of Transport Layer Security
- RFC 6131 Sieve Vacation Extension: "Seconds" Parameter
- RFC 6124 An EAP Authentication Method Based on the Encrypted Key Exchange Protocol
- RFC 6132 Sieve Notification Using Presence Information