The question isn't whether one is cynical, but what one is cynical about and why. The expression "The nice thing about standards is that there are so many of them to choose from" was a pretty cynical statement of the benefits of having them.
The only standards that work well are so brutally simple that I sometimes wonder if some of these standards aren't as much curse as blessing. RADIUS? And the follow-on replacements often just perpetuate the problems. It's enough to make one cynical. People think technology changes happen quickly. If only. http://blog.ioshints.info/2009/10/what-went-wrong-tcp-lives-in-dial-up.html http://blog.ioshints.info/2010/07/tcpip-is-like-mainframe-you-cant-change.html http://blog.ioshints.info/2009/08/what-went-wrong-tcpip-lacks-session.html On Wed, Jan 30, 2013 at 8:43 AM, Lee H Badman <[email protected]> wrote: > I’m cynical.**** > > ** ** > > SIP, LWAPP, and CAPWAP at different times were all supposed to bring > interoperability, depending on who you talked with. They’ll find a way to > hose up open flow, with per vendor special sauce.**** > > ** ** > > Grrrr.**** > > ** ** > > A Curmudgeon in Syracuse**** > > ** ** > > ** ** > > *From:* The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto: > [email protected]] *On Behalf Of *Daniel Eklund > *Sent:* Wednesday, January 30, 2013 10:46 AM > *To:* [email protected] > *Subject:* Re: [WIRELESS-LAN] New Cisco Wireless Gear - 5760WLC & Cat3850* > *** > > ** ** > > Yes, this is pretty much what I'm thinking Philippe. All devices are > getting smarter as time goes on, but APs have gotten dumber (in some ways). > Perhaps Cisco will do something good with the acquisition of Meraki in > this regard. > **** > > ** ** > > --**** > > Daniel Eklund**** > > Network Planning Manager**** > > ITS Communications Systems and Data Centers**** > > University of Michigan**** > > 734.763.6389**** > > ** ** > > On Wed, Jan 30, 2013 at 8:04 AM, phanset <[email protected]> wrote:**** > > Just brainstorming here...**** > > ** ** > > CAPWAP tried to accomplish some standardization for Controller/AP > communication, but I haven't seen **** > > many CAPWAP compatible devices!**** > > http://en.wikipedia.org/wiki/CAPWAP**** > > ** ** > > This said, if you follow what's happening with OpenFlow ( > http://en.wikipedia.org/wiki/OpenFlow) on switches,**** > > and since switches and wireless equipment seem to progressively integrate, > we could make a leap and think**** > > that eventually there will be a common set of features that will be > standardized for wireless as well.**** > > ** ** > > OpenFlow accomplishes on switches what we have been doing with wireless > for a few years:**** > > Separation of control plane and data plane!**** > > ** ** > > This reminds me a little bit of OBD-II with cars. Part of the settings are > public and standard, part of it is private!**** > > ** ** > > Philippe Hanset**** > > www.eduroamus.org**** > > ** ** > > ** ** > > ** ** > > ** ** > > On Jan 30, 2013, at 7:41 AM, "Osborne, Bruce W" <[email protected]>**** > > wrote:**** > > > > **** > > Daniel,**** > > **** > > There are too many custom features and proprietary closed protocols to > permit AP to controller interoperability.**** > > **** > > For multi-vendor wireless monitoring & management, the Airwave AWMS (AMP) > product has excelled for many years. Even though the product is now owned > by Aruba Networks, Airwave has retained its multi-vendor features.**** > > **** > > Bruce Osborne**** > > Liberty University**** > > **** > > *From:* Daniel Eklund [mailto:[email protected]] > *Sent:* Tuesday, January 29, 2013 3:55 PM > *Subject:* Re: New Cisco Wireless Gear - 5760WLC & Cat3850**** > > **** > > As I've said recently, I really wish that there was a standard that all > APs would use and all controllers would use so that they could all talk > together. I know this is probably unlikely to happen, but we have > interoperable wired networks and I just wish the same for the wireless > side. Maybe a universal controller is more realistic, something that > understands how to talk to all types of APs. > **** > > **** > > --**** > > Daniel Eklund**** > > Network Planning Manager**** > > ITS Communications Systems and Data Centers**** > > University of Michigan**** > > 734.763.6389**** > > **** > > On Tue, Jan 29, 2013 at 1:34 PM, Peter P Morrissey <[email protected]> > wrote:**** > > My view regarding the 3850 is that anything that locks you into a vendor, > and makes it more difficult to switch to a competitor is a bad thing for > the consumer, and should be considered with your eyes wide open to the > long term consequences. In my mind, one would have to make an extremely > compelling business case to counter that tradeoff. Keep in mind that the > Vendor’s job is to make “switching costs” as high as possible for the > consumer.**** > > It is bad enough that we still have to purchase AP’s and controller’s from > the same vendor.**** > > **** > > The 5700 looks like a great idea for those of us with large wireless > networks.**** > > **** > > Pete Morrissey**** > > **** > > **** > > **** > > *From:* The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto: > [email protected]] *On Behalf Of *Luke Jenkins > *Sent:* Tuesday, January 29, 2013 1:18 PM > *To:* [email protected] > *Subject:* [WIRELESS-LAN] New Cisco Wireless Gear - 5760WLC & Cat3850**** > > **** > > At Cisco Live London today, Cisco announced two new WLCs:**** > > **** > > 5760 WLC - http://www.cisco.com/en/US/products/ps12598/index.html**** > > **** > > and the Cat3850 Switch - > http://www.cisco.com/en/US/products/ps12686/index.html**** > > **** > > IOS XE for both of these (not AireOS) and the ability to do termination of > CAPWAP on the switch with optional mobility tunnels back to a controller. > The datasheet for the Cat3850 has some info on this new option. Could be > situationally useful, but I'm not quite sold on the advantages vs. the > current model for higher ed where many of us are using big central pools of > real IPs and no NAT for our wireless users. Thoughts?**** > > **** > > -Luke > **** > > **** > > --**** > > =-=-=-=-=-=-=-=-=-=-=-=**** > > Luke Jenkins > Network Engineer > Weber State University**** > > ********** Participation and subscription information for this EDUCAUSE > Constituent Group discussion list can be found at > http://www.educause.edu/groups/.**** > > ********** Participation and subscription information for this EDUCAUSE > Constituent Group discussion list can be found at > http://www.educause.edu/groups/.**** > > > ********** Participation and subscription information for this EDUCAUSE > Constituent Group discussion list can be found at > http://www.educause.edu/groups/.**** > > ********** Participation and subscription information for this EDUCAUSE > Constituent Group discussion list can be found at > http://www.educause.edu/groups/. **** > > ** ** > > ** ** > > ********** Participation and subscription information for this EDUCAUSE > Constituent Group discussion list can be found at > http://www.educause.edu/groups/. **** > > > ********** Participation and subscription information for this EDUCAUSE > Constituent Group discussion list can be found at > http://www.educause.edu/groups/. ** ** > ********** Participation and subscription information for this EDUCAUSE > Constituent Group discussion list can be found at > http://www.educause.edu/groups/. > > ********** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/groups/.
