idnits 2.17.1 draft-ietf-mpls-generalized-signaling-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 3471 5 Title: Generalized Multi-Protocol Label Switching (GMPLS) 6 Signaling Functional Description 7 Author(s): L. Berger, Editor 8 Status: Standards Track 9 Date: January 2003 10 Mailbox: lberger@movaz.com 11 Pages: 34 12 Characters: 72746 13 Updates/Obsoletes/SeeAlso: None 15 I-D Tag: draft-ietf-mpls-generalized-signaling-09.txt 17 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3471.txt 19 This document describes extensions to Multi-Protocol Label Switching 20 (MPLS) signaling required to support Generalized MPLS. Generalized 21 MPLS extends the MPLS control plane to encompass time-division (e.g., 22 Synchronous Optical Network and Synchronous Digital Hierarchy, 23 SONET/SDH), wavelength (optical lambdas) and spatial switching (e.g., 24 incoming port or fiber to outgoing port or fiber). This document 25 presents a functional description of the extensions. Protocol 26 specific formats and mechanisms, and technology specific details are 27 specified in separate documents. 29 This document is a product of the Common Control Measurement Plane 30 (ccamp) Working Group of the IETF. 32 This is a Proposed Standard Protocol. 34 This document specifies an Internet standards track protocol for 35 the Internet community, and requests discussion and suggestions 36 for improvements. Please refer to the current edition of the 37 "Internet Official Protocol Standards" (STD 1) for the 38 standardization state and status of this protocol. Distribution 39 of this memo is unlimited. 41 This announcement is sent to the IETF list and the RFC-DIST list. 42 Requests to be added to or deleted from the IETF distribution list 43 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 44 added to or deleted from the RFC-DIST distribution list should 45 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 47 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 48 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 49 help: ways_to_get_rfcs. For example: 51 To: rfc-info@RFC-EDITOR.ORG 52 Subject: getting rfcs 54 help: ways_to_get_rfcs 56 Requests for special distribution should be addressed to either the 57 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 58 specifically noted otherwise on the RFC itself, all RFCs are for 59 unlimited distribution.echo 60 Submissions for Requests for Comments should be sent to 61 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 62 Authors, for further information.