Investigating the Multicast Usage Model for P802.1CQ

Slides:

Advertisements

Similar presentations

IEEE ???.? March, 2007 Ethernet AVB Transport TG Draft for Orlando FL USA March meeting 1 Transport of Time-Sensitive Streaming Audio/Video in Bridged.

Advertisements

Doc.: IEEE /0022r0 Submission July 2005 Steve Shellhammer, Qualcomm Inc.Slide 1 Discussion on Contention-based Protocol (CBP) Study Group Notice:

Addressing IP v4 W.Lilakiatsakun. Anatomy of IPv4 (1) Dotted Decimal Address Network Address Host Address.

IEEE MSC April, 2009 AVB Device Discovery, Connection and Control SG Draft 1 A Device Discovery, Connection Management and Control Protocol for P1722 based.

Consolidated comments on LASG 802c PAR and CSD Stephen Haddock March 11,

Multicast Routing. Unicast: one source to one destination Multicast: one source to many destinations Two main functions: – Efficient data distribution.

Doc.: IEEE 11-04/0319r0 Submission March 2004 W. Steven Conner, Intel Corporation Slide 1 Architectural Considerations and Requirements for ESS.

Doc.: IEEE /0074r2 Submission May 2010 Tuncer Baykas, NICTSlide TG1 Introduction and Status Notice: This document has been prepared to.

Doc.: IEEE /1021r1 Submission July 18, 2006 John Simons, Hitachi America, Ltd.Slide 1 WLAN for Next Generation AV: Motion for SG Creation Date:

Doc.: IEEE /1021r0 Submission July 18, 2006 Todor Cooklev, Hitachi America, Ltd.Slide 1 MAC Extensions for Next Generation AV: Motion for SG Creation.

The OSI Model. History of OSI Model ISO began developing the OSI model in It is widely accepted as a model for understanding network communication.

PAR Review - Agenda and Meeting slides - March 2016

IETF DetNet and IEEE Time-Sensitive Networking

Local MAC Address Assignment Protocol(LAAP) -- Thought on 802.1CQ

Network instantiation

P802.1CM Time-Sensitive Networking for Fronthaul

P802.11aq Waiver request regarding IEEE RAC comments

GCR for mesh Date: January 2011 Authors: January 2011 July 2010

TG1 Introduction and Status

July 2017 Response to comments on 802.1ACct - Amendment: Support for IEEE Std PAR and CSD July 2017 Thomas Kürner, Chair TG3d .

Local MAC Address Protocol

Ethernet : Framing and Addressing

<month year> <doc.: IEEE doc> May 2015

IEEE 802 EC Privacy Recommendation SG Comments on 802c PAR and CSD

NOV 01 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Application Specific Information Element] Date.

Background Information on Amendment and Standard

<month year> doc.: IEEE < e>

IEEE OmniRAN TG Status Report to IEEE 802 WGs

Response to Comments Received on the a PAR and CSD

March 2013 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: Comment Resolution Suggestions Date Submitted:

July 2017 Response to comments on 802.1ACct - Amendment: Support for IEEE Std PAR and CSD July 2017 Thomas Kürner, Chair TG3d .

Proposal for the MAC address assignment protocol

doc.: IEEE <doc#>

<month year> <doc.: IEEE doc> July 2015

IEEE OmniRAN TG February 6th , 2019 Conference Call

doc.: IEEE <doc#>

<month year> doc.: IEEE < e> <November 2018>

New Connection Identifier Approach

New Connection Identifier Approach

July 2013 doc.: IEEE < > July 2013

Project: IEEE Wireless Personal Area Networks (WPANs)

MAC Address Acquisition Protocol

IEEE OmniRAN TG Status Report to IEEE 802 WGs

Video Transport Streaming SG Orlando Opening Report

March 2013 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: Comment Resolution Suggestions Date Submitted:

IEEE OmniRAN TG Status Report to IEEE 802 WGs

PAR Review - Agenda and Meeting slides - March 2016

<month year> doc.: IEEE < e>

Investigating the Multicast Usage Model for P802.1CQ

Jul 12, /12/10 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: Response to PAR and 5C Comments.

IEEE OmniRAN TG Status Report to IEEE 802 WGs

November 2018 Opening Report

P802.11aq Waiver request regarding IEEE RAC comments

P802.11aq Waiver request regarding IEEE RAC comments

MAC Address Acquisition Protocol

16EC Computer networks unit II Mr.M.Jagadesh

doc.: IEEE <doc#1>

Submission Title: [TG5 Closing Report at Mid-Week Plenary, LA, CA]

GCR for mesh Date: January 2011 Authors: January 2011 July 2010

Proposed liaison to IEEE 1722 Working Group

Antonio de la Oliva (UC3M)

Comments to IEEE /68 Date: Authors: September 2009

Investigating the Multicast Usage Model for P802.1CQ

Assignment of Temporary Addresses

Editors: Bala’zs Varga, Jouni Korhonen

Submission Title: TG9ma Closing Report for July Meeting

Summary of MAC Address policy contribution to IEEE

Proposed liaison to IEEE 1722 Working Group

Audio/Video Transport Extensions (avtext) Working Group

Submission Title: TG9ma Closing Report for July Meeting

Presentation transcript:

Investigating the Multicast Usage Model for P802.1CQ Roger Marks (EthAirNet Associates) 2019-01-24

Multicast for P802.1CQ: History The initial P802.1CQ draft PAR was "Local Addresses Assignment” Later, it was changed to "Multicast and Local Address Assignment" As I recall, the TG Chair stated that there was a need to add multicast address assignments for TSN streams. Nothing about multicast was added to the Scope, or to the CSD. The following text added to the Purpose: Multicast flows also need addresses to identify the flows. They will benefit from a set of protocols to distribute multicast addresses.

Multicast for P802.1CQ: History IEEE 1722-2011 ("Transport Protocol for Time-Sensitive Applications in Bridged Local Area Networks") includes specification of the "MAC Address Acquisition Protocol" (MAAP) that seems intended for this purpose. 1722 was revised in 2016 MAAP is not referenced in 802.1Q, 802.1BA, or 802.1CA although 802.1Q cites IEEE 1722 MAAP was mentioned in some 802.1 contributions (2008 and 2009)

Multicast for P802.1CQ: History Avnu (based on 802.1 TSN) uses 1722 MAAP: Multicast MAC addresses or locally administered unicast addresses are required by AVTP for the transmission of media streams. Because AVTP runs directly on a layer 2 transport, there is no existing protocol to allocate multicast MAC addresses dynamically. MAAP is designed to provide a way to allocate dynamically the multicast MAC addresses needed by AVTP. MAAP is not designed to allocate locally administered unicast addresses. “AVNU Milan Network redundancy interoperability specification” June 5, 2018 Revision 1.3

Discussion with TSN Chair I discussed this with TSN Chair. He noted that multicast MAC addresses are part of the Stream ID in Audio Video Bridging inherited by TSN has been developed further by 802.1CB P802.1CBdb will add further possibilities TSN Chair recommended that we ask TSN for views.

Questions for TSN From a TSN perspective, is there a need to specify multicast address assignment beyond the IEEE 1722 MAAP? If so, could we discuss a way forward to reach an understanding of the usage model and requirements? If not, should P802.1CQ simply include suitable references to IEEE 1722?