LDP Extensions for Multi Topology Routing
draft-ietf-mpls-ldp-multi-topology-02

The information below is for an old version of the document
Document Type Active Internet-Draft (mpls WG)
Last updated 2011-11-21 (latest revision 2011-10-31)
Replaces draft-zhao-mpls-ldp-multi-topology
Stream IETF
Intended RFC status (None)
Formats plain text pdf html
Stream WG state WG Document
Document shepherd None
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Internet Engineering Task Force                                  Q. Zhao
Internet-Draft                                         Huawei Technology
Intended status: Standards Track                                 L. Fang
Expires: May 24, 2012                                            C. Zhou
                                                           Cisco Systems
                                                                   L. Li
                                                            China Mobile                                                         
                                                                   N. So
                                                        Verizon Business
                                                                R. Torvi
                                                        Juniper Networks
                                                       November 21, 2011

               LDP Extensions for Multi Topology Routing
               draft-ietf-mpls-ldp-multi-topology-02.txt

Abstract

   Multi-Topology (MT) routing is supported in IP through extension of
   IGP protocols, such as OSPF and IS-IS.  It would be advantageous to
   extend Multiprotocol Label Switching (MPLS), using Label Distribution
   Protocol (LDP), to support multiple topologies.  These LDP
   extensions, known as Multiple Topology Label Distribution Protocol
   (MT LDP), would allow the configuration of multiple topologies within
   an MPLS LDP enabled network.

   This document describes the protocol extensions required to extend
   the existing MPLS LDP signalling protocol for creating and
   maintaining LSPs in an MT environment.

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).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any

Zhao, et al.              Expires May 24, 2012                  [Page 1]
Internet-Draft        LDP Multi Topology Extension         November 2011

   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on May 24, 2012.

Copyright Notice

   Copyright (c) 2011 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 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.

Zhao, et al.              Expires May 24, 2012                  [Page 2]
Internet-Draft        LDP Multi Topology Extension         November 2011

Table of Contents

   1.  Terminology  . . . . . . . . . . . . . . . . . . . . . . . . .  4
     1.1.  Requirements Language  . . . . . . . . . . . . . . . . . .  4
   2.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  4
   3.  Requirements . . . . . . . . . . . . . . . . . . . . . . . . .  5
     3.1.  Application Scenarios  . . . . . . . . . . . . . . . . . .  6
       3.1.1.  Simplified Data-plane  . . . . . . . . . . . . . . . .  6
       3.1.2.  Using MT for p2p Protection  . . . . . . . . . . . . .  6
       3.1.3.  Using MT for mLDP Protection . . . . . . . . . . . . .  7
       3.1.4.  Service Separation . . . . . . . . . . . . . . . . . .  7
       3.1.5.  An Alternative inter-AS VPN Solution . . . . . . . . .  7
     3.2.  Signaling Extensions . . . . . . . . . . . . . . . . . . .  7
       3.2.1.  Topology-Scoped Prefix FEC . . . . . . . . . . . . . .  7
       3.2.2.  LDP MT Capability Advertisement  . . . . . . . . . . .  9
       3.2.3.  Procedures . . . . . . . . . . . . . . . . . . . . . . 11
       3.2.4.  LDP Sessions . . . . . . . . . . . . . . . . . . . . . 12
       3.2.5.  Reserved MT ID Values  . . . . . . . . . . . . . . . . 12
     3.3.  MT Applicability on FEC-based features . . . . . . . . . . 13
       3.3.1.  Typed Wildcard Prefix FEC Element  . . . . . . . . . . 13
       3.3.2.  End-of-LIB . . . . . . . . . . . . . . . . . . . . . . 13
Show full document text