RFC 7361: LDP Extensions for Optimized MAC Address Withdrawal in a Hierarchical Virtual Private LAN Service (H-VPLS)
In plain English — editorial summary, not part of the RFC
RFC 4762 describes a mechanism to remove or unlearn Media Access Control (MAC) addresses that have been dynamically learned in a Virtual Private LAN Service (VPLS) instance for faster convergence on topology changes. The procedure also removes MAC addresses in the VPLS that do not require relearning due to such topology changes. This document defines an enhancement to the MAC address withdraw procedure with an empty MAC list (RFC 4762); this enhancement enables a Provider Edge (PE) device to remove only the MAC addresses that need to be relearned. Additional extensions to RFC 4762 MAC withdraw procedures are specified to provide an optimized MAC flushing for the Provider Backbone Bridging (PBB) VPLS specified in RFC 7041.
Document record
- Document ID
- RFC7361
- Published
- September 2014
- Authors
- P. Dutta; F. Balus; O. Stokes; G. Calvignac; D. Fedyk
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 27
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7358Label Advertisement Discipline for LDP Forwarding Equivalence Classes (FECs)Current
October 2014
- RFC 7364Problem Statement: Overlays for Network VirtualizationCurrent
October 2014
- RFC 7357Transparent Interconnection of Lots of Links (TRILL): End Station Address Distribution Information (ESADI) ProtocolCurrent
September 2014
- RFC 7365Framework for Data Center (DC) Network VirtualizationCurrent
October 2014
- RFC 7356IS-IS Flooding Scope Link State PDUs (LSPs)Current
September 2014
- RFC 7367Definition of Managed Objects for the Mobile Ad Hoc Network (MANET) Simplified Multicast Framework Relay Set ProcessCurrent
October 2014
- RFC 7353Security Requirements for BGP Path ValidationCurrent
August 2014
- RFC 7369GMPLS RSVP-TE Extensions for Ethernet Operations, Administration, and Maintenance (OAM) ConfigurationCurrent
October 2014
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?