Re: [netext] [Fwd: I-D Action: draft-ietf-netext-pmipv6-flowmob-09.txt]

Hidetoshi Yokota <yokota@kddilabs.jp> Sun, 22 June 2014 00:47 UTC

Return-Path: <yokota@kddilabs.jp>
X-Original-To: netext@ietfa.amsl.com
Delivered-To: netext@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 16D431B284B for <netext@ietfa.amsl.com>; Sat, 21 Jun 2014 17:47:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.958
X-Spam-Level: **
X-Spam-Status: No, score=2.958 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3IPppmSLZtRi for <netext@ietfa.amsl.com>; Sat, 21 Jun 2014 17:47:25 -0700 (PDT)
Received: from mandala.kddilabs.jp (mandala.kddilabs.jp [IPv6:2001:200:601:12::16]) by ietfa.amsl.com (Postfix) with ESMTP id C72C01B2848 for <netext@ietf.org>; Sat, 21 Jun 2014 17:47:24 -0700 (PDT)
Received: from localhost (mandala.kddilabs.jp [127.0.0.1]) by mandala.kddilabs.jp (Postfix) with ESMTP id 63767174817D; Sun, 22 Jun 2014 09:47:20 +0900 (JST)
X-Virus-Scanned: amavisd-new at kddilabs.jp
Received: from mandala.kddilabs.jp ([127.0.0.1]) by localhost (mandala.kddilabs.jp [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q7l7wcVyWtvR; Sun, 22 Jun 2014 09:47:18 +0900 (JST)
Received: from ultra.mip.kddilabs.jp (ultra.mip.kddilabs.jp [172.19.90.145]) by mandala.kddilabs.jp (Postfix) with ESMTP id 5D3411748118; Sun, 22 Jun 2014 09:47:18 +0900 (JST)
Received: from [127.0.0.1] (unknown [10.8.0.6]) by ultra.mip.kddilabs.jp (Postfix) with ESMTP id C60591B866; Sun, 22 Jun 2014 09:32:12 +0900 (JST)
Message-ID: <53A6277F.6080608@kddilabs.jp>
Date: Sun, 22 Jun 2014 09:46:55 +0900
From: Hidetoshi Yokota <yokota@kddilabs.jp>
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: =?UTF-8?B?Q2FybG9zIEplc8O6cyBCZXJuYXJkb3MgQ2Fubw==?= <cjbc@it.uc3m.es>
References: <1402679783.4063.11.camel@acorde.it.uc3m.es> <53A269DB.6050504@kddilabs.jp> <1403199406.4456.36.camel@acorde.it.uc3m.es>
In-Reply-To: <1403199406.4456.36.camel@acorde.it.uc3m.es>
Content-Type: multipart/alternative; boundary="------------050007050105040405020704"
Archived-At: http://mailarchive.ietf.org/arch/msg/netext/2nvlSQvJKn-A0L-V6sMUw9Femmo
Cc: "netext@ietf.org" <netext@ietf.org>
Subject: Re: [netext] [Fwd: I-D Action: draft-ietf-netext-pmipv6-flowmob-09.txt]
X-BeenThere: netext@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Mailing list for discusion of extensions to network mobility protocol, i.e PMIP6. " <netext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netext>, <mailto:netext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/netext/>
List-Post: <mailto:netext@ietf.org>
List-Help: <mailto:netext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netext>, <mailto:netext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 22 Jun 2014 00:47:27 -0000

Hi Carlos,

Thanks for your response and the discussion is getting more active 
towards the WGLC!

Please see inline:

(2014/06/20 2:36), Carlos Jesús Bernardos Cano wrote:
> Hi Hidetoshi,
>
> Thanks for your comments. Please see inline below.
>
> On Thu, 2014-06-19 at 13:40 +0900, Hidetoshi Yokota wrote:
>> Hello Carlos,
>>
>> Thanks for updating the draft.
>> I have a couple of questions and comments:
>>
>> o In Section 3.2.1, which is the shared prefix case, there is no
>> message exchange between the LMA and MAG, so there is no flow
>> information on the MAG side. It should work in the sense of routing,
>> but if, for example, each flow has a specific QoS, the MAG should also
>> need to know which flow should go on which QoS path especially for
>> upstream traffic towards the LMA. Or, the MAG may want to send a
>> trigger for flow mobility to the MN (the exact mechanism is out of
>> scope).  Some mobility signaling should be there, too.
> [Carlos] There was a discussion on this in the past (don't remember
> exactly when, but I recall that Rajeev was one of the drivers) and the
> group decision was to make the signaling at the prefix level, not at
> flow level. If the group think there is value on supporting
> flow-granularity signaling, we could add it.

Flow movement at the prefix level is ok, but the new MAG needs to know 
which flow(s) is/are coming within that prefix to link it/them to proper 
QoS path(s) and optionally to inform the MN about it. Actual use cases 
would require more than just routing.

>> o In Section 3.3, FMI/FMA are revived considering the case where UPN
>> is not supported, but they convey very little information. There is no
>> special information that cannot be conveyed by the existing messages.
>> Since RFC7077 is now a proposed standard, I cannot think of a
>> situation where the UPN/UPA are not supported, nevertheless FMI/FMA
>> are supported. It rather seems more natural to mandate the support of
>> RFC7077 or to mandate FMI/FMA for all flow mobility operations.
>> Also, when compared with UPN/UPA case in Figure 4, FMI/FMA seem to
>> convey different set of parameters in Figure 7. Could you clarify it a
>> little bit more please?
>>
> [Carlos] As Pierrick has already replied to you, there was discussion in
> London about supporting both mechanisms. I think this deserves another
> thread on the mailing list devoted to that discussion. As I expressed in
> a previous e-mail, my personal opinion as WG member is that we should go
> for just one signaling mechanism (being UPN/UPA my preference), but here
> I'm acting as the editor of the document and I just updated the document
> to reflect the consensus of the room in London.

I see, but Sri has a different view on it. Let's discuss it on the ML. I 
also prefer to stick to one set of signaling messages.

>> o In Section 3.3, just above Figure 7, there is a description: "...,
>> and the type of flow mobility operation (add flow)", but does RFC6089
>> define such an operation code? This kind of operation should also be
>> defined in the draft.
> [Carlos] By "add", a lifetime higher than 0 is meant (as 0 means
> "remove"). I agree this should be clarified in the document. Thanks for
> the comment.

Not only clarifying the text, but also more explicit mobility operation 
commands such as "add" or "remove" should be defined rather than using 
the lifetime value. This would be more true if the flow movement is at 
the prefix level; you don't want to lose all flows with the same prefix 
by setting the lifetime value to zero for removing just one flow. Please 
take it into consideration.

Regards,

-- 
Hidetoshi Yokota

KDDI R&D Laboratories, Inc.
e-mail:yokota@kddilabs.jp


> Once again, thanks for your comments!
>
> Carlos
>
>> Regards,
>> -- 
>> Hidetoshi Yokota
>>
>> KDDI R&D Laboratories, Inc.
>> e-mail:yokota@kddilabs.jp
>>
>>
>> (2014/06/14 2:16), Carlos Jesús Bernardos Cano wrote:
>>
>>> Hi,
>>>
>>> As agreed in London, I've updated the flow mobility draft to include
>>> also the FMI/FMA signaling option (in addition to the use of Update
>>> Notifications). The draft also includes a mechanism to allow selecting
>>> which one of the two signaling mechanisms to use.
>>>
>>> In my personal opinion, it'd be much cleaner and simpler to just specify
>>> one signaling mechanism, but this is up to the WG to decide.
>>>
>>> Comments, reviews and discussion on this new revision would be welcome.
>>> Hopefully we could get at least a new revision before Toronto.
>>>
>>> Thanks,
>>>
>>> Carlos
>>>
>>>
>>> _______________________________________________
>>> netext mailing list
>>> netext@ietf.org
>>> https://www.ietf.org/mailman/listinfo/netext
>> _______________________________________________
>> netext mailing list
>> netext@ietf.org
>> https://www.ietf.org/mailman/listinfo/netext
>
>
>
>