References from draft-malas-enum-trunk-sip
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 |
References Referenced by |
normatively references | ||
| RFC 1034 |
Domain names - concepts and facilities
References Referenced by |
Internet Standard | normatively references | |
| RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels
References Referenced by |
Best Current Practice | normatively references | |
| RFC 3261 |
SIP: Session Initiation Protocol
References Referenced by |
Proposed Standard | normatively references | |
| RFC 3402 |
Dynamic Delegation Discovery System (DDDS) Part Two: The Algorithm
References Referenced by |
Proposed Standard | normatively references | |
| RFC 3403 |
Dynamic Delegation Discovery System (DDDS) Part Three: The Domain Name System (DNS) Database
References Referenced by |
Proposed Standard | normatively 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 3764 |
enumservice registration for Session Initiation Protocol (SIP) Addresses-of-Record
References Referenced by |
Proposed Standard | normatively references | |
| RFC 4904 |
Representing Trunk Groups in tel/sip Uniform Resource Identifiers (URIs)
References Referenced by |
Proposed Standard | normatively references | |
| RFC 5483 |
ENUM Implementation Issues and Experiences
References Referenced by |
Informational | normatively references | |
| RFC 5486 |
Session Peering for Multimedia Interconnect (SPEERMINT) Terminology
References Referenced by |
Informational | normatively references | |
| STD 13 |
References Referenced by |
normatively references |