Subject: Re: [Capwap] duplicate message element values

From: "Dorothy Stanley" <[email-masked]>
Date: Thu, 27 Apr 2006 06:53:16 -0700

Proposed resolution:

Re-number all the message element values as follows:

CAPWAP message elements - begin with #1
IEEE 802.11 message elements - beginning with #1024

This eliminates duplicates, provides values for several existing TBDs, and
enables
straightforward Identification of the CAPWAP/IEEE specific nature of the
elements.

Currently there are 40 CAPWAP message elements,   and
24 IEEE specific message elements defined.

Comments?

Thanks,

Dorothy

On 3/31/06, Michael Montemurro <[email-masked]> wrote:
>
> I've created item 91 to track this issue.
>
> Cheers,
>
>         Mike
>
> > -----Original Message-----
> > From: Scott G. Kelly [mailto:[email-masked]]
> > Sent: March 30, 2006 6:07 PM
> > To: capwap; Pat Calhoun
> > Subject: [Capwap] duplicate message element values
> >
> > Hi Pat,
> >
> > The following capwap message elements are currently defined
> > with duplicate values:
> >
> > - AC Address and Result Code (2)
> >
> > - 802.11 supported rates and 802.11 rate set (16)
> >
> > - Duplicate IPv4 address and Duplicate IPv6 address (77)
> >
> > Are these typos, or do new unique values need to be assigned?
> >
> > Scott
> >
> > _________________________________________________________________
> > To unsubscribe or modify your subscription options, please visit:
> > http://lists.frascone.com/mailman/listinfo/capwap
> >
> > Archives: http://lists.frascone.com/pipermail/capwap
> >
> _________________________________________________________________
> To unsubscribe or modify your subscription options, please visit:
> http://lists.frascone.com/mailman/listinfo/capwap
>
> Archives: http://lists.frascone.com/pipermail/capwap
>
_________________________________________________________________
To unsubscribe or modify your subscription options, please visit:
http://lists.frascone.com/mailman/listinfo/capwap

Archives: http://lists.frascone.com/pipermail/capwap