Using BGP to Bind MPLS Labels to Address Prefixes
draft-rosen-mpls-rfc3107bis-01
| Document | Type |
Replaced Internet-Draft
(candidate for mpls WG)
Expired & archived
|
|
|---|---|---|---|
| Author | Eric C. Rosen | ||
| Last updated | 2016-05-31 | ||
| Replaces | draft-rosen-idr-rfc3107bis | ||
| Replaced by | draft-ietf-mpls-rfc3107bis | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | Call For Adoption By WG Issued | |
| Document shepherd | Loa Andersson | ||
| IESG | IESG state | Replaced by draft-ietf-mpls-rfc3107bis | |
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | "Loa Andersson" <loa@pi.nu> |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This document specifies a set of procedures for using BGP to advertise that a specified router has bound a specified MPLS label (or a specified sequence of MPLS labels, organized as a contiguous part of a label stack) to a specified address prefix. This can be done by sending a BGP UPDATE message whose Network Layer Reachability Information field contains both the prefix and the MPLS label(s), and whose Next Hop field identifies the node at which said prefix is bound to said label(s). This document obsoletes RFC 3107.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)