U.S. Dept of State ITAC-T Advisory Committee, SG-A AdHoc Meeting on ENUM, Washington DC, 28 Mar 2001

A Designated ENUM DN...
Designated ENUM DNS Zone Provisioning
                 Transaction Interfaces and Notes
ENUM DNS Transaction Interfaces
1 ...
Upcoming SlideShare
Loading in …5
×

A Designated ENUM DNS Zone Provisioning Architecture

1,216 views

Published on

VeriSign-Telcordia

Published in: Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
1,216
On SlideShare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
7
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

A Designated ENUM DNS Zone Provisioning Architecture

  1. 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 Most frequently the local telephone Tier1a Registry name servers directly in service provider the e164.foo zone file Authenticators Authenticates End User’s right to use specific Subscriber Number(s) assigned . [root] Digital within the national numbering plans of DNS geographical area foo. Certificate DNS Key Server e164.foo. Option DNS [1.e164.foo.] DNS 2 getdata query 1 2 4 1 These interfaces are either an Tier1a Registry 6 2 1 undefined commercial relationship or non-existent if N1.1.e164.foo the Authenticator is also the Tier2 Provider DNS Tier1a 3 Well-defined API Registrars SMS 3 2 Tier2 Provider 6 SMS 2 5 Subscriber DNS 4 Tier1a Registries N2.1.e164.foo 3 1 4 SMS 1 DNS 2 5 3 SMS Service User These interfaces are either an undefined commercial Tier1a registrars are LDAP relationship or non-existent if required to effect the Tier2 Provider is also a some kind of Tier1a Registrar contractual agreement between the Registrar and the It is unclear where this function Presumably similar to today’s Registry for which belongs and how it is supported Public EPP protocol for Registry- write permissions are by other providers Registrar interworking granted 1 VeriSign-Telcordia
  2. 2. Designated ENUM DNS Zone Provisioning Transaction Interfaces and Notes ENUM DNS Transaction Interfaces 1 Normal BIND resolution via root, foo, PKI Authentication Transaction Interfaces e164.foo, and 1.e164.foo nameservers 1 Subscriber obtains ENUM Digital Certificate 2 Normal BIND resolution down to fully authenticating right to use number using qualified ENUM name specified Tier2 provider 2 Certificate authority updates key server; 3 Normal BIND resolution to ENUM and when telephone or Tier2 provider nameserver supporting NAPTR records service is terminated, revokes the certificate 3 Subscriber (optionally) provides ENUM 4 Service user obtains ENUM URIs. Further digital certificate with SMS transaction 1 service queries using the URI may be 4 Tier2 provider verifies ENUM digital necessary but are not covered here. certificate 5 Tier2 provider (optionally) provides ENUM SMS Transaction Interfaces digital certificate to Tier1a provider with 1 Subscriber uses some form of Web or SMS transaction 2 phone API to: 1) establish the service, or 2) 6 Tier1a provider verifies ENUM digital maintain the service certificate 2 Tier2 Provider uses an undefined protocol to Request Tier1a Registrar instantiate Authentication Transaction Interfaces ENUM fully qualified ENUM name and 1 Tier2 provider (optionally) makes query to NAPTR nameserver inclusion verify subscriber’s right to use number 3 Tier1a Registrar uses EPP to create an 2 Tier1a Registrar (optionally) makes query to ENUM zone file with nameservers, similar to verify subscriber’s right to use number COM domain transactions today Directory Transaction Interfaces = coordinated provisioning 1 Public LDAP query = autonomous

×