[AVTCORE] FW: I-D Action: draft-ietf-avtcore-6222bis-01.txt

"Ali C. Begen (abegen)" <abegen@cisco.com> Mon, 11 March 2013 22:32 UTC

From: "Ali C. Begen (abegen)" <abegen@cisco.com>
To: "avt@ietf.org" <avt@ietf.org>
Thread-Topic: [AVTCORE] I-D Action: draft-ietf-avtcore-6222bis-01.txt
Thread-Index: AQHOHgbGfj4bECOS7Uyum6wf56PwBJihJTsA
Date: Mon, 11 Mar 2013 22:32:07 +0000
Message-ID: <C15918F2FCDA0243A7C919DA7C4BE9940CF59A31@xmb-aln-x01.cisco.com>
In-Reply-To: <20130311031602.27199.40366.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
user-agent: Microsoft-MacOutlook/14.3.0.121105
Content-Type: text/plain; charset="utf-8"
Content-ID: <8EB1FF12CA91D446A1509309E57DFAF5@cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Subject: [AVTCORE] FW: I-D Action: draft-ietf-avtcore-6222bis-01.txt
Precedence: list

This version has a few changes that should address Kevin G.'s comments. As
far as the authors are concerned, there are no open issues remaining.
Please review and post your comments to the list, if any. We should be
able to last call this pretty soon IMO.

-acbegen

-----Original Message-----
From: "internet-drafts@ietf.org" <internet-drafts@ietf.org>
Date: Sunday, March 10, 2013 11:16 PM
To: "i-d-announce@ietf.org" <i-d-announce@ietf.org>
Cc: "avt@ietf.org" <avt@ietf.org>
Subject: [AVTCORE] I-D Action: draft-ietf-avtcore-6222bis-01.txt

>
>A New Internet-Draft is available from the on-line Internet-Drafts
>directories.
> This draft is a work item of the Audio/Video Transport Core Maintenance
>Working Group of the IETF.
>
>	Title           : Guidelines for Choosing RTP Control Protocol (RTCP)
>Canonical Names (CNAMEs)
>	Author(s)       : Ali Begen
>                          Colin Perkins
>                          Dan Wing
>                          Eric Rescorla
>	Filename        : draft-ietf-avtcore-6222bis-01.txt
>	Pages           : 11
>	Date            : 2013-03-10
>
>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.  RFC 6222 was published to update those
>   guidelines to allow endpoints to choose unique RTCP CNAMEs.
>   Unfortunately, later investigations showed that some parts of the new
>   algorithms were unnecessarily complicated and/or ineffective.  This
>   document addresses these concerns and replaces RFC 6222.
>
>
>The IETF datatracker status page for this draft is:
>https://datatracker.ietf.org/doc/draft-ietf-avtcore-6222bis
>
>There's also a htmlized version available at:
>http://tools.ietf.org/html/draft-ietf-avtcore-6222bis-01
>
>A diff from the previous version is available at:
>http://www.ietf.org/rfcdiff?url2=draft-ietf-avtcore-6222bis-01
>
>
>Internet-Drafts are also available by anonymous FTP at:
>ftp://ftp.ietf.org/internet-drafts/
>
>_______________________________________________
>Audio/Video Transport Core Maintenance
>avt@ietf.org
>https://www.ietf.org/mailman/listinfo/avt
>

[AVTCORE] I-D Action: draft-ietf-avtcore-6222bis-… internet-drafts
[AVTCORE] FW: I-D Action: draft-ietf-avtcore-6222… Ali C. Begen (abegen)