@misc{rfc6222,
    series =    {Request for Comments},
    number =    6222,
    howpublished =  {RFC 6222},
    publisher = {RFC Editor},
    doi =       {10.17487/RFC6222},
    url =       {https://www.rfc-editor.org/info/rfc6222},
    author =    {Colin Perkins and Ali C. Begen and Dan Wing},
    title =     {{Guidelines for Choosing RTP Control Protocol (RTCP) Canonical Names (CNAMEs)}},
    pagetotal = 9,
    year =      2011,
    month =     apr,
    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{]}},
}