RE: [netlmm] #55: Define desired scalability more precisely
"Narayanan, Vidya" <vidyan@qualcomm.com> Sat, 27 May 2006 02:12 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FjoIB-00077K-2L; Fri, 26 May 2006 22:12:39 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FjoI9-00073x-Hf for netlmm@ietf.org; Fri, 26 May 2006 22:12:37 -0400
Received: from ithilien.qualcomm.com ([129.46.51.59]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FjoI8-0007ks-3w for netlmm@ietf.org; Fri, 26 May 2006 22:12:37 -0400
Received: from magus.qualcomm.com (magus.qualcomm.com [129.46.61.148]) by ithilien.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id k4R2CUXN020183 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Fri, 26 May 2006 19:12:31 -0700
Received: from NAEXBR03.na.qualcomm.com (naexbr03.qualcomm.com [129.46.134.172]) by magus.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id k4R2CT9d010816; Fri, 26 May 2006 19:12:29 -0700 (PDT)
Received: from NAEX06.na.qualcomm.com ([129.46.135.160]) by NAEXBR03.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 26 May 2006 19:12:29 -0700
x-mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [netlmm] #55: Define desired scalability more precisely
Date: Fri, 26 May 2006 19:12:27 -0700
Message-ID: <2EBB8025B6D1BA41B567DB32C1D8DB8490B689@NAEX06.na.qualcomm.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [netlmm] #55: Define desired scalability more precisely
Thread-Index: AcZ/9td9Y0i3ZbEmQEyqJrN4LgPl8QBOudcw
From: "Narayanan, Vidya" <vidyan@qualcomm.com>
To: Pekka Savola <pekkas@netcore.fi>, netlmm@ietf.org
X-OriginalArrivalTime: 27 May 2006 02:12:29.0324 (UTC) FILETIME=[016354C0:01C68133]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0a7aa2e6e558383d84476dc338324fab
Cc:
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
Hi Pekka, <snip> > > I'd rather state explicitly that the solution must be able to > scale to, say, O(10K) or O(50K) simultaneous users. I can't understand the reasoning behind explicitly stating any number here. Any numbers for scalability are system level requirements and not protocol level requirements. The only goal of a protocol should be that it be scalable - in the sense that in a real deployment, it must be possible to *scale up/out* the protocol. For e.g., if the NETLMM protocol had limitations in the number of LMAs that can be present for the protocol to function properly, that would be a bad protocol design. But, as long as more users can be supported by increasing the number of LMAs and/or ARs, the protocol itself is scalable. System level scalability requirements can then say x number of simultaneous users (to figure out how many actual boxes are needed) or x number of users per LMA, etc., but this is outside the scope of the protocol itself. > If the > implementations can work on the scalability to make that much > higher -- that's great, but not something we in the IETF > should be concerned about, because networks can just deploy > more boxes without significant disadvantage to the user if > the limit is reached. > As I said above, I don't think the numbers mean anything to a protocol and should not be part of any protocol requirements. > It seems to me that as soon as we discard Mobile IP as a > basis for localized mobility management, there seems to be > push to make the LMM domain bigger and bigger so that you > could make do without any non-LMM mobility management > solution. As shown in the list a)-f), building one LMA/MAP > big enough to cover the whole world (or break users' > session if (s)he moves e.g. from one city to another) just > doesn't seem feasible, so I can't figure out why we're trying. > This itself is a valid concern and I do believe that an applicability statement or the like in the document must be added to clarify that there are limitations in making the LMM domain bigger and bigger. Regards, Vidya > -- > Pekka Savola "You each name yourselves king, yet the > Netcore Oy kingdom bleeds." > Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings > > _______________________________________________ > netlmm mailing list > netlmm@ietf.org > https://www1.ietf.org/mailman/listinfo/netlmm > _______________________________________________ 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