Re: [netext] COMMENTS ON draft-ietf-netext-pmipv6-flowmob-04
Carlos Jesús Bernardos Cano <cjbc@it.uc3m.es> Tue, 11 September 2012 20:58 UTC
Return-Path: <cjbc@it.uc3m.es>
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 1F2A521F8669 for <netext@ietfa.amsl.com>; Tue, 11 Sep 2012 13:58:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.699
X-Spam-Level:
X-Spam-Status: No, score=-5.699 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_21=0.6, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
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 yNEx1wRYtquU for <netext@ietfa.amsl.com>; Tue, 11 Sep 2012 13:58:10 -0700 (PDT)
Received: from smtp02.uc3m.es (smtp02.uc3m.es [163.117.176.132]) by ietfa.amsl.com (Postfix) with ESMTP id 27B2921F865E for <netext@ietf.org>; Tue, 11 Sep 2012 13:58:09 -0700 (PDT)
X-uc3m-safe: yes
Received: from [10.64.28.194] (93-158-5-42.subs.ibrowse.com [93.158.5.42]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: cjbc@smtp02.uc3m.es) by smtp02.uc3m.es (Postfix) with ESMTPSA id 2A4EC86C2AB; Tue, 11 Sep 2012 22:58:06 +0200 (CEST)
Message-ID: <1347397084.17961.31.camel@acorde.it.uc3m.es>
From: Carlos Jesús Bernardos Cano <cjbc@it.uc3m.es>
To: sarikaya@ieee.org
Date: Tue, 11 Sep 2012 22:58:04 +0200
In-Reply-To: <CAC8QAcdHfpqqdkkKv0iDA8xU4gRJ2oYyvtUhLR4o7vwWxot-vw@mail.gmail.com>
References: <CAC8QAcdHfpqqdkkKv0iDA8xU4gRJ2oYyvtUhLR4o7vwWxot-vw@mail.gmail.com>
Organization: Universidad Carlos III de Madrid
Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-pHbejJQzfMHk4l+7kjUg"
X-Mailer: Evolution 3.4.3-1
Mime-Version: 1.0
X-TM-AS-Product-Ver: IMSS-7.1.0.1224-6.8.0.1017-19178.001
X-TM-AS-Result: No--14.814-7.0-31-1
X-imss-scan-details: No--14.814-7.0-31-1
Cc: netext@ietf.org
Subject: Re: [netext] COMMENTS ON draft-ietf-netext-pmipv6-flowmob-04
X-BeenThere: netext@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: cjbc@it.uc3m.es
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: Tue, 11 Sep 2012 20:58:11 -0000
Hi Behcet, I just came back from holidays. I'm catching up with e-mails and I'll go back to you early next week. Thanks for the understanding. Carlos On Tue, 2012-09-11 at 13:12 -0500, Behcet Sarikaya wrote: > I had posted this mail almost a month ago and have not seen any reply yet? > > On Fri, Aug 24, 2012 at 4:13 PM, Behcet Sarikaya <sarikaya2012@gmail.com> wrote: > > 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 > _______________________________________________ > netext mailing list > netext@ietf.org > https://www.ietf.org/mailman/listinfo/netext -- Carlos Jesús Bernardos Cano http://www.netcom.it.uc3m.es/ GPG FP: D29B 0A6A 639A A561 93CA 4D55 35DC BA4D D170 4F67
- [netext] COMMENTS ON draft-ietf-netext-pmipv6-flo… Behcet Sarikaya
- Re: [netext] COMMENTS ON draft-ietf-netext-pmipv6… Carlos Jesús Bernardos Cano