Guidelines for Choosing RTP Control Protocol Canonical Names
RFC 7022, “Guidelines for Choosing RTP Control Protocol Canonical Names”, is a Proposed Standard document published in September 2013 by A. Begen, C. Perkins, D. Wing, E. Rescorla. It updates RFC 3550. It obsoletes RFC 6222. The canonical text is published by the RFC Editor.
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.
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
The canonical text of RFC 7022 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 7021 Assessing the Impact of Carrier-Grade NAT on Network Applications
- RFC 7023 MPLS and Ethernet Operations, Administration, and Maintenance Interworking
- RFC 7020 The Internet Numbers Registry System
- RFC 7024 Virtual Hub-and-Spoke in BGP/MPLS VPNs
- RFC 7019 Application-Layer Multicast Extensions to REsource LOcation And Discovery
- RFC 7025 Requirements for GMPLS Applications of PCE
- RFC 7018 Auto-Discovery VPN Problem Statement and Requirements
- RFC 7026 Retiring TLVs from the Associated Channel Header of the MPLS Generic Associated Channel