802.11 -- Interworking with 802.1Qat Stream Reservation Protocol

1. 802.11 -- Interworking with 802.1Qat Stream Reservation Protocol Date: 2010-03-01 Authors: Ganesh Venkatesan, Intel Corporation, et al

2. Abstract This submission is an overview of proposed input from 802.11 to 802.1Qat Annex-Q Clause Q.3 -- Discussions on the normative text (10/137r0) corresponding to 09/926r7 spawned interest in revisiting the solution proposed and seek a ‘future proof’ alternative, if possible. Note: In the rest of this presentation AP and non-AP STA denote 802.11 implementations with dot1QatNetworking set to true. Slide 2 Ganesh Venkatesan, Intel Corporation, et al

3. Handling SRP Reservation Requests Ganesh Venkatesan, Intel Corporation, et al

4. Common Scenarios Listener(s) Talker DMN DMN AP AP AP non-AP STA non-AP STA non-AP STA non-AP STA Alternate Data Path Talker Listener(s) Talker Listener(s) Ganesh Venkatesan, Intel Corporation, et al

5. Advanced Scenario: STA is an Intermediate node or a Talker/Listener Talker/Listener(s) • non-AP STA are intermediate nodes, Talker or Listener • Note: This scenario is included for completeness. Support for this requires resolution of the “Station Bridge issue*”. DMN AP non-AP STA non-AP STA Listener(s) Talker Listener(s) * See http://www.ieee802.org/1/files/public/docs2008/avb-nfinn-802-11-bridging-0308-v3.pdf Ganesh Venkatesan, Intel Corporation, et al

6. MSPRDU Processing at the AP/DMN (adopted proposal – 10/137r0) • A non-AP STA can either be Talker/Listener or an intermediate node in the path from the Talker to the Listener. • An intermediate node non-AP STA or a non-AP STA that is also the Talker/Listener just pass the MSRPDU to the AP • AP forwards the MSRPDU to the AP’s DMN • AP’s DMN invokes (DMN/AP interface) Reserve.request or Query.request with parameters corresponding to the received SRP Reservation/Query request • If the MSRPDU is a Reservation Request and the AP has sufficient resources: • AP’s SME issues a MLME.ADDTS.response to the talker • AP’s SME issues a MLME.ADDTS.response to the listener • AP responds to the DMN with a Reserve.confirm or Query.confirm Ganesh Venkatesan, Intel Corporation, et al

7. MSRP Handling at AP/DMN (to Talker/Listener) In 10/137r0 Ganesh Venkatesan, Intel Corporation, et al

8. Table Q.3 SRP to 802.11 SME QoS Services Mapping MAD – MRP (Multiple Registration Protocol) Attribute Declaration Ganesh Venkatesan, Intel Corporation, et al

9. Changes to 802.11 – Summary • Ability for APs to send Autonomous ADDTS Response • Add ADDTS Response.indication to the STA MLME interface (omission in 10/137r0) • To the DMN 802.11 interface (out of scope for 802.11) • Add SME-QUERY.{request|confirm} • Add SME-ADDTS.{request|confirm} 802.1Qat Mandate that 802.11 STAs and APs supporting SRP shall also support EDCA Admission Control The 802.11 AP and SRP DMN shall co-exist in the same device The SRP DMN shall generate 802.11 TSPECs as described in document 09/926r7 Mandate that 802.11STAs and APs supporting SRP shall encapsulate and de-encapsulate the 802.1q Tag Ganesh Venkatesan, Intel Corporation, et al

10. Summary of discussions in LA Need a discussion on the internals of 802.1Qat as far as SRP goes Scheduled for the joint meeting with 802.1AVB in March, 2010 How does the current proposal (10/137r0) deal with Power Save? How does the current proposal deal with TSPEC, TCLAS and TCLAS processing negotiation? Would the current proposal be able to take advantage of enhancements in 802.11? Should the solution be the same irrespective of if the 802.11 STA is a Talker/Listener or is just a node in the path from the Talker to the Listener? Slide 10 Ganesh Venkatesan, Intel Corporation, et al

11. Alternate Proposal-A .1 -- MSRP Handling at AP/DMN (to Talker/Listener) • non-AP STA at the Talker/Listener ends parse SRP and invoke corresponding 802.11 mechanisms • Synchronization issues need to be addressed at the AP Ganesh Venkatesan, Intel Corporation, et al

12. Alternate Proposal-A .2 -- MSRP Handling at AP/DMN (to Talker/Listener) • Network-side request for a .1Qat reservation is processed by DMN at AP (omitting .11 reservations) and passed to .1Qat Talker/Listener which requests the SME to complete a .11 ADDTS exchange. The .1Qat Talker/Listener reports the outcome to the DMN at AP • No Synchronization issues at the AP • Upper layer request for a .1Qat reservation is mapped by .1Qat Talker/Listener to a .11 ADDTS exchange, and if successful, the .1Qat Talker/Listener proceeds with MSRPDU exchanges • No Synchronization issues at the AP Ganesh Venkatesan, Intel Corporation, et al

13. Alternate Proposal-B -- MSRP Handling at AP/DMN (to Talker/Listener) Need a new “Reserve” management frame between AP to STA STA at Talker end does not have to parse SRP messages; no additional processing in 802.11 No synchronization issues Addresses all issues listed in slide-10 Ganesh Venkatesan, Intel Corporation, et al

14. What is in the Reserve Request? TSPEC Element with parameters set to values derived from information in the MSRPDU Optionally TCLAS and TCLAS Processing elements. Ganesh Venkatesan, Intel Corporation, et al

15. What is in the Reserve Response? A Status Code corresponding to the Success/Failure of TSPEC/TCLAS negotiation between the AP and the STA Ganesh Venkatesan, Intel Corporation, et al

16. The TSPEC Element in Reserve Request Ganesh Venkatesan, Intel Corporation, et al

17. Straw Polls • Should we stay with just the current solution (Slide-7)? • Which of the three alternate proposals do you prefer • A.1 • A.2 • B • Should we allow a simple and a complete solution – current solution (slide-7) + Alternate (one of slide-11, 12 or 13) or just an Alternate Proposal (one of slide-11, 12 or 13)? Ganesh Venkatesan, Intel Corporation, et al