Capwap Mailing List: RE: So many architectures, so little time... - take 2

[Matt Holdrege (matt.holdrege]

Pricing should not be an issue in any IETF charter. Rather efficiency and 
performance are the major issues. It's up to manufacturers to set their 
prices.

-Matt

At 02:04 AM 8/5/2004, Randy Chou wrote:
> I think most consumers not only want the first requirement, but more
> specifically want to be able to purchase the most inexpensive AP from
> any vendor without sacrificing security.  If agreeable, I would suggest
> making that one of the goals of the charter.
>
> Regards,
>
> --
> Randy
>
> -----Original Message-----
> From: capwap-admin [at] frascone.com [mailto:capwap-admin [at] frascone.com] On
> Behalf Of Mani, Mahalingam (Mahalingam)
> Sent: Wednesday, August 04, 2004 4:24 PM
> To: James Kempf; Shehzad Merchant; capwap [at] frascone.com
> Cc: bwijnen [at] lucent.com; david.kessens [at] nokia.com;
> Dorothy.Gellert [at] nokia.com; Inderpreet Singh
> Subject: RE: [Capwap] So many architectures, so little time... - take 2
>
>
> 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)] [...]
>
>
> _______________________________________________
> Capwap mailing list
> Capwap [at] frascone.com http://mail.frascone.com/mailman/listinfo/capwap
> _______________________________________________
> Capwap mailing list
> Capwap [at] frascone.com
> http://mail.frascone.com/mailman/listinfo/capwap