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

Dan Wing <dwing@cisco.com> Tue, 26 March 2013 15:45 UTC

Return-Path: <dwing@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 B1E2821F8A5E for <avt@ietfa.amsl.com>; Tue, 26 Mar 2013 08:45:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.359
X-Spam-Level:
X-Spam-Status: No, score=-109.359 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, 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 y2IKbE3jFq2p for <avt@ietfa.amsl.com>; Tue, 26 Mar 2013 08:45:54 -0700 (PDT)
Received: from mtv-iport-3.cisco.com (mtv-iport-3.cisco.com [173.36.130.14]) by ietfa.amsl.com (Postfix) with ESMTP id EEC5321F871C for <avt@ietf.org>; Tue, 26 Mar 2013 08:45:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3038; q=dns/txt; s=iport; t=1364312754; x=1365522354; h=mime-version:subject:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=i86HMeyGyL953TYgAirWu6wnV0qEDzNSjQ0wVRh3kKE=; b=lyzh+BiPTuLm+cDRtNneiGc7tOs2EIScRDIlGzK5mKt1TnDDGB3jREEN hwcq/7IEkYqWAll9qBrLzCppnLtvdwFYcTFeBoJdG9rWo8VH/1IvJeYsm EWGkD79qTZVLx+gn5Plidc9l391DYw9IM0b2Dj59HBBufeLA1UOS1rpkM A=;
X-IronPort-AV: E=Sophos;i="4.84,913,1355097600"; d="scan'208";a="74198404"
Received: from mtv-core-3.cisco.com ([171.68.58.8]) by mtv-iport-3.cisco.com with ESMTP; 26 Mar 2013 15:45:53 +0000
Received: from [10.32.240.194] ([10.32.240.194]) by mtv-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id r2QFjp7d021270; Tue, 26 Mar 2013 15:45:51 GMT
Content-Type: text/plain; charset="iso-8859-1"
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
From: Dan Wing <dwing@cisco.com>
In-Reply-To: <C15918F2FCDA0243A7C919DA7C4BE9940CF74D47@xmb-aln-x01.cisco.com>
Date: Tue, 26 Mar 2013 08:45:51 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <C1137278-360A-46E0-87E5-00955CED6685@cisco.com>
References: <C15918F2FCDA0243A7C919DA7C4BE9940CF74D47@xmb-aln-x01.cisco.com>
To: "Ali C. Begen (abegen)" <abegen@cisco.com>
X-Mailer: Apple Mail (2.1503)
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:45:54 -0000

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.

-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