[netext] draft-ietf-netext-pmipv6-flowmob-04

Behcet Sarikaya <sarikaya2012@gmail.com> Fri, 24 August 2012 21:13 UTC

Return-Path: <sarikaya2012@gmail.com>
X-Original-To: netext@ietfa.amsl.com
Delivered-To: netext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 83B2821F8540 for <netext@ietfa.amsl.com>; Fri, 24 Aug 2012 14:13:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.605
X-Spam-Level:
X-Spam-Status: No, score=-3.605 tagged_above=-999 required=5 tests=[AWL=-0.006, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cQU17m6NkoV6 for <netext@ietfa.amsl.com>; Fri, 24 Aug 2012 14:13:04 -0700 (PDT)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id F34D921F8533 for <netext@ietf.org>; Fri, 24 Aug 2012 14:13:03 -0700 (PDT)
Received: by iabz21 with SMTP id z21so4641406iab.31 for <netext@ietf.org>; Fri, 24 Aug 2012 14:13:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:date:message-id:subject:from:to:content-type; bh=HTrXP4dYoDq/FQtsREeY4R2goWzpK3Fy35h2n1y8g7Y=; b=ZijCkBdTVW6PFbo40m6sIMlt2wm9e6OX9ZdGeQizRQl2GkVcw8cudQNg0wBYBv399O +q5k4rvpzGgDyulZcXbz4KWrGGzAc/veehYv8gKoEnZRtHAMe17zev0wRS/YM0qkzHjF DDqEJ2j2ik6n/ys95RbMlOMQXirZHNrzsJKCmV6z49XdlU6oFQQRzkR/+DOnxTDHfFXQ UsuKsDmi1CV0t+d5iS3u3uT9F8+jUW8fivRmji6Be9GX/7EH6EkWL2hjS+iuErZVNO6J nF2EI3K4BeRGkuIHu4M91O5Q0WH0eIRJNqnckaXWxkska8MKFswYnLK7eTD9Fj/Eh8sX DLrQ==
MIME-Version: 1.0
Received: by 10.50.17.133 with SMTP id o5mr3613542igd.41.1345842783453; Fri, 24 Aug 2012 14:13:03 -0700 (PDT)
Received: by 10.231.55.70 with HTTP; Fri, 24 Aug 2012 14:13:03 -0700 (PDT)
Date: Fri, 24 Aug 2012 16:13:03 -0500
Message-ID: <CAC8QAcegrZifKxbQ=wn4hEZYXutGLPg6Mtmqxd6=edioiT53Qg@mail.gmail.com>
From: Behcet Sarikaya <sarikaya2012@gmail.com>
To: netext@ietf.org
Content-Type: text/plain; charset="ISO-8859-1"
Subject: [netext] draft-ietf-netext-pmipv6-flowmob-04
X-BeenThere: netext@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: sarikaya@ieee.org
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: Fri, 24 Aug 2012 21:13:04 -0000

Hi Carlos,

I have questions on Section 3.2.1. on MN sharing a common set of
prefixes on all MAGs.

I don't understand why this is related to flow mobility but not prefix
allocation policy.
In Fig. 2, you consider flow Y to pref1::mn1 on if2

and then you move flow Y to if1. I am confused about the figure. How
come pref1::mn1 and pref1::mn1 stays the same? What is mn1? Is it the
iid?
Do you assume that both if1 and if2 have the same iid? How could this
be possible? Secondly you did not mention this assumption.

I think that if2 should be referred to as mn2 then the situation will
be clear, i.e. moving flows between two different interfaces with
different addresses, so this case is not any different than the cases
you have in Sections 3.2.2 and 3.2.3.

You  explain in this section that some flow mobility update action (?)
happens in both LMA and MN and the flow is magically moved. Even if we
assume what you have is correct this case does not deserve any mention
in the draft, i.e. there is no observable action to specify.

I have more coming up later.

Regards,

Behcet