Multi-chassis PON Protection in MPLS
draft-ietf-pals-mc-pon-01

The information below is for an old version of the document
Document Type Active Internet-Draft (pals WG)
Last updated 2015-07-06
Replaces draft-jiang-pwe3-mc-pon
Stream IETF
Intended RFC status (None)
Formats pdf htmlized bibtex
Reviews
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                  Y. Jiang, Ed.
Internet Draft                                                Y. Luo
Intended status: Standards Track                              Huawei
                                                    E. Mallette, Ed.
                                               Bright House Networks
C. Shen                                                      Y. Shen
China Telecom                                       Juniper Networks
W. Cheng                                                     G. Zhou
China Mobile                                            China Unicom
Expires: January 2016                                   July 6, 2015

                    Multi-chassis PON Protection in MPLS
                       draft-ietf-pals-mc-pon-01.txt

Status of this Memo

   This Internet-Draft is submitted to IETF in full conformance with
   the provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF), its areas, and its working groups.  Note that
   other groups may also distribute working documents as Internet-
   Drafts.

   Internet-Drafts are draft documents valid for a maximum of six
   months and may be updated, replaced, or obsoleted by other documents
   at any time.  It is inappropriate to use Internet-Drafts as
   reference material or to cite them other than as "work in progress."

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/ietf/1id-abstracts.txt

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html

   This Internet-Draft will expire on January 6, 2013.

Copyright Notice

   Copyright (c) 2015 IETF Trust and the persons identified as the
   document authors. All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with
   respect to this document. Code Components extracted from this

Jiang, et al           Expires January 6, 2016              [Page 1]
Internet-Draft            MC-PON Protection                July 2015

   document must include Simplified BSD License text as described in
   Section 4.e of the Trust Legal Provisions and are provided without
   warranty as described in the Simplified BSD License.

Abstract

   MPLS is being deployed deeper into operator networks, often to or
   past the access network node. Separately network access nodes such
   as PON OLTs have evolved to support first-mile access protection,
   where one or more physical OLTs provide first-mile diversity to the
   customer edge. Multi-homing support is needed on the MPLS-enabled
   PON OLT to provide resiliency for provided services.  This document
   describes the multi-chassis PON protection architecture in MPLS and
   also proposes the ICCP extension to support it.

Table of Contents

   1.   Conventions used in this document ......................... 2
   2.   Terminology ............................................... 3
   3.   Introduction .............................................. 3
   4.   ICCP Protocol Extensions .................................. 6
      4.1. Multi-chassis PON Application TLVs ..................... 6
      4.1.1.  PON Connect TLV ..................................... 6
      4.1.2.  PON Disconnect TLV .................................. 7
      4.1.3.  PON Configuration TLV ............................... 8
      4.1.4.  PON State TLV ....................................... 9
      4.1.5.  PON ONU Database Sync TLV ........................... 9
   5.   PON ONU Database Synchronization ......................... 11
   6.   Multi-chassis PON application procedures ................. 11
      6.1. Protection procedure upon PON link failures ........... 13
      6.2. Protection procedure upon PW failures ................. 13
      6.3. Protection procedure upon the working OLT failure ..... 14
   7.   Security Considerations .................................. 14
   8.   IANA Considerations ...................................... 14
   9.   References ............................................... 14
      9.1. Normative References .................................. 14
      9.2. Informative References ................................ 15
   10.  Acknowledgments .......................................... 15
   Authors' Addresses ............................................ 16

1. Conventions used in this document

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in [RFC2119].

Jiang, et al           Expires January 6, 2016              [Page 2]
Show full document text