RFC 6128: RTP Control Protocol (RTCP) Port for Source-Specific Multicast (SSM) Sessions
In plain English — editorial summary, not part of the RFC
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]
Document record
- Document ID
- RFC6128
- Published
- February 2011
- Authors
- A. Begen
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rai
- Pages
- 6
- Also known as
- —
- Updates:
- RFC 5760
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6135An Alternative Connection Model for the Message Session Relay Protocol (MSRP)Current
February 2011
- RFC 6118Update of Legacy IANA Registrations of EnumservicesCurrent
March 2011
- RFC 6117IANA Registration of Enumservices: Guide, Template, and IANA ConsiderationsCurrent
March 2011
- RFC 6140Registration for Multiple Phone Numbers in the Session Initiation Protocol (SIP)Current
March 2011
- RFC 6116The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application (ENUM)Current
March 2011
- RFC 6155Use of Device Identity in HTTP-Enabled Location Delivery (HELD)Updated
March 2011
- RFC 6157IPv6 Transition in the Session Initiation Protocol (SIP)Current
April 2011
- RFC 6080A Framework for Session Initiation Protocol User Agent Profile DeliveryCurrent
March 2011
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?