A Designated ENUM DNS Zone Provisioning Architecture

1. U.S. Dept of State ITAC-T Advisory Committee, SG-A AdHoc Meeting on ENUM, Washington DC, 28 Mar 2001 A Designated ENUM DNS Zone Provisioning Architecture Could be omitted, placing instead the Tier1a Registry name servers directly in the e164.foo zone file Most frequently the local telephone service provider Authenticators Authenticates End User’s right to use specific Subscriber Number(s) assigned within the national numbering plans of geographical area . [root] DNS Digital Certificate Option foo. DNS Key Server e164.foo. DNS DNS [1.e164.foo.] 2 getdata query 1 4 2 1 These interfaces are either an undefined commercial relationship or non-existent if the Authenticator is also the Tier2 Provider Tier1a Registry 2 6 1 N1.1.e164.foo DNS Tier1a Registrars 3 Well-defined API SMS Tier2 Provider SMS 2 3 6 Subscriber 2 DNS 5 4 Tier1a Registries N2.1.e164.foo 3 SMS 1 DNS 4 1 2 5 3 SMS Service User These interfaces are either an undefined commercial relationship or non-existent if the Tier2 Provider is also a Tier1a Registrar LDAP Tier1a registrars are required to effect some kind of contractual agreement between the Registrar and the Registry for which write permissions are granted It is unclear where this function belongs and how it is supported by other providers Public Presumably similar to today’s EPP protocol for Registry-Registrar interworking 1 VeriSign-Telcordia

2. Designated ENUM DNS Zone Provisioning Transaction Interfaces and Notes ENUM DNS Transaction Interfaces PKI Authentication Transaction Interfaces SMS Transaction Interfaces Authentication Transaction Interfaces Directory Transaction Interfaces = coordinated provisioning = autonomous