idnits 2.17.1 draft-lin-ccamp-gmpls-ason-rsvpte-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 3474 5 Title: Documentation of IANA assignments for 6 Generalized MultiProtocol Label Switching (GMPLS) 7 Resource Reservation Protocol - Traffic 8 Engineering (RSVP-TE) Usage and Extensions for 9 Automatically Switched Optical Network (ASON) 10 Author(s): Z. Lin, D. Pendarakis 11 Status: Informational 12 Date: March 2003 13 Mailbox: zhiwlin@nyct.com, dpendarakis@tellium.com 14 Pages: 25 15 Characters: 52551 16 Updates/Obsoletes/SeeAlso: None 18 I-D Tag: draft-lin-ccamp-gmpls-ason-rsvpte-04.txt 20 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3474.txt 22 The Generalized MultiProtocol Label Switching (GMPLS) suite of 23 protocol specifications has been defined to provide support for 24 different technologies as well as different applications. These 25 include support for requesting TDM connections based on Synchronous 26 Optical NETwork/Synchronous Digital Hierarchy (SONET/SDH) as 27 well as Optical Transport Networks (OTNs). 29 This document concentrates on the signaling aspects of the GMPLS 30 suite of protocols, specifically GMPLS signaling using Resource 31 Reservation Protocol - Traffic Engineering (RSVP-TE). It 32 proposes additional extensions to these signaling protocols to 33 support the capabilities of an ASON network. 35 This document proposes appropriate extensions towards the resolution 36 of additional requirements identified and communicated by the ITU-T 37 Study Group 15 in support of ITU's ASON standardization effort. 39 This memo provides information for the Internet community. It does 40 not specify an Internet standard of any kind. Distribution of this 41 memo is unlimited. 43 This announcement is sent to the IETF list and the RFC-DIST list. 44 Requests to be added to or deleted from the IETF distribution list 45 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 46 added to or deleted from the RFC-DIST distribution list should 47 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 49 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 50 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 51 help: ways_to_get_rfcs. For example: 53 To: rfc-info@RFC-EDITOR.ORG 54 Subject: getting rfcs 56 help: ways_to_get_rfcs 58 Requests for special distribution should be addressed to either the 59 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 60 specifically noted otherwise on the RFC itself, all RFCs are for 61 unlimited distribution.echo 62 Submissions for Requests for Comments should be sent to 63 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 64 Authors, for further information.