Use of Label Switching With RSVP
draft-ietf-mpls-rsvp-00
| Document | Type | Expired Internet-Draft (mpls WG) | |
|---|---|---|---|
| Last updated | 1998-03-12 | ||
| Stream | IETF | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
plain text
pdf
html
bibtex
|
||
| Stream | WG state | WG Document | |
| Document shepherd | No shepherd assigned | ||
| IESG | IESG state | Expired | |
| Consensus Boilerplate | Unknown | ||
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-ietf-mpls-rsvp-00.txt
Abstract
Multiprotocol Label Switching (MPLS) allows labels to be bound to various granularities of forwarding information, including application flows. In this document we present a specification for allocating and binding labels to RSVP flows, and to distributing the appropriate binding information using RSVP messages.
Authors
Bruce Davie
(bsd@cisco.com)
Yakov Rekhter
(yakov@juniper.net)
Arun Viswanathan
(arunv@lucent.com)
Steven Blake
(slblake@torrentnet.com)
Vijay Srinivasan
(vijay@cosinecom.com)
Eric Rosen
(erosen@cisco.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)