Last Call Review of draft-ietf-bfd-on-lags-02

Request Review of draft-ietf-bfd-on-lags
Requested rev. no specific revision (document currently at 04)
Type Last Call Review
Team Security Area Directorate (secdir)
Deadline 2013-12-02
Requested 2013-11-21
Authors Manav Bhatia, Mach Chen, Sami Boutros, Marc Binderberger, Jeffrey Haas
Draft last updated 2013-12-05
Completed reviews Secdir Last Call review of -02 by Sam Hartman (diff)
Opsdir Last Call review of -02 by Kiran Chittimaneni (diff)
Genart Last Call review of -02 by Joel Halpern (diff)
Assignment Reviewer Sam Hartman
State Completed
Review review-ietf-bfd-on-lags-02-secdir-lc-hartman-2013-12-05
Reviewed rev. 02 (document currently at 04)
Review result Ready
Review completed: 2013-12-05


I seem to be getting easy documents of late.

This document describes how to run BFD over LAGs.  Multiple l2 links are
combined into a larger l2 link for better throughput and load balancing
and redundancy.
>From the standpoint of /l3 these all appear to be a single interface.

If you look at it funny and futz your tables so BFD gets to treat these
interfaces as distinct, you can use BFD to make sure members of the LAG
are up.

If the universe valued good abstraction layers, entire civilizations
would crumble in disgust every time you send one of these packets.
However, it is a useful hack for performance and code re-use.

The document claims that there are no new security considerations.
As far as I can tell, that is true.

I have no concerns.