summaryrefslogtreecommitdiff
path: root/doc/rfc/rfc7494.txt
blob: 796d946f8256d552466c23334a16396ca0ef0ee7 (plain) (blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
Internet Engineering Task Force (IETF)                           C. Shao
Request for Comments: 7494                                       H. Deng
Category: Standards Track                                   China Mobile
ISSN: 2070-1721                                            R. Pazhyannur
                                                           Cisco Systems
                                                                 F. Bari
                                                                    AT&T
                                                                R. Zhang
                                                           China Telecom
                                                           S. Matsushima
                                                        SoftBank Telecom
                                                              April 2015


    IEEE 802.11 Medium Access Control (MAC) Profile for Control and
            Provisioning of Wireless Access Points (CAPWAP)

Abstract

   The Control and Provisioning of Wireless Access Points (CAPWAP)
   protocol binding for IEEE 802.11 defines two Medium Access Control
   (MAC) modes for IEEE 802.11 Wireless Transmission Points (WTPs):
   Split and Local MAC.  In the Split MAC mode, the partitioning of
   encryption/decryption functions is not clearly defined.  In the Split
   MAC mode description, IEEE 802.11 encryption is specified as located
   in either the Access Controller (AC) or the WTP, with no clear way
   for the AC to inform the WTP of where the encryption functionality
   should be located.  This leads to interoperability issues, especially
   when the AC and WTP come from different vendors.  To prevent
   interoperability issues, this specification defines an IEEE 802.11
   MAC Profile message element in which each profile specifies an
   unambiguous division of encryption functionality between the WTP and
   AC.

Status of This Memo

   This is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force
   (IETF).  It represents the consensus of the IETF community.  It has
   received public review and has been approved for publication by the
   Internet Engineering Steering Group (IESG).  Further information on
   Internet Standards is available in Section 2 of RFC 5741.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at
   http://www.rfc-editor.org/info/rfc7494.




Shao, et al.                 Standards Track                    [Page 1]
^L
RFC 7494                   CAPWAP MAC Profile                 April 2015


Copyright Notice

   Copyright (c) 2015 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  IEEE MAC Profile Descriptions . . . . . . . . . . . . . . . .   5
     2.1.  Split MAC with WTP Encryption . . . . . . . . . . . . . .   5
     2.2.  Split MAC with AC Encryption  . . . . . . . . . . . . . .   6
     2.3.  IEEE 802.11 MAC Profile Frame Exchange  . . . . . . . . .   8
   3.  MAC Profile Message Element Definitions . . . . . . . . . . .   8
     3.1.  IEEE 802.11 Supported MAC Profiles  . . . . . . . . . . .   8
     3.2.  IEEE 802.11 MAC Profile . . . . . . . . . . . . . . . . .   9
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .   9
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  10
   6.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  11
     6.1.  Normative References  . . . . . . . . . . . . . . . . . .  11
     6.2.  Informative References  . . . . . . . . . . . . . . . . .  11
   Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . .  12
   Contributors  . . . . . . . . . . . . . . . . . . . . . . . . . .  12
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  12


















Shao, et al.                 Standards Track                    [Page 2]
^L
RFC 7494                   CAPWAP MAC Profile                 April 2015


1.  Introduction

   The CAPWAP protocol supports two MAC modes of operation: Split and
   Local MAC, as described in [RFC5415] and [RFC5416].  However, there
   are MAC functions that have not been clearly defined.  For example,
   IEEE 802.11 [IEEE.802.11] encryption is specified as located in
   either the AC or the WTP with no clear way to negotiate where it
   should be located.  Because different vendors have different
   definitions of the MAC mode, many MAC-layer functions are mapped
   differently to either the WTP or the AC by different vendors.
   Therefore, depending upon the vendor, the operators in their
   deployments have to perform different configurations based on
   implementation of the two modes by their vendor.  If there is no
   clear specification, then operators will experience interoperability
   issues with WTPs and ACs from different vendors.

   Figure 1 from [RFC5416] illustrates how some functions are processed
   in different places in the Local MAC and Split MAC mode.
   Specifically, note that in the Split MAC mode, the IEEE 802.11
   encryption/decryption is specified as WTP/AC, implying that it could
   be at either location.  This is not an issue with Local MAC because
   encryption is always at the WTP.





























Shao, et al.                 Standards Track                    [Page 3]
^L
RFC 7494                   CAPWAP MAC Profile                 April 2015


   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |            Functions                  | Local MAC | Split MAC |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |             |Distribution Service     |  WTP/AC   |     AC    |
   +             +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |             |Integration Service      |   WTP     |     AC    |
   +             +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |             |Beacon Generation        |   WTP     |     WTP   |
   +             +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |             |Probe Response Generation|   WTP     |     WTP   |
   +             +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   | Function    |Power Mgmt/              |   WTP     |     WTP   |
   +             |Packet Buffering         |           |           |
   |             +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |             |Fragmentation/           |   WTP     |    WTP/AC |
   +             |Defragmentation          |           |           |
   |             +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |             |Assoc/Disassoc/Reassoc   |  WTP/AC   |     AC    |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |             |Classifying              |   WTP     |     AC    |
   +   IEEE      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   | 802.11 QoS  |Scheduling               |   WTP     |    WTP/AC |
   +             +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |             |Queuing                  |   WTP     |    WTP    |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |             |IEEE 802.1X/EAP          |   AC      |    AC     |
   +   IEEE      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   | 802.11 RSN  |RSNA Key Management      |   AC      |    AC     |
   +  (WPA2)     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |             |IEEE 802.11              |   WTP     |    WTP/AC |
   +             |Encryption/Decryption    |           |           |
   |-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

   Note:
     RSN - Robust Security Network
     RSNA - Robust Security Network Association
     WPA2 - Wi-Fi Protected Access 2

              Figure 1: Functions in Local MAC and Split MAC

   To solve this problem, this specification introduces the IEEE 802.11
   MAC Profile.  The IEEE 802.11 MAC Profile unambiguously specifies
   where the various MAC functionalities should be located.








Shao, et al.                 Standards Track                    [Page 4]
^L
RFC 7494                   CAPWAP MAC Profile                 April 2015


2.  IEEE MAC Profile Descriptions

   A IEEE 802.11 MAC Profile refers to a description of how the MAC
   functionality is split between the WTP and AC shown in Figure 1.

2.1.  Split MAC with WTP Encryption

   The functional split for the Split MAC with WTP encryption is
   provided in Figure 2.  This profile is similar to the Split MAC
   description in [RFC5416], except that IEEE 802.11 encryption/
   decryption is at the WTP.  Note that fragmentation is always done at
   the same entity as the encryption.  Consequently, in this profile
   fragmentation/defragmentation is also done only at the WTP.  Note
   that scheduling functionality is denoted as WTP/AC.  As explained in
   [RFC5416], this means that the admission control component of IEEE
   802.11 resides on the AC; the real-time scheduling and queuing
   functions are on the WTP.


































Shao, et al.                 Standards Track                    [Page 5]
^L
RFC 7494                   CAPWAP MAC Profile                 April 2015


   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |            Functions                  | Profile   |
   |                                       |    0      |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |             |Distribution Service     |   AC      |
   +             +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |             |Integration Service      |   AC      |
   +             +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |             |Beacon Generation        |   WTP     |
   +             +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |             |Probe Response Generation|   WTP     |
   +             +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   | Function    |Power Mgmt/              |   WTP     |
   +             |Packet Buffering        |           |
   |             +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |             |Fragmentation/           |   WTP     |
   +             |Defragmentation          |           |
   |             +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |             |Assoc/Disassoc/Reassoc   |   AC      |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |             |Classifying              |   AC      |
   +   IEEE      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   | 802.11 QoS  |Scheduling               |   WTP/AC  |
   +             +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |             |Queuing                  |   WTP     |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |             |IEEE 802.1X/EAP          |   AC      |
   +   IEEE      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   | 802.11 RSN  |RSNA Key Management      |   AC      |
   +  (WPA2)     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |             |IEEE 802.11              |   WTP     |
   +             |Encryption/Decryption    |           |
   |-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

   Note:
   EAP - Extensible Authentication Protocol

           Figure 2: Functions in Split MAC with WTP Encryption













Shao, et al.                 Standards Track                    [Page 6]
^L
RFC 7494                   CAPWAP MAC Profile                 April 2015


2.2.  Split MAC with AC Encryption

   The functional split for the Split MAC with AC encryption is provided
   in Figure 3.  This profile is similar to the Split MAC in [RFC5416],
   except that IEEE 802.11 encryption/decryption is at the AC.  Since
   fragmentation is always done at the same entity as the encryption, in
   this profile, AC does fragmentation/defragmentation.

   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |            Functions                  | Profile   |
   |                                       |    1      |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |             |Distribution Service     |   AC      |
   +             +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |             |Integration Service      |   AC      |
   +             +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |             |Beacon Generation        |   WTP     |
   +             +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |             |Probe Response Generation|   WTP     |
   +             +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   | Function    |Power Mgmt/              |   WTP     |
   +             |Packet Buffering         |           |
   |             +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |             |Fragmentation/           |   AC      |
   +             |Defragmentation          |           |
   |             +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |             |Assoc/Disassoc/Reassoc   |   AC      |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |             |Classifying              |   AC      |
   +   IEEE      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   | 802.11 QoS  |Scheduling               |   WTP     |
   +             +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |             |Queuing                  |   WTP     |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |             |IEEE 802.1X/EAP          |   AC      |
   +   IEEE      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   | 802.11 RSN  |RSNA Key Management      |   AC      |
   +  (WPA2)     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |             |IEEE 802.11              |   AC      |
   +             |Encryption/Decryption    |           |
   |-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

            Figure 3: Functions in Split MAC with AC encryption








Shao, et al.                 Standards Track                    [Page 7]
^L
RFC 7494                   CAPWAP MAC Profile                 April 2015


2.3.  IEEE 802.11 MAC Profile Frame Exchange

   An example of message exchange using the IEEE 802.11 MAC Profile
   message element is shown in Figure 4.  The WTP informs the AC of the
   various MAC Profiles it supports.  This happens in either a Discovery
   Request message or the Join Request message.  The AC determines the
   appropriate profile and configures the WTP with the profile while
   configuring the WLAN.

       +-+-+-+-+-+-+                             +-+-+-+-+-+-+
       |    WTP    |                             |    AC     |
       +-+-+-+-+-+-+                             +-+-+-+-+-+-+
             |Join Request[Supported IEEE 802.11       |
             |       MAC Profiles   ]                  |
             |---------------------------------------->|
             |                                         |
             |Join Response                            |
             |<----------------------------------------|
             |                                         |
             |IEEE 802.11 WLAN Config. Request [       |
             | IEEE 802.11 Add WLAN,                   |
             | IEEE 802.11 MAC Profile                 |
             |   ]                                     |
             |<----------------------------------------|
             |                                         |
             |IEEE 802.11 WLAN Config. Response        |
             |---------------------------------------->|

          Figure 4: Message Exchange for Negotiating MAC Profiles

3.  MAC Profile Message Element Definitions

3.1.  IEEE 802.11 Supported MAC Profiles

   The IEEE 802.11 Supported MAC Profile message element allows the WTP
   to communicate the profiles it supports.  The Discovery Request
   message, Primary Discovery Request message, and Join Request message
   may include one such message element.

           0               1               2               3
           0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 0
          +=+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-
          | Num_Profiles  |  Profile_1    |   Profile_[2..N]..
          +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-

               Figure 5: IEEE 802.11 Supported MAC Profiles

   o  Type: 1060 for IEEE 802.11 Supported MAC Profiles



Shao, et al.                 Standards Track                    [Page 8]
^L
RFC 7494                   CAPWAP MAC Profile                 April 2015


   o  Num_Profiles >=1: This refers to the number of profiles present in
      this message element.  There must be at least one profile.

   o  Profile: Each profile is identified by a value specified in
      Section 3.2.

3.2.  IEEE 802.11 MAC Profile

   The IEEE 802.11 MAC Profile message element allows the AC to select a
   profile.  This message element may be provided along with the IEEE
   802.11 ADD WLAN message element while configuring a WLAN on the WTP.

           0 1 2 3 4 5 6 7
          +=+-+-+-+-+-+-+-+
          |  Profile      |
          +-+-+-+-+-+-+-+-+

                     Figure 6: IEEE 802.11 MAC Profile

   o  Type: 1061 for IEEE 802.11 MAC Profile

   o  Profile: The profile is identified by a value as given below

      *  0: This refers to the IEEE 802.11 Split MAC Profile with WTP
         encryption

      *  1: This refers to the IEEE 802.11 Split MAC Profile with AC
         encryption

4.  Security Considerations

   This document does not introduce any new security risks compared to
   [RFC5416].  The negotiation messages between the WTP and AC have
   origin authentication and data integrity.  As a result, an attacker
   cannot interfere with the messages to force a less-secure mode
   choice.  The security considerations described in [RFC5416] apply
   here as well.














Shao, et al.                 Standards Track                    [Page 9]
^L
RFC 7494                   CAPWAP MAC Profile                 April 2015


5.  IANA Considerations

   The following IANA actions have been completed.

   o  This specification defines two new message elements: IEEE 802.11
      Supported MAC Profiles (described in Section 3.1) and the IEEE
      802.11 MAC Profile (described in Section 3.2).  These elements
      have been registered in the existing "CAPWAP Message Element Type"
      registry, defined in [RFC5415].

              CAPWAP Protocol Message Element                Type Value
              IEEE 802.11 Supported MAC Profiles              1060
              IEEE 802.11 MAC Profile                         1061

   o  The IEEE 802.11 Supported MAC Profiles message element and IEEE
      802.11 MAC Profile message element include a Profile field (as
      defined in Section 3.2).  The Profile field in the IEEE 802.11
      Supported MAC Profiles denotes the MAC Profiles supported by the
      WTP.  The Profile field in the IEEE 802.11 MAC Profile denotes the
      MAC Profile assigned to the WTP.  The namespace for the field is 8
      bits (0-255).  This specification defines two values: zero (0) and
      one (1) as described below.  The remaining values (2-255) are
      controlled and maintained by IANA, and the registration procedure
      is Expert Review [RFC5226].  IANA has created a new subregistry
      called "IEEE 802.11 Split MAC Profile" under the existing registry
      "Control And Provisioning of Wireless Access Points (CAPWAP)
      Parameters".  The registry format is given below.

               Profile                             Type Value  Reference
               Split MAC with WTP encryption       0           RFC 7494
               Split MAC with AC encryption        1           RFC 7494




















Shao, et al.                 Standards Track                   [Page 10]
^L
RFC 7494                   CAPWAP MAC Profile                 April 2015


6.  References

6.1.  Normative References

   [IEEE.802.11]
              IEEE, "IEEE Standard for 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", IEEE Std
              802.11-2012, March 2012,
              <http://standards.ieee.org/about/get/802/802.11.html>.

   [RFC5415]  Calhoun, P., Ed., Montemurro, M., Ed., and D. Stanley,
              Ed., "Control And Provisioning of Wireless Access Points
              (CAPWAP) Protocol Specification", RFC 5415, March 2009,
              <http://www.rfc-editor.org/info/rfc5415>.

   [RFC5416]  Calhoun, P., Ed., Montemurro, M., Ed., and D. Stanley,
              Ed., "Control and Provisioning of Wireless Access Points
              (CAPWAP) Protocol Binding for IEEE 802.11", RFC 5416,
              March 2009, <http://www.rfc-editor.org/info/rfc5416>.

6.2.  Informative References

   [RFC5226]  Narten, T. and H. Alvestrand, "Guidelines for Writing an
              IANA Considerations Section in RFCs", BCP 26, RFC 5226,
              May 2008, <http://www.rfc-editor.org/info/rfc5226>.























Shao, et al.                 Standards Track                   [Page 11]
^L
RFC 7494                   CAPWAP MAC Profile                 April 2015


Acknowledgments

   The authors are grateful for extremely valuable suggestions from
   Dorothy Stanley in developing this specification.

   Guidance from the management team -- Melinda Shore, Scott Bradner,
   Chris Liljenstolpe, Benoit Claise, Joel Jaeggli, and Dan Romascanu --
   is highly appreciated.

Contributors

   Yifan Chen <chenyifan@chinamobile.com>

   Naibao Zhou <zhounaibao@chinamobile.com>

Authors' Addresses

   Chunju Shao
   China Mobile
   No.32 Xuanwumen West Street
   Beijing  100053
   China

   EMail: shaochunju@chinamobile.com


   Hui Deng
   China Mobile
   No.32 Xuanwumen West Street
   Beijing  100053
   China

   EMail: denghui@chinamobile.com


   Rajesh S. Pazhyannur
   Cisco Systems
   170 West Tasman Drive
   San Jose, CA 95134
   United States

   EMail: rpazhyan@cisco.com









Shao, et al.                 Standards Track                   [Page 12]
^L
RFC 7494                   CAPWAP MAC Profile                 April 2015


   Farooq Bari
   AT&T
   7277 164th Ave NE
   Redmond, WA 98052
   United States

   EMail: farooq.bari@att.com


   Rong Zhang
   China Telecom
   No.109 Zhongshandadao avenue
   Guangzhou  510630
   China

   EMail: zhangr@gsta.com


   Satoru Matsushima
   SoftBank Telecom
   1-9-1 Higashi-Shinbashi, Munato-ku
   Tokyo
   Japan

   EMail: satoru.matsushima@g.softbank.co.jp


























Shao, et al.                 Standards Track                   [Page 13]
^L