ENUM Tutorial

Slides by Steven D. Lind, AT&T

Jim McEachern

Disclaimer
Heavily borrowed from:
Patrik Faltstrms IETF presentation to February 2002 ITU Workshop on ENUM AT&T/ENUM Forum presentation to December 2002 SG2 meeting

Assumption
Use of standard telephone numbers is not going away
PSTN/analog terminals are going to be around IP phones use 12button keypad Globally unique identifier that has established familiarity with end users

Problem statements
How do network elements (gateways, SIP servers etc) find services on the Internet if you only have a telephone (E.164) number? How can subscribers define their preferences for incoming communications?

More Problem Statements

How do you address an IP-based voice terminal from the PSTN? For a call that starts out as VoIP, how do you know to keep the call on the IP-plane (as opposed to the PSTN) for a dialed telephone number if the customer is not yours?

Today, Many Addresses

tel:+46-8-971234 mailto:paf@example.com tel:+46-706051234 sip:paf@example.com

With ENUM, Only One

tel:+46-8-971234 ENUM mailto:paf@example.com tel:+46-706051234 sip:paf@example.com

Give this number to friends: +46-8-971234

Solution in short
Put domain names derived from telephone numbers in the global domain name system, DNS IETF ENUM Working Group created to solve the problem of using the DNS for:
domain name in [Numbers re-formatted as domain names] URI out [mailto, sip, tel, http or other URI scheme]

Solution: NAPTR records Use the URIs for the communication

ENUM in a nutshell
take phone number +46-8-6859131

turn into domain name ask the DNS

1.3.1.9.5.8.6.8.6.4.e164.arpa.

mailto:paf@cisco.com return list of URIs sip:paf@cisco.com

Step 1
Take an E.164 number and create a fully qualified domain name in a single highly defined and structured domain The input to the +46-8-971234 NAPTR algorithm +468971234 4.3.2.1.7.9.8.6.4.e164.arpa.

Step 1 - Explanation
Each digit can become a definable and distributed zone in DNS terms Delegation can (doesnt have to) happen at every digit, including at last digit Zones such as country codes, area codes or primary delegated blocks of numbers can be delegated as well as individual numbers DNS defines authoritative name servers for NAPTR/service resource records

Step 2
Lookup NAPTR RRs in DNS, and apply NAPTR/ENUM algorithm
4.3.2.1.7.9.8.6.4.e164.arpa. !^.*$!mailto:spam@paf.se! !^+46(.*)$!ldap://ldap.telco.se/cn=0\1!

Use rewrite rules using regular expressions which operate on the E.164 number (+468971234)

Regular Expressions
For ENUM, the NAPTR regexp field may yield an (unchanged) URL !<regexp>!<string>!
Match <regexp> on original E.164, and apply rewrite rule <string>
^ - Match beginning $ - Match end . - Match any character .* - Match any number of any character () - Grouping, \n in <string> is replaced with group number n in <regexp>

Step 2 in detail
$ORIGIN 4.3.2.1.7.9.8.6.4.e164.arpa. IN NAPTR 10 10 U mailto+E2U !^.*$!mailto:spam@paf.se! IN NAPTR 20 10 U ldap+E2U !^+46(.*)$!ldap://ldap.telco.se/cn=0\1 Note that no line break should be in the records

Provisioning
Authentica tion & Validation Entities

Domain Name System

Tier 0

ENUM Enabled Applications

Registrar

Registry

Tier 1
Application Service Provider

Tier 2

voice fax messaging & presence email web pages

The Public ENUM Infrastructure

e164.arpa Tier 0 (Country Code Registry)
$ORIGIN e164.arpa. 3.7.9.1 IN NS nsnanp.enum.com . 4.4 IN NS sweden_enum.com .

sweden_enum.com (4.4.e164.arpa)

Tier 1 (Telephone Number Registry) nsnanp.enum.com (3.7.9.1.e164.arpa)

$ORIGIN 3.7.9.1.e164.arpa. 7.9.7.6.6.3.2 IN NS e164.att.net . 8.9.7.6.6.3.2 IN NS e164.xyz.com .

Tier 2 (Application Information) e164.att.net

$ORIGIN 7.9.7.6.6.3.2.3.7.9.1.e164.arpa. IN NAPTR 100 10 "u" "sip+E2U" "!^.*$!sip:19732366797@att.net!" .

International Implementation worked in IETF and ITU-T National Implementation worked in ENUM Forum (US)

Important Aspects of ENUM

Access Public DNS (e164.arpa) or Private? Content User URI (AoR) or Interconnection URI? Control of content End user opt-in & control, or carrier control? Routing decision originating end user, terminating end user, or carrier?

- 17 -

ENUM for Dummies

Public (e164.arpa)

User ENUM

Infrastructure ENUM

Private

Private ENUM

Infrastructure ENUM?

User URI
- 18 -

Interconnect URI

Who is in Control?
Public (e164.arpa)

End User User opt-in ENUM

Infrastructure ENUM

Private

Private ENUM

Infrastructure ENUM?

User URI
- 19 -

Interconnect URI

User ENUM (SIP) Call Flow

ENUM Global Directory (DNS) Equates +1202-555-1234 to sip:name@domain.com to enable Voice over IP using SIP 3. DNS returns NAPTR record containing SIP URL 2. Calling party proxy UAC queries DNS for location of end point

1. The caller simply dials the persons normal telephone number

4. Calling party UA connects the call

- 20 -

ENUM typically illustrated like this, but

Infrastructure ENUM
I-ENUM
SIP Proxy

SIP Proxy

SIP Client A

SIP Client B

Carrier A
Internet

Carrier B

Infrastructure ENUM identifies interconnect point

- 21 -

IMS - Private ENUM

I-ENUM
P-ENUM
SIP Proxy

P-ENUM

SIP Proxy

SIP Client A

SIP Client B

Carrier A
Internet

Carrier B

Private ENUM Translates E.164 - to - URI

- 22 -

Enterprise ENUM
SIP Client B

Internal translation from E.164 to SIP URI

ENUM

2
SIP PBX

SIP Proxy

SIP Client A

SIP Client C

Carrier A
Internet

Carrier B

- 23 -

Enterprise ENUM can take many forms