RFC 3958: Domain-Based Application Service Location Using SRV RRs and the Dynamic Delegation Discovery Service (DDDS)
In plain English — editorial summary, not part of the RFC
This memo defines a generalized mechanism for application service naming that allows service location without relying on rigid domain naming conventions (so-called name hacks). The proposal defines a Dynamic Delegation Discovery System (DDDS) Application to map domain name, application service name, and application protocol dynamically to target server and port. [STANDARDS-TRACK]
Document record
- Document ID
- RFC3958
- Published
- January 2005
- Authors
- L. Daigle; A. Newton
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- —
- Pages
- 25
- Also known as
- —
- Updated by:
- RFC 8553
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4095Attaching Meaning to Solicitation Class KeywordsCurrent
May 2005
- RFC 3761The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application (ENUM)Obsoleted
April 2004
- RFC 5483ENUM Implementation Issues and ExperiencesCurrent
March 2009
- RFC 6116The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application (ENUM)Current
March 2011
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?