Re: [netlmm] #55: Define desired scalability more precisely
"James Kempf" <kempf@docomolabs-usa.com> Tue, 30 May 2006 11:06 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fl23S-00017s-Ck; Tue, 30 May 2006 07:06:30 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fl23R-00017n-0d for netlmm@ietf.org; Tue, 30 May 2006 07:06:29 -0400
Received: from key1.docomolabs-usa.com ([216.98.102.225] helo=fridge.docomolabs-usa.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fl23P-0006Qh-JU for netlmm@ietf.org; Tue, 30 May 2006 07:06:28 -0400
Message-ID: <03b701c683d9$1b285dd0$5f6015ac@dcml.docomolabsusa.com>
From: James Kempf <kempf@docomolabs-usa.com>
To: "LAI, SHOU WEN -HCHBJ" <swlai@hitachi.cn>
References: <834B54D356AA8F46B9B233DD88BEAA38C8A1A0@hcbjdc2>
Subject: Re: [netlmm] #55: Define desired scalability more precisely
Date: Tue, 30 May 2006 04:06:29 -0700
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"; charset="iso-8859-1"; reply-type="original"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 3.1 (+++)
X-Scan-Signature: 25620135586de10c627e3628c432b04a
Cc: netlmm@ietf.org
X-BeenThere: netlmm@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: NETLMM working group discussion list <netlmm.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/netlmm>, <mailto:netlmm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/netlmm>
List-Post: <mailto:netlmm@ietf.org>
List-Help: <mailto:netlmm-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/netlmm>, <mailto:netlmm-request@ietf.org?subject=subscribe>
Errors-To: netlmm-bounces@ietf.org
Please see paragraph 7 of the charter: "The scope of the work is initially limited to IPv6 both in the backbone and on the edges..." jak ----- Original Message ----- From: "LAI, SHOU WEN -HCHBJ" <swlai@hitachi.cn> To: "James Kempf" <kempf@docomolabs-usa.com> Cc: <netlmm@ietf.org>; "Pekka Savola" <pekkas@netcore.fi> Sent: Tuesday, May 30, 2006 2:20 AM Subject: RE: [netlmm] #55: Define desired scalability more precisely The design goal NETLMM protocol mentioned: Support for any IP version host. (65th IETF minutes) That means MN can be IPv4 host or IPv6 host. If the host is IPv4, we can use DHCP to assign address. In that case, there is scalability problem, I think. -----Original Message----- From: James Kempf [mailto:kempf@docomolabs-usa.com] Sent: Tuesday, May 30, 2006 5:07 PM To: LAI, SHOU WEN -HCHBJ Cc: netlmm@ietf.org; Pekka Savola Subject: Re: [netlmm] #55: Define desired scalability more precisely >NETLMM is currently only being defined for IPv6. jak ----- Original Message ----- From: "LAI, SHOU WEN -HCHBJ" <swlai@hitachi.cn> To: "James Kempf" <kempf@docomolabs-usa.com> Cc: <netlmm@ietf.org>; "Pekka Savola" <pekkas@netcore.fi> Sent: Tuesday, May 30, 2006 1:49 AM Subject: RE: [netlmm] #55: Define desired scalability more precisely >Hi, I have a question when the protocal is scaled large, O(100K) IPv4 nodes >simultaneously for example. >Do we use one DHCP server to distribute addresses for those nodes, or use >multiple DHCP server? >If multiple DHCP servers are used, then the address gained from previous >DHCP server will change after the node attached to a AR assoicated with >another DHCP server. >If only one DHCP server, maybe there are not enough addresses for all >nodes. >Thanks, Disclaimer: The contents of this e-mail, and its attachments, if any, are confidential and may be protected by law against any unauthorized use. If you have received this e-mail by mistake or have reason to believe that you are not the intended recipient, please notify the sender by reply e-mail as soon as possible and delete it from your computer system immediately thereafter. If you are not the intended recipient, you must not copy this e-mail or attachment or disclose the contents to any other person. While we have made every effort to keep our network virus free, we take no responsibility for any computer virus which might be transferred by way of this e-mail. _______________________________________________ netlmm mailing list netlmm@ietf.org https://www1.ietf.org/mailman/listinfo/netlmm
- [netlmm] #55: Define desired scalability more pre… netlmm-tracker
- Re: [netlmm] #55: Define desired scalability more… netlmm-tracker
- Re: [netlmm] #55: Define desired scalability more… netlmm-tracker
- Re: [netlmm] #55: Define desired scalability more… Pekka Savola
- RE: [netlmm] #55: Define desired scalability more… Narayanan, Vidya
- RE: [netlmm] #55: Define desired scalability more… Pekka Savola
- Re: [netlmm] #55: Define desired scalability more… James Kempf
- Re: [netlmm] #55: Define desired scalability more… Pekka Savola
- Re: [netlmm] #55: Define desired scalability more… James Kempf
- RE: [netlmm] #55: Define desired scalability more… LAI, SHOU WEN -HCHBJ
- Re: [netlmm] #55: Define desired scalability more… James Kempf
- RE: [netlmm] #55: Define desired scalability more… LAI, SHOU WEN -HCHBJ
- Re: [netlmm] #55: Define desired scalability more… James Kempf
- Re: [netlmm] #55: Define desired scalability more… Vijay Devarapalli
- RE: [netlmm] #55: Define desired scalability more… Narayanan, Vidya
- Re: [netlmm] #55: Define desired scalability more… James Kempf
- Re: [netlmm] #55: Define desired scalability more… Andy Huang
- RE: [netlmm] #55: Define desired scalability more… Pekka Savola
- RE: [netlmm] #55: Define desired scalability more… Narayanan, Vidya
- RE: [netlmm] #55: Define desired scalability more… Pekka Savola
- RE: [netlmm] #55: Define desired scalability more… Kent Leung (kleung)
- Re: [netlmm] #55: Define desired scalability more… netlmm