1. THIS IS THE WAY ENUM Variants Jim McEachern Carrier VoIP Standards Strategy THIS IS

2. - 2 - ENUM Variants User ENUM Infrastructure ENUM Private ENUM Enterprise ENUM ENUM to enable new business models

3. - 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. - 4 - ENUM for Dummies Public (e164.arpa) Private User URIInterconnect URI User ENUM Infrastructure ENUM Private ENUM Infrastructure ENUM?

5. - 5 - Who is in Control? Public (e164.arpa) Private User URIInterconnect URI User ENUM Infrastructure ENUM Private ENUM Infrastructure ENUM? Carrier Control End User opt-in End User opt-in

6. - 6 - ENUM Variants User ENUM Infrastructure ENUM Private ENUM Enterprise ENUM ENUM for new business model

7. - 7 - User ENUM (SIP) Call Flow 1. The caller simply dials the person’s 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:name@domain.com to enable Voice over IP using SIP ENUM typically illustrated like this, but…

8. - 8 - User ENUM vs. SIP User ENUM query can return a single response, or multiple responses, 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. - 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. Caller’s UA initiates call with SIP URL ENUM Global Directory (DNS) Equates +1-613-555-1234 to sip:jmce@domain.com to enable Voice over IP using SIP ENUM query can be done by VoIP client ENUM SIP Proxy SIP Proxy Dial +1-613-555-1234 Query 4.3.2.1.5.5.5.3.1.6.1.e164.arpa? Response sip:jmce@domain.com Sip Sip:jmce@domain.com Call Setup

10. - 10 - User ENUM for Routing? ENUM Carrier A Carrier B SIP Proxy SIP Client B SIP Proxy SIP Client A Internet ? ? ? ? ? ? User ENUM cannot provide routing

11. - 11 - ENUM Variants User ENUM Infrastructure ENUM Private ENUM Enterprise ENUM ENUM for new business model

12. - 12 - Infrastructure ENUM I-ENUM Carrier A Carrier B SIP Proxy SIP Client B SIP Proxy SIP Client A Internet Infrastructure ENUM identifies interconnect point

13. - 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 the interconnection point for that carrier. if you don’t have a business relationship, you probably won’t be allowed to directly interconnect anyway. What problem is SPEERMINT solving?

14. - 14 - ENUM Variants User ENUM Infrastructure ENUM Private ENUM Enterprise ENUM ENUM for new business model

15. - 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 between IMS networks

16. - 16 - IMS - Private ENUM I-ENUM Carrier A Carrier B SIP Proxy SIP Client B SIP Proxy SIP Client A Internet Private ENUM Translates E.164 - to - URI P-ENUM

17. - 17 - ENUM Variants User ENUM Infrastructure ENUM Private ENUM Enterprise ENUM ENUM for new business model

18. - 18 - Enterprise ENUM ENUM Carrier A Carrier B SIP Proxy SIP Client C SIP PBX SIP Client A Internet Enterprise ENUM can take many forms SIP Client B Internal translation from E.164 to SIP URI Internal translation from E.164 to SIP URI 1 2 3 ENUM

19. - 19 - Enterprise ENUM Public (e164.arpa) Private User URIInterconnect URI User ENUM Infrastructure ENUM Private ENUM Infrastructure ENUM? 3 2 1

20. - 20 - ENUM Variants User ENUM Infrastructure ENUM Private ENUM Enterprise ENUM ENUM for new business model

21. - 21 - New ENUM Applications - vCard ENUM Carrier A Carrier B SIP Proxy SIP Client B SIP PBX SIP Client A Query based on originating E.164 number vCard

22. - 22 - New ENUM Applications - CNAM Carrier A Carrier B SIP Proxy SIP Client B SIP PBX SIP Client A Query based on originating E.164 number P-ENUM

23. - 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 - Thank you