References from RFC 6427
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 | ||
BCP 26 |
References Referenced by |
normatively references | ||
RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels
References Referenced by |
Best Current Practice | Possible Reference | |
RFC 4385 |
Pseudowire Emulation Edge-to-Edge (PWE3) Control Word for Use over an MPLS PSN
References Referenced by |
Proposed Standard | normatively references | |
RFC 5085 |
Pseudowire Virtual Circuit Connectivity Verification (VCCV): A Control Channel for Pseudowires
References Referenced by |
Proposed Standard | informatively references | |
RFC 5226 |
Guidelines for Writing an IANA Considerations Section in RFCs
References Referenced by |
Best Current Practice | Possible Reference | |
RFC 5586 |
MPLS Generic Associated Channel
References Referenced by |
Proposed Standard | normatively references | |
RFC 5654 |
Requirements of an MPLS Transport Profile
References Referenced by |
Proposed Standard | normatively references | |
RFC 5741 |
RFC Streams, Headers, and Boilerplates
References Referenced by |
Informational | Possible Reference | Possible Downref |
RFC 5860 |
Requirements for Operations, Administration, and Maintenance (OAM) in MPLS Transport Networks
References Referenced by |
Proposed Standard | normatively references | |
RFC 5920 |
Security Framework for MPLS and GMPLS Networks
References Referenced by |
Informational | informatively references | |
RFC 6370 |
MPLS Transport Profile (MPLS-TP) Identifiers
References Referenced by |
Proposed Standard | normatively references |