idnits 2.17.1 draft-ietf-mpls-rsvp-lsp-tunnel-09.txt: Skipping this file; it looks like a tombstone file to me. -------------------------------------------------------------------------------- 1 A new Request for Comments is now available in online RFC libraries. 3 RFC 3209 5 Title: RSVP-TE: Extensions to RSVP for LSP Tunnels 6 Author(s): D. Awduche, L. Berger, D. Gan, T. Li, 7 V. Srinivasan, G. Swallow 8 Status: Standards Track 9 Date: December 2001 10 Mailbox: awduche@movaz.com, lberger@movaz.com, 11 dhg@juniper.net, tli@procket.com, 12 vsriniva@cosinecom.com, swallow@cisco.com 13 Pages: 61 14 Characters: 132264 15 Updates/Obsoletes/SeeAlso: None 17 I-D Tag: draft-ietf-mpls-rsvp-lsp-tunnel-09.txt 19 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3209.txt 21 This document describes the use of RSVP (Resource Reservation 22 Protocol), including all the necessary extensions, to establish 23 label-switched paths (LSPs) in MPLS (Multi-Protocol Label Switching). 24 Since the flow along an LSP is completely identified by the label 25 applied at the ingress node of the path, these paths may be treated as 26 tunnels. A key application of LSP tunnels is traffic engineering with 27 MPLS as specified in RFC 2702. 29 We propose several additional objects that extend RSVP, allowing the 30 establishment of explicitly routed label switched paths using RSVP as 31 a signaling protocol. The result is the instantiation of 32 label-switched tunnels which can be automatically routed away from 33 network failures, congestion, and bottlenecks. 35 This document is a product of the Multiprotocol Label Switching 36 Working Group of the IETF. 38 This is now a Proposed Standard Protocol. 40 This document specifies an Internet standards track protocol for 41 the Internet community, and requests discussion and suggestions 42 for improvements. Please refer to the current edition of the 43 "Internet Official Protocol Standards" (STD 1) for the 44 standardization state and status of this protocol. Distribution 45 of this memo is unlimited. 47 This announcement is sent to the IETF list and the RFC-DIST list. 48 Requests to be added to or deleted from the IETF distribution list 49 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 50 added to or deleted from the RFC-DIST distribution list should 51 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 53 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 54 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 55 help: ways_to_get_rfcs. For example: 57 To: rfc-info@RFC-EDITOR.ORG 58 Subject: getting rfcs 60 help: ways_to_get_rfcs 62 Requests for special distribution should be addressed to either the 63 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 64 specifically noted otherwise on the RFC itself, all RFCs are for 65 unlimited distribution.echo 66 Submissions for Requests for Comments should be sent to 67 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 68 Authors, for further information.