MPLS Profiles
draft-rosen-mpls-profiles-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Eric C. Rosen , Bob Thomas , George Swallow , Carol Iturralde , Lance Levine | ||
| Last updated | 2000-03-07 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
The MPLS protocol specifications provide a large number of options, and it can be difficult to know exactly which protocol messages, objects, and procedures must be supported in order to provide some particular application of MPLS, or in order to interoperate with some other implementation. This document specifies a number of MPLS 'Profiles'. Each Profile is a subset of the full MPLS functionality, specified in enough detail to ensure that two implementations of a given Profile will interoperate. This document also specifies which Profiles may be used for which purposes. In the future, it is hoped that specifications for the applications of MPLS will specify the Profiles that must be implemented in order to support the application.
Authors
Eric C. Rosen
Bob Thomas
George Swallow
Carol Iturralde
Lance Levine
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)