90 likes | 97 Views
802.11aa – Robust Audio Video Transport Streaming Los Angeles Closing Report. Authors:. Date: 2009-01-22. Abstract. This submission summarizes the outcomes of the meetings Task Group 802.11aa had during the Los Angeles Session. Closing Report. Slide 3.
E N D
802.11aa – Robust Audio Video Transport Streaming Los Angeles Closing Report Authors: Date: 2009-01-22 Ganesh Venkatesan, Intel Corporation
Abstract This submission summarizes the outcomes of the meetings Task Group 802.11aa had during the Los Angeles Session. Ganesh Venkatesan, Intel Corporation
Closing Report Slide 3 Ganesh Venkatesan, Intel Corporation
802.11aa Goal(s) for the Los Angeles Session Listen to proposals 08/0764-01 Using Packet Drop Precedence for Graceful Degradation 09/0045-00 OBSS Simplification 09/0022-00 Implementation for Intra AC differentiated Services 08/1244-00 Multicast Normative text discussion 09/0130-02 Efficient Error Control using BlockAck and Network Coding for Multicast 09/0124r0 EDCA and BlockAck extensions for Reliable Multicast/Broadcast Services Agree on a OBSS definition Converge on reliable multicast proposal(s) [& adopt normative text] Agree on Intra-AC prioritization strategy [& adopt normative text] Listen to technical proposals on other topic(s) Plan agenda topics for joint meeting with 802.1AVB Slide 4 Ganesh Venkatesan, Intel Corporation
What is OBSS? OBSS Definitions: OBSS edge -- Any two APs operating in the same channel and can hear each other (either directly or via a STA associated to one of the APs) OBSS Graph – is a graph where APs are nodes of the graph and the edges are OBSS edges and every AP within the OBSS graph can be connected via one or more OBSS APs to every other AP in the OBSS graph Length(OBSS graph) – longest shortest path between any two APs in the OBSS graph Size(OBSS graph) – number of nodes (APs) in the OBSS graph Scope of OBSS Solution – if length(OBSS graph) <= 2 and the size(OBSS graph) <=3 , enable the OBSS QAP solution otherwise (a) backoff to legacy (non .11aa) mode or (b) use a different solution Slide 5 Ganesh Venkatesan, Intel Corporation
Reliable Multicast • Documents 08/1244r0, 09/0015r0 and 09/125r0 are normative texts proposed for Reliable Multicast. • Numerous mechanisms (some similar in strategy) are proposed and specified in the normative text document(s) above • It is not clear how each of these mechanisms stack up against each other • It is clear that the above normative text submissions can be harmonized into one In the upcoming teleconferences TGaa will resolve the above issues and produce normative text ready for adoption in the March meeting. Ganesh Venkatesan, Intel Corporation
Intra AC and Intra Stream Prioritization • Documents 08/0764r1and 09/0022r0 are the proposals. • Need to confirm with 802.1 if these mechanisms will work as expected in a wired/wireless network In the joint meeting with 802.1AVB this topic will be discussed in detail. Ganesh Venkatesan, Intel Corporation
Plans For upcoming teleconferences Evaluate and prioritize reliable multicast options To meet jointly with 802.1AVB in March ‘09 Prepare Designated Multimedia Stream Reservation Protocol Node input discussion Prepare for Drop Precedence discussion For Mar ‘09 (Vancouver, BC) Session Adopt reliable multicast proposals into the draft Review and converge on OBSS definition/solution Based on input from 802.1AVB adopt Intra-AC, Intra-Stream normative text Complete Draft 0.01 Slide 8 Ganesh Venkatesan, Intel Corporation
Teleconference Schedule Three Bi-Weekly on Mondays at 11:00 Eastern Time (1 hour long) starting from Feb 02, 2009 • Feb 02, 2009 • Feb 16, 2009 • Mar 02, 2009 Ganesh Venkatesan, Intel Corporation