MPLS Deployments and Use Cases That Cannot be Solved By Using 20-bit Label
draft-lzl-mpls-ucase-n-20bit-label-limitation-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Katherine Zhao , Richard Li , Zhenbin Li | ||
| Last updated | 2014-12-27 (Latest revision 2014-06-25) | ||
| 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 label format and encoding method are specified in [RFC3032], the label value is represented using the 20-bit space and supports up to 1 million of instances. As exponential Internet growth continues there are specific network deployment scenarios where a clear need to represent more than one million entities is required. This document describes the MPLS deployment scenarios, use cases, and requirements, where the current 20-bit label will no longer be sufficient.
Authors
Katherine Zhao
Richard Li
Zhenbin Li
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)