idnits 2.17.1 draft-ietf-mpls-atm-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 3035 5 Title: MPLS using LDP and ATM VC Switching 6 Author(s): B. Davie, J. Lawrence, K. McCloghrie, Y. Rekhter, 7 E. Rosen, G. Swallow, P. Doolan 8 Status: Standards Track 9 Date: January 2001 10 Mailbox: bsd@cisco.com, pdoolan@ennovatenetworks.com, 11 jlawrenc@cisco.com, kzm@cisco.com, 12 yakov@juniper.net, erosen@cisco.com, 13 swallow@cisco.com 14 Pages: 20 15 Characters: 46463 16 Updates/Obsoletes/SeeAlso: None 18 I-D Tag: draft-ietf-mpls-atm-04.txt 20 URL: ftp://ftp.isi.edu/in-notes/rfc3035.txt 22 The Multiprotocol Label Switching (MPLS) Architecture discusses a 23 way in which Asynchronous Transfer Mode (ATM) switches may be used as 24 Label Switching Routers. The ATM switches run network layer routing 25 algorithms (such as Open Shortest Path First (OSPF), Intermediate 26 System to Intermediate System (IS-IS), etc.), and their data 27 forwarding is based on the results of these routing algorithms. No 28 ATM-specific routing or addressing is needed. ATM switches used in 29 this way are known as ATM-LSRs (Label Switching Routers). 31 This document extends and clarifies the relevant portions of and 32 by specifying in more detail the procedures which to be used when 33 distributing labels to or from ATM-LSRs, when those labels represent 34 Forwarding Equivalence Classes (FECs) for which the routes are 35 determined on a hop-by-hop basis by network layer routing algorithms. 37 This document also specifies the MPLS encapsulation to be used when 38 sending labeled packets to or from ATM-LSRs. 40 This document is a product of the Multiprotocol Label Switching 41 Working Group of the IETF. 43 This is now a Proposed Standard Protocol. 45 This document specifies an Internet standards track protocol for 46 the Internet community, and requests discussion and suggestions 47 for improvements. Please refer to the current edition of the 48 "Internet Official Protocol Standards" (STD 1) for the 49 standardization state and status of this protocol. Distribution 50 of this memo is unlimited. 52 This announcement is sent to the IETF list and the RFC-DIST list. 53 Requests to be added to or deleted from the IETF distribution list 54 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 55 added to or deleted from the RFC-DIST distribution list should 56 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 58 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 59 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 60 help: ways_to_get_rfcs. For example: 62 To: rfc-info@RFC-EDITOR.ORG 63 Subject: getting rfcs 65 help: ways_to_get_rfcs 67 Requests for special distribution should be addressed to either the 68 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 69 specifically noted otherwise on the RFC itself, all RFCs are for 70 unlimited distribution.echo 71 Submissions for Requests for Comments should be sent to 72 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 73 Authors, for further information.