RFC - 3209

RSVP-TE: Extensions to RSVP for LSP Tunnels

Original:	ftp://ftp.isi.edu/in-notes/rfc3209.txt
Authors:	D. Awduche [Movaz Networks, Inc.], L. Berger [Juniper Networks, Inc.], D. Gan [Juniper Networks, Inc.], T. Li [Procket Networks, Inc.], V. Srinivasan [Cosine Communications, Inc.], G. Swallow [Cisco Systems, Inc.]
Date:	December 2001
Category:	Proposed Standard

---

Updated by:
RFC-4874prop	Exclude Routes - Extension to Resource ReserVation Protocol-Traffic Engineering (RSVP-TE)
RFC-4420prop	Encoding of Attributes for Multiprotocol Label Switching (MPLS) Label Switched Path (LSP) Establishment Using Resource ReserVation Protocol-Traffic Engineering (RSVP-TE)
RFC-3936 [BCP 96]	Procedures for Modifying the Resource reSerVation Protocol (RSVP)

Referred by:	66 RFC
Refers to:	16 RFC

---

Status

This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited.

Copyright Notice

Copyright (C) The Internet Society (2001). All Rights Reserved.

Abstract

This document describes the use of RSVP (Resource Reservation Protocol), including all the necessary extensions, to establish label-switched paths (LSPs) in MPLS (Multi-Protocol Label Switching). Since the flow along an LSP is completely identified by the label applied at the ingress node of the path, these paths may be treated as tunnels. A key application of LSP tunnels is traffic engineering with MPLS as specified in RFC 2702.

We propose several additional objects that extend RSVP, allowing the establishment of explicitly routed label switched paths using RSVP as a signaling protocol. The result is the instantiation of label- switched tunnels which can be automatically routed away from network failures, congestion, and bottlenecks.

---