Re: [netlmm] Consensus call: Adopting draft-korhonen-netlmm-lma-discovery as a WG item
Sri Gundavelli <sgundave@cisco.com> Wed, 29 April 2009 23:03 UTC
Return-Path: <sgundave@cisco.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 39D993A67B6 for <netlmm@core3.amsl.com>; Wed, 29 Apr 2009 16:03:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.428
X-Spam-Level:
X-Spam-Status: No, score=-6.428 tagged_above=-999 required=5 tests=[AWL=0.171, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 8OMeYYXBDatm for <netlmm@core3.amsl.com>; Wed, 29 Apr 2009 16:03:09 -0700 (PDT)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70]) by core3.amsl.com (Postfix) with ESMTP id 535633A6A9E for <netlmm@ietf.org>; Wed, 29 Apr 2009 16:03:09 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.40,269,1238976000"; d="scan'208";a="178761361"
Received: from sj-dkim-3.cisco.com ([171.71.179.195]) by sj-iport-1.cisco.com with ESMTP; 29 Apr 2009 23:04:32 +0000
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238]) by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id n3TN4Vrc025556; Wed, 29 Apr 2009 16:04:31 -0700
Received: from irp-view13.cisco.com (irp-view13.cisco.com [171.70.120.60]) by sj-core-5.cisco.com (8.13.8/8.13.8) with ESMTP id n3TN4V4M022663; Wed, 29 Apr 2009 23:04:31 GMT
Date: Wed, 29 Apr 2009 16:04:31 -0700
From: Sri Gundavelli <sgundave@cisco.com>
To: Behcet Sarikaya <sarikaya@ieee.org>
In-Reply-To: <934656.70845.qm@web111410.mail.gq1.yahoo.com>
Message-ID: <Pine.GSO.4.63.0904291603020.16006@irp-view13.cisco.com>
References: <BE82361A0E26874DBC2ED1BA244866B93961F022@NALASEXMB08.na.qualcomm.com> <EA7603A6-E67B-40A7-97BD-BC9A9F90AED3@gmail.com> <934656.70845.qm@web111410.mail.gq1.yahoo.com>
MIME-Version: 1.0
Content-Type: MULTIPART/MIXED; BOUNDARY="-559023410-52182039-1241046271=:16006"
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=3138; t=1241046272; x=1241910272; c=relaxed/simple; s=sjdkim3002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=sgundave@cisco.com; z=From:=20Sri=20Gundavelli=20<sgundave@cisco.com> |Subject:=20Re=3A=20[netlmm]=20Consensus=20call=3A=20Adopti ng=20draft-korhonen-netlmm-lma-discovery=0A=20as=20a=20WG=20 item |Sender:=20; bh=1OwjqsUodfVBT5Ao4MOZXsQyCgJCF1XndvH2jViVx0A=; b=lcTNTP7FG7xHY0NNQCB0hL1vYqCk1Y61U/1svSAyWIVxO5GAWEhmU/tbVK Mb5jOSpS1RS3EuFTcISy6lX7z+C4Ode2Fq9TyOlI3R87OkpBHlUVYAFxXFcz jVP8qdSwt7;
Authentication-Results: sj-dkim-3; header.From=sgundave@cisco.com; dkim=pass ( sig from cisco.com/sjdkim3002 verified; );
Cc: "netlmm@ietf.org" <netlmm@ietf.org>
Subject: Re: [netlmm] Consensus call: Adopting draft-korhonen-netlmm-lma-discovery as a WG item
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: Wed, 29 Apr 2009 23:03:10 -0000
Not sure, if you guys cant merge and come out with a single doc. Since, the issue is well defined, the specific approach can be decided as part of this work. My 2c. Sri On Wed, 29 Apr 2009, Behcet Sarikaya wrote: > Hi Ryuji, > Please see my replies below. > > Regards, > > Behcet > > > > ________________________________ > > > > I also read draft-xia-netlmm-lma-discovery-00. > DHCP can be alternative approach to discovery LMA address. > However AAA or L2 solutions seems to be much straightforward and light-weight approach. > Are their any strong reasons to use DHCP for this specific function (LMA discovery)? > > [behcet] The charter Item 6 is the answer, I think. > > comments to Frank's document > - In IPv4 support doc, we also uses DHCP for IPv4 address assignment. > To design the DHCP parts, we tried not to introduces any PMIP specific states or data at the DHCP entity. > > [behcet] As Frank said we are assuming something similar to (DS)MIPv6. I don't think a lot of state is needed, in most cases a single record would be enough. > MAG access to DHCP is on the other hand is stateless which will probably make you happy. > > > DHCP-server just notify the IPv4 address to the DHCP client. The IPv4 address is always assigned by LMA. > On the other hand, this document assumes DHCP server manages all the PMIP states such as LMA and home network prefix. > We might need some interaction between PMIP and DHCP to keep protocol states consistency. > [behcet] No not really, please see above. If several LMAs are in the same domain then a few more. > > - This document assumes one DHCP server per PMIP domain, because DHCP relay has to be configured with the same DHCP server address. > Is this reasonable assumption in terms of scalability and optimized management , etc. ? > > [behcet] I agree with you on this. Please provide some text and help us improve the draft. > > > regards, > ryuji > > > On 2009/04/28, at 17:10, Narayanan, Vidya wrote: > >> Hi, >> This is a consensus call to determine adoption of draft-korhonen-netlmm-lma-discovery as a WG item. This relates to the LMA discovery work in our charter. >> >> Please respond on whether or not you support adoption of this draft as a WG item to the list by May 6th, 2009. Please note that this document would be a starting point for the work, if adopted and the current content in the draft is by no means final. >> >> Thanks, >> Vidya >> _______________________________________________ >> netlmm mailing list >> netlmm@ietf.org >> https://www.ietf.org/mailman/listinfo/netlmm > > _______________________________________________ > netlmm mailing list > netlmm@ietf.org > https://www.ietf.org/mailman/listinfo/netlmm > > > >
- [netlmm] Consensus call: Adopting draft-korhonen-… Narayanan, Vidya
- Re: [netlmm] Consensus call: Adopting draft-korho… Frank Xia
- Re: [netlmm] Consensus call: Adopting draft-korho… Vijay Devarapalli
- Re: [netlmm] Consensus call: Adopting draft-korho… Frank Xia
- Re: [netlmm] Consensus call: Adopting draft-korho… Sri Gundavelli
- Re: [netlmm] Consensus call: Adopting draft-korho… Frank Xia
- Re: [netlmm] Consensus call: Adopting draft-korho… Ryuji Wakikawa
- Re: [netlmm] Consensus call: Adopting draft-korho… Vijay Devarapalli
- Re: [netlmm] Consensus call: Adopting draft-korho… Sri Gundavelli
- Re: [netlmm] Consensus call: Adoptingdraft-korhon… Frank Xia
- Re: [netlmm] Consensus call: Adopting draft-korho… Sri Gundavelli
- Re: [netlmm] Consensus call: Adopting draft-korho… Vijay Devarapalli
- Re: [netlmm] Consensus call: Adopting draft-korho… Sri Gundavelli
- Re: [netlmm] Consensus call: Adopting draft-korho… Frank Xia
- Re: [netlmm] Consensus call: Adopting draft-korho… Sri Gundavelli
- Re: [netlmm] Consensus call: Adopting draft-korho… jouni
- Re: [netlmm] Consensus call: Adopting draft-korho… Behcet Sarikaya
- Re: [netlmm] Consensus call: Adopting draft-korho… Sri Gundavelli
- Re: [netlmm] Consensus call: Adopting draft-korho… Sri Gundavelli
- Re: [netlmm] Consensus call: Adopting draft-korho… jouni
- Re: [netlmm] Consensus call: Adopting draft-korho… jouni
- Re: [netlmm] Consensus call: Adopting draft-korho… Behcet Sarikaya
- Re: [netlmm] Consensus call: Adopting draft-korho… Soininen, Jonne (NSN - FI/Espoo)
- Re: [netlmm] Consensus call: Adopting draft-korho… Premec, Domagoj
- Re: [netlmm] Consensus call: Adopting draft-korho… Soininen, Jonne (NSN - FI/Espoo)
- Re: [netlmm] Consensus call: Adopting draft-korho… Basavaraj.Patil
- Re: [netlmm] Consensus call: Adoptingdraft-korhon… pierrick.seite
- Re: [netlmm] Consensus call: Adopting draft-korho… Christian Vogt
- Re: [netlmm] Consensus call: Adopting draft-korho… Vijay Devarapalli
- Re: [netlmm] Consensus call: Adopting draft-korho… Julien Laganier
- Re: [netlmm] Consensus call: Adopting draft-korho… Behcet Sarikaya
- Re: [netlmm] Consensus call: Adopting draft-korho… jouni korhonen
- Re: [netlmm] Consensus call: Adopting draft-korho… Christian Vogt
- Re: [netlmm] Consensus call: Adopting draft-korho… Christian Vogt
- Re: [netlmm] Consensus call: Adopting draft-korho… jouni korhonen
- Re: [netlmm] Consensus call: Adopting draft-korho… jouni korhonen
- Re: [netlmm] Consensus call: Adopting draft-korho… Julien Laganier
- Re: [netlmm] Consensus call: Adopting draft-korho… Julien Laganier
- Re: [netlmm] Consensus call: Adopting draft-korho… Julien Laganier
- Re: [netlmm] Consensus call: Adopting draft-korho… Christian Vogt
- Re: [netlmm] Consensus call: Adopting draft-korho… Christian Vogt
- Re: [netlmm] Consensus call: Adopting draft-korho… Behcet Sarikaya
- Re: [netlmm] Consensus call: Adopting draft-korho… Julien Laganier