Subject: Last Call: <draft-ietf-pals-mpls-tp-dual-homing-coordination-05.txt> (Dual-Homing Coordination for MPLS Transport Profile (MPLS-TP) Pseudowires Protection) to Proposed Standard

From: The IESG <[email-masked]>
Date: Mon, 30 Jan 2017 15:12:49 -0800

The IESG has received a request from the Pseudowire And LDP-enabled
Services WG (pals) to consider the following document:
- 'Dual-Homing Coordination for MPLS Transport Profile (MPLS-TP)
   Pseudowires Protection'
  <draft-ietf-pals-mpls-tp-dual-homing-coordination-05.txt> as Proposed
Standard

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
[email-masked] mailing lists by 2017-02-13. Exceptionally, comments may be
sent to [email-masked] instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

Abstract

   In some scenarios, MPLS Transport Profile (MPLS-TP) Pseudowires (PWs)
   (RFC 5921) may be statically configured (management plane based),
   when a dynamic control plane is not available.  A fast protection
   mechanism for MPLS-TP PWs is needed to protect against the failure of
   an Attachment Circuit (AC), the failure of a Provider Edge (PE), or a
   failure in the Packet Switched Network (PSN).  The framework and
   typical scenarios of dual-homing PW local protection are described in
   [draft-ietf-pals-mpls-tp-dual-homing-protection].  This document
   proposes a dual-homing coordination mechanism for MPLS-TP PWs, which
   is used for state exchange and switchover coordination between the
   dual-homing PEs for dual-homing PW local protection.

The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-pals-mpls-tp-dual-homing-coordination/

IESG discussion can be tracked via
https://datatracker.ietf.org/doc/draft-ietf-pals-mpls-tp-dual-homing-coordination/ballot/

The following IPR Declarations may be related to this I-D:

   https://datatracker.ietf.org/ipr/2534/

The document contains these normative downward references.
See RFC 3967 for additional information: 
    rfc5921: A Framework for MPLS in Transport Networks (Informational - IETF stream)
Note that some of these references may already be listed in the acceptable Downref Registry.