Encoding of Big Labels in MPLS Label Stacks
draft-renwei-mpls-big-label-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Renwei (Richard) Li , Ming Li | ||
| Last updated | 2014-01-01 (Latest revision 2013-06-30) | ||
| 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 specifies encoding and encapsulation methods for MPLS big labels. Big labels are required for accessing virtual networks in data centers by using, for example, BGP/MPLS IP VPNs. Data center virtualization encapsulation methods and protocols such as VXLAN, NVGRE and NVO3 are being standardized to support a few millions of virtual networks, but the currently label format can support up to one million of labels. When the BGP/MPLS IP VPN method, for example, is used by an enterprise/customer to access its corresponding virtual networks, more than one million of labels are required to map VPN labels and Virtual Network Identifiers.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)