Search RFCs

RFC Editor

File formats:

Status:

PROPOSED STANDARD

Obsoletes:

RFC 6222

Updates:

RFC 3550

Authors:

A. Begen
C. Perkins
D. Wing
E. Rescorla

Stream:

IETF

Source:

avtcore (wit)

Cite this RFC:TXT  | XML  |  BibTeX

DOI:  https://doi.org/10.17487/RFC7022

Discuss this RFC: Send questions or comments to the mailing listavt@ietf.org

Other actions:Submit Errata  | Find IPR Disclosures from the IETF  | View History of RFC 7022

Abstract

The RTP Control Protocol (RTCP) Canonical Name (CNAME) is apersistent transport-level identifier for an RTP endpoint. While theSynchronization Source (SSRC) identifier of an RTP endpoint maychange if a collision is detected or when the RTP application isrestarted, its RTCP CNAME is meant to stay unchanged, so that RTPendpoints can be uniquely identified and associated with their RTPmedia streams.

For proper functionality, RTCP CNAMEs should be unique within theparticipants of an RTP session. However, the existing guidelines forchoosing the RTCP CNAME provided in the RTP standard (RFC 3550) areinsufficient to achieve this uniqueness. RFC 6222 was published toupdate those guidelines to allow endpoints to choose unique RTCPCNAMEs. Unfortunately, later investigations showed that some partsof the new algorithms were unnecessarily complicated and/orineffective. This document addresses these concerns and replaces RFC6222.

For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.