RFC 7899: Multicast VPN State Damping
In plain English — editorial summary, not part of the RFC
This document describes procedures to damp Multicast VPN (MVPN) routing state changes and control the effect of the churn due to the multicast dynamicity in customer sites. The procedures described in this document are applicable to BGP-based multicast VPN and help avoid uncontrolled control-plane load increase in the core routing infrastructure. The new procedures proposed were inspired by BGP unicast route damping principles that have been adapted to multicast.
Document record
- Document ID
- RFC7899
- Published
- June 2016
- Authors
- T. Morin; S. Litkowski; K. Patel; Z. Zhang; R. Kebler; J. Haas
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 18
- Also known as
- —
- Updates:
- RFC 6514
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6517Mandatory Features in a Layer 3 Multicast BGP/MPLS VPN SolutionCurrent
February 2012
- RFC 7887Hierarchical Join/Prune AttributesCurrent
June 2016
- RFC 7611BGP ACCEPT_OWN Community AttributeCurrent
August 2015
- RFC 5501Requirements for Multicast Support in Virtual Private LAN ServicesCurrent
March 2009
- RFC 8114Delivery of IPv4 Multicast Services to IPv4 Clients over an IPv6 Multicast NetworkCurrent
March 2017
- RFC 8313Use of Multicast across Inter-domain Peering PointsCurrent
January 2018
- RFC 7411Multicast Listener Extensions for Mobile IPv6 (MIPv6) and Proxy Mobile IPv6 (PMIPv6) Fast HandoversCurrent
November 2014
- RFC 8487Mtrace Version 2: Traceroute Facility for IP MulticastCurrent
October 2018
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?