References from draft-salam-l2vpn-evpn-oam-req-frmwk
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.
| Document | Title | Status | Type | Downref |
|---|---|---|---|---|
| BCP 14 |
References Referenced by |
normatively references | ||
| draft-ietf-l2vpn-evpn |
BGP MPLS-Based Ethernet VPN
References Referenced by |
Proposed Standard | normatively references | |
| draft-ietf-l2vpn-pbb-evpn |
Provider Backbone Bridging Combined with Ethernet VPN (PBB-EVPN)
References Referenced by |
Proposed Standard | normatively references | |
| draft-ietf-l2vpn-trill-evpn |
TRILL-EVPN
References Referenced by |
Proposed Standard | normatively references | |
| draft-ietf-trill-oam-req |
Requirements for Operations, Administration, and Maintenance (OAM) in Transparent Interconnection of Lots of Links (TRILL)
References Referenced by |
Informational | informatively references | |
| draft-mizrahi-trill-loss-delay |
Loss and Delay Measurement in Transparent Interconnection of Lots of Links (TRILL)
References Referenced by |
informatively references | ||
| RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels
References Referenced by |
Best Current Practice | normatively references | |
| RFC 2544 |
Benchmarking Methodology for Network Interconnect Devices
References Referenced by |
Informational | Possible Reference | |
| RFC 4379 |
Detecting Multi-Protocol Label Switched (MPLS) Data Plane Failures
References Referenced by |
Proposed Standard | Possible Reference | |
| RFC 5085 |
Pseudowire Virtual Circuit Connectivity Verification (VCCV): A Control Channel for Pseudowires
References Referenced by |
Proposed Standard | informatively references | |
| RFC 6136 |
Layer 2 Virtual Private Network (L2VPN) Operations, Administration, and Maintenance (OAM) Requirements and Framework
References Referenced by |
Informational | Possible Reference | |
| RFC 6291 |
Guidelines for the Use of the "OAM" Acronym in the IETF
References Referenced by |
Best Current Practice | normatively references |