RFC 3353: Overview of IP Multicast in a Multi-Protocol Label Switching (MPLS) Environment
In plain English — editorial summary, not part of the RFC
This document offers a framework for IP multicast deployment in an MPLS environment. Issues arising when MPLS techniques are applied to IP multicast are overviewed. The pros and cons of existing IP multicast routing protocols in the context of MPLS are described and the relation to the different trigger methods and label distribution modes are discussed. The consequences of various layer 2 (L2) technologies are listed. Both point-to-point and multi-access networks are considered.
Document record
- Document ID
- RFC3353
- Published
- August 2002
- Authors
- D. Ooms; B. Sales; W. Livens; A. Acharya; F. Griffoul; F. Ansari
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rtg
- Pages
- 30
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5501Requirements for Multicast Support in Virtual Private LAN ServicesCurrent
March 2009
- RFC 3355Layer Two Tunnelling Protocol (L2TP) Over ATM Adaptation Layer 5 (AAL5)Current
September 2002
- RFC 3358Optional Checksums in Intermediate System to Intermediate System (ISIS)Current
August 2002
- RFC 3359Reserved Type, Length and Value (TLV) Codepoints in Intermediate System to Intermediate SystemCurrent
August 2002
- RFC 3345Border Gateway Protocol (BGP) Persistent Route Oscillation ConditionCurrent
August 2002
- RFC 3371Layer Two Tunneling Protocol "L2TP" Management Information BaseCurrent
September 2002
- RFC 3373Three-Way Handshake for Intermediate System to Intermediate System (IS-IS) Point-to-Point AdjacenciesObsoleted
September 2002
- RFC 3376Internet Group Management Protocol, Version 3Obsoleted
October 2002
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?