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

"Ali C. Begen (abegen)" <abegen@cisco.com> Tue, 26 March 2013 15:52 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 9AB6221F8BA6 for <avt@ietfa.amsl.com>; Tue, 26 Mar 2013 08:52:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.979
X-Spam-Level:
X-Spam-Status: No, score=-9.979 tagged_above=-999 required=5 tests=[AWL=-0.620, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, SARE_LWSHORTT=1.24]
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 m-eXgCvy8S7O for <avt@ietfa.amsl.com>; Tue, 26 Mar 2013 08:52:27 -0700 (PDT)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) by ietfa.amsl.com (Postfix) with ESMTP id BD3D521F8B0C for <avt@ietf.org>; Tue, 26 Mar 2013 08:52:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5236; q=dns/txt; s=iport; t=1364313146; x=1365522746; h=from:to:cc:subject:date:message-id:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=G3vnVcH5GFCv77b/k1Fpahv45FlAuEvt3KohhQSvUc8=; b=WzIIxbD9fUqUFeWWEIAz5325ej1liOPsEIKChuvKQkW7BVB4/RWruHK4 TDg213ZaR/sTrk/237YHCQDxterB5SS6RuKV6NxPk046RaVa4jlnLFb3H Cp8Ova+GM3nED0RuIqawluCflGbTZZStChww0HgxzIhWt/DZ6293Xveb1 M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AkIFAIDDUVGtJXHA/2dsb2JhbABDgmeDFlq9Kw15FoEqgh8BAQEEAQEBCRcRRQwCBAEGAhEDAQIBAgIGHQMCBBkMCxQBCAgCBA4FCIgMAQuTSJsEgkCPfgQEgR+NPAIWEAsHBoInMmEDp26DCoIo
X-IronPort-AV: E=Sophos;i="4.84,913,1355097600"; d="scan'208";a="191622987"
Received: from rcdn-core2-5.cisco.com ([173.37.113.192]) by rcdn-iport-5.cisco.com with ESMTP; 26 Mar 2013 15:52:26 +0000
Received: from xhc-rcd-x06.cisco.com (xhc-rcd-x06.cisco.com [173.37.183.80]) by rcdn-core2-5.cisco.com (8.14.5/8.14.5) with ESMTP id r2QFqQ5Y003337 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 26 Mar 2013 15:52:26 GMT
Received: from xmb-aln-x01.cisco.com ([fe80::747b:83e1:9755:d453]) by xhc-rcd-x06.cisco.com ([173.37.183.80]) with mapi id 14.02.0318.004; Tue, 26 Mar 2013 10:52:25 -0500
From: "Ali C. Begen (abegen)" <abegen@cisco.com>
To: "Dan Wing (dwing)" <dwing@cisco.com>
Thread-Topic: [AVTCORE] WG last call on draft-ietf-avtcore-6222bis-01
Thread-Index: AQHOH1SRBgQ8NzU4bUC2VIRlvWTydpi2+uKA///tk62AATsWAIAAExuAgABQfoCAABKYAA==
Date: Tue, 26 Mar 2013 15:51:43 +0000
Message-ID: <C15918F2FCDA0243A7C919DA7C4BE9940CF755B0@xmb-aln-x01.cisco.com>
In-Reply-To: <C1137278-360A-46E0-87E5-00955CED6685@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.3.2.130206
x-originating-ip: [10.61.98.55]
Content-Type: text/plain; charset="utf-8"
Content-ID: <8BD27E1D0DD59F4FBAB00E1FDF01A3DD@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Cc: Magnus Westerlund <magnus.westerlund@ericsson.com>, "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 15:52:27 -0000

-----Original Message-----
From: Dan Wing <dwing@cisco.com>
Date: Tuesday, March 26, 2013 5:45 PM
To: "Ali C. Begen" <abegen@cisco.com>
Cc: Magnus Westerlund <magnus.westerlund@ericsson.com>,
"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

>
>On Mar 26, 2013, at 2:57 AM, Ali C. Begen (abegen) <abegen@cisco.com>
>wrote:
>
>> -----Original Message-----
>> From: Magnus Westerlund <magnus.westerlund@ericsson.com>
>> Date: Tuesday, March 26, 2013 11:49 AM
>> To: "Ali C. Begen" <abegen@cisco.com>
>> Cc: "avt@ietf.org" <avt@ietf.org>,
>> "draft-ietf-avtcore-6222bis@tools.ietf.org"
>> <draft-ietf-avtcore-6222bis@tools.ietf.org>
>> Subject: Re: [AVTCORE] WG last call on draft-ietf-avtcore-6222bis-01
>> 
>>> On 2013-03-25 21:00, Ali C. Begen (abegen) wrote:
>>>> Thanks for the review.
>>>> 
>>>> On Mar 25, 2013, at 5:07 PM, "Magnus Westerlund"
>>>> <magnus.westerlund@ericsson.com> wrote:
>>>> 
>>>>> 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.
>
>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.

>
>-d
>
>
>
>
>> 
>> 
>>> 
>>> 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
>>> ----------------------------------------------------------------------
>>> 
>>> 
>> 
>> 
>> _______________________________________________
>> Audio/Video Transport Core Maintenance
>> avt@ietf.org
>> https://www.ietf.org/mailman/listinfo/avt
>
>