[mpls] Opsdir last call review of draft-ietf-mpls-egress-protection-framework-05
Scott Bradner via Datatracker <noreply@ietf.org> Mon, 17 June 2019 01:46 UTC
Return-Path: <noreply@ietf.org>
X-Original-To: mpls@ietf.org
Delivered-To: mpls@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 23F3512010C; Sun, 16 Jun 2019 18:46:06 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Scott Bradner via Datatracker <noreply@ietf.org>
To: ops-dir@ietf.org
Cc: draft-ietf-mpls-egress-protection-framework.all@ietf.org, ietf@ietf.org, mpls@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.98.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Scott Bradner <sob@sobco.com>
Message-ID: <156073596605.8311.3687141912546256519@ietfa.amsl.com>
Date: Sun, 16 Jun 2019 18:46:06 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/6mn122tlKF9TIkasb3QC_mr29Ww>
Subject: [mpls] Opsdir last call review of draft-ietf-mpls-egress-protection-framework-05
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mpls/>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Jun 2019 01:46:06 -0000
Reviewer: Scott Bradner Review result: Has Nits 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
- [mpls] Opsdir last call review of draft-ietf-mpls… Scott Bradner via Datatracker
- Re: [mpls] Opsdir last call review of draft-ietf-… Yimin Shen