Multiprotocol Label Switching Pre-emption
draft-farrel-mpls-preemption-01
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Author | Adrian Farrel | ||
Last updated | 2004-04-09 | ||
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
Multiprotocol Label Switching (MPLS) signaling is documented in 'RSVP-TE: Extensions to RSVP for LSP Tunnels', RFC 3209, using mechanisms inherited from 'Resource ReserVation Protocol -- Version 1 Functional Specification', RFC 2205. MPLS includes the concept of pre-emption where, for administrative reasons such as contention for system resources, a new Label Switched Path (LSP) may displace an existing LSP. This document clarifies the procedures for MPLS pre-emption in the light of implementation experience. The procedures in this document update those described in RFC 2205 and RFC 3209, but apply only to RSVP-TE used in the MPLS context.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)