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 (RFC 3550) are insufficient to achieve this uniqueness. RFC 6222 was published to update those guidelines to allow endpoints to choose unique RTCP CNAMEs. Unfortunately, later investigations showed that some parts of the new algorithms were unnecessarily complicated and/or ineffective. This document addresses these concerns and replaces RFC 6222.
Document record
- Document ID
- RFC7022
- Published
- September 2013
- Authors
- A. Begen; C. Perkins; D. Wing; E. Rescorla
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- wit
- Pages
- 10
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7007Update to Remove DVI4 from the Recommended Codecs for the RTP Profile for Audio and Video Conferences with Minimal Control (RTP/AVP)Current
August 2013
- RFC 6994Shared Use of Experimental TCP OptionsCurrent
August 2013
- RFC 7053SACK-IMMEDIATELY Extension for the Stream Control Transmission ProtocolObsoleted
November 2013
- RFC 6951UDP Encapsulation of Stream Control Transmission Protocol (SCTP) Packets for End-Host to End-Host CommunicationUpdated
May 2013
- RFC 6937Proportional Rate Reduction for TCPObsoleted
May 2013
- RFC 6928Increasing TCP's Initial WindowCurrent
April 2013
- RFC 6904Encryption of Header Extensions in the Secure Real-time Transport Protocol (SRTP)Current
April 2013
- RFC 7141Byte and Packet Congestion NotificationCurrent
February 2014
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?