Re: [AVTCORE] I-D Action: draft-ietf-avtcore-6222bis-02.txt

"Ali C. Begen (abegen)" <abegen@cisco.com> Sat, 13 April 2013 10:44 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-02.txt
Thread-Index: AQHOODKPqSyveEg+S0yJ9MQm6MP6c5jUfWGA
Date: Sat, 13 Apr 2013 10:44:03 +0000
Message-ID: <C15918F2FCDA0243A7C919DA7C4BE9940CFEF3A5@xmb-aln-x01.cisco.com>
In-Reply-To: <20130413103455.19455.13643.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
user-agent: Microsoft-MacOutlook/14.3.2.130206
Content-Type: text/plain; charset="utf-8"
Content-ID: <4945303E334D57439272E500B6A0DCB6@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Subject: Re: [AVTCORE] I-D Action: draft-ietf-avtcore-6222bis-02.txt
Precedence: list

I think we got all the essential WGLC comments addressed in this revision.
If there is something we skipped, please let us know.

-acbegen

-----Original Message-----
From: "internet-drafts@ietf.org" <internet-drafts@ietf.org>
Date: Saturday, April 13, 2013 1:34 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-02.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-02.txt
>	Pages           : 10
>	Date            : 2013-04-13
>
>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-02
>
>A diff from the previous version is available at:
>http://www.ietf.org/rfcdiff?url2=draft-ietf-avtcore-6222bis-02
>
>
>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
Re: [AVTCORE] I-D Action: draft-ietf-avtcore-6222… Ali C. Begen (abegen)
Re: [AVTCORE] I-D Action: draft-ietf-avtcore-6222… Roni Even
Re: [AVTCORE] I-D Action: draft-ietf-avtcore-6222… Magnus Westerlund
Re: [AVTCORE] I-D Action: draft-ietf-avtcore-6222… Ali C. Begen (abegen)
Re: [AVTCORE] I-D Action: draft-ietf-avtcore-6222… Magnus Westerlund
Re: [AVTCORE] I-D Action: draft-ietf-avtcore-6222… Ali C. Begen (abegen)