2006-06 ENUM McEachern

8/12/2019 2006-06 ENUM McEachern

1/24

THIS IS THE WAYENUM Variants

Jim McEachern

Carrier VoIP Standards Strategy

THIS IS


2/24

- 2 -

ENUM Variants

User ENUM

Infrastructure ENUM

Private ENUM

Enterprise ENUM

ENUM to enable new business models


3/24

- 3 -

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?


4/24

- 4 -

ENUM for Dummies

Public

(e164.arpa)

Private

User URI Interconnect URI

User

ENUM

Infrastructure

ENUM

Private

ENUM

Infrastructure

ENUM?


5/24

- 5 -

Who is in Control?

Public

(e164.arpa)

Private


User

ENUM

Infrastructure

ENUM

Private

ENUM

Infrastructure

ENUM?

End User

opt-in


6/24

- 6 -

ENUM Variants

User ENUM

Infrastructure ENUM

Private ENUM

Enterprise ENUM

ENUM for new business model


7/24- 7 -

User ENUM (SIP) Call Flow

1. The caller

simply dials the

persons normal

telephone number

2. Calling party proxy UAC queries

DNS for location of end point

3. DNS returns NAPTR record

containing SIP URL

4. Calling party UA connects the call

ENUM Global Directory (DNS) Equates+1-202-555-1234 to sip:[email protected] enable Voice over IP using SIP

ENUM typically illustrated like this, but


8/24- 8 -

User ENUM vs. SIP

User ENUM query can return a single response, or multipleresponses, with priority indicated.

sipping WG (RFC 3824) recommends returning a single SIP address-of-

record, and letting SIP mechanisms deal with priorities, capabilities,

preference, presence & redirection.

User ENUM allows multiple entries, including priorities and capabilities.

SIP, H.323, mobile, messages, email, etc.

can even return another E.164 number

duplicates functionality in SIP

no consensus on which should be used

User ENUM provides user preferences for being reached

hints to help the caller decide where to direct the call

nothing requires the caller to follow those preferences


9/24- 9 -

Alternative User ENUM/SIP Call Flow

1. Caller dials normal

phone number

2. SIP UAC queries DNS for

location of end point

3. DNS returns NAPTR record

containing SIP URL to Calling Party

UA

4. Callers UA initiates call with SIP URL

ENUM Global Directory (DNS) Equates+1-613-555-1234 to sip:[email protected] enable Voice over IP using SIP

ENUM query can be done by VoIP client

ENUM

SIPProxy

SIPProxyDial

+1-613-555-1234

Query

4.3.2.1.5.5.5.3.1.6.1.e164.arpa?

Response

sip:[email protected]

Sip

Sip:[email protected]

Call Setup


10/24- 10 -

User ENUM for Routing?

ENUM

Carrier A Carrier B

SIPProxy

SIPClient

B

SIPProxy

SIPClient

A

Internet

?

?

?

User ENUM cannot provide routing


11/24- 11 -

ENUM Variants

User ENUM

Infrastructure ENUM

Private ENUM

Enterprise ENUM



12/24- 12 -

Infrastructure ENUM

I-ENUM

Carrier A Carrier B

SIPProxy

SIPClient

B

SIP

Proxy

SIPClient

A

Internet

Infrastructure ENUM identifies interconnect point


13/24- 13 -

VoIP Peering

IETF SPEERMINT WG is addressing VoIP peering problem

in cooperation with Infrastructure ENUM

Infrastructure ENUM identifies the carrier of record, but if you have a business relationship, you already know theinterconnection point for that carrier.

if you dont have a business relationship, you probably wont be

allowed to directly interconnect anyway.

What problem is SPEERMINT solving?


14/24- 14 -

ENUM Variants

User ENUM

Infrastructure ENUM

Private ENUM

Enterprise ENUM



15/24- 15 -

ENUM for 3GPP IMS

IMS specifies that all routing shall be based on SIP URI E.164 numbers shall be translated to SIP URI using ENUM, or any

other suitable translation database

ENUM in IMS must be Private ENUM full SIP URI required for routing

data privacy laws

competitive information

Infrastructure ENUM can be used to interconnect betweenIMS networks


16/24- 16 -

IMS - Private ENUM

I-ENUM

Carrier A Carrier B

SIPProxy

SIPClient

B

SIP

Proxy

SIPClient

A

Internet

Private ENUM Translates E.164 - to - URI

P-ENUM

P-ENUM


17/24

- 17 -

ENUM Variants

User ENUM

Infrastructure ENUM

Private ENUM

Enterprise ENUM



18/24

- 18 -

Enterprise ENUM

ENUM

Carrier A Carrier B

SIPProxy

SIPClient

C

SIPPBX

SIPClient

A

Internet

Enterprise ENUM can take many forms

SIPClient

B

Internal translation

from E.164 to SIP URI

1 2 3

ENUM


19/24

- 19 -

Enterprise ENUM

Public

(e164.arpa)

Private


User

ENUM

Infrastructure

ENUM

Private

ENUM

Infrastructure

ENUM?

32

1


20/24

- 20 -

ENUM Variants

User ENUM

Infrastructure ENUM

Private ENUM

Enterprise ENUM



21/24

- 21 -

New ENUM Applications - vCard

ENUM

Carrier A Carrier B

SIPProxy

SIPClient

B

SIPPBX

SIPClient

A

Query based on originating E.164 number

vCard


22/24

- 22 -

New ENUM Applications - CNAM

Carrier A Carrier B

SIPProxy

SIPClient

B

SIPPBX

SIPClient

A

Query based on originating E.164 number

P-ENUM


23/24

- 23 -

Summary

When ENUM is specified, which variant is intended?

ENUM flavors are reasonably orthogonal With clear rules they could be completely orthogonal

Many interesting applications for ENUM will use

Private ENUM


24/24

24

Thank you

Documents

2006-06 ENUM McEachern