[AVT] FW: New Version Notification for draft-begen-avt-rtp-cnames-01

["Ali C. Begen (abegen)" <[e-mail]>]

Here is the new version of the CNAME draft.

http://www.ietf.org/id/draft-begen-avt-rtp-cnames-01.txt

We took the comments into consideration. Hopefully, the text is almost complete now. Feedback is welcome.

-acbegen

-----Original Message-----
From: IETF I-D Submission Tool [mailto:[e-mail]] 
Sent: Wednesday, May 05, 2010 10:31 AM
To: Ali C. Begen (abegen)
Cc: [e-mail]
Subject: New Version Notification for draft-begen-avt-rtp-cnames-01 


A new version of I-D, draft-begen-avt-rtp-cnames-01.txt has been successfully submitted by Ali Begen and posted to the IETF repository.

Filename:	 draft-begen-avt-rtp-cnames
Revision:	 01
Title:		 Guidelines for Choosing RTP Control Protocol (RTCP) Canonical Names (CNAMEs)
Creation_date:	 2010-05-05
WG ID:		 Independent Submission
Number_of_pages: 6

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
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.
                                                                                  


The IETF Secretariat.