doc.: IEEE /0219r3 Submission Interworking with 802.1Qat Stream Reservation Protocol Date: Authors: Mar 2010 Ganesh Venkatesan, Intel Corporation, et alSlide 1

doc.: IEEE /0219r3 SubmissionSlide 2 Abstract This submission is an overview of proposed input from 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. Mar 2010 Ganesh Venkatesan, Intel Corporation, et alSlide 2 Note: In the rest of this presentation AP and non-AP STA denote implementations with dot1QatNetworking set to true.

doc.: IEEE /0219r3 Submission Handling SRP Reservation Requests Mar 2010 Ganesh Venkatesan, Intel Corporation, et alSlide 3

doc.: IEEE /0219r3 Submission Common Scenarios Mar 2010 Ganesh Venkatesan, Intel Corporation, et alSlide 4 Talker AP DMN Listener(s) AP DMN Talker Listener(s)Talker AP Listener(s) non-AP STA Alternate Data Path

doc.: IEEE /0219r3 Submission Advanced Scenario: STA is an Intermediate node or a Talker/Listener Mar 2010 Ganesh Venkatesan, Intel Corporation, et alSlide 5 AP DMN Listener(s) non-AP STA Talker/Listener(s) 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*”. * See

doc.: IEEE /0219r3 Submission 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 MSPRDU Processing at the AP/DMN (adopted proposal – 10/137r0) Mar 2010 Ganesh Venkatesan, Intel Corporation, et alSlide 6

doc.: IEEE /0219r3 Submission MSRP Handling at AP/DMN (to Talker/Listener) In 10/137r0 Mar 2010 Ganesh Venkatesan, Intel Corporation, et alSlide 7

doc.: IEEE /0219r3 Submission Table Q.3 SRP to SME QoS Services Mapping Mar 2010 Ganesh Venkatesan, Intel Corporation, et alSlide 8 MSRP AttributeMAD Primitive SME QoS Service Description Talker AdvertiseMAD_Join_Request (new) SME.QUERYQuery bandwidth availability without reservation Listener Ready or Listener Ready Failed MAD_Join_Request (new) SME.ADDTSReserve bandwidth for a stream Listener Ready or Listener Ready Failed MAD_Join_Request ()SME.ADDTSModify bandwidth reserved for a stream – no renewal needed, if requirements have not changed. Listener Request Removed MAD_Leave_Request ()SME.DELTSFree bandwidth associated with a stream MAD – MRP (Multiple Registration Protocol) Attribute Declaration

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

doc.: IEEE /0219r3 SubmissionSlide 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 ? Should the solution be the same irrespective of if the STA is a Talker/Listener or is just a node in the path from the Talker to the Listener? Mar 2010 Ganesh Venkatesan, Intel Corporation, et alSlide 10

doc.: IEEE /0219r3 Submission Alternate Proposal-A.1 -- MSRP Handling at AP/DMN (to Talker/Listener) Mar 2010 Ganesh Venkatesan, Intel Corporation, et alSlide 11 non-AP STA at the Talker/Listener ends parse SRP and invoke corresponding mechanisms Synchronization issues need to be addressed at the AP

doc.: IEEE /0219r3 Submission Alternate Proposal-A.2 -- MSRP Handling at AP/DMN (to Talker/Listener) Mar 2010 Ganesh Venkatesan, Intel Corporation, et alSlide 12 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 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

doc.: IEEE /0219r3 Submission Alternate Proposal-B -- MSRP Handling at AP/DMN (to Talker/Listener) Mar 2010 Ganesh Venkatesan, Intel Corporation, et alSlide 13 1.Need a new “Reserve” management frame between AP to STA 2.STA at Talker end does not have to parse SRP messages; no additional processing in No synchronization issues 4.Addresses all issues listed in slide-10

doc.: IEEE /0219r3 Submission Mar 2010 Ganesh Venkatesan, Intel Corporation, et alSlide 14 What is in the Reserve Request? 1.TSPEC Element with parameters set to values derived from information in the MSRPDU 2.Optionally TCLAS and TCLAS Processing elements.

doc.: IEEE /0219r3 Submission Mar 2010 Ganesh Venkatesan, Intel Corporation, et alSlide 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

doc.: IEEE /0219r3 Submission Mar 2010 Ganesh Venkatesan, Intel Corporation, et alSlide 16 The TSPEC Element in Reserve Request Element ID LengthTS InfoNominal MSDU Size Max MSDU Size Min Service Interval Max Service Interval Inactivity Interval Suspension Interval EDCA- AC /926r7 Slide #20 SRP Tspec MaxFram eSize + 18 n/a HCCA /925r7 Slide #22 10 ?? Octets Service Start Time Minimum Data Rate Mean Data Rate Peak Data Rate Burst Size Delay Bound Minimum PHY Rate Surplus Bandwidth Allowance Medium Time EDCA- AC n/a (SRP Tspec MaxFram eSize +18) * SRP Tspec MaxInterv alFrames n/a 20msecs * (SRP TSpec MaxFram eSize + 18) * SRP TSpec MaxInterv alFrames bits/sec 1.2n/a HCCA n/a0 (SRP Tspec MaxFram eSize + 18) * SRP Tspec MaxInterv alFrames (SRP Tspec MaxFra meSize + 18) * SRP Tspec MaxInte rvalFra mes * n/a Octets

doc.: IEEE /0219r3 Submission Mar 2010 Ganesh Venkatesan, Intel Corporation, et alSlide 17 Straw Polls 1.Should we stay with just the current solution (Slide-7)? 2.Which of the three alternate proposals do you prefer A.1 A.2 B 3.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)?