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

Metadata

Publisher: IETF
Doc Type: Standard
Pages: 10
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.
Publication Date: 2013-09-01
Status Note: Proposed Standard
DOI: 10.17487/RFC7022
Link: https://doi.org/10.17487/RFC7022
Author(s): Ali C. Begen
Colin Perkins
Dan Wing
Eric Rescorla

Latest version of IETF RFC 7022

Document Versions — IETF RFC 7022

▶ IETF RFC 7022 (2013-09-01)

THIS DOC [ACTIVE] [LATEST VERSION]

Normative Reference(s)

IETF RFC 2119 [Active*]
IETF RFC 3550 [Active*]
IETF RFC 4086 [Active*]
IETF RFC 4122 [Superseded*]
IETF RFC 4648 [Active*]

Bibliographic Reference(s)

Rescorla, E., "Random algorithm for RTP CNAME generation" , Work in Progress, July 2012. EXTERNAL
Rescorla, E., "WebRTC Security Architecture" , Work in Progress, July 2013. EXTERNAL
IETF RFC 1918 [Active*]
IETF RFC 3022 [Active*]
IETF RFC 3261 [Active*]
IETF RFC 3711 [Active*]
IETF RFC 4941 [Superseded*]
RFC5245 — 19 EXTERNAL
IETF RFC 5764 [Active*]
IETF RFC 6222 [Superseded*]

Source Data (JSON)

Full registry record with provenance metadata. Open directly: /api/doc/RFC7022.json

Reference Tree

Explore all references and references to this document, as a navigable tree.

Open Reference Tree

Reference this Doc

Plain text (ISO 690 compliant)

Preview:

IETF RFC 7022, Guidelines for Choosing RTP Control Protocol (RTCP) Canonical Names (CNAMEs). Available at https://doi.org/10.17487/RFC7022

Snippet:

IETF RFC 7022, Guidelines for Choosing RTP Control Protocol (RTCP) Canonical Names (CNAMEs). Available at https://doi.org/10.17487/RFC7022

HTML (ISO 690 compliant)

Preview:

IETF RFC 7022, Guidelines for Choosing RTP Control Protocol (RTCP) Canonical Names (CNAMEs). Available at https://doi.org/10.17487/RFC7022

Snippet:

<span class="citation"><cite>IETF RFC 7022</cite>, Guidelines for Choosing RTP Control Protocol (RTCP) Canonical Names (CNAMEs). Available at <a href="https://doi.org/10.17487/RFC7022" target="_blank" rel="noopener">https://doi.org/10.17487/RFC7022</a></span>

SMPTE's HTML Pub

Preview:

IETF RFC 7022, Guidelines for Choosing RTP Control Protocol (RTCP) Canonical Names (CNAMEs)
doi: 10.17487/RFC7022
url: https://doi.org/10.17487/RFC7022

Snippet:

<li>
<cite id="bib-rfc7022">IETF RFC 7022</cite>, Guidelines for Choosing RTP Control Protocol (RTCP) Canonical Names (CNAMEs)
<span class="doi">10.17487/RFC7022</span>
</li>

Referenced By

IETF RFC 7273 [Active*]
IETF RFC 8108 [Active*]