RFC 6222 · PROPOSED STANDARD · 2011

Guidelines for Choosing RTP Control Protocol Canonical Names

Overview

RFC 6222, “Guidelines for Choosing RTP Control Protocol Canonical Names”, is a Proposed Standard document published in April 2011 by A. Begen, C. Perkins, D. Wing. It updates RFC 3550. It has been obsoleted by RFC 7022 — refer to the newer document for the authoritative version. 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 are insufficient to achieve this uniqueness. This memo updates those guidelines to allow endpoints to choose unique RTCP CNAMEs. [STANDARDS-TRACK]

Abstract as published in the RFC, via rfc-editor.org.

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.

Read this RFC

The canonical text of RFC 6222 is hosted at rfc-editor.org. Available in TXT,HTML.

Relationships to other RFCs
Obsoleted by
RFC 7022
This RFC updates
RFC 3550
Other RFCs from 2011

Who Is Online

In total there are 45 users online: 0 registered, 39 guests and 6 bots.

Most users ever online was 1,226 on 13 Jun 2026, 3:56 am.

Bots: AhrefsBot Applebot Googlebot Other Bot SemrushBot Sogou

Users active in the past 15 minutes. Total registered members: 354