1 / 13

CAPWAP Evaluation Draft Follow up

CAPWAP Evaluation Draft Follow up. CAPWAP WG - IETF 64 7 November, 2005 Darren Loher dloher@rovingplanet.com. Evaluation Team Details. Team Members David Nelson <dnelson@enterasys.com> Oleg Volinsky <ovolinsky@colubris.com> Behcet Sarikaya <sarikaya@unbc.ca>

lobdell
Download Presentation

CAPWAP Evaluation Draft Follow up

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. CAPWAP Evaluation DraftFollow up CAPWAP WG - IETF 64 7 November, 2005 Darren Loher dloher@rovingplanet.com

  2. Evaluation Team Details • Team Members • David Nelson <dnelson@enterasys.com> • Oleg Volinsky <ovolinsky@colubris.com> • Behcet Sarikaya <sarikaya@unbc.ca> • Darren Loher – Editor <dloher@rovingplanet.com> • Team Meetings • Team formed 8th June 2005 • Weekly meetings 15 June – 29 July • Observed by WG Chairs • Evaluation draft completed 13 September 2005 CAPWAP WG - IETF 64

  3. Summary Results C = Complete Compliance P = Partial Compliance F = Failed Compliance CAPWAP WG - IETF 64

  4. Evaluation Draft Recommendations • Protocol Recommendation • Adopt LWAPP as the base protocol • Several additional technical recommendations made • Evaluation team believes the working group should consider the technical merit of these recommendations • Primary Recommendations • 9.1.1. Information Elements • 9.1.2 Control Channel Security (DTLS) • 9.1.3 Data Tunneling Modes (Local MAC user data tunneling) • Additional Recommendations • 9.2.1. Access Control (Add mobile) • 9.2.2. Removal of Layer 2 Encapsulation for Data Tunneling • 9.2.3. Data Encapsulation Standard (GRE, L2TP) • A few recommendations in the body of the text • Configuration Consistency • Firmware Trigger • DoS consideration for join method CAPWAP WG - IETF 64

  5. Protocol Recommendation Use LWAPP as the base protocol for CAPWAP • Most closely meets all the working group objectives • The most detailed and complete specification • Flexible enough to be extended CAPWAP WG - IETF 64

  6. Recommendation: Information Elements CAPWAP WG - IETF 64

  7. RecommendationControl Channel Security (DTLS) CAPWAP WG - IETF 64

  8. Recommendation:Local MAC Data Tunneling Mode CAPWAP WG - IETF 64

  9. Recommendation:Mandatory and optional tunneling modes CAPWAP WG - IETF 64

  10. Recommendation:STA Access Control (Add Mobile) CAPWAP WG - IETF 64

  11. Recommendation:Removal of Layer 2 encapsulated tunnel for data CAPWAP WG - IETF 64

  12. Recommendation:Change data encapsulation to standard (GRE) CAPWAP WG - IETF 64

  13. Additional Recommendations • Configuration Consistency • Objective is to maintain configurations for a large number of network elements (1000’s) • Recommend that a token, key or serial number be used to represent WTP configuration • Allows quick configuration audit for a large number of devices • Firmware Trigger • The firmware trigger needs to be executed at any time in state machine • Should not require multiple resets/reboots of WTP just to initiate firmware check and update) • Allows possibility of less disruptive firmware upgrades than current LWAPP mechanism • DoS consideration • LWAP should recommend throttling of join requests to protect the AC CAPWAP WG - IETF 64

More Related