References from rfc3953
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 |
Rights Contributors Provide to the IETF Trust
References Referenced by |
Best Current Practice | informatively references | |
RFC 1034 |
Domain names - concepts and facilities
References Referenced by |
Internet Standard | informatively references | |
RFC 2396 |
Uniform Resource Identifiers (URI): Generic Syntax
References Referenced by |
Draft Standard | informatively references | |
RFC 2778 |
A Model for Presence and Instant Messaging
References Referenced by |
Informational | normatively references | Downref |
RFC 2779 |
Instant Messaging / Presence Protocol Requirements
References Referenced by |
Informational | normatively references | Downref |
RFC 3261 |
SIP: Session Initiation Protocol
References Referenced by |
Proposed Standard | informatively references | |
RFC 3403 |
Dynamic Delegation Discovery System (DDDS) Part Three: The Domain Name System (DNS) Database
References Referenced by |
Proposed Standard | informatively references | |
RFC 3761 |
The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application (ENUM)
References Referenced by |
Proposed Standard | normatively references | |
RFC 3859 |
Common Profile for Presence (CPP)
References Referenced by |
Proposed Standard | normatively references | |
RFC 3861 |
Address Resolution for Instant Messaging and Presence
References Referenced by |
Proposed Standard | normatively references | |
RFC 3863 |
Presence Information Data Format (PIDF)
References Referenced by |
Proposed Standard | informatively references | |
STD 13 |
Domain names - implementation and specification
References Referenced by |
Internet Standard | informatively references |