Jeff,
Thank you for the quick reply.
Please see inline...
Original
From: JeffreyHaas
To: 肖敏10093570;
Cc: Reshad Rahman ;BFD WG ;Alexander
Vainshtein ;Nitsan Dolev
;Shell Nakash
;james.l...@rbbn.com ;
Date: 2022年11月04日 19:22
Subject: Re: A missing read/write attribute in RFC 9314?
Jeff,
Thank you for the quick reply.
Please see inline...
Original
From: JeffreyHaas
To: 肖敏10093570;
Cc: Bocci, Matthew (Nokia - GB) ;n...@ietf.org
;rtg-bfd@ietf.org ;
Date: 2022年11月04日 19:20
Subject: Re: Extending WG LC for draft-ietf-nvo3-bfd-geneve by two weeks
Xiao Min,
+1 and phew.
Regards,Reshad.
On Friday, November 4, 2022, 07:22:30 AM EDT, Jeffrey Haas
wrote:
Thank you for the correction and apologies for my error in copying, Xiao Min.
It would seem that Juniper is unique in using the learned MAC address for the
session. :-)
However, none of the
Thank you for the correction and apologies for my error in copying, Xiao Min.
It would seem that Juniper is unique in using the learned MAC address for the
session. :-)
However, none of the implementations permit dynamic use of both. We have
compliant implementations that do not need
Xiao Min,
> On Nov 3, 2022, at 10:52 PM,
> wrote:
>> : If the BFD packet is received with Your Discriminator equals to 0, the BFD
>> : session MUST be identified using the VNI number, and the inner
>> : Ethernet/IP/UDP Header, i.e., the source MAC, the source IP, the
>> destination
>> : MAC,
