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

"Ali C. Begen (abegen)" <abegen@cisco.com> Mon, 15 July 2013 17:26 UTC

Return-Path: <abegen@cisco.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4ADA121E80FA for <avt@ietfa.amsl.com>; Mon, 15 Jul 2013 10:26:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.299
X-Spam-Level:
X-Spam-Status: No, score=-10.299 tagged_above=-999 required=5 tests=[AWL=0.300, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Su+Nc67t0coj for <avt@ietfa.amsl.com>; Mon, 15 Jul 2013 10:26:08 -0700 (PDT)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) by ietfa.amsl.com (Postfix) with ESMTP id 8CBD711E8105 for <avt@ietf.org>; Mon, 15 Jul 2013 10:26:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5141; q=dns/txt; s=iport; t=1373909168; x=1375118768; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=wvwHx1Mebj6DnU+JCJwRNIXvXhC9+lccTMWmP4l4d9U=; b=bkC+RfTAR+SXFp6LhVpoUmihcwsIs/1Ed+gpMHwjDGKF3cSHEKyfcxmB PqzXdhZZ4npKV/ZWZeOoQYuA/8AcHGX/4FXXRXp4N71/I4wqxMT9VCB89 d7/5Q//Z2HpyjKaVWmeWpSW8dI7RPd24MFHZiIcBr8dzya5LhyKTPrIlV s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ah4FAFIv5FGtJXHB/2dsb2JhbABXA4JlITRJBsFSgRMWdIIjAQEBAwEBAQEJPTAFCQICAQgYCh0HGwwLFBECBA4FCAGIAQYBBgW1ZASPLQIhEAcRgnptA4hvkBaQJIMSgig
X-IronPort-AV: E=Sophos;i="4.89,670,1367971200"; d="scan'208";a="234837398"
Received: from rcdn-core2-6.cisco.com ([173.37.113.193]) by rcdn-iport-1.cisco.com with ESMTP; 15 Jul 2013 17:26:06 +0000
Received: from xhc-aln-x09.cisco.com (xhc-aln-x09.cisco.com [173.36.12.83]) by rcdn-core2-6.cisco.com (8.14.5/8.14.5) with ESMTP id r6FHQ5sY015893 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 15 Jul 2013 17:26:05 GMT
Received: from xmb-aln-x01.cisco.com ([fe80::747b:83e1:9755:d453]) by xhc-aln-x09.cisco.com ([173.36.12.83]) with mapi id 14.02.0318.004; Mon, 15 Jul 2013 12:26:05 -0500
From: "Ali C. Begen (abegen)" <abegen@cisco.com>
To: Kevin Gross <kevin.gross@avanw.com>
Thread-Topic: [AVTCORE] I-D Action: draft-ietf-avtcore-6222bis-05.txt
Thread-Index: AQHOfCI4duxf3HHV+EK539KA5+dpqJlcUx0AgAoEwACAAAR2AA==
Date: Mon, 15 Jul 2013 17:26:04 +0000
Message-ID: <C15918F2FCDA0243A7C919DA7C4BE9940D1E6F5F@xmb-aln-x01.cisco.com>
References: <20130708212917.31411.52919.idtracker@ietfa.amsl.com> <51DBC578.9000306@ericsson.com> <CALw1_Q0YEQmXpCCercTxRpq97whcM4nswcZqSodbKW8b_asmoA@mail.gmail.com>
In-Reply-To: <CALw1_Q0YEQmXpCCercTxRpq97whcM4nswcZqSodbKW8b_asmoA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.21.149.67]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <A2A9DD6F03F61845B1004F308B5460DA@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Magnus Westerlund <magnus.westerlund@ericsson.com>, "avt@ietf.org" <avt@ietf.org>
Subject: Re: [AVTCORE] I-D Action: draft-ietf-avtcore-6222bis-05.txt
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Jul 2013 17:26:13 -0000

MAC addresses are not unique anymore, so cannot be reliably used for cname generation.

On Jul 15, 2013, at 10:10 AM, Kevin Gross <kevin.gross@avanw.com> wrote:

> Yes, this is a significant change. It appears to imply that a cryptographic PRNG is required in every RTP device and things will be more difficult for 3rd party network performance monitoring systems.
> 
> Although there is discussion in the draft downplaying these issues, there are RTP applications that won't otherwise require a CPRNG and there are applications where ease of monitoring is more important than security.
> 
> What was the reason given for wanting to remove the MAC option?
> 
> If we go with this, I suggest an editorial pass to reduce repetition in the last two bullets in section 4.2 and clean up references to "multiple", "several" as there are now only two methods recommended for generating CNAMEs. Let me know if you need any help with this.
> 
> Kevin Gross
> +1-303-447-0517
> Media Network Consultant
> AVA Networks - www.AVAnw.com, www.X192.org
> 
> 
> On Tue, Jul 9, 2013 at 2:10 AM, Magnus Westerlund <magnus.westerlund@ericsson.com> wrote:
> WG,
> 
> This document has just been in IESG review and the authors has discussed
> with the IESG. One discuss raised was the implications of the MAC based
> generation of short-term persistent CNAMES. The conclusion in that
> discussion was to remove that option and rely only on random names in
> that case.
> 
> I wanted to inform the WG about this significant change and give you a
> chance to react to this change before the document is approved. You will
> have one week to react.
> 
> The details can be seen in this diff:
> http://www.ietf.org/rfcdiff?url2=draft-ietf-avtcore-6222bis-05
> 
> 
> Cheers
> 
> Magnus Westerlund
> 
> 
> On 2013-07-08 23:29, internet-drafts@ietf.org wrote:
> >
> > 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-05.txt
> >       Pages           : 10
> >       Date            : 2013-07-08
> >
> > 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-05
> >
> > A diff from the previous version is available at:
> > http://www.ietf.org/rfcdiff?url2=draft-ietf-avtcore-6222bis-05
> >
> >
> > 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
> >
> >
> 
> 
> --
> 
> Magnus Westerlund
> 
> ----------------------------------------------------------------------
> Multimedia Technologies, Ericsson Research EAB/TVM
> ----------------------------------------------------------------------
> Ericsson AB                | Phone  +46 10 7148287
> Färögatan 6                | Mobile +46 73 0949079
> SE-164 80 Stockholm, Sweden| mailto: magnus.westerlund@ericsson.com
> ----------------------------------------------------------------------
> 
> _______________________________________________
> Audio/Video Transport Core Maintenance
> avt@ietf.org
> https://www.ietf.org/mailman/listinfo/avt
> 
> _______________________________________________
> Audio/Video Transport Core Maintenance
> avt@ietf.org
> https://www.ietf.org/mailman/listinfo/avt