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

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

Full text not currently available from Enlighten.

Publisher's URL: http://datatracker.ietf.org/doc/rfc7022/

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.

Item Type:Articles (Other)
Additional Information:This document replaces RFC 6222.
Status:Published
Refereed:Yes
Glasgow Author(s) Enlighten ID:Perkins, Dr Colin
Authors: Begen, A., Perkins, C., Wing, D., and Rescorla, E.
College/School:College of Science and Engineering > School of Computing Science
Research Group:ENDS
Journal Name:Internet RFC
Publisher:Internet Society
ISSN:2070-1721

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