References from rfc8416

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 122 Classless Inter-domain Routing (CIDR): The Internet Address Assignment and Aggregation Plan
References Referenced by
Best Current Practice normatively references
BCP 14 Key words for use in RFCs to Indicate Requirement Levels
References Referenced by
Best Current Practice normatively references
BCP 153 Special Use IPv4 Addresses
References Referenced by
Best Current Practice informatively references
BCP 5 Address Allocation for Private Internets
References Referenced by
Best Current Practice informatively references
BCP 6 Guidelines for creation, selection, and registration of an Autonomous System (AS)
References Referenced by
Best Current Practice informatively references
RFC 1918 Address Allocation for Private Internets
References Referenced by
Best Current Practice informatively references
RFC 1930 Guidelines for creation, selection, and registration of an Autonomous System (AS)
References Referenced by
Best Current Practice informatively references
RFC 2119 Key words for use in RFCs to Indicate Requirement Levels
References Referenced by
Best Current Practice normatively references
RFC 4193 Unique Local IPv6 Unicast Addresses
References Referenced by
Proposed Standard informatively references
RFC 4632 Classless Inter-domain Routing (CIDR): The Internet Address Assignment and Aggregation Plan
References Referenced by
Best Current Practice normatively references
RFC 4648 The Base16, Base32, and Base64 Data Encodings
References Referenced by
Proposed Standard normatively references
RFC 5952 A Recommendation for IPv6 Address Text Representation
References Referenced by
Proposed Standard normatively references
RFC 6482 A Profile for Route Origin Authorizations (ROAs)
References Referenced by
Proposed Standard informatively references
RFC 6487 A Profile for X.509 PKIX Resource Certificates
References Referenced by
Proposed Standard normatively references
RFC 6491 Resource Public Key Infrastructure (RPKI) Objects Issued by IANA
References Referenced by
Proposed Standard informatively references
RFC 6598 IANA-Reserved IPv4 Prefix for Shared Address Space
References Referenced by
Best Current Practice informatively references
RFC 6810 The Resource Public Key Infrastructure (RPKI) to Router Protocol
References Referenced by
Proposed Standard informatively references
RFC 6811 BGP Prefix Origin Validation
References Referenced by
Proposed Standard normatively references
RFC 6996 Autonomous System (AS) Reservation for Private Use
References Referenced by
Best Current Practice informatively references
RFC 8174 Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words
References Referenced by
Best Current Practice normatively references
RFC 8205 BGPsec Protocol Specification
References Referenced by
Proposed Standard normatively references
RFC 8208 BGPsec Algorithms, Key Formats, and Signature Formats
References Referenced by
Proposed Standard normatively references
RFC 8209 A Profile for BGPsec Router Certificates, Certificate Revocation Lists, and Certification Requests
References Referenced by
Proposed Standard normatively references
RFC 8210 The Resource Public Key Infrastructure (RPKI) to Router Protocol, Version 1
References Referenced by
Proposed Standard informatively references
RFC 8211 Adverse Actions by a Certification Authority (CA) or Repository Manager in the Resource Public Key Infrastructure (RPKI)
References Referenced by
Informational informatively references
RFC 8259 The JavaScript Object Notation (JSON) Data Interchange Format
References Referenced by
Internet Standard normatively references
STD 90 The JavaScript Object Notation (JSON) Data Interchange Format
References Referenced by
Internet Standard normatively references