database logo graphic

RFC 7022

"Guidelines for Choosing RTP Control Protocol (RTCP) Canonical Names (CNAMEs)", September 2013

Canonical URL:
http://www.rfc-editor.org/rfc/rfc7022.txt
This document is also available in this non-normative format: PDF.
Status:
PROPOSED STANDARD
Obsoletes:
RFC 6222
Updates:
RFC 3550
Authors:
A. Begen
C. Perkins
D. Wing
E. Rescorla
Stream:
IETF
Source:
avtcore (rai)

Cite this RFC: TXT  |  XML

Other actions: Find Errata (if any)  |  Submit Errata  |  Find IPR Disclosures from the IETF


Abstract

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.


For the definition of Status, see RFC 2026.

For the definition of Stream, see RFC 4844.


Go to the RFC Editor Homepage.