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

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
References Referenced by
Best Current Practice informatively references
draft-ietf-bess-evpn-prefix-advertisement IP Prefix Advertisement in EVPN
References Referenced by
Proposed Standard normatively references
RFC 2119 Key words for use in RFCs to Indicate Requirement Levels
References Referenced 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)
References Referenced by
Proposed Standard informatively references
RFC 5085 Pseudowire Virtual Circuit Connectivity Verification (VCCV): A Control Channel for Pseudowires
References Referenced by
Proposed Standard informatively references
RFC 6338 Definition of a Uniform Resource Name (URN) Namespace for the Schema for Academia (SCHAC)
References Referenced by
Informational informatively references
RFC 6425 Detecting Data-Plane Failures in Point-to-Multipoint MPLS - Extensions to LSP Ping
References Referenced by
Proposed Standard normatively references
RFC 6426 MPLS On-Demand Connectivity Verification and Route Tracing
References Referenced by
Proposed Standard normatively references
RFC 7432 BGP MPLS-Based Ethernet VPN
References Referenced by
Proposed Standard normatively references
RFC 7623 Provider Backbone Bridging Combined with Ethernet VPN (PBB-EVPN)
References Referenced by
Proposed Standard normatively references
RFC 8029 Detecting Multiprotocol Label Switched (MPLS) Data-Plane Failures
References Referenced by
Proposed Standard normatively references