Clarifying Procedures for Establishing BFD Sessions for MPLS Label Switched Paths (LSPs)
RFC 7726

Note: This ballot was opened for revision 03 and is now closed.

Alvaro Retana Yes

(Alia Atlas) No Objection

Deborah Brungard No Objection

Ben Campbell No Objection

(Benoît Claise) No Objection

Spencer Dawkins No Objection

(Stephen Farrell) No Objection

(Brian Haberman) No Objection

Comment (2015-10-14 for -03)
No email
send info
Just a question on this draft... Given its status as clarifying (and updating) RFC 5884, does it also inherit any of the IPR claims levied against RFC 5884?

(Joel Jaeggli) No Objection

Comment (2015-10-12 for -03)
No email
send info
Scott Bradner did the Opsdir review

I have done a OPS-DIR review of "Clarifications to RFC 5884” <draft-ietf-bfd-rfc5884-clarifications-03.txt>

summary - ready for publication

This document clarifies how best to operate multiple BFD (Bidirectional Forwarding Detection) sessions in MPLS environments.  
Any document that purports to clarify operational procedures is, by definition, a good thing when it comes
to operational impact, assuming the document is clear and makes sense.  This document is clear and makes sense.

One suggestion though.
The first observation in Section 2.3 says:

      The BFD session MAY be removed in the egress LSR if the BFD
      session transitions from UP to DOWN.  This can be done after the
      expiry of a configurable timer started after the BFD session state
      transitions from UP to DOWN at the egress LSR.

It might be helpful to specifically say what the aim of using such a timer is.  My guess is that the 
timer is used to introduce hysteresis to reduce flapping - but it would nice to say one way or the other

(Barry Leiba) No Objection

(Kathleen Moriarty) No Objection

Comment (2015-10-13 for -03)
No email
send info
Thanks for your work on this draft.  I'd just ask that you expand out BFD on first use since it is an acronym used frequently in the draft.

(Martin Stiemerling) No Objection