Operational Requirements for ENUM-Based Softswitch Use
RFC 5346
Revision differences
Document history
| Date | By | Action |
|---|---|---|
|
2018-12-20
|
(System) | Received changes through RFC Editor sync (changed abstract to 'This document describes experiences of operational requirements and several considerations for ENUM-based softswitches concerning call routing … Received changes through RFC Editor sync (changed abstract to '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.') |
|
2015-10-14
|
(System) | Notify list changed from enum-chairs@ietf.org, draft-ietf-enum-softswitch-req@ietf.org to (None) |
|
2008-11-05
|
(System) | Posted related IPR disclosure: Comcast IP Holdings I, LLC's Statement about IPR related to RFC 3953, RFC 4415, RFC 4759, RFC 4769 … |
|
2008-10-06
|
Amy Vezza | State Changes to RFC Published from RFC Ed Queue by Amy Vezza |
|
2008-10-06
|
Amy Vezza | [Note]: 'RFC 5346' added by Amy Vezza |
|
2008-10-03
|
(System) | RFC published |