| RE: So many architectures, so little time... - take 2 | <– Date –> <– Thread –> |
|
From: Mani, Mahalingam (Mahalingam) (mmani |
|
| Date: Wed, 4 Aug 2004 19:10:46 -0400 (EDT) | |
This in itself justifies the need to be able to seek idiosyncracies and commonalities of "customer" pressure-points and later sit back to prioritize them. Of the two requirements the more thought about is the first (and more of the core challenge). However,... -----Original Message----- From: James Kempf [mailto:kempf [at] docomolabs-usa.com] Sent: Wednesday, August 04, 2004 3:29 PM To: Shehzad Merchant; capwap [at] frascone.com Cc: bwijnen [at] lucent.com; Mani, Mahalingam (Mahalingam); david.kessens [at] nokia.com; Dorothy.Gellert [at] nokia.com; Inderpreet Singh Subject: Re: [Capwap] So many architectures, so little time... - take 2 As a potential customer, let me put it concretely. I want to be able to buy my access points from Vendor X and my switch from Vendor Y and plug the two together and have them work without any configuration. Also, I'd like to be able to buy switches from Vendor Y and Vendor Z and be able to plug them [Mani, Mahalingam (Mahalingam)] [Mani, Mahalingam (Mahalingam)] the latter is a new, good and interesting requirement to consider; whether it goes into desirable or mandatory bucket remains to be seen. Also - whether it is a coexistence requirement or interoperability requirement is to be analyzed as well. -mani into my network at various places and have them interoperate. jak ----- Original Message ----- From: "Shehzad Merchant" <smerchant [at] extremenetworks.com> To: <capwap [at] frascone.com> Cc: <bwijnen [at] lucent.com>; <mmani [at] avaya.com>; <david.kessens [at] nokia.com>; <Dorothy.Gellert [at] nokia.com>; "Inderpreet Singh" <isingh [at] chantrynetworks.com> Sent: Wednesday, August 04, 2004 3:19 PM Subject: RE: [Capwap] So many architectures, so little time... - take 2 > I think the implementation variations even with the split MAC may cover a > broad spectrum. As such its important to clearly articulate what aspects of > interoperability we are targetting. Is it truly just control/management or > is it interoperability between disparate implementations of the split MAC, > i.e. mix and match operation of WTP and ACs of all variants within this > category. > > I suspect for the latter we may have to arrive at some consensus on what > particular implementations we are targeting interoperability for. If so, > ultimately this problem statement could become part of the charter. > > -Shehzad > [Mani, Mahalingam (Mahalingam)] [...]
- RE: So many architectures, so little time... - take 2, (continued)
- RE: So many architectures, so little time... - take 2 Pat R. Calhoun, August 4 2004
- RE: So many architectures, so little time... - take 2 Dorothy.Gellert, August 4 2004
-
RE: So many architectures, so little time... - take 2 Shehzad Merchant, August 4 2004
- Re: So many architectures, so little time... - take 2 James Kempf, August 4 2004
- RE: So many architectures, so little time... - take 2 Mani, Mahalingam (Mahalingam), August 4 2004
-
RE: So many architectures, so little time... - take 2 Randy Chou, August 4 2004
- Message not available
- RE: So many architectures, so little time... - take 2 Matt Holdrege, August 5 2004
- Re: So many architectures, so little time... - take 2 James Kempf, August 5 2004
- Message not available
Results generated by Tiger Technologies using MHonArc.