csperkins.org

Guidelines for Choosing RTP Control Protocol (RTCP) Canonical Names (CNAMEs)

Ali C. Begen, Colin Perkins, and Dan Wing

Internet Engineering Task Force, RFC 6222, April 2011.

DOI:10.17487/RFC6222

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.

Download: rfc6222.txt

Opinions expressed are my own, and do not represent those of my employers or the organisations that fund my research.