enumservice Compendium, Trial, Demo

1
enumserviceCompendium, Trial, Demo

• IETF 55November 2002
• Lawrence Conroy Richard STASTNY
• Roke Manor Research ÖFEG, Postfach 147,
  1103-Wien
• Tel[phone] Tel [phone]
• Fax [phone] E-Maillwc_at_roke.co.uk
  E-Mail richard.stastny_at_oefeg.at richard_at_sta
  stny.com

2
Content

• Background
• The Austrian ENUM Trial Platform
• Scope of the ENUM trials
• Tasks of the ENUM trial partners
• Status of the ENUM trials
• Current functionality
• Demonstration of the trials
• More information

3
Backgrounder

• This is a Calling Party Control Scheme - but
• We intend it as an extensible framework, into
  which the Called Party Control enumservices
  fit.
• Focus on Kind of Communication caller wants
• Execution of this Kind of Communication can be by
  a number of different protocols - URI scheme
  handlers
• Note that, in the current trial, all the clients
  cheat - they look to the right in the NAPTRs
  they have. Some of our examples in the Draft (and
  on the list) have shown an enumservice without a
  protocol sub-field with a copy of the URI
  scheme. This is NOT a key feature of the
  compendium

4
View of ENUM

• "Electronic Business Card" Calling Party
  Control
• ENUM subscriber (recipient) offers all his
  contacts
• ENUM User (originator) selects application
• ENUM entries may raise privacy issues
• Personal User Agent Called Party Control
• The ENUM subscriber offers only one pointer to a
  "Service Resolution Service" (e.g. SIP, H323)
• Application or service selection is done by
  negotiation with the PUA of the recipient
• ENUM entires may expose no private data
• ENUM as Number Translation Database
• Infrastructure ENUM for Number Portability and
  other IN-services
• Routing Numbers, PSTN-Numbers, Gateways, Proxy
  Server, Gatekeeper

5
ENUM Services and Applications

• talk interactive (media stream exchange) calls
• voice, ivoice, video tel, sip, h323
• msg discrete (non-session related) messages
• email mailto
• fax tel
• sms, ems, mms tel, eventually sip and mailto
• chat session-oriented message exchanges
• im instant messaging- sip (SIMPLE)
• tp textphone- tel
• info information source
• web http, https
• ft ftp
• srs service resolution service
• sip sip
• h323 h323
• dap ldap
• all default

• Additional services
• public keys
• location information (GPS coord.)
• number portability info

IN NAPTR 10 10 "U" "E2Uvoiceh323"
"!.!h323richard23_at_telekom.at!" .
6
More Examples

• A caller who is interested in (say) talking to
  callee might filter on the category talk, and its
  comprised services (voice/ivoice, video) --
  example 1
• A caller who is interested in sending a message
  might filter on the category msg and its
  comprised servicesexample 2

1) IN NAPTR 10 10 "U" "E2Uvoiceh323"
"!.!h323richard23_at_telekom.at!" .
2) IN NAPTR 10 10 "U" "E2Usmstel"
"!.!tel[phone]!svcsms" .
or
IN NAPTR 10 10 "U" "E2Uemailmailto"
"!.!mailtorichard_at_stastny.com!" .
7
...Now how we use it...

• Background in Austria
• The Austrian ENUM Trial Platform
• Scope of the ENUM trials
• Tasks of the ENUM trial partners
• Status of the ENUM trials
• Current functionality
• Demonstration of the trials
• More information

8
ENUM Background in Austria

• 2000-09 Start of activities
• 2001-08 First consulation by Austrian regulator
  (RTR)
• 2001-09 Telekom Austria internal Task Force
• 2002-02 ENUM Workshop RTR, group of interested
  partners formed
• 2002-05 Interim procedures from ITU-T SG2 and TSB
• 2002-05 Delegation request by RTR to RIPE and
  ITU-TSB
• 2002-06 Tier 1 Registry in operation by NIC.AT
  (the Austrian ccTLD)
• 2002-06 Tier 1 Registry in operation by Infonova
  (VISIONng)
• 2002-06 Delegations for 3.4.e164.arpa and
  0.1.8.7.8.e164.arpa
• 2002-06 Start of development and deployment
• 2002-07 First draft of policy framework for MoU
  by RTR
• 2002-09 Austrian ENUM Trial Platform estabished

9
Austrian ENUM Trial Platform

• Mission
• Co-ordination of activities for the Austrian ENUM
  trial between the trial partners
• Tasks
• develop and approve documents beside the
  regulatory framework compulsory during the trial
• enable communication between the trial partners
• monitor trial activities
• monitor international ENUM standards and trial
  activities
• gather results and experiences
• serve as a basis for a Austrian ENUM forum
  required for commercial implementation
• Members
• RTR, NIC.AT, Telekom Austria, Infonova, AOSA,
  Kapsch, ÖFEG, Telcordia

10
Scope of the ENUM Trials

• Provide a DNS based infrastructure in Tier 1 and
  Tier 2
• Basic administration und validation by Registrar
  (ENUM Service Provider) and Tier 1 Registry
  including the necessary provisioning processes
• Web-Portal for registration of ENUM Subscribers
  and for simple manipulations of the entries in
  Tier 2
• Client-SW for ENUM Users to query the ENUM
  database
• VoIP Applications for ENUM Subscribers and Users.
• Evaluation of standards and feedback to the
  relevant bodies
• Evaluation of the services provided and of user
  feedback
• Monitoring of and interworking with other trials
• ETSI Guide Minimum requirements for
  interoperability of European ENUM trials
• Basis ETSI TS 102 051, RFC2916bis, RFC3403,
  draft-brandner-enum-compendium and related
  drafts.

11
Tasks of the trial partners

• "Inner circle" (must sign MoU)
• RTR responsible for policy framework
• Nic.at tier 1 registry
• Telekom Austria a registrar and tier 2
  nameserver (ENUM SP)
• "Outer circle"
• Client SW (Infonova, Kapsch, AOSA (Siemens,
  Alcatel), Telcordia)
• Provisioning SW (Infonova, Telcordia)
• Applications (Telekom Austria (VoIP), any others)
• Consulting, standards (OeFEG)

12
ENUM Trials Workplan

• 2002-03 Start of planning activities
• 2001-06 Tier 1 Registry (NIC.AT and Infonova) in
  operation
• 2002-06 Start of development
• 2002-09 Tier 2 Nameserver (Telekom Austria) in
  operation
• First clients available (ENUM
  queries on public Internet)
• 2002-10 Web-Portal for Registration and
  Modification in operation
• 2002-10 SIP and H.323 VoIP applications available
• 2002-10 First Live Demo in Atlanta, GA
  (VISIONng/VON/TIPHON)
• 2002-10 Set-up of call center and registrar
• 2002-11 Test of provisioning processes with
  selected subscribers
• 2002-12 Ready to invite real subscribers and
  users
• 2003-04 End of phase 1 of trial (feasability
  study)
• decision required to start phase 2
  (pre-commercial)

13
Validation within the trial

• Requirements
• ENUM subscriber shall be the assignee of an E.164
  number valid for the ENUM trial and the number
  shall be in operation with a TSP.
• It has to be verified, that the ENUM subscriber
  is the named entity
• Registration shall cease if first item is no
  longer valid.
• Interim solution for trial
• Only known subscribers
• later identification via billing address possible
• Only geographic and mobile numbers
• Number shall be listed in directory, data need to
  be the same
• Validation done by Registrar
• De-validation with periodic check (will be
  automated)
• Evaluation of methods during trial
• Open issue corporate ENUM subscribers

14
WHOIS

• ENUM is DNS
• Processes have to be similar to normal domain
  name administration
• For operation of DNS the storage of e.g.
• Domain Name Holder
• Administrative Contact
• Technical Contact
• in a database is necessary (WHOIS-DB)
• Currently there is still a discussion, which data
  are stored in the WHOIS-DB and which data are
  public available.
• Regarding the Austrian ENUM Trial it has been
  decided temporarily that all data are stored and
  are public available.
• Domain Name Holder ENUM Subscriber
• admin-c Registrar
• tech-c Nameserver Provider

15
ENUM Trial Application Aspects
ENUM Trial Administrative Aspects
ENUM USER
ENUM DNS QUERY
ENUM TIER 0 NS
RTR policyframework
ITU TSB RIPE NCC
WHOIS
3.4.e164.arpa
ENUM Application email VoIPetc.
NIC.AT
ENUM TIER 1 NS
ENUM TIER 1 Registry
ENUM DELEGATION
ENUM SP TELEKOM AUSTRIA
x.x.x.x.3.4.e164.arpa
ENUM TIER 2 NS
ENUM TIER 2 Register
ENUM Registrar
Communication
ENUM NAPTR MODIFICATION
VALIDATION
ENUM SUBSCRIBER
Web SERVICES
REGISTRATION
Web portal
16
Austrian ENUM and UPT ENUM
17
Why UPT ENUM?
National ENUM is a second line service
4317973321
UPT ENUM is a primary line service
878108781087810
18
Demonstration of ENUM Trials

• DNS-query of ENUM entries by ENUM User with ENUM
  client SW
• This is the basic client - with manual selection
  by caller from returned list
• There are others that take a callers
  pre-selected Kinds of Communication/Services of
  Interest and use this to filter the returned
  NAPTRs
• Another takes calling line information data,
  performs an ENUM lookup, and displays returned
  data (e.g. a TXT record with name, or info/web -
  Super Caller Display)
• Yet another one takes a bar-coded business card
  and does an ENUM lookup to extract the contact
  records.

19
More Information

• Austrian ENUM Trial Web-site
• http//enum.nic.at