Re: [netlmm] Consensus call: RFC5107 based DHCP message interceptat MAG

Ryuji Wakikawa <ryuji.wakikawa@gmail.com> Tue, 14 April 2009 05:33 UTC

Return-Path: <ryuji.wakikawa@gmail.com>
X-Original-To: netlmm@core3.amsl.com
Delivered-To: netlmm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BB94C3A6959 for <netlmm@core3.amsl.com>; Mon, 13 Apr 2009 22:33:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RHT175egRMrd for <netlmm@core3.amsl.com>; Mon, 13 Apr 2009 22:33:15 -0700 (PDT)
Received: from mail-qy0-f134.google.com (mail-qy0-f134.google.com [209.85.221.134]) by core3.amsl.com (Postfix) with ESMTP id B8C583A67F4 for <netlmm@ietf.org>; Mon, 13 Apr 2009 22:33:14 -0700 (PDT)
Received: by qyk40 with SMTP id 40so840439qyk.29 for <netlmm@ietf.org>; Mon, 13 Apr 2009 22:34:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:to:in-reply-to:subject :references:message-id:content-type:content-transfer-encoding :mime-version:date:cc:x-mailer; bh=5RSyoQcYjuL20ns7TOx7DiqR2Kd9GQymQao1GY3x2iI=; b=udBCqRTltJ6/g7kscZ2B9lR9/XS8jDQTHcLQSkI6ZHPfimoNWd5kEuJUjKsXDfisYc iN1OTmlM+hKCVibr3nkN2NqUKn8ddaX6r9nujw4jTm2StNBUMBg+BQiTv47Jp0q1cjgw QUn9Id3vSzgVxh2uRNnqQs102qA110iBLRNzI=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:in-reply-to:subject:references:message-id:content-type :content-transfer-encoding:mime-version:date:cc:x-mailer; b=H5Z+h6ylhYRPo6DeFtpp+GNu+ew5sA5Va7viIn7tL91HbWQ9l28iUhD6FTrNCk3SPY jHy70Wm/IMDG3iwbAqIEZ7bkhSh+baO/ix42lOkXHwL76SlfNEUEbSiCP0RfgU4CtAqX MCDth36j7Ds6tI7sDW4Lrp/Cja+qiAEl/MEeM=
Received: by 10.224.19.210 with SMTP id c18mr6969373qab.233.1239687265805; Mon, 13 Apr 2009 22:34:25 -0700 (PDT)
Received: from ?172.17.191.127? ([208.251.140.35]) by mx.google.com with ESMTPS id 5sm10072480qwg.4.2009.04.13.22.34.24 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 13 Apr 2009 22:34:25 -0700 (PDT)
From: Ryuji Wakikawa <ryuji.wakikawa@gmail.com>
To: Hidetoshi Yokota <yokota@kddilabs.jp>
In-Reply-To: <49E3E08B.40202@kddilabs.jp>
References: <C608B346.62A1%vijay@wichorus.com> <49E3E08B.40202@kddilabs.jp>
Message-Id: <8923ADB7-D4DD-402F-BF3E-2B6ED845CAA5@gmail.com>
Content-Type: text/plain; charset="US-ASCII"; format="flowed"; delsp="yes"
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v930.3)
Date: Tue, 14 Apr 2009 01:34:23 -0400
X-Mailer: Apple Mail (2.930.3)
Cc: netlmm@ietf.org
Subject: Re: [netlmm] Consensus call: RFC5107 based DHCP message interceptat MAG
X-BeenThere: netlmm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: NETLMM working group discussion list <netlmm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/netlmm>, <mailto:netlmm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/netlmm>
List-Post: <mailto:netlmm@ietf.org>
List-Help: <mailto:netlmm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netlmm>, <mailto:netlmm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Apr 2009 05:33:15 -0000

Hi Yokota-san,

On 2009/04/13, at 21:02, Hidetoshi Yokota wrote:

> Hi Vijay,
>
> Vijay Devarapalli wrote:
>> Hello,
>>
>>
>> On 4/13/09 1:57 AM, "Hidetoshi Yokota" wrote:
>>
>>> Hi Rajeev and all,
>>>
>>> I have a bit of concern about the restriction that the DHCP server  
>>> has
>>> to be collocated with the LMA. Some deployment scenario may have
>>> multiple LMAs and one DHCP server in a PMIPv6 domain and there is a
>>> situation where the LMA for some mobile node gets changed to  
>>> another for
>>> failure recovery reason. If RFC5107 can allow this configuration and
>>> handle this situation well, then it's worth keeping it in the  
>>> document.
>>> A further clarification will be helpful as you pointed out, though.
>>
>> LMA relocation while preserving the IP address for the mobile node is
>> something that is not supported even in RFC 5213. So can you  
>> describe the
>> above scenario in more detail?
>
> Here, I'm thinking of a real PMIPv6 deployment not limited to RFC5213.
> 5213 is the base spec and we all know that we need further extensions
> including binding revocations, redirections, etc. The concern I raised
> here is that it would be a bit restrictive if the collocation of the  
> LMA
> and DHCP server is mandated.

I agree. if there is a case to deploy DHCP server solely in PMIP6  
domain,
we need to keep RFC5107 or MAG promiscuous listening. I prefer using  
5107.

>
>
>> If this is a failover case where another LMA takes over for a  
>> failed LMA,
>> and the state is synced between the two, this change should not  
>> even be
>> visible to the MAG or the MN. All the mobility sessions continue as  
>> is.
>
> If the state is synced between the two, yes. But in the collocated  
> case,
> a change of LMA means a change of DHCP server. DHCP and PMIP are
> basically separate things in protocol and operations although their

This is good point.  It's useful to have just normative reference to  
5107.

regards,
ryuji

>
> states should be in sync. Here, I raised a question that this
> collocation is a must or a choice.




>
>
> Regards,
> -- 
> Hidetoshi
>
>
>> Vijay
>>
>>
>>
>>
>
> _______________________________________________
> netlmm mailing list
> netlmm@ietf.org
> https://www.ietf.org/mailman/listinfo/netlmm