Video Transport Streaming SG PAR Scope Statement Discussion November 2007 doc.: IEEE 802.11-07/2752r1 January 2008 Video Transport Streaming SG PAR Scope Statement Discussion Date: 2008-01-27 Authors: Ganesh Venkatesan, Intel Corporation Peter Ecclesine, Cisco Systems

November 2007 doc.: IEEE 802.11-07/2752r1 January 2008 Abstract This submission is a starting point for discussion(s) on the completeness of Video Transport Streaming PAR Scope Statement. Ganesh Venkatesan, Intel Corporation Peter Ecclesine, Cisco Systems

General Concerns Typographical Errors January is spelt incorrectly Hitachi is spelt incorrectly Ganesh Venkatesan, Intel Corporation

Current Scope Statement (07/1972r11) November 2007 doc.: IEEE 802.11-07/2752r1 January 2008 Current Scope Statement (07/1972r11) 5.2 Scope of Proposed Standard: This amendment defines enhancements to the 802.11 MAC for robust video streaming, while maintaining co-existence with other types of traffic. The MAC enhancements specified in this amendment are: Interworking with relevant 802.1 mechanisms including, but not limited to, 802.1Qat, 802.1Qav and 802.1AS Enabling graceful degradation of video streams when there is insufficient channel capacity. Increasing robustness in overlapping BSS environments, without the requirement for a centralised management entity. Modifying EDCA timing and parameter selection for video transport Improving Multicast/Broadcast video streams for link reliability with low delay and jitter. Ganesh Venkatesan, Intel Corporation Peter Ecclesine, Cisco Systems

Concerns on Scope Statement January 2008 Concerns on Scope Statement The leading text does not meld well with the bullets – “The MAC enhancements specified in this amendment are: Enabling graceful degradation of video streams when there is insufficient channel capacity.” Implied “Upper layer mechanisms” in layer 2 (bullets-2/4) Implied “deep packet inspection” (bullets -2/4) Relevance of 802.1 mechanisms to VTS in the home environment 802.11 STA Bridge Ganesh Venkatesan, Intel Corporation

Proposed Modification January 2008 Proposed Modification 5.2 This amendment defines enhancements to the 802.11 MAC for robust video streaming, while maintaining co-existence with other types of traffic.  The MAC enhancements specified in this amendment are enables: Interworking with relevant 802.1 mechanisms including, but not limited to, 802.1Qat, 802.1Qav and 802.1AS, EnablingUse of 802.1ad drop precedence to gracefully degradeation of quality of video streams when there is insufficient channel capacity, Increaseding robustness in overlapping BSS environments, without the requirement for a centralised management entity, Modifying EDCA timing and parameter selection for video transportPrioritizing between traffic streams within the same Access Category and between data within the same traffic stream without any requirement for deep packet inspection, Improveding Multicast/Broadcast video streams for link reliability with low delay and jitter. Ganesh Venkatesan, Intel Corporation

Proposed Modifications (1/28/08) January 2008 Proposed Modifications (1/28/08) 5.2 This amendment defines enhancements to the 802.11 MAC for robust video streaming, while maintaining co-existence with other types of traffic.  The MAC enhancements specified in this amendment are enable: Interworking with relevant 802.1 mechanisms including, but not limited to, 802.1Qat, 802.1Qav and 802.1AS, EnablingGraceful degradation of video streams when there is insufficient channel capacity, Increaseding robustness in overlapping BSS environments, without the requirement for a centralised management entity, Modifying EDCA timing and parameter selection for video transport without any requirement for deep packet inspection, Improveding Multicast/Broadcast video streams for link reliability with low delay and jitter. Ganesh Venkatesan, Intel Corporation

Proposed Modifications (1/31/08) (take-1) Joint meeting with 802.1 January 2008 Proposed Modifications (1/31/08) (take-1) Joint meeting with 802.1 5.2 This amendment defines enhancements to the 802.11 MAC for robust video streaming, while maintaining co-existence with other types of traffic.  The MAC enhancements specified in this amendment are enables interworking with relevant 802.1 AVB mechanisms (e.g. 802.1Qat, 802.1Qav, 802.1AS), Within the 802.11 BSS, the MAC enhancements specified in this amendment enable: EnablingGraceful degradation of video streams when there is insufficient channel capacity, Increaseding robustness in overlapping BSS environments, without the requirement for a centralised management entity, Modifying EDCA timing and parameter selection for video transport without any requirement for deep packet inspection, Improveding Multicast/Broadcast video streams for link reliability with low delay and jitter. Ganesh Venkatesan, Intel Corporation

Proposed Modifications (1/31/08) -- final Joint meeting with 802.1 January 2008 Proposed Modifications (1/31/08) -- final Joint meeting with 802.1 5.2 This amendment defines enhancements to the 802.11 MAC for robust audio video streaming, while maintaining co-existence with other types of traffic.  The MAC enhancements specified in this amendment are enable: Interworking with relevant 802.1 mechanisms including, but not limited to, 802.1Qat, 802.1Qav and 802.1AS, EnablingGraceful degradation of video streams when there is insufficient channel capacity, Increaseding robustness in overlapping BSS environments, without the requirement for a centralised management entity, Modifying EDCA timing and parameter selection for video transport without any requirement for deep packet inspection, Improveding Multicast/Broadcast video streams for link reliability with low delay and jitter, Interworking with relevant 802.1 AVB mechanisms (e.g. 802.1Qat, 802.1Qav, 802.1AS). Ganesh Venkatesan, Intel Corporation

January 2008 Audio Video Bridge Interworking with relevant 802.1 mechanisms including, but not limited to, 802.1Qat, 802.1Qav and 802.1AS, Ganesh Venkatesan, Intel Corporation

January 2008 802.11 STA Bridge Today, an 802.11 cannot fully function as a bridge.  Example:  If a STA which bridges between several interfaces (including at least one 802.11 interface) bridges a broadcast frame to the AP that was received on an a different interface, the AP will eventually reflect the frame back to the STA, and the STA cannot know for sure whether or not it should forward that frame out the other interfaces it is attached to.  To forward the broadcast frame back toward the interface on which it arrived (or on another interface twice) would violate the rules of an 802 LAN.   One possible solution is to use the 4-address format so that the STA bridge can see its own MAC as the source and then ignore the frame. Ganesh Venkatesan, Intel Corporation

802.11 STA Bridge Thoughts? January 2008 Ganesh Venkatesan, Intel Corporation