<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.begen-avt-rtp-cnames" target="https://datatracker.ietf.org/doc/html/draft-begen-avt-rtp-cnames-02">
   <front>
      <title>Guidelines for Choosing RTP Control Protocol (RTCP) Canonical Names (CNAMEs)</title>
      <author initials="A. C." surname="Begen" fullname="Ali C. Begen">
         <organization>Cisco</organization>
      </author>
      <author initials="C." surname="Perkins" fullname="Colin Perkins">
         <organization>University of Glasgow</organization>
      </author>
      <author initials="D." surname="Wing" fullname="Dan Wing">
         <organization>Cisco</organization>
      </author>
      <date month="May" day="24" year="2010" />
      <abstract>
	 <t>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.
	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-begen-avt-rtp-cnames-02" />
   
</reference>
