References to RFC 3405
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.
Showing RFCs and active Internet-Drafts, sorted by reference type, then document name.
| Document | Title | Status | Type | Downref |
|---|---|---|---|---|
| draft-drake-agent-identity-resolution |
Resolution and Verification of Agent Identities using DNS and RDAP
References Referenced by |
normatively references | ||
| RFC 4355 |
IANA Registration for Enumservices email, fax, mms, ems, and sms
References Referenced by |
Proposed Standard | normatively references | |
| RFC 4415 |
IANA Registration for Enumservice Voice
References Referenced by |
Proposed Standard | normatively references | |
| RFC 5483 |
ENUM Implementation Issues and Experiences
References Referenced by |
Informational | normatively references | |
| RFC 8958 |
Updated Registration Rules for URI.ARPA
References Referenced by |
Best Current Practice | normatively references | |
| RFC 9676 |
LEX: A Uniform Resource Name (URN) Namespace for Sources of Law
References Referenced by |
Informational | normatively references | |
| RFC 3401 |
Dynamic Delegation Discovery System (DDDS) Part One: The Comprehensive DDDS
References Referenced by |
Informational | informatively references | |
| RFC 3402 |
Dynamic Delegation Discovery System (DDDS) Part Two: The Algorithm
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 3406 |
Uniform Resource Names (URN) Namespace Definition Mechanisms
References Referenced by |
Best Current Practice | informatively references |