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

The information below is for an old version of the document
Document Type Active Internet-Draft (mpls WG)
Last updated 2013-11-11 (latest revision 2013-10-14)
Replaces draft-zhao-mpls-ldp-multi-topology
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf html
Stream WG state Submitted to IESG for Publication
Consensus Unknown
Document shepherd Loa Andersson
Shepherd write-up Show (last changed 2013-10-16)
IESG IESG state Waiting for AD Go-Ahead::Revised I-D Needed
Telechat date
Responsible AD Adrian Farrel
IESG note Loa Andersson <loa@pi.nu> is the document shepherd
Send notices to mpls-chairs@tools.ietf.org, draft-ietf-mpls-ldp-multi-topology@tools.ietf.org
IANA IANA review state IANA - Not OK
IANA action state None
Internet Engineering Task Force                                  Q. Zhao
Internet-Draft                                         Huawei Technology
Intended status: Standards Track                                 L. Fang
Expires: April 18, 2014                                          C. Zhou
                                                           Cisco Systems
                                                                   L. Li
                                                            China Mobile
                                                                 K. Raza
                                                           Cisco Systems
                                                        October 14, 2013

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

Abstract

   Multi-Topology (MT) routing is supported in IP networks with the use
   of MT aware IGPs.  In order to provide MT routing within
   Multiprotocol Label Switching (MPLS) Label Distribution Protocol
   (LDP) networks new extensions are required.

   This document describes the LDP protocol extensions required to
   support MT routing in an MPLS environment.

Status of this Memo

   This Internet-Draft is submitted 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
   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 April 20, 2014.

Copyright Notice

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

Zhao, et al.             Expires April 20, 2014                 [Page 1]
Internet-Draft        LDP Multi Topology Extensions         October 2013

   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 April 20, 2014                 [Page 2]
Internet-Draft        LDP Multi Topology Extensions         October 2013

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  4
   2.  Terminology  . . . . . . . . . . . . . . . . . . . . . . . . .  4
   3.  Signaling Extensions . . . . . . . . . . . . . . . . . . . . .  5
     3.1.  Topology-Scoped Forwarding Equivalence Class (FEC) . . . .  5
     3.2.  New Address Families: MT IP  . . . . . . . . . . . . . . .  5
     3.3.  LDP FEC Elements with MT IP AF . . . . . . . . . . . . . .  6
     3.4.  IGP MT-ID Mapping and Translation  . . . . . . . . . . . .  7
     3.5.  LDP MT Capability Advertisement  . . . . . . . . . . . . .  7
       3.5.1.  Protocol Extension . . . . . . . . . . . . . . . . . .  7
       3.5.2.  Procedures . . . . . . . . . . . . . . . . . . . . . .  9
     3.6.  LDP Sessions . . . . . . . . . . . . . . . . . . . . . . . 10
     3.7.  Reserved MT ID Values  . . . . . . . . . . . . . . . . . . 10
   4.  MT Applicability on FEC-based features . . . . . . . . . . . . 10
     4.1.  Typed Wildcard FEC Element . . . . . . . . . . . . . . . . 10
     4.2.  End-of-LIB . . . . . . . . . . . . . . . . . . . . . . . . 11
     4.3.  LSP Ping . . . . . . . . . . . . . . . . . . . . . . . . . 11
       4.3.1.  New FEC Sub-Types  . . . . . . . . . . . . . . . . . . 11
       4.3.2.  MT LDP IPv4 FEC Sub-TLV  . . . . . . . . . . . . . . . 12
       4.3.3.  MT LDP IPv6 FEC Sub-TLV  . . . . . . . . . . . . . . . 12
       4.3.4.  Operation Considerations . . . . . . . . . . . . . . . 13
   5.  Error Handling . . . . . . . . . . . . . . . . . . . . . . . . 13
     5.1.  MT Error Notification for Invalid Topology ID  . . . . . . 13
   6.  Backwards Compatibility  . . . . . . . . . . . . . . . . . . . 13
   7.  MPLS Forwarding in MT  . . . . . . . . . . . . . . . . . . . . 14
   8.  Security Consideration . . . . . . . . . . . . . . . . . . . . 14
   9.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 14
Show full document text