Seamless MPLS Architecture
draft-ietf-mpls-seamless-mpls-07
| Document | Type | Expired Internet-Draft (mpls WG) | |
|---|---|---|---|
| Authors | Nicolai Leymann , Bruno Decraene , Clarence Filsfils , Maciek Konstantynowicz , Dirk Steinberg | ||
| Last updated | 2015-10-14 (latest revision 2014-06-28) | ||
| Replaces | draft-leymann-mpls-seamless-mpls | ||
| Stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | Informational | ||
| Formats |
Expired & archived
pdf
htmlized
bibtex
|
||
| Stream | WG state | Submitted to IESG for Publication | |
| Document shepherd | Loa Andersson | ||
| Shepherd write-up | Show (last changed 2014-09-30) | ||
| IESG | IESG state | Expired (IESG: Dead) | |
| Action Holders |
(None)
|
||
| Consensus Boilerplate | Unknown | ||
| Telechat date | |||
| Responsible AD | Deborah Brungard | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-ietf-mpls-seamless-mpls-07.txt
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.
Authors
Nicolai Leymann
(n.leymann@telekom.de)
Bruno Decraene
(bruno.decraene@orange.com)
Clarence Filsfils
(cfilsfil@cisco.com)
Maciek Konstantynowicz
(maciek@cisco.com)
Dirk Steinberg
(dws@steinbergnet.net)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)