Re: [AVTCORE] WG last call on draft-ietf-avtcore-6222bis-01

Magnus Westerlund <magnus.westerlund@ericsson.com> Tue, 26 March 2013 16:40 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 3617621F8C8F for <avt@ietfa.amsl.com>; Tue, 26 Mar 2013 09:40:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.629
X-Spam-Level:
X-Spam-Status: No, score=-105.629 tagged_above=-999 required=5 tests=[AWL=-0.620, BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4, SARE_LWSHORTT=1.24, 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 ny2U4DuDL396 for <avt@ietfa.amsl.com>; Tue, 26 Mar 2013 09:40:48 -0700 (PDT)
Received: from mailgw7.ericsson.se (mailgw7.ericsson.se [193.180.251.48]) by ietfa.amsl.com (Postfix) with ESMTP id 6EDE321F8C71 for <avt@ietf.org>; Tue, 26 Mar 2013 09:40:47 -0700 (PDT)
X-AuditID: c1b4fb30-b7f0d6d000007e61-75-5151cf8e9682
Received: from esessmw0191.eemea.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw7.ericsson.se (Symantec Mail Security) with SMTP id 25.0A.32353.E8FC1515; Tue, 26 Mar 2013 17:40:46 +0100 (CET)
Received: from [127.0.0.1] (153.88.115.8) by esessmw0191.eemea.ericsson.se (153.88.115.85) with Microsoft SMTP Server id 8.3.279.1; Tue, 26 Mar 2013 17:40:45 +0100
Message-ID: <5151CF8C.5080304@ericsson.com>
Date: Tue, 26 Mar 2013 17:40:44 +0100
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130307 Thunderbird/17.0.4
MIME-Version: 1.0
To: "Ali C. Begen (abegen)" <abegen@cisco.com>
References: <C15918F2FCDA0243A7C919DA7C4BE9940CF74D47@xmb-aln-x01.cisco.com>
In-Reply-To: <C15918F2FCDA0243A7C919DA7C4BE9940CF74D47@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+NgFprFLMWRmVeSWpSXmKPExsUyM+JvjW7f+cBAgx+dEhYPts9ltHjZs5Ld 4vSEe4wOzB5Tfm9k9Viy5CeTx5fLn9kCmKO4bFJSczLLUov07RK4Mh6cuMxcsFu4YmvLP8YG xi38XYycHBICJhInr09jhLDFJC7cW88GYgsJnGSUmN+S08XIBWQvZ5TY9WsBE0iCV0BbovFS I5jNIqAqsfjMdbAGNgELiZs/GsFsUYFgiZ+vzrBA1AtKnJz5BMwWEdCT2N8BsYxZoFbi7ov1 rCC2sICLxL9JDxghFvtI9E/5zAxicwr4Smxu3ckEcZykxJYX7ewQvZoSrdt/Q9nyEs1bZzND 9GpLNDR1sE5gFJqFZPUsJC2zkLQsYGRexciem5iZk15uvokRGL4Ht/w22MG46b7YIUZpDhYl cd5w1wsBQgLpiSWp2ampBalF8UWlOanFhxiZODilGhgrPyl6v9aZ23Zx4TsGlx53c4P27ScT DZfusVvMPFmXzbFuYUp54JSbE/SeH5HxZi85HnL+7LPYv6tj4+OWuZV8nrUw+Jth5wGONy7T 2o1aQmIylW9/DD41Maf1+MmbeyLvKb/7UzFboEH1SJve5KTChb0832dmpW0QT7v63PBR3ruC KQFSCsZKLMUZiYZazEXFiQBfmp6JLQIAAA==
Cc: "draft-ietf-avtcore-6222bis@tools.ietf.org" <draft-ietf-avtcore-6222bis@tools.ietf.org>, "avt@ietf.org" <avt@ietf.org>
Subject: Re: [AVTCORE] WG last call on draft-ietf-avtcore-6222bis-01
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: Tue, 26 Mar 2013 16:40:49 -0000

On 2013-03-26 10:57, Ali C. Begen (abegen) wrote:
> -----Original Message-----
> From: Magnus Westerlund <magnus.westerlund@ericsson.com>
>>>
>>>> wonder of its persistence behavior as it says to use the MAC of
>>>> the Interface that ones initiate the communication over. With
>>>> multiple interfaces, I can in the context of an application use all
>>>> of these interfaces over a set of calls. Thus it doesn't have
>>>> particular good long term stability either.
>>>
>>> I think it is meant to say the interface over which the initial
>>> connection was made not all other possible interfaces that could be
>>> used during the rtp session.
>>>>
>>
>> The main point I try to get across is that which interface you use for
>> the initial connection varies between different communication
>> establishments. If your goal is to have a long term persistent
>> identifier then you need to store the first one used in the context of
>> an application and use that, rather than take the interface you used for
>> the SIP dialog, or similar, used to establish this particular RTP
>> session(s).
> 
> The text is not saying to use MAC for long-term persistent CNAME. It says
> to use it for *short-term* persistency. Sorry, I am not getting where
> there is unclarity.
> 

Sorry, about the short term vs. long term persistence. My mixup.

I think the text that exist is likely to produce the desired result, but
not really clear. As the aspect that the same short term persistent
CNAME needs to be used over all the RTP sessions part of the same
communication session is not that explicit.

One improvement could be to say:

   o  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

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