Skip to main content

Last Call Review of draft-ietf-bfd-on-lags-02
review-ietf-bfd-on-lags-02-opsdir-lc-chittimaneni-2013-12-10-00

Request Review of draft-ietf-bfd-on-lags
Requested revision No specific revision (document currently at 04)
Type Last Call Review
Team Ops Directorate (opsdir)
Deadline 2013-12-03
Requested 2013-11-20
Authors Manav Bhatia , Mach Chen , Sami Boutros , Marc Binderberger , Jeffrey Haas
I-D last updated 2013-12-10
Completed reviews Secdir Last Call review of -02 by Sam Hartman (diff)
Opsdir Last Call review of -02 by Kiran K. Chittimaneni (diff)
Genart Last Call review of -02 by Joel M. Halpern (diff)
Assignment Reviewer Kiran K. Chittimaneni
State Completed
Request Last Call review on draft-ietf-bfd-on-lags by Ops Directorate Assigned
Reviewed revision 02 (document currently at 04)
Result Ready
Completed 2013-12-10
review-ietf-bfd-on-lags-02-opsdir-lc-chittimaneni-2013-12-10-00
Hello!

As a member of the Operations Directorate, I have reviewed the following draft
for its operational impact. These comments  have been written primarily for the
benefit of the operations area directors.  Document editors and WG chairs
should treat these comments just like any other last call comments. I hope
these comments are clear and useful.

Bidirectional Forwarding Detection (BFD) on Link Aggregation Group (LAG)
Interfaces (Intended Status: Standards Track)

http://tools.ietf.org/html/draft-ietf-bfd-on-lags-03

This specification defines a mechanism to run BFD on Link Aggregation Group
(LAG) interfaces.  It does so by running an independent Asynchronous mode BFD
session on every LAG member link. The solution defined here allows operators
who have already deployed BFD over different technologies such as IP, MPLS, to
use a common failure detection mechanism.

Overall, the document is well written and I don't see any specific issues.

From an operational and manageability point of view (using RFC 5706 as
guidance), I find that several of those considerations are either specified or
implied across various sections of the doc. However, just as an option, it
would have been nice to have a specific section or an appendix that caters
towards various operational and management considerations that implementors and
operators can reference. For example, it would be useful to have a specific
section with advice regarding the management and reporting of this solution.

Regards,

KK