| Re: CAPWAP IESG Issue T5 | <– Date –> <– Thread –> |
|
From: Pat Calhoun (pacalhou) (pcalhoun |
|
| Date: Wed, 18 Jun 2008 22:20:24 -0700 (PDT) | |
Ok, that sounds good. I have made the necessary changes throughout the
spec.
<text>
4.6.1. AC Descriptor
[...]
AC Information Type: Vendor specific encoding of AC information.
The following enumerated values are supported. Both the
Hardware and Software Version sub-elements MUST be included in
the AC Descriptor message element.
4.6.15. CAPWAP Transport Protocol
[...]
Transport: The transport to use for the CAPWAP data channel. The
following enumerated values are supported:
4.6.16. Data Transfer Data
[...]
Data Type: An 8-bit value the type of information being sent. The
following enumerated values are supported:
4.6.17. Data Transfer Mode
[...]
Data Type: An 8-bit value the type of information being requested.
The following enumerated values are supported:
4.6.23. Discovery Type
[...]
Discovery Type: An 8-bit value indicating how the WTP discovered
the AC. The following enumerated values are supported:
4.6.27. Image Data
[...]
Opcode: An 8-bit value representing the transfer opcode. The
following enumerated values are supported:
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 enumerated values are
supported:
4.6.34. Radio Operational State
[...]
Cause: When a radio is inoperable, the cause field contains the
reason the radio is out of service. The following enumerated
values are supported:
4.6.35. Result Code
[...]
Result Code: The following enumerated values are defined:
4.6.36. Returned Message Element
[...]
Reason: The reason why the configuration in the offending message
element could not be applied by the WTP. The following enumerated
values are supported:
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.11. The following
enumerated values are supported:
4.6.46. WTP MAC Type
[...]
MAC Type: The MAC mode of operation supported by the WTP. The
following enumerated values are supported:
4.6.49. WTP Radio Statistics
[...]
Last Failure Type: The last WTP failure. The following enumerated
values are supported:
4.6.50. WTP Reboot Statistics
[...]
Last Failure Type: The failure type of the most recent WTP failure.
The following enumerated values are supported:
</text>
PatC
</text>
-----Original Message-----
From: David B. Nelson [mailto:dnelson [at] elbrysnetworks.com]
Sent: Monday, June 16, 2008 9:35 AM
To: Pat Calhoun (pacalhou); capwap [at] frascone.com
Subject: Re: [Capwap] CAPWAP IESG Issue T5
> No, this is not a bitmask. I'm not actually sure how to explicitely
> state it isn't a bitmask, because in my mind any field is not a
> bitmask unless it is explicitely stated, so I will use the term
numerical.
Or maybe the term "enumerated value"?
_________________________________________________________________
To unsubscribe or modify your subscription options, please visit:
http://lists.frascone.com/mailman/listinfo/capwap
Archives: http://lists.frascone.com/pipermail/capwap
-
CAPWAP IESG Issue T5 Pat Calhoun (pacalhou), June 16 2008
-
Re: CAPWAP IESG Issue T5 David B. Nelson, June 16 2008
- Re: CAPWAP IESG Issue T5 Pat Calhoun (pacalhou), June 18 2008
- Re: CAPWAP IESG Issue T5 Romascanu, Dan (Dan), June 19 2008
- Re: CAPWAP IESG Issue T5 Pat Calhoun (pacalhou), June 19 2008
-
Re: CAPWAP IESG Issue T5 David B. Nelson, June 16 2008
Results generated by Tiger Technologies using MHonArc.