References from RFC 5064
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 78 |
References Referenced by |
informatively references | ||
BCP 90 |
References Referenced by |
normatively references | ||
RFC 1036 |
Standard for interchange of USENET messages
References Referenced by |
Unknown | informatively references | |
RFC 2046 |
Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types
References Referenced by |
Draft Standard | informatively references | |
RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels
References Referenced by |
Best Current Practice | normatively references | |
RFC 2369 |
The Use of URLs as Meta-Syntax for Core Mail List Commands and their Transport through Message Header Fields
References Referenced by |
Proposed Standard | informatively references | |
RFC 2822 |
Internet Message Format
References Referenced by |
Proposed Standard | normatively references | |
RFC 3864 |
Registration Procedures for Message Header Fields
References Referenced by |
Best Current Practice | normatively references | |
RFC 3987 |
Internationalized Resource Identifiers (IRIs)
References Referenced by |
Proposed Standard | normatively references | |
RFC 4234 |
Augmented BNF for Syntax Specifications: ABNF
References Referenced by |
Draft Standard | normatively references | |
RFC 822 |
STANDARD FOR THE FORMAT OF ARPA INTERNET TEXT MESSAGES
References Referenced by |
Internet Standard | Possible Reference | |
STD 66 |
References Referenced by |
normatively references |