CAPWAP Working Group H. Wen Internet-Draft Alcatel Shanghai Bell Expires: April 14, 2009 S. Jain Alcatel-Lucent October 15, 2008 CAPWAP WLAN-VLAN Information Message Element draft-wen-capwap-wlan-vlan-00.txt Status of this Memo By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section 6 of BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet- Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt. The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html. This Internet-Draft will expire on April 14, 2009. Wen & Jain Expires April 14, 2009 [Page 1] Internet-Draft draft-wen-capwap-wlan-vlan-00.txt October 2008 Abstract In Control And Provisioning of Wireless Access Points Protocol, the WLANs on the Wireless Termination Point are created by the Access Controller with the appropriate setting. This document defines a mew messages elements, i.e., WLAN-VLAN Information message element, which is used to set WLAN-VLAN binding information on the WTP. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1.1. Conventions used in this document . . . . . . . . . . . . 3 1.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3 2. CAPWAP WLAN-VLAN Information . . . . . . . . . . . . . . . . . 4 3. Type Value Consideration . . . . . . . . . . . . . . . . . . 5 4. IANA Consideration . . . . . . . . . . . . . . . . . . . . . . 5 5. Security Considerations . . . . . . . . . . . . . . . . . . . 5 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 6 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 6 7.1. Normative References . . . . . . . . . . . . . . . . . . . 6 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 7 Intellectual Property and Copyright Statements . . . . . . . . . . 8 Wen & Jain Expires April 14, 2009 [Page 2] Internet-Draft draft-wen-capwap-wlan-vlan-00.txt October 2008 1. Introduction In the centralized WLAN architecture [I-D.ietf-capwap-protocol- specification], WTPs can be inter-connected via Distribution System (DS),which is constructed by Ethernet technology. On each WTP, more than one WLAN can be defined by the AC via multiple IEEE 802.11 Add WLAN message element [I-D.ietf-capwap-protocol-binding-ieee80211]. The operator of centralized WLAN network could provide differentiated services to the stations connected to different kind of WLANs. The local-MAC mode with local bridging method (i.e., the traffic can locally switched) is more efficient for traffic delivery and can offload from the Access Controller (AC), so it attracts more attention. However, the traffic sending from the northbound interface of the WTP has lost all the WLAN information; in fact, the traffic from different WLAN on the WTP may have different requirements (e.g., priority, throughput) on the DS, so in order to provide better control and management on the traffic belonging to different WLAN from the WTP, the traffic identification and segregation from the northbound interface of the WTP is needed. The traffic related to different WLAN can be tagged with different VLAN tag. This document defines WLAN-VLAN Information message element , which is used by the AC to create the WLAN on the WTP with the appropriate VLAN information. In fact, there is one-to-one mapping between SSID, WLAN and VLAN. This VLAN is useful when local bridging is deployed in the network. 1.1. Conventions used in this document The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [RFC2119]. 1.2. Terminology This document uses terminology defined in [I-D.ietf-capwap-protocol- specification] and [I-D.ietf-capwap-protocol-binding-ieee80211]. Wen & Jain Expires April 14, 2009 [Page 3] Internet-Draft draft-wen-capwap-wlan-vlan-00.txt October 2008 2. CAPWAP WLAN-VLAN Information The WLAN-VLAN Information message element accompanies the IEEE 802.11 Add WLAN message element, and is used to deliver the binding information of WLAN and VLAN to the WTP for the local-MAC mode which works with local bridging method. The traffic received from this specified WLAN will be sent by the WTP with the VLAN information specified in this WLAN-VLAN Information message element. The traffic on the path from the northbound interface of the WTP is segregated by VLAN technology. The CAPWAP WLAN-VLAN Information message element for CAPWAP IEEE802.11 has the format shown in the following figure: 0 1 2 3 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 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Radio ID | WLAN ID | VLAN tag | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | VLAN tag | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Type: WLAN_VLAN_INFO (TBD) Length: = 8 Radio ID: An 8-bit value representing the radio WLAN ID: An 8-bit value specifying the WLAN Identifier VLAN tag: 4-byte. there are 2 bytes for 802.1q type identfier with a fixed value of 0x8100, 3-bit user priority, 1-bit canonical format (CFI indicator), and 12-bit VLAN identifier. Usage: This information element is an optional message element and will be used in WLAN Configuration Request in association with Add WLAN Message element. Wen & Jain Expires April 14, 2009 [Page 4] Internet-Draft draft-wen-capwap-wlan-vlan-00.txt October 2008 3. Type Value Consideration The following Message Element type value for CAPWAP WLAN-VLAN Information message element MUST be assigned Message Element Value ----------------------------------------------------------- CAPWAP WLAN-VLAN Information WLAN_VLAN_INFO 4. IANA Consideration This document has no actions for IANA. 5. Security Considerations There is no more security issue introduced by this message element. Wen & Jain Expires April 14, 2009 [Page 5] Internet-Draft draft-wen-capwap-wlan-vlan-00.txt October 2008 6. Acknowledgements The following individuals are acknowledged for their contributions to this draft: Songwei MA. 7. References 7.1. Normative References [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [I-D.ietf-capwap-protocol-specification] Calhoun, P., "CAPWAP Protocol Specification", draft-ietf-capwap-protocol-specification-13 (work in progress), September 19, 2008. [I-D.ietf-capwap-protocol-binding-ieee80211] Calhoun, P., "CAPWAP Protocol Binding for IEEE 802.11", draft-ietf-capwap-protocol-binding-ieee80211-10 (work in progress), September 19, 2008. Wen & Jain Expires April 14, 2009 [Page 6] Internet-Draft draft-wen-capwap-wlan-vlan-00.txt October 2008 Author's Address Haibo Wen Alcatel Shanghai Bell Co., Ltd. 388#, NingQiao Road, Pudong Jinqiao Shanghai 201206 P.R. China Phone: +86 (21) 5854-1240, extension. 9273 Email: Haibo.WEN@alcatel-sbell.com.cn Sudhanshu JAIN Alcatel-Lucent 755 Ravendale Dr, Mountain View, CA 94043 Phone: +1 650 623 3329 Email: Sudhanshu.jain@alcatel-lucent.com Wen & Jain Expires April 14, 2009 [Page 7] Internet-Draft draft-wen-capwap-wlan-vlan-00.txt October 2008 Full Copyright Statement Copyright (C) The IETF Trust (2008). This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights. This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Intellectual Property The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79. Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr. The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf-ipr@ietf.org. Wen & Jain Expires April 14, 2009 [Page 8]