Extensions to Resource Reservation Protocol - Traffic Engineering for Point-to-Multipoint TE Label Switched Paths
RFC 4875, “Extensions to Resource Reservation Protocol - Traffic Engineering for Point-to-Multipoint TE Label Switched Paths”, is a Proposed Standard document published in May 2007 by R. Aggarwal, D. Papadimitriou, S. Yasukawa. It has since been updated by RFC 6510. The canonical text is published by the RFC Editor.
Abstract
This document describes extensions to Resource Reservation Protocol - Traffic Engineering (RSVP-TE) for the set up of Traffic Engineered (TE) point-to-multipoint (P2MP) Label Switched Paths (LSPs) in Multi- Protocol Label Switching (MPLS) and Generalized MPLS (GMPLS) networks. The solution relies on RSVP-TE without requiring a multicast routing protocol in the Service Provider core. Protocol elements and procedures for this solution are described.
There can be various applications for P2MP TE LSPs such as IP multicast. Specification of how such applications will use a P2MP TE LSP is outside the scope of this document. [STANDARDS-TRACK]
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
The canonical text of RFC 4875 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 4874 Exclude Routes - Extension to Resource ReserVation Protocol-Traffic Engineering
- RFC 4876 A Configuration Profile Schema for Lightweight Directory Access Protocol -Based Agents
- RFC 4873 GMPLS Segment Recovery
- RFC 4877 Mobile IPv6 Operation with IKEv2 and the Revised IPsec Architecture
- RFC 4872 RSVP-TE Extensions in Support of End-to-End Generalized Multi- Protocol Label Switching Recovery
- RFC 4878 Definitions and Managed Objects for Operations, Administration, and Maintenance Functions on Ethernet-Like Interfaces
- RFC 4871 DomainKeys Identified Mail Signatures
- RFC 4879 Clarification of the Third Party Disclosure Procedure in RFC 3979