idnits 2.17.1 draft-ietf-mpls-diff-ext-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 3270 5 Title: Multi-Protocol Label Switching (MPLS) Support of 6 Differentiated Services 7 Author(s): F. Le Faucheur, L. Wu, B. Davie, S. Davari, 8 P. Vaananen, R. Krishnan, P. Cheval, J. Heinanen 9 Status: Standards Track 10 Date: May 2002 11 Mailbox: flefauch@cisco.com, liwwu@cisco.com, 12 bsd@cisco.com, davari@ieee.org, 13 pasi.vaananen@nokia.com, ram@axiowave.com, 14 pierrick.cheval@space.alcatel.fr, 15 jh@song.fi 16 Pages: 64 17 Characters: 137960 18 Updates/Obsoletes/SeeAlso: None 20 I-D Tag: draft-ietf-mpls-diff-ext-09.txt 22 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3270.txt 24 This document defines a flexible solution for support of 25 Differentiated Services (Diff-Serv) over Multi-Protocol Label 26 Switching (MPLS) networks. 28 This solution allows the MPLS network administrator to select how 29 Diff-Serv Behavior Aggregates (BAs) are mapped onto Label Switched 30 Paths (LSPs) so that he/she can best match the Diff-Serv, Traffic 31 Engineering and protection objectives within his/her particular 32 network. For instance, this solution allows the network 33 administrator to decide whether different sets of BAs are to be 34 mapped onto the same LSP or mapped onto separate LSPs. 36 This document is a product of the Multiprotocol Label Switching 37 Working Group of the IETF. 39 This is now a Proposed Standard Protocol. 41 This document specifies an Internet standards track protocol for 42 the Internet community, and requests discussion and suggestions 43 for improvements. Please refer to the current edition of the 44 "Internet Official Protocol Standards" (STD 1) for the 45 standardization state and status of this protocol. Distribution 46 of this memo is unlimited. 48 This announcement is sent to the IETF list and the RFC-DIST list. 49 Requests to be added to or deleted from the IETF distribution list 50 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 51 added to or deleted from the RFC-DIST distribution list should 52 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 54 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 55 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 56 help: ways_to_get_rfcs. For example: 58 To: rfc-info@RFC-EDITOR.ORG 59 Subject: getting rfcs 61 help: ways_to_get_rfcs 63 Requests for special distribution should be addressed to either the 64 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 65 specifically noted otherwise on the RFC itself, all RFCs are for 66 unlimited distribution.echo 67 Submissions for Requests for Comments should be sent to 68 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 69 Authors, for further information.