idnits 2.17.1 draft-ietf-mpls-ldp-state-04.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 3215 5 Title: LDP State Machine 6 Author(s): C. Boscher, P. Cheval, L. Wu, E. Gray 7 Status: Informational 8 Date: January 2002 9 Mailbox: christophe.boscher@alcatel.fr, 10 pierrick.cheval@space.alcatel.fr, liwwu@cisco.com, 11 eric.gray@sandburst.com 12 Pages: 78 13 Characters: 117278 14 Updates/Obsoletes/SeeAlso: NONE 16 I-D Tag: draft-ietf-mpls-ldp-state-04.txt 18 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3215.txt 20 This document provides state machine tables for ATM (Asynchronous 21 Transfer Mode) switch LSRs. In the current LDP specification, there 22 is no state machine specified for processing LDP messages. We think 23 that defining a common state machine is very important for 24 interoperability between different LDP and CR-LDP implementations. 26 We begin in section 1 by defining a list of terminologies. Then in 27 section 2, we propose two sets of state machine tables for ATM switch 28 LSRs that use downstream-on-demand mode, one method can be used for 29 non-vc merge capable ATM LSRs, while the other one can be used for 30 the vc-merge capable ATM LSRs. In section 3, we provides a state 31 machine for downstream unsolicited mode ATM LSRs. 33 We focus on the LDP state machines and the associated control blocks 34 used for establishing and maintaining LSPs. We do not describe state 35 machines for the "LDP controller" that is in charge of LDP session 36 initialization, address mapping messages management, routing 37 interface, etc. that is defined in the LDP specification. 39 Even though the state machines in this document are specific for 40 ATM-LSR, they can be easily adapted for other types of LSRs. 42 This document is a product of the Multiprotocol Label Switching 43 Working Group of the IETF. 45 This memo provides information for the Internet community. It does 46 not specify an Internet standard of any kind. Distribution of this 47 memo is unlimited. 49 This announcement is sent to the IETF list and the RFC-DIST list. 50 Requests to be added to or deleted from the IETF distribution list 51 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 52 added to or deleted from the RFC-DIST distribution list should 53 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 55 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 56 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 57 help: ways_to_get_rfcs. For example: 59 To: rfc-info@RFC-EDITOR.ORG 60 Subject: getting rfcs 62 help: ways_to_get_rfcs 64 Requests for special distribution should be addressed to either the 65 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 66 specifically noted otherwise on the RFC itself, all RFCs are for 67 unlimited distribution.echo 68 Submissions for Requests for Comments should be sent to 69 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 70 Authors, for further information.