idnits 2.17.1 draft-ietf-mpls-loop-prevention-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 3063 5 Title: MPLS Loop Prevention Mechanism 6 Author(s): Y. Ohba, Y. Katsube, E. Rosen, P. Doolan 7 Status: Experimental 8 Date: February 2001 9 Mailbox: yoshihiro.ohba@toshiba.co.jp, 10 yasuhiro.katsube@toshiba.co.jp, erosen@cisco.com, 11 pdoolan@ennovatenetworks.com 12 Pages: 44 13 Characters: 93523 14 Updates/Obsoletes/SeeAlso: None 16 I-D Tag: draft-ietf-mpls-loop-prevention-03.txt 18 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3063.txt 20 This paper presents a simple mechanism, based on "threads", which 21 can be used to prevent Multiprotocol Label Switching (MPLS) from 22 setting up label switched path (LSPs) which have loops. The 23 mechanism is compatible with, but does not require, VC merge. The 24 mechanism can be used with either the ordered downstream-on-demand 25 allocation or ordered downstream allocation. The amount of 26 information that must be passed in a protocol message is tightly 27 bounded (i.e., no path-vector is used). When a node needs to change 28 its next hop, a distributed procedure is executed, but only nodes 29 which are downstream of the change are involved. 31 This document is a product of the Multiprotocol Label Switching 32 Working Group of the IETF. 34 This memo defines an Experimental Protocol for the Internet community. 35 It does not specify an Internet standard of any kind. Discussion and 36 suggestions for improvement are requested. Distribution of this memo 37 is unlimited. 39 This announcement is sent to the IETF list and the RFC-DIST list. 40 Requests to be added to or deleted from the IETF distribution list 41 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 42 added to or deleted from the RFC-DIST distribution list should 43 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 45 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 46 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 47 help: ways_to_get_rfcs. For example: 49 To: rfc-info@RFC-EDITOR.ORG 50 Subject: getting rfcs 52 help: ways_to_get_rfcs 54 Requests for special distribution should be addressed to either the 55 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 56 specifically noted otherwise on the RFC itself, all RFCs are for 57 unlimited distribution.echo 58 Submissions for Requests for Comments should be sent to 59 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 60 Authors, for further information.