Re: [1904.2 TF] OAM Destination MAC Address

[Kevin A Noll <ieee.lists@xxxxxxxxxxxxxxx>]

That’s what I thought, too. Just wanted to confirm.

Thanks

—kan— 

On Nov 2, 2020, at 4:56 PM, Glen Kramer <000006d1020766de-dmarc-request@xxxxxxxxxxxxxxxxx> wrote:

Yes, this was the main motivation to start 1904.2. 

 

-Glen

 

From: Curtis Knittle <C.Knittle@xxxxxxxxxxxxx> 
Sent: Monday, November 02, 2020 11:57 AM
To: Glen Kramer <glen.kramer@xxxxxxxxxxxx>; STDS-1904-2-TF@xxxxxxxxxxxxxxxxx
Subject: RE: [1904.2 TF] OAM Destination MAC Address

 

In fact, isn’t this what led us down the road to 1904.2?

 

From: Glen Kramer <000006d1020766de-dmarc-request@xxxxxxxxxxxxxxxxx> 
Sent: Monday, November 2, 2020 11:34 AM
To: STDS-1904-2-TF@xxxxxxxxxxxxxxxxx
Subject: Re: [1904.2 TF] OAM Destination MAC Address

 

No, not allowed per 802.3, Clause 57:

 

<image001.jpg>

 

-Glen

 

From: Kevin Noll <kevin.noll@xxxxxxxxxxxx> 
Sent: Sunday, November 01, 2020 6:41 PM
To: Glen Kramer <glen.kramer@xxxxxxxxxxxx>
Cc: stds-1904-2-TF@xxxxxxxxxxxxxxxxx
Subject: OAM Destination MAC Address

 

Glen,

 

Is it allowed for an OAMPDU to have a destination MAC address that is NOT SP_MAC_ADDR, but is the MAC address of the destination OAM peer?

 

For example:

 

Given two IEEE 802.3 Clause 57 OAM Sublayer entities: OAM Peer A and OAM Peer Z

 

What is the expected behavior at OAM Peer Z, if OAM Peer A sends an OAMPDU with SRC_ADDR==OAM Peer A and DST_ADDR==OAM Peer Z ??

 

Will OAM Peer Z correctly receive and process the OAMPDU? Will it drop the OAMPDU? Will it do something else?

 

--

Kevin A. Noll

---

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

---

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