Capwap Mailing List: Re: Use of SESSION ID

[Scott G. Kelly (s.kelly]

-----Original Message-----
>From: "Bob O'Hara (boohara)" <boohara [at] cisco.com>
>Sent: Jun 2, 2006 12:02 PM
>To: capwap [at] frascone.com
>Subject: Re: [Capwap] Use of SESSION ID
>
>Abhijit,
>
>The use of the CAPWAP header to distinguish between control and data
>suffers from all the same problems that using a custom shim for that
>purpose, i.e., there is not a router or switch in the world that
>understands either one.
>

Ummm... that's definitely not right. The *airespace* switch has no problem 
understanding this, nor do other vendors *wlan* switches, if they want to 
update their firmware and/or microcode accordingly. This talk about "custom 
shims" is misdirection. What's custom here is what you guys are proposing.

Backward compatibility with a particluar vendor's legacy network gear in terms 
of identifying capwap internals is not a stated goal of this working group, nor 
should it be. It's not in the objectives draft, the architectural taxonomy, or 
the working group charter. And it's not in the interest of the broader 
community - vendors *or* customers.

--Scott