I-D Action:draft-begen-avt-rtp-cnames-01.txt

Internet-Drafts@ietf.org Wed, 05 May 2010 14:45 UTC

From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Subject: I-D Action:draft-begen-avt-rtp-cnames-01.txt
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20100505144501.E0FC228C344@core3.amsl.com>
Date: Wed, 05 May 2010 07:45:01 -0700
Precedence: list
Reply-To: internet-drafts@ietf.org

A New Internet-Draft is available from the on-line Internet-Drafts directories.

	Title           : Guidelines for Choosing RTP Control Protocol (RTCP) Canonical Names (CNAMEs)
	Author(s)       : A. Begen, C. Perkins
	Filename        : draft-begen-avt-rtp-cnames-01.txt
	Pages           : 6
	Date            : 2010-05-05

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
recommendations for choice of the RTCP CNAME provided in RFC 3550 are
insufficient to achieve this uniqueness.  This memo updates the
guidelines in RFC 3550 to allow endpoints to choose unique CNAMEs.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-begen-avt-rtp-cnames-01.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

ftp://ftp.ietf.org/internet-drafts/draft-begen-avt-rtp-cnames-01.txt"><ftp://ftp.ietf.org/internet-drafts/draft-begen-avt-rtp-cnames-01.txt>

I-D Action:draft-begen-avt-rtp-cnames-01.txt Internet-Drafts