Skip to main content

References to draft-ietf-l2vpn-vpls-bgp

These dependencies are extracted using heuristics looking for strings with particular prefixes. Notably, this means that references to I-Ds by title only are not reflected here. If it's really important, please inspect the documents' references sections directly.

Showing RFCs and active Internet-Drafts, sorted by reference type, then document name.

Document Title Status Type Downref
draft-ietf-bess-bgp-sdwan-usage
As rfc4761
BGP Usage for SD-WAN Overlay Networks
References Referenced by
Informational normatively references
draft-ietf-bess-rfc7432bis
As rfc4761
BGP MPLS-Based Ethernet VPN
References Referenced by
normatively references
draft-ietf-bess-v4-v6-pe-all-safi
As rfc4761
IPv4-Only and IPv6-Only PE Design DESIGN ALL SAFI
References Referenced by
normatively references
draft-ietf-idr-flowspec-l2vpn
As rfc4761
BGP Dissemination of L2 Flow Specification Rules
References Referenced by
normatively references
RFC 5462
As rfc4761
Multiprotocol Label Switching (MPLS) Label Stack Entry: "EXP" Field Renamed to "Traffic Class" Field
References Referenced by
Proposed Standard normatively references
RFC 6136
As rfc4761
Layer 2 Virtual Private Network (L2VPN) Operations, Administration, and Maintenance (OAM) Requirements and Framework
References Referenced by
Informational normatively references
RFC 6624
As rfc4761
Layer 2 Virtual Private Networks Using BGP for Auto-Discovery and Signaling
References Referenced by
Informational normatively references
RFC 7041
As rfc4761
Extensions to the Virtual Private LAN Service (VPLS) Provider Edge (PE) Model for Provider Backbone Bridging
References Referenced by
Informational normatively references
RFC 7117
As rfc4761
Multicast in Virtual Private LAN Service (VPLS)
References Referenced by
Proposed Standard normatively references
RFC 7152
As rfc4761
Requirements for Metro Ethernet Forum (MEF) Ethernet-Tree (E-Tree) Support in Layer 2 Virtual Private Network (L2VPN)
References Referenced by
Informational normatively references
RFC 7209
As rfc4761
Requirements for Ethernet VPN (EVPN)
References Referenced by
Informational normatively references
RFC 7257
As rfc4761
Virtual Private LAN Service (VPLS) Management Information Base
References Referenced by
Proposed Standard normatively references
RFC 7387
As rfc4761
A Framework for Ethernet Tree (E-Tree) Service over a Multiprotocol Label Switching (MPLS) Network
References Referenced by
Informational normatively references
RFC 7432
As rfc4761
BGP MPLS-Based Ethernet VPN
References Referenced by
Proposed Standard normatively references
RFC 7524
As rfc4761
Inter-Area Point-to-Multipoint (P2MP) Segmented Label Switched Paths (LSPs)
References Referenced by
Proposed Standard normatively references
RFC 7734
As rfc4761
Support for Shortest Path Bridging MAC Mode over Ethernet VPN (EVPN)
References Referenced by
Proposed Standard normatively references
RFC 7796
As rfc4761
Ethernet-Tree (E-Tree) Support in Virtual Private LAN Service (VPLS)
References Referenced by
Proposed Standard normatively references
RFC 7855
As rfc4761
Source Packet Routing in Networking (SPRING) Problem Statement and Requirements
References Referenced by
Informational normatively references
RFC 8385
As rfc4761
Transparent Interconnection of Lots of Links (TRILL) Transparent Transport over MPLS
References Referenced by
Informational normatively references
RFC 8395
As rfc4761
Extensions to BGP-Signaled Pseudowires to Support Flow-Aware Transport Labels
References Referenced by
Proposed Standard normatively references
RFC 8466
As rfc4761
A YANG Data Model for Layer 2 Virtual Private Network (L2VPN) Service Delivery
References Referenced by
Proposed Standard normatively references
RFC 8560
As rfc4761
Seamless Integration of Ethernet VPN (EVPN) with Virtual Private LAN Service (VPLS) and Their Provider Backbone Bridge (PBB) Equivalents
References Referenced by
Proposed Standard normatively references
RFC 8614
As rfc4761
Updated Processing of Control Flags for BGP Virtual Private LAN Service (VPLS)
References Referenced by
Proposed Standard normatively references
RFC 8944
As rfc4761
A YANG Data Model for Layer 2 Network Topologies
References Referenced by
Proposed Standard normatively references
RFC 9014
As rfc4761
Interconnect Solution for Ethernet VPN (EVPN) Overlay Networks
References Referenced by
Proposed Standard normatively references
RFC 9291
As rfc4761
A YANG Network Data Model for Layer 2 VPNs
References Referenced by
Proposed Standard normatively references
draft-ietf-mpls-1stnibble
As rfc4761
IANA Registry for the First Nibble Following a Label Stack
References Referenced by
Proposed Standard informatively references
draft-ietf-netmod-sub-intf-vlan-model
As rfc4761
Sub-interface VLAN YANG Data Models
References Referenced by
informatively references
draft-kompella-mpls-nffrr
As rfc4761
No Further Fast Reroute
References Referenced by
informatively references
RFC 5283
As rfc4761
LDP Extension for Inter-Area Label Switched Paths (LSPs)
References Referenced by
Proposed Standard informatively references
RFC 5501
As rfc4761
Requirements for Multicast Support in Virtual Private LAN Services
References Referenced by
Informational informatively references
RFC 6074
As rfc4761
Provisioning, Auto-Discovery, and Signaling in Layer 2 Virtual Private Networks (L2VPNs)
References Referenced by
Proposed Standard informatively references
RFC 6511
As rfc4761
Non-Penultimate Hop Popping Behavior and Out-of-Band Mapping for RSVP-TE Label Switched Paths
References Referenced by
Proposed Standard informatively references
RFC 7439
As rfc4761
Gap Analysis for Operating IPv6-Only MPLS Networks
References Referenced by
Informational informatively references
RFC 7623
As rfc4761
Provider Backbone Bridging Combined with Ethernet VPN (PBB-EVPN)
References Referenced by
Proposed Standard informatively references
RFC 7814
As rfc4761
Virtual Subnet: A BGP/MPLS IP VPN-Based Subnet Extension Solution
References Referenced by
Informational informatively references
RFC 8029
As rfc4761
Detecting Multiprotocol Label Switched (MPLS) Data-Plane Failures
References Referenced by
Proposed Standard informatively references
RFC 8220
As rfc4761
Protocol Independent Multicast (PIM) over Virtual Private LAN Service (VPLS)
References Referenced by
Informational informatively references
RFC 8388
As rfc4761
Usage and Applicability of BGP MPLS-Based Ethernet VPN
References Referenced by
Informational informatively references
RFC 8969
As rfc4761
A Framework for Automating Service and Network Management with YANG
References Referenced by
Informational informatively references
RFC 8986
As rfc4761
Segment Routing over IPv6 (SRv6) Network Programming
References Referenced by
Proposed Standard informatively references
RFC 9181
As rfc4761
A Common YANG Data Model for Layer 2 and Layer 3 VPNs
References Referenced by
Proposed Standard informatively references
RFC 9408
As rfc4761
A YANG Network Data Model for Service Attachment Points (SAPs)
References Referenced by
Proposed Standard informatively references
RFC 9494
As rfc4761
Long-Lived Graceful Restart for BGP
References Referenced by
Proposed Standard informatively references
RFC 4762
As rfc4761
Virtual Private LAN Service (VPLS) Using Label Distribution Protocol (LDP) Signaling
References Referenced by
Proposed Standard Possible Reference