idnits 2.17.00 (12 Aug 2021) /tmp/idnits64128/draft-ietf-mpls-crlsp-modify-03.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 3214 5 Title: LSP Modification Using CR-LDP 6 Author(s): J. Ash, Y. Lee, P. Ashwood-Smith, B. Jamoussi, 7 D. Fedyk, D. Skalecki, L. Li 8 Status: Standards Track 9 Date: January 2002 10 Mailbox: gash@att.com, jamoussi@NortelNetworks.com, 11 petera@NortelNetworks.com, 12 dareks@nortelnetworks.com, 13 ylee@ceterusnetworks.com, 14 lili@ss8networks.com, dwfedyk@nortelnetworks.com 15 Pages: 11 16 Characters: 25453 17 Updates/Obsoletes/SeeAlso: NONE 19 I-D Tag: draft-ietf-mpls-crlsp-modify-03.txt 21 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3214.txt 23 This document presents an approach to modify the bandwidth and 24 possibly other parameters of an established CR-LSP (Constraint-based 25 Routed Label Switched Paths) using CR-LDP (Constraint-based Routed 26 Label Distribution Protocol) without service interruption. After a 27 CR-LSP is set up, its bandwidth reservation may need to be changed by 28 the network operator, due to the new requirements for the traffic 29 carried on that CR-LSP. The LSP modification feature can be supported 30 by CR-LDP by use of the _modify_value for the _action indicator flag_ 31 in the LSPID TLV. This feature has application in dynamic network 32 resources management where traffic of different priorities and service 33 classes is involved. 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.