Last Call Review of draft-ietf-mpls-egress-protection-framework-05

Request Review of draft-ietf-mpls-egress-protection-framework
Requested rev. no specific revision (document currently at 07)
Type Last Call Review
Team Ops Directorate (opsdir)
Deadline 2019-06-17
Requested 2019-06-03
Authors Yimin Shen, Jeyananth Jeganathan, Bruno Decraene, Hannes Gredler, Carsten Michel, Huaimo Chen
Draft last updated 2019-06-16
Completed reviews Rtgdir Last Call review of -03 by Sasha Vainshtein (diff)
Secdir Last Call review of -05 by Christian Huitema (diff)
Genart Last Call review of -05 by Peter Yee (diff)
Opsdir Last Call review of -05 by Scott Bradner (diff)
Secdir Telechat review of -06 by Christian Huitema (diff)
Assignment Reviewer Scott Bradner
State Completed
Review review-ietf-mpls-egress-protection-framework-05-opsdir-lc-bradner-2019-06-16
Posted at
Reviewed rev. 05 (document currently at 07)
Review result Has Nits
Review completed: 2019-06-16


I did an OPS-DIR review of MPLS Egress Protection Framework (draft-ietf-mpls-egress-protection-framework) – The document describes a protection mechanism for the egress links of an MPLS network.  The function described looks quitter useful (at least for multi homed sites that are using MPLS services) 

I did not find any operational issues of note and consider the document ready for publication except for one ops-related observation.  I did not see any discussion of how a management station would be notified if a protection circuit were to be utilized.  It seems to me that is something that a network operation would like to know. I admit to not knowing how a network operator knows when any of the fast reroute techniques are engaged so I may be missing some basic fact about how MPLS networks are operated and monitored but some words of guidance would seem to be useful or some alert function added to the node that does the switching would be helpful