RFC 7734: Support for Shortest Path Bridging MAC Mode over Ethernet VPN (EVPN)
In plain English — editorial summary, not part of the RFC
This document describes how Ethernet Shortest Path Bridging MAC mode (SPBM) can be combined with Ethernet VPN (EVPN) to interwork with Provider Backbone Bridging Provider Edges (PBB PEs) as described in the PBB-EVPN solution (RFC 7623). This is achieved via operational isolation of each Ethernet network attached to an EVPN core while supporting full interworking between the different variations of Ethernet networks.
Document record
- Document ID
- RFC7734
- Published
- January 2016
- Authors
- D. Allan; J. Tantsura; D. Fedyk; A. Sajassi
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 11
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8560Seamless Integration of Ethernet VPN (EVPN) with Virtual Private LAN Service (VPLS) and Their Provider Backbone Bridge (PBB) EquivalentsCurrent
May 2019
- RFC 9062Framework and Requirements for Ethernet VPN (EVPN) Operations, Administration, and Maintenance (OAM)Current
June 2021
- RFC 7733Applicability Statement: The Use of the Routing Protocol for Low-Power and Lossy Networks (RPL) Protocol Suite in Home Automation and Building ControlCurrent
February 2016
- RFC 7732Forwarder Policy for Multicast with Admin-Local Scope in the Multicast Protocol for Low-Power and Lossy Networks (MPL)Current
February 2016
- RFC 7737Label Switched Path (LSP) Ping and Traceroute Reply Mode SimplificationCurrent
January 2016
- RFC 7731Multicast Protocol for Low-Power and Lossy Networks (MPL)Current
February 2016
- RFC 7730Resource Public Key Infrastructure (RPKI) Trust Anchor LocatorObsoleted
January 2016
- RFC 7740Simulating Partial Mesh of Multipoint-to-Multipoint (MP2MP) Provider Tunnels with Ingress ReplicationCurrent
January 2016
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?