Lwapp Mailing List: RE: Another Way to Think about CAPWAP

[Pat R. Calhoun (pcalhoun]

Title: RE: [Lwapp] Another Way to Think about CAPWAP

There are mainly three different types of data that need to go between AP and AC.
Discovery related messages,  configuration/signaling information and actual
data packets.  Data packet could be voice data and requires QoS. TCP is not
a good transport to transfer this information. For discovery,
multicasting is required and TCP is not suitable. For control and signaling data,
either TCP or UDP with application reliability can be adapted.

<PRC> For the most part you are correct, but it also depends on the aggressiveness
required for control messages. For instance, if TCP's backoff algorithm could harm
the 802.11 service, then it may not be the right transport.

PatC