1. National Internet Development Agency of Korea (NIDA)
RFC4114 Experiences
6 Dec. 2007
Joonhyung Lim /
National Internet Development Agency of Korea (NIDA)
PEPPERMINT BoF
70th IETF – Vancouver

2. Background KR(+82) Infra ENUM trial in 2006
Call routing using infra ENUM was tested between 2 KR VoIP carriers and NIDA(2.8.e164.arpa operator)
EPP also implemented based on RFC4114
ENUM WG Document : ENUM-based Softswitch Requirement
See the detail about KR infra ENUM trial

3. Trial System Topology

4. Our implementation (EPP Commands)
Service discovery Commands
<hello>
<greeting>
Session Management Commands
<login>, <logout>
Although it was not defined in 4114, but 3730, we had to identify multiple carriers.
Query Commands
<check>
<info>
Object Transform Commands
<create>
<delete>
<update>
<renew> : never used
<transfer> : never used

5. Issues EPP Command Issues Carrier Issues
Some commands from RFC3730 was needed
i.e. <login>, <logout>
Some commands from RFC4114 was not needed
i.e. <renew>, <transfer>
Carrier Issues
Usually carriers already have their own system for E.164 number provisioning
New E.164 number must be added to ENUM registration server, softswitch, and billing server simultaneously.
What is the easiest way to implement a ENUM provisioning function on currently running system?

6. Thank You!