Hi Dhruv, authors,
I just took a look at the document. Some high-level comments:
- The document name is bfd-parameters but the rest of the doc talks about
S-BFD. Should the document be renamed fo sbfd-parameters?- The abstract
mentions LSP parameters and S-BFD. In the intro, there's no mention of BFD,
that seems to be an omission. IIUC, the goal is to carry S-BFD parameters per
LSP or LSP group?- Why are Min Tx Interval and multiplier exchanged?- Looking
at RFC7884, it's very clear what's the flow/relationship between S-BFD and OSPF
(below). With PCEP, that relationship isn't very clear to me. Disclaimer: it's
been a while since I looked at PCEP. This document implicitly defines a
relationship between OSPF and
S-BFD. S-BFD assigns one or more discriminators to each S-BFD
reflector node. OSPF, in turn, learns about these from S-BFD and
floods them in the newly defined TLV. After this information is
flooded, it is stored in all the OSPF nodes such that S-BFD
initiators can map out target nodes to target discriminators and can
therefore construct the S-BFD probe.
- RFC7880 should be referenced.
Regards,Reshad.
On Monday, March 27, 2023, 05:20:10 AM EDT, Dhruv Dhody
<[email protected]> wrote:
Hi BFD WG,
We had a new I-D presented in the PCE WG session regarding enabling S-BFD (and
carrying the parameters) for the LSP / SR-paths created by PCE via PCEP.
https://datatracker.ietf.org/doc/draft-fizgeer-pce-pcep-bfd-parameters/00/
If you have any thoughts about this please let the PCE WG know!
Thanks! Dhruv _______________________________________________
Pce mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/pce
