110 likes | 134 Views
This document discusses the base functionality of the CAPWAP Tunneling Protocol (CTP), including AP to AC registration, security credentials exchange, authentication mechanisms, AP and AC session creation, and more.
E N D
CAPWAP WG CAPWAP Tunneling Protocol (CTP) Inderpreet Singh Chantry Networks A division of Siemens AG IETF 62, Minneapolis, MN
Base Functionality of CTP • AP to AC Registration Functions • Exchange of security credentials • Authentication mechanisms • Capability exchange • AP and AC session creation • Keep Alive • Periodic poll messages to confirm connectivity between AP and AC • Supports availability failover and alert triggers
Base Functionality of CTP • Mobile Session Management • Connection management • MU connection and disconnection services • Encryption key management • Policy exchange services • Encapsulation of User Data • Encapsulated 802.3 data • Identifiers that assist in understanding policy assignment (i.e. Network ID, WTP ID etc.) • TOS bit translation
Base Functionality of CTP • AP Management • Configuration • AP auto request on boot up • Triggered from AC • Statistics • Periodic polling from AC • Firmware Upgrade Triggers • AP auto request on boot up • Triggered from AC • AP State Management • Reset services, operational state
Control, management and provisioning of WTPs and ACs Network layer agnostic (L2 or L3) Radio Technology agnostic New requirement !! Local vs. Split MAC agnostic The Objectives
AC Discovery Use DNS or DHCP option or SLP (unicast/multicast) or Static Config SW Image update mechanism Define sw update command messages SW Version SW server IP address Utilize ftp or tftp The NON-Requirements
CTP Transport • UDP based only • No distinction of L2 or L3 • No fragmentation/reassembly • No L2 specific discovery
Configuration and Statistics • Assumption: All WTPs incorporate an SNMP agent • This is true for 802.11 Access Point reference designs, but also assumed for future wireless APs • Every 802 standard has a MIB defined • Example: 802.11 Annex D defines 802.11 MIB already • Model all configuration and statistics on a MIB and utilize the CTP transport to carry the OIDs for configuration and statistics • Advantage • Need to do MIB work anyway for CAPWAP • Flexible and modular for other wireless technologies
Local vs. Split MAC • ATT-MAC-INFO – This attribute consists of information pertaining to the implementation of the wireless MAC layer in the WTP. This in turn specifies to the AC the expected data type that will be received. At this time only two types of MAC implementation are supported, ie. Local MAC and Split MAC. • Type= 3 • Length= 2 bytes • Value= MAC layer information as defined below: • 0 1 • 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 • +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ • | RADIO-INDEX | MAC-TYPE | • +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ • where • RADIO-INDEX is a unique index of the enumeration of the number • of radios that the AP supports • MAC-TYPE is defined as • o Local MAC = 1 • o Split MAC = 2
Local vs. Split (WTP) +--+--+ +----+------+ Control <===>| | | | | CTP |<===========>|WirelessMAC| Data <--->| | | | +--+--+ +----+------+ ^ ^ | +-----------+ | | | | | Data (optional) <-------+--->| L2 bridge |<---+ | | +-----------+ Local +--+--+ +----+------+ Control <===>| | | Split | | CTP |<===========>| Wireless | Data <--->| | | MAC | +--+--+ +----+------+ Split