RFC 5346: Operational Requirements for ENUM-Based Softswitch Use
In plain English — editorial summary, not part of the RFC
This document describes experiences of operational requirements and several considerations for ENUM-based softswitches concerning call routing between two Korean Voice over IP (VoIP) carriers, gained during the ENUM pre-commercial trial hosted by the National Internet Development Agency of Korea (NIDA) in 2006. These experiences show that an interim solution can maintain the stability of ongoing commercial softswitch system operations during the initial stage of ENUM service, where the DNS does not have sufficient data for the majority of calls. This memo provides information for the Internet community.
Document record
- Document ID
- RFC5346
- Published
- October 2008
- Authors
- J. Lim; W. Kim; C. Park; L. Conroy
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rai
- Pages
- 14
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- 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
- RFC 5076ENUM Validation Information Mapping for the Extensible Provisioning ProtocolCurrent
December 2007
- RFC 4969IANA Registration for vCard EnumserviceUpdated
August 2007
- RFC 4759The ENUM Dip Indicator Parameter for the "tel" URICurrent
December 2006
- RFC 6315IANA Registration for Enumservice 'iax'Current
July 2011
- RFC 3761The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application (ENUM)Obsoleted
April 2004
- RFC 2916E.164 number and DNSObsoleted
September 2000
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?