References from draft-takahashi-mile-sci
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 72 |
References Referenced by |
informatively references | ||
RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels
References Referenced by |
Best Current Practice | normatively references | |
RFC 3339 |
Date and Time on the Internet: Timestamps
References Referenced by |
Proposed Standard | informatively references | |
RFC 3552 |
Guidelines for Writing RFC Text on Security Considerations
References Referenced by |
Best Current Practice | informatively references | |
RFC 3688 |
The IETF XML Registry
References Referenced by |
Best Current Practice | informatively references | |
RFC 3986 |
Uniform Resource Identifier (URI): Generic Syntax
References Referenced by |
Internet Standard | informatively references | |
RFC 5070 |
The Incident Object Description Exchange Format
References Referenced by |
Proposed Standard | normatively references | |
RFC 5322 |
Internet Message Format
References Referenced by |
Draft Standard | informatively references | |
RFC 6045 |
Real-time Inter-network Defense (RID)
References Referenced by |
Informational | normatively references | |
RFC 6046 |
Transport of Real-time Inter-network Defense (RID) Messages
References Referenced by |
Informational | normatively references | |
RFC 6116 |
The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application (ENUM)
References Referenced by |
Proposed Standard | informatively references | |
STD 66 |
References Referenced by |
informatively references |