ENUM-based Softswitch Requirement
draft-lim-kim-enum-based-softswitch-01
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | JoonHyung Lim | ||
| Last updated | 2010-04-26 (Latest revision 2007-03-02) | ||
| Replaced by | RFC 5346 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-enum-softswitch-req | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This document describes operational requirement and several considerations for ENUM-based softswitch, which can route a call between 2 Korean VoIP carriers during the ENUM pre-commercial trial hosted by National Internet Development Agency of Korea(NIDA) in 2006. This experience can be one of interim solution to maintain stability of on-going commercial softswitch system while initial stage of ENUM service that does not have sufficient data.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)