Thread Links Date Links
Thread Prev Thread Next Thread Index Date Prev Date Next Date Index

Re: [1904.2 TF] Expected Forwarding Behavior?



Of course, any multi-hop L2 path goes through MAC relays. But in your diagram, there is no L2 path from the *TX interface* of OAM sublayer A to *RX interface* of OAM sublayer Z, with or without MAC relays. It has nothing to do with VLC sublayer and where it is located.

 

-Glen

 

From: Kevin Noll <kevin.noll@xxxxxxxxxxxx>
Sent: Friday, October 30, 2020 6:54 AM
To: Glen Kramer <glen.kramer@xxxxxxxxxxxx>
Cc: stds-1904-2-TF@xxxxxxxxxxxxxxxxx
Subject: Re: [1904.2 TF] Expected Forwarding Behavior?

 

OAM A and OAM Z are OAM Sublayer entities.

 

OAM A might be a “Manager” for OAM Z (e.g. OAM Z is on an ONU)

 

Agreed, an L2 path needs to exist… it could exist via the MAC relay, but VLC is below MAC relay, so how does the frame get back up the stack?

 

--kan--

--

 

From: Glen Kramer <glen.kramer@xxxxxxxxxxxx>
Date: Thursday, October 29, 2020 at 7:34 PM
To: Kevin Noll <kevin.noll@xxxxxxxxxxxx>
Cc: stds-1904-2-TF@xxxxxxxxxxxxxxxxx <stds-1904-2-TF@xxxxxxxxxxxxxxxxx>
Subject: RE: [1904.2 TF] Expected Forwarding Behavior?

What are OAM A and OAM Z exactly, in IEEE terms? Are these OAM Clients?

 

For OAM Client A to talk to OAM Client Z, there should exist a L2 path from TX interface of OAM sublayer A to RX interface of OAM sublayer Z. You diagram does not show any such path.

 

-Glen

 

From: Kevin Noll <kevin.noll@xxxxxxxxxxxx>
Sent: Thursday, October 29, 2020 4:10 PM
To: Glen Kramer <glen.kramer@xxxxxxxxxxxx>
Cc: stds-1904-2-TF@xxxxxxxxxxxxxxxxx
Subject: Re: [1904.2 TF] Expected Forwarding Behavior?

 

I should have asked my question more specifically...

 

What happens if OAM A wants to talk to OAM Z via VLC?

Sent from my mobile device

 

On Oct 29, 2020, at 6:38 PM, Glen Kramer <glen.kramer@xxxxxxxxxxxx> wrote:



The OAMPDUs received by the port on the left (MAC A) will be delivered to OAM client located above OAM SL Z (not shown).  This is one direction of the use case described in 8A.3.

 

<image002.png>

 

The diagram below corresponds to the direction from Station S to Manager M. Port A below is the same as Bridge Y Port 0 here, port Z is the same Port M (Manager) here. The diagram below shows only one intermediate bridge, but there can be any number of them.

 

-Glen

 

From: Kevin Noll <kevin.noll@xxxxxxxxxxxx>
Sent: Wednesday, October 28, 2020 12:48 PM
To: STDS-1904-2-TF@xxxxxxxxxxxxxxxxx
Subject: [1904.2 TF] Expected Forwarding Behavior?

 

Glen, et al,

 

Given the topology and rule in the picture below, what is the expected behavior?

 

<image001.png>

 

 


To unsubscribe from the STDS-1904-2-TF list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-1904-2-TF&A=1


To unsubscribe from the STDS-1904-2-TF list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-1904-2-TF&A=1

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature