Guidelines for choosing RTP control protocol (RTCP) canonical names (CNAMEs)

Begen, A., Perkins, C., and Wing, D. (2011) Guidelines for choosing RTP control protocol (RTCP) canonical names (CNAMEs). Internet RFC,

Full text not currently available from Enlighten.

Publisher's URL: http://www.ietf.org/rfc/rfc6222.txt

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 are insufficient to achieve this uniqueness. This memo updates those guidelines to allow endpoints to choose unique RTCP CNAMEs.

Item Type:Articles
Status:Published
Refereed:No
Glasgow Author(s) Enlighten ID:Perkins, Dr Colin
Authors: Begen, A., Perkins, C., and Wing, D.
Subjects:Q Science > QA Mathematics > QA75 Electronic computers. Computer science
College/School:College of Science and Engineering > School of Computing Science
Journal Name:Internet RFC
Publisher:Internet Society
ISSN:2070-1721

University Staff: Request a correction | Enlighten Editors: Update this record