References from RFC 5070
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 78 |
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 2396 |
Uniform Resource Identifiers (URI): Generic Syntax
References Referenced by |
Draft Standard | Possible Reference | |
| RFC 2822 |
Internet Message Format
References Referenced by |
Proposed Standard | normatively references | |
| RFC 3339 |
Date and Time on the Internet: Timestamps
References Referenced by |
Proposed Standard | normatively references | |
| RFC 3688 |
The IETF XML Registry
References Referenced by |
Best Current Practice | normatively references | |
| RFC 3986 |
Uniform Resource Identifier (URI): Generic Syntax
References Referenced by |
Internet Standard | normatively references | |
| RFC 4180 |
Common Format and MIME Type for Comma-Separated Values (CSV) Files
References Referenced by |
Informational | informatively references | |
| RFC 4519 |
Lightweight Directory Access Protocol (LDAP): Schema for User Applications
References Referenced by |
Proposed Standard | normatively references | |
| RFC 4646 |
Tags for Identifying Languages
References Referenced by |
Best Current Practice | normatively references | |
| RFC 4765 |
The Intrusion Detection Message Exchange Format (IDMEF)
References Referenced by |
Experimental | informatively references | |
| RFC 822 |
STANDARD FOR THE FORMAT OF ARPA INTERNET TEXT MESSAGES
References Referenced by |
Internet Standard | Possible Reference | |
| STD 1 |
References Referenced by |
Possible Reference |