References from rfc4979
This is an experimental product. 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 |
Key words for use in RFCs to Indicate Requirement Levels Refs Ref'd by |
Best Current Practice | normatively references | |
| BCP 78 |
Rights Contributors Provide to the IETF Trust Refs Ref'd by |
Best Current Practice | informatively references | |
| RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels Refs Ref'd by |
Best Current Practice | Possible Reference | |
| RFC 3761 |
The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application (ENUM) Refs Ref'd by |
Proposed Standard | normatively references | |
| RFC 3920 |
Extensible Messaging and Presence Protocol (XMPP): Core Refs Ref'd by |
Proposed Standard | informatively references | |
| RFC 3987 |
Internationalized Resource Identifiers (IRIs) Refs Ref'd by |
Proposed Standard | normatively references | |
| RFC 4622 |
Internationalized Resource Identifiers (IRIs) and Uniform Resource Identifiers (URIs) for the Extensible Messaging and Presence Protocol (XMPP) Refs Ref'd by |
Proposed Standard | normatively references | |
| STD 13 |
Domain names - implementation and specification Refs Ref'd by |
Internet Standard | informatively references | |
| STD 66 |
Uniform Resource Identifier (URI): Generic Syntax Refs Ref'd by |
Internet Standard | normatively references |