RFC 6222: Guidelines for Choosing RTP Control Protocol (RTCP) Canonical Names (CNAMEs)
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 7022.
Current version: RFC 7022 — Guidelines for Choosing RTP Control Protocol (RTCP) Canonical Names (CNAMEs)
In plain English — editorial summary, not part of the RFC
The RTP Control Protocol (RTCP) Canonical Name (CNAME) is a persistent transport-level identifier for an RTP endpoint. While the Synchronization Source (SSRC) identifier of an RTP endpoint may change if a collision is detected or when the RTP application is restarted, its RTCP CNAME is meant to stay unchanged, so that RTP endpoints can be uniquely identified and associated with their RTP media streams. For proper functionality, RTCP CNAMEs should be unique within the participants of an RTP session. However, the existing guidelines for choosing the RTCP CNAME provided in the RTP standard are insufficient to achieve this uniqueness. This memo updates those guidelines to allow endpoints to choose unique RTCP CNAMEs. [STANDARDS-TRACK]
Document record
- Document ID
- RFC6222
- Published
- April 2011
- Authors
- A. Begen; C. Perkins; D. Wing
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rai
- Pages
- 9
- Also known as
- —
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6225Dynamic Host Configuration Protocol Options for Coordinate-Based Location Configuration InformationCurrent
July 2011
- RFC 6230Media Control Channel FrameworkCurrent
May 2011
- RFC 6231An Interactive Voice Response (IVR) Control Package for the Media Control Channel FrameworkUpdated
May 2011
- RFC 6188The Use of AES-192 and AES-256 in Secure RTPCurrent
March 2011
- RFC 6185RTP Payload Format for H.264 Reduced-Complexity Decoding Operation (RCDO) VideoCurrent
May 2011
- RFC 6184RTP Payload Format for H.264 VideoCurrent
May 2011
- RFC 6271Requirements for SIP-Based Session PeeringCurrent
June 2011
- RFC 6280An Architecture for Location and Location Privacy in Internet ApplicationsCurrent
July 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?