Seamless MPLS Architecture
draft-ietf-mpls-seamless-mpls-03

The information below is for an old version of the document
Document Type Active Internet-Draft (mpls WG)
Last updated 2013-05-13
Replaces draft-leymann-mpls-seamless-mpls
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)
MPLS Working Group                                       N. Leymann, Ed.
Internet-Draft                                       Deutsche Telekom AG
Intended status: Informational                               B. Decraene
Expires: November 14, 2013                                France Telecom
                                                             C. Filsfils
                                                 M. Konstantynowicz, Ed.
                                                           Cisco Systems
                                                            D. Steinberg
                                                    Steinberg Consulting
                                                            May 13, 2013

                       Seamless MPLS Architecture
                    draft-ietf-mpls-seamless-mpls-03

Abstract

   This documents describes an architecture which can be used to extend
   MPLS networks to integrate access and aggregation networks into a
   single MPLS domain ("Seamless MPLS").  The Seamless MPLS approach is
   based on existing and well known protocols.  It provides a highly
   flexible and a scalable architecture and the possibility to integrate
   100.000 of nodes.  The separation of the service and transport plane
   is one of the key elements; Seamless MPLS provides end to end service
   independent transport.  Therefore it removes the need for service
   specific configurations in network transport nodes (without end to
   end transport MPLS, some additional services nodes/configurations
   would be required to glue each transport domain).  This draft defines
   a routing architecture using existing standardized protocols.  It
   does not invent any new protocols or defines extensions to existing
   protocols.

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 November 14, 2013.

Leymann, et al.        Expires November 14, 2013                [Page 1]
Internet-Draft               Seamless MPLS                      May 2013

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
   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  . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.1.  Requirements Language . . . . . . . . . . . . . . . . . .   4
     1.2.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   4
   2.  Motivation  . . . . . . . . . . . . . . . . . . . . . . . . .   5
     2.1.  Why Seamless MPLS . . . . . . . . . . . . . . . . . . . .   6
     2.2.  Use Case #1 . . . . . . . . . . . . . . . . . . . . . . .   7
       2.2.1.  Description . . . . . . . . . . . . . . . . . . . . .   7
       2.2.2.  Typical Numbers . . . . . . . . . . . . . . . . . . .   9
     2.3.  Use Case #2 . . . . . . . . . . . . . . . . . . . . . . .  10
       2.3.1.  Description . . . . . . . . . . . . . . . . . . . . .  10
       2.3.2.  Typical Numbers . . . . . . . . . . . . . . . . . . .  11
   3.  Requirements  . . . . . . . . . . . . . . . . . . . . . . . .  12
     3.1.  Overall . . . . . . . . . . . . . . . . . . . . . . . . .  12
       3.1.1.  Access  . . . . . . . . . . . . . . . . . . . . . . .  12
       3.1.2.  Aggregation . . . . . . . . . . . . . . . . . . . . .  13
       3.1.3.  Core  . . . . . . . . . . . . . . . . . . . . . . . .  13
     3.2.  Multicast . . . . . . . . . . . . . . . . . . . . . . . .  13
     3.3.  Availability  . . . . . . . . . . . . . . . . . . . . . .  14
     3.4.  Scalability . . . . . . . . . . . . . . . . . . . . . . .  14
     3.5.  Stability . . . . . . . . . . . . . . . . . . . . . . . .  14
Show full document text