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

Magnus Westerlund <magnus.westerlund@ericsson.com> Mon, 22 April 2013 07:02 UTC

Return-Path: <magnus.westerlund@ericsson.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 DB7D621F8ADC for <avt@ietfa.amsl.com>; Mon, 22 Apr 2013 00:02:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.806
X-Spam-Level:
X-Spam-Status: No, score=-105.806 tagged_above=-999 required=5 tests=[AWL=0.443, BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 UsH+FnQMpoGp for <avt@ietfa.amsl.com>; Mon, 22 Apr 2013 00:02:48 -0700 (PDT)
Received: from mailgw7.ericsson.se (mailgw7.ericsson.se [193.180.251.48]) by ietfa.amsl.com (Postfix) with ESMTP id 828FC21F8551 for <avt@ietf.org>; Mon, 22 Apr 2013 00:02:47 -0700 (PDT)
X-AuditID: c1b4fb30-b7f266d000000cb5-3f-5174e0964872
Received: from esessmw0247.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw7.ericsson.se (Symantec Mail Security) with SMTP id 35.33.03253.690E4715; Mon, 22 Apr 2013 09:02:46 +0200 (CEST)
Received: from [127.0.0.1] (153.88.115.8) by esessmw0247.eemea.ericsson.se (153.88.115.94) with Microsoft SMTP Server id 8.3.279.1; Mon, 22 Apr 2013 09:02:44 +0200
Message-ID: <5174E093.2050604@ericsson.com>
Date: Mon, 22 Apr 2013 09:02:43 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: "Ali C. Begen (abegen)" <abegen@cisco.com>
References: <C15918F2FCDA0243A7C919DA7C4BE9940D00BCE3@xmb-aln-x01.cisco.com>
In-Reply-To: <C15918F2FCDA0243A7C919DA7C4BE9940D00BCE3@xmb-aln-x01.cisco.com>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFuplluLIzCtJLcpLzFFi42KZGfG3Vnfag5JAg8ntihYPts9ltHjZs5Ld gcljyu+NrB5LlvxkCmCK4rJJSc3JLEst0rdL4MrYO/EzS8F1wYo9m1+zNTA+5u1i5OCQEDCR 2DJXt4uRE8gUk7hwbz1bFyMXh5DAKUaJ3zeOsIAkhASWM0r82FwOYvMKaEscn3uAHcRmEVCV aL4xH8xmE7CQuPmjkQ1kpqhAsMTW1hiIckGJkzOfgI0REdCT2N8xjRGkhFlAUWJSuyRIWFjA ReJN42EmiE0+EpPm3GUDsTkFfCV+tK1ghjhNUmLLi3awTcwCmhKt239D2fISzVtnM0P0aks0 NHWwTmAUmoVk8ywkLbOQtCxgZF7FyJ6bmJmTXm6+iREYpAe3/DbYwbjpvtghRmkOFiVx3nDX CwFCAumJJanZqakFqUXxRaU5qcWHGJk4OKUaGPNybRqYvqktdEhZmbhp4vGmlheTFU5dnb7t 6dnPd9Y8eGej9vlz4YZnkVt+Cd7IT2yPCdN84fmlaNmJTomiMxd+1Hgfqn09ad2TMqW3jwR/ VP/+s1E+RduAT4Q5IuDZ3UV8sdkfVh/qePSlPvNBLoscl8yX31NcLyyLDFw96a3szG+huwXX d/cpsRRnJBpqMRcVJwIARR/UYSACAAA=
Cc: "avt@ietf.org" <avt@ietf.org>
Subject: Re: [AVTCORE] I-D Action: draft-ietf-avtcore-6222bis-02.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, 22 Apr 2013 07:02:49 -0000

On 2013-04-22 08:11, Ali C. Begen (abegen) wrote:
> Hi Magnus,
> 
> I am not that knowledgeable about how the virtualization products deal
> with their networking interfaces. While I am not comfortable to make a
> generalization and somewhat blame such products for improper selection of
> mac addresses, what about the following change?
> 
> After the following bullet in section 4.2:
> 
> To produce a short-term persistent RTCP CNAME, an RTP endpoint
>       MUST either (a) use the numeric representation of the layer-2
>       (Media Access Control (MAC)) address of the interface that is used
>       to initiate the initial set of RTP sessions as the "host" part of
>       its RTCP CNAME or (b) generate and use an identifier by following
>       the procedure described in Section 5.  In either case, the
>       procedure is performed once per initialization of the software.
>       After obtaining an identifier in case of (a), the 48 bits are
>       converted to the standard colon-separated hexadecimal format
>       [RFC5342], e.g., "00:23:32:af:9b:aa", resulting in a 17-octet
>       printable string representation.  In case of (b), minimally the
>       least significant 96 bits SHOULD be converted to ASCII using
>       Base64 encoding [RFC4648] (to compromise between packet size and
>       uniqueness - refer to Section 6.1).  If 96 bits are used, the
>       resulting string will be 16 octets.
> 
> 
> Add the following text?
> 
> "In some environments (for example, a virtualized operating system), the
> MAC address may not be unique as expected. In these cases, using option
> (b) above is RECOMMENDED."
> 

Thanks, that is exactly what I wanted. Resolves my issue fully.

I hope others in the WG has input on this.

Cheers

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