ENUM: history and current status and future Explanation of ENUM (RFC 2916)

Patrik Fältström . Naming and Name Space Workshop. July 22, 2002, Seoul

ENUM: history and current status and future

Explanation of ENUM (RFC 2916)

Patrik Fältström<[email protected]>

Corporate Consulting Engineer, Cisco

Area Director, Applications Area, IETF

Patrik Fältström . Naming and Name Space Workshop. July 22, 2002, Seoul 2

Patrik FältströmConsulting EngineerOffice of the CTO170 W Tasman DriveSan José, CA 95134USADirect: +1-426-525-8509Fax: +1-408-526-8766Mobile: +46-70-6059051Email: [email protected]: http://www.cisco.com

Patrik FältströmConsulting EngineerOffice of the CTOÅrstaängsvägen 31J117 43 StockholmSwedenPhone: +46-8-6859000Direct: +46-8-6859131Fax: +46-8-190424Mobile: +46-70-6059051Email: [email protected]: http://www.cisco.com

Patrik FältströmFounder / OwnerFirma PAFLedåsa273 71 LövestadSwedenEmail: [email protected]: http://paf.se

Patrik FältströmLedåsa273 71 LövestadSwedenEmail: [email protected]: http://alexandria.paf.se

Patrik FältströmArea Director, Applications AreaIETFEmail: [email protected]: http://www.ietf.org

How many addresses do you have on your buissness card?


Today, many addresses

tel:+46-8-971234

mailto:[email protected]

tel:+46-706051234

sip:[email protected]


Today

• Convergence

• Telecom in Turmoil

• The IP and PSTN worlds are about to collide


Where are we?

• There are substantial indicators that the market for IP Telephony is turning– Enterprise driven– 40% CAGR– IP-PBX sales are

gaining steam …..– IP-Centrex has the

attention of service providers


Buissnes case for VoIP

• Enterprise want to leverage investment in IP networks

• Cost Reduction – Toll Bypass

• Still the #1 argument• Toll Charges $960.00 per line per

year

– Simplified Add Modify and Delete of Users

– Single Wiring Harness

• Rapid Service Creation – Applications created at the Edge

using standard tools – XML– Time to market


VoIP Issues?

• Protocol Wars are over …. SIP wins!– Every Copy of XP is SIP enabled– Enterprise .NET server will be a SIP proxy– Every major Enterprise Phone Vendor supports SIP

• SIP Unifies Real-time Communications– Voice

– Text [ Instant Messaging ]

– Video

• Quality of Service Issues now well understood– 802.1p Ethernet Priority Bit

– Remove Hubs – Convert to 10/100 switches

– Overprovision IP transport


With ENUM, only one

tel:+46-8-971234


tel:+46-706051234

sip:[email protected]

tel:+46-706051234

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

ENUM


ENUM in a nutshell

• take phone number +46-8-6859131

• turn into domain name 1.3.1.9.5.8.6.8.6.4.e164.arpa.

• return list of URI’ssip:[email protected]

• ask the DNS



“Call setup”

ENUM use in more detail

Sipsip:[email protected]

Query1.3.1.9.5.8.6.8.6.4.e164.arpa.?

Dial+4686859131

DNS-Server

Sip serverGateway

Responsesip:[email protected]


ExampleDNS-Server

InternetPSTN

Cal

led

par

ty

Cal

ling

par

ty


VoIP via SIP to VoIPDNS-Server

“ENUM”


PSTN via SIP to VoIPDNS-Server

“ENUM”


Step 1

• Take an E.164 number and create a fully qualified domain name in a single highly defined and structured domain

• +46-8-971234

• +468971234

• 4.3.2.1.7.9.8.6.4.e164.arpa.

The input to theNAPTR algorithm


Step 1, Explanation

• Each digit can become a definable and distributed “zone” in DNS terms

• Delegation can (doesn’t 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 RR’s in DNS, and apply NAPTR/ENUM algorithm4.3.2.1.7.9.8.6.4.e164.arpa.!^.*$!mailto:[email protected]!!^+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:[email protected]!”• 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


How is this used?

Internet

TelcoPSTN

ISP

IPENUM


Convergence...

Internet

TelcoPSTN

ISP

IPENUM

ISP

ASP≠ISPWho pays how much to who for what?

ASP


Payment for IP

Internet

TelcoPSTN

ISP

IP

ISP

Money movestowards the center

ASP


Payment for Service

Internet

TelcoPSTN

ISP

IP

ISP

Money doesn’t routewell over the Internet

ASP


Payments

• PSTN– Fixed fee– Termination fee (per minute charge) that follows

the call

• Email– Payment for IP– Payment for both incoming and outgoing

• VoIP– Payment for IP– Payment for both incoming and outgoing

• No termination fees for VoIP!


Avoid Tromboning

Internet

ISP

ISP

If there is no termination fee for VoIP,

originator want to know where final destination is

PSTN


Voice Extranet

• Phone numbers only routable over PSTN network

• Enterprise Dialing plans cannot be accessed by Trading Partners

• Connect “Friends and Family” Customers and Suppliers to Single Dialing plan E.164

ENUM


Voice Intranet

• Enterprises want to use unite global dialing plans across existing VPN and Intranet Links

• ENUM unites them through common administration and access plan

ENUM


• RFC 2916 published in September 2000• The domain e164.arpa delegated to RIPE

NCC– RIPE NCC appointed by the IAB according to RFC

2916

• ITU SG2/WP1/2 liaison statement:– Member state can inform ITU on entry of numbers

in DNS

Status (done)


Status (done)

• ENUM Nation-State Application Process Ratified in May 2002

• In short:– Requests sent to RIPE NCC– RIPE NCC announces the request

• On public mailing list

• On web page (http://www.ripe.net/enum/)

• To TSB via electronic mail

– Waiting period 60 days– If no issues

• Do delegation according to request

– If there are issues• Send case to TSB for further investigation


Status July 1, 2002

• RFC 2916 published in September 2000– New version draft-ietf-enum-rfc2916bis

• Delegations from e164.arpa– 44 (UK)– 43 (Austria)– 49 (Germany)– 87810 (Telekom Austria)– 991001 (Neustar)

• Information at RIPE– http://www.ripe.net/enum/


National Level

• France issues request for comments from French Telecom Industry

• Swedish regulator PTS issues ENUM roadmap and begins planning for Trials

• Swiss regulator OFFCOM Beginning Industry consultations.

• ETSI – Report on “Management of ENUM in Europe”

• European Commission monitoring ongoing activities

• Japan, USA and others:– Created Industry Forum


Conclusion

• Why ENUM?– Given E.164 number, what is the SIP URI?– Given E.164 number, what is email address?

• What is ENUM not?– Routing mechanism

• Still within scope of each protocol, i.e. ENUM is not a competitor with SIP

• Why is ENUM important?– Convergence will happen– Now is the time to talk in a country on how to

handle convergence in the larger picture

Patrik Fältström . Naming and Name Space Workshop. July 22, 2002, Seoul

Patrik Fältströ[email protected]

Date post:	02-Feb-2016
Category:	Documents
Upload:	vina
View:	51 times
Download:	0 times

ENUM: history and current status and future Explanation of ENUM (RFC 2916)

Documents