MPLS Big Label Usecases and Requirements
draft-mpls-big-label-ucase-req-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Richard Li , Katherine Zhao | ||
| Last updated | 2014-04-23 (Latest revision 2013-10-20) | ||
| 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
This document describes usecases and requirements for MPLS big label. The MPLS label format and encoding method have been specified in [RFC 3032], the label value is represented by 20-bit space and support up to 1 million of instances. This proven technology has been widely deployed and worked fine for years. However in certain network deployment scenarios of recent years, the 20-bit MPLS label space is no longer sufficient to support the widespread adoption of network virtualization technologies. In what follows we will describe each of the usecase respectively
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)