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/eid5085
[Note that I have adjusted the addresses in the headers to try to catch the
RFC authors' current accounts.]
The 5884 interop issue keeps bubbling up. Balaji submitted an errata, which
provides us with a good place to start technical discussion.
Please note I also spent some time off-list discus
Trill WG,
I was recently reminded that trill has an interest in the BFD multipoint
features. (C.f. RFC 7175.)
The BFD Multipoint features are in extended working group last call. Your
input on the documents is solicited:
https://tools.ietf.org/html/draft-ietf-bfd-multipoint-10
https://tools.ie
Re-sending to the corrected list (apologies for duplicates).
Dear All,
I suggest to reject this proposal. The current text is clear and the
mechanics of bootstrapping BFD session over MPLS LSP is well understood -
remote peer MUST start sending BFD control packets first and BFD peer MAY
send Echo
Jeff, WG,
I believe there is one additional consideration — please see inline.
On Aug 11, 2017, at 1:39 PM, Jeffrey Haas
mailto:jh...@pfrc.org>> wrote:
[Note that I have adjusted the addresses in the headers to try to catch the
RFC authors' current accounts.]
The 5884 interop issue keeps bubb
Greg,
> On Aug 11, 2017, at 2:12 PM, Greg Mirsky wrote:
>
> Re-sending to the corrected list (apologies for duplicates).
>
> Dear All,
> I suggest to reject this proposal. The current text is clear and the
> mechanics of bootstrapping BFD session over MPLS LSP is well understood -
> remote pe
