References from draft-ietf-bess-evpn-lsp-ping

This is an experimental product. 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.

Reference type help

Document Title Status Type Downref
BCP 14 Key words for use in RFCs to Indicate Requirement Levels
Refs Ref'd by
Best Current Practice informatively references
draft-ietf-bess-evpn-prefix-advertisement IP Prefix Advertisement in EVPN
Refs Ref'd by
Proposed Standard normatively references
RFC 2119 Key words for use in RFCs to Indicate Requirement Levels
Refs Ref'd by
Best Current Practice informatively references
RFC 4875 Extensions to Resource Reservation Protocol - Traffic Engineering (RSVP-TE) for Point-to-Multipoint TE Label Switched Paths (LSPs)
Refs Ref'd by
Proposed Standard informatively references
RFC 5085 Pseudowire Virtual Circuit Connectivity Verification (VCCV): A Control Channel for Pseudowires
Refs Ref'd by
Proposed Standard informatively references
RFC 6338 Definition of a Uniform Resource Name (URN) Namespace for the Schema for Academia (SCHAC)
Refs Ref'd by
Informational informatively references
RFC 6425 Detecting Data-Plane Failures in Point-to-Multipoint MPLS - Extensions to LSP Ping
Refs Ref'd by
Proposed Standard normatively references
RFC 6426 MPLS On-Demand Connectivity Verification and Route Tracing
Refs Ref'd by
Proposed Standard normatively references
RFC 7432 BGP MPLS-Based Ethernet VPN
Refs Ref'd by
Proposed Standard normatively references
RFC 7623 Provider Backbone Bridging Combined with Ethernet VPN (PBB-EVPN)
Refs Ref'd by
Proposed Standard normatively references
RFC 8029 Detecting Multiprotocol Label Switched (MPLS) Data-Plane Failures
Refs Ref'd by
Proposed Standard normatively references