References from rfc3863
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 13 |
Multipurpose Internet Mail Extensions (MIME) Part Four: Registration Procedures References Referenced by |
Best Current Practice | normatively references | |
BCP 14 |
Key words for use in RFCs to Indicate Requirement Levels References Referenced by |
Best Current Practice | Possible Reference | |
BCP 18 |
IETF Policy on Character Sets and Languages References Referenced by |
Best Current Practice | normatively references | |
BCP 47 |
Tags for Identifying Languages References Referenced by |
Best Current Practice | normatively references | |
BCP 78 |
Rights Contributors Provide to the IETF Trust References Referenced by |
Best Current Practice | informatively references | |
RFC 2045 |
Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies References Referenced by |
Draft Standard | normatively references | |
RFC 2046 |
Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types References Referenced by |
Draft Standard | normatively references | |
RFC 2047 |
MIME (Multipurpose Internet Mail Extensions) Part Three: Message Header Extensions for Non-ASCII Text References Referenced by |
Draft Standard | normatively references | |
RFC 2049 |
Multipurpose Internet Mail Extensions (MIME) Part Five: Conformance Criteria and Examples References Referenced by |
Draft Standard | normatively references | |
RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels References Referenced by |
Best Current Practice | normatively references | |
RFC 2141 |
URN Syntax References Referenced by |
Proposed Standard | normatively references | |
RFC 2277 |
IETF Policy on Character Sets and Languages References Referenced by |
Best Current Practice | normatively references | |
RFC 2396 |
Uniform Resource Identifiers (URI): Generic Syntax References Referenced by |
Draft Standard | normatively references | |
RFC 2426 |
vCard MIME Directory Profile References Referenced by |
Proposed Standard | informatively references | |
RFC 2648 |
A URN Namespace for IETF Documents References Referenced by |
Informational | normatively references | Downref |
RFC 2778 |
A Model for Presence and Instant Messaging References Referenced by |
Informational | informatively references | |
RFC 2779 |
Instant Messaging / Presence Protocol Requirements References Referenced by |
Informational | informatively references | |
RFC 3023 |
XML Media Types References Referenced by |
Proposed Standard | normatively references | |
RFC 3066 |
Tags for the Identification of Languages References Referenced by |
Best Current Practice | normatively references | |
RFC 3282 |
Content Language Headers References Referenced by |
Draft Standard | informatively 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 3851 |
Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 3.1 Message Specification References Referenced by |
Proposed Standard | informatively references | |
RFC 3859 |
Common Profile for Presence (CPP) References Referenced by |
Proposed Standard | informatively references | |
RFC 3860 |
Common Profile for Instant Messaging (CPIM) References Referenced by |
Proposed Standard | informatively references | |
STD 1 |
Internet Official Protocol Standards References Referenced by |
Historic | Possible Reference | Possible Downref |