idnits 2.17.1 draft-ietf-mpls-multicast-08.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 3353 5 Title: Overview of IP Multicast in a Multi-Protocol Label 7 Switching (MPLS) Environment 8 Author(s): D. Ooms, B. Sales, W. Livens, A. Acharya, 9 F. Griffoul, F. Ansari 10 Status: Informational 11 Date: August 2002 12 Mailbox: Dirk.Ooms@alcatel.be, Bernard.Sales@alcatel.be, 13 WLivens@colt-telecom.be, arup@us.ibm.com, 14 griffoul@ulticom.com, furquan@dnrc.bell-labs.com 15 Pages: 30 16 Characters: 65860 17 Updates/Obsoletes/SeeAlso: None 19 I-D Tag: draft-ietf-mpls-multicast-08.txt 21 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3353.txt 23 This document offers a framework for IP multicast deployment in an 24 MPLS environment. Issues arising when MPLS techniques are applied to 25 IP multicast are overviewed. The pros and cons of existing IP 26 multicast routing protocols in the context of MPLS are described and 27 the relation to the different trigger methods and label distribution 28 modes are discussed. The consequences of various layer 2 (L2) 29 technologies are listed. Both point-to-point and multi-access 30 networks are considered. 32 This document is a product of the Multiprotocol Label Switching 33 Working Group of the IETF. 35 This memo provides information for the Internet community. It does 36 not specify an Internet standard of any kind. Distribution of this 37 memo is unlimited. 39 This announcement is sent to the IETF list and the RFC-DIST list. 40 Requests to be added to or deleted from the IETF distribution list 41 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 42 added to or deleted from the RFC-DIST distribution list should 43 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 45 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 46 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 47 help: ways_to_get_rfcs. For example: 49 To: rfc-info@RFC-EDITOR.ORG 50 Subject: getting rfcs 52 help: ways_to_get_rfcs 54 Requests for special distribution should be addressed to either the 55 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 56 specifically noted otherwise on the RFC itself, all RFCs are for 57 unlimited distribution.echo 58 Submissions for Requests for Comments should be sent to 59 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 60 Authors, for further information.