References from draft-flanagan-regext-datadictionary
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 219 |
References Referenced by |
normatively references | ||
BCP 26 |
References Referenced by |
normatively references | ||
RFC 1034 |
Domain names - concepts and facilities
References Referenced by |
Internet Standard | normatively references | |
RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels
References Referenced by |
Best Current Practice | normatively references | |
RFC 3629 |
UTF-8, a transformation format of ISO 10646
References Referenced by |
Internet Standard | normatively references | |
RFC 5322 |
Internet Message Format
References Referenced by |
Draft Standard | normatively references | |
RFC 5731 |
Extensible Provisioning Protocol (EPP) Domain Name Mapping
References Referenced by |
Internet Standard | normatively references | |
RFC 8126 |
Guidelines for Writing an IANA Considerations Section in RFCs
References Referenced by |
Best Current Practice | normatively references | |
RFC 8174 |
Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words
References Referenced by |
Best Current Practice | normatively references | |
RFC 8499 |
DNS Terminology
References Referenced by |
Best Current Practice | normatively references | |
STD 13 |
References Referenced by |
normatively references | ||
STD 63 |
References Referenced by |
normatively references | ||
STD 69 |
References Referenced by |
normatively references |