Requirements for Advanced Multipath in MPLS Networks
draft-ietf-rtgwg-cl-requirement-13

The information below is for an old version of the document
Document Type Active Internet-Draft (rtgwg WG)
Last updated 2013-12-24 (latest revision 2013-11-13)
Stream IETF
Intended RFC status Informational
Formats pdf htmlized bibtex
Reviews
Stream WG state Submitted to IESG for Publication
Document shepherd Alia Atlas
Shepherd write-up Show (last changed 2013-11-25)
IESG IESG state Waiting for Writeup::Revised I-D Needed
Consensus Boilerplate Yes
Telechat date
Responsible AD Stewart Bryant
IESG note Alia Atlas (akatlas@gmail.com) is the document shepherd.
Send notices to rtgwg-chairs@tools.ietf.org, draft-ietf-rtgwg-cl-requirement@tools.ietf.org
IANA IANA review state IANA OK - No Actions Needed
RTGWG                                                 C. Villamizar, Ed.
Internet-Draft                                                OCCNC, LLC
Intended status: Informational                           D. McDysan, Ed.
Expires: May 17, 2014                                            Verizon
                                                                 S. Ning
                                                     Tata Communications
                                                                A. Malis
                                                              Consultant
                                                                 L. Yong
                                                              Huawei USA
                                                       November 13, 2013

          Requirements for Advanced Multipath in MPLS Networks
                   draft-ietf-rtgwg-cl-requirement-13

Abstract

   This document provides a set of requirements for Advanced Multipath
   in MPLS Networks.

   Advanced Multipath is a formalization of multipath techniques
   currently in use in IP and MPLS networks and a set of extensions to
   existing multipath techniques.

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 17, 2014.

Copyright Notice

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

Villamizar, et al.        Expires May 17, 2014                  [Page 1]
Internet-Draft       Advanced Multipath Requirements       November 2013

   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.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Requirements Language . . . . . . . . . . . . . . . . . .   3
   2.  Definitions . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Functional Requirements . . . . . . . . . . . . . . . . . . .   6
     3.1.  Availability, Stability and Transient Response  . . . . .   6
     3.2.  Component Links Provided by Lower Layer         Networks    7
     3.3.  Component Links with Different Characteristics  . . . . .   7
     3.4.  Considerations for Bidirectional Client LSP . . . . . . .   8
     3.5.  Multipath Load Balancing Dynamics . . . . . . . . . . . .   9
   4.  General Requirements for Protocol Solutions . . . . . . . . .  11
   5.  Management Requirements . . . . . . . . . . . . . . . . . . .  12
   6.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  13
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  13
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .  13
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  14
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .  14
     9.2.  Informative References  . . . . . . . . . . . . . . . . .  14
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  15

1.  Introduction

   There is often a need to provide large aggregates of bandwidth that
   are best provided using parallel links between routers or carrying
   traffic over multiple MPLS LSP.  In core networks there is often no
   alternative since the aggregate capacities of core networks today far
   exceed the capacity of a single physical link or single packet
   processing element.

   The presence of parallel links, with each link potentially comprised
   of multiple layers has resulted in additional requirements.  Certain
   services may benefit from being restricted to a subset of the
   component links or a specific component link, where component link
   characteristics, such as latency, differ.  Certain services require
   that an LSP be treated as atomic and avoid reordering.  Other
   services will continue to require only that reordering not occur
   within a microflow as is current practice.
Show full document text