Use of Multipath with MPLS-TP and MPLS
draft-villamizar-mpls-multipath-use-00

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2012-11-12
Replaces draft-villamizar-mpls-tp-multipath
Replaced by draft-ietf-mpls-multipath-use, rfc7190
Stream (None)
Intended RFC status (None)
Formats pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
MPLS                                                  C. Villamizar, Ed.
Internet-Draft                                    Outer Cape Cod Network
Intended status: Informational                                Consulting
Expires: May 16, 2013                                  November 12, 2012

                 Use of Multipath with MPLS-TP and MPLS
                 draft-villamizar-mpls-multipath-use-00

Abstract

   Many MPLS implementations have supported multipath techniques and
   many MPLS deployments have used multipath techniques, particularly in
   very high bandwidth applications, such as provider IP/MPLS core
   networks.  MPLS-TP has strongly discouraged the use of multipath
   techniques.  Some degradation of MPLS-TP OAM performance cannot be
   avoided when operating over many types of multipath implementations.

   Using MPLS Entropy label, MPLS can LSP can be carried over multipath
   links while also providing a fully MPLS-TP compliant server layer for
   MPLS-TP LSP.  This document describes the means of supporting MPLS as
   a server layer for MPLS-TP.  The use of MPLS-TP LSP as a server layer
   for MPLS LSP is also discussed.

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 May 16, 2013.

Copyright Notice

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

Villamizar                Expires May 16, 2013                  [Page 1]
Internet-Draft         MPLS-TP and MPLS Multipath          November 2012

   (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.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . . . 3
   2.  Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . 3
   3.  MPLS as a Server Layer for MPLS-TP  . . . . . . . . . . . . . . 5
   4.  MPLS-TP as a Server Layer for MPLS  . . . . . . . . . . . . . . 7
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 8
   6.  Security Considerations . . . . . . . . . . . . . . . . . . . . 8
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . . . 8
     7.1.  Normative References  . . . . . . . . . . . . . . . . . . . 8
     7.2.  Informative References  . . . . . . . . . . . . . . . . . . 8
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . . . 9

Villamizar                Expires May 16, 2013                  [Page 2]
Internet-Draft         MPLS-TP and MPLS Multipath          November 2012

1.  Introduction

   Today the requirement to handle large aggregations of traffic, can be
   handled by a number of techniques which we will collectively call
   multipath.  Multipath applied to parallel links between the same set
   of nodes includes Ethernet Link Aggregation [IEEE-802.1AX], link
   bundling [RFC4201], or other aggregation techniques some of which may
   be vendor specific.  Multipath applied to diverse paths rather than
   parallel links includes Equal Cost MultiPath (ECMP) as applied to
   OSPF, ISIS, or BGP, and equal cost LSP.  Some vendors support load
   split across equal cost MPLS LSP where the load is split
   proportionally to the reserved bandwidth of the set of LSP.

   RFC 5654 requirement 33 requires the capability to carry a client
   MPLS-TP or MPLS layer over a server MPLS-TP or MPLS layer [RFC5654].
   This is possible in all cases with one exception.  When an MPLS LSP
   exceeds the capacity of any single component link it may be carried
   by a network using multipath techniques, but may not be carried by an
   MPLS-TP LSP due to the inherent MPLS-TP capacity limitation imposed
   by MPLS-TP OAM packet ordering constraints.

   The term composite link is more general than terms such as link
   aggregation (which is specific to Ethernet) or ECMP (which implies
   equal cost paths within a routing protocol).  The use of the term
Show full document text