Carrying Big Labels in BGP-4
draft-renwei-mpls-bgp-big-label-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Richard Li , Lin Han | ||
| 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
When BGP is used to distribute a particular route, it can also be used to distribute an MPLS label which is mapped to that route. In some cases, for example, when L3VPN is used to access and connect to virtual networks in data centers, there may be 16 millions of VPN instances on a router. In order to map MPLS labels to VPN instances, big labels are required. This document specifies the method to carry and distribute such big labels by piggybacking the big label mapping information for an IP route in the BGP Update message that is used to distribute the route itself.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)