References from RFC 7108
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 126 |
References Referenced by |
normatively references | ||
BCP 16 |
References Referenced by |
normatively references | ||
RFC 1034 |
Domain names - concepts and facilities
References Referenced by |
Internet Standard | normatively references | |
RFC 1035 |
Domain names - implementation and specification
References Referenced by |
Internet Standard | normatively references | |
RFC 2182 |
Selection and Operation of Secondary DNS Servers
References Referenced by |
Best Current Practice | normatively references | |
RFC 4786 |
Operation of Anycast Services
References Referenced by |
Best Current Practice | normatively references | |
RFC 4892 |
Requirements for a Mechanism Identifying a Name Server Instance
References Referenced by |
Informational | normatively references | |
RFC 5001 |
DNS Name Server Identifier (NSID) Option
References Referenced by |
Proposed Standard | normatively references | |
RFC 5741 |
RFC Streams, Headers, and Boilerplates
References Referenced by |
Informational | Possible Reference | |
RFC 6891 |
Extension Mechanisms for DNS (EDNS(0))
References Referenced by |
Internet Standard | normatively references | |
STD 13 |
References Referenced by |
normatively references | ||
STD 75 |
References Referenced by |
normatively references |