idnits 2.17.1 draft-malis-diff-te-serviceclass-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 3496 5 Title: Protocol Extension for Support of Asynchronous 6 Transfer Mode (ATM) Service Class-aware 7 Multiprotocol Label Switching (MPLS) 8 Traffic Engineering 9 Author(s): A. G. Malis, T. Hsiao 10 Status: Informational 11 Date: March 2003 12 Mailbox: Andy.Malis@vivacenetworks.com, 13 Tony.Hsiao@VivaceNetworks.com 14 Pages: 6 15 Characters: 11431 16 Updates/Obsoletes/SeeAlso: None 18 I-D Tag: draft-malis-diff-te-serviceclass-04.txt 20 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3496.txt 22 This document specifies a Resource ReSerVation Protocol-Traffic 23 Engineering (RSVP-TE) signaling extension for support of Asynchronous 24 Transfer Mode (ATM) Service Class-aware Multiprotocol Label Switching 25 (MPLS) Traffic Engineering. 27 This memo provides information for the Internet community. It does 28 not specify an Internet standard of any kind. Distribution of this 29 memo is unlimited. 31 This announcement is sent to the IETF list and the RFC-DIST list. 32 Requests to be added to or deleted from the IETF distribution list 33 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 34 added to or deleted from the RFC-DIST distribution list should 35 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 37 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 38 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 39 help: ways_to_get_rfcs. For example: 41 To: rfc-info@RFC-EDITOR.ORG 42 Subject: getting rfcs 44 help: ways_to_get_rfcs 46 Requests for special distribution should be addressed to either the 47 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 48 specifically noted otherwise on the RFC itself, all RFCs are for 49 unlimited distribution.echo 50 Submissions for Requests for Comments should be sent to 51 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 52 Authors, for further information.