This sounds like a good summary of the tactical fix.
(Although, like Les wrote down, saying “MUST follow [LSP-Ping]” is better than
“MUST Send a Reply”)
As an aside -- When it comes to Interop, I remember also issues around the UDP
Port on the egress BFD Control packet, depending on whether the
Hi Balaji,
thank you for sharing your experience with the issue. Had you captured what
are the values of the Return Mode field in Echo request packets in each
case? Perhaps these would explain the behavior of the egress LSR.
Regards,
Greg
On Tue, Aug 15, 2017 at 10:23 PM, Balaji Rajagopalan
wrot
The following errata report has been submitted for RFC5884,
"Bidirectional Forwarding Detection (BFD) for MPLS Label Switched Paths (LSPs)".
--
You may review the report below and at:
http://www.rfc-editor.org/errata/eid5087
Greg –
Thanx.
Section 6.1 currently states:
“If the BFD session is not in UP state, the periodic LSP Ping Echo
request messages MUST include the BFD Discriminator TLV.”
I think this language is unambiguous.
??
Les
From: Greg Mirsky [mailto:gregimir...@gmail.com]
Sent: Tuesday, August 1
Hi Les,
apologies as I wasn't clear in my proposal. I've referred to the Echo reply
sent by the egress LSR. I think that the reference to RFC 8029 in the last
sentence is not sufficient to define use of BFD Discriminator TLV in Echo
reply. I think that Mach has captured it in the new text he provid
