Capwap Mailing List: Re: CAPWAP IESG Review Comment T20

[Pat Calhoun (pacalhou) (pcalhoun]

OK, well I'm getting conflicting requests from the AD and the chair, so
I need the two of you to agree on a path forward.

PatC 

-----Original Message-----
From: Margaret Wasserman [mailto:margaret [at] thingmagic.com] 
Sent: Tuesday, June 17, 2008 8:54 AM
To: Pat Calhoun (pacalhou)
Cc: capwap [at] frascone.com
Subject: Re: [Capwap] CAPWAP IESG Review Comment T20


Again, I do not see any value in renumbering fields at this point.   
We can always use 0 later if we run out...

Margaret

On Jun 16, 2008, at 11:35 AM, Pat Calhoun (pacalhou) wrote:

> All,
>
> Here is the IESG Review Comment:
>
>    T20 - Section 4.6.16, 4.6.17, 4.6.33, 4.6.36, 4.6.42, 4.6.43 - why 
> do the encoded
>    values start from 1 and not from 0?
>
> There is actually no reason why the values did not start at zero. I 
> will make the changes to renumber the values to start at zero (0). The

> only one I disagree with is 4.6.43, because this is a bit field, but I

> noticed that the text did not explicitely call for a bit field, so I 
> also made the necessary change.
>
> <text>
> 4.6.16.  Data Transfer Data
> [...]
>    Data Type:   An 8-bit value the type of information being sent.   
> The
>       following values are supported:
>
>       0 -  WTP Crash Data
>
>       1 -  WTP Memory Dump
>
> 4.6.17.  Data Transfer Mode
> [...]
>    Data Type:   An 8-bit value the type of information being  
> requested.
>       The following values are supported:
>
>       0 -  WTP Crash Data
>
>       1 -  WTP Memory Dump
>
> 4.6.33.  Radio Administrative State
> [...]
>    Admin State:   An 8-bit value representing the administrative state
>       of the radio.  The default value for the Admin State field is
>       listed in Section 4.8.1.  The following values are supported:
>
>       0 -  Enabled
>
>       1 -  Disabled
>
> 4.6.36.  Returned Message Element
> [...]
>    Reason:   The reason why the configuration in the offending message
>       element could not be applied by the WTP.
>
>       0 -  Unknown Message Element
>
>       1 -  Unsupported Message Element
>
>       2 -  Unknown Message Element Value
>
>       3 -  Unsupported Message Element Value
>
> 4.6.42.  WTP Fallback
> [...]
>
>    Mode:   The 8-bit value indicates the status of automatic CAPWAP
>       fallback on the WTP.  When enabled, if the WTP detects that its
>       primary AC is available, and that the WTP is not connected to 
> the
>       primary AC, the WTP SHOULD automatically disconnect from its
>       current AC and reconnect to its primary AC.  If disabled, the 
> WTP
>       will only reconnect to its primary AC through manual 
> intervention
>       (e.g., through the Reset Request message).  The default value 
> for
>       this field is specified in Section 4.8.10.  The following values
>       are supported:
>
>       0 -  Enabled
>
>       1 -  Disabled
>
>    Frame Tunnel Mode:   The Frame Tunnel mode specifies the tunneling
>       modes for station data that are supported by the WTP.  The 
> following
>       values are supported for this bit field:
>
> <text>
>
> PatC
> _________________________________________________________________
> 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