Debian Codegraph @

rfc5412.html

raw
1 <pre>Independent Submission P. Calhoun
2 Request for Comments: 5412 R. Suri
3 Category: Historic N. Cam-Winget
4 ISSN: 2070-1721 Cisco Systems, Inc.
5 M. Williams
6 GWhiz Arts &amp; Sciences
7 S. Hares
8 B. O'Hara
9 S.Kelly
10 February 2010
11
12
13 <span class="h1">Lightweight Access Point Protocol</span>
14
15 Abstract
16
17 In recent years, there has been a shift in wireless LAN (WLAN)
18 product architectures from autonomous access points to centralized
19 control of lightweight access points. The general goal has been to
20 move most of the traditional wireless functionality such as access
21 control (user authentication and authorization), mobility, and radio
22 management out of the access point into a centralized controller.
23
24 The IETF's CAPWAP (Control and Provisioning of Wireless Access
25 Points) WG has identified that a standards-based protocol is
26 necessary between a wireless Access Controller and Wireless
27 Termination Points (the latter are also commonly referred to as
28 Lightweight Access Points). This specification defines the
29 Lightweight Access Point Protocol (LWAPP), which addresses the
30 CAPWAP's (Control and Provisioning of Wireless Access Points)
31 protocol requirements. Although the LWAPP protocol is designed to be
32 flexible enough to be used for a variety of wireless technologies,
33 this specific document describes the base protocol and an extension
34 that allows it to be used with the IEEE's 802.11 wireless LAN
35 protocol.
36
37 Status of This Memo
38
39 This document is not an Internet Standards Track specification; it is
40 published for the historical record.
41
42 This document defines a Historic Document for the Internet community.
43 This is a contribution to the RFC Series, independently of any other
44 RFC stream. The RFC Editor has chosen to publish this document at
45 its discretion and makes no statement about its value for
46 implementation or deployment. Documents approved for publication by
47 the RFC Editor are not a candidate for any level of Internet
48 Standard; see <a href="./rfc5741#section-2">Section&nbsp;2 of RFC 5741</a>.
49
50
51
52 <span class="grey">Calhoun, et al. Historic [Page 1]</span></pre>
53 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
54 <span class="grey"><a href="./rfc5412">RFC 5412</a> Lightweight Access Point Protocol February 2010</span>
55
56
57 Information about the current status of this document, any errata,
58 and how to provide feedback on it may be obtained at
59 <a href="http://www.rfc-editor.org/info/rfc5412">http://www.rfc-editor.org/info/rfc5412</a>.
60
61 IESG Note
62
63 This RFC documents the LWAPP protocol as it was when submitted to the
64 IETF as a basis for further work in the CAPWAP Working Group, and
65 therefore it may resemble the CAPWAP protocol specification in <a href="./rfc5415">RFC</a>
66 <a href="./rfc5415">5415</a> as well as other IETF work. This RFC is being published solely
67 for the historical record. The protocol described in this RFC has
68 not been thoroughly reviewed and may contain errors and omissions.
69
70 <a href="./rfc5415">RFC 5415</a> documents the standards track solution for the CAPWAP
71 Working Group and obsoletes any and all mechanisms defined in this
72 RFC. This RFC is not a candidate for any level of Internet Standard
73 and should not be used as a basis for any sort of Internet
74 deployment.
75
76 Copyright Notice
77
78 Copyright (c) 2010 IETF Trust and the persons identified as the
79 document authors. All rights reserved.
80
81 This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal
82 Provisions Relating to IETF Documents
83 (<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of
84 publication of this document. Please review these documents
85 carefully, as they describe your rights and restrictions with respect
86 to this document.
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108 <span class="grey">Calhoun, et al. Historic [Page 2]</span></pre>
109 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
110 <span class="grey"><a href="./rfc5412">RFC 5412</a> Lightweight Access Point Protocol February 2010</span>
111
112
113 Table of Contents
114
115 <a href="#section-1">1</a>. Introduction ....................................................<a href="#page-8">8</a>
116 <a href="#section-1.1">1.1</a>. Conventions Used in This Document ..........................<a href="#page-9">9</a>
117 <a href="#section-2">2</a>. Protocol Overview ..............................................<a href="#page-10">10</a>
118 <a href="#section-2.1">2.1</a>. Wireless Binding Definition ...............................<a href="#page-11">11</a>
119 <a href="#section-2.2">2.2</a>. LWAPP State Machine Definition ............................<a href="#page-12">12</a>
120 <a href="#section-3">3</a>. LWAPP Transport Layers .........................................<a href="#page-20">20</a>
121 <a href="#section-3.1">3.1</a>. LWAPP Transport Header ....................................<a href="#page-21">21</a>
122 <a href="#section-3.1.1">3.1.1</a>. VER Field ..........................................<a href="#page-21">21</a>
123 <a href="#section-3.1.2">3.1.2</a>. RID Field ..........................................<a href="#page-21">21</a>
124 <a href="#section-3.1.3">3.1.3</a>. C Bit ..............................................<a href="#page-21">21</a>
125 <a href="#section-3.1.4">3.1.4</a>. F Bit ..............................................<a href="#page-21">21</a>
126 <a href="#section-3.1.5">3.1.5</a>. L Bit ..............................................<a href="#page-22">22</a>
127 <a href="#section-3.1.6">3.1.6</a>. Fragment ID ........................................<a href="#page-22">22</a>
128 <a href="#section-3.1.7">3.1.7</a>. Length .............................................<a href="#page-22">22</a>
129 <a href="#section-3.1.8">3.1.8</a>. Status and WLANS ...................................<a href="#page-22">22</a>
130 <a href="#section-3.1.9">3.1.9</a>. Payload ............................................<a href="#page-22">22</a>
131 <a href="#section-3.2">3.2</a>. Using IEEE 802.3 MAC as LWAPP Transport ...................<a href="#page-22">22</a>
132 <a href="#section-3.2.1">3.2.1</a>. Framing ............................................<a href="#page-23">23</a>
133 <a href="#section-3.2.2">3.2.2</a>. AC Discovery .......................................<a href="#page-23">23</a>
134 3.2.3. LWAPP Message Header Format over IEEE 802.3
135 MAC Transport ......................................<a href="#page-23">23</a>
136 <a href="#section-3.2.4">3.2.4</a>. Fragmentation/Reassembly ...........................<a href="#page-24">24</a>
137 <a href="#section-3.2.5">3.2.5</a>. Multiplexing .......................................<a href="#page-24">24</a>
138 <a href="#section-3.3">3.3</a>. Using IP/UDP as LWAPP Transport ...........................<a href="#page-24">24</a>
139 <a href="#section-3.3.1">3.3.1</a>. Framing ............................................<a href="#page-24">24</a>
140 <a href="#section-3.3.2">3.3.2</a>. AC Discovery .......................................<a href="#page-25">25</a>
141 <a href="#section-3.3.3">3.3.3</a>. LWAPP Message Header Format over IP/UDP Transport ..25
142 <a href="#section-3.3.4">3.3.4</a>. Fragmentation/Reassembly for IPv4 ..................<a href="#page-26">26</a>
143 <a href="#section-3.3.5">3.3.5</a>. Fragmentation/Reassembly for IPv6 ..................<a href="#page-26">26</a>
144 <a href="#section-3.3.6">3.3.6</a>. Multiplexing .......................................<a href="#page-26">26</a>
145 <a href="#section-4">4</a>. LWAPP Packet Definitions .......................................<a href="#page-26">26</a>
146 <a href="#section-4.1">4.1</a>. LWAPP Data Messages .......................................<a href="#page-27">27</a>
147 <a href="#section-4.2">4.2</a>. LWAPP Control Messages Overview ...........................<a href="#page-27">27</a>
148 <a href="#section-4.2.1">4.2.1</a>. Control Message Format .............................<a href="#page-28">28</a>
149 <a href="#section-4.2.2">4.2.2</a>. Message Element Format .............................<a href="#page-29">29</a>
150 <a href="#section-4.2.3">4.2.3</a>. Quality of Service .................................<a href="#page-31">31</a>
151 <a href="#section-5">5</a>. LWAPP Discovery Operations .....................................<a href="#page-31">31</a>
152 <a href="#section-5.1">5.1</a>. Discovery Request .........................................<a href="#page-31">31</a>
153 <a href="#section-5.1.1">5.1.1</a>. Discovery Type .....................................<a href="#page-32">32</a>
154 <a href="#section-5.1.2">5.1.2</a>. WTP Descriptor .....................................<a href="#page-33">33</a>
155 <a href="#section-5.1.3">5.1.3</a>. WTP Radio Information ..............................<a href="#page-34">34</a>
156 <a href="#section-5.2">5.2</a>. Discovery Response ........................................<a href="#page-34">34</a>
157 <a href="#section-5.2.1">5.2.1</a>. AC Address .........................................<a href="#page-35">35</a>
158 <a href="#section-5.2.2">5.2.2</a>. AC Descriptor ......................................<a href="#page-35">35</a>
159 <a href="#section-5.2.3">5.2.3</a>. AC Name ............................................<a href="#page-36">36</a>
160 <a href="#section-5.2.4">5.2.4</a>. WTP Manager Control IPv4 Address ...................<a href="#page-37">37</a>
161
162
163
164 <span class="grey">Calhoun, et al. Historic [Page 3]</span></pre>
165 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
166 <span class="grey"><a href="./rfc5412">RFC 5412</a> Lightweight Access Point Protocol February 2010</span>
167
168
169 <a href="#section-5.2.5">5.2.5</a>. WTP Manager Control IPv6 Address ...................<a href="#page-37">37</a>
170 <a href="#section-5.3">5.3</a>. Primary Discovery Request .................................<a href="#page-38">38</a>
171 <a href="#section-5.3.1">5.3.1</a>. Discovery Type .....................................<a href="#page-38">38</a>
172 <a href="#section-5.3.2">5.3.2</a>. WTP Descriptor .....................................<a href="#page-38">38</a>
173 <a href="#section-5.3.3">5.3.3</a>. WTP Radio Information ..............................<a href="#page-38">38</a>
174 <a href="#section-5.4">5.4</a>. Primary Discovery Response ................................<a href="#page-38">38</a>
175 <a href="#section-5.4.1">5.4.1</a>. AC Descriptor ......................................<a href="#page-39">39</a>
176 <a href="#section-5.4.2">5.4.2</a>. AC Name ............................................<a href="#page-39">39</a>
177 <a href="#section-5.4.3">5.4.3</a>. WTP Manager Control IPv4 Address ...................<a href="#page-39">39</a>
178 <a href="#section-5.4.4">5.4.4</a>. WTP Manager Control IPv6 Address ...................<a href="#page-39">39</a>
179 <a href="#section-6">6</a>. Control Channel Management .....................................<a href="#page-39">39</a>
180 <a href="#section-6.1">6.1</a>. Join Request ..............................................<a href="#page-39">39</a>
181 <a href="#section-6.1.1">6.1.1</a>. WTP Descriptor .....................................<a href="#page-40">40</a>
182 <a href="#section-6.1.2">6.1.2</a>. AC Address .........................................<a href="#page-40">40</a>
183 <a href="#section-6.1.3">6.1.3</a>. WTP Name ...........................................<a href="#page-40">40</a>
184 <a href="#section-6.1.4">6.1.4</a>. Location Data ......................................<a href="#page-41">41</a>
185 <a href="#section-6.1.5">6.1.5</a>. WTP Radio Information ..............................<a href="#page-41">41</a>
186 <a href="#section-6.1.6">6.1.6</a>. Certificate ........................................<a href="#page-41">41</a>
187 <a href="#section-6.1.7">6.1.7</a>. Session ID .........................................<a href="#page-42">42</a>
188 <a href="#section-6.1.8">6.1.8</a>. Test ...............................................<a href="#page-42">42</a>
189 <a href="#section-6.1.9">6.1.9</a>. XNonce .............................................<a href="#page-42">42</a>
190 <a href="#section-6.2">6.2</a>. Join Response .............................................<a href="#page-43">43</a>
191 <a href="#section-6.2.1">6.2.1</a>. Result Code ........................................<a href="#page-44">44</a>
192 <a href="#section-6.2.2">6.2.2</a>. Status .............................................<a href="#page-44">44</a>
193 <a href="#section-6.2.3">6.2.3</a>. Certificate ........................................<a href="#page-45">45</a>
194 <a href="#section-6.2.4">6.2.4</a>. WTP Manager Data IPv4 Address ......................<a href="#page-45">45</a>
195 <a href="#section-6.2.5">6.2.5</a>. WTP Manager Data IPv6 Address ......................<a href="#page-45">45</a>
196 <a href="#section-6.2.6">6.2.6</a>. AC IPv4 List .......................................<a href="#page-46">46</a>
197 <a href="#section-6.2.7">6.2.7</a>. AC IPv6 List .......................................<a href="#page-46">46</a>
198 <a href="#section-6.2.8">6.2.8</a>. ANonce .............................................<a href="#page-47">47</a>
199 <a href="#section-6.2.9">6.2.9</a>. PSK-MIC ............................................<a href="#page-48">48</a>
200 <a href="#section-6.3">6.3</a>. Join ACK ..................................................<a href="#page-48">48</a>
201 <a href="#section-6.3.1">6.3.1</a>. Session ID .........................................<a href="#page-49">49</a>
202 <a href="#section-6.3.2">6.3.2</a>. WNonce .............................................<a href="#page-49">49</a>
203 <a href="#section-6.3.3">6.3.3</a>. PSK-MIC ............................................<a href="#page-49">49</a>
204 <a href="#section-6.4">6.4</a>. Join Confirm ..............................................<a href="#page-49">49</a>
205 <a href="#section-6.4.1">6.4.1</a>. Session ID .........................................<a href="#page-50">50</a>
206 <a href="#section-6.4.2">6.4.2</a>. PSK-MIC ............................................<a href="#page-50">50</a>
207 <a href="#section-6.5">6.5</a>. Echo Request ..............................................<a href="#page-50">50</a>
208 <a href="#section-6.6">6.6</a>. Echo Response .............................................<a href="#page-50">50</a>
209 <a href="#section-6.7">6.7</a>. Key Update Request ........................................<a href="#page-51">51</a>
210 <a href="#section-6.7.1">6.7.1</a>. Session ID .........................................<a href="#page-51">51</a>
211 <a href="#section-6.7.2">6.7.2</a>. XNonce .............................................<a href="#page-51">51</a>
212 <a href="#section-6.8">6.8</a>. Key Update Response .......................................<a href="#page-51">51</a>
213 <a href="#section-6.8.1">6.8.1</a>. Session ID .........................................<a href="#page-51">51</a>
214 <a href="#section-6.8.2">6.8.2</a>. ANonce .............................................<a href="#page-51">51</a>
215 <a href="#section-6.8.3">6.8.3</a>. PSK-MIC ............................................<a href="#page-52">52</a>
216 <a href="#section-6.9">6.9</a>. Key Update ACK ............................................<a href="#page-52">52</a>
217
218
219
220 <span class="grey">Calhoun, et al. Historic [Page 4]</span></pre>
221 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
222 <span class="grey"><a href="./rfc5412">RFC 5412</a> Lightweight Access Point Protocol February 2010</span>
223
224
225 <a href="#section-6.9.1">6.9.1</a>. WNonce .............................................<a href="#page-52">52</a>
226 <a href="#section-6.9.2">6.9.2</a>. PSK-MIC ............................................<a href="#page-52">52</a>
227 <a href="#section-6.10">6.10</a>. Key Update Confirm .......................................<a href="#page-52">52</a>
228 <a href="#section-6.10.1">6.10.1</a>. PSK-MIC ...........................................<a href="#page-52">52</a>
229 <a href="#section-6.11">6.11</a>. Key Update Trigger .......................................<a href="#page-52">52</a>
230 <a href="#section-6.11.1">6.11.1</a>. Session ID ........................................<a href="#page-53">53</a>
231 <a href="#section-7">7</a>. WTP Configuration Management ...................................<a href="#page-53">53</a>
232 <a href="#section-7.1">7.1</a>. Configuration Consistency .................................<a href="#page-53">53</a>
233 <a href="#section-7.2">7.2</a>. Configure Request .........................................<a href="#page-54">54</a>
234 <a href="#section-7.2.1">7.2.1</a>. Administrative State ...............................<a href="#page-54">54</a>
235 <a href="#section-7.2.2">7.2.2</a>. AC Name ............................................<a href="#page-55">55</a>
236 <a href="#section-7.2.3">7.2.3</a>. AC Name with Index .................................<a href="#page-55">55</a>
237 <a href="#section-7.2.4">7.2.4</a>. WTP Board Data .....................................<a href="#page-56">56</a>
238 <a href="#section-7.2.5">7.2.5</a>. Statistics Timer ...................................<a href="#page-56">56</a>
239 <a href="#section-7.2.6">7.2.6</a>. WTP Static IP Address Information ..................<a href="#page-57">57</a>
240 <a href="#section-7.2.7">7.2.7</a>. WTP Reboot Statistics ..............................<a href="#page-58">58</a>
241 <a href="#section-7.3">7.3</a>. Configure Response ........................................<a href="#page-58">58</a>
242 <a href="#section-7.3.1">7.3.1</a>. Decryption Error Report Period .....................<a href="#page-59">59</a>
243 <a href="#section-7.3.2">7.3.2</a>. Change State Event .................................<a href="#page-59">59</a>
244 <a href="#section-7.3.3">7.3.3</a>. LWAPP Timers .......................................<a href="#page-60">60</a>
245 <a href="#section-7.3.4">7.3.4</a>. AC IPv4 List .......................................<a href="#page-60">60</a>
246 <a href="#section-7.3.5">7.3.5</a>. AC IPv6 List .......................................<a href="#page-61">61</a>
247 <a href="#section-7.3.6">7.3.6</a>. WTP Fallback .......................................<a href="#page-61">61</a>
248 <a href="#section-7.3.7">7.3.7</a>. Idle Timeout .......................................<a href="#page-61">61</a>
249 <a href="#section-7.4">7.4</a>. Configuration Update Request ..............................<a href="#page-62">62</a>
250 <a href="#section-7.4.1">7.4.1</a>. WTP Name ...........................................<a href="#page-62">62</a>
251 <a href="#section-7.4.2">7.4.2</a>. Change State Event .................................<a href="#page-62">62</a>
252 <a href="#section-7.4.3">7.4.3</a>. Administrative State ...............................<a href="#page-62">62</a>
253 <a href="#section-7.4.4">7.4.4</a>. Statistics Timer ...................................<a href="#page-62">62</a>
254 <a href="#section-7.4.5">7.4.5</a>. Location Data ......................................<a href="#page-62">62</a>
255 <a href="#section-7.4.6">7.4.6</a>. Decryption Error Report Period .....................<a href="#page-62">62</a>
256 <a href="#section-7.4.7">7.4.7</a>. AC IPv4 List .......................................<a href="#page-62">62</a>
257 <a href="#section-7.4.8">7.4.8</a>. AC IPv6 List .......................................<a href="#page-62">62</a>
258 <a href="#section-7.4.9">7.4.9</a>. Add Blacklist Entry ................................<a href="#page-63">63</a>
259 <a href="#section-7.4.10">7.4.10</a>. Delete Blacklist Entry ............................<a href="#page-63">63</a>
260 <a href="#section-7.4.11">7.4.11</a>. Add Static Blacklist Entry ........................<a href="#page-64">64</a>
261 <a href="#section-7.4.12">7.4.12</a>. Delete Static Blacklist Entry .....................<a href="#page-64">64</a>
262 <a href="#section-7.4.13">7.4.13</a>. LWAPP Timers ......................................<a href="#page-65">65</a>
263 <a href="#section-7.4.14">7.4.14</a>. AC Name with Index ................................<a href="#page-65">65</a>
264 <a href="#section-7.4.15">7.4.15</a>. WTP Fallback ......................................<a href="#page-65">65</a>
265 <a href="#section-7.4.16">7.4.16</a>. Idle Timeout ......................................<a href="#page-65">65</a>
266 <a href="#section-7.5">7.5</a>. Configuration Update Response .............................<a href="#page-65">65</a>
267 <a href="#section-7.5.1">7.5.1</a>. Result Code ........................................<a href="#page-65">65</a>
268 <a href="#section-7.6">7.6</a>. Change State Event Request ................................<a href="#page-65">65</a>
269 <a href="#section-7.6.1">7.6.1</a>. Change State Event .................................<a href="#page-66">66</a>
270 <a href="#section-7.7">7.7</a>. Change State Event Response ...............................<a href="#page-66">66</a>
271 <a href="#section-7.8">7.8</a>. Clear Config Indication ...................................<a href="#page-66">66</a>
272 <a href="#section-8">8</a>. Device Management Operations ...................................<a href="#page-66">66</a>
273
274
275
276 <span class="grey">Calhoun, et al. Historic [Page 5]</span></pre>
277 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
278 <span class="grey"><a href="./rfc5412">RFC 5412</a> Lightweight Access Point Protocol February 2010</span>
279
280
281 <a href="#section-8.1">8.1</a>. Image Data Request ........................................<a href="#page-66">66</a>
282 <a href="#section-8.1.1">8.1.1</a>. Image Download .....................................<a href="#page-67">67</a>
283 <a href="#section-8.1.2">8.1.2</a>. Image Data .........................................<a href="#page-67">67</a>
284 <a href="#section-8.2">8.2</a>. Image Data Response .......................................<a href="#page-68">68</a>
285 <a href="#section-8.3">8.3</a>. Reset Request .............................................<a href="#page-68">68</a>
286 <a href="#section-8.4">8.4</a>. Reset Response ............................................<a href="#page-68">68</a>
287 <a href="#section-8.5">8.5</a>. WTP Event Request .........................................<a href="#page-68">68</a>
288 <a href="#section-8.5.1">8.5.1</a>. Decryption Error Report ............................<a href="#page-69">69</a>
289 <a href="#section-8.5.2">8.5.2</a>. Duplicate IPv4 Address .............................<a href="#page-69">69</a>
290 <a href="#section-8.5.3">8.5.3</a>. Duplicate IPv6 Address .............................<a href="#page-70">70</a>
291 <a href="#section-8.6">8.6</a>. WTP Event Response ........................................<a href="#page-70">70</a>
292 <a href="#section-8.7">8.7</a>. Data Transfer Request .....................................<a href="#page-71">71</a>
293 <a href="#section-8.7.1">8.7.1</a>. Data Transfer Mode .................................<a href="#page-71">71</a>
294 <a href="#section-8.7.2">8.7.2</a>. Data Transfer Data .................................<a href="#page-71">71</a>
295 <a href="#section-8.8">8.8</a>. Data Transfer Response ....................................<a href="#page-72">72</a>
296 <a href="#section-9">9</a>. Mobile Session Management ......................................<a href="#page-72">72</a>
297 <a href="#section-9.1">9.1</a>. Mobile Config Request .....................................<a href="#page-72">72</a>
298 <a href="#section-9.1.1">9.1.1</a>. Delete Mobile ......................................<a href="#page-73">73</a>
299 <a href="#section-9.2">9.2</a>. Mobile Config Response ....................................<a href="#page-73">73</a>
300 <a href="#section-9.2.1">9.2.1</a>. Result Code ........................................<a href="#page-74">74</a>
301 <a href="#section-10">10</a>. LWAPP Security ................................................<a href="#page-74">74</a>
302 <a href="#section-10.1">10.1</a>. Securing WTP-AC Communications ...........................<a href="#page-74">74</a>
303 <a href="#section-10.2">10.2</a>. LWAPP Frame Encryption ...................................<a href="#page-75">75</a>
304 <a href="#section-10.3">10.3</a>. Authenticated Key Exchange ...............................<a href="#page-76">76</a>
305 <a href="#section-10.3.1">10.3.1</a>. Terminology .......................................<a href="#page-76">76</a>
306 <a href="#section-10.3.2">10.3.2</a>. Initial Key Generation ............................<a href="#page-77">77</a>
307 <a href="#section-10.3.3">10.3.3</a>. Refreshing Cryptographic Keys .....................<a href="#page-81">81</a>
308 <a href="#section-10.4">10.4</a>. Certificate Usage ........................................<a href="#page-82">82</a>
309 <a href="#section-11">11</a>. IEEE 802.11 Binding ...........................................<a href="#page-82">82</a>
310 <a href="#section-11.1">11.1</a>. Division of Labor ........................................<a href="#page-82">82</a>
311 <a href="#section-11.1.1">11.1.1</a>. Split MAC .........................................<a href="#page-83">83</a>
312 <a href="#section-11.1.2">11.1.2</a>. Local MAC .........................................<a href="#page-85">85</a>
313 <a href="#section-11.2">11.2</a>. Roaming Behavior and 802.11 Security .....................<a href="#page-87">87</a>
314 <a href="#section-11.3">11.3</a>. Transport-Specific Bindings ..............................<a href="#page-88">88</a>
315 <a href="#section-11.3.1">11.3.1</a>. Status and WLANS Field ............................<a href="#page-88">88</a>
316 <a href="#section-11.4">11.4</a>. BSSID to WLAN ID Mapping .................................<a href="#page-89">89</a>
317 <a href="#section-11.5">11.5</a>. Quality of Service .......................................<a href="#page-89">89</a>
318 <a href="#section-11.6">11.6</a>. Data Message Bindings ....................................<a href="#page-90">90</a>
319 <a href="#section-11.7">11.7</a>. Control Message Bindings .................................<a href="#page-90">90</a>
320 <a href="#section-11.7.1">11.7.1</a>. Mobile Config Request .............................<a href="#page-90">90</a>
321 <a href="#section-11.7.2">11.7.2</a>. WTP Event Request .................................<a href="#page-96">96</a>
322 <a href="#section-11.8">11.8</a>. 802.11 Control Messages ..................................<a href="#page-97">97</a>
323 <a href="#section-11.8.1">11.8.1</a>. IEEE 802.11 WLAN Config Request ...................<a href="#page-98">98</a>
324 <a href="#section-11.8.2">11.8.2</a>. IEEE 802.11 WLAN Config Response .................<a href="#page-103">103</a>
325 <a href="#section-11.8.3">11.8.3</a>. IEEE 802.11 WTP Event ............................<a href="#page-103">103</a>
326 <a href="#section-11.9">11.9</a>. Message Element Bindings ................................<a href="#page-105">105</a>
327 <a href="#section-11.9.1">11.9.1</a>. IEEE 802.11 WTP WLAN Radio Configuration .........<a href="#page-105">105</a>
328 <a href="#section-11.9.2">11.9.2</a>. IEEE 802.11 Rate Set .............................<a href="#page-107">107</a>
329
330
331
332 <span class="grey">Calhoun, et al. Historic [Page 6]</span></pre>
333 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
334 <span class="grey"><a href="./rfc5412">RFC 5412</a> Lightweight Access Point Protocol February 2010</span>
335
336
337 <a href="#section-11.9.3">11.9.3</a>. IEEE 802.11 Multi-Domain Capability ..............<a href="#page-107">107</a>
338 <a href="#section-11.9.4">11.9.4</a>. IEEE 802.11 MAC Operation ........................<a href="#page-108">108</a>
339 <a href="#section-11.9.5">11.9.5</a>. IEEE 802.11 Tx Power .............................<a href="#page-109">109</a>
340 <a href="#section-11.9.6">11.9.6</a>. IEEE 802.11 Tx Power Level .......................<a href="#page-110">110</a>
341 <a href="#section-11.9.7">11.9.7</a>. IEEE 802.11 Direct Sequence Control ..............<a href="#page-110">110</a>
342 <a href="#section-11.9.8">11.9.8</a>. IEEE 802.11 OFDM Control .........................<a href="#page-111">111</a>
343 <a href="#section-11.9.9">11.9.9</a>. IEEE 802.11 Antenna ..............................<a href="#page-112">112</a>
344 <a href="#section-11.9.10">11.9.10</a>. IEEE 802.11 Supported Rates .....................<a href="#page-113">113</a>
345 <a href="#section-11.9.11">11.9.11</a>. IEEE 802.11 CFP Status ..........................<a href="#page-114">114</a>
346 <a href="#section-11.9.12">11.9.12</a>. IEEE 802.11 WTP Mode and Type ...................<a href="#page-114">114</a>
347 <a href="#section-11.9.13">11.9.13</a>. IEEE 802.11 Broadcast Probe Mode ................<a href="#page-115">115</a>
348 <a href="#section-11.9.14">11.9.14</a>. IEEE 802.11 WTP Quality of Service ..............<a href="#page-115">115</a>
349 <a href="#section-11.9.15">11.9.15</a>. IEEE 802.11 MIC Error Report From Mobile ........<a href="#page-117">117</a>
350 <a href="#section-11.10">11.10</a>. IEEE 802.11 Message Element Values .....................<a href="#page-117">117</a>
351 <a href="#section-12">12</a>. LWAPP Protocol Timers ........................................<a href="#page-118">118</a>
352 <a href="#section-12.1">12.1</a>. MaxDiscoveryInterval ....................................<a href="#page-118">118</a>
353 <a href="#section-12.2">12.2</a>. SilentInterval ..........................................<a href="#page-118">118</a>
354 <a href="#section-12.3">12.3</a>. NeighborDeadInterval ....................................<a href="#page-118">118</a>
355 <a href="#section-12.4">12.4</a>. EchoInterval ............................................<a href="#page-118">118</a>
356 <a href="#section-12.5">12.5</a>. DiscoveryInterval .......................................<a href="#page-118">118</a>
357 <a href="#section-12.6">12.6</a>. RetransmitInterval ......................................<a href="#page-119">119</a>
358 <a href="#section-12.7">12.7</a>. ResponseTimeout .........................................<a href="#page-119">119</a>
359 <a href="#section-12.8">12.8</a>. KeyLifetime .............................................<a href="#page-119">119</a>
360 <a href="#section-13">13</a>. LWAPP Protocol Variables .....................................<a href="#page-119">119</a>
361 <a href="#section-13.1">13.1</a>. MaxDiscoveries ..........................................<a href="#page-119">119</a>
362 <a href="#section-13.2">13.2</a>. DiscoveryCount ..........................................<a href="#page-119">119</a>
363 <a href="#section-13.3">13.3</a>. RetransmitCount .........................................<a href="#page-119">119</a>
364 <a href="#section-13.4">13.4</a>. MaxRetransmit ...........................................<a href="#page-120">120</a>
365 <a href="#section-14">14</a>. NAT Considerations ...........................................<a href="#page-120">120</a>
366 <a href="#section-15">15</a>. Security Considerations ......................................<a href="#page-121">121</a>
367 <a href="#section-15.1">15.1</a>. Certificate-Based Session Key Establishment .............<a href="#page-122">122</a>
368 <a href="#section-15.2">15.2</a>. PSK-Based Session Key Establishment .....................<a href="#page-123">123</a>
369 <a href="#section-16">16</a>. Acknowledgements .............................................<a href="#page-123">123</a>
370 <a href="#section-17">17</a>. References ...................................................<a href="#page-123">123</a>
371 <a href="#section-17.1">17.1</a>. Normative References ....................................<a href="#page-123">123</a>
372 <a href="#section-17.2">17.2</a>. Informative References ..................................<a href="#page-124">124</a>
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388 <span class="grey">Calhoun, et al. Historic [Page 7]</span></pre>
389 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
390 <span class="grey"><a href="./rfc5412">RFC 5412</a> Lightweight Access Point Protocol February 2010</span>
391
392
393 <span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
394
395 Unlike wired network elements, Wireless Termination Points (WTPs)
396 require a set of dynamic management and control functions related to
397 their primary task of connecting the wireless and wired mediums.
398 Today, protocols for managing WTPs are either manual static
399 configuration via HTTP, proprietary Layer 2-specific, or non-existent
400 (if the WTPs are self-contained). The emergence of simple 802.11
401 WTPs that are managed by a WLAN appliance or switch (also known as an
402 Access Controller, or AC) suggests that having a standardized,
403 interoperable protocol could radically simplify the deployment and
404 management of wireless networks. In many cases, the overall control
405 and management functions themselves are generic and could apply to an
406 AP for any wireless Layer 2 (L2) protocol. Being independent of
407 specific wireless Layer 2 technologies, such a protocol could better
408 support interoperability between Layer 2 devices and enable smoother
409 intertechnology handovers.
410
411 The details of how these functions would be implemented are dependent
412 on the particular Layer 2 wireless technology. Such a protocol would
413 need provisions for binding to specific technologies.
414
415 LWAPP assumes a network configuration that consists of multiple WTPs
416 communicating either via Layer 2 (Medium Access Control (MAC)) or
417 Layer 3 (IP) to an AC. The WTPs can be considered as remote radio
418 frequency (RF) interfaces, being controlled by the AC. The AC
419 forwards all L2 frames it wants to transmit to a WTP via the LWAPP
420 protocol. Packets from mobile nodes are forwarded by the WTP to the
421 AC, also via this protocol. Figure 1 illustrates this arrangement as
422 applied to an IEEE 802.11 binding.
423
424 +-+ 802.11 frames +-+
425 | |--------------------------------| |
426 | | +-+ | |
427 | |--------------| |---------------| |
428 | | 802.11 PHY/ | | LWAPP | |
429 | | MAC sublayer | | | |
430 +-+ +-+ +-+
431 STA WTP AC
432
433 Figure 1: LWAPP Architecture
434
435
436
437
438
439
440
441
442
443
444 <span class="grey">Calhoun, et al. Historic [Page 8]</span></pre>
445 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
446 <span class="grey"><a href="./rfc5412">RFC 5412</a> Lightweight Access Point Protocol February 2010</span>
447
448
449 Security is another aspect of Wireless Termination Point management
450 that is not well served by existing solutions. Provisioning WTPs
451 with security credentials, and managing which WTPs are authorized to
452 provide service are today handled by proprietary solutions. Allowing
453 these functions to be performed from a centralized AC in an
454 interoperable fashion increases manageability and allows network
455 operators to more tightly control their wireless network
456 infrastructure.
457
458 This document describes the Lightweight Access Point Protocol
459 (LWAPP), allowing an AC to manage a collection of WTPs. The protocol
460 is defined to be independent of Layer 2 technology, but an 802.11
461 binding is provided for use in growing 802.11 wireless LAN networks.
462
463 Goals:
464
465 The following are goals for this protocol:
466
467 1. Centralization of the bridging, forwarding, authentication, and
468 policy enforcement functions for a wireless network. Optionally,
469 the AC may also provide centralized encryption of user traffic.
470 This will permit reduced cost and higher efficiency when applying
471 the capabilities of network processing silicon to the wireless
472 network, as it has already been applied to wired LANs.
473
474 2. Permit shifting of the higher-level protocol processing burden
475 away from the WTP. This leaves the computing resource of the WTP
476 to the timing-critical applications of wireless control and
477 access. This makes the most efficient use of the computing power
478 available in WTPs that are the subject of severe cost pressure.
479
480 3. Providing a generic encapsulation and transport mechanism, the
481 protocol may be applied to other access point types in the future
482 by adding the binding.
483
484 The LWAPP protocol concerns itself solely with the interface between
485 the WTP and the AC. Inter-AC, or mobile-to-AC communication is
486 strictly outside the scope of this document.
487
488 <span class="h3"><a class="selflink" id="section-1.1" href="#section-1.1">1.1</a>. Conventions Used in This Document</span>
489
490 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
491 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
492 document are to be interpreted as described in <a href="./rfc2119">RFC 2119</a> [<a href="#ref-1" title="&quot;Key words for use in RFCs to Indicate Requirement Levels&quot;">1</a>].
493
494
495
496
497
498
499
500 <span class="grey">Calhoun, et al. Historic [Page 9]</span></pre>
501 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
502 <span class="grey"><a href="./rfc5412">RFC 5412</a> Lightweight Access Point Protocol February 2010</span>
503
504
505 <span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Protocol Overview</span>
506
507 LWAPP is a generic protocol defining how Wireless Termination Points
508 communicate with Access Controllers. Wireless Termination Points and
509 Access Controllers may communicate either by means of Layer 2
510 protocols or by means of a routed IP network.
511
512 LWAPP messages and procedures defined in this document apply to both
513 types of transports unless specified otherwise. Transport
514 independence is achieved by defining formats for both MAC-level and
515 IP-level transport (see <a href="#section-3">Section 3</a>). Also defined are framing,
516 fragmentation/reassembly, and multiplexing services to LWAPP for each
517 transport type.
518
519 The LWAPP Transport layer carries two types of payload. LWAPP data
520 messages are forwarded wireless frames. LWAPP control messages are
521 management messages exchanged between a WTP and an AC. The LWAPP
522 transport header defines the "C-bit", which is used to distinguish
523 data and control traffic. When used over IP, the LWAPP data and
524 control traffic are also sent over separate UDP ports. Since both
525 data and control frames can exceed Path Maximum Transmission Unit
526 (PMTU), the payload of an LWAPP data or control message can be
527 fragmented. The fragmentation behavior is highly dependent upon the
528 lower-layer transport and is defined in <a href="#section-3">Section 3</a>.
529
530 The Lightweight Access Protocol (LWAPP) begins with a discovery
531 phase. The WTPs send a Discovery Request frame, causing any Access
532 Controller (AC), receiving that frame to respond with a Discovery
533 Response. From the Discovery Responses received, a WTP will select
534 an AC with which to associate, using the Join Request and Join
535 Response. The Join Request also provides an MTU discovery mechanism,
536 to determine whether there is support for the transport of large
537 frames between the WTP and its AC. If support for large frames is
538 not present, the LWAPP frames will be fragmented to the maximum
539 length discovered to be supported by the network.
540
541 Once the WTP and the AC have joined, a configuration exchange is
542 accomplished that will cause both devices to agree on version
543 information. During this exchange, the WTP may receive provisioning
544 settings. For the 802.11 binding, this information would typically
545 include a name (802.11 Service Set Identifier, SSID), and security
546 parameters, the data rates to be advertised, as well as the radio
547 channel (channels, if the WTP is capable of operating more than one
548 802.11 MAC and Physical Layer (PHY) simultaneously) to be used.
549 Finally, the WTPs are enabled for operation.
550
551
552
553
554
555
556 <span class="grey">Calhoun, et al. Historic [Page 10]</span></pre>
557 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
558 <span class="grey"><a href="./rfc5412">RFC 5412</a> Lightweight Access Point Protocol February 2010</span>
559
560
561 When the WTP and AC have completed the version and provision exchange
562 and the WTP is enabled, the LWAPP encapsulates the wireless frames
563 sent between them. LWAPP will fragment its packets, if the size of
564 the encapsulated wireless user data (Data) or protocol control
565 (Management) frames cause the resultant LWAPP packet to exceed the
566 MTU supported between the WTP and AC. Fragmented LWAPP packets are
567 reassembled to reconstitute the original encapsulated payload.
568
569 In addition to the functions thus far described, LWAPP also provides
570 for the delivery of commands from the AC to the WTP for the
571 management of devices that are communicating with the WTP. This may
572 include the creation of local data structures in the WTP for the
573 managed devices and the collection of statistical information about
574 the communication between the WTP and the 802.11 devices. LWAPP
575 provides the ability for the AC to obtain any statistical information
576 collected by the WTP.
577
578 LWAPP also provides for a keepalive feature that preserves the
579 communication channel between the WTP and AC. If the AC fails to
580 appear alive, the WTP will try to discover a new AC to communicate
581 through.
582
583 This document uses terminology defined in [<a href="#ref-5" title="&quot;Mobility Related Terminology&quot;">5</a>].
584
585 <span class="h3"><a class="selflink" id="section-2.1" href="#section-2.1">2.1</a>. Wireless Binding Definition</span>
586
587 This draft standard specifies a protocol independent of a specific
588 wireless access point radio technology. Elements of the protocol are
589 designed to accommodate specific needs of each wireless technology in
590 a standard way. Implementation of this standard for a particular
591 wireless technology must follow the binding requirements defined for
592 that technology. This specification includes a binding for the IEEE
593 802.11 (see <a href="#section-11">Section 11</a>).
594
595 When defining a binding for other technologies, the authors MUST
596 include any necessary definitions for technology-specific messages
597 and all technology-specific message elements for those messages. At
598 a minimum, a binding MUST provide the definition for a binding-
599 specific Statistics message element, which is carried in the WTP
600 Event Request message, and Add Mobile message element, which is
601 carried in the Mobile Configure Request. If any technology-specific
602 message elements are required for any of the existing LWAPP messages
603 defined in this specification, they MUST also be defined in the
604 technology-binding document.
605
606 The naming of binding-specific message elements MUST begin with the
607 name of the technology type, e.g., the binding for IEEE 802.11,
608 provided in this standard, begins with "IEEE 802.11".
609
610
611
612 <span class="grey">Calhoun, et al. Historic [Page 11]</span></pre>
613 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span>
614 <span class="grey"><a href="./rfc5412">RFC 5412</a> Lightweight Access Point Protocol February 2010</span>
615
616
617 <span class="h3"><a class="selflink" id="section-2.2" href="#section-2.2">2.2</a>. LWAPP State Machine Definition</span>
618
619 The following state diagram represents the life cycle of a WTP-AC
620 session:
621
622 /-------------\
623 | v
624 | +------------+
625 | C| Idle |&lt;-----------------------------------\
626 | +------------+&lt;-----------------------\ |
627 | ^ |a ^ | |
628 | | | \----\ | |
629 | | | | +------------+ |
630 | | | | -------| Key Confirm| |
631 | | | | w/ +------------+ |
632 | | | | | ^ |
633 | | | |t V |5 |
634 | | | +-----------+ +------------+ |
635 | / | C| Run | | Key Update | |
636 | / | r+-----------+------&gt;+------------+ |
637 | / | ^ |s u x| |
638 | | v | | | |
639 | | +--------------+ | | v |y
640 | | C| Discovery | q| \---------------&gt;+-------+
641 | | b+--------------+ +-------------+ | Reset |
642 | | |d f| ^ | Configure |-------&gt;+-------+
643 | | | | | +-------------+p ^
644 | |e v | | ^ |
645 | +---------+ v |i 2| |
646 | C| Sulking | +------------+ +--------------+ |
647 | +---------+ C| Join |---&gt;| Join-Confirm | |
648 | g+------------+z +--------------+ |
649 | |h m| 3| |4 |
650 | | | | v |o
651 |\ | | | +------------+
652 \\-----------------/ \--------+----&gt;| Image Data |C
653 \------------------------------------/ +------------+n
654
655 Figure 2: LWAPP State Machine
656
657 The LWAPP state machine, depicted above, is used by both the AC and
658 the WTP. For every state defined, only certain messages are
659 permitted to be sent and received. In all of the LWAPP control
660 messages defined in this document, the state for which each command
661 is valid is specified.
662
663
664
665
666
667
668 <span class="grey">Calhoun, et al. Historic [Page 12]</span></pre>
669 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span>
670 <span class="grey"><a href="./rfc5412">RFC 5412</a> Lightweight Access Point Protocol February 2010</span>
671
672
673 Note that in the state diagram figure above, the 'C' character is
674 used to represent a condition that causes the state to remain the
675 same.
676
677 The following text discusses the various state transitions, and the
678 events that cause them.
679
680 Idle to Discovery (a): This is the initialization state.
681
682 WTP: The WTP enters the Discovery state prior to transmitting the
683 first Discovery Request (see <a href="#section-5.1">Section 5.1</a>). Upon entering
684 this state, the WTP sets the DiscoveryInterval timer (see
685 <a href="#section-12">Section 12</a>). The WTP resets the DiscoveryCount counter to
686 zero (0) (see <a href="#section-13">Section 13</a>). The WTP also clears all
687 information from ACs (e.g., AC Addresses) it may have
688 received during a previous discovery phase.
689
690 AC: The AC does not need to maintain state information for the
691 WTP upon reception of the Discovery Request, but it MUST
692 respond with a Discovery Response (see <a href="#section-5.2">Section 5.2</a>).
693
694 Discovery to Discovery (b): This is the state the WTP uses to
695 determine to which AC it wishes to connect.
696
697 WTP: This event occurs when the DiscoveryInterval timer expires.
698 The WTP transmits a Discovery Request to every AC to which
699 the WTP hasn't received a response. For every transition to
700 this event, the WTP increments the DisoveryCount counter.
701 See <a href="#section-5.1">Section 5.1</a> for more information on how the WTP knows to
702 which ACs it should transmit the Discovery Requests. The
703 WTP restarts the DiscoveryInterval timer.
704
705 AC: This is a noop.
706
707 Discovery to Sulking (d): This state occurs on a WTP when Discovery
708 or connectivity to the AC fails.
709
710 WTP: The WTP enters this state when the DiscoveryInterval timer
711 expires and the DiscoveryCount variable is equal to the
712 MaxDiscoveries variable (see <a href="#section-13">Section 13</a>). Upon entering
713 this state, the WTP will start the SilentInterval timer.
714 While in the Sulking state, all LWAPP messages received are
715 ignored.
716
717 AC: This is a noop.
718
719 Sulking to Idle (e): This state occurs on a WTP when it must restart
720 the discovery phase.
721
722
723
724 <span class="grey">Calhoun, et al. Historic [Page 13]</span></pre>
725 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span>
726 <span class="grey"><a href="./rfc5412">RFC 5412</a> Lightweight Access Point Protocol February 2010</span>
727
728
729 WTP: The WTP enters this state when the SilentInterval timer (see
730 <a href="#section-12">Section 12</a>) expires.
731
732 AC: This is a noop.
733
734 Discovery to Join (f): This state is used by the WTP to confirm its
735 commitment to an AC that it wishes to be provided service.
736
737 WTP: The WTP selects the best AC based on the information it
738 gathered during the discovery phase. It then transmits a
739 Join Request (see <a href="#section-6.1">Section 6.1</a>) to its preferred AC. The WTP
740 starts the WaitJoin timer (see <a href="#section-12">Section 12</a>).
741
742 AC: The AC enters this state for the given WTP upon reception of
743 a Join Request. The AC processes the request and responds
744 with a Join Response.
745
746 Join to Join (g): This state transition occurs during the join
747 phase.
748
749 WTP: The WTP enters this state when the WaitJoin timer expires,
750 and the underlying transport requires LWAPP MTU detection
751 (<a href="#section-3">Section 3</a>).
752
753 AC: This state occurs when the AC receives a retransmission of a
754 Join Request. The WTP processes the request and responds
755 with the Join Response.
756
757 Join to Idle (h): This state is used when the join process has
758 failed.
759
760 WTP: This state transition occurs if the WTP is configured to use
761 pre-shared key (PSK) security and receives a Join Response
762 that includes an invalid PSK-MIC (Message Integrity Check)
763 message element.
764
765 AC: The AC enters this state when it transmits an unsuccessful
766 Join Response.
767
768 Join to Discovery (i): This state is used when the join process has
769 failed.
770
771 WTP: The WTP enters this state when it receives an unsuccessful
772 Join Response. Upon entering this state, the WTP sets the
773 DiscoveryInterval timer (see <a href="#section-12">Section 12</a>). The WTP resets
774 the DiscoveryCount counter to zero (0) (see <a href="#section-13">Section 13</a>).
775 This state transition may also occur if the PSK-MIC (see
776 <a href="#section-6.2.9">Section 6.2.9</a>) message element is invalid.
777
778
779
780 <span class="grey">Calhoun, et al. Historic [Page 14]</span></pre>
781 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span>
782 <span class="grey"><a href="./rfc5412">RFC 5412</a> Lightweight Access Point Protocol February 2010</span>
783
784
785 AC: This state transition is invalid.
786
787 Join to Join-Confirm (z): This state is used to provide key
788 confirmation during the join process.
789
790 WTP: This state is entered when the WTP receives a Join Response.
791 In the event that certificate-based security is utilized,
792 this transition will occur if the Certificate message
793 element is present and valid in the Join Response. For pre-
794 shared key security, the Join Response must include a valid
795 and authenticated PSK-MIC message element. The WTP MUST
796 respond with a Join ACK, which is used to provide key
797 confirmation.
798
799 AC: The AC enters this state when it receives a valid Join ACK.
800 For certificate-based security, the Join ACK MUST include
801 the WNonce message element. For pre-shared key security,
802 the message must include a valid PSK-MIC message element.
803 The AC MUST respond with a Join Confirm message, which
804 includes the Session Key message element.
805
806 Join-Confirm to Idle (3): This state is used when the join process
807 has failed.
808
809 WTP: This state transition occurs when the WTP receives an
810 invalid Join Confirm.
811
812 AC: The AC enters this state when it receives an invalid Join
813 ACK.
814
815 Join-Confirm to Configure (2): This state is used by the WTP and the
816 AC to exchange configuration information.
817
818 WTP: The WTP enters this state when it receives a successful Join
819 Confirm and determines that its version number and the
820 version number advertised by the AC are the same. The WTP
821 transmits the Configure Request (see <a href="#section-7.2">Section 7.2</a>) message to
822 the AC with a snapshot of its current configuration. The
823 WTP also starts the ResponseTimeout timer (see <a href="#section-12">Section 12</a>).
824
825 AC: This state transition occurs when the AC receives the
826 Configure Request from the WTP. The AC must transmit a
827 Configure Response (see <a href="#section-7.3">Section 7.3</a>) to the WTP, and may
828 include specific message elements to override the WTP's
829 configuration.
830
831
832
833
834
835
836 <span class="grey">Calhoun, et al. Historic [Page 15]</span></pre>
837 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-16" ></span>
838 <span class="grey"><a href="./rfc5412">RFC 5412</a> Lightweight Access Point Protocol February 2010</span>
839
840
841 Join-Confirm to Image Data (4): This state is used by the WTP and
842 the AC to download executable firmware.
843
844 WTP: The WTP enters this state when it receives a successful Join
845 Confirm, and determines that its version number and the
846 version number advertised by the AC are different. The WTP
847 transmits the Image Data Request (see <a href="#section-8.1">Section 8.1</a>) message
848 requesting that the AC's latest firmware be initiated.
849
850 AC: This state transition occurs when the AC receives the Image
851 Data Request from the WTP. The AC must transmit an Image
852 Data Response (see <a href="#section-8.2">Section 8.2</a>) to the WTP, which includes a
853 portion of the firmware.
854
855 Image Data to Image Data (n): This state is used by the WTP and the
856 AC during the firmware download phase.
857
858 WTP: The WTP enters this state when it receives an Image Data
859 Response that indicates that the AC has more data to send.
860
861 AC: This state transition occurs when the AC receives the Image
862 Data Request from the WTP while already in this state, and
863 it detects that the firmware download has not completed.
864
865 Image Data to Reset (o): This state is used when the firmware
866 download is completed.
867
868 WTP: The WTP enters this state when it receives an Image Data
869 Response that indicates that the AC has no more data to
870 send, or if the underlying LWAPP transport indicates a link
871 failure. At this point, the WTP reboots itself.
872
873 AC: This state transition occurs when the AC receives the Image
874 Data Request from the WTP while already in this state, and
875 it detects that the firmware download has completed or if
876 the underlying LWAPP transport indicates a link failure.
877 Note that the AC itself does not reset, but it places the
878 specific WTP's context it is communicating with in the reset
879 state: meaning that it clears all state associated with the
880 WTP.
881
882 Configure to Reset (p): This state transition occurs if the
883 configure phase fails.
884
885 WTP: The WTP enters this state when the reliable transport fails
886 to deliver the Configure Request, or if the ResponseTimeout
887 timer (see <a href="#section-12">Section 12</a>) expires.
888
889
890
891
892 <span class="grey">Calhoun, et al. Historic [Page 16]</span></pre>
893 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-17" ></span>
894 <span class="grey"><a href="./rfc5412">RFC 5412</a> Lightweight Access Point Protocol February 2010</span>
895
896
897 AC: This state transition occurs if the AC is unable to transmit
898 the Configure Response to a specific WTP. Note that the AC
899 itself does not reset, but it places the specific WTP's
900 context it is communicating with in the reset state: meaning
901 that it clears all state associated with the WTP.
902
903 Configure to Run (q): This state transition occurs when the WTP and
904 AC enter their normal state of operation.
905
906 WTP: The WTP enters this state when it receives a successful
907 Configure Response from the AC. The WTP initializes the
908 HeartBeat timer (see <a href="#section-12">Section 12</a>), and transmits the Change
909 State Event Request message (see <a href="#section-7.6">Section 7.6</a>).
910
911 AC: This state transition occurs when the AC receives the Change
912 State Event Request (see <a href="#section-7.6">Section 7.6</a>) from the WTP. The AC
913 responds with a Change State Event Response (see <a href="#section-7.7">Section</a>
914 <a href="#section-7.7">7.7</a>) message. The AC must start the Session ID and
915 NeighborDead timers (see <a href="#section-12">Section 12</a>).
916
917 Run to Run (r): This is the normal state of operation.
918
919 WTP: This is the WTP's normal state of operation, and there are
920 many events that cause this to occur:
921
922 Configuration Update: The WTP receives a Configuration Update
923 Request (see <a href="#section-7.4">Section 7.4</a>). The WTP MUST respond with a
924 Configuration Update Response (see <a href="#section-7.5">Section 7.5</a>).
925
926 Change State Event: The WTP receives a Change State Event
927 Response, or determines that it must initiate a Change State
928 Event Request, as a result of a failure or change in the state
929 of a radio.
930
931 Echo Request: The WTP receives an Echo Request message
932 (<a href="#section-6.5">Section 6.5</a>), to which it MUST respond with an Echo Response
933 (see <a href="#section-6.6">Section 6.6</a>).
934
935 Clear Config Indication: The WTP receives a Clear Config
936 Indication message (<a href="#section-7.8">Section 7.8</a>). The WTP MUST reset its
937 configuration back to manufacturer defaults.
938
939 WTP Event: The WTP generates a WTP Event Request to send
940 information to the AC (<a href="#section-8.5">Section 8.5</a>). The WTP receives a WTP
941 Event Response from the AC (<a href="#section-8.6">Section 8.6</a>).
942
943
944
945
946
947
948 <span class="grey">Calhoun, et al. Historic [Page 17]</span></pre>
949 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-18" ></span>
950 <span class="grey"><a href="./rfc5412">RFC 5412</a> Lightweight Access Point Protocol February 2010</span>
951
952
953 Data Transfer: The WTP generates a Data Transfer Request to
954 the AC (<a href="#section-8.7">Section 8.7</a>). The WTP receives a Data Transfer
955 Response from the AC (<a href="#section-8.8">Section 8.8</a>).
956
957 WLAN Config Request: The WTP receives a WLAN Config Request
958 message (<a href="#section-11.8.1">Section 11.8.1</a>), to which it MUST respond with a WLAN
959 Config Response (see <a href="#section-11.8.2">Section 11.8.2</a>).
960
961 Mobile Config Request: The WTP receives an Mobile Config
962 Request message (<a href="#section-9.1">Section 9.1</a>), to which it MUST respond with a
963 Mobile Config Response (see <a href="#section-9.2">Section 9.2</a>).
964
965 AC: This is the AC's normal state of operation, and there are
966 many events that cause this to occur:
967
968 Configuration Update: The AC sends a Configuration Update
969 Request (see <a href="#section-7.4">Section 7.4</a>) to the WTP to update its
970 configuration. The AC receives a Configuration Update Response
971 (see <a href="#section-7.5">Section 7.5</a>) from the WTP.
972
973 Change State Event: The AC receives a Change State Event
974 Request (see <a href="#section-7.6">Section 7.6</a>), to which it MUST respond with the
975 Change State Event Response (see <a href="#section-7.7">Section 7.7</a>).
976
977 Echo: The AC sends an Echo Request message (<a href="#section-6.5">Section 6.5</a>) or
978 receives the associated Echo Response (see <a href="#section-6.6">Section 6.6</a>) from
979 the WTP.
980
981 Clear Config Indication: The AC sends a Clear Config
982 Indication message (<a href="#section-7.8">Section 7.8</a>).
983
984 WLAN Config: The AC sends a WLAN Config Request message
985 (<a href="#section-11.8.1">Section 11.8.1</a>) or receives the associated WLAN Config
986 Response (see <a href="#section-11.8.2">Section 11.8.2</a>) from the WTP.
987
988 Mobile Config: The AC sends a Mobile Config Request message
989 (<a href="#section-9.1">Section 9.1</a>) or receives the associated Mobile Config Response
990 (see <a href="#section-9.2">Section 9.2</a>) from the WTP.
991
992 Data Transfer: The AC receives a Data Transfer Request from
993 the AC (see <a href="#section-8.7">Section 8.7</a>) and MUST generate the associated Data
994 Transfer Response message (see <a href="#section-8.8">Section 8.8</a>).
995
996 WTP Event: The AC receives a WTP Event Request from the AC
997 (see <a href="#section-8.5">Section 8.5</a>) and MUST generate the associated WTP Event
998 Response message (see <a href="#section-8.6">Section 8.6</a>).
999
1000
1001
1002
1003
1004 <span class="grey">Calhoun, et al. Historic [Page 18]</span></pre>
1005 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-19" ></span>
1006 <span class="grey"><a href="./rfc5412">RFC 5412</a> Lightweight Access Point Protocol February 2010</span>
1007
1008
1009 Run to Reset (s): This event occurs when the AC wishes for the WTP
1010 to reboot.
1011
1012 WTP: The WTP enters this state when it receives a Reset Request
1013 (see <a href="#section-8.3">Section 8.3</a>). It must respond with a Reset Response
1014 (see <a href="#section-8.4">Section 8.4</a>), and once the reliable transport
1015 acknowledgement has been received, it must reboot itself.
1016
1017 AC: This state transition occurs either through some
1018 administrative action, or via some internal event on the AC
1019 that causes it to request that the WTP disconnect. Note
1020 that the AC itself does not reset, but it places the
1021 specific WTPs context it is communicating with in the reset
1022 state.
1023
1024 Run to Idle (t): This event occurs when an error occurs in the
1025 communication between the WTP and the AC.
1026
1027 WTP: The WTP enters this state when the underlying reliable
1028 transport is unable to transmit a message within the
1029 RetransmitInterval timer (see <a href="#section-12">Section 12</a>), and the maximum
1030 number of RetransmitCount counter has reached the
1031 MaxRetransmit variable (see <a href="#section-13">Section 13</a>).
1032
1033 AC: The AC enters this state when the underlying reliable
1034 transport in unable to transmit a message within the
1035 RetransmitInterval timer (see <a href="#section-12">Section 12</a>), and the maximum
1036 number of RetransmitCount counter has reached the
1037 MaxRetransmit variable (see <a href="#section-13">Section 13</a>).
1038
1039 Run to Key Update (u): This event occurs when the WTP and the AC are
1040 to exchange new keying material, with which it must use to protect
1041 all future messages.
1042
1043 WTP: This state transition occurs when the KeyLifetime timer
1044 expires (see <a href="#section-12">Section 12</a>).
1045
1046 AC: The WTP enters this state when it receives a Key Update
1047 Request (see <a href="#section-6.7">Section 6.7</a>).
1048
1049 Key Update to Key Confirm (w): This event occurs during the rekey
1050 phase and is used to complete the loop.
1051
1052 WTP: This state transition occurs when the WTP receives the Key
1053 Update Response. The WTP MUST only accept the message if it
1054 is authentic. The WTP responds to this response with a Key
1055 Update ACK.
1056
1057
1058
1059
1060 <span class="grey">Calhoun, et al. Historic [Page 19]</span></pre>
1061 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-20" ></span>
1062 <span class="grey"><a href="./rfc5412">RFC 5412</a> Lightweight Access Point Protocol February 2010</span>
1063
1064
1065 AC: The AC enters this state when it receives an authenticated
1066 Key Update ACK message.
1067
1068 Key Confirm to Run (5): This event occurs when the rekey exchange
1069 phase is completed.
1070
1071 WTP: This state transition occurs when the WTP receives the Key
1072 Update Confirm. The newly derived encryption key and
1073 Initialization Vector (IV) must be plumbed into the crypto
1074 module after validating the message's authentication.
1075
1076 AC: The AC enters this state when it transmits the Key Update
1077 Confirm message. The newly derived encryption key and IV
1078 must be plumbed into the crypto module after transmitting a
1079 Key Update Confirm message.
1080
1081 Key Update to Reset (x): This event occurs when the key exchange
1082 phase times out.
1083
1084 WTP: This state transition occurs when the WTP does not receive a
1085 Key Update Response from the AC.
1086
1087 AC: The AC enters this state when it is unable to process a Key
1088 Update Request.
1089
1090 Reset to Idle (y): This event occurs when the state machine is
1091 restarted.
1092
1093 WTP: The WTP reboots itself. After rebooting, the WTP will start
1094 its LWAPP state machine in the Idle state.
1095
1096 AC: The AC clears out any state associated with the WTP. The AC
1097 generally does this as a result of the reliable link layer
1098 timing out.
1099
1100 <span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. LWAPP Transport Layers</span>
1101
1102 The LWAPP protocol can operate at Layer 2 or 3. For Layer 2 support,
1103 the LWAPP messages are carried in a native Ethernet frame. As such,
1104 the protocol is not routable and depends upon Layer 2 connectivity
1105 between the WTP and the AC. Layer 3 support is provided by
1106 encapsulating the LWAPP messages within UDP.
1107
1108
1109
1110
1111
1112
1113
1114
1115
1116 <span class="grey">Calhoun, et al. Historic [Page 20]</span></pre>
1117 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-21" ></span>
1118 <span class="grey"><a href="./rfc5412">RFC 5412</a> Lightweight Access Point Protocol February 2010</span>
1119
1120
1121 <span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>. LWAPP Transport Header</span>
1122
1123 All LWAPP protocol packets are encapsulated using a common header
1124 format, regardless of the transport used to carry the frames.
1125 However, certain flags are not applicable for a given transport, and
1126 it is therefore necessary to refer to the specific transport section
1127 in order to determine which flags are valid.
1128
1129 0 1 2 3
1130 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
1131 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1132 |VER| RID |C|F|L| Frag ID | Length |
1133 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1134 | Status/WLANs | Payload... |
1135 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1136
1137 <span class="h4"><a class="selflink" id="section-3.1.1" href="#section-3.1.1">3.1.1</a>. VER Field</span>
1138
1139 A 2-bit field that contains the version of LWAPP used in this packet.
1140 The value for this document is 0.
1141
1142 <span class="h4"><a class="selflink" id="section-3.1.2" href="#section-3.1.2">3.1.2</a>. RID Field</span>
1143
1144 A 3-bit field that contains the Radio ID number for this packet.
1145 WTPs with multiple radios but a single MAC address use this field to
1146 indicate which radio is associated with the packet.
1147
1148 <span class="h4"><a class="selflink" id="section-3.1.3" href="#section-3.1.3">3.1.3</a>. C Bit</span>
1149
1150 The control message 'C' bit indicates whether this packet carries a
1151 data or control message. When this bit is zero (0), the packet
1152 carries an LWAPP data message in the payload (see <a href="#section-4.1">Section 4.1</a>). When
1153 this bit is one (1), the packet carries an LWAPP control message as
1154 defined in <a href="#section-4.2">Section 4.2</a> for consumption by the addressed destination.
1155
1156 <span class="h4"><a class="selflink" id="section-3.1.4" href="#section-3.1.4">3.1.4</a>. F Bit</span>
1157
1158 The Fragment 'F' bit indicates whether this packet is a fragment.
1159 When this bit is one (1), the packet is a fragment and MUST be
1160 combined with the other corresponding fragments to reassemble the
1161 complete information exchanged between the WTP and AC.
1162
1163
1164
1165
1166
1167
1168
1169
1170
1171
1172 <span class="grey">Calhoun, et al. Historic [Page 21]</span></pre>
1173 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-22" ></span>
1174 <span class="grey"><a href="./rfc5412">RFC 5412</a> Lightweight Access Point Protocol February 2010</span>
1175
1176
1177 <span class="h4"><a class="selflink" id="section-3.1.5" href="#section-3.1.5">3.1.5</a>. L Bit</span>
1178
1179 The Not Last 'L' bit is valid only if the 'F' bit is set and
1180 indicates whether the packet contains the last fragment of a
1181 fragmented exchange between the WTP and AC. When this bit is 1, the
1182 packet is not the last fragment. When this bit is 0, the packet is
1183 the last fragment.
1184
1185 <span class="h4"><a class="selflink" id="section-3.1.6" href="#section-3.1.6">3.1.6</a>. Fragment ID</span>
1186
1187 An 8-bit field whose value is assigned to each group of fragments
1188 making up a complete set. The Fragment ID space is managed
1189 individually for every WTP/AC pair. The value of Fragment ID is
1190 incremented with each new set of fragments. The Fragment ID wraps to
1191 zero after the maximum value has been used to identify a set of
1192 fragments. LWAPP only supports up to 2 fragments per frame.
1193
1194 <span class="h4"><a class="selflink" id="section-3.1.7" href="#section-3.1.7">3.1.7</a>. Length</span>
1195
1196 The 16-bit length field contains the number of bytes in the Payload.
1197 The field is encoded as an unsigned number. If the LWAPP packet is
1198 encrypted, the length field includes the Advanced Encryption Standard
1199 Counter with CBC-MAC (AES-CCM) MIC (see <a href="#section-10.2">Section 10.2</a> for more
1200 information).
1201
1202 <span class="h4"><a class="selflink" id="section-3.1.8" href="#section-3.1.8">3.1.8</a>. Status and WLANS</span>
1203
1204 The interpretation of this 16-bit field is binding-specific. Refer
1205 to the transport portion of the binding for a wireless technology for
1206 the specification.
1207
1208 <span class="h4"><a class="selflink" id="section-3.1.9" href="#section-3.1.9">3.1.9</a>. Payload</span>
1209
1210 This field contains the header for an LWAPP data message or LWAPP
1211 control message, followed by the data associated with that message.
1212
1213 <span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a>. Using IEEE 802.3 MAC as LWAPP Transport</span>
1214
1215 This section describes how the LWAPP protocol is provided over native
1216 Ethernet frames. An LWAPP packet is formed from the MAC frame
1217 header, followed by the LWAPP message header. The following figure
1218 provides an example of the frame formats used when LWAPP is used over
1219 the IEEE 802.3 transport.
1220
1221
1222
1223
1224
1225
1226
1227
1228 <span class="grey">Calhoun, et al. Historic [Page 22]</span></pre>
1229 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-23" ></span>
1230 <span class="grey"><a href="./rfc5412">RFC 5412</a> Lightweight Access Point Protocol February 2010</span>
1231
1232
1233 Layer 2 LWAPP Data Frame
1234 +-----------------------------------------------------------+
1235 | MAC Header | LWAPP Header [C=0] | Forwarded Data ... |
1236 +-----------------------------------------------------------+
1237
1238 Layer 2 LWAPP Control Frame
1239 +---------------------------------------------------+
1240 | MAC Header | LWAPP Header [C=1] | Control Message |
1241 +---------------------------------------------------+
1242 | Message Elements ... |
1243 +----------------------+
1244
1245 <span class="h4"><a class="selflink" id="section-3.2.1" href="#section-3.2.1">3.2.1</a>. Framing</span>
1246
1247 Source Address
1248
1249 A MAC address belonging to the interface from which this message is
1250 sent. If multiple source addresses are configured on an interface,
1251 then the one chosen is implementation-dependent.
1252
1253 Destination Address
1254
1255 A MAC address belonging to the interface to which this message is to
1256 be sent. This destination address MAY be either an individual
1257 address or a multicast address, if more than one destination
1258 interface is intended.
1259
1260 Ethertype
1261
1262 The Ethertype field is set to 0x88bb.
1263
1264 <span class="h4"><a class="selflink" id="section-3.2.2" href="#section-3.2.2">3.2.2</a>. AC Discovery</span>
1265
1266 When run over IEEE 802.3, LWAPP messages are distributed to a
1267 specific MAC-level broadcast domain. The AC discovery mechanism used
1268 with this transport is for a WTP to transmit a Discovery Request
1269 message to a broadcast destination MAC address. The ACs will receive
1270 this message and reply based on their policy.
1271
1272 <span class="h4"><a class="selflink" id="section-3.2.3" href="#section-3.2.3">3.2.3</a>. LWAPP Message Header Format over IEEE 802.3 MAC Transport</span>
1273
1274 All of the fields described in <a href="#section-3.1">Section 3.1</a> are used when LWAPP uses
1275 the IEEE 802.3 MAC transport.
1276
1277
1278
1279
1280
1281
1282
1283
1284 <span class="grey">Calhoun, et al. Historic [Page 23]</span></pre>
1285 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-24" ></span>
1286 <span class="grey"><a href="./rfc5412">RFC 5412</a> Lightweight Access Point Protocol February 2010</span>
1287
1288
1289 <span class="h4"><a class="selflink" id="section-3.2.4" href="#section-3.2.4">3.2.4</a>. Fragmentation/Reassembly</span>
1290
1291 Fragmentation at the MAC layer is managed using the F, L, and Frag ID
1292 fields of the LWAPP message header. The LWAPP protocol only allows a
1293 single packet to be fragmented into 2, which is sufficient for a
1294 frame that exceeds MTU due to LWAPP encapsulation. When used with
1295 Layer 2 (Ethernet) transport, both fragments MUST include the LWAPP
1296 header.
1297
1298 <span class="h4"><a class="selflink" id="section-3.2.5" href="#section-3.2.5">3.2.5</a>. Multiplexing</span>
1299
1300 LWAPP control messages and data messages are distinguished by the 'C'
1301 bit in the LWAPP message header.
1302
1303 <span class="h3"><a class="selflink" id="section-3.3" href="#section-3.3">3.3</a>. Using IP/UDP as LWAPP Transport</span>
1304
1305 This section defines how LWAPP makes use of IP/UDP transport between
1306 the WTP and the AC. When this transport is used, the MAC layer is
1307 controlled by the IP stack, and there are therefore no special MAC-
1308 layer requirements. The following figure provides an example of the
1309 frame formats used when LWAPP is used over the IP/UDP transport. IP
1310 stacks can be either IPv4 or IPv6.
1311
1312 Layer 3 LWAPP Data Frame
1313 +--------------------------------------------+
1314 | MAC Header | IP | UDP | LWAPP Header [C=0] |
1315 +--------------------------------------------+
1316 |Forwarded Data ... |
1317 +-------------------+
1318
1319 Layer 3 LWAPP Control Frame
1320 +--------------------------------------------+
1321 | MAC Header | IP | UDP | LWAPP Header [C=1] |
1322 +--------------------------------------------+
1323 | Control Message | Message Elements ... |
1324 +-----------------+----------------------+
1325
1326 <span class="h4"><a class="selflink" id="section-3.3.1" href="#section-3.3.1">3.3.1</a>. Framing</span>
1327
1328 Communication between the WTP and AC is established according to the
1329 standard UDP client/server model. The connection is initiated by the
1330 WTP (client) to the well-known UDP port of the AC (server) used for
1331 control messages. This UDP port number of the AC is 12222 for LWAPP
1332 data and 12223 for LWAPP control frames.
1333
1334
1335
1336
1337
1338
1339
1340 <span class="grey">Calhoun, et al. Historic [Page 24]</span></pre>
1341 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-25" ></span>
1342 <span class="grey"><a href="./rfc5412">RFC 5412</a> Lightweight Access Point Protocol February 2010</span>
1343
1344
1345 <span class="h4"><a class="selflink" id="section-3.3.2" href="#section-3.3.2">3.3.2</a>. AC Discovery</span>
1346
1347 When LWAPP is run over routed IP networks, the WTP and the AC do not
1348 need to reside in the same IP subnet (broadcast domain). However, in
1349 the event the peers reside on separate subnets, there must exist a
1350 mechanism for the WTP to discover the AC.
1351
1352 As the WTP attempts to establish communication with the AC, it sends
1353 the Discovery Request message and receives the corresponding response
1354 message from the AC. The WTP must send the Discovery Request message
1355 to either the limited broadcast IP address (255.255.255.255), a well
1356 known multicast address, or the unicast IP address of the AC. Upon
1357 receipt of the message, the AC issues a Discovery Response message to
1358 the unicast IP address of the WTP, regardless of whether a Discovery
1359 Request was sent as a broadcast, multicast, or unicast message.
1360
1361 Whether the WTP uses a limited IP broadcast, multicast or unicast IP
1362 address is implementation-dependent.
1363
1364 In order for a WTP to transmit a Discovery Request to a unicast
1365 address, the WTP must first obtain the IP address of the AC. Any
1366 static configuration of an AC's IP address on the WTP non-volatile
1367 storage is implementation-dependent. However, additional dynamic
1368 schemes are possible: for example:
1369
1370 DHCP: A comma-delimited, ASCII-encoded list of AC IP addresses is
1371 embedded inside a DHCP vendor-specific option 43 extension.
1372 An example of the actual format of the vendor-specific payload
1373 for IPv4 is of the form "10.1.1.1, 10.1.1.2".
1374
1375 DNS: The DNS name "LWAPP-AC-Address" MAY be resolvable to one or
1376 more AC addresses.
1377
1378 <span class="h4"><a class="selflink" id="section-3.3.3" href="#section-3.3.3">3.3.3</a>. LWAPP Message Header Format over IP/UDP Transport</span>
1379
1380 All of the fields described in <a href="#section-3.1">Section 3.1</a> are used when LWAPP uses
1381 the IPv4/UDP or IPv6/UDP transport, with the following exceptions.
1382
1383 <span class="h5"><a class="selflink" id="section-3.3.3.1" href="#section-3.3.3.1">3.3.3.1</a>. F Bit</span>
1384
1385 This flag field is not used with this transport, and MUST be set to
1386 zero.
1387
1388 <span class="h5"><a class="selflink" id="section-3.3.3.2" href="#section-3.3.3.2">3.3.3.2</a>. L Bit</span>
1389
1390 This flag field is not used with this transport, and MUST be set to
1391 zero.
1392
1393
1394
1395
1396 <span class="grey">Calhoun, et al. Historic [Page 25]</span></pre>
1397 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-26" ></span>
1398 <span class="grey"><a href="./rfc5412">RFC 5412</a> Lightweight Access Point Protocol February 2010</span>
1399
1400
1401 <span class="h5"><a class="selflink" id="section-3.3.3.3" href="#section-3.3.3.3">3.3.3.3</a>. Frag ID</span>
1402
1403 This field is not used with this transport, and MUST be set to zero.
1404
1405 <span class="h4"><a class="selflink" id="section-3.3.4" href="#section-3.3.4">3.3.4</a>. Fragmentation/Reassembly for IPv4</span>
1406
1407 When LWAPP is implemented at L3, the transport layer uses IP
1408 fragmentation to fragment and reassemble LWAPP messages that are
1409 longer than the MTU size used by either the WTP or AC. The details
1410 of IP fragmentation are covered in [<a href="#ref-8" title="&quot;IP datagram reassembly algorithms&quot;">8</a>]. When used with the IP
1411 transport, only the first fragment would include the LWAPP header.
1412
1413 <span class="h4"><a class="selflink" id="section-3.3.5" href="#section-3.3.5">3.3.5</a>. Fragmentation/Reassembly for IPv6</span>
1414
1415 IPv6 does MTU discovery so fragmentation and re-assembly is not
1416 necessary for UDP packets.
1417
1418 <span class="h4"><a class="selflink" id="section-3.3.6" href="#section-3.3.6">3.3.6</a>. Multiplexing</span>
1419
1420 LWAPP messages convey control information between WTP and AC, as well
1421 as binding specific data frames or binding specific management
1422 frames. As such, LWAPP messages need to be multiplexed in the
1423 transport sub-layer and be delivered to the proper software entities
1424 in the endpoints of the protocol. However, the 'C' bit is still used
1425 to differentiate between data and control frames.
1426
1427 In case of Layer 3 connection, multiplexing is achieved by use of
1428 different UDP ports for control and data packets (see <a href="#section-3.3.1">Section 3.3.1</a>).
1429
1430 As part of the Join procedure, the WTP and AC may negotiate different
1431 IP Addresses for data or control messages. The IP address returned
1432 in the AP Manager Control IP Address message element is used to
1433 inform the WTP with the IP address to which it must send all control
1434 frames. The AP Manager Data IP Address message element MAY be
1435 present only if the AC has a different IP address that the WTP is to
1436 use to send its data LWAPP frames.
1437
1438 In the event the WTP and AC are separated by a NAT, with the WTP
1439 using private IP address space, it is the responsibility of the NAT
1440 to manage appropriate UDP port mapping.
1441
1442 <span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. LWAPP Packet Definitions</span>
1443
1444 This section contains the packet types and format. The LWAPP
1445 protocol is designed to be transport-agnostic by specifying packet
1446 formats for both MAC frames and IP packets. An LWAPP packet consists
1447 of an LWAPP Transport Layer packet header followed by an LWAPP
1448 message.
1449
1450
1451
1452 <span class="grey">Calhoun, et al. Historic [Page 26]</span></pre>
1453 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-27" ></span>
1454 <span class="grey"><a href="./rfc5412">RFC 5412</a> Lightweight Access Point Protocol February 2010</span>
1455
1456
1457 Transport details can be found in <a href="#section-3">Section 3</a>.
1458
1459 <span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a>. LWAPP Data Messages</span>
1460
1461 An LWAPP data message is a forwarded wireless frame. When forwarding
1462 wireless frames, the sender simply encapsulates the wireless frame in
1463 an LWAPP data packet, using the appropriate transport rules defined
1464 in <a href="#section-3">Section 3</a>.
1465
1466 In the event that the encapsulated frame would exceed the transport
1467 layer's MTU, the sender is responsible for the fragmentation of the
1468 frame, as specified in the transport-specific section of <a href="#section-3">Section 3</a>.
1469
1470 The actual format of the encapsulated LWAPP data frame is subject to
1471 the rules defined under the specific wireless technology binding.
1472
1473 <span class="h3"><a class="selflink" id="section-4.2" href="#section-4.2">4.2</a>. LWAPP Control Messages Overview</span>
1474
1475 The LWAPP Control protocol provides a control channel between the WTP
1476 and the AC. The control channel is the series of control messages
1477 between the WTP and AC, associated with a session ID and key.
1478 Control messages are divided into the following distinct message
1479 types:
1480
1481 Discovery: LWAPP Discovery messages are used to identify potential
1482 ACs, their load and capabilities.
1483
1484 Control Channel Management: Messages that fall within this
1485 classification are used for the discovery of ACs by the WTPs as
1486 well as the establishment and maintenance of an LWAPP control
1487 channel.
1488
1489 WTP Configuration: The WTP Configuration messages are used by the AC
1490 to push a specific configuration to the WTPs with which it has a
1491 control channel. Messages that deal with the retrieval of
1492 statistics from the WTP also fall in this category.
1493
1494 Mobile Session Management: Mobile Session Management messages are
1495 used by the AC to push specific mobile policies to the WTP.
1496
1497 Firmware Management: Messages in this category are used by the AC to
1498 push a new firmware image down to the WTP.
1499
1500 Control Channel, WTP Configuration, and Mobile Session Management
1501 MUST be implemented. Firmware Management MAY be implemented.
1502
1503 In addition, technology-specific bindings may introduce new control
1504 channel commands that depart from the above list.
1505
1506
1507
1508 <span class="grey">Calhoun, et al. Historic [Page 27]</span></pre>
1509 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-28" ></span>
1510 <span class="grey"><a href="./rfc5412">RFC 5412</a> Lightweight Access Point Protocol February 2010</span>
1511
1512
1513 <span class="h4"><a class="selflink" id="section-4.2.1" href="#section-4.2.1">4.2.1</a>. Control Message Format</span>
1514
1515 All LWAPP control messages are sent encapsulated within the LWAPP
1516 header (see <a href="#section-3.1">Section 3.1</a>). Immediately following the header is the
1517 LWAPP control header, which has the following format:
1518
1519 0 1 2 3
1520 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
1521 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1522 | Message Type | Seq Num | Msg Element Length |
1523 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1524 | Session ID |
1525 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1526 | Msg Element [0..N] |
1527 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1528
1529 <span class="h5"><a class="selflink" id="section-4.2.1.1" href="#section-4.2.1.1">4.2.1.1</a>. Message Type</span>
1530
1531 The Message Type field identifies the function of the LWAPP control
1532 message. The valid values for a Message Type are the following:
1533
1534 Description Value
1535 Discovery Request 1
1536 Discovery Response 2
1537 Join Request 3
1538 Join Response 4
1539 Join ACK 5
1540 Join Confirm 6
1541 Unused 7-9
1542 Configure Request 10
1543 Configure Response 11
1544 Configuration Update Request 12
1545 Configuration Update Response 13
1546 WTP Event Request 14
1547 WTP Event Response 15
1548 Change State Event Request 16
1549 Change State Event Response 17
1550 Unused 18-21
1551 Echo Request 22
1552 Echo Response 23
1553 Image Data Request 24
1554 Image Data Response 25
1555 Reset Request 26
1556 Reset Response 27
1557 Unused 28-29
1558 Key Update Request 30
1559 Key Update Response 31
1560 Primary Discovery Request 32
1561
1562
1563
1564 <span class="grey">Calhoun, et al. Historic [Page 28]</span></pre>
1565 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-29" ></span>
1566 <span class="grey"><a href="./rfc5412">RFC 5412</a> Lightweight Access Point Protocol February 2010</span>
1567
1568
1569 Primary Discovery Response 33
1570 Data Transfer Request 34
1571 Data Transfer Response 35
1572 Clear Config Indication 36
1573 WLAN Config Request 37
1574 WLAN Config Response 38
1575 Mobile Config Request 39
1576 Mobile Config Response 40
1577
1578 <span class="h5"><a class="selflink" id="section-4.2.1.2" href="#section-4.2.1.2">4.2.1.2</a>. Sequence Number</span>
1579
1580 The Sequence Number field is an identifier value to match request/
1581 response packet exchanges. When an LWAPP packet with a request
1582 message type is received, the value of the Sequence Number field is
1583 copied into the corresponding response packet.
1584
1585 When an LWAPP control frame is sent, its internal sequence number
1586 counter is monotonically incremented, ensuring that no two requests
1587 pending have the same sequence number. This field will wrap back to
1588 zero.
1589
1590 <span class="h5"><a class="selflink" id="section-4.2.1.3" href="#section-4.2.1.3">4.2.1.3</a>. Message Element Length</span>
1591
1592 The length field indicates the number of bytes following the Session
1593 ID field. If the LWAPP packet is encrypted, the length field
1594 includes the AES-CCM MIC (see <a href="#section-10.2">Section 10.2</a> for more information).
1595
1596 <span class="h5"><a class="selflink" id="section-4.2.1.4" href="#section-4.2.1.4">4.2.1.4</a>. Session ID</span>
1597
1598 The Session ID is a 32-bit unsigned integer that is used to identify
1599 the security context for encrypted exchanges between the WTP and the
1600 AC. Note that a Session ID is a random value that MUST be unique
1601 between a given AC and any of the WTPs with which it may be
1602 communicating.
1603
1604 <span class="h5"><a class="selflink" id="section-4.2.1.5" href="#section-4.2.1.5">4.2.1.5</a>. Message Element [0..N]</span>
1605
1606 The message element(s) carry the information pertinent to each of the
1607 control message types. Every control message in this specification
1608 specifies which message elements are permitted.
1609
1610 <span class="h4"><a class="selflink" id="section-4.2.2" href="#section-4.2.2">4.2.2</a>. Message Element Format</span>
1611
1612 The message element is used to carry information pertinent to a
1613 control message. Every message element is identified by the Type
1614 field, whose numbering space is managed via IANA (see <a href="#section-16">Section 16</a>).
1615 The total length of the message elements is indicated in the Message
1616 Element Length field.
1617
1618
1619
1620 <span class="grey">Calhoun, et al. Historic [Page 29]</span></pre>
1621 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-30" ></span>
1622 <span class="grey"><a href="./rfc5412">RFC 5412</a> Lightweight Access Point Protocol February 2010</span>
1623
1624
1625 All of the message element definitions in this document use a diagram
1626 similar to the one below in order to depict their formats. Note that
1627 in order to simplify this specification, these diagrams do not
1628 include the header fields (Type and Length). However, in each
1629 message element description, the header's field values will be
1630 defined.
1631
1632 Note that additional message elements may be defined in separate IETF
1633 documents.
1634
1635 The format of a message element uses the TLV format shown here:
1636
1637 0 1 2 3
1638 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
1639 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1640 | Type | Length | Value ... |
1641 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1642
1643 where Type (8 bits) identifies the character of the information
1644 carried in the Value field and Length (16 bits) indicates the number
1645 of bytes in the Value field.
1646
1647 <span class="h5"><a class="selflink" id="section-4.2.2.1" href="#section-4.2.2.1">4.2.2.1</a>. Generic Message Elements</span>
1648
1649 This section includes message elements that are not bound to a
1650 specific control message.
1651
1652 <span class="h6"><a class="selflink" id="section-4.2.2.1.1" href="#section-4.2.2.1.1">4.2.2.1.1</a>. Vendor Specific</span>
1653
1654 The Vendor-Specific Payload is used to communicate vendor-specific
1655 information between the WTP and the AC. The value contains the
1656 following format:
1657
1658 0 1 2 3
1659 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
1660 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1661 | Vendor Identifier |
1662 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1663 | Element ID | Value... |
1664 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1665
1666 Type: 104 for Vendor Specific
1667
1668 Length: &gt;= 7
1669
1670 Vendor Identifier: A 32-bit value containing the IANA-assigned "SMI
1671 Network Management Private Enterprise Codes" [<a href="#ref-13" title="&quot;Assigned Numbers: RFC 1700 is Replaced by an On-line Database&quot;">13</a>].
1672
1673
1674
1675
1676 <span class="grey">Calhoun, et al. Historic [Page 30]</span></pre>
1677 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-31" ></span>
1678 <span class="grey"><a href="./rfc5412">RFC 5412</a> Lightweight Access Point Protocol February 2010</span>
1679
1680
1681 Element ID: A 16-bit Element Identifier that is managed by the
1682 vendor.
1683
1684 Value: The value associated with the vendor-specific element.
1685
1686 <span class="h4"><a class="selflink" id="section-4.2.3" href="#section-4.2.3">4.2.3</a>. Quality of Service</span>
1687
1688 It is recommended that LWAPP control messages be sent by both the AC
1689 and the WTP with an appropriate Quality-of-Service precedence value,
1690 ensuring that congestion in the network minimizes occurrences of
1691 LWAPP control channel disconnects. Therefore, a Quality-of-Service-
1692 enabled LWAPP device should use:
1693
1694 802.1P: The precedence value of 7 SHOULD be used.
1695
1696 DSCP: The Differentiated Services Code Point (DSCP) tag value of 46
1697 SHOULD be used.
1698
1699 <span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. LWAPP Discovery Operations</span>
1700
1701 The Discovery messages are used by a WTP to determine which ACs are
1702 available to provide service, as well as the capabilities and load of
1703 the ACs.
1704
1705 <span class="h3"><a class="selflink" id="section-5.1" href="#section-5.1">5.1</a>. Discovery Request</span>
1706
1707 The Discovery Request is used by the WTP to automatically discover
1708 potential ACs available in the network. A WTP must transmit this
1709 command even if it has a statically configured AC, as it is a
1710 required step in the LWAPP state machine.
1711
1712 Discovery Requests MUST be sent by a WTP in the Discover state after
1713 waiting for a random delay less of than MaxDiscoveryInterval, after a
1714 WTP first comes up or is (re)initialized. A WTP MUST send no more
1715 than a maximum of MaxDiscoveries discoveries, waiting for a random
1716 delay less than MaxDiscoveryInterval between each successive
1717 discovery.
1718
1719 This is to prevent an explosion of WTP Discoveries. An example of
1720 this occurring would be when many WTPs are powered on at the same
1721 time.
1722
1723 Discovery Requests MUST be sent by a WTP when no Echo Responses are
1724 received for NeighborDeadInterval and the WTP returns to the Idle
1725 state. Discovery Requests are sent after NeighborDeadInterval, they
1726 MUST be sent after waiting for a random delay less than
1727
1728
1729
1730
1731
1732 <span class="grey">Calhoun, et al. Historic [Page 31]</span></pre>
1733 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-32" ></span>
1734 <span class="grey"><a href="./rfc5412">RFC 5412</a> Lightweight Access Point Protocol February 2010</span>
1735
1736
1737 MaxDiscoveryInterval. A WTP MAY send up to a maximum of
1738 MaxDiscoveries discoveries, waiting for a random delay less than
1739 MaxDiscoveryInterval between each successive discovery.
1740
1741 If a Discovery Response is not received after sending the maximum
1742 number of Discovery Requests, the WTP enters the Sulking state and
1743 MUST wait for an interval equal to SilentInterval before sending
1744 further Discovery Requests.
1745
1746 The Discovery Request message may be sent as a unicast, broadcast, or
1747 multicast message.
1748
1749 Upon receiving a Discovery Request, the AC will respond with a
1750 Discovery Response sent to the address in the source address of the
1751 received Discovery Request.
1752
1753 The following subsections define the message elements that MUST be
1754 included in this LWAPP operation.
1755
1756 <span class="h4"><a class="selflink" id="section-5.1.1" href="#section-5.1.1">5.1.1</a>. Discovery Type</span>
1757
1758 The Discovery message element is used to configure a WTP to operate
1759 in a specific mode.
1760
1761 0
1762 0 1 2 3 4 5 6 7
1763 +-+-+-+-+-+-+-+-+
1764 | Discovery Type|
1765 +-+-+-+-+-+-+-+-+
1766
1767 Type: 58 for Discovery Type
1768
1769 Length: 1
1770
1771 Discovery Type: An 8-bit value indicating how the AC was
1772 discovered. The following values are supported:
1773
1774 0 - Broadcast
1775
1776 1 - Configured
1777
1778
1779
1780
1781
1782
1783
1784
1785
1786
1787
1788 <span class="grey">Calhoun, et al. Historic [Page 32]</span></pre>
1789 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-33" ></span>
1790 <span class="grey"><a href="./rfc5412">RFC 5412</a> Lightweight Access Point Protocol February 2010</span>
1791
1792
1793 <span class="h4"><a class="selflink" id="section-5.1.2" href="#section-5.1.2">5.1.2</a>. WTP Descriptor</span>
1794
1795 The WTP Descriptor message element is used by the WTP to communicate
1796 its current hardware/firmware configuration. The value contains the
1797 following fields.
1798
1799 0 1 2 3
1800 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
1801 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1802 | Hardware Version |
1803 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1804 | Software Version |
1805 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1806 | Boot Version |
1807 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1808 | Max Radios | Radios in use | Encryption Capabilities |
1809 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1810
1811 Type: 3 for WTP Descriptor
1812
1813 Length: 16
1814
1815 Hardware Version: A 32-bit integer representing the WTP's hardware
1816 version number.
1817
1818 Software Version: A 32-bit integer representing the WTP's Firmware
1819 version number.
1820
1821 Boot Version: A 32-bit integer representing the WTP's boot loader's
1822 version number.
1823
1824 Max Radios: An 8-bit value representing the number of radios (where
1825 each radio is identified via the RID field) supported by the WTP.
1826
1827 Radios in Use: An 8-bit value representing the number of radios
1828 present in the WTP.
1829
1830 Encryption Capabilities: This 16-bit field is used by the WTP to
1831 communicate its capabilities to the AC. Since most WTPs support
1832 link-layer encryption, the AC may make use of these services.
1833 There are binding-dependent encryption capabilites. A WTP that
1834 does not have any encryption capabilities would set this field to
1835 zero (0). Refer to the specific binding for the specification.
1836
1837
1838
1839
1840
1841
1842
1843
1844 <span class="grey">Calhoun, et al. Historic [Page 33]</span></pre>
1845 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-34" ></span>
1846 <span class="grey"><a href="./rfc5412">RFC 5412</a> Lightweight Access Point Protocol February 2010</span>
1847
1848
1849 <span class="h4"><a class="selflink" id="section-5.1.3" href="#section-5.1.3">5.1.3</a>. WTP Radio Information</span>
1850
1851 The WTP Radio Information message element is used to communicate the
1852 radio information in a specific slot. The Discovery Request MUST
1853 include one such message element per radio in the WTP. The Radio-
1854 Type field is used by the AC in order to determine which technology-
1855 specific binding is to be used with the WTP.
1856
1857 The value contains two fields, as shown:
1858
1859 0 1
1860 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5
1861 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1862 | Radio ID | Radio Type |
1863 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1864
1865 Type: 4 for WTP Radio Information
1866
1867 Length: 2
1868
1869 Radio ID: The Radio Identifier, typically refers to some interface
1870 index on the WTP.
1871
1872 Radio Type: The type of radio present. The following values are
1873 supported:
1874
1875 1 - 802.11bg: An 802.11bg radio.
1876
1877 2 - 802.11a: An 802.11a radio.
1878
1879 3 - 802.16: An 802.16 radio.
1880
1881 4 - Ultra Wideband: A UWB radio.
1882
1883 7 - all: Used to specify all radios in the WTP.
1884
1885 <span class="h3"><a class="selflink" id="section-5.2" href="#section-5.2">5.2</a>. Discovery Response</span>
1886
1887 The Discovery Response is a mechanism by which an AC advertises its
1888 services to requesting WTPs.
1889
1890 Discovery Responses are sent by an AC after receiving a Discovery
1891 Request.
1892
1893
1894
1895
1896
1897
1898
1899
1900 <span class="grey">Calhoun, et al. Historic [Page 34]</span></pre>
1901 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-35" ></span>
1902 <span class="grey"><a href="./rfc5412">RFC 5412</a> Lightweight Access Point Protocol February 2010</span>
1903
1904
1905 When a WTP receives a Discovery Response, it MUST wait for an
1906 interval not less than DiscoveryInterval for receipt of additional
1907 Discovery Responses. After the DiscoveryInterval elapses, the WTP
1908 enters the Joining state and will select one of the ACs that sent a
1909 Discovery Response and send a Join Request to that AC.
1910
1911 The following subsections define the message elements that MUST be
1912 included in this LWAPP operation.
1913
1914 <span class="h4"><a class="selflink" id="section-5.2.1" href="#section-5.2.1">5.2.1</a>. AC Address</span>
1915
1916 The AC Address message element is used to communicate the identity of
1917 the AC. The value contains two fields, as shown:
1918
1919 0 1 2 3
1920 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
1921 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1922 | Reserved | MAC Address |
1923 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1924 | MAC Address |
1925 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1926
1927 Type: 2 for AC Address
1928
1929 Length: 7
1930
1931 Reserved: MUST be set to zero
1932
1933 MAC Address: The MAC address of the AC
1934
1935 <span class="h4"><a class="selflink" id="section-5.2.2" href="#section-5.2.2">5.2.2</a>. AC Descriptor</span>
1936
1937 The AC Descriptor message element is used by the AC to communicate
1938 its current state. The value contains the following fields:
1939
1940 0 1 2 3
1941 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
1942 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1943 | Reserved | Hardware Version ... |
1944 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1945 | HW Ver | Software Version ... |
1946 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1947 | SW Ver | Stations | Limit |
1948 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1949 | Limit | Radios | Max Radio |
1950 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1951 | Max Radio | Security |
1952 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1953
1954
1955
1956 <span class="grey">Calhoun, et al. Historic [Page 35]</span></pre>
1957 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-36" ></span>
1958 <span class="grey"><a href="./rfc5412">RFC 5412</a> Lightweight Access Point Protocol February 2010</span>
1959
1960
1961 Type: 6 for AC Descriptor
1962
1963 Length: 17
1964
1965 Reserved: MUST be set to zero
1966
1967 Hardware Version: A 32-bit integer representing the AC's hardware
1968 version number.
1969
1970 Software Version: A 32-bit integer representing the AC's Firmware
1971 version number.
1972
1973 Stations: A 16-bit integer representing the number of mobile
1974 stations currently associated with the AC.
1975
1976 Limit: A 16-bit integer representing the maximum number of stations
1977 supported by the AC.
1978
1979 Radios: A 16-bit integer representing the number of WTPs currently
1980 attached to the AC.
1981
1982 Max Radio: A 16-bit integer representing the maximum number of WTPs
1983 supported by the AC.
1984
1985 Security: An 8-bit bitmask specifying the security schemes
1986 supported by the AC. The following values are supported (see
1987 <a href="#section-10">Section 10</a>):
1988
1989 1 - X.509 Certificate-Based
1990
1991 2 - Pre-Shared Secret
1992
1993 <span class="h4"><a class="selflink" id="section-5.2.3" href="#section-5.2.3">5.2.3</a>. AC Name</span>
1994
1995 The AC Name message element contains an ASCII representation of the
1996 AC's identity. The value is a variable-length byte string. The
1997 string is NOT zero terminated.
1998
1999 0
2000 0 1 2 3 4 5 6 7
2001 +-+-+-+-+-+-+-+-+
2002 | Name ...
2003 +-+-+-+-+-+-+-+-+
2004
2005 Type: 31 for AC Name
2006
2007 Length: &gt; 0
2008
2009
2010
2011
2012 <span class="grey">Calhoun, et al. Historic [Page 36]</span></pre>
2013 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-37" ></span>
2014 <span class="grey"><a href="./rfc5412">RFC 5412</a> Lightweight Access Point Protocol February 2010</span>
2015
2016
2017 Name: A variable-length ASCII string containing the AC's name.
2018
2019 <span class="h4"><a class="selflink" id="section-5.2.4" href="#section-5.2.4">5.2.4</a>. WTP Manager Control IPv4 Address</span>
2020
2021 The WTP Manager Control IPv4 Address message element is sent by the
2022 AC to the WTP during the discovery process and is used by the AC to
2023 provide the interfaces available on the AC, and their current load.
2024 This message element is useful for the WTP to perform load balancing
2025 across multiple interfaces.
2026
2027 0 1 2 3
2028 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
2029 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
2030 | IP Address |
2031 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
2032 | WTP Count |
2033 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
2034
2035 Type: 99 for WTP Manager Control IPv4 Address
2036
2037 Length: 6
2038
2039 IP Address: The IP address of an interface.
2040
2041 WTP Count: The number of WTPs currently connected to the interface.
2042
2043 <span class="h4"><a class="selflink" id="section-5.2.5" href="#section-5.2.5">5.2.5</a>. WTP Manager Control IPv6 Address</span>
2044
2045 The WTP Manager Control IPv6 Address message element is sent by the
2046 AC to the WTP during the discovery process and is used by the AC to
2047 provide the interfaces available on the AC, and their current load.
2048 This message element is useful for the WTP to perform load balancing
2049 across multiple interfaces.
2050
2051 0 1 2 3
2052 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
2053 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
2054 | IP Address |
2055 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
2056 | IP Address |
2057 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
2058 | IP Address |
2059 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
2060 | IP Address |
2061 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
2062 | WTP Count |
2063 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
2064
2065
2066
2067
2068 <span class="grey">Calhoun, et al. Historic [Page 37]</span></pre>
2069 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-38" ></span>
2070 <span class="grey"><a href="./rfc5412">RFC 5412</a> Lightweight Access Point Protocol February 2010</span>
2071
2072
2073 Type: 137 for WTP Manager Control IPv6 Address
2074
2075 Length: 6
2076
2077 IP Address: The IP address of an interface.
2078
2079 WTP Count: The number of WTPs currently connected to the interface.
2080
2081 <span class="h3"><a class="selflink" id="section-5.3" href="#section-5.3">5.3</a>. Primary Discovery Request</span>
2082
2083 The Primary Discovery Request is sent by the WTP in order to
2084 determine whether its preferred (or primary) AC is available.
2085
2086 Primary Discovery Requests are sent by a WTP when it has a primary AC
2087 configured, and is connected to another AC. This generally occurs as
2088 a result of a failover, and is used by the WTP as a means to discover
2089 when its primary AC becomes available. As a consequence, this
2090 message is only sent by a WTP when it is in the Run state.
2091
2092 The frequency of the Primary Discovery Requests should be no more
2093 often than the sending of the Echo Request message.
2094
2095 Upon receiving a Discovery Request, the AC will respond with a
2096 Primary Discovery Response sent to the address in the source address
2097 of the received Primary Discovery Request.
2098
2099 The following subsections define the message elements that MUST be
2100 included in this LWAPP operation.
2101
2102 <span class="h4"><a class="selflink" id="section-5.3.1" href="#section-5.3.1">5.3.1</a>. Discovery Type</span>
2103
2104 The Discovery Type message element is defined in <a href="#section-5.1.1">Section 5.1.1</a>.
2105
2106 <span class="h4"><a class="selflink" id="section-5.3.2" href="#section-5.3.2">5.3.2</a>. WTP Descriptor</span>
2107
2108 The WTP Descriptor message element is defined in <a href="#section-5.1.2">Section 5.1.2</a>.
2109
2110 <span class="h4"><a class="selflink" id="section-5.3.3" href="#section-5.3.3">5.3.3</a>. WTP Radio Information</span>
2111
2112 A WTP Radio Information message element must be present for every
2113 radio in the WTP. This message element is defined in <a href="#section-5.1.3">Section 5.1.3</a>.
2114
2115 <span class="h3"><a class="selflink" id="section-5.4" href="#section-5.4">5.4</a>. Primary Discovery Response</span>
2116
2117 The Primary Discovery Response is a mechanism by which an AC
2118 advertises its availability and services to requesting WTPs that are
2119 configured to have the AC as its primary AC.
2120
2121
2122
2123
2124 <span class="grey">Calhoun, et al. Historic [Page 38]</span></pre>
2125 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-39" ></span>
2126 <span class="grey"><a href="./rfc5412">RFC 5412</a> Lightweight Access Point Protocol February 2010</span>
2127
2128
2129 Primary Discovery Responses are sent by an AC after receiving a
2130 Primary Discovery Request.
2131
2132 When a WTP receives a Primary Discovery Response, it may opt to
2133 establish an LWAPP connection to its primary AC, based on the
2134 configuration of the WTP Fallback Status message element on the WTP.
2135
2136 The following subsections define the message elements that MUST be
2137 included in this LWAPP operation.
2138
2139 <span class="h4"><a class="selflink" id="section-5.4.1" href="#section-5.4.1">5.4.1</a>. AC Descriptor</span>
2140
2141 The Discovery Type message element is defined in <a href="#section-5.2.2">Section 5.2.2</a>.
2142
2143 <span class="h4"><a class="selflink" id="section-5.4.2" href="#section-5.4.2">5.4.2</a>. AC Name</span>
2144
2145 The AC Name message element is defined in <a href="#section-5.2.3">Section 5.2.3</a>.
2146
2147 <span class="h4"><a class="selflink" id="section-5.4.3" href="#section-5.4.3">5.4.3</a>. WTP Manager Control IPv4 Address</span>
2148
2149 A WTP Radio Information message element MAY be present for every
2150 radio in the WTP that is reachable via IPv4. This message element is
2151 defined in <a href="#section-5.2.4">Section 5.2.4</a>.
2152
2153 <span class="h4"><a class="selflink" id="section-5.4.4" href="#section-5.4.4">5.4.4</a>. WTP Manager Control IPv6 Address</span>
2154
2155 A WTP Radio Information message element must be present for every
2156 radio in the WTP that is reachable via IPv6. This message element is
2157 defined in <a href="#section-5.2.5">Section 5.2.5</a>.
2158
2159 <span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Control Channel Management</span>
2160
2161 The Control Channel Management messages are used by the WTP and AC to
2162 create and maintain a channel of communication on which various other
2163 commands may be transmitted, such as configuration, firmware update,
2164 etc.
2165
2166 <span class="h3"><a class="selflink" id="section-6.1" href="#section-6.1">6.1</a>. Join Request</span>
2167
2168 The Join Request is used by a WTP to inform an AC that it wishes to
2169 provide services through it.
2170
2171 Join Requests are sent by a WTP in the Joining state after receiving
2172 one or more Discovery Responses. The Join Request is also used as an
2173 MTU discovery mechanism by the WTP. The WTP issues a Join Request
2174 with a Test message element, bringing the total size of the message
2175 to exceed MTU.
2176
2177
2178
2179
2180 <span class="grey">Calhoun, et al. Historic [Page 39]</span></pre>
2181 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-40" ></span>
2182 <span class="grey"><a href="./rfc5412">RFC 5412</a> Lightweight Access Point Protocol February 2010</span>
2183
2184
2185 If the transport used does not provide MTU path discovery, the
2186 initial Join Request is padded with the Test message element to 1596
2187 bytes. If a Join Response is received, the WTP can forward frames
2188 without requiring any fragmentation. If no Join Response is
2189 received, it issues a second Join Request padded with the Test
2190 payload to a total of 1500 bytes. The WTP continues to cycle from
2191 large (1596) to small (1500) packets until a Join Response has been
2192 received, or until both packets' sizes have been retransmitted 3
2193 times. If the Join Response is not received after the maximum number
2194 of retransmissions, the WTP MUST abandon the AC and restart the
2195 discovery phase.
2196
2197 When an AC receives a Join Request, it will respond with a Join
2198 Response. If the certificate-based security mechanism is used, the
2199 AC validates the certificate found in the request. If valid, the AC
2200 generates a session key that will be used to secure the control
2201 frames it exchanges with the WTP. When the AC issues the Join
2202 Response, the AC creates a context for the session with the WTP.
2203
2204 If the pre-shared session key security mechanism is used, the AC
2205 saves the WTP's nonce, found in the WNonce message element, and
2206 creates its own nonce, which it includes in the ANonce message
2207 element. Finally, the AC creates the PSK-MIC, which is computed
2208 using a key that is derived from the PSK.
2209
2210 A Join Request that includes both a WNonce and a Certificate message
2211 element MUST be considered invalid.
2212
2213 Details on the key generation are found in <a href="#section-10">Section 10</a>.
2214
2215 The following subsections define the message elements that MUST be
2216 included in this LWAPP operation.
2217
2218 <span class="h4"><a class="selflink" id="section-6.1.1" href="#section-6.1.1">6.1.1</a>. WTP Descriptor</span>
2219
2220 The WTP Descriptor message element is defined in <a href="#section-5.1.2">Section 5.1.2</a>.
2221
2222 <span class="h4"><a class="selflink" id="section-6.1.2" href="#section-6.1.2">6.1.2</a>. AC Address</span>
2223
2224 The AC Address message element is defined in <a href="#section-5.2.1">Section 5.2.1</a>.
2225
2226 <span class="h4"><a class="selflink" id="section-6.1.3" href="#section-6.1.3">6.1.3</a>. WTP Name</span>
2227
2228 The WTP Name message element value is a variable-length byte string.
2229 The string is NOT zero terminated.
2230
2231
2232
2233
2234
2235
2236 <span class="grey">Calhoun, et al. Historic [Page 40]</span></pre>
2237 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-41" ></span>
2238 <span class="grey"><a href="./rfc5412">RFC 5412</a> Lightweight Access Point Protocol February 2010</span>
2239
2240
2241 0
2242 0 1 2 3 4 5 6 7
2243 +-+-+-+-+-+-+-+-+
2244 | Name ...
2245 +-+-+-+-+-+-+-+-+
2246
2247 Type: 5 for WTP Name
2248
2249 Length: &gt; 0
2250
2251 Name: A non-zero-terminated string containing the WTP's name.
2252
2253 <span class="h4"><a class="selflink" id="section-6.1.4" href="#section-6.1.4">6.1.4</a>. Location Data</span>
2254
2255 The Location Data message element is a variable-length byte string
2256 containing user-defined location information (e.g., "Next to
2257 Fridge"). The string is NOT zero terminated.
2258
2259 0
2260 0 1 2 3 4 5 6 7
2261 +-+-+-+-+-+-+-+-+
2262 | Location ...
2263 +-+-+-+-+-+-+-+-+
2264
2265 Type: 35 for Location Data
2266
2267 Length: &gt; 0
2268
2269 Location: A non-zero-terminated string containing the WTP's
2270 location.
2271
2272 <span class="h4"><a class="selflink" id="section-6.1.5" href="#section-6.1.5">6.1.5</a>. WTP Radio Information</span>
2273
2274 A WTP Radio Information message element must be present for every
2275 radio in the WTP. This message element is defined in <a href="#section-5.1.3">Section 5.1.3</a>.
2276
2277 <span class="h4"><a class="selflink" id="section-6.1.6" href="#section-6.1.6">6.1.6</a>. Certificate</span>
2278
2279 The Certificate message element value is a byte string containing a
2280 DER-encoded x.509v3 certificate. This message element is only
2281 included if the LWAPP security type used between the WTP and the AC
2282 makes use of certificates (see <a href="#section-10">Section 10</a> for more information).
2283
2284 0
2285 0 1 2 3 4 5 6 7
2286 +-+-+-+-+-+-+-+-+
2287 | Certificate...
2288 +-+-+-+-+-+-+-+-+
2289
2290
2291
2292 <span class="grey">Calhoun, et al. Historic [Page 41]</span></pre>
2293 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-42" ></span>
2294 <span class="grey"><a href="./rfc5412">RFC 5412</a> Lightweight Access Point Protocol February 2010</span>
2295
2296
2297 Type: 44 for Certificate
2298
2299 Length: &gt; 0
2300
2301 Certificate: A non-zero-terminated string containing the device's
2302 certificate.
2303
2304 <span class="h4"><a class="selflink" id="section-6.1.7" href="#section-6.1.7">6.1.7</a>. Session ID</span>
2305
2306 The Session ID message element value contains a randomly generated
2307 [<a href="#ref-4" title="&quot;Randomness Requirements for Security&quot;">4</a>] unsigned 32-bit integer.
2308
2309 0 1 2 3
2310 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
2311 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
2312 | Session ID |
2313 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
2314
2315 Type: 45 for Session ID
2316
2317 Length: 4
2318
2319 Session ID: 32-bit random session identifier.
2320
2321 <span class="h4"><a class="selflink" id="section-6.1.8" href="#section-6.1.8">6.1.8</a>. Test</span>
2322
2323 The Test message element is used as padding to perform MTU discovery,
2324 and it MAY contain any value, of any length.
2325
2326 0
2327 0 1 2 3 4 5 6 7
2328 +-+-+-+-+-+-+-+-+
2329 | Padding ...
2330 +-+-+-+-+-+-+-+-+
2331
2332 Type: 18 for Test
2333
2334 Length: &gt; 0
2335
2336 Padding: A variable-length pad.
2337
2338 <span class="h4"><a class="selflink" id="section-6.1.9" href="#section-6.1.9">6.1.9</a>. XNonce</span>
2339
2340 The XNonce is used by the WTP to communicate its random nonce during
2341 the join or rekey phase. See <a href="#section-10">Section 10</a> for more information.
2342
2343
2344
2345
2346
2347
2348 <span class="grey">Calhoun, et al. Historic [Page 42]</span></pre>
2349 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-43" ></span>
2350 <span class="grey"><a href="./rfc5412">RFC 5412</a> Lightweight Access Point Protocol February 2010</span>
2351
2352
2353 0 1 2 3
2354 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
2355 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
2356 | Nonce |
2357 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
2358 | Nonce |
2359 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
2360 | Nonce |
2361 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
2362 | Nonce |
2363 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
2364
2365 Type: 111 for XNonce
2366
2367 Length: 16
2368
2369 Nonce: 1 16-octet random nonce.
2370
2371 <span class="h3"><a class="selflink" id="section-6.2" href="#section-6.2">6.2</a>. Join Response</span>
2372
2373 The Join Response is sent by the AC to indicate to a WTP whether it
2374 is capable and willing to provide service to it.
2375
2376 Join Responses are sent by the AC after receiving a Join Request.
2377 Once the Join Response has been sent, the Heartbeat timer is
2378 initiated for the session to EchoInterval. Expiration of the timer
2379 will result in deletion of the AC-WTP session. The timer is
2380 refreshed upon receipt of the Echo Request.
2381
2382 If the security method used is certificate-based, when a WTP receives
2383 a Join Response, it enters the Joined state and initiates either a
2384 Configure Request or Image Data to the AC to which it is now joined.
2385 Upon entering the Joined state, the WTP begins timing an interval
2386 equal to NeighborDeadInterval. Expiration of the timer will result
2387 in the transmission of the Echo Request.
2388
2389 If the security method used is pre-shared-secret-based, when a WTP
2390 receives a Join Response that includes a valid PSK-MIC message
2391 element, it responds with a Join ACK that also MUST include a locally
2392 computed PSK-MIC message element.
2393
2394 The following subsections define the message elements that MUST be
2395 included in this LWAPP operation.
2396
2397
2398
2399
2400
2401
2402
2403
2404 <span class="grey">Calhoun, et al. Historic [Page 43]</span></pre>
2405 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-44" ></span>
2406 <span class="grey"><a href="./rfc5412">RFC 5412</a> Lightweight Access Point Protocol February 2010</span>
2407
2408
2409 <span class="h4"><a class="selflink" id="section-6.2.1" href="#section-6.2.1">6.2.1</a>. Result Code</span>
2410
2411 The Result Code message element value is a 32-bit integer value,
2412 indicating the result of the request operation corresponding to the
2413 sequence number in the message. The Result Code is included in a
2414 successful Join Response.
2415
2416 0 1 2 3
2417 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
2418 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
2419 | Result Code |
2420 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
2421
2422 Type: 2 for Result Code
2423
2424 Length: 4
2425
2426 Result Code: The following values are defined:
2427
2428 0 Success
2429
2430 1 Failure (AC List message element MUST be present)
2431
2432 <span class="h4"><a class="selflink" id="section-6.2.2" href="#section-6.2.2">6.2.2</a>. Status</span>
2433
2434 The Status message element is sent by the AC to the WTP in a non-
2435 successful Join Response message. This message element is used to
2436 indicate the reason for the failure and should only be accompanied
2437 with a Result Code message element that indicates a failure.
2438
2439 0
2440 0 1 2 3 4 5 6 7
2441 +-+-+-+-+-+-+-+-+
2442 | Status |
2443 +-+-+-+-+-+-+-+-+
2444
2445 Type: 60 for Status
2446
2447 Length: 1
2448
2449 Status: The Status field indicates the reason for an LWAPP failure.
2450 The following values are supported:
2451
2452
2453
2454
2455
2456
2457
2458
2459
2460 <span class="grey">Calhoun, et al. Historic [Page 44]</span></pre>
2461 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-45" ></span>
2462 <span class="grey"><a href="./rfc5412">RFC 5412</a> Lightweight Access Point Protocol February 2010</span>
2463
2464
2465 1 - Reserved - do not use
2466
2467 2 - Resource Depletion
2468
2469 3 - Unknown Source
2470
2471 4 - Incorrect Data
2472
2473 <span class="h4"><a class="selflink" id="section-6.2.3" href="#section-6.2.3">6.2.3</a>. Certificate</span>
2474
2475 The Certificate message element is defined in <a href="#section-6.1.6">Section 6.1.6</a>. Note
2476 this message element is only included if the WTP and the AC make use
2477 of certificate-based security as defined in <a href="#section-10">Section 10</a>.
2478
2479 <span class="h4"><a class="selflink" id="section-6.2.4" href="#section-6.2.4">6.2.4</a>. WTP Manager Data IPv4 Address</span>
2480
2481 The WTP Manager Data IPv4 Address message element is optionally sent
2482 by the AC to the WTP during the join phase. If present, the IP
2483 Address contained in this message element is the address the WTP is
2484 to use when sending any of its LWAPP data frames.
2485
2486 Note that this message element is only valid when LWAPP uses the
2487 IP/UDP Layer 3 transport.
2488
2489 0 1 2 3
2490 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
2491 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
2492 | IP Address |
2493 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
2494
2495 Type: 138 for WTP Manager Data IPv4 Address
2496
2497 Length: 4
2498
2499 IP Address: The IP address of an interface.
2500
2501 <span class="h4"><a class="selflink" id="section-6.2.5" href="#section-6.2.5">6.2.5</a>. WTP Manager Data IPv6 Address</span>
2502
2503 The WTP Manager Data IPv6 Address message element is optionally sent
2504 by the AC to the WTP during the join phase. If present, the IP
2505 Address contained in this message element is the address the WTP is
2506 to use when sending any of its LWAPP data frames.
2507
2508 Note that this message element is only valid when LWAPP uses the
2509 IP/UDP Layer 3 transport.
2510
2511
2512
2513
2514
2515
2516 <span class="grey">Calhoun, et al. Historic [Page 45]</span></pre>
2517 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-46" ></span>
2518 <span class="grey"><a href="./rfc5412">RFC 5412</a> Lightweight Access Point Protocol February 2010</span>
2519
2520
2521 0 1 2 3
2522 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
2523 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
2524 | IP Address |
2525 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
2526 | IP Address |
2527 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
2528 | IP Address |
2529 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
2530 | IP Address |
2531 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
2532
2533 Type: 139 for WTP Manager Data IPv6 Address
2534
2535 Length: 4
2536
2537 IP Address: The IP address of an interface.
2538
2539 <span class="h4"><a class="selflink" id="section-6.2.6" href="#section-6.2.6">6.2.6</a>. AC IPv4 List</span>
2540
2541 The AC List message element is used to configure a WTP with the
2542 latest list of ACs in a cluster. This message element MUST be
2543 included if the Join Response returns a failure indicating that the
2544 AC cannot handle the WTP at this time, allowing the WTP to find an
2545 alternate AC to which to connect.
2546
2547 0 1 2 3
2548 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
2549 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
2550 | AC IP Address[] |
2551 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
2552
2553 Type: 59 for AC List
2554
2555 Length: &gt;= 4
2556
2557 AC IP Address: An array of 32-bit integers containing an AC's IPv4
2558 Address.
2559
2560 <span class="h4"><a class="selflink" id="section-6.2.7" href="#section-6.2.7">6.2.7</a>. AC IPv6 List</span>
2561
2562 The AC List message element is used to configure a WTP with the
2563 latest list of ACs in a cluster. This message element MUST be
2564 included if the Join Response returns a failure indicating that the
2565 AC cannot handle the WTP at this time, allowing the WTP to find an
2566 alternate AC to which to connect.
2567
2568
2569
2570
2571
2572 <span class="grey">Calhoun, et al. Historic [Page 46]</span></pre>
2573 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-47" ></span>
2574 <span class="grey"><a href="./rfc5412">RFC 5412</a> Lightweight Access Point Protocol February 2010</span>
2575
2576
2577 0 1 2 3
2578 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
2579 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
2580 | AC IP Address[] |
2581 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
2582 | AC IP Address[] |
2583 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
2584 | AC IP Address[] |
2585 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
2586 | AC IP Address[] |
2587 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
2588
2589 Type: 141 for AC List
2590
2591 Length: &gt;= 4
2592
2593 AC IP Address: An array of 32-bit integers containing an AC's IPv6
2594 Address.
2595
2596 <span class="h4"><a class="selflink" id="section-6.2.8" href="#section-6.2.8">6.2.8</a>. ANonce</span>
2597
2598 The ANonce message element is sent by an AC during the join or rekey
2599 phase. The contents of the ANonce are encrypted as described in
2600 <a href="#section-10">Section 10</a> for more information.
2601
2602 0 1 2 3
2603 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
2604 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
2605 | Nonce |
2606 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
2607 | Nonce |
2608 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
2609 | Nonce |
2610 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
2611 | Nonce |
2612 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
2613
2614 Type: 108 for ANonce
2615
2616 Length: 16
2617
2618 Nonce: An encrypted, 16-octet random nonce.
2619
2620
2621
2622
2623
2624
2625
2626
2627
2628 <span class="grey">Calhoun, et al. Historic [Page 47]</span></pre>
2629 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-48" ></span>
2630 <span class="grey"><a href="./rfc5412">RFC 5412</a> Lightweight Access Point Protocol February 2010</span>
2631
2632
2633 <span class="h4"><a class="selflink" id="section-6.2.9" href="#section-6.2.9">6.2.9</a>. PSK-MIC</span>
2634
2635 The PSK-MIC message element includes a message integrity check, whose
2636 purpose is to provide confirmation to the peer that the sender has
2637 the proper session key. This message element is only included if the
2638 security method used between the WTP and the AC is the pre-shared
2639 secret mechanism. See <a href="#section-10">Section 10</a> for more information.
2640
2641 When present, the PSK-MIC message element MUST be the last message
2642 element in the message. The MIC is computed over the complete LWAPP
2643 packet, from the LWAPP control header as defined in <a href="#section-4.2.1">Section 4.2.1</a> to
2644 the end of the packet (which MUST be this PSK-MIC message element).
2645 The MIC field in this message element and the Sequence Number field
2646 in the LWAPP control header MUST be set to zeroes prior to computing
2647 the MIC. The length field in the LWAPP control header must already
2648 include this message element prior to computing the MIC.
2649
2650 0 1 2 3
2651 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
2652 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
2653 | SPI | MIC ...
2654 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
2655
2656 Type: 109 for PSK-MIC
2657
2658 Length: &gt; 1
2659
2660 SPI: The Security Parameter Index (SPI) field specifies the
2661 cryptographic algorithm used to create the message integrity
2662 check. The following values are supported:
2663
2664 0 - Unused
2665
2666 1 - HMAC-SHA-1 (<a href="./rfc2104">RFC 2104</a> [<a href="#ref-15" title="&quot;HMAC: Keyed-Hashing for Message Authentication&quot;">15</a>])
2667
2668 MIC: A 20-octet Message Integrity Check.
2669
2670 <span class="h3"><a class="selflink" id="section-6.3" href="#section-6.3">6.3</a>. Join ACK</span>
2671
2672 The Join ACK message is sent by the WTP upon receiving a Join
2673 Response, which has a valid PSK-MIC message element, as a means of
2674 providing key confirmation to the AC. The Join ACK is only used in
2675 the case where the WTP makes use of the pre-shared key LWAPP mode
2676 (see <a href="#section-10">Section 10</a> for more information).
2677
2678 Note that the AC should never receive this message unless the
2679 security method used between the WTP and the AC is pre-shared-secret-
2680 based.
2681
2682
2683
2684 <span class="grey">Calhoun, et al. Historic [Page 48]</span></pre>
2685 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-49" ></span>
2686 <span class="grey"><a href="./rfc5412">RFC 5412</a> Lightweight Access Point Protocol February 2010</span>
2687
2688
2689 The following subsections define the message elements that MUST be
2690 included in this LWAPP operation.
2691
2692 <span class="h4"><a class="selflink" id="section-6.3.1" href="#section-6.3.1">6.3.1</a>. Session ID</span>
2693
2694 The Session ID message element is defined in <a href="#section-6.1.7">Section 6.1.7</a>.
2695
2696 <span class="h4"><a class="selflink" id="section-6.3.2" href="#section-6.3.2">6.3.2</a>. WNonce</span>
2697
2698 The WNonce message element is sent by a WTP during the join or rekey
2699 phase. The contents of the ANonce are encrypted as described in
2700 <a href="#section-10">Section 10</a> for more information.
2701
2702 0 1 2 3
2703 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
2704 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
2705 | Nonce |
2706 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
2707 | Nonce |
2708 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
2709 | Nonce |
2710 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
2711 | Nonce |
2712 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
2713
2714 Type: 107 for WNonce
2715
2716 Length: 16
2717
2718 Nonce: An encrypted, 16-octet random nonce.
2719
2720 <span class="h4"><a class="selflink" id="section-6.3.3" href="#section-6.3.3">6.3.3</a>. PSK-MIC</span>
2721
2722 The PSK-MIC message element is defined in <a href="#section-6.2.9">Section 6.2.9</a>.
2723
2724 <span class="h3"><a class="selflink" id="section-6.4" href="#section-6.4">6.4</a>. Join Confirm</span>
2725
2726 The Join Confirm message is sent by the AC upon receiving a Join ACK,
2727 which has a valid PSK-MIC message element, as a means of providing
2728 key confirmation to the WTP. The Join Confirm is only used in the
2729 case where the WTP makes use of the pre-shared key LWAPP mode (see
2730 <a href="#section-10">Section 10</a> for more information).
2731
2732 If the security method used is pre-shared-key-based, when a WTP
2733 receives a Join Confirm, it enters the Joined state and initiates
2734 either a Configure Request or Image Data to the AC to which it is now
2735
2736
2737
2738
2739
2740 <span class="grey">Calhoun, et al. Historic [Page 49]</span></pre>
2741 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-50" ></span>
2742 <span class="grey"><a href="./rfc5412">RFC 5412</a> Lightweight Access Point Protocol February 2010</span>
2743
2744
2745 joined. Upon entering the Joined state, the WTP begins timing an
2746 interval equal to NeighborDeadInterval. Expiration of the timer will
2747 result in the transmission of the Echo Request.
2748
2749 This message is never received, or sent, when the security type used
2750 between the WTP and the AC is certificated-based.
2751
2752 The following subsections define the message elements that MUST be
2753 included in this LWAPP operation.
2754
2755 <span class="h4"><a class="selflink" id="section-6.4.1" href="#section-6.4.1">6.4.1</a>. Session ID</span>
2756
2757 The Session ID message element is defined in <a href="#section-6.1.7">Section 6.1.7</a>.
2758
2759 <span class="h4"><a class="selflink" id="section-6.4.2" href="#section-6.4.2">6.4.2</a>. PSK-MIC</span>
2760
2761 The PSK-MIC message element is defined in <a href="#section-6.2.9">Section 6.2.9</a>.
2762
2763 <span class="h3"><a class="selflink" id="section-6.5" href="#section-6.5">6.5</a>. Echo Request</span>
2764
2765 The Echo Request message is a keepalive mechanism for the LWAPP
2766 control message.
2767
2768 Echo Requests are sent periodically by a WTP in the Run state (see
2769 Figure 2) to determine the state of the connection between the WTP
2770 and the AC. The Echo Request is sent by the WTP when the Heartbeat
2771 timer expires, and it MUST start its NeighborDeadInterval timer.
2772
2773 The Echo Request carries no message elements.
2774
2775 When an AC receives an Echo Request, it responds with an Echo
2776 Response.
2777
2778 <span class="h3"><a class="selflink" id="section-6.6" href="#section-6.6">6.6</a>. Echo Response</span>
2779
2780 The Echo Response acknowledges the Echo Request, and is only accepted
2781 while in the Run state (see Figure 2).
2782
2783 Echo Responses are sent by an AC after receiving an Echo Request.
2784 After transmitting the Echo Response, the AC should reset its
2785 Heartbeat timer to expire in the value configured for EchoInterval.
2786 If another Echo request is not received by the AC when the timer
2787 expires, the AC SHOULD consider the WTP to no longer be reachable.
2788
2789 The Echo Response carries no message elements.
2790
2791
2792
2793
2794
2795
2796 <span class="grey">Calhoun, et al. Historic [Page 50]</span></pre>
2797 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-51" ></span>
2798 <span class="grey"><a href="./rfc5412">RFC 5412</a> Lightweight Access Point Protocol February 2010</span>
2799
2800
2801 When a WTP receives an Echo Response it stops the
2802 NeighborDeadInterval timer, and starts the Heartbeat timer to
2803 EchoInterval.
2804
2805 If the NeighborDeadInterval timer expires prior to receiving an Echo
2806 Response, the WTP enters the Idle state.
2807
2808 <span class="h3"><a class="selflink" id="section-6.7" href="#section-6.7">6.7</a>. Key Update Request</span>
2809
2810 The Key Update Request is used by the WTP to initiate the rekeying
2811 phase. This message is sent by a WTP when in the Run state and MUST
2812 include a new unique Session Identifier. This message MUST also
2813 include a unique nonce in the XNonce message element, which is used
2814 to protect against replay attacks (see <a href="#section-10">Section 10</a>).
2815
2816 The following subsections define the message elements that MUST be
2817 included in this LWAPP operation.
2818
2819 <span class="h4"><a class="selflink" id="section-6.7.1" href="#section-6.7.1">6.7.1</a>. Session ID</span>
2820
2821 The Session ID message element is defined in <a href="#section-6.1.7">Section 6.1.7</a>.
2822
2823 <span class="h4"><a class="selflink" id="section-6.7.2" href="#section-6.7.2">6.7.2</a>. XNonce</span>
2824
2825 The XNonce message element is defined in <a href="#section-6.1.9">Section 6.1.9</a>.
2826
2827 <span class="h3"><a class="selflink" id="section-6.8" href="#section-6.8">6.8</a>. Key Update Response</span>
2828
2829 The Key Update Response is sent by the AC in response to the request
2830 message, and includes an encrypted ANonce, which is used to derive
2831 new session keys. This message MUST include a Session Identifier
2832 message element, whose value MUST be identical to the one found in
2833 the Key Update Request.
2834
2835 The AC MUST include a PSK-MIC message element, which provides message
2836 integrity over the whole message.
2837
2838 The following subsections define the message elements that MUST be
2839 included in this LWAPP operation.
2840
2841 <span class="h4"><a class="selflink" id="section-6.8.1" href="#section-6.8.1">6.8.1</a>. Session ID</span>
2842
2843 The Session ID message element is defined in <a href="#section-6.1.7">Section 6.1.7</a>.
2844
2845 <span class="h4"><a class="selflink" id="section-6.8.2" href="#section-6.8.2">6.8.2</a>. ANonce</span>
2846
2847 The ANonce message element is defined in <a href="#section-6.2.8">Section 6.2.8</a>.
2848
2849
2850
2851
2852 <span class="grey">Calhoun, et al. Historic [Page 51]</span></pre>
2853 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-52" ></span>
2854 <span class="grey"><a href="./rfc5412">RFC 5412</a> Lightweight Access Point Protocol February 2010</span>
2855
2856
2857 <span class="h4"><a class="selflink" id="section-6.8.3" href="#section-6.8.3">6.8.3</a>. PSK-MIC</span>
2858
2859 The PSK-MIC message element is defined in <a href="#section-6.2.9">Section 6.2.9</a>.
2860
2861 <span class="h3"><a class="selflink" id="section-6.9" href="#section-6.9">6.9</a>. Key Update ACK</span>
2862
2863 The Key Update ACK is sent by the WTP and includes an encrypted
2864 version of the WTP's nonce, which is used in the key derivation
2865 process. The session keys derived are then used as new LWAPP control
2866 message encryption keys (see <a href="#section-10">Section 10</a>).
2867
2868 The WTP MUST include a PSK-MIC message element, which provides
2869 message integrity over the whole message.
2870
2871 The following subsections define the message elements that MUST be
2872 included in this LWAPP operation.
2873
2874 <span class="h4"><a class="selflink" id="section-6.9.1" href="#section-6.9.1">6.9.1</a>. WNonce</span>
2875
2876 The WNonce message element is defined in <a href="#section-6.3.2">Section 6.3.2</a>.
2877
2878 <span class="h4"><a class="selflink" id="section-6.9.2" href="#section-6.9.2">6.9.2</a>. PSK-MIC</span>
2879
2880 The PSK-MIC message element is defined in <a href="#section-6.2.9">Section 6.2.9</a>.
2881
2882 <span class="h3"><a class="selflink" id="section-6.10" href="#section-6.10">6.10</a>. Key Update Confirm</span>
2883
2884 The Key Update Confirm closes the rekeying loop, and allows the WTP
2885 to recognize that the AC has received and processed the Key Update
2886 messages. At this point, the WTP updates its session key in its
2887 crypto engine, and the associated Initialization Vector, ensuring
2888 that all future LWAPP control frames are encrypted with the newly
2889 derived encryption key.
2890
2891 The WTP MUST include a PSK-MIC message element, which provides
2892 message integrity over the whole message.
2893
2894 The following subsections define the message elements that MUST be
2895 included in this LWAPP operation.
2896
2897 <span class="h4"><a class="selflink" id="section-6.10.1" href="#section-6.10.1">6.10.1</a>. PSK-MIC</span>
2898
2899 The PSK-MIC message element is defined in <a href="#section-6.2.9">Section 6.2.9</a>.
2900
2901 <span class="h3"><a class="selflink" id="section-6.11" href="#section-6.11">6.11</a>. Key Update Trigger</span>
2902
2903 The Key Update Trigger is used by the AC to request that a Key Update
2904 Request be initiated by the WTP.
2905
2906
2907
2908 <span class="grey">Calhoun, et al. Historic [Page 52]</span></pre>
2909 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-53" ></span>
2910 <span class="grey"><a href="./rfc5412">RFC 5412</a> Lightweight Access Point Protocol February 2010</span>
2911
2912
2913 Key Update Triggers are sent by an AC in the Run state to inform the
2914 WTP to initiate a Key Update Request message.
2915
2916 When a WTP receives a Key Update Trigger, it generates a Key Update
2917 Request.
2918
2919 The following subsections define the message elements that MUST be
2920 included in this LWAPP operation.
2921
2922 <span class="h4"><a class="selflink" id="section-6.11.1" href="#section-6.11.1">6.11.1</a>. Session ID</span>
2923
2924 The Session ID message element is defined in <a href="#section-6.1.7">Section 6.1.7</a>.
2925
2926 <span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. WTP Configuration Management</span>
2927
2928 The Wireless Termination Point Configuration messages are used to
2929 exchange configuration between the AC and the WTP.
2930
2931 <span class="h3"><a class="selflink" id="section-7.1" href="#section-7.1">7.1</a>. Configuration Consistency</span>
2932
2933 The LWAPP protocol provides flexibility in how WTP configuration is
2934 managed. To put it simply, a WTP has one of two options:
2935
2936 1. The WTP retains no configuration and simply abides by the
2937 configuration provided by the AC.
2938
2939 2. The WTP retains the configuration of parameters provided by the AC
2940 that are non-default values.
2941
2942 If the WTP opts to save configuration locally, the LWAPP protocol
2943 state machine defines the "Configure" state, which is used during the
2944 initial binding WTP-AC phase, which allows for configuration
2945 exchange. During this period, the WTP sends its current
2946 configuration overrides to the AC via the Configure Request message.
2947 A configuration override is a parameter that is non-default. One
2948 example is that in the LWAPP protocol, the default antenna
2949 configuration is an internal-omni antenna. However, a WTP that
2950 either has no internal antennas, or has been explicitely configured
2951 by the AC to use external antennas would send its antenna
2952 configuration during the configure phase, allowing the AC to become
2953 aware of the WTP's current configuration.
2954
2955 Once the WTP has provided its configuration to the AC, the AC sends
2956 down its own configuration. This allows the WTP to inherit the
2957 configuration and policies on the AC.
2958
2959
2960
2961
2962
2963
2964 <span class="grey">Calhoun, et al. Historic [Page 53]</span></pre>
2965 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-54" ></span>
2966 <span class="grey"><a href="./rfc5412">RFC 5412</a> Lightweight Access Point Protocol February 2010</span>
2967
2968
2969 An LWAPP AC maintains a copy of each active WTP's configuration.
2970 There is no need for versioning or other means to identify
2971 configuration changes. If a WTP becomes inactive, the AC MAY delete
2972 the configuration associated with it. If a WTP were to fail, and
2973 connect to a new AC, it would provide its overridden configuration
2974 parameters, allowing the new AC to be aware of the WTP's
2975 configuration.
2976
2977 As a consequence, this model allows for resiliency, whereby in light
2978 of an AC failure, another AC could provide service to the WTP. In
2979 this scenario, the new AC would be automatically updated on any
2980 possible WTP configuration changes -- eliminating the need for Inter-
2981 AC communication or the need for all ACs to be aware of the
2982 configuration of all WTPs in the network.
2983
2984 Once the LWAPP protocol enters the Run state, the WTPs begin to
2985 provide service. However, it is quite common for administrators to
2986 require that configuration changes be made while the network is
2987 operational. Therefore, the Configuration Update Request is sent by
2988 the AC to the WTP in order to make these changes at run-time.
2989
2990 <span class="h3"><a class="selflink" id="section-7.2" href="#section-7.2">7.2</a>. Configure Request</span>
2991
2992 The Configure Request message is sent by a WTP to send its current
2993 configuration to its AC.
2994
2995 Configure Requests are sent by a WTP after receiving a Join Response,
2996 while in the Configure state.
2997
2998 The Configure Request carries binding-specific message elements.
2999 Refer to the appropriate binding for the definition of this
3000 structure.
3001
3002 When an AC receives a Configure Request, it will act upon the content
3003 of the packet and respond to the WTP with a Configure Response.
3004
3005 The Configure Request includes multiple Administrative State message
3006 elements. There is one such message element for the WTP, and then
3007 one per radio in the WTP.
3008
3009 The following subsections define the message elements that MUST be
3010 included in this LWAPP operation.
3011
3012 <span class="h4"><a class="selflink" id="section-7.2.1" href="#section-7.2.1">7.2.1</a>. Administrative State</span>
3013
3014 The Administrative Event message element is used to communicate the
3015 state of a particular radio. The value contains the following
3016 fields.
3017
3018
3019
3020 <span class="grey">Calhoun, et al. Historic [Page 54]</span></pre>
3021 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-55" ></span>
3022 <span class="grey"><a href="./rfc5412">RFC 5412</a> Lightweight Access Point Protocol February 2010</span>
3023
3024
3025 0 1
3026 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5
3027 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
3028 | Radio ID | Admin State |
3029 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
3030
3031 Type: 27 for Administrative State
3032
3033 Length: 2
3034
3035 Radio ID: An 8-bit value representing the radio to configure. The
3036 Radio ID field may also include the value of 0xff, which is used
3037 to identify the WTP itself. Therefore, if an AC wishes to change
3038 the administrative state of a WTP, it would include 0xff in the
3039 Radio ID field.
3040
3041 Admin State: An 8-bit value representing the administrative state
3042 of the radio. The following values are supported:
3043
3044 1 - Enabled
3045
3046 2 - Disabled
3047
3048 <span class="h4"><a class="selflink" id="section-7.2.2" href="#section-7.2.2">7.2.2</a>. AC Name</span>
3049
3050 The AC Name message element is defined in <a href="#section-5.2.3">Section 5.2.3</a>.
3051
3052 <span class="h4"><a class="selflink" id="section-7.2.3" href="#section-7.2.3">7.2.3</a>. AC Name with Index</span>
3053
3054 The AC Name with Index message element is sent by the AC to the WTP
3055 to configure preferred ACs. The number of instances where this
3056 message element would be present is equal to the number of ACs
3057 configured on the WTP.
3058
3059 0 1
3060 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5
3061 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
3062 | Index | AC Name...
3063 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
3064
3065 Type: 90 for AC Name with Index
3066
3067 Length: 5
3068
3069 Index: The index of the preferred server (e.g., 1=primary,
3070 2=secondary).
3071
3072 AC Name: A variable-length ASCII string containing the AC's name.
3073
3074
3075
3076 <span class="grey">Calhoun, et al. Historic [Page 55]</span></pre>
3077 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-56" ></span>
3078 <span class="grey"><a href="./rfc5412">RFC 5412</a> Lightweight Access Point Protocol February 2010</span>
3079
3080
3081 <span class="h4"><a class="selflink" id="section-7.2.4" href="#section-7.2.4">7.2.4</a>. WTP Board Data</span>
3082
3083 The WTP Board Data message element is sent by the WTP to the AC and
3084 contains information about the hardware present.
3085
3086 0 1 2 3
3087 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
3088 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
3089 | Card ID | Card Revision |
3090 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
3091 | WTP Model |
3092 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
3093 | WTP Model |
3094 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
3095 | WTP Serial Number ... |
3096 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
3097 | Reserved |
3098 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
3099 | Ethernet MAC Address |
3100 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
3101 | Ethernet MAC Address |
3102 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
3103
3104 Type: 50 for WTP Board Data
3105
3106 Length: 26
3107
3108 Card ID: A hardware identifier.
3109
3110 Card Revision: 4-byte Revision of the card.
3111
3112 WTP Model: 8-byte WTP Model Number.
3113
3114 WTP Serial Number: 24-byte WTP Serial Number.
3115
3116 Reserved: A 4-byte reserved field that MUST be set to zero (0).
3117
3118 Ethernet MAC Address: MAC address of the WTP's Ethernet interface.
3119
3120 <span class="h4"><a class="selflink" id="section-7.2.5" href="#section-7.2.5">7.2.5</a>. Statistics Timer</span>
3121
3122 The Statistics Timer message element value is used by the AC to
3123 inform the WTP of the frequency that it expects to receive updated
3124 statistics.
3125
3126
3127
3128
3129
3130
3131
3132 <span class="grey">Calhoun, et al. Historic [Page 56]</span></pre>
3133 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-57" ></span>
3134 <span class="grey"><a href="./rfc5412">RFC 5412</a> Lightweight Access Point Protocol February 2010</span>
3135
3136
3137 0 1
3138 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5
3139 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
3140 | Statistics Timer |
3141 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
3142
3143 Type: 37 for Statistics Timer
3144
3145 Length: 2
3146
3147 Statistics Timer: A 16-bit unsigned integer indicating the time, in
3148 seconds.
3149
3150 <span class="h4"><a class="selflink" id="section-7.2.6" href="#section-7.2.6">7.2.6</a>. WTP Static IP Address Information</span>
3151
3152 The WTP Static IP Address Information message element is used by an
3153 AC to configure or clear a previously configured static IP address on
3154 a WTP.
3155
3156 0 1 2 3
3157 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
3158 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
3159 | IP Address |
3160 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
3161 | Netmask |
3162 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
3163 | Gateway |
3164 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
3165 | Static |
3166 +-+-+-+-+-+-+-+-+
3167
3168 Type: 82 for WTP Static IP Address Information
3169
3170 Length: 13
3171
3172 IP Address: The IP address to assign to the WTP.
3173
3174 Netmask: The IP Netmask.
3175
3176 Gateway: The IP address of the gateway.
3177
3178 Netmask: The IP Netmask.
3179
3180 Static: An 8-bit Boolean stating whether or not the WTP should use
3181 a static IP address. A value of zero disables the static IP
3182 address, while a value of one enables it.
3183
3184
3185
3186
3187
3188 <span class="grey">Calhoun, et al. Historic [Page 57]</span></pre>
3189 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-58" ></span>
3190 <span class="grey"><a href="./rfc5412">RFC 5412</a> Lightweight Access Point Protocol February 2010</span>
3191
3192
3193 <span class="h4"><a class="selflink" id="section-7.2.7" href="#section-7.2.7">7.2.7</a>. WTP Reboot Statistics</span>
3194
3195 The WTP Reboot Statistics message element is sent by the WTP to the
3196 AC to communicate information about reasons why reboots have
3197 occurred.
3198
3199 0 1 2 3
3200 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
3201 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
3202 | Crash Count | LWAPP Initiated Count |
3203 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
3204 | Link Failure Count | Failure Type |
3205 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
3206
3207 Type: 67 for WTP Reboot Statistics
3208
3209 Length: 7
3210
3211 Crash Count: The number of reboots that have occurred due to a WTP
3212 crash.
3213
3214 LWAPP Initiated Count: The number of reboots that have occurred at
3215 the request of some LWAPP message, such as a change in
3216 configuration that required a reboot or an explicit LWAPP reset
3217 request.
3218
3219 Link Failure Count: The number of times that an LWAPP connection
3220 with an AC has failed.
3221
3222 Failure Type: The last WTP failure. The following values are
3223 supported:
3224
3225 0 - Link Failure
3226
3227 1 - LWAPP Initiated
3228
3229 2 - WTP Crash
3230
3231 <span class="h3"><a class="selflink" id="section-7.3" href="#section-7.3">7.3</a>. Configure Response</span>
3232
3233 The Configure Response message is sent by an AC and provides an
3234 opportunity for the AC to override a WTP's requested configuration.
3235
3236 Configure Responses are sent by an AC after receiving a Configure
3237 Request.
3238
3239
3240
3241
3242
3243
3244 <span class="grey">Calhoun, et al. Historic [Page 58]</span></pre>
3245 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-59" ></span>
3246 <span class="grey"><a href="./rfc5412">RFC 5412</a> Lightweight Access Point Protocol February 2010</span>
3247
3248
3249 The Configure Response carries binding-specific message elements.
3250 Refer to the appropriate binding for the definition of this
3251 structure.
3252
3253 When a WTP receives a Configure Response, it acts upon the content of
3254 the packet, as appropriate. If the Configure Response message
3255 includes a Change State Event message element that causes a change in
3256 the operational state of one of the Radios, the WTP will transmit a
3257 Change State Event to the AC as an acknowledgement of the change in
3258 state.
3259
3260 The following subsections define the message elements that MUST be
3261 included in this LWAPP operation.
3262
3263 <span class="h4"><a class="selflink" id="section-7.3.1" href="#section-7.3.1">7.3.1</a>. Decryption Error Report Period</span>
3264
3265 The Decryption Error Report Period message element value is used by
3266 the AC to inform the WTP of how frequently it should send decryption
3267 error report messages.
3268
3269 0 1 2
3270 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3
3271 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
3272 | Radio ID | Report Interval |
3273 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
3274
3275 Type: 38 for Decryption Error Report Period
3276
3277 Length: 3
3278
3279 Radio ID: The Radio Identifier: typically refers to some interface
3280 index on the WTP.
3281
3282 Report Interval: A 16-bit, unsigned integer indicating the time, in
3283 seconds.
3284
3285 <span class="h4"><a class="selflink" id="section-7.3.2" href="#section-7.3.2">7.3.2</a>. Change State Event</span>
3286
3287 The WTP Radio Information message element is used to communicate the
3288 operational state of a radio. The value contains two fields, as
3289 shown.
3290
3291 0 1
3292 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5
3293 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
3294 | Radio ID | State | Cause |
3295 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
3296
3297
3298
3299
3300 <span class="grey">Calhoun, et al. Historic [Page 59]</span></pre>
3301 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-60" ></span>
3302 <span class="grey"><a href="./rfc5412">RFC 5412</a> Lightweight Access Point Protocol February 2010</span>
3303
3304
3305 Type: 26 for Change State Event
3306
3307 Length: 3
3308
3309 Radio ID: The Radio Identifier: typically refers to some interface
3310 index on the WTP.
3311
3312 State: An 8-bit Boolean value representing the state of the radio.
3313 A value of one disables the radio, while a value of two enables
3314 it.
3315
3316 Cause: In the event of a radio being inoperable, the Cause field
3317 would contain the reason the radio is out of service. The
3318 following values are supported:
3319
3320 0 - Normal
3321
3322 1 - Radio Failure
3323
3324 2 - Software Failure
3325
3326 <span class="h4"><a class="selflink" id="section-7.3.3" href="#section-7.3.3">7.3.3</a>. LWAPP Timers</span>
3327
3328 The LWAPP Timers message element is used by an AC to configure LWAPP
3329 timers on a WTP.
3330
3331 0 1
3332 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5
3333 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
3334 | Discovery | Echo Request |
3335 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
3336
3337 Type: 68 for LWAPP Timers
3338
3339 Length: 2
3340
3341 Discovery: The number of seconds between LWAPP Discovery packets
3342 when the WTP is in the discovery mode.
3343
3344 Echo Request: The number of seconds between WTP Echo Request LWAPP
3345 messages.
3346
3347 <span class="h4"><a class="selflink" id="section-7.3.4" href="#section-7.3.4">7.3.4</a>. AC IPv4 List</span>
3348
3349 The AC List message element is defined in <a href="#section-6.2.6">Section 6.2.6</a>.
3350
3351
3352
3353
3354
3355
3356 <span class="grey">Calhoun, et al. Historic [Page 60]</span></pre>
3357 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-61" ></span>
3358 <span class="grey"><a href="./rfc5412">RFC 5412</a> Lightweight Access Point Protocol February 2010</span>
3359
3360
3361 <span class="h4"><a class="selflink" id="section-7.3.5" href="#section-7.3.5">7.3.5</a>. AC IPv6 List</span>
3362
3363 The AC List message element is defined in <a href="#section-6.2.7">Section 6.2.7</a>.
3364
3365 <span class="h4"><a class="selflink" id="section-7.3.6" href="#section-7.3.6">7.3.6</a>. WTP Fallback</span>
3366
3367 The WTP Fallback message element is sent by the AC to the WTP to
3368 enable or disable automatic LWAPP fallback in the event that a WTP
3369 detects its preferred AC, and is not currently connected to it.
3370
3371 0
3372 0 1 2 3 4 5 6 7
3373 +-+-+-+-+-+-+-+-+
3374 | Mode |
3375 +-+-+-+-+-+-+-+-+
3376
3377 Type: 91 for WTP Fallback
3378
3379 Length: 1
3380
3381 Mode: The 8-bit Boolean value indicates the status of automatic
3382 LWAPP fallback on the WTP. A value of zero disables the fallback
3383 feature, while a value of one enables it. When enabled, if the
3384 WTP detects that its primary AC is available, and it is not
3385 connected to it, it SHOULD automatically disconnect from its
3386 current AC and reconnect to its primary. If disabled, the WTP
3387 will only reconnect to its primary through manual intervention
3388 (e.g., through the Reset Request command).
3389
3390 <span class="h4"><a class="selflink" id="section-7.3.7" href="#section-7.3.7">7.3.7</a>. Idle Timeout</span>
3391
3392 The Idle Timeout message element is sent by the AC to the WTP to
3393 provide it with the idle timeout that it should enforce on its active
3394 mobile station entries.
3395
3396 0 1 2 3
3397 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
3398 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
3399 | Timeout |
3400 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
3401
3402 Type: 97 for Idle Timeout
3403
3404 Length: 4
3405
3406 Timeout: The current idle timeout to be enforced by the WTP.
3407
3408
3409
3410
3411
3412 <span class="grey">Calhoun, et al. Historic [Page 61]</span></pre>
3413 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-62" ></span>
3414 <span class="grey"><a href="./rfc5412">RFC 5412</a> Lightweight Access Point Protocol February 2010</span>
3415
3416
3417 <span class="h3"><a class="selflink" id="section-7.4" href="#section-7.4">7.4</a>. Configuration Update Request</span>
3418
3419 Configure Update Requests are sent by the AC to provision the WTP
3420 while in the Run state. This is used to modify the configuration of
3421 the WTP while it is operational.
3422
3423 When an AC receives a Configuration Update Request it will respond
3424 with a Configuration Update Response, with the appropriate Result
3425 Code.
3426
3427 The following subsections define the message elements introduced by
3428 this LWAPP operation.
3429
3430 <span class="h4"><a class="selflink" id="section-7.4.1" href="#section-7.4.1">7.4.1</a>. WTP Name</span>
3431
3432 The WTP Name message element is defined in <a href="#section-6.1.3">Section 6.1.3</a>.
3433
3434 <span class="h4"><a class="selflink" id="section-7.4.2" href="#section-7.4.2">7.4.2</a>. Change State Event</span>
3435
3436 The Change State Event message element is defined in <a href="#section-7.3.2">Section 7.3.2</a>.
3437
3438 <span class="h4"><a class="selflink" id="section-7.4.3" href="#section-7.4.3">7.4.3</a>. Administrative State</span>
3439
3440 The Administrative State message element is defined in <a href="#section-7.2.1">Section 7.2.1</a>.
3441
3442 <span class="h4"><a class="selflink" id="section-7.4.4" href="#section-7.4.4">7.4.4</a>. Statistics Timer</span>
3443
3444 The Statistics Timer message element is defined in <a href="#section-7.2.5">Section 7.2.5</a>.
3445
3446 <span class="h4"><a class="selflink" id="section-7.4.5" href="#section-7.4.5">7.4.5</a>. Location Data</span>
3447
3448 The Location Data message element is defined in <a href="#section-6.1.4">Section 6.1.4</a>.
3449
3450 <span class="h4"><a class="selflink" id="section-7.4.6" href="#section-7.4.6">7.4.6</a>. Decryption Error Report Period</span>
3451
3452 The Decryption Error Report Period message element is defined in
3453 <a href="#section-7.3.1">Section 7.3.1</a>.
3454
3455 <span class="h4"><a class="selflink" id="section-7.4.7" href="#section-7.4.7">7.4.7</a>. AC IPv4 List</span>
3456
3457 The AC List message element is defined in <a href="#section-6.2.6">Section 6.2.6</a>.
3458
3459 <span class="h4"><a class="selflink" id="section-7.4.8" href="#section-7.4.8">7.4.8</a>. AC IPv6 List</span>
3460
3461 The AC List message element is defined in <a href="#section-6.2.7">Section 6.2.7</a>.
3462
3463
3464
3465
3466
3467
3468 <span class="grey">Calhoun, et al. Historic [Page 62]</span></pre>
3469 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-63" ></span>
3470 <span class="grey"><a href="./rfc5412">RFC 5412</a> Lightweight Access Point Protocol February 2010</span>
3471
3472
3473 <span class="h4"><a class="selflink" id="section-7.4.9" href="#section-7.4.9">7.4.9</a>. Add Blacklist Entry</span>
3474
3475 The Add Blacklist Entry message element is used by an AC to add a
3476 blacklist entry on a WTP, ensuring that the WTP no longer provides
3477 any service to the MAC addresses provided in the message. The MAC
3478 addresses provided in this message element are not expected to be
3479 saved in non-volative memory on the WTP.
3480
3481 0 1 2 3
3482 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
3483 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
3484 | Num of Entries| MAC Address[] |
3485 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
3486 | MAC Address[] |
3487 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
3488
3489 Type: 65 for Add Blacklist Entry
3490
3491 Length: &gt;= 7
3492
3493 Num of Entries: The number of MAC addresses in the array.
3494
3495 MAC Address: An array of MAC addresses to add to the blacklist
3496 entry.
3497
3498 <span class="h4"><a class="selflink" id="section-7.4.10" href="#section-7.4.10">7.4.10</a>. Delete Blacklist Entry</span>
3499
3500 The Delete Blacklist Entry message element is used by an AC to delete
3501 a previously added blacklist entry on a WTP, ensuring that the WTP
3502 provides service to the MAC addresses provided in the message.
3503
3504 0 1 2 3
3505 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
3506 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
3507 | Num of Entries| MAC Address[] |
3508 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
3509 | MAC Address[] |
3510 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
3511
3512 Type: 66 for Delete Blacklist Entry
3513
3514 Length: &gt;= 7
3515
3516 Num of Entries: The number of MAC addresses in the array.
3517
3518 MAC Address: An array of MAC addresses to delete from the blacklist
3519 entry.
3520
3521
3522
3523
3524 <span class="grey">Calhoun, et al. Historic [Page 63]</span></pre>
3525 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-64" ></span>
3526 <span class="grey"><a href="./rfc5412">RFC 5412</a> Lightweight Access Point Protocol February 2010</span>
3527
3528
3529 <span class="h4"><a class="selflink" id="section-7.4.11" href="#section-7.4.11">7.4.11</a>. Add Static Blacklist Entry</span>
3530
3531 The Add Static Blacklist Entry message element is used by an AC to
3532 add a permanent Blacklist Entry on a WTP, ensuring that the WTP no
3533 longer provides any service to the MAC addresses provided in the
3534 message. The MAC addresses provided in this message element are
3535 expected to be saved in non-volative memory on the WTP.
3536
3537 0 1 2 3
3538 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
3539 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
3540 | Num of Entries| MAC Address[] |
3541 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
3542 | MAC Address[] |
3543 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
3544
3545 Type: 70 for Delete Blacklist Entry
3546
3547 Length: &gt;= 7
3548
3549 Num of Entries: The number of MAC addresses in the array.
3550
3551 MAC Address: An array of MAC addresses to add to the permanent
3552 blacklist entry.
3553
3554 <span class="h4"><a class="selflink" id="section-7.4.12" href="#section-7.4.12">7.4.12</a>. Delete Static Blacklist Entry</span>
3555
3556 The Delete Static Blacklist Entry message element is used by an AC to
3557 delete a previously added static blacklist entry on a WTP, ensuring
3558 that the WTP provides service to the MAC addresses provided in the
3559 message.
3560
3561 0 1 2 3
3562 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
3563 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
3564 | Num of Entries| MAC Address[] |
3565 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
3566 | MAC Address[] |
3567 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
3568
3569 Type: 71 for Delete Blacklist Entry
3570
3571 Length: &gt;= 7
3572
3573 Num of Entries: The number of MAC addresses in the array.
3574
3575 MAC Address: An array of MAC addresses to delete from the static
3576 blacklist entry.
3577
3578
3579
3580 <span class="grey">Calhoun, et al. Historic [Page 64]</span></pre>
3581 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-65" ></span>
3582 <span class="grey"><a href="./rfc5412">RFC 5412</a> Lightweight Access Point Protocol February 2010</span>
3583
3584
3585 <span class="h4"><a class="selflink" id="section-7.4.13" href="#section-7.4.13">7.4.13</a>. LWAPP Timers</span>
3586
3587 The LWAPP Timers message element is defined in <a href="#section-7.3.3">Section 7.3.3</a>.
3588
3589 <span class="h4"><a class="selflink" id="section-7.4.14" href="#section-7.4.14">7.4.14</a>. AC Name with Index</span>
3590
3591 The AC Name with Index message element is defined in <a href="#section-7.2.3">Section 7.2.3</a>.
3592
3593 <span class="h4"><a class="selflink" id="section-7.4.15" href="#section-7.4.15">7.4.15</a>. WTP Fallback</span>
3594
3595 The WTP Fallback message element is defined in <a href="#section-7.3.6">Section 7.3.6</a>.
3596
3597 <span class="h4"><a class="selflink" id="section-7.4.16" href="#section-7.4.16">7.4.16</a>. Idle Timeout</span>
3598
3599 The Idle Timeout message element is defined in <a href="#section-7.3.7">Section 7.3.7</a>.
3600
3601 <span class="h3"><a class="selflink" id="section-7.5" href="#section-7.5">7.5</a>. Configuration Update Response</span>
3602
3603 The Configuration Update Response is the acknowledgement message for
3604 the Configuration Update Request.
3605
3606 Configuration Update Responses are sent by a WTP after receiving a
3607 Configuration Update Request.
3608
3609 When an AC receives a Configure Update Response, the result code
3610 indicates if the WTP successfully accepted the configuration.
3611
3612 The following subsections define the message elements that must be
3613 present in this LWAPP operation.
3614
3615 <span class="h4"><a class="selflink" id="section-7.5.1" href="#section-7.5.1">7.5.1</a>. Result Code</span>
3616
3617 The Result Code message element is defined in <a href="#section-6.2.1">Section 6.2.1</a>.
3618
3619 <span class="h3"><a class="selflink" id="section-7.6" href="#section-7.6">7.6</a>. Change State Event Request</span>
3620
3621 The Change State Event is used by the WTP to inform the AC of a
3622 change in the operational state.
3623
3624 The Change State Event message is sent by the WTP when it receives a
3625 Configuration Response that includes a Change State Event message
3626 element. It is also sent in the event that the WTP detects an
3627 operational failure with a radio. The Change State Event may be sent
3628 in either the Configure or Run state (see Figure 2).
3629
3630 When an AC receives a Change State Event it will respond with a
3631 Change State Event Response and make any necessary modifications to
3632 internal WTP data structures.
3633
3634
3635
3636 <span class="grey">Calhoun, et al. Historic [Page 65]</span></pre>
3637 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-66" ></span>
3638 <span class="grey"><a href="./rfc5412">RFC 5412</a> Lightweight Access Point Protocol February 2010</span>
3639
3640
3641 The following subsections define the message elements that must be
3642 present in this LWAPP operation.
3643
3644 <span class="h4"><a class="selflink" id="section-7.6.1" href="#section-7.6.1">7.6.1</a>. Change State Event</span>
3645
3646 The Change State Event message element is defined in <a href="#section-7.3.2">Section 7.3.2</a>.
3647
3648 <span class="h3"><a class="selflink" id="section-7.7" href="#section-7.7">7.7</a>. Change State Event Response</span>
3649
3650 The Change State Event Response acknowledges the Change State Event.
3651
3652 Change State Event Responses are sent by a WTP after receiving a
3653 Change State Event.
3654
3655 The Change State Event Response carries no message elements. Its
3656 purpose is to acknowledge the receipt of the Change State Event.
3657
3658 The WTP does not need to perform any special processing of the Change
3659 State Event Response message.
3660
3661 <span class="h3"><a class="selflink" id="section-7.8" href="#section-7.8">7.8</a>. Clear Config Indication</span>
3662
3663 The Clear Config Indication is used to reset a WTP's configuration.
3664
3665 The Clear Config Indication is sent by an AC to request that a WTP
3666 reset its configuration to manufacturing defaults. The Clear Config
3667 Indication message is sent while in the Run LWAPP state.
3668
3669 The Reset Request carries no message elements.
3670
3671 When a WTP receives a Clear Config Indication, it will reset its
3672 configuration to manufacturing defaults.
3673
3674 <span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. Device Management Operations</span>
3675
3676 This section defines LWAPP operations responsible for debugging,
3677 gathering statistics, logging, and firmware management.
3678
3679 <span class="h3"><a class="selflink" id="section-8.1" href="#section-8.1">8.1</a>. Image Data Request</span>
3680
3681 The Image Data Request is used to update firmware on the WTP. This
3682 message and its companion response are used by the AC to ensure that
3683 the image being run on each WTP is appropriate.
3684
3685 Image Data Requests are exchanged between the WTP and the AC to
3686 download a new program image to a WTP.
3687
3688 When a WTP or AC receives an Image Data Request, it will respond with
3689
3690
3691
3692 <span class="grey">Calhoun, et al. Historic [Page 66]</span></pre>
3693 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-67" ></span>
3694 <span class="grey"><a href="./rfc5412">RFC 5412</a> Lightweight Access Point Protocol February 2010</span>
3695
3696
3697 an Image Data Response.
3698
3699 The format of the Image Data and Image Download message elements are
3700 described in the following subsections.
3701
3702 <span class="h4"><a class="selflink" id="section-8.1.1" href="#section-8.1.1">8.1.1</a>. Image Download</span>
3703
3704 The Image Download message element is sent by the WTP to the AC and
3705 contains the image filename. The value is a variable-length byte
3706 string. The string is NOT zero terminated.
3707
3708 <span class="h4"><a class="selflink" id="section-8.1.2" href="#section-8.1.2">8.1.2</a>. Image Data</span>
3709
3710 The Image Data message element is present when sent by the AC and
3711 contains the following fields.
3712
3713 0 1 2 3
3714 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
3715 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
3716 | Opcode | Checksum | Image Data |
3717 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
3718 | Image Data ... |
3719 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
3720
3721 Type: 33 for Image Data
3722
3723 Length: &gt;= 5
3724
3725 Opcode: An 8-bit value representing the transfer opcode. The
3726 following values are supported:
3727
3728 3 - Image Data is included.
3729
3730 5 - An error occurred. Transfer is aborted.
3731
3732 Checksum: A 16-bit value containing a checksum of the Image Data
3733 that follows.
3734
3735 Image Data: The Image Data field contains 1024 characters, unless
3736 the payload being sent is the last one (end of file).
3737
3738
3739
3740
3741
3742
3743
3744
3745
3746
3747
3748 <span class="grey">Calhoun, et al. Historic [Page 67]</span></pre>
3749 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-68" ></span>
3750 <span class="grey"><a href="./rfc5412">RFC 5412</a> Lightweight Access Point Protocol February 2010</span>
3751
3752
3753 <span class="h3"><a class="selflink" id="section-8.2" href="#section-8.2">8.2</a>. Image Data Response</span>
3754
3755 The Image Data Response acknowledges the Image Data Request.
3756
3757 An Image Data Responses is sent in response to an Image Data Request.
3758 Its purpose is to acknowledge the receipt of the Image Data Request
3759 packet.
3760
3761 The Image Data Response carries no message elements.
3762
3763 No action is necessary on receipt.
3764
3765 <span class="h3"><a class="selflink" id="section-8.3" href="#section-8.3">8.3</a>. Reset Request</span>
3766
3767 The Reset Request is used to cause a WTP to reboot.
3768
3769 Reset Requests are sent by an AC to cause a WTP to reinitialize its
3770 operation.
3771
3772 The Reset Request carries no message elements.
3773
3774 When a WTP receives a Reset Request it will respond with a Reset
3775 Response and then reinitialize itself.
3776
3777 <span class="h3"><a class="selflink" id="section-8.4" href="#section-8.4">8.4</a>. Reset Response</span>
3778
3779 The Reset Response acknowledges the Reset Request.
3780
3781 Reset Responses are sent by a WTP after receiving a Reset Request.
3782
3783 The Reset Response carries no message elements. Its purpose is to
3784 acknowledge the receipt of the Reset Request.
3785
3786 When an AC receives a Reset Response, it is notified that the WTP
3787 will now reinitialize its operation.
3788
3789 <span class="h3"><a class="selflink" id="section-8.5" href="#section-8.5">8.5</a>. WTP Event Request</span>
3790
3791 The WTP Event Request is used by a WTP to send information to its AC.
3792 These types of events may be periodical, or some asynchronous event
3793 on the WTP. For instance, a WTP collects statistics and uses the WTP
3794 Event Request to transmit this information to the AC.
3795
3796 When an AC receives a WTP Event Request, it will respond with a WTP
3797 Event Request.
3798
3799
3800
3801
3802
3803
3804 <span class="grey">Calhoun, et al. Historic [Page 68]</span></pre>
3805 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-69" ></span>
3806 <span class="grey"><a href="./rfc5412">RFC 5412</a> Lightweight Access Point Protocol February 2010</span>
3807
3808
3809 The WTP Event Request message MUST contain one of the following
3810 message element described in the next subsections, or a message
3811 element that is defined for a specific technology.
3812
3813 <span class="h4"><a class="selflink" id="section-8.5.1" href="#section-8.5.1">8.5.1</a>. Decryption Error Report</span>
3814
3815 The Decryption Error Report message element value is used by the WTP
3816 to inform the AC of decryption errors that have occurred since the
3817 last report.
3818
3819 0 1 2
3820 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3
3821 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
3822 | Radio ID |Num Of Entries | Mobile MAC Address |
3823 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
3824 | Mobile MAC Address[] |
3825 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
3826
3827 Type: 39 for Decryption Error Report
3828
3829 Length: &gt;= 8
3830
3831 Radio ID: The Radio Identifier, typically refers to some interface
3832 index on the WTP.
3833
3834 Num Of Entries: An 8-bit unsigned integer indicating the number of
3835 mobile MAC addresses.
3836
3837 Mobile MAC Address: An array of mobile station MAC addresses that
3838 have caused decryption errors.
3839
3840 <span class="h4"><a class="selflink" id="section-8.5.2" href="#section-8.5.2">8.5.2</a>. Duplicate IPv4 Address</span>
3841
3842 The Duplicate IPv4 Address message element is used by a WTP to inform
3843 an AC that it has detected another host using the same IP address it
3844 is currently using.
3845
3846 0 1 2 3
3847 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
3848 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
3849 | IP Address |
3850 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
3851 | MAC Address |
3852 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
3853 | MAC Address |
3854 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
3855
3856 Type: 77 for Duplicate IPv4 Address
3857
3858
3859
3860 <span class="grey">Calhoun, et al. Historic [Page 69]</span></pre>
3861 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-70" ></span>
3862 <span class="grey"><a href="./rfc5412">RFC 5412</a> Lightweight Access Point Protocol February 2010</span>
3863
3864
3865 Length: 10
3866
3867 IP Address: The IP address currently used by the WTP.
3868
3869 MAC Address: The MAC address of the offending device.
3870
3871 <span class="h4"><a class="selflink" id="section-8.5.3" href="#section-8.5.3">8.5.3</a>. Duplicate IPv6 Address</span>
3872
3873 The Duplicate IPv6 Address message element is used by a WTP to inform
3874 an AC that it has detected another host using the same IP address it
3875 is currently using.
3876
3877 0 1 2 3
3878 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
3879 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
3880 | IP Address |
3881 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
3882 | IP Address |
3883 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
3884 | IP Address |
3885 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
3886 | IP Address |
3887 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
3888 | MAC Address |
3889 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
3890 | MAC Address |
3891 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
3892
3893 Type: 77 for Duplicate IPv6 Address
3894
3895 Length: 10
3896
3897 IP Address: The IP address currently used by the WTP.
3898
3899 MAC Address: The MAC address of the offending device.
3900
3901 <span class="h3"><a class="selflink" id="section-8.6" href="#section-8.6">8.6</a>. WTP Event Response</span>
3902
3903 The WTP Event Response acknowledges the WTP Event Request.
3904
3905 WTP Event Responses are sent by an AC after receiving a WTP Event
3906 Request.
3907
3908 The WTP Event Response carries no message elements.
3909
3910
3911
3912
3913
3914
3915
3916 <span class="grey">Calhoun, et al. Historic [Page 70]</span></pre>
3917 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-71" ></span>
3918 <span class="grey"><a href="./rfc5412">RFC 5412</a> Lightweight Access Point Protocol February 2010</span>
3919
3920
3921 <span class="h3"><a class="selflink" id="section-8.7" href="#section-8.7">8.7</a>. Data Transfer Request</span>
3922
3923 The Data Transfer Request is used to upload debug information from
3924 the WTP to the AC.
3925
3926 Data Transfer Requests are sent by the WTP to the AC when it
3927 determines that it has important information to send to the AC. For
3928 instance, if the WTP detects that its previous reboot was caused by a
3929 system crash, it would want to send the crash file to the AC. The
3930 remote debugger function in the WTP also uses the Data Transfer
3931 Request in order to send console output to the AC for debugging
3932 purposes.
3933
3934 When an AC receives a Data Transfer Request, it will respond with a
3935 Data Transfer Response. The AC may log the information received as
3936 it sees fit.
3937
3938 The Data Transfer Request message MUST contain ONE of the following
3939 message element described in the next subsection.
3940
3941 <span class="h4"><a class="selflink" id="section-8.7.1" href="#section-8.7.1">8.7.1</a>. Data Transfer Mode</span>
3942
3943 The Data Transfer Mode message element is used by the AC to request
3944 information from the WTP for debugging purposes.
3945
3946 0
3947 0 1 2 3 4 5 6 7
3948 +-+-+-+-+-+-+-+-+
3949 | Data Type |
3950 +-+-+-+-+-+-+-+-+
3951
3952 Type: 52 for Data Transfer Mode
3953
3954 Length: 1
3955
3956 Data Type: An 8-bit value describing the type of information being
3957 requested. The following values are supported:
3958
3959 1 - WTP Crash Data
3960
3961 2 - WTP Memory Dump
3962
3963 <span class="h4"><a class="selflink" id="section-8.7.2" href="#section-8.7.2">8.7.2</a>. Data Transfer Data</span>
3964
3965 The Data Transfer Data message element is used by the WTP to provide
3966 information to the AC for debugging purposes.
3967
3968
3969
3970
3971
3972 <span class="grey">Calhoun, et al. Historic [Page 71]</span></pre>
3973 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-72" ></span>
3974 <span class="grey"><a href="./rfc5412">RFC 5412</a> Lightweight Access Point Protocol February 2010</span>
3975
3976
3977 0 1 2 3
3978 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
3979 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
3980 | Data Type | Data Length | Data ....
3981 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
3982
3983 Type: 53 for Data Transfer Data
3984
3985 Length: &gt;= 3
3986
3987 Data Type: An 8-bit value describing the type of information being
3988 sent. The following values are supported:
3989
3990 1 - WTP Crash Data
3991
3992 2 - WTP Memory Dump
3993
3994 Data Length: Length of data field.
3995
3996 Data: Debug information.
3997
3998 <span class="h3"><a class="selflink" id="section-8.8" href="#section-8.8">8.8</a>. Data Transfer Response</span>
3999
4000 The Data Transfer Response acknowledges the Data Transfer Request.
4001
4002 A Data Transfer Response is sent in response to a Data Transfer
4003 Request. Its purpose is to acknowledge the receipt of the Data
4004 Transfer Request packet.
4005
4006 The Data Transfer Response carries no message elements.
4007
4008 Upon receipt of a Data Transfer Response, the WTP transmits more
4009 information, if any is available.
4010
4011 <span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. Mobile Session Management</span>
4012
4013 Messages in this section are used by the AC to create, modify, or
4014 delete mobile station session state on the WTPs.
4015
4016 <span class="h3"><a class="selflink" id="section-9.1" href="#section-9.1">9.1</a>. Mobile Config Request</span>
4017
4018 The Mobile Config Request message is used to create, modify, or
4019 delete mobile session state on a WTP. The message is sent by the AC
4020 to the WTP, and may contain one or more message elements. The
4021
4022
4023
4024
4025
4026
4027
4028 <span class="grey">Calhoun, et al. Historic [Page 72]</span></pre>
4029 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-73" ></span>
4030 <span class="grey"><a href="./rfc5412">RFC 5412</a> Lightweight Access Point Protocol February 2010</span>
4031
4032
4033 message elements for this LWAPP control message include information
4034 that is generally highly technology-specific. Therefore, please
4035 refer to the appropriate binding section or document for the
4036 definitions of the messages elements that may be used in this control
4037 message.
4038
4039 This section defines the format of the Delete Mobile message element,
4040 since it does not contain any technology-specific information.
4041
4042 <span class="h4"><a class="selflink" id="section-9.1.1" href="#section-9.1.1">9.1.1</a>. Delete Mobile</span>
4043
4044 The Delete Mobile message element is used by the AC to inform a WTP
4045 that it should no longer provide service to a particular mobile
4046 station. The WTP must terminate service immediately upon receiving
4047 this message element.
4048
4049 The transmission of a Delete Mobile message element could occur for
4050 various reasons, including administrative reasons, as a result of the
4051 fact that the mobile has roamed to another WTP, etc.
4052
4053 Once access has been terminated for a given station, any future
4054 packets received from the mobile must result in a deauthenticate
4055 message, as specified in [<a href="#ref-6" title="&quot;Information technology - Telecommunications and information exchange between systems - Local and metropolitan area networks - Specific requirements - Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) specifications&quot;">6</a>].
4056
4057 0 1 2 3
4058 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
4059 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
4060 | Radio ID | MAC Address |
4061 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
4062 | MAC Address |
4063 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
4064
4065 Type: 30 for Delete Mobile
4066
4067 Length: 7
4068
4069 Radio ID: An 8-bit value representing the radio
4070
4071 MAC Address: The mobile station's MAC address
4072
4073 <span class="h3"><a class="selflink" id="section-9.2" href="#section-9.2">9.2</a>. Mobile Config Response</span>
4074
4075 The Mobile Configuration Response is used to acknowledge a previously
4076 received Mobile Configuration Request, and includes a Result Code
4077 message element that indicates whether an error occurred on the WTP.
4078
4079 This message requires no special processing and is only used to
4080 acknowledge the Mobile Configuration Request.
4081
4082
4083
4084 <span class="grey">Calhoun, et al. Historic [Page 73]</span></pre>
4085 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-74" ></span>
4086 <span class="grey"><a href="./rfc5412">RFC 5412</a> Lightweight Access Point Protocol February 2010</span>
4087
4088
4089 The Data Transfer Request message MUST contain the message elements
4090 described in the next subsection.
4091
4092 <span class="h4"><a class="selflink" id="section-9.2.1" href="#section-9.2.1">9.2.1</a>. Result Code</span>
4093
4094 The Result Code message element is defined in <a href="#section-6.2.1">Section 6.2.1</a>.
4095
4096 <span class="h2"><a class="selflink" id="section-10" href="#section-10">10</a>. LWAPP Security</span>
4097
4098 Note: This version only defines a certificate and a shared-secret-
4099 based mechanism to secure control LWAPP traffic exchanged between the
4100 WTP and the AC.
4101
4102 <span class="h3"><a class="selflink" id="section-10.1" href="#section-10.1">10.1</a>. Securing WTP-AC Communications</span>
4103
4104 While it is generally straightforward to produce network
4105 installations in which the communications medium between the WTP and
4106 AC is not accessible to the casual user (e.g., these LAN segments are
4107 isolated, and no RJ45 or other access ports exist between the WTP and
4108 the AC), this will not always be the case. Furthermore, a determined
4109 attacker may resort to various, more sophisticated monitoring and/or
4110 access techniques, thereby compromising the integrity of this
4111 connection.
4112
4113 In general, a certain level of threat on the local (wired) LAN is
4114 expected and accepted in most computing environments. That is, it is
4115 expected that in order to provide users with an acceptable level of
4116 service and maintain reasonable productivity levels, a certain amount
4117 of risk must be tolerated. It is generally believed that a certain
4118 perimeter is maintained around such LANs, that an attacker must have
4119 access to the building(s) in which such LANs exist, and that they
4120 must be able to "plug in" to the LAN in order to access the network.
4121
4122 With these things in mind, we can begin to assess the general
4123 security requirements for AC-WTP communications. While an in-depth
4124 security analysis of threats and risks to these communications is
4125 beyond the scope of this document, some discussion of the motivation
4126 for various security-related design choices is useful. The
4127 assumptions driving the security design thus far include the
4128 following:
4129
4130 o WTP-AC communications take place over a wired connection that may
4131 be accessible to a sophisticated attacker.
4132
4133 o access to this connection is not trivial for an outsider (i.e.,
4134 someone who does not "belong" in the building) to access.
4135
4136
4137
4138
4139
4140 <span class="grey">Calhoun, et al. Historic [Page 74]</span></pre>
4141 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-75" ></span>
4142 <span class="grey"><a href="./rfc5412">RFC 5412</a> Lightweight Access Point Protocol February 2010</span>
4143
4144
4145 o if authentication and/or privacy of end-to-end traffic for which
4146 the WTP and AC are intermediaries is required, this may be
4147 provided via IPsec [<a href="#ref-14" title="&quot;Security Architecture for the Internet Protocol&quot;">14</a>].
4148
4149 o privacy and authentication for at least some WTP-AC control
4150 traffic is required (e.g., Wired Equivalent Privacy (WEP) keys for
4151 user sessions, passed from the AC to the WTP).
4152
4153 o the AC can be trusted to generate strong cryptographic keys.
4154
4155 The AC-WTP traffic can be considered to consist of two types: data
4156 traffic (e.g., to or from an end user), and control traffic, which is
4157 strictly between the AC and WTP. Since data traffic may be secured
4158 using IPsec (or some other end-to-end security mechanism), we confine
4159 our solution to control traffic. The resulting security consists of
4160 two components: an authenticated key exchange and control traffic
4161 security encapsulation. The security encapsulation is accomplished
4162 using AES-CCM, described in [<a href="#ref-3" title="&quot;Counter with CBC- MAC (CCM)&quot;">3</a>]. This encapsulation provides for
4163 strong AES-based authentication and encryption [<a href="#ref-2" title="&quot;Advanced Encryption Standard (AES)&quot;">2</a>]. The exchange of
4164 cryptographic keys used for CCM is described below.
4165
4166 <span class="h3"><a class="selflink" id="section-10.2" href="#section-10.2">10.2</a>. LWAPP Frame Encryption</span>
4167
4168 While the LWAPP protocol uses AES-CCM to encrypt control traffic, it
4169 is important to note that not all control frames are encrypted. The
4170 LWAPP discovery and join phase are not encrypted. The Discovery
4171 messages are sent in the clear since there does not exist a security
4172 association between the WTP and the AC during the discovery phase.
4173 The join phase is an authenticated exchange used to negotiate
4174 symmetric session keys (see <a href="#section-10.3">Section 10.3</a>).
4175
4176 Once the join phase has been successfully completed, the LWAPP state
4177 machine Figure 2 will move to the Configure state, at which time all
4178 LWAPP control frames are encrypted using AES-CCM.
4179
4180 Encryption of a control message begins at the Message Element field:
4181 meaning the Msg Type, Seq Num, Msg Element Length, and Session ID
4182 fields are left intact (see <a href="#section-4.2.1">Section 4.2.1</a>).
4183
4184 The AES-CCM 12-byte authentication data is appended to the end of the
4185 message. The authentication data is calculated from the start of the
4186 LWAPP packet and includes the complete LWAPP control header (see
4187 <a href="#section-4.2.1">Section 4.2.1</a>).
4188
4189
4190
4191
4192
4193
4194
4195
4196 <span class="grey">Calhoun, et al. Historic [Page 75]</span></pre>
4197 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-76" ></span>
4198 <span class="grey"><a href="./rfc5412">RFC 5412</a> Lightweight Access Point Protocol February 2010</span>
4199
4200
4201 The AES-CCM block cipher protocol requires an initialization vector.
4202 The LWAPP protocol requires that the WTP and the AC maintain two
4203 separate IVs, one for transmission and one for reception. The IV
4204 derived during the key exchange phase by both the WTP and the AC is
4205 used as the base for all encrypted packets with a new key.
4206
4207 <span class="h3"><a class="selflink" id="section-10.3" href="#section-10.3">10.3</a>. Authenticated Key Exchange</span>
4208
4209 This section describes the key management component of the LWAPP
4210 protocol. There are two modes supported by LWAPP: certificate and
4211 pre-shared key.
4212
4213 <span class="h4"><a class="selflink" id="section-10.3.1" href="#section-10.3.1">10.3.1</a>. Terminology</span>
4214
4215 This section details the key management protocol that makes use of
4216 pre-shared secrets.
4217
4218 The following notations are used throughout this section:
4219
4220 o PSK - the pre-shared key shared between the WTP and the AC.
4221
4222 o Kpriv - the private key of a public-private key pair.
4223
4224 o Kpub - the public key of the pair.
4225
4226 o SessionID - a randomly generated LWAPP session identifier,
4227 provided by the WTP in the Join Request.
4228
4229 o E-x{Kpub, M} - RSA encryption of M using X's public key.
4230
4231 o D-x{Kpriv, C} - RSA decryption of C using X's private key.
4232
4233 o AES-CMAC(key, packet) - A message integrity check, using AES-CMAC
4234 and key, of the complete LWAPP packet, with the Sequence Number
4235 field and the payload of the PSK-MIC message element set to zero.
4236
4237 o AES-E(key, plaintext) - Plaintext is encrypted with key, using
4238 AES.
4239
4240 o AES-D(key, ciphertext) - ciphertext is decrypted with key, using
4241 AES.
4242
4243 o Certificate-AC - AC's Certificate.
4244
4245 o Certificate-WTP - WTP's Certificate.
4246
4247 o WTP-MAC - The WTP's MAC address.
4248
4249
4250
4251
4252 <span class="grey">Calhoun, et al. Historic [Page 76]</span></pre>
4253 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-77" ></span>
4254 <span class="grey"><a href="./rfc5412">RFC 5412</a> Lightweight Access Point Protocol February 2010</span>
4255
4256
4257 o AC-MAC - The AC's MAC address.
4258
4259 o RK0 - the root key, which is created through a Key Derivation
4260 Function (KDF) function.
4261
4262 o RK0E - the root Encryption key, derived from RK0.
4263
4264 o RK0M - the root MIC key, derived from RK0.
4265
4266 o SK1 - the session key.
4267
4268 o SK1C - the session confirmation key, derived from SK.
4269
4270 o SK1E - the session encryption key, derived from SK.
4271
4272 o SK1W - the session keywrap key, derived from SK (see <a href="./rfc3394">RFC 3394</a>
4273 [<a href="#ref-9" title="&quot;Advanced Encryption Standard (AES) Key Wrap Algorithm&quot;">9</a>]).
4274
4275 o WNonce - The WTP's randomly generated nonce.
4276
4277 o ANonce - The AC's randomly generated nonce.
4278
4279 o EWNonce - The payload of the WNonce message element, which
4280 includes the WNonce.
4281
4282 o EANonce - The payload of the ANonce message element, which
4283 includes the ANonce.
4284
4285 <span class="h4"><a class="selflink" id="section-10.3.2" href="#section-10.3.2">10.3.2</a>. Initial Key Generation</span>
4286
4287 The AC and WTP accomplish mutual authentication and a cryptographic
4288 key exchange in a dual round trip using the Join Request, Join
4289 Response, Join ACK, and Join Confirm (see <a href="#section-6.1">Section 6.1</a>).
4290
4291 The following text describes the exchange between the WTP and the AC
4292 that creates a session key, which is used to secure LWAPP control
4293 messages.
4294
4295 o The WTP creates a Join Request using the following process:
4296
4297 o If certificate-based security is used, the WTP adds the
4298 Certificate message element (see <a href="#section-6.1.6">Section 6.1.6</a>) with its
4299 contents set to Certificate-WTP.
4300
4301 o The WTP adds the Session ID message element (see <a href="#section-6.1.7">Section 6.1.7</a>)
4302 with the contents set to a randomly generated session
4303 identifier (see <a href="./rfc1750">RFC 1750</a> [<a href="#ref-4" title="&quot;Randomness Requirements for Security&quot;">4</a>]). The WTP MUST save the Session
4304 ID in order to validate the Join Response.
4305
4306
4307
4308 <span class="grey">Calhoun, et al. Historic [Page 77]</span></pre>
4309 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-78" ></span>
4310 <span class="grey"><a href="./rfc5412">RFC 5412</a> Lightweight Access Point Protocol February 2010</span>
4311
4312
4313 o The WTP creates a random nonce, included in the XNonce message
4314 element (see <a href="#section-6.1.9">Section 6.1.9</a>). The WTP MUST save the XNonce to
4315 validate the Join Response.
4316
4317 o The WTP transmits the Join Request to the AC.
4318
4319 o Upon receiving the Join Request, the AC uses the following
4320 process:
4321
4322 o The AC creates the Join Response, and ensures that the Session
4323 ID message element matches the value found in the Join Request.
4324
4325 o If certificate-based security is used, the AC:
4326
4327 o adds the Certificate-AC to the Certificate message element.
4328
4329 o creates a random 'AC Nonce' and encrypts it using the
4330 following algorithm E-wtp(Kpub, XNonce XOR 'AC Nonce'). The
4331 encrypted contents are added to the ANonce's message element
4332 payload.
4333
4334 o If a pre-shared-key-based security is used, the AC:
4335
4336 o creates RK0 through the following algorithm: RK0 = KDF-
4337 256{PSK, "LWAPP PSK Top K0" || Session ID || WTP-MAC || AC-
4338 MAC}, where WTP-MAC is the WTP's MAC address in the form
4339 "xx:xx:xx:xx:xx:xx". Similarly, the AC-MAC is an ASCII
4340 encoding of the AC's MAC address, of the form "xx:xx:xx:xx:
4341 xx:xx". The resulting K0 is split into the following:
4342
4343 o The first 16 octets are known as RK0E, and are used as an
4344 encryption key.
4345
4346 o The second 16 octets are known as RK0M, and are used for
4347 MIC'ing purposes.
4348
4349 o The AC creates a random 'AC Nonce' and encrypts it using the
4350 following algorithm: AES-E(RK0E, XNonce XOR 'AC Nonce').
4351 The encrypted contents are added to the ANonce's message
4352 element payload.
4353
4354 o The AC adds a MIC to the contents of the Join Response using
4355 AES-CMAC(RK0M, Join Response) and adds the resulting hash to
4356 the PSK-MIC (<a href="#section-6.2.9">Section 6.2.9</a>) message element.
4357
4358 o Upon receiving the Join Response, the WTP uses the following
4359 process:
4360
4361
4362
4363
4364 <span class="grey">Calhoun, et al. Historic [Page 78]</span></pre>
4365 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-79" ></span>
4366 <span class="grey"><a href="./rfc5412">RFC 5412</a> Lightweight Access Point Protocol February 2010</span>
4367
4368
4369 o If a pre-shared key is used, the WTP authenticates the Join
4370 Response's PSK-MIC message element. If authentication fails,
4371 the packet is dropped.
4372
4373 o The WTP decrypts the ANonce message element and XOR's the value
4374 with XNonce to retrieve the 'AC Nonce'. The ANonce payload is
4375 referred to as ciphertext below:
4376
4377 o If a pre-shared key is used, use AES-D(RK0E, ciphertext).
4378 The 'AC Nonce' is then recovered using XNonce XOR plaintext.
4379
4380 o If certificates are used, use d-wtp(Kpriv, ciphertext). The
4381 'AC Nonce' is then recovered using XNonce XOR plaintext.
4382
4383 o The WTP creates a random 'WTP Nonce'.
4384
4385 o The WTP uses the KDF function to create a 64-octet session key
4386 (SK). The KDF function used is as follows: KDF-512{'WTP Nonce'
4387 || 'AC Nonce', "LWAPP Key Generation", WTP-MAC || AC-MAC}. The
4388 KDF function is defined in [<a href="#ref-7" title="&quot;Information technology - Telecommunications and information exchange between systems - Local and metropolitan area networks - Specific requirements - Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) specifications Amendment 6: Medium Access Control (MAC) Security Enhancements&quot;">7</a>].
4389
4390 o SK is then broken down into three separate session keys with
4391 different purposes:
4392
4393 o The first 16 octets are known as SK1C, and are used as a
4394 confirmation key.
4395
4396 o The second 16 octets are known as SK1E, and are as the
4397 encryption key.
4398
4399 o The third 16 octets are known as SK1D, and are used as the
4400 keywrap key.
4401
4402 o The fourth 16 octets are known as IV, and are used as the
4403 Initialization Vector during encryption.
4404
4405 o The WTP creates the Join ACK message.
4406
4407 o If certificate-based security is used, the AC:
4408
4409 o encrypts the 'WTP Nonce' using the following algorithm: E-
4410 ac(Kpub, 'WTP Nonce'). The encrypted contents are added to
4411 the WNonce's message element payload.
4412
4413 o If a pre-shared-key-based security is used, the AC:
4414
4415
4416
4417
4418
4419
4420 <span class="grey">Calhoun, et al. Historic [Page 79]</span></pre>
4421 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-80" ></span>
4422 <span class="grey"><a href="./rfc5412">RFC 5412</a> Lightweight Access Point Protocol February 2010</span>
4423
4424
4425 o encrypts the 'WTP Nonce' using the following algorithm:
4426 AES-E(RK0E, 'WTP Nonce'). The encrypted contents are added
4427 to the WNonce's message element payload.
4428
4429 o The WTP adds a MIC to the contents of the Join ACK using
4430 AES-CMAC(SK1M, Join ACK) and adds the resulting hash to the
4431 PSK-MIC (<a href="#section-6.2.9">Section 6.2.9</a>) message element.
4432
4433 o The WTP then transmits the Join ACK to the AC.
4434
4435 o Upon receiving the Join ACK, the AC uses the following process:
4436
4437 o The AC authenticates the Join ACK through the PSK-MIC message
4438 element. If authentic, the AC decrypts the WNonce message
4439 element to retrieve the 'WTP Nonce'. If the Join ACK cannot be
4440 authenticated, the packet is dropped.
4441
4442 o The AC decrypts the WNonce message element to retrieve the 'WTP
4443 Nonce'. The WNonce payload is referred to as ciphertext below:
4444
4445 o If a pre-shared key is used, use AES-D(RK0E, ciphertext).
4446 The plaintext is then considered the 'WTP Nonce'.
4447
4448 o If certificates are used, use d-ac(Kpriv, ciphertext). The
4449 plaintext is then considered the 'WTP Nonce'.
4450
4451 o The AC then uses the KDF function to create a 64-octet session
4452 key (SK). The KDF function used is as follows: KDF-512{'WTP
4453 Nonce' || 'AC Nonce', "LWAPP Key Generation", WTP-MAC ||
4454 AC-MAC}. The KDF function is defined in [<a href="#ref-7" title="&quot;Information technology - Telecommunications and information exchange between systems - Local and metropolitan area networks - Specific requirements - Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) specifications Amendment 6: Medium Access Control (MAC) Security Enhancements&quot;">7</a>]. The SK is split
4455 into SK1C, SK1E, SK1D, and IV, as previously noted.
4456
4457 o The AC creates the Join Confirm.
4458
4459 o The AC adds a MIC to the contents of the Join Confirm using
4460 AES-CMAC(SK1M, Join Confirm) and adds the resulting hash to the
4461 MIC (<a href="#section-6.2.9">Section 6.2.9</a>) message element.
4462
4463 o The AC then transmits the Join Confirm to the WTP.
4464
4465 o Upon receiving the Join Confirm, the WTP uses the following
4466 process:
4467
4468 o The WTP authenticates the Join Confirm through the PSK-MIC
4469 message element. If the Join Confirm cannot be authenticated,
4470 the packet is dropped.
4471
4472
4473
4474
4475
4476 <span class="grey">Calhoun, et al. Historic [Page 80]</span></pre>
4477 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-81" ></span>
4478 <span class="grey"><a href="./rfc5412">RFC 5412</a> Lightweight Access Point Protocol February 2010</span>
4479
4480
4481 o SK1E is now plumbed into the AC and WTP's crypto engine as the
4482 AES-CCM LWAPP control encryption session key. Furthermore, the
4483 random IV is used as the base Initialization Vector. From this
4484 point on, all control protocol payloads between the WTP and AC are
4485 encrypted and authenticated using the new session key.
4486
4487 <span class="h4"><a class="selflink" id="section-10.3.3" href="#section-10.3.3">10.3.3</a>. Refreshing Cryptographic Keys</span>
4488
4489 Since AC-WTP associations will tend to be relatively long-lived, it
4490 is sensible to periodically refresh the encryption and authentication
4491 keys; this is referred to as "rekeying". When the key lifetime
4492 reaches 95% of the configured value, identified in the KeyLifetime
4493 timer (see <a href="#section-12">Section 12</a>), the rekeying will proceed as follows:
4494
4495 o The WTP creates RK0 through the previously defined KDF algorithm:
4496 RK0 = KDF-256{SK1D, "LWAPP PSK Top K0" || Session ID || WTP-MAC ||
4497 AC-MAC}. Note that the difference in this specific instance is
4498 that SK1D that was previously generated is used instead of the
4499 PSK. Note this is used in both the certificate and pre-shared key
4500 modes. The resulting RK0 creates RK0E, RK0M.
4501
4502 o The remaining steps used are identical to the join process, with
4503 the exception that the rekey messages are used instead of join
4504 messages, and the fact that the messages are encrypted using the
4505 previously created SK1E. This means the Join Request is replaced
4506 with the Rekey Request, the Join Response is replaced with the
4507 Rekey Response, etc. The two differences between the rekey and
4508 the join process are:
4509
4510 o The Certificate-WTP and Certificate-AC are not included in the
4511 Rekey-Request and Rekey-Response, respectively.
4512
4513 o Regardless of whether certificates or pre-shared keys were used
4514 in the initial key derivation, the process now uses the pre-
4515 shared key mode only, using SK1D as the "PSK".
4516
4517 o The Key Update Request is sent to the AC.
4518
4519 o The newly created SK1E is now plumbed into the AC and WTP's crypto
4520 engine as the AES-CCM LWAPP control encryption session key.
4521 Furthermore, the new random IV is used as the base Initialization
4522 Vector. From this point on, all control protocol payloads between
4523 the WTP and AC are encrypted and authenticated using the new
4524 session key.
4525
4526
4527
4528
4529
4530
4531
4532 <span class="grey">Calhoun, et al. Historic [Page 81]</span></pre>
4533 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-82" ></span>
4534 <span class="grey"><a href="./rfc5412">RFC 5412</a> Lightweight Access Point Protocol February 2010</span>
4535
4536
4537 If either the WTP or the AC do not receive an expected response by
4538 the time the ResponseTimeout timer expires (see <a href="#section-12">Section 12</a>), the
4539 WTP MUST delete the new and old session information, and reset the
4540 state machine to the Idle state.
4541
4542 Following a rekey process, both the WTP and the AC keep the
4543 previous encryption for 5-10 seconds in order to be able to
4544 process packets that arrive out of order.
4545
4546 <span class="h3"><a class="selflink" id="section-10.4" href="#section-10.4">10.4</a>. Certificate Usage</span>
4547
4548 Validation of the certificates by the AC and WTP is required so that
4549 only an AC may perform the functions of an AC and that only a WTP may
4550 perform the functions of a WTP. This restriction of functions to the
4551 AC or WTP requires that the certificates used by the AC MUST be
4552 distinguishable from the certificate used by the WTP. To accomplish
4553 this differentiation, the x.509v3 certificates MUST include the
4554 Extensions field [<a href="#ref-10" title="&quot;Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile&quot;">10</a>] and MUST include the NetscapeComment [<a href="#ref-11" title="&quot;Netscape-Defined Certificate Extensions&quot;">11</a>]
4555 extension.
4556
4557 For an AC, the value of the NetscapeComment extension MUST be the
4558 string "CAPWAP AC Device Certificate". For a WTP, the value of the
4559 NetscapeComment extension MUST be the string "CAPWAP WTP Device
4560 Certificate".
4561
4562 Part of the LWAPP certificate validation process includes ensuring
4563 that the proper string is included in the NetscapeComment extension,
4564 and only allowing the LWAPP session to be established if the
4565 extension does not represent the same role as the device validating
4566 the certificate. For instance, a WTP MUST NOT accept a certificate
4567 whose NetscapeComment field is set to "CAPWAP WTP Device
4568 Certificate".
4569
4570 <span class="h2"><a class="selflink" id="section-11" href="#section-11">11</a>. IEEE 802.11 Binding</span>
4571
4572 This section defines the extensions required for the LWAPP protocol
4573 to be used with the IEEE 802.11 protocol.
4574
4575 <span class="h3"><a class="selflink" id="section-11.1" href="#section-11.1">11.1</a>. Division of Labor</span>
4576
4577 The LWAPP protocol, when used with IEEE 802.11 devices, requires a
4578 specific behavior from the WTP and the AC, specifically in terms of
4579 which 802.11 protocol functions are handled.
4580
4581 For both the Split and Local MAC approaches, the CAPWAP functions, as
4582 defined in the taxonomy specification, reside in the AC.
4583
4584
4585
4586
4587
4588 <span class="grey">Calhoun, et al. Historic [Page 82]</span></pre>
4589 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-83" ></span>
4590 <span class="grey"><a href="./rfc5412">RFC 5412</a> Lightweight Access Point Protocol February 2010</span>
4591
4592
4593 <span class="h4"><a class="selflink" id="section-11.1.1" href="#section-11.1.1">11.1.1</a>. Split MAC</span>
4594
4595 This section shows the division of labor between the WTP and the AC
4596 in a Split MAC architecture. Figure 3 shows the clear separation of
4597 functionality among LWAPP components.
4598
4599 Function Location
4600 Distribution Service AC
4601 Integration Service AC
4602 Beacon Generation WTP
4603 Probe Response WTP
4604 Power Mgmt/Packet Buffering WTP
4605 Fragmentation/Defragmentation WTP
4606 Assoc/Disassoc/Reassoc AC
4607
4608 802.11e
4609 Classifying AC
4610 Scheduling WTP/AC
4611 Queuing WTP
4612
4613 802.11i
4614 802.1X/EAP AC
4615 Key Management AC
4616 802.11 Encryption/Decryption WTP or AC
4617
4618 Figure 3: Mapping of 802.11 Functions for Split MAC Architecture
4619
4620 The Distribution and Integration services reside on the AC, and
4621 therefore all user data is tunneled between the WTP and the AC. As
4622 noted above, all real-time 802.11 services, including the control
4623 protocol and the beacon and Probe Response frames, are handled on the
4624 WTP.
4625
4626 All remaining 802.11 MAC management frames are supported on the AC,
4627 including the Association Request, which allows the AC to be involved
4628 in the access policy enforcement portion of the 802.11 protocol. The
4629 802.1X and 802.11i key management function are also located on the
4630 AC.
4631
4632 While the admission control component of 802.11e resides on the AC,
4633 the real-time scheduling and queuing functions are on the WTP. Note
4634 that this does not exclude the AC from providing additional policing
4635 and scheduling functionality.
4636
4637 Note that in the following figure, the use of '( - )' indicates that
4638 processing of the frames is done on the WTP.
4639
4640
4641
4642
4643
4644 <span class="grey">Calhoun, et al. Historic [Page 83]</span></pre>
4645 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-84" ></span>
4646 <span class="grey"><a href="./rfc5412">RFC 5412</a> Lightweight Access Point Protocol February 2010</span>
4647
4648
4649 Client WTP AC
4650
4651 Beacon
4652 &lt;-----------------------------
4653 Probe Request
4654 ----------------------------( - )-------------------------&gt;
4655 Probe Response
4656 &lt;-----------------------------
4657 802.11 AUTH/Association
4658 &lt;---------------------------------------------------------&gt;
4659 Add Mobile (Clear Text, 802.1X Only)
4660 &lt;-------------------------&gt;
4661 802.1X Authentication &amp; 802.11i Key Exchange
4662 &lt;---------------------------------------------------------&gt;
4663 Add Mobile (AES-CCMP, PTK=x)
4664 &lt;-------------------------&gt;
4665 802.11 Action Frames
4666 &lt;---------------------------------------------------------&gt;
4667 802.11 DATA (1)
4668 &lt;---------------------------( - )-------------------------&gt;
4669
4670 Figure 4: Split MAC Message Flow
4671
4672 Figure 4 provides an illustration of the division of labor in a Split
4673 MAC architecture. In this example, a WLAN has been created that is
4674 configured for 802.11i, using AES-CCMP for privacy. The following
4675 process occurs:
4676
4677 o The WTP generates the 802.11 beacon frames, using information
4678 provided to it through the Add WLAN (see <a href="#section-11.8.1.1">Section 11.8.1.1</a>) message
4679 element.
4680
4681 o The WTP processes the Probe Request and responds with a
4682 corresponding Probe Response. The problem request is then
4683 forwarded to the AC for optional processing.
4684
4685 o The WTP forwards the 802.11 Authentication and Association frames
4686 to the AC, which is responsible for responding to the client.
4687
4688 o Once the association is complete, the AC transmits an LWAPP Add
4689 Mobile Request to the WTP (see <a href="#section-11.7.1.1">Section 11.7.1.1</a>). In the above
4690 example, the WLAN is configured for 802.1X, and therefore the
4691 '802.1X only' policy bit is enabled.
4692
4693 o If the WTP is providing encryption/decryption services, once the
4694 client has completed the 802.11i key exchange, the AC transmits
4695 another Add Mobile Request to the WTP, stating the security policy
4696 to enforce for the client (in this case AES-CCMP), as well as the
4697
4698
4699
4700 <span class="grey">Calhoun, et al. Historic [Page 84]</span></pre>
4701 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-85" ></span>
4702 <span class="grey"><a href="./rfc5412">RFC 5412</a> Lightweight Access Point Protocol February 2010</span>
4703
4704
4705 encryption key to use. If encryption/decryption is handled in the
4706 AC, the Add Mobile Request would have the encryption policy set to
4707 "Clear Text".
4708
4709 o The WTP forwards any 802.11 Action frames received to the AC.
4710
4711 o All client data frames are tunneled between the WTP and the AC.
4712 Note that the WTP is responsible for encrypting and decrypting
4713 frames, if it was indicated in the Add Mobile Request.
4714
4715 <span class="h4"><a class="selflink" id="section-11.1.2" href="#section-11.1.2">11.1.2</a>. Local MAC</span>
4716
4717 This section shows the division of labor between the WTP and the AC
4718 in a Local MAC architecture. Figure 5 shows the clear separation of
4719 functionality among LWAPP components.
4720
4721 Function Location
4722 Distribution Service WTP
4723 Integration Service WTP
4724 Beacon Generation WTP
4725 Probe Response WTP
4726 Power Mgmt/Packet Buffering WTP
4727 Fragmentation/Defragmentation WTP
4728 Assoc/Disassoc/Reassoc WTP
4729
4730 802.11e
4731 Classifying WTP
4732 Scheduling WTP
4733 Queuing WTP
4734
4735 802.11i
4736 802.1X/EAP AC
4737 Key Management AC
4738 802.11 Encryption/Decryption WTP
4739
4740 Figure 5: Mapping of 802.11 Functions for Local AP Architecture
4741
4742 Given that Distribution and Integration Services exist on the WTP,
4743 client data frames are not forwarded to the AC, with the exception
4744 listed in the following paragraphs.
4745
4746 While the MAC is terminated on the WTP, it is necessary for the AC to
4747 be aware of mobility events within the WTPs. As a consequence, the
4748 WTP MUST forward the 802.11 Association Requests to the AC, and the
4749 AC MAY reply with a failed Association Response if it deems it
4750 necessary.
4751
4752
4753
4754
4755
4756 <span class="grey">Calhoun, et al. Historic [Page 85]</span></pre>
4757 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-86" ></span>
4758 <span class="grey"><a href="./rfc5412">RFC 5412</a> Lightweight Access Point Protocol February 2010</span>
4759
4760
4761 The 802.1X and 802.11i Key Management function resides in the AC.
4762 Therefore, the WTP MUST forward all 802.1X/Key Management frames to
4763 the AC and forward the associated responses to the station.
4764
4765 Note that in the following figure, the use of '( - )' indicates that
4766 processing of the frames is done on the WTP.
4767
4768
4769 Client WTP AC
4770
4771 Beacon
4772 &lt;-----------------------------
4773 Probe
4774 &lt;----------------------------&gt;
4775 802.11 AUTH
4776 &lt;-----------------------------
4777 802.11 Association
4778 &lt;---------------------------( - )-------------------------&gt;
4779 Add Mobile (Clear Text, 802.1X Only)
4780 &lt;-------------------------&gt;
4781 802.1X Authentication &amp; 802.11i Key Exchange
4782 &lt;---------------------------------------------------------&gt;
4783 802.11 Action Frames
4784 &lt;---------------------------------------------------------&gt;
4785 Add Mobile (AES-CCMP, PTK=x)
4786 &lt;-------------------------&gt;
4787 802.11 DATA
4788 &lt;-----------------------------&gt;
4789
4790 Figure 6: Local MAC Message Flow
4791
4792 Figure 6 provides an illustration of the division of labor in a Local
4793 MAC architecture. In this example, a WLAN has been created that is
4794 configured for 802.11i, using AES-CCMP for privacy. The following
4795 process occurs:
4796
4797 o The WTP generates the 802.11 beacon frames, using information
4798 provided to it through the Add WLAN (see <a href="#section-11.8.1.1">Section 11.8.1.1</a>) message
4799 element.
4800
4801 o The WTP processes the Probe Request and responds with a
4802 corresponding Probe Response.
4803
4804 o The WTP forwards the 802.11 Authentication and Association frames
4805 to the AC, which is responsible for responding to the client.
4806
4807
4808
4809
4810
4811
4812 <span class="grey">Calhoun, et al. Historic [Page 86]</span></pre>
4813 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-87" ></span>
4814 <span class="grey"><a href="./rfc5412">RFC 5412</a> Lightweight Access Point Protocol February 2010</span>
4815
4816
4817 o Once the association is complete, the AC transmits an LWAPP Add
4818 Mobile Request to the WTP (see <a href="#section-11.7.1.1">Section 11.7.1.1</a>. In the above
4819 example, the WLAN is configured for 802.1X, and therefore the
4820 '802.1X only' policy bit is enabled.
4821
4822 o The WTP forwards all 802.1X and 802.11i key exchange messages to
4823 the AC for processing.
4824
4825 o The AC transmits another Add Mobile Request to the WTP, stating
4826 the security policy to enforce for the client (in this case, AES-
4827 CCMP), as well as the encryption key to use. The Add Mobile
4828 Request MAY include a VLAN name, which when present is used by the
4829 WTP to identify the VLAN on which the user's data frames are to be
4830 bridged.
4831
4832 o The WTP forwards any 802.11 Action frames received to the AC.
4833
4834 o The WTP locally bridges all client data frames, and provides the
4835 necessary encryption and decryption services.
4836
4837 <span class="h3"><a class="selflink" id="section-11.2" href="#section-11.2">11.2</a>. Roaming Behavior and 802.11 Security</span>
4838
4839 It is important that LWAPP implementations react properly to mobile
4840 devices associating to the networks in how they generate Add Mobile
4841 and Delete Mobile messages. This section expands upon the examples
4842 provided in the previous section, and describes how the LWAPP control
4843 protocol is used in order to provide secure roaming.
4844
4845 Once a client has successfully associated with the network in a
4846 secure fashion, it is likely to attempt to roam to another access
4847 point. Figure 7 shows an example of a currently associated station
4848 moving from its "Old WTP" to a new "WTP". The figure is useful for
4849 multiple different security policies, including standard 802.1X and
4850 dynamic WEP keys, WPA or even WPA2 both with key caching (where the
4851 802.1x exchange would be bypassed) and without.
4852
4853
4854
4855
4856
4857
4858
4859
4860
4861
4862
4863
4864
4865
4866
4867
4868 <span class="grey">Calhoun, et al. Historic [Page 87]</span></pre>
4869 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-88" ></span>
4870 <span class="grey"><a href="./rfc5412">RFC 5412</a> Lightweight Access Point Protocol February 2010</span>
4871
4872
4873 Client Old WTP WTP AC
4874
4875 Association Request/Response
4876 &lt;--------------------------------------( - )--------------&gt;
4877 Add Mobile (Clear Text, 802.1X Only)
4878 &lt;----------------&gt;
4879 802.1X Authentication (if no key cache entry exists)
4880 &lt;--------------------------------------( - )--------------&gt;
4881 802.11i 4-way Key Exchange
4882 &lt;--------------------------------------( - )--------------&gt;
4883 Delete Mobile
4884 &lt;----------------------------------&gt;
4885 Add Mobile (AES-CCMP, PTK=x)
4886 &lt;----------------&gt;
4887
4888 Figure 7: Client Roaming Example
4889
4890 <span class="h3"><a class="selflink" id="section-11.3" href="#section-11.3">11.3</a>. Transport-Specific Bindings</span>
4891
4892 All LWAPP transports have the following IEEE 802.11 specific
4893 bindings:
4894
4895 <span class="h4"><a class="selflink" id="section-11.3.1" href="#section-11.3.1">11.3.1</a>. Status and WLANS Field</span>
4896
4897 The interpretation of this 16-bit field depends on the direction of
4898 transmission of the packet. Refer to the figure in <a href="#section-3.1">Section 3.1</a>.
4899
4900 Status
4901
4902 When an LWAPP packet is transmitted from a WTP to an AC, this field
4903 is called the Status field and indicates radio resource information
4904 associated with the frame. When the message is an LWAPP control
4905 message this field is transmitted as zero.
4906
4907 The Status field is divided into the signal strength and signal-to-
4908 noise ratio with which an IEEE 802.11 frame was received, encoded in
4909 the following manner:
4910
4911 0 1
4912 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5
4913 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
4914 | RSSI | SNR |
4915 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
4916
4917 RSSI: RSSI is a signed, 8-bit value. It is the received signal
4918 strength indication, in dBm.
4919
4920
4921
4922
4923
4924 <span class="grey">Calhoun, et al. Historic [Page 88]</span></pre>
4925 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-89" ></span>
4926 <span class="grey"><a href="./rfc5412">RFC 5412</a> Lightweight Access Point Protocol February 2010</span>
4927
4928
4929 SNR: SNR is a signed, 8-bit value. It is the signal-to-noise ratio
4930 of the received IEEE 802.11 frame, in dB.
4931
4932 WLANs field: When an LWAPP data message is transmitted from an AC
4933 to a WTP, this 16-bit field indicates on which WLANs the
4934 encapsulated IEEE 802.11 frame is to be transmitted. For unicast
4935 packets, this field is not used by the WTP. For broadcast or
4936 multicast packets, the WTP might require this information if it
4937 provides encryption services.
4938
4939 Given that a single broadcast or multicast packet might need to be
4940 sent to multiple wireless LANs (presumably each with a different
4941 broadcast key), this field is defined as a bit field. A bit set
4942 indicates a WLAN ID (see <a href="#section-11.8.1.1">Section 11.8.1.1</a>), which will be sent the
4943 data. The WLANS field is encoded in the following manner:
4944
4945 0 1
4946 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5
4947 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
4948 | WLAN ID(s) |
4949 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
4950
4951 <span class="h3"><a class="selflink" id="section-11.4" href="#section-11.4">11.4</a>. BSSID to WLAN ID Mapping</span>
4952
4953 The LWAPP protocol makes assumptions regarding the BSSIDs used on the
4954 WTP. It is a requirement for the WTP to use a contiguous block of
4955 BSSIDs. The WLAN Identifier field, which is managed by the AC, is
4956 used as an offset into the BSSID list.
4957
4958 For instance, if a WTP had a base BSSID address of 00:01:02:00:00:00,
4959 and the AC sent an Add WLAN message with a WLAN Identifier of 2 (see
4960 <a href="#section-11.8.1.1">Section 11.8.1.1</a>), the BSSID for the specific WLAN on the WTP would
4961 be 00:01:02:00:00:02.
4962
4963 The WTP communicates the maximum number of BSSIDs that it supports
4964 during the Config Request within the IEEE 802.11 WTP WLAN Radio
4965 Configuration message element (see <a href="#section-11.9.1">Section 11.9.1</a>).
4966
4967 <span class="h3"><a class="selflink" id="section-11.5" href="#section-11.5">11.5</a>. Quality of Service</span>
4968
4969 It is recommended that 802.11 MAC management be sent by both the AC
4970 and the WTP with appropriate Quality-of-Service (QoS) values,
4971 ensuring that congestion in the network minimizes occurrences of
4972 packet loss. Therefore, a QoS-enabled LWAPP device should use:
4973
4974 802.1P: The precedence value of 6 SHOULD be used for all 802.11 MAC
4975 management messages, except for Probe Requests, which SHOULD use
4976 4.
4977
4978
4979
4980 <span class="grey">Calhoun, et al. Historic [Page 89]</span></pre>
4981 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-90" ></span>
4982 <span class="grey"><a href="./rfc5412">RFC 5412</a> Lightweight Access Point Protocol February 2010</span>
4983
4984
4985 DSCP: The DSCP tag value of 46 SHOULD be used for all 802.11 MAC
4986 management messages, except for Probe Requests, which SHOULD use
4987 34.
4988
4989 <span class="h3"><a class="selflink" id="section-11.6" href="#section-11.6">11.6</a>. Data Message Bindings</span>
4990
4991 There are no LWAPP data message bindings for IEEE 802.11.
4992
4993 <span class="h3"><a class="selflink" id="section-11.7" href="#section-11.7">11.7</a>. Control Message Bindings</span>
4994
4995 The IEEE 802.11 binding has the following control message
4996 definitions.
4997
4998 <span class="h4"><a class="selflink" id="section-11.7.1" href="#section-11.7.1">11.7.1</a>. Mobile Config Request</span>
4999
5000 This section contains the 802.11-specific message elements that are
5001 used with the Mobile Config Request.
5002
5003 <span class="h5"><a class="selflink" id="section-11.7.1.1" href="#section-11.7.1.1">11.7.1.1</a>. Add Mobile</span>
5004
5005 The Add Mobile Request is used by the AC to inform a WTP that it
5006 should forward traffic from a particular mobile station. The Add
5007 Mobile Request may also include security parameters that must be
5008 enforced by the WTP for the particular mobile.
5009
5010 When the AC sends an Add Mobile Request, it includes any security
5011 parameters that may be required. An AC that wishes to update a
5012 mobile's policy on a WTP may do so by simply sending a new Add Mobile
5013 message element.
5014
5015 When a WTP receives an Add Mobile message element, it must first
5016 override any existing state it may have for the mobile station in
5017 question. The latest Add Mobile overrides any previously received
5018 messages. If the Add Mobile message element's EAP-Only bit is set,
5019 the WTP MUST drop all 802.11 packets that do not contain EAP packets.
5020 Note that when EAP Only is set, the Encryption Policy field MAY have
5021 additional values, and therefore it is possible to inform a WTP to
5022 only accept encrypted EAP packets. Once the mobile station has
5023 successfully completed EAP authentication, the AC must send a new Add
5024 Mobile message element to push the session key down to the WTP as
5025 well as to remove the EAP Only restriction.
5026
5027 If the QoS field is set, the WTP MUST observe and provide policing of
5028 the 802.11e priority tag to ensure that it does not exceed the value
5029 provided by the AC.
5030
5031
5032
5033
5034
5035
5036 <span class="grey">Calhoun, et al. Historic [Page 90]</span></pre>
5037 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-91" ></span>
5038 <span class="grey"><a href="./rfc5412">RFC 5412</a> Lightweight Access Point Protocol February 2010</span>
5039
5040
5041 0 1 2 3
5042 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
5043 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
5044 | Radio ID | Association ID | MAC Address |
5045 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
5046 | MAC Address |
5047 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
5048 | MAC Address |E|C| Encryption Policy |
5049 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
5050 |Encrypt Policy | Session Key... |
5051 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
5052 | Pairwise TSC... |
5053 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
5054 | Pairwise RSC... |
5055 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
5056 | Capabilities | WLAN ID | WME Mode |
5057 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
5058 | 802.11e Mode | Qos | Supported Rates |
5059 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
5060 | Supported Rates |
5061 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
5062 | VLAN Name...
5063 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
5064
5065 Type: 29 for Add Mobile
5066
5067 Length: 36
5068
5069 Radio ID: An 8-bit value representing the radio.
5070
5071 Association ID: A 16-bit value specifying the 802.11 Association
5072 Identifier.
5073
5074 MAC Address: The mobile station's MAC address.
5075
5076 E: The 1-bit field is set by the AC to inform the WTP that it MUST
5077 NOT accept any 802.11 data frames, other than 802.1X frames. This
5078 is the equivalent of the WTP's 802.1X port for the mobile station
5079 to be in the closed state. When set, the WTP MUST drop any
5080 non-802.1X packets it receives from the mobile station.
5081
5082 C: The 1-bit field is set by the AC to inform the WTP that
5083 encryption services will be provided by the AC. When set, the WTP
5084 SHOULD police frames received from stations to ensure that they
5085 comply to the stated encryption policy, but does not need to take
5086 specific cryptographic action on the frame. Similarly, for
5087 transmitted frames, the WTP only needs to forward already
5088 encrypted frames.
5089
5090
5091
5092 <span class="grey">Calhoun, et al. Historic [Page 91]</span></pre>
5093 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-92" ></span>
5094 <span class="grey"><a href="./rfc5412">RFC 5412</a> Lightweight Access Point Protocol February 2010</span>
5095
5096
5097 Encryption Policy: The policy field informs the WTP how to handle
5098 packets from/to the mobile station. The following values are
5099 supported:
5100
5101 0 - Encrypt WEP 104: All packets to/from the mobile station must
5102 be encrypted using a standard 104-bit WEP.
5103
5104 1 - Clear Text: All packets to/from the mobile station do not
5105 require any additional crypto processing by the WTP.
5106
5107 2 - Encrypt WEP 40: All packets to/from the mobile station must
5108 be encrypted using a standard 40-bit WEP.
5109
5110 3 - Encrypt WEP 128: All packets to/from the mobile station must
5111 be encrypted using a standard 128-bit WEP.
5112
5113 4 - Encrypt AES-CCMP 128: All packets to/from the mobile station
5114 must be encrypted using a 128-bit AES-CCMP [<a href="#ref-7" title="&quot;Information technology - Telecommunications and information exchange between systems - Local and metropolitan area networks - Specific requirements - Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) specifications Amendment 6: Medium Access Control (MAC) Security Enhancements&quot;">7</a>].
5115
5116 5 - Encrypt TKIP-MIC: All packets to/from the mobile station must
5117 be encrypted using Temporal Key Integrity Protocol (TKIP) and
5118 authenticated using Michael [<a href="#ref-16" title="&quot;WiFi Protected Access (WPA) rev 1.6&quot;">16</a>].
5119
5120 Session Key: A 32-octet session key the WTP is to use when
5121 encrypting traffic to or decrypting traffic from the mobile
5122 station. The type of key is determined based on the Encryption
5123 Policy field.
5124
5125 Pairwise TSC: The TKIP Sequence Counter (TSC) to use for unicast
5126 packets transmitted to the mobile.
5127
5128 Pairwise RSC: The Receive Sequence Counter (RSC) to use for unicast
5129 packets received from the mobile.
5130
5131 Capabilities: A 16-bit field containing the 802.11 capabilities to
5132 use with the mobile.
5133
5134 WLAN ID: An 8-bit value specifying the WLAN Identifier.
5135
5136 WME Mode: An 8-bit Boolean used to identify whether the station is
5137 WME capable. A value of zero is used to indicate that the station
5138 is not Wireless Multimedia Extension (WME) capable, while a value
5139 of one means that the station is WME capable.
5140
5141 802.11e Mode: An 8-bit Boolean used to identify whether the station
5142 is 802.11e-capable. A value of zero is used to indicate that the
5143 station is not 802.11e-capable, while a value of one means that
5144 the station is 802.11e-capable.
5145
5146
5147
5148 <span class="grey">Calhoun, et al. Historic [Page 92]</span></pre>
5149 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-93" ></span>
5150 <span class="grey"><a href="./rfc5412">RFC 5412</a> Lightweight Access Point Protocol February 2010</span>
5151
5152
5153 QoS: An 8-bit value specifying the QoS policy to enforce for the
5154 station. The following values are supported: PRC: TO CHECK
5155
5156 0 - Silver (Best Effort)
5157
5158 1 - Gold (Video)
5159
5160 2 - Platinum (Voice)
5161
5162 3 - Bronze (Background)
5163
5164 Supported Rates: The supported rates to be used with the mobile
5165 station.
5166
5167 VLAN Name: An optional variable string containing the VLAN Name on
5168 which the WTP is to locally bridge user data. Note that this
5169 field is only valid with Local MAC WTPs.
5170
5171 <span class="h5"><a class="selflink" id="section-11.7.1.2" href="#section-11.7.1.2">11.7.1.2</a>. IEEE 802.11 Mobile Session Key</span>
5172
5173 The Mobile Session Key Payload message element is sent when the AC
5174 determines that encryption of a mobile station must be performed in
5175 the WTP. This message element MUST NOT be present without the Add
5176 Mobile message element, and MUST NOT be sent if the WTP had not
5177 specifically advertised support for the requested encryption scheme
5178 (see <a href="#section-11.7.1.1">Section 11.7.1.1</a>).
5179
5180 0 1 2 3
5181 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
5182 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
5183 | MAC Address |
5184 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
5185 | MAC Address | Encryption Policy |
5186 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
5187 | Encryption Policy | Session Key... |
5188 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
5189
5190 Type: 105 for IEEE 802.11 Mobile Session Key
5191
5192 Length: &gt;= 11
5193
5194 MAC Address: The mobile station's MAC address.
5195
5196 Encryption Policy: The policy field informs the WTP how to handle
5197 packets from/to the mobile station. The following values are
5198 supported:
5199
5200
5201
5202
5203
5204 <span class="grey">Calhoun, et al. Historic [Page 93]</span></pre>
5205 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-94" ></span>
5206 <span class="grey"><a href="./rfc5412">RFC 5412</a> Lightweight Access Point Protocol February 2010</span>
5207
5208
5209 0 - Encrypt WEP 104: All packets to/from the mobile station must
5210 be encrypted using a standard 104-bit WEP.
5211
5212 1 - Clear Text: All packets to/from the mobile station do not
5213 require any additional crypto processing by the WTP.
5214
5215 2 - Encrypt WEP 40: All packets to/from the mobile station must
5216 be encrypted using a standard 40-bit WEP.
5217
5218 3 - Encrypt WEP 128: All packets to/from the mobile station must
5219 be encrypted using a standard 128-bit WEP.
5220
5221 4 - Encrypt AES-CCMP 128: All packets to/from the mobile station
5222 must be encrypted using a 128-bit AES-CCMP [<a href="#ref-7" title="&quot;Information technology - Telecommunications and information exchange between systems - Local and metropolitan area networks - Specific requirements - Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) specifications Amendment 6: Medium Access Control (MAC) Security Enhancements&quot;">7</a>].
5223
5224 5 - Encrypt TKIP-MIC: All packets to/from the mobile station must
5225 be encrypted using TKIP and authenticated using Michael [<a href="#ref-16" title="&quot;WiFi Protected Access (WPA) rev 1.6&quot;">16</a>].
5226
5227 Session Key: The session key the WTP is to use when encrypting
5228 traffic to/from the mobile station.
5229
5230 <span class="h5"><a class="selflink" id="section-11.7.1.3" href="#section-11.7.1.3">11.7.1.3</a>. Station QoS Profile</span>
5231
5232 The Station QoS Profile Payload message element contains the maximum
5233 802.11e priority tag that may be used by the station. Any packets
5234 received that exceed the value encoded in this message element must
5235 either be dropped or tagged using the maximum value permitted to the
5236 user. The priority tag must be between zero (0) and seven (7).
5237
5238 0 1 2 3
5239 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
5240 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
5241 | MAC Address |
5242 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
5243 | MAC Address | 802.1P Precedence Tag |
5244 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
5245
5246 Type: 140 for IEEE 802.11 Station QoS Profile
5247
5248 Length: 12
5249
5250 MAC Address: The mobile station's MAC address.
5251
5252 802.1P Precedence Tag: The maximum 802.1P precedence value that the
5253 WTP will allow in the Traffic Identifier (TID) field in the
5254 extended 802.11e QoS Data header.
5255
5256
5257
5258
5259
5260 <span class="grey">Calhoun, et al. Historic [Page 94]</span></pre>
5261 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-95" ></span>
5262 <span class="grey"><a href="./rfc5412">RFC 5412</a> Lightweight Access Point Protocol February 2010</span>
5263
5264
5265 <span class="h5"><a class="selflink" id="section-11.7.1.4" href="#section-11.7.1.4">11.7.1.4</a>. IEEE 802.11 Update Mobile QoS</span>
5266
5267 The Update Mobile QoS message element is used to change the Quality-
5268 of-Service policy on the WTP for a given mobile station.
5269
5270 0 1 2 3
5271 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
5272 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
5273 | Radio ID | Association ID | MAC Address |
5274 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
5275 | MAC Address |
5276 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
5277 | MAC Address | QoS Profile | Vlan Identifier |
5278 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
5279 | DSCP Tag | 802.1P Tag |
5280 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
5281
5282 Type: 106 for IEEE 802.11 Update Mobile QoS
5283
5284 Length: 14
5285
5286 Radio ID: The Radio Identifier, typically refers to some interface
5287 index on the WTP.
5288
5289 Association ID: The 802.11 Association Identifier.
5290
5291 MAC Address: The mobile station's MAC address.
5292
5293 QoS Profile: An 8-bit value specifying the QoS policy to enforce
5294 for the station. The following values are supported:
5295
5296 0 - Silver (Best Effort)
5297
5298 1 - Gold (Video)
5299
5300 2 - Platinum (Voice)
5301
5302 3 - Bronze (Background)
5303
5304 VLAN Identifier: PRC.
5305
5306 DSCP Tag: The DSCP label to use if packets are to be DSCP tagged.
5307
5308 802.1P Tag: The 802.1P precedence value to use if packets are to be
5309 802.1P-tagged.
5310
5311
5312
5313
5314
5315
5316 <span class="grey">Calhoun, et al. Historic [Page 95]</span></pre>
5317 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-96" ></span>
5318 <span class="grey"><a href="./rfc5412">RFC 5412</a> Lightweight Access Point Protocol February 2010</span>
5319
5320
5321 <span class="h4"><a class="selflink" id="section-11.7.2" href="#section-11.7.2">11.7.2</a>. WTP Event Request</span>
5322
5323 This section contains the 802.11-specific message elements that are
5324 used with the WTP Event Request message.
5325
5326 <span class="h5"><a class="selflink" id="section-11.7.2.1" href="#section-11.7.2.1">11.7.2.1</a>. IEEE 802.11 Statistics</span>
5327
5328 The Statistics message element is sent by the WTP to transmit its
5329 current statistics. The value contains the following fields:
5330
5331 0 1 2 3
5332 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
5333 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
5334 | Radio ID | Tx Fragment Count |
5335 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
5336 |Tx Fragment Cnt| Multicast Tx Count |
5337 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
5338 | Mcast Tx Cnt | Failed Count |
5339 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
5340 | Failed Count | Retry Count |
5341 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
5342 | Retry Count | Multiple Retry Count |
5343 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
5344 |Multi Retry Cnt| Frame Duplicate Count |
5345 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
5346 | Frame Dup Cnt | RTS Success Count |
5347 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
5348 |RTS Success Cnt| RTS Failure Count |
5349 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
5350 |RTS Failure Cnt| ACK Failure Count |
5351 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
5352 |ACK Failure Cnt| Rx Fragment Count |
5353 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
5354 |Rx Fragment Cnt| Multicast RX Count |
5355 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
5356 | Mcast Rx Cnt | FCS Error Count |
5357 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
5358 | FCS Error Cnt| Tx Frame Count |
5359 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
5360 | Tx Frame Cnt | Decryption Errors |
5361 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
5362 |Decryption Errs|
5363 +-+-+-+-+-+-+-+-+
5364
5365 Type: 38 for Statistics
5366
5367 Length: 57
5368
5369
5370
5371
5372 <span class="grey">Calhoun, et al. Historic [Page 96]</span></pre>
5373 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-97" ></span>
5374 <span class="grey"><a href="./rfc5412">RFC 5412</a> Lightweight Access Point Protocol February 2010</span>
5375
5376
5377 Radio ID: An 8-bit value representing the radio.
5378
5379 Tx Fragment Count: A 32-bit value representing the number of
5380 fragmented frames transmitted.
5381
5382 Multicast Tx Count: A 32-bit value representing the number of
5383 multicast frames transmitted.
5384
5385 Failed Count: A 32-bit value representing the transmit excessive
5386 retries.
5387
5388 Retry Count: A 32-bit value representing the number of transmit
5389 retries.
5390
5391 Multiple Retry Count: A 32-bit value representing the number of
5392 transmits that required more than one retry.
5393
5394 Frame Duplicate Count: A 32-bit value representing the duplicate
5395 frames received.
5396
5397 RTS Success Count: A 32-bit value representing the number of
5398 successfully transmitted Ready To Send (RTS).
5399
5400 RTS Failure Count: A 32-bit value representing the failed
5401 transmitted RTS.
5402
5403 ACK Failure Count: A 32-bit value representing the number of failed
5404 acknowledgements.
5405
5406 Rx Fragment Count: A 32-bit value representing the number of
5407 fragmented frames received.
5408
5409 Multicast RX Count: A 32-bit value representing the number of
5410 multicast frames received.
5411
5412 FCS Error Count: A 32-bit value representing the number of Frame
5413 Check Sequence (FCS) failures.
5414
5415 Decryption Errors: A 32-bit value representing the number of
5416 Decryption errors that occurred on the WTP. Note that this field
5417 is only valid in cases where the WTP provides encryption/
5418 decryption services.
5419
5420 <span class="h3"><a class="selflink" id="section-11.8" href="#section-11.8">11.8</a>. 802.11 Control Messages</span>
5421
5422 This section will define LWAPP control messages that are specific to
5423 the IEEE 802.11 binding.
5424
5425
5426
5427
5428 <span class="grey">Calhoun, et al. Historic [Page 97]</span></pre>
5429 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-98" ></span>
5430 <span class="grey"><a href="./rfc5412">RFC 5412</a> Lightweight Access Point Protocol February 2010</span>
5431
5432
5433 <span class="h4"><a class="selflink" id="section-11.8.1" href="#section-11.8.1">11.8.1</a>. IEEE 802.11 WLAN Config Request</span>
5434
5435 The IEEE 802.11 WLAN Configuration Request is sent by the AC to the
5436 WTP in order to change services provided by the WTP. This control
5437 message is used to either create, update, or delete a WLAN on the
5438 WTP.
5439
5440 The IEEE 802.11 WLAN Configuration Request is sent as a result of
5441 either some manual administrative process (e.g., deleting a WLAN), or
5442 automatically to create a WLAN on a WTP. When sent automatically to
5443 create a WLAN, this control message is sent after the LWAPP
5444 Configuration Request message has been received by the WTP.
5445
5446 Upon receiving this control message, the WTP will modify the
5447 necessary services, and transmit an IEEE 802.11 WLAN Configuration
5448 Response.
5449
5450 An WTP MAY provide service for more than one WLAN: therefore, every
5451 WLAN is identified through a numerical index. For instance, a WTP
5452 that is capable of supporting up to 16 SSIDs could accept up to 16
5453 IEEE 802.11 WLAN Configuration Request messages that include the Add
5454 WLAN message element.
5455
5456 Since the index is the primary identifier for a WLAN, an AC SHOULD
5457 attempt to ensure that the same WLAN is identified through the same
5458 index number on all of its WTPs. An AC that does not follow this
5459 approach MUST find some other means of maintaining a WLAN Identifier
5460 to SSID mapping table.
5461
5462 The following subsections define the message elements that are of
5463 value for this LWAPP operation. Only one message MUST be present.
5464
5465 <span class="h5"><a class="selflink" id="section-11.8.1.1" href="#section-11.8.1.1">11.8.1.1</a>. IEEE 802.11 Add WLAN</span>
5466
5467 The Add WLAN message element is used by the AC to define a wireless
5468 LAN on the WTP. The value contains the following format:
5469
5470
5471
5472
5473
5474
5475
5476
5477
5478
5479
5480
5481
5482
5483
5484 <span class="grey">Calhoun, et al. Historic [Page 98]</span></pre>
5485 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-99" ></span>
5486 <span class="grey"><a href="./rfc5412">RFC 5412</a> Lightweight Access Point Protocol February 2010</span>
5487
5488
5489 0 1 2 3
5490 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
5491 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
5492 | Radio ID | WLAN Capability | WLAN ID |
5493 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
5494 | Encryption Policy |
5495 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
5496 | Key ... |
5497 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
5498 | Key Index | Shared Key | WPA Data Len |WPA IE Data ...|
5499 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
5500 | RSN Data Len |RSN IE Data ...| Reserved .... |
5501 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
5502 | WME Data Len |WME IE Data ...| 11e Data Len |11e IE Data ...|
5503 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
5504 | QoS | Auth Type |Broadcast SSID | Reserved... |
5505 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
5506 | SSID ... |
5507 +-+-+-+-+-+-+-+-+
5508
5509 Type: 7 for IEEE 802.11 Add WLAN
5510
5511 Length: &gt;= 298
5512
5513 Radio ID: An 8-bit value representing the radio.
5514
5515 WLAN Capability: A 16-bit value containing the capabilities to be
5516 advertised by the WTP within the Probe and Beacon messages.
5517
5518 WLAN ID: A 16-bit value specifying the WLAN Identifier.
5519
5520 Encryption Policy: A 32-bit value specifying the encryption scheme
5521 to apply to traffic to and from the mobile station.
5522
5523 The following values are supported:
5524
5525 0 - Encrypt WEP 104: All packets to/from the mobile station must
5526 be encrypted using a standard 104-bit WEP.
5527
5528 1 - Clear Text: All packets to/from the mobile station do not
5529 require any additional crypto processing by the WTP.
5530
5531 2 - Encrypt WEP 40: All packets to/from the mobile station must
5532 be encrypted using a standard 40-bit WEP.
5533
5534 3 - Encrypt WEP 128: All packets to/from the mobile station must
5535 be encrypted using a standard 128-bit WEP.
5536
5537
5538
5539
5540 <span class="grey">Calhoun, et al. Historic [Page 99]</span></pre>
5541 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-100" ></span>
5542 <span class="grey"><a href="./rfc5412">RFC 5412</a> Lightweight Access Point Protocol February 2010</span>
5543
5544
5545 4 - Encrypt AES-CCMP 128: All packets to/from the mobile station
5546 must be encrypted using a 128-bit AES-CCMP [<a href="#ref-7" title="&quot;Information technology - Telecommunications and information exchange between systems - Local and metropolitan area networks - Specific requirements - Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) specifications Amendment 6: Medium Access Control (MAC) Security Enhancements&quot;">7</a>].
5547
5548 5 - Encrypt TKIP-MIC: All packets to/from the mobile station must
5549 be encrypted using TKIP and authenticated using Michael [<a href="#ref-16" title="&quot;WiFi Protected Access (WPA) rev 1.6&quot;">16</a>].
5550
5551 6 - Encrypt CKIP: All packets to/from the mobile station must be
5552 encrypted using Cisco TKIP.
5553
5554 Key: A 32-byte session key to use with the encryption policy.
5555
5556 Key-Index: The Key Index associated with the key.
5557
5558 Shared Key: A 1-byte Boolean that specifies whether the key
5559 included in the Key field is a shared WEP key. A value of zero is
5560 used to state that the key is not a shared WEP key, while a value
5561 of one is used to state that the key is a shared WEP key.
5562
5563 WPA Data Len: Length of the WPA Information Element (IE).
5564
5565 WPA IE: A 32-byte field containing the WPA Information Element.
5566
5567 RSN Data Len: Length of the Robust Security Network (RSN) IE.
5568
5569 RSN IE: A 64-byte field containing the RSN Information Element.
5570
5571 Reserved: A 49-byte reserved field, which MUST be set to zero (0).
5572
5573 WME Data Len: Length of the WME IE.
5574
5575 WME IE: A 32-byte field containing the WME Information Element.
5576
5577 DOT11E Data Len: Length of the 802.11e IE.
5578
5579 DOT11E IE: A 32-byte field containing the 802.11e Information
5580 Element.
5581
5582 QOS: An 8-bit value specifying the QoS policy to enforce for the
5583 station.
5584
5585 The following values are supported:
5586
5587 0 - Silver (Best Effort)
5588
5589 1 - Gold (Video)
5590
5591 2 - Platinum (Voice)
5592
5593
5594
5595
5596 <span class="grey">Calhoun, et al. Historic [Page 100]</span></pre>
5597 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-101" ></span>
5598 <span class="grey"><a href="./rfc5412">RFC 5412</a> Lightweight Access Point Protocol February 2010</span>
5599
5600
5601 3 - Bronze (Background)
5602
5603 Auth Type: An 8-bit value specifying the station's authentication
5604 type.
5605
5606 The following values are supported:
5607
5608 0 - Open System
5609
5610 1 - WEP Shared Key
5611
5612 2 - WPA/WPA2 802.1X
5613
5614 3 - WPA/WPA2 PSK
5615
5616 Broadcast SSID: A Boolean indicating whether the SSID is to be
5617 broadcast by the WTP. A value of zero disables SSID broadcast,
5618 while a value of one enables it.
5619
5620 Reserved: A 40-byte reserved field.
5621
5622 SSID: The SSID attribute is the service set identifier that will be
5623 advertised by the WTP for this WLAN.
5624
5625 <span class="h5"><a class="selflink" id="section-11.8.1.2" href="#section-11.8.1.2">11.8.1.2</a>. IEEE 802.11 Delete WLAN</span>
5626
5627 The Delete WLAN message element is used to inform the WTP that a
5628 previously created WLAN is to be deleted. The value contains the
5629 following fields:
5630
5631 0 1 2
5632 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3
5633 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
5634 | Radio ID | WLAN ID |
5635 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
5636
5637 Type: 28 for IEEE 802.11 Delete WLAN
5638
5639 Length: 3
5640
5641 Radio ID: An 8-bit value representing the radio
5642
5643 WLAN ID: A 16-bit value specifying the WLAN Identifier
5644
5645 <span class="h5"><a class="selflink" id="section-11.8.1.3" href="#section-11.8.1.3">11.8.1.3</a>. IEEE 802.11 Update WLAN</span>
5646
5647 The Update WLAN message element is used by the AC to define a
5648 wireless LAN on the WTP. The value contains the following format:
5649
5650
5651
5652 <span class="grey">Calhoun, et al. Historic [Page 101]</span></pre>
5653 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-102" ></span>
5654 <span class="grey"><a href="./rfc5412">RFC 5412</a> Lightweight Access Point Protocol February 2010</span>
5655
5656
5657 0 1 2 3
5658 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
5659 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
5660 | Radio ID | WLAN ID |Encrypt Policy |
5661 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
5662 | Encryption Policy | Key... |
5663 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
5664 | Key ... |
5665 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
5666 | Key Index | Shared Key | WLAN Capability |
5667 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
5668
5669 Type: 34 for IEEE 802.11 Update WLAN
5670
5671 Length: 43
5672
5673 Radio ID: An 8-bit value representing the radio.
5674
5675 WLAN ID: A 16-bit value specifying the WLAN Identifier.
5676
5677 Encryption Policy: A 32-bit value specifying the encryption scheme
5678 to apply to traffic to and from the mobile station.
5679
5680 The following values are supported:
5681
5682 0 - Encrypt WEP 104: All packets to/from the mobile station must
5683 be encrypted using a standard 104-bit WEP.
5684
5685 1 - Clear Text: All packets to/from the mobile station do not
5686 require any additional crypto processing by the WTP.
5687
5688 2 - Encrypt WEP 40: All packets to/from the mobile station must
5689 be encrypted using a standard 40-bit WEP.
5690
5691 3 - Encrypt WEP 128: All packets to/from the mobile station must
5692 be encrypted using a standard 128-bit WEP.
5693
5694 4 - Encrypt AES-CCMP 128: All packets to/from the mobile station
5695 must be encrypted using a 128-bit AES-CCMP [<a href="#ref-7" title="&quot;Information technology - Telecommunications and information exchange between systems - Local and metropolitan area networks - Specific requirements - Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) specifications Amendment 6: Medium Access Control (MAC) Security Enhancements&quot;">7</a>].
5696
5697 5 - Encrypt TKIP-MIC: All packets to/from the mobile station must
5698 be encrypted using TKIP and authenticated using Michael [<a href="#ref-16" title="&quot;WiFi Protected Access (WPA) rev 1.6&quot;">16</a>].
5699
5700 6 - Encrypt CKIP: All packets to/from the mobile station must be
5701 encrypted using Cisco TKIP.
5702
5703 Key: A 32-byte session key to use with the encryption policy.
5704
5705
5706
5707
5708 <span class="grey">Calhoun, et al. Historic [Page 102]</span></pre>
5709 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-103" ></span>
5710 <span class="grey"><a href="./rfc5412">RFC 5412</a> Lightweight Access Point Protocol February 2010</span>
5711
5712
5713 Key-Index: The Key Index associated with the key.
5714
5715 Shared Key: A 1-byte Boolean that specifies whether the key
5716 included in the Key field is a shared WEP key. A value of zero
5717 means that the key is not a shared WEP key, while a value of one
5718 is used to state that the key is a shared WEP key.
5719
5720 WLAN Capability: A 16-bit value containing the capabilities to be
5721 advertised by the WTP within the Probe and Beacon messages.
5722
5723 <span class="h4"><a class="selflink" id="section-11.8.2" href="#section-11.8.2">11.8.2</a>. IEEE 802.11 WLAN Config Response</span>
5724
5725 The IEEE 802.11 WLAN Configuration Response is sent by the WTP to the
5726 AC as an acknowledgement of the receipt of an IEEE 802.11 WLAN
5727 Configuration Request.
5728
5729 This LWAPP control message does not include any message elements.
5730
5731 <span class="h4"><a class="selflink" id="section-11.8.3" href="#section-11.8.3">11.8.3</a>. IEEE 802.11 WTP Event</span>
5732
5733 The IEEE 802.11 WTP Event LWAPP message is used by the WTP in order
5734 to report asynchronous events to the AC. There is no reply message
5735 expected from the AC, except that the message is acknowledged via the
5736 reliable transport.
5737
5738 When the AC receives the IEEE 802.11 WTP Event, it will take whatever
5739 action is necessary, depending upon the message elements present in
5740 the message.
5741
5742 The IEEE 802.11 WTP Event message MUST contain one of the following
5743 message elements described in the next subsections.
5744
5745 <span class="h5"><a class="selflink" id="section-11.8.3.1" href="#section-11.8.3.1">11.8.3.1</a>. IEEE 802.11 MIC Countermeasures</span>
5746
5747 The MIC Countermeasures message element is sent by the WTP to the AC
5748 to indicate the occurrence of a MIC failure.
5749
5750 0 1 2 3
5751 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
5752 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
5753 | Radio ID | WLAN ID | MAC Address |
5754 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
5755 | MAC Address |
5756 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
5757
5758 Type: 61 for IEEE 802.11 MIC Countermeasures
5759
5760 Length: 8
5761
5762
5763
5764 <span class="grey">Calhoun, et al. Historic [Page 103]</span></pre>
5765 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-104" ></span>
5766 <span class="grey"><a href="./rfc5412">RFC 5412</a> Lightweight Access Point Protocol February 2010</span>
5767
5768
5769 Radio ID: The Radio Identifier, typically refers to some interface
5770 index on the WTP.
5771
5772 WLAN ID: This 8-bit unsigned integer includes the WLAN Identifier,
5773 on which the MIC failure occurred.
5774
5775 MAC Address: The MAC address of the mobile station that caused the
5776 MIC failure.
5777
5778 <span class="h5"><a class="selflink" id="section-11.8.3.2" href="#section-11.8.3.2">11.8.3.2</a>. IEEE 802.11 WTP Radio Fail Alarm Indication</span>
5779
5780 The WTP Radio Fail Alarm Indication message element is sent by the
5781 WTP to the AC when it detects a radio failure.
5782
5783 0 1 2 3
5784 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
5785 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
5786 | Radio ID | Type | Status | Pad |
5787 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
5788
5789 Type: 95 for WTP Radio Fail Alarm Indication
5790
5791 Length: 4
5792
5793 Radio ID: The Radio Identifier, typically refers to some interface
5794 index on the WTP.
5795
5796 Type: The type of radio failure detected. The following values are
5797 supported:
5798
5799 1 - Receiver
5800
5801 2 - Transmitter
5802
5803 Status: An 8-bit Boolean indicating whether the radio failure is
5804 being reported or cleared. A value of zero is used to clear the
5805 event, while a value of one is used to report the event.
5806
5807 Pad: Reserved field MUST be set to zero (0).
5808
5809
5810
5811
5812
5813
5814
5815
5816
5817
5818
5819
5820 <span class="grey">Calhoun, et al. Historic [Page 104]</span></pre>
5821 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-105" ></span>
5822 <span class="grey"><a href="./rfc5412">RFC 5412</a> Lightweight Access Point Protocol February 2010</span>
5823
5824
5825 <span class="h3"><a class="selflink" id="section-11.9" href="#section-11.9">11.9</a>. Message Element Bindings</span>
5826
5827 The IEEE 802.11 Message Element binding has the following
5828 definitions:
5829
5830 Conf Conf Conf Add
5831 Req Resp Upd Mobile
5832
5833 IEEE 802.11 WTP WLAN Radio Configuration X X X
5834 IEEE 802.11 Rate Set X X
5835 IEEE 802.11 Multi-domain Capability X X X
5836 IEEE 802.11 MAC Operation X X X
5837 IEEE 802.11 Tx Power X X X
5838 IEEE 802.11 Tx Power Level X
5839 IEEE 802.11 Direct Sequence Control X X X
5840 IEEE 802.11 OFDM Control X X X
5841 IEEE 802.11 Supported Rates X X
5842 IEEE 802.11 Antenna X X X
5843 IEEE 802.11 CFP Status X X
5844 IEEE 802.11 Broadcast Probe Mode X X
5845 IEEE 802.11 WTP Mode and Type X? X
5846 IEEE 802.11 WTP Quality of Service X X
5847 IEEE 802.11 MIC Error Report From Mobile X
5848 IEEE 802.11 Update Mobile QoS X
5849 IEEE 802.11 Mobile Session Key X
5850
5851 <span class="h4"><a class="selflink" id="section-11.9.1" href="#section-11.9.1">11.9.1</a>. IEEE 802.11 WTP WLAN Radio Configuration</span>
5852
5853 The WTP WLAN radio configuration is used by the AC to configure a
5854 Radio on the WTP. The message element value contains the following
5855 Fields:
5856
5857 0 1 2 3
5858 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
5859 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
5860 | Radio ID | Reserved | Occupancy Limit |
5861 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
5862 | CFP Per | CFP Maximum Duration | BSS ID |
5863 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
5864 | BSS ID |
5865 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
5866 | BSS ID | Beacon Period | DTIM Per |
5867 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
5868 | Country String |
5869 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
5870 | Num Of BSSIDs |
5871 +-+-+-+-+-+-+-+-+
5872
5873
5874
5875
5876 <span class="grey">Calhoun, et al. Historic [Page 105]</span></pre>
5877 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-106" ></span>
5878 <span class="grey"><a href="./rfc5412">RFC 5412</a> Lightweight Access Point Protocol February 2010</span>
5879
5880
5881 Type: 8 for IEEE 802.11 WTP WLAN Radio Configuration
5882
5883 Length: 20
5884
5885 Radio ID: An 8-bit value representing the radio to configure.
5886
5887 Reserved: MUST be set to zero
5888
5889 Occupancy Limit: This attribute indicates the maximum amount of
5890 time, in Time Units (TUs), that a point coordinator MAY control
5891 the usage of the wireless medium without relinquishing control for
5892 long enough to allow at least one instance of Distributed
5893 Coordination Function (DCF) access to the medium. The default
5894 value of this attribute SHOULD be 100, and the maximum value
5895 SHOULD be 1000.
5896
5897 CFP Period: The attribute describes the number of DTIM intervals
5898 between the start of Contention-Free Periods (CFPs).
5899
5900 CFP Maximum Duration: The attribute describes the maximum duration
5901 of the CFP in TU that MAY be generated by the Point Coordination
5902 Function (PCF).
5903
5904 BSSID: The WLAN Radio's base MAC address. For WTPs that support
5905 more than a single WLAN, the value of the WLAN Identifier is added
5906 to the last octet of the BSSID. Therefore, a WTP that supports 16
5907 WLANs MUST have 16 MAC addresses reserved for it, and the last
5908 nibble is used to represent the WLAN ID.
5909
5910 Beacon Period: This attribute specifies the number of TUs that a
5911 station uses for scheduling Beacon transmissions. This value is
5912 transmitted in Beacon and Probe Response frames.
5913
5914 DTIM Period: This attribute specifies the number of Beacon
5915 intervals that elapses between transmission of Beacons frames
5916 containing a TIM element whose DTIM Count field is 0. This value
5917 is transmitted in the DTIM Period field of Beacon frames.
5918
5919 Country Code: This attribute identifies the country in which the
5920 station is operating. The first two octets of this string is the
5921 two-character country code as described in document ISO/IEC 3166-
5922 1. The third octet MUST be one of the following:
5923
5924 1. an ASCII space character, if the regulations under which the
5925 station is operating encompass all environments in the country,
5926
5927 2. an ASCII 'O' character, if the regulations under which the station
5928 is operating are for an outdoor environment only, or
5929
5930
5931
5932 <span class="grey">Calhoun, et al. Historic [Page 106]</span></pre>
5933 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-107" ></span>
5934 <span class="grey"><a href="./rfc5412">RFC 5412</a> Lightweight Access Point Protocol February 2010</span>
5935
5936
5937 3. an ASCII 'I' character, if the regulations under which the station
5938 is operating are for an indoor environment only.
5939
5940 Number of BSSIDs: This attribute contains the maximum number of
5941 BSSIDs supported by the WTP. This value restricts the number of
5942 logical networks supported by the WTP.
5943
5944 <span class="h4"><a class="selflink" id="section-11.9.2" href="#section-11.9.2">11.9.2</a>. IEEE 802.11 Rate Set</span>
5945
5946 The Rate Set message element value is sent by the AC and contains the
5947 supported operational rates. It contains the following fields:
5948
5949 0 1 2 3
5950 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
5951 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
5952 | Radio ID | Rate Set |
5953 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
5954
5955 Type: 16 for IEEE 802.11 Rate Set
5956
5957 Length: 4
5958
5959 Radio ID: An 8-bit value representing the radio to configure.
5960
5961 Rate Set: The AC generates the Rate Set that the WTP is to include
5962 in its Beacon and Probe messages.
5963
5964 <span class="h4"><a class="selflink" id="section-11.9.3" href="#section-11.9.3">11.9.3</a>. IEEE 802.11 Multi-Domain Capability</span>
5965
5966 The Multi-Domain Capability message element is used by the AC to
5967 inform the WTP of regulatory limits. The value contains the
5968 following fields:
5969
5970 0 1 2 3
5971 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
5972 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
5973 | Radio ID | Reserved | First Channel # |
5974 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
5975 | Number of Channels | Max Tx Power Level |
5976 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
5977
5978 Type: 10 for IEEE 802.11 Multi-Domain Capability
5979
5980 Length: 8
5981
5982 Radio ID: An 8-bit value representing the radio to configure.
5983
5984 Reserved: MUST be set to zero
5985
5986
5987
5988 <span class="grey">Calhoun, et al. Historic [Page 107]</span></pre>
5989 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-108" ></span>
5990 <span class="grey"><a href="./rfc5412">RFC 5412</a> Lightweight Access Point Protocol February 2010</span>
5991
5992
5993 First Channel #: This attribute indicates the value of the lowest
5994 channel number in the subband for the associated domain country
5995 string.
5996
5997 Number of Channels: This attribute indicates the value of the total
5998 number of channels allowed in the subband for the associated
5999 domain country string.
6000
6001 Max Tx Power Level: This attribute indicates the maximum transmit
6002 power, in dBm, allowed in the subband for the associated domain
6003 country string.
6004
6005 <span class="h4"><a class="selflink" id="section-11.9.4" href="#section-11.9.4">11.9.4</a>. IEEE 802.11 MAC Operation</span>
6006
6007 The MAC Operation message element is sent by the AC to set the 802.11
6008 MAC parameters on the WTP. The value contains the following fields:
6009
6010 0 1 2 3
6011 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
6012 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
6013 | Radio ID | Reserved | RTS Threshold |
6014 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
6015 | Short Retry | Long Retry | Fragmentation Threshold |
6016 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
6017 | Tx MSDU Lifetime |
6018 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
6019 | Rx MSDU Lifetime |
6020 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
6021
6022 Type: 11 for IEEE 802.11 MAC Operation
6023
6024 Length: 16
6025
6026 Radio ID: An 8-bit value representing the radio to configure.
6027
6028 Reserved: MUST be set to zero
6029
6030 RTS Threshold: This attribute indicates the number of octets in a
6031 Management Protocol Data Unit (MPDU), below which an RTS/CTS
6032 (clear to send) handshake MUST NOT be performed. An RTS/CTS
6033 handshake MUST be performed at the beginning of any frame exchange
6034 sequence where the MPDU is of type Data or Management, the MPDU
6035 has an individual address in the Address1 field, and the length of
6036 the MPDU is greater than this threshold. Setting this attribute
6037 to be larger than the maximum MAC Service Data Unit (MSDU) size
6038 MUST have the effect of turning off the RTS/CTS handshake for
6039 frames of Data or Management type transmitted by this Station
6040 (STA). Setting this attribute to zero MUST have the effect of
6041
6042
6043
6044 <span class="grey">Calhoun, et al. Historic [Page 108]</span></pre>
6045 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-109" ></span>
6046 <span class="grey"><a href="./rfc5412">RFC 5412</a> Lightweight Access Point Protocol February 2010</span>
6047
6048
6049 turning on the RTS/CTS handshake for all frames of Data or
6050 Management type transmitted by this STA. The default value of
6051 this attribute MUST be 2347.
6052
6053 Short Retry: This attribute indicates the maximum number of
6054 transmission attempts of a frame, the length of which is less than
6055 or equal to RTSThreshold, that MUST be made before a failure
6056 condition is indicated. The default value of this attribute MUST
6057 be 7.
6058
6059 Long Retry: This attribute indicates the maximum number of
6060 transmission attempts of a frame, the length of which is greater
6061 than dot11RTSThreshold, that MUST be made before a failure
6062 condition is indicated. The default value of this attribute MUST
6063 be 4.
6064
6065 Fragmentation Threshold: This attribute specifies the current
6066 maximum size, in octets, of the MPDU that MAY be delivered to the
6067 PHY. An MSDU MUST be broken into fragments if its size exceeds
6068 the value of this attribute after adding MAC headers and trailers.
6069 An MSDU or MAC Management Protocol Data Unit (MMPDU) MUST be
6070 fragmented when the resulting frame has an individual address in
6071 the Address1 field, and the length of the frame is larger than
6072 this threshold. The default value for this attribute MUST be the
6073 lesser of 2346 or the aMPDUMaxLength of the attached PHY and MUST
6074 never exceed the lesser of 2346 or the aMPDUMaxLength of the
6075 attached PHY. The value of this attribute MUST never be less than
6076 256.
6077
6078 Tx MSDU Lifetime: This attribute specifies the elapsed time in TU,
6079 after the initial transmission of an MSDU, after which, further
6080 attempts to transmit the MSDU MUST be terminated. The default
6081 value of this attribute MUST be 512.
6082
6083 Rx MSDU Lifetime: This attribute specifies the elapsed time, in TU,
6084 after the initial reception of a fragmented MMPDU or MSDU, after
6085 which, further attempts to reassemble the MMPDU or MSDU MUST be
6086 terminated. The default value MUST be 512.
6087
6088 <span class="h4"><a class="selflink" id="section-11.9.5" href="#section-11.9.5">11.9.5</a>. IEEE 802.11 Tx Power</span>
6089
6090 The Tx Power message element value is bi-directional. When sent by
6091 the WTP, it contains the current power level of the radio in
6092 question. When sent by the AC, it contains the power level to which
6093 the WTP MUST adhere:
6094
6095
6096
6097
6098
6099
6100 <span class="grey">Calhoun, et al. Historic [Page 109]</span></pre>
6101 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-110" ></span>
6102 <span class="grey"><a href="./rfc5412">RFC 5412</a> Lightweight Access Point Protocol February 2010</span>
6103
6104
6105 0 1 2 3
6106 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
6107 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
6108 | Radio ID | Reserved | Current Tx Power |
6109 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
6110
6111 Type: 12 for IEEE 802.11 Tx Power
6112
6113 Length: 4
6114
6115 Radio ID: An 8-bit value representing the radio to configure.
6116
6117 Reserved: MUST be set to zero
6118
6119 Current Tx Power: This attribute contains the transmit output power
6120 in mW.
6121
6122 <span class="h4"><a class="selflink" id="section-11.9.6" href="#section-11.9.6">11.9.6</a>. IEEE 802.11 Tx Power Level</span>
6123
6124 The Tx Power Level message element is sent by the WTP and contains
6125 the different power levels supported. The value contains the
6126 following fields:
6127
6128 0 1 2 3
6129 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
6130 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
6131 | Radio ID | Num Levels | Power Level [n] |
6132 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
6133
6134 Type: 13 for IEEE 802.11 Tx Power Level
6135
6136 Length: &gt;= 4
6137
6138 Radio ID: An 8-bit value representing the radio to configure.
6139
6140 Num Levels: The number of power level attributes.
6141
6142 Power Level: Each power level fields contains a supported power
6143 level, in mW.
6144
6145 <span class="h4"><a class="selflink" id="section-11.9.7" href="#section-11.9.7">11.9.7</a>. IEEE 802.11 Direct Sequence Control</span>
6146
6147 The Direct Sequence Control message element is a bi-directional
6148 element. When sent by the WTP, it contains the current state. When
6149 sent by the AC, the WTP MUST adhere to the values. This element is
6150 only used for 802.11b radios. The value has the following fields.
6151
6152
6153
6154
6155
6156 <span class="grey">Calhoun, et al. Historic [Page 110]</span></pre>
6157 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-111" ></span>
6158 <span class="grey"><a href="./rfc5412">RFC 5412</a> Lightweight Access Point Protocol February 2010</span>
6159
6160
6161 0 1 2 3
6162 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
6163 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
6164 | Radio ID | Reserved | Current Chan | Current CCA |
6165 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
6166 | Energy Detect Threshold |
6167 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
6168
6169 Type: 14 for IEEE 802.11 Direct Sequence Control
6170
6171 Length: 8
6172
6173 Radio ID: An 8-bit value representing the radio to configure.
6174
6175 Reserved: MUST be set to zero
6176
6177 Current Channel: This attribute contains the current operating
6178 frequency channel of the Direct Sequence Spread Spectrum (DSSS)
6179 PHY.
6180
6181 Current CCA: The current Controlled Channel Access (CCA) method in
6182 operation. Valid values are:
6183
6184 1 - energy detect only (edonly)
6185
6186 2 - carrier sense only (csonly)
6187
6188 4 - carrier sense and energy detect (edandcs)
6189
6190 8 - carrier sense with timer (cswithtimer)
6191
6192 16 - high-rate carrier sense and energy detect (hrcsanded)
6193
6194 Energy Detect Threshold: The current Energy Detect Threshold being
6195 used by the DSSS PHY.
6196
6197 <span class="h4"><a class="selflink" id="section-11.9.8" href="#section-11.9.8">11.9.8</a>. IEEE 802.11 OFDM Control</span>
6198
6199 The Orthogonal Frequency Division Multiplexing (OFDM) Control message
6200 element is a bi-directional element. When sent by the WTP, it
6201 contains the current state. When sent by the AC, the WTP MUST adhere
6202 to the values. This element is only used for 802.11a radios. The
6203 value contains the following fields:
6204
6205
6206
6207
6208
6209
6210
6211
6212 <span class="grey">Calhoun, et al. Historic [Page 111]</span></pre>
6213 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-112" ></span>
6214 <span class="grey"><a href="./rfc5412">RFC 5412</a> Lightweight Access Point Protocol February 2010</span>
6215
6216
6217 0 1 2 3
6218 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
6219 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
6220 | Radio ID | Reserved | Current Chan | Band Support |
6221 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
6222 | TI Threshold |
6223 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
6224
6225 Type: 15 for IEEE 802.11 OFDM Control
6226
6227 Length: 8
6228
6229 Radio ID: An 8-bit value representing the radio to configure.
6230
6231 Reserved: MUST be set to zero
6232
6233 Current Channel: This attribute contains the current operating
6234 frequency channel of the OFDM PHY.
6235
6236 Band Supported: The capability of the OFDM PHY implementation to
6237 operate in the three U-NII bands. Coded as an integer value of a
6238 3-bit field as follows:
6239
6240 Bit 0 - capable of operating in the lower (5.15-5.25 GHz) U-NII
6241 band
6242
6243 Bit 1 - capable of operating in the middle (5.25-5.35 GHz) U-NII
6244 band
6245
6246 Bit 2 - capable of operating in the upper (5.725-5.825 GHz) U-NII
6247 band
6248
6249 For example, for an implementation capable of operating in the
6250 lower and mid bands, this attribute would take the value.
6251
6252 TI Threshold: The threshold being used to detect a busy medium
6253 (frequency). CCA MUST report a busy medium upon detecting the
6254 RSSI above this threshold.
6255
6256 <span class="h4"><a class="selflink" id="section-11.9.9" href="#section-11.9.9">11.9.9</a>. IEEE 802.11 Antenna</span>
6257
6258 The Antenna message element is communicated by the WTP to the AC to
6259 provide information on the antennas available. The AC MAY use this
6260 element to reconfigure the WTP's antennas. The value contains the
6261 following fields:
6262
6263
6264
6265
6266
6267
6268 <span class="grey">Calhoun, et al. Historic [Page 112]</span></pre>
6269 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-113" ></span>
6270 <span class="grey"><a href="./rfc5412">RFC 5412</a> Lightweight Access Point Protocol February 2010</span>
6271
6272
6273 0 1 2 3
6274 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
6275 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
6276 | Radio ID | Diversity | Combiner | Antenna Cnt |
6277 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
6278 | Antenna Selection [0..N] |
6279 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
6280
6281 Type: 41 for IEEE 802.11 Antenna
6282
6283 Length: &gt;= 8
6284
6285 Radio ID: An 8-bit value representing the radio to configure.
6286
6287 Diversity: An 8-bit value specifying whether the antenna is to
6288 provide receive diversity. The following values are supported:
6289
6290 0 - Disabled
6291
6292 1 - Enabled (may only be true if the antenna can be used as a
6293 receive antenna)
6294
6295 Combiner: An 8-bit value specifying the combiner selection. The
6296 following values are supported:
6297
6298 1 - Sectorized (Left)
6299
6300 2 - Sectorized (Right)
6301
6302 3 - Omni
6303
6304 4 - Mimo
6305
6306 Antenna Count: An 8-bit value specifying the number of Antenna
6307 Selection fields.
6308
6309 Antenna Selection: One 8-bit antenna configuration value per
6310 antenna in the WTP. The following values are supported:
6311
6312 1 - Internal Antenna
6313
6314 2 - External Antenna
6315
6316 <span class="h4"><a class="selflink" id="section-11.9.10" href="#section-11.9.10">11.9.10</a>. IEEE 802.11 Supported Rates</span>
6317
6318 The Supported Rates message element is sent by the WTP to indicate
6319 the rates that it supports. The value contains the following fields:
6320
6321
6322
6323
6324 <span class="grey">Calhoun, et al. Historic [Page 113]</span></pre>
6325 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-114" ></span>
6326 <span class="grey"><a href="./rfc5412">RFC 5412</a> Lightweight Access Point Protocol February 2010</span>
6327
6328
6329 0 1 2 3
6330 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
6331 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
6332 | Radio ID | Supported Rates |
6333 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
6334
6335 Type: 16 for IEEE 802.11 Supported Rates
6336
6337 Length: 4
6338
6339 Radio ID: An 8-bit value representing the radio.
6340
6341 Supported Rates: The WTP includes the Supported Rates that its
6342 hardware supports. The format is identical to the Rate Set
6343 message element.
6344
6345 <span class="h4"><a class="selflink" id="section-11.9.11" href="#section-11.9.11">11.9.11</a>. IEEE 802.11 CFP Status</span>
6346
6347 The CFP Status message element is sent to provide the CF Polling
6348 configuration.
6349
6350 0 1
6351 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5
6352 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
6353 | Radio ID | Status |
6354 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
6355
6356 Type: 48 for IEEE 802.11 CFP Status
6357
6358 Length: 2
6359
6360 Radio ID: The Radio Identifier, typically refers to some interface
6361 index on the WTP.
6362
6363 Status: An 8-bit Boolean containing the status of the CF Polling
6364 feature. A value of zero disables CFP Status, while a value of
6365 one enables it.
6366
6367 <span class="h4"><a class="selflink" id="section-11.9.12" href="#section-11.9.12">11.9.12</a>. IEEE 802.11 WTP Mode and Type</span>
6368
6369 The WTP Mode and Type message element is used to configure a WTP to
6370 operate in a specific mode.
6371
6372 0 1
6373 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5
6374 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
6375 | Mode | Type |
6376 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
6377
6378
6379
6380 <span class="grey">Calhoun, et al. Historic [Page 114]</span></pre>
6381 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-115" ></span>
6382 <span class="grey"><a href="./rfc5412">RFC 5412</a> Lightweight Access Point Protocol February 2010</span>
6383
6384
6385 Type: 54 for IEEE 802.11 WTP Mode and Type
6386
6387 Length: 2
6388
6389 Mode: An 8-bit value describing the type of information being sent.
6390 The following values are supported:
6391
6392 0 - Split MAC
6393
6394 2 - Local MAC
6395
6396 Type: The type field is not currently used.
6397
6398 <span class="h4"><a class="selflink" id="section-11.9.13" href="#section-11.9.13">11.9.13</a>. IEEE 802.11 Broadcast Probe Mode</span>
6399
6400 The Broadcast Probe Mode message element indicates whether a WTP will
6401 respond to NULL SSID Probe requests. Since broadcast NULL Probes are
6402 not sent to a specific BSSID, the WTP cannot know which SSID the
6403 sending station is querying. Therefore, this behavior must be global
6404 to the WTP.
6405
6406 0
6407 0 1 2 3 4 5 6 7
6408 +-+-+-+-+-+-+-+-+
6409 | Status |
6410 +-+-+-+-+-+-+-+-+
6411
6412 Type: 51 for IEEE 802.11 Broadcast Probe Mode
6413
6414 Length: 1
6415
6416 Status: An 8-bit Boolean indicating the status of whether a WTP
6417 shall respond to a NULL SSID Probe request. A value of zero
6418 disables the NULL SSID Probe response, while a value of one
6419 enables it.
6420
6421 <span class="h4"><a class="selflink" id="section-11.9.14" href="#section-11.9.14">11.9.14</a>. IEEE 802.11 WTP Quality of Service</span>
6422
6423 The WTP Quality of Service message element value is sent by the AC to
6424 the WTP to communicate quality-of-service configuration information.
6425
6426 0 1
6427 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5
6428 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
6429 | Radio ID | Tag Packets |
6430 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
6431
6432 Type: 57 for IEEE 802.11 WTP Quality of Service
6433
6434
6435
6436 <span class="grey">Calhoun, et al. Historic [Page 115]</span></pre>
6437 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-116" ></span>
6438 <span class="grey"><a href="./rfc5412">RFC 5412</a> Lightweight Access Point Protocol February 2010</span>
6439
6440
6441 Length: 12
6442
6443 Radio ID: The Radio Identifier, typically refers to some interface
6444 index on the WTP.
6445
6446 Tag Packets: A value indicating whether LWAPP packets should be
6447 tagged for QoS purposes. The following values are currently
6448 supported:
6449
6450 0 - Untagged
6451
6452 1 - 802.1P
6453
6454 2 - DSCP
6455
6456 Immediately following the above header is the following data
6457 structure. This data structure will be repeated five times, once
6458 for every QoS profile. The order of the QoS profiles is Uranium,
6459 Platinum, Gold, Silver, and Bronze.
6460
6461 0 1 2 3
6462 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
6463 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
6464 | Queue Depth | CWMin | CWMax |
6465 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
6466 | CWMax | AIFS | CBR |
6467 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
6468 | Dot1P Tag | DSCP Tag |
6469 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
6470
6471 Queue Depth: The number of packets that can be on the specific QoS
6472 transmit queue at any given time.
6473
6474 CWMin: The Contention Window minimum value for the QoS transmit
6475 queue.
6476
6477 CWMax: The Contention Window maximum value for the QoS transmit
6478 queue.
6479
6480 AIFS: The Arbitration Inter Frame Spacing to use for the QoS
6481 transmit queue.
6482
6483 CBR: The Constant Bit Rate (CBR) value to observe for the QoS
6484 transmit queue.
6485
6486 Dot1P Tag: The 802.1P precedence value to use if packets are to be
6487 802.1P tagged.
6488
6489
6490
6491
6492 <span class="grey">Calhoun, et al. Historic [Page 116]</span></pre>
6493 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-117" ></span>
6494 <span class="grey"><a href="./rfc5412">RFC 5412</a> Lightweight Access Point Protocol February 2010</span>
6495
6496
6497 DSCP Tag: The DSCP label to use if packets are to be DSCP tagged.
6498
6499 <span class="h4"><a class="selflink" id="section-11.9.15" href="#section-11.9.15">11.9.15</a>. IEEE 802.11 MIC Error Report From Mobile</span>
6500
6501 The MIC Error Report From Mobile message element is sent by an AC to
6502 a WTP when it receives a MIC failure notification via the Error bit
6503 in the EAP over LAN (EAPOL)-Key frame.
6504
6505 0 1 2 3
6506 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
6507 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
6508 | Client MAC Address |
6509 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
6510 | Client MAC Address | BSSID |
6511 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
6512 | BSSID |
6513 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
6514 | Radio ID | WLAN ID |
6515 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
6516
6517 Type: 79 for IEEE 802.11 MIC Error Report From Mobile
6518
6519 Length: 14
6520
6521 Client MAC Address: The Client MAC address of the station reporting
6522 the MIC failure.
6523
6524 BSSID: The BSSID on which the MIC failure is being reported.
6525
6526 Radio ID: The Radio Identifier, typically refers to some interface
6527 index on the WTP.
6528
6529 WLAN ID: The WLAN ID on which the MIC failure is being reported.
6530
6531 <span class="h3"><a class="selflink" id="section-11.10" href="#section-11.10">11.10</a>. IEEE 802.11 Message Element Values</span>
6532
6533 This section lists IEEE 802.11-specific values for any generic LWAPP
6534 message elements that include fields whose values are technology-
6535 specific.
6536
6537 IEEE 802.11 uses the following values:
6538
6539 4 - Encrypt AES-CCMP 128: WTP supports AES-CCMP, as defined in [<a href="#ref-7" title="&quot;Information technology - Telecommunications and information exchange between systems - Local and metropolitan area networks - Specific requirements - Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) specifications Amendment 6: Medium Access Control (MAC) Security Enhancements&quot;">7</a>].
6540
6541 5 - Encrypt TKIP-MIC: WTP supports TKIP and Michael, as defined in
6542 [<a href="#ref-16" title="&quot;WiFi Protected Access (WPA) rev 1.6&quot;">16</a>].
6543
6544
6545
6546
6547
6548 <span class="grey">Calhoun, et al. Historic [Page 117]</span></pre>
6549 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-118" ></span>
6550 <span class="grey"><a href="./rfc5412">RFC 5412</a> Lightweight Access Point Protocol February 2010</span>
6551
6552
6553 <span class="h2"><a class="selflink" id="section-12" href="#section-12">12</a>. LWAPP Protocol Timers</span>
6554
6555 A WTP or AC that implements LWAPP discovery MUST implement the
6556 following timers.
6557
6558 <span class="h3"><a class="selflink" id="section-12.1" href="#section-12.1">12.1</a>. MaxDiscoveryInterval</span>
6559
6560 The maximum time allowed between sending Discovery Requests from the
6561 interface, in seconds. Must be no less than 2 seconds and no greater
6562 than 180 seconds.
6563
6564 Default: 20 seconds.
6565
6566 <span class="h3"><a class="selflink" id="section-12.2" href="#section-12.2">12.2</a>. SilentInterval</span>
6567
6568 The minimum time, in seconds, a WTP MUST wait after failing to
6569 receive any responses to its Discovery Requests, before it MAY again
6570 send Discovery Requests.
6571
6572 Default: 30
6573
6574 <span class="h3"><a class="selflink" id="section-12.3" href="#section-12.3">12.3</a>. NeighborDeadInterval</span>
6575
6576 The minimum time, in seconds, a WTP MUST wait without having received
6577 Echo Responses to its Echo Requests, before the destination for the
6578 Echo Request may be considered dead. Must be no less than
6579 2*EchoInterval seconds and no greater than 240 seconds.
6580
6581 Default: 60
6582
6583 <span class="h3"><a class="selflink" id="section-12.4" href="#section-12.4">12.4</a>. EchoInterval</span>
6584
6585 The minimum time, in seconds, between sending Echo Requests to the AC
6586 with which the WTP has joined.
6587
6588 Default: 30
6589
6590 <span class="h3"><a class="selflink" id="section-12.5" href="#section-12.5">12.5</a>. DiscoveryInterval</span>
6591
6592 The minimum time, in seconds, that a WTP MUST wait after receiving a
6593 Discovery Response, before sending a Join Request.
6594
6595 Default: 5
6596
6597
6598
6599
6600
6601
6602
6603
6604 <span class="grey">Calhoun, et al. Historic [Page 118]</span></pre>
6605 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-119" ></span>
6606 <span class="grey"><a href="./rfc5412">RFC 5412</a> Lightweight Access Point Protocol February 2010</span>
6607
6608
6609 <span class="h3"><a class="selflink" id="section-12.6" href="#section-12.6">12.6</a>. RetransmitInterval</span>
6610
6611 The minimum time, in seconds, that a non-acknowledged LWAPP packet
6612 will be retransmitted.
6613
6614 Default: 3
6615
6616 <span class="h3"><a class="selflink" id="section-12.7" href="#section-12.7">12.7</a>. ResponseTimeout</span>
6617
6618 The minimum time, in seconds, in which an LWAPP Request message must
6619 be responded to.
6620
6621 Default: 1
6622
6623 <span class="h3"><a class="selflink" id="section-12.8" href="#section-12.8">12.8</a>. KeyLifetime</span>
6624
6625 The maximum time, in seconds, that an LWAPP session key is valid.
6626
6627 Default: 28800
6628
6629 <span class="h2"><a class="selflink" id="section-13" href="#section-13">13</a>. LWAPP Protocol Variables</span>
6630
6631 A WTP or AC that implements LWAPP discovery MUST allow for the
6632 following variables to be configured by system management; default
6633 values are specified so as to make it unnecessary to configure any of
6634 these variables in many cases.
6635
6636 <span class="h3"><a class="selflink" id="section-13.1" href="#section-13.1">13.1</a>. MaxDiscoveries</span>
6637
6638 The maximum number of Discovery Requests that will be sent after a
6639 WTP boots.
6640
6641 Default: 10
6642
6643 <span class="h3"><a class="selflink" id="section-13.2" href="#section-13.2">13.2</a>. DiscoveryCount</span>
6644
6645 The number of discoveries transmitted by a WTP to a single AC. This
6646 is a monotonically increasing counter.
6647
6648 <span class="h3"><a class="selflink" id="section-13.3" href="#section-13.3">13.3</a>. RetransmitCount</span>
6649
6650 The number of retransmissions for a given LWAPP packet. This is a
6651 monotonically increasing counter.
6652
6653
6654
6655
6656
6657
6658
6659
6660 <span class="grey">Calhoun, et al. Historic [Page 119]</span></pre>
6661 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-120" ></span>
6662 <span class="grey"><a href="./rfc5412">RFC 5412</a> Lightweight Access Point Protocol February 2010</span>
6663
6664
6665 <span class="h3"><a class="selflink" id="section-13.4" href="#section-13.4">13.4</a>. MaxRetransmit</span>
6666
6667 The maximum number of retransmissions for a given LWAPP packet before
6668 the link layer considers the peer dead.
6669
6670 Default: 5
6671
6672 <span class="h2"><a class="selflink" id="section-14" href="#section-14">14</a>. NAT Considerations</span>
6673
6674 There are two specific situations where a NAT system may be used in
6675 conjunction with LWAPP. The first consists of a configuration where
6676 the WTP is behind a NAT system. Given that all communication is
6677 initiated by the WTP, and all communication is performed over IP
6678 using a single UDP port, the protocol easily traverses NAT systems in
6679 this configuration.
6680
6681 The second configuration is one where the AC sits behind a NAT, and
6682 there are two main issues that exist in this situation. First, an AC
6683 communicates its interfaces and associated WTP load on these
6684 interfaces, through the WTP Manager Control IP Address. This message
6685 element is currently mandatory, and if NAT compliance became an
6686 issue, it would be possible to either:
6687
6688 1. make the WTP Manager Control IP Address optional, allowing the WTP
6689 to simply use the known IP address. However, note that this
6690 approach would eliminate the ability to perform load balancing of
6691 WTP across ACs, and therefore is not the recommended approach.
6692
6693 2. allow an AC to be able to configure a NAT'ed address for every
6694 associated AC that would generally be communicated in the WTP
6695 Manager Control IP Address message element.
6696
6697 3. require that if a WTP determines that the AC List message element
6698 consists of a set of IP addresses that are different from the AC's
6699 IP address it is currently communicating with, then assume that
6700 NAT is being enforced, and require that the WTP communicate with
6701 the original AC's IP address (and ignore the WTP Manager Control
6702 IP Address message element(s)).
6703
6704 Another issue related to having an AC behind a NAT system is LWAPP's
6705 support for the CAPWAP Objective to allow the control and data plane
6706 to be separated. In order to support this requirement, the LWAPP
6707 protocol defines the WTP Manager Data IP Address message element,
6708 which allows the AC to inform the WTP that the LWAPP data frames are
6709 to be forwarded to a separate IP address. This feature MUST be
6710 disabled when an AC is behind a NAT. However, there is no easy way
6711 to provide some default mechanism that satisfies both the data/
6712
6713
6714
6715
6716 <span class="grey">Calhoun, et al. Historic [Page 120]</span></pre>
6717 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-121" ></span>
6718 <span class="grey"><a href="./rfc5412">RFC 5412</a> Lightweight Access Point Protocol February 2010</span>
6719
6720
6721 control separation and NAT objectives, as they directly conflict with
6722 each other. As a consequence, user intervention will be required to
6723 support such networks.
6724
6725 LWAPP has a feature that allows for all of the AC's identities
6726 supporting a group of WTPs to be communicated through the AC List
6727 message element. This feature must be disabled when the AC is behind
6728 a NAT and the IP address that is embedded would be invalid.
6729
6730 The LWAPP protocol has a feature that allows an AC to configure a
6731 static IP address on a WTP. The WTP Static IP Address Information
6732 message element provides such a function; however, this feature
6733 SHOULD NOT be used in NAT'ed environments, unless the administrator
6734 is familiar with the internal IP addressing scheme within the WTP's
6735 private network, and does not rely on the public address seen by the
6736 AC.
6737
6738 When a WTP detects the duplicate address condition, it generates a
6739 message to the AC, which includes the Duplicate IP Address message
6740 element. Once again, it is important to note that the IP address
6741 embedded within this message element would be different from the
6742 public IP address seen by the AC.
6743
6744 <span class="h2"><a class="selflink" id="section-15" href="#section-15">15</a>. Security Considerations</span>
6745
6746 LWAPP uses either an authenticated key exchange or key agreement
6747 mechanism to ensure peer authenticity and establish fresh session
6748 keys to protect the LWAPP communications.
6749
6750 The LWAPP protocol defines a join phase, which allows a WTP to bind a
6751 session with an AC. During this process, a session key is mutually
6752 derived, and secured either through an X.509 certificate or a pre-
6753 shared key. The resulting key exchange generates an encryption
6754 session key, which is used to encrypt the LWAPP control packets, and
6755 a key derivation key.
6756
6757 During the established secure communication, the WTP and AC may rekey
6758 using the key update process, which is identical to the join phase,
6759 meaning the session keys are mutually derived. However, the exchange
6760 described for pre-shared session keys is always used for the key
6761 update, with the pre-shared key set to the derivation key created
6762 either during the join, or the last key update if one has occurred.
6763 The key update results in a new derivation key, which is used in the
6764 next key update, as well as an encryption session key to encrypt the
6765 LWAPP control packets.
6766
6767
6768
6769
6770
6771
6772 <span class="grey">Calhoun, et al. Historic [Page 121]</span></pre>
6773 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-122" ></span>
6774 <span class="grey"><a href="./rfc5412">RFC 5412</a> Lightweight Access Point Protocol February 2010</span>
6775
6776
6777 Replay protection of the Join Request is handled through an exchange
6778 of nonces during the join (or key update) phase. The Join Request
6779 includes an XNonce, which is included in the AC's authenticated Join
6780 Reply's encrypted ANonce message element, allowing for the two
6781 messages to be bound. Upon receipt of the Join Reply, the WTP
6782 generates the WNonce, and generates a set of session keys using a KDF
6783 function. One of these keys is used to MIC the Join ACK. The AC
6784 responds with a Join Confirm, which must also include a MIC, and
6785 therefore be capable of deriving the same set of session keys.
6786
6787 In both the X.509 certificate and pre-shared key modes, an
6788 initialization vector is created through the above mentioned KDF
6789 function. The IV and the KDF created encryption key are used to
6790 encrypt the LWAPP control frames.
6791
6792 Given that authentication in the Join exchange does not occur until
6793 the WTP transmits the Join ACK message, it is crucial that an AC not
6794 delete any state for a WTP it is servicing until an authentication
6795 Join ACK has been received. Otherwise, a potential Denial-of-Service
6796 attack exists, whereby sending a spoofed Join Request for a valid WTP
6797 would cause the AC to reset the WTP's connection.
6798
6799 It is important to note that Perfect Forward Secrecy is not a
6800 requirement for the LWAPP protocol.
6801
6802 Note that the LWAPP protocol does not add any new vulnerabilities to
6803 802.11 infrastructure that makes use of WEP for encryption purposes.
6804 However, implementors SHOULD discourage the use of WEP to allow the
6805 market to move towards technically sound cryptographic solutions,
6806 such as 802.11i.
6807
6808 <span class="h3"><a class="selflink" id="section-15.1" href="#section-15.1">15.1</a>. Certificate-Based Session Key Establishment</span>
6809
6810 LWAPP uses public key cryptography to ensure trust between the WTP
6811 and the AC. One question that periodically arises is why the Join
6812 Request is not signed. Signing this request would not be optimal for
6813 the following reasons:
6814
6815 1. The Join Request is replayable, so a signature doesn't provide
6816 much protection unless the switches keep track of all previous
6817 Join Requests from a given WTP.
6818
6819 2. Replay detection is handled during the Join Reply and Join ACK
6820 messages.
6821
6822 3. A signed Join Request provides a potential Denial-of-Service
6823 attack on the AC, which would have to authenticate each
6824 (potentially malicious) message.
6825
6826
6827
6828 <span class="grey">Calhoun, et al. Historic [Page 122]</span></pre>
6829 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-123" ></span>
6830 <span class="grey"><a href="./rfc5412">RFC 5412</a> Lightweight Access Point Protocol February 2010</span>
6831
6832
6833 The WTP-Certificate that is included in the Join Request MUST be
6834 validated by the AC. It is also good practice that the AC perform
6835 some form of authorization, ensuring that the WTP in question is
6836 allowed to establish an LWAPP session with it.
6837
6838 <span class="h3"><a class="selflink" id="section-15.2" href="#section-15.2">15.2</a>. PSK-Based Session Key Establishment</span>
6839
6840 Use of a fixed shared secret of limited entropy (for example, a PSK
6841 that is relatively short, or was chosen by a human and thus may
6842 contain less entropy than its length would imply) may allow an
6843 attacker to perform a brute-force or dictionary attack to recover the
6844 secret.
6845
6846 It is RECOMMENDED that implementations that allow the administrator
6847 to manually configure the PSK also provide a functionality for
6848 generating a new random PSK, taking <a href="./rfc1750">RFC 1750</a> [<a href="#ref-4" title="&quot;Randomness Requirements for Security&quot;">4</a>] into account.
6849
6850 Since the key generation does not expose the nonces in plaintext,
6851 there are no practical passive attacks possible.
6852
6853 <span class="h2"><a class="selflink" id="section-16" href="#section-16">16</a>. Acknowledgements</span>
6854
6855 The authors wish to thank Michael Vakulenko for contributing text
6856 that describes how LWAPP can be used over a Layer 3 (IP) network.
6857
6858 The authors would also like to thanks Russ Housley and Charles Clancy
6859 for their assistance in providing a security review of the LWAPP
6860 specification. Charles' review can be found in [<a href="#ref-12" title="&quot;Security Review of the Light-Weight Access Point Protocol&quot;">12</a>].
6861
6862 <span class="h2"><a class="selflink" id="section-17" href="#section-17">17</a>. References</span>
6863
6864 <span class="h3"><a class="selflink" id="section-17.1" href="#section-17.1">17.1</a>. Normative References</span>
6865
6866 [<a id="ref-1">1</a>] Bradner, S., "Key words for use in RFCs to Indicate Requirement
6867 Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997.
6868
6869 [<a id="ref-2">2</a>] National Institute of Standards and Technology, "Advanced
6870 Encryption Standard (AES)", FIPS PUB 197, November 2001,
6871 &lt;<a href="http://csrc.nist.gov/publications/fips/fips197/fips-197.pdf">http://csrc.nist.gov/publications/fips/fips197/fips-197.pdf</a>&gt;.
6872
6873 [<a id="ref-3">3</a>] Whiting, D., Housley, R., and N. Ferguson, "Counter with CBC-
6874 MAC (CCM)", <a href="./rfc3610">RFC 3610</a>, September 2003.
6875
6876 [<a id="ref-4">4</a>] Eastlake, D., 3rd, Schiller, J., and S. Crocker, "Randomness
6877 Requirements for Security", <a href="https://www.rfc-editor.org/bcp/bcp106">BCP 106</a>, <a href="./rfc4086">RFC 4086</a>, June 2005.
6878
6879 [<a id="ref-5">5</a>] Manner, J., Ed., and M. Kojo, Ed., "Mobility Related
6880 Terminology", <a href="./rfc3753">RFC 3753</a>, June 2004.
6881
6882
6883
6884 <span class="grey">Calhoun, et al. Historic [Page 123]</span></pre>
6885 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-124" ></span>
6886 <span class="grey"><a href="./rfc5412">RFC 5412</a> Lightweight Access Point Protocol February 2010</span>
6887
6888
6889 [<a id="ref-6">6</a>] "Information technology - Telecommunications and information
6890 exchange between systems - Local and metropolitan area networks
6891 - Specific requirements - Part 11: Wireless LAN Medium Access
6892 Control (MAC) and Physical Layer (PHY) specifications", IEEE
6893 Standard 802.11, 2007,
6894 &lt;<a href="http://standards.ieee.org/getieee802/download/802.11-2007.pdf">http://standards.ieee.org/getieee802/download/802.11-2007.pdf</a>&gt;
6895
6896 [<a id="ref-7">7</a>] "Information technology - Telecommunications and information
6897 exchange between systems - Local and metropolitan area networks
6898 - Specific requirements - Part 11: Wireless LAN Medium Access
6899 Control (MAC) and Physical Layer (PHY) specifications Amendment
6900 6: Medium Access Control (MAC) Security Enhancements", IEEE
6901 Standard 802.11i, July 2004,
6902 <a href="http://standards.ieee.org/getieee802/download/802.11i-2004.pdf">http://standards.ieee.org/getieee802/download/802.11i-2004.pdf</a>
6903
6904 [<a id="ref-8">8</a>] Clark, D., "IP datagram reassembly algorithms", <a href="./rfc815">RFC 815</a>, July
6905 1982.
6906
6907 [<a id="ref-9">9</a>] Schaad, J. and R. Housley, "Advanced Encryption Standard (AES)
6908 Key Wrap Algorithm", <a href="./rfc3394">RFC 3394</a>, September 2002.
6909
6910 [<a id="ref-10">10</a>] Cooper, D., Santesson, S., Farrell, S., Boeyen, S., Housley,
6911 R., and W. Polk, "Internet X.509 Public Key Infrastructure
6912 Certificate and Certificate Revocation List (CRL) Profile", <a href="./rfc5280">RFC</a>
6913 <a href="./rfc5280">5280</a>, May 2008.
6914
6915 [<a id="ref-11">11</a>] "Netscape-Defined Certificate Extensions",
6916 &lt;<a href="http://www.redhat.com/docs/manuals/cert-system/admin/7.1/app_ext.html#35336">http://www.redhat.com/docs/manuals/cert-</a>
6917 <a href="http://www.redhat.com/docs/manuals/cert-system/admin/7.1/app_ext.html#35336">system/admin/7.1/app_ext.html#35336</a>&gt;.
6918
6919 [<a id="ref-12">12</a>] Clancy, C., "Security Review of the Light-Weight Access Point
6920 Protocol", May 2005,
6921 &lt;<a href="http://www.cs.umd.edu/~clancy/docs/lwapp-review.pdf">http://www.cs.umd.edu/~clancy/docs/lwapp-review.pdf</a>&gt;.
6922
6923 <span class="h3"><a class="selflink" id="section-17.2" href="#section-17.2">17.2</a>. Informative References</span>
6924
6925 [<a id="ref-13">13</a>] Reynolds, J., Ed., "Assigned Numbers: <a href="./rfc1700">RFC 1700</a> is Replaced by
6926 an On-line Database", <a href="./rfc3232">RFC 3232</a>, January 2002.
6927
6928 [<a id="ref-14">14</a>] Kent, S. and K. Seo, "Security Architecture for the Internet
6929 Protocol", <a href="./rfc4301">RFC 4301</a>, December 2005.
6930
6931 [<a id="ref-15">15</a>] Krawczyk, H., Bellare, M., and R. Canetti, "HMAC: Keyed-Hashing
6932 for Message Authentication", <a href="./rfc2104">RFC 2104</a>, February 1997.
6933
6934 [<a id="ref-16">16</a>] "WiFi Protected Access (WPA) rev 1.6", April 2003.
6935
6936
6937
6938
6939
6940 <span class="grey">Calhoun, et al. Historic [Page 124]</span></pre>
6941 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-125" ></span>
6942 <span class="grey"><a href="./rfc5412">RFC 5412</a> Lightweight Access Point Protocol February 2010</span>
6943
6944
6945 Authors' Addresses
6946
6947 Pat R. Calhoun
6948 Cisco Systems, Inc.
6949 170 West Tasman Drive
6950 San Jose, CA 95134
6951 Phone: +1 408-853-5269
6952 EMail: [email protected]
6953
6954 Rohit Suri
6955 Cisco Systems, Inc.
6956 170 West Tasman Drive
6957 San Jose, CA 95134
6958 Phone: +1 408-853-5548
6959 EMail: [email protected]
6960
6961 Nancy Cam-Winget
6962 Cisco Systems, Inc.
6963 170 West Tasman Drive
6964 San Jose, CA 95134
6965 Phone: +1 408-853-0532
6966 EMail: [email protected]
6967
6968 Scott Kelly
6969 EMail: [email protected]
6970
6971
6972 Michael Glenn Williams
6973 GWhiz Arts &amp; Sciences
6974 1560 Newbury Road, Suite 1-204
6975 Newbury Park, CA 91320
6976 Phone: +1 805-499-1994
6977 EMail: [email protected]
6978
6979
6980 Sue Hares
6981 Phone: +1 734-604-0332
6982 EMail: [email protected]
6983
6984 Bob O'Hara
6985 EMail: [email protected]
6986
6987
6988
6989
6990
6991
6992
6993
6994
6995
6996 Calhoun, et al. Historic [Page 125]
6997 </pre>