Mach,
Lots of thanks for an important input.

Regards,
Sasha

From: Mach Chen <mach.c...@huawei.com>
Sent: Friday, October 21, 2022 1:08 PM
To: Jeffrey Haas <jh...@pfrc.org>; Reshad Rahman <res...@yahoo.com>
Cc: BFD WG <rtg-bfd@ietf.org>; Alexander Vainshtein 
<alexander.vainsht...@rbbn.com>; Nitsan Dolev <nitsan.do...@rbbn.com>; Shell 
Nakash <shell.nak...@rbbn.com>; James Lian <james.l...@rbbn.com>
Subject: [EXTERNAL] RE: A missing read/write attribute in RFC 9314?

Hi Jeff,

Huawei's implementation only used dedicated Multicast MAC (when we proposed 
RFC7130), and did not support the optional behavior. There should be no change 
since then.

Best regards,
Mach

From: Rtg-bfd <rtg-bfd-boun...@ietf.org<mailto:rtg-bfd-boun...@ietf.org>> On 
Behalf Of Jeffrey Haas
Sent: Thursday, October 20, 2022 8:52 PM
To: Reshad Rahman <res...@yahoo.com<mailto:res...@yahoo.com>>
Cc: BFD WG <rtg-bfd@ietf.org<mailto:rtg-bfd@ietf.org>>; Alexander Vainshtein 
<alexander.vainsht...@rbbn.com<mailto:alexander.vainsht...@rbbn.com>>; Nitsan 
Dolev <nitsan.do...@rbbn.com<mailto:nitsan.do...@rbbn.com>>; Shell Nakash 
<shell.nak...@rbbn.com<mailto:shell.nak...@rbbn.com>>; James Lian 
<james.l...@rbbn.com<mailto:james.l...@rbbn.com>>
Subject: Re: A missing read/write attribute in RFC 9314?



On Oct 19, 2022, at 3:24 PM, Jeffrey Haas 
<jh...@pfrc.org<mailto:jh...@pfrc.org>> wrote:

I think what this work looks like is:
1. Survey of implementations to see whether they do this behavior, and what
their knob is, if so.

I have confirmed that Juniper's implementation does not support the behavior 
described in this thread.  When in the Up state, Juniper's BFD on LAG uses the 
discovered unicast MAC address.

Xiao Min reports that ZTE's implementation behaves similarly.

It'd be good to get responses from Cisco, Huawei, and Nokia.

-- Jeff


Notice: This e-mail together with any attachments may contain information of 
Ribbon Communications Inc. and its Affiliates that is confidential and/or 
proprietary for the sole use of the intended recipient. Any review, disclosure, 
reliance or distribution by others or forwarding without express permission is 
strictly prohibited. If you are not the intended recipient, please notify the 
sender immediately and then delete all copies, including any attachments.

Reply via email to