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

Magnus Westerlund <magnus.westerlund@ericsson.com> Tue, 26 March 2013 16:45 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 683BC21F8A3E for <avt@ietfa.amsl.com>; Tue, 26 Mar 2013 09:45:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.474
X-Spam-Level:
X-Spam-Status: No, score=-105.474 tagged_above=-999 required=5 tests=[AWL=-0.465, 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 Cf0KUw-TFm7C for <avt@ietfa.amsl.com>; Tue, 26 Mar 2013 09:45:37 -0700 (PDT)
Received: from mailgw1.ericsson.se (mailgw1.ericsson.se [193.180.251.45]) by ietfa.amsl.com (Postfix) with ESMTP id 786A821F8A41 for <avt@ietf.org>; Tue, 26 Mar 2013 09:45:34 -0700 (PDT)
X-AuditID: c1b4fb2d-b7f316d0000028db-f5-5151d0aba3bf
Received: from esessmw0184.eemea.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw1.ericsson.se (Symantec Mail Security) with SMTP id 17.0F.10459.BA0D1515; Tue, 26 Mar 2013 17:45:32 +0100 (CET)
Received: from [127.0.0.1] (153.88.115.8) by esessmw0184.eemea.ericsson.se (153.88.115.82) with Microsoft SMTP Server id 8.3.279.1; Tue, 26 Mar 2013 17:45:32 +0100
Message-ID: <5151D0AB.6010804@ericsson.com>
Date: Tue, 26 Mar 2013 17:45:31 +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: <C15918F2FCDA0243A7C919DA7C4BE9940CF755B0@xmb-aln-x01.cisco.com>
In-Reply-To: <C15918F2FCDA0243A7C919DA7C4BE9940CF755B0@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+NgFprPLMWRmVeSWpSXmKPExsUyM+Jvje6aC4GBBl3ruS0ebJ/LaPGyZyW7 xekJ9xgtLl57yOTA4jHl90ZWjyVLfjJ5fLn8mS2AOYrLJiU1J7MstUjfLoEr40PvWtaCxUIV 95pPsTYwnuTrYuTkkBAwkVgz5zQ7hC0mceHeerYuRi4OIYGTjBIn7k1mhnCWM0pMfvCbGaSK V0Bb4uKdXWwgNouAqsSFXesZQWw2AQuJmz8aweKiAsESP1+dYYGoF5Q4OfMJmC0ioCexv2Ma WD2zwFJGiWnLI0FsYQEXiX+THgDFOYCW+Ugc7zMECXMK+Eq83DKZEeI4SYktL9rZIVo1JVq3 /4ay5SWat84GO00I6LSGpg7WCYxCs5BsnoWkZRaSlgWMzKsY2XMTM3PSyw03MQID+eCW37o7 GE+dEznEKM3BoiTOG+Z6IUBIID2xJDU7NbUgtSi+qDQntfgQIxMHp1QDo7/C78hcwdB34fuX S92PSX+fwxkSx/3hNfsOu81rw37XH30trG1wx8JL6p3W/ZDdZww4Vm0S3+IZ7e+sn/a0r4Lz 6conTNf9XRZr2j0xYVGNffpm4oSSRTqT7Ot+/o74sJpxgYs5fyHrg7O3WXj5PF9t3T55cpao opTq5dfOcidWmf9r/RTho8RSnJFoqMVcVJwIAFNiUkAyAgAA
Cc: "draft-ietf-avtcore-6222bis@tools.ietf.org" <draft-ietf-avtcore-6222bis@tools.ietf.org>, "avt@ietf.org" <avt@ietf.org>, "Dan Wing (dwing)" <dwing@cisco.com>
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:45:38 -0000

On 2013-03-26 16:51, Ali C. Begen (abegen) wrote:

>>>>
>>>> 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.
>>
>> I think what Magnus is saying is that one person's long term is another
>> person's short term, and the text needs to explain this situation.  How
>> about this:
>>
>>    For the duration of an RTP session, different interfaces
>>    might be used.  For example, a single RTP session might be
>>    established on a WiFi interface and a mobility event moves
>>    that session to a 3G interface.  When such an interface change
>>    occurs, the same CNAME MUST be retained.
> 
> Regardless of what method you use to produce a CNAME or how many
> interfaces you have or whether you roam from one to another during an RTP
> session, you must keep the same CNAME anyway. I think we wanted to say
> this thru "In either case, the procedure is performed once per
> initialization of the software." But your clarification is helpful, I
> agree.
> 

Exactly, this what was I was after. The main point is the need to
continue using the same CNAME during the whole communication session
that include any set of RTP sessions.

I will leave it the authors hands to do what you think are the best word
smithing to improve 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
----------------------------------------------------------------------