References from RFC 5492
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 | normatively references | |
| RFC 2842 | Capabilities Advertisement with BGP-4 References Referenced by | Proposed Standard | informatively references | |
| RFC 3392 | Capabilities Advertisement with BGP-4 References Referenced by | Draft Standard | informatively references | |
| RFC 4271 | A Border Gateway Protocol 4 (BGP-4) References Referenced by | Draft Standard | normatively references | |
| RFC 4272 | BGP Security Vulnerabilities Analysis References Referenced by | Informational | informatively references | |
| RFC 4760 | Multiprotocol Extensions for BGP-4 References Referenced by | Draft Standard | informatively references | |
| RFC 5226 | Guidelines for Writing an IANA Considerations Section in RFCs References Referenced by | Best Current Practice | normatively references |