%% You should probably cite draft-ietf-avt-rtp-cnames instead of this I-D. @techreport{begen-avt-rtp-cnames-02, number = {draft-begen-avt-rtp-cnames-02}, type = {Internet-Draft}, institution = {Internet Engineering Task Force}, publisher = {Internet Engineering Task Force}, note = {Work in Progress}, url = {https://datatracker.ietf.org/doc/draft-begen-avt-rtp-cnames/02/}, author = {Ali C. Begen and Colin Perkins and Dan Wing}, title = {{Guidelines for Choosing RTP Control Protocol (RTCP) Canonical Names (CNAMEs)}}, pagetotal = 7, year = 2010, month = may, day = 24, 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, the CNAME is meant to stay unchanged, so that RTP endpoints can be uniquely identified and associated with their RTP media streams. For proper functionality, 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 these guidelines to allow endpoints to choose unique CNAMEs.}, }