1 / 7

Roaming Improvements to TGe

Roaming Improvements to TGe. Mark Bilstad, Cisco Systems. Motivations. Resolve several comments related to roaming performance, including comment numbers 860, 861, 862, 863 Alternate resolution to 181, 182, 186, 187, 189, 369, 864, 865, 880

leilani-snyder
Download Presentation

Roaming Improvements to TGe

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. Roaming Improvements to TGe Mark Bilstad, Cisco Systems M. Bilstad, Cisco Systems

  2. Motivations • Resolve several comments related to roaming performance, including comment numbers 860, 861, 862, 863 • Alternate resolution to 181, 182, 186, 187, 189, 369, 864, 865, 880 • Respond to general mandate from task group to maintain and improve roaming performance in light of QoS application needs M. Bilstad, Cisco Systems

  3. Probe Requests … Probe Response Pre-authentication Exchange Re-association Exchange ADDTS, 4-way crypto handshakes Existing Handoff Process STA APs Discovery Other APs New AP IAPP Commit M. Bilstad, Cisco Systems

  4. Design Considerations • Discovery phase: QoS must be part of new AP selection • Client needs some confidence that its TSPECs will be accepted by the new AP while in the discovery phase • But, AP needs to be able to respond to probe requests quickly (must not require a query to admissions control) • Commit phase: QoS handshakes must not slow this down • TSPEC information should be allowed to be piggybacked on existing messages rather than sent in discrete action frames • Allow grouping of multiple TSPEC elements, regardless of frame M. Bilstad, Cisco Systems

  5. AP Authenticator Ideally, compress roaming to: Client Supplicant Probe Request Probe Response: available admission capacity (predictor) Reassociate Request: TSPEC(2), TCLAS Reassociate Response: status,TSPEC(2) M. Bilstad, Cisco Systems

  6. Changes Required • Define a new “Available Admission Capacity” field in the QBSS Load element • Define a new “QoS Management Action Header” element to allow ADDTS (and other) actions to be attached to (re)association requests and responses • A “transport” alternative; semantics are preserved • Create a “bidirectional” TSPEC direction code • Two TSPECs collapse into one: good reduction of message size M. Bilstad, Cisco Systems

  7. Mapping between action frame andelement sequence in (re)association Existing action frame example Action Category = QoS Mgmt Action Code = ADDTS Dialog Token Status TSPEC Element TCLAS Element Element ID = QoS Mgmt Action Header Element Length = 3 Action Code = ADDTS Dialog Token Status TSPEC Element TCLAS Element Corresponding element sequence M. Bilstad, Cisco Systems

More Related