Presentation is loading. Please wait.

Presentation is loading. Please wait.

1ENUM ENUM Technical issues / DNS Patrik Fältström Area Director, Applications Area, IETF

Similar presentations

Presentation on theme: "1ENUM ENUM Technical issues / DNS Patrik Fältström Area Director, Applications Area, IETF"— Presentation transcript:

1 1ENUM ENUM Technical issues / DNS Patrik Fältström Area Director, Applications Area, IETF

2 2 ENUM Agenda Background Problem we want to solve Technical solution Conclusion

3 3ENUM Background 3

4 4 The Domain Name System It is a distributed database It is a protocol Often the two get mixed up

5 5 ENUM DNS as distributed database Central server, root server Server for com Server for se Server for jp Client Local resolver

6 6 ENUM Query Ask! Query Ask se! Query Query Local resolver Root-server Server se Server

7 7 ENUM Domains and zones bb sese nsns aa cc "root""root" nsns nsns zone "" domain "" domain/zone ""

8 8 ENUM Delegations Root server se. IN NS IN A IN NS IN NS IN NS IN A IN A IN A IN NS IN NS IN A IN A IN NS IN A IN N S IN A

9 9 ENUM E.164 numbers Allocation at CC level by the ITU, SG2/WP1/2 (from an IETF perspective) E.164 provides the number structure and functionality of numbers used for international public telecommunicationsHierarchically allocated

10 10 ENUM Structure of E digits CCNDC N digitsMax (15-N) digits SN National (significant) number International public telecommunication Number for geographical areas Structure to use for geographic areas

11 11ENUM Problem we want to solve 11ENUM

12 12 ENUM Problem statements 1(2) How do network elements find services on the Internet if you only have a telephone (E.164) number? How can subscribers (as opposed to carriers) define their preferences for incoming communications? How can we (IETF/ITU) enable new services while enabling competition, consumer choice and consumer protection?

13 13 ENUM Problem statements 2(2) How can consumers, carriers and new players have equal access to these new opportunities? How do we (IETF/ITU) make this simple and easy to use without reinventing the wheel?

14 14ENUM Technical solution 14ENUM

15 15 ENUM Solution in short Put telephone numbers* in the global domain name system, DNS ENUM Working Group created to solve the problem of using the DNS for: Domainname in [Numbers reformatted as domain names] URI out [mailto, sip, tel, http or other URI scheme] Solution was to use NAPTR records * Maybe not in the original E.164 format

16 16 ENUM Example $ORIGIN IN NAPTR " U " " sip+E2U " " " IN NAPTR " U " " ldap+E2U " " "

17 17 ENUM Why DNS? Its there It works… Its global… It scales… Its fast… Its open… Grandfather existing DNS delegation mechanisms, which looks like delegation in E.164 world ENUM enabled DNS provides a low cost, shared SCP-like infrastructure for IP infrastructure ENUM facilitates PSTN/IP convergence

18 18 ENUM 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 NAPTR algorithm

19 19 ENUM Step 1 Explanation Each digit becomes 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 nameservers for NAPTR/service resource records (RRs)

20 20 ENUM Step 2 Lookup NAPTR RRs in DNS, and apply NAPTR/ENUM algorithm !^+46(.*)$!ldap://\1! Use rewrite rules using regular expressions which operate on the E.164 number ( )

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

22 22 ENUM Step 2 in detail $ORIGIN IN NAPTR U mailto+E2U IN NAPTR U ldap+E2U !^+46(.*)$!ldap://\1 Note that no line break should be in the records

23 23 ENUM ENUM DNS Hierarchy Alternative 1Alternative 2


25 25 ENUM DNS Hierarchy Strictly delegated One authoritative server for each name, and only one Have led to the registry/registrar model One responsible registry, but many registrars which talk with customers

26 26 ENUM Registry/registrar Root server Server Verisign Global Registry Server NIC-SE AB Registrars Today 77 Registrar Network Solutions Registrar Active ISP Registrar interQ Incorporated Registrar Tele2 Registrars Today 227

27 27ENUM Conclusion 27ENUM

28 28 ENUM Call setup ENUM example flow/usage Sip Query Dial DNS-Server Sip proxy Response

29 29 ENUM ENUM and VoIP ENUM allows VoIP proxies and servers to find each other Intra and inter domain call setup Only for declaring ability to accept certain applications ENUM is an opt-in system (also on country code level)

30 30 ENUM ENUM in Universal Messaging IETF Voice Profile for Internet Mail ENUM enables carrier and enterprise voice mail systems to find each other, interoperate and exchange messages Linkage to directory gives access to spoken name as well as authenticated access to sensitive information (privacy)

31 31 ENUM ENUM in Internet Fax IETF RFC 2305 / ITU-T Rec. T.37 ENUM enables internet aware fax machines to find each other, interoperate and exchange messages

32 32 ENUM Detailed example of Fax Person X wants to send a fax to Person Y; she knows Y's E.164 number. Person Y has many IP applications tied to her own (Y's) E.164 number. Device C became responsible for delivering the fax. Device C is Internet Aware, is ENUM-enhanced, can do SMTP and SIP, but can't do H.323 yet. Device C does a DNS query on the E.164 number. Device C discovers from the response that Person Y prefers real-time to store-and-forward fax delivery, likes SIP and H.323 equally, and has SMTP, too. Device C tries SIP first. If SIP fails, Device C does not try H.323. Instead, Device C then tries SMTP. Note: Device C uses ENUM in its application selection logic. ENUM is an enabler and not the same sort of thing as SMTP, SIP, H.323, voice/fax/data, etc.

33 33 ENUM From RFC IANA Considerations This memo requests that the IANA delegate the E164.ARPA domain following instructions to be provided by the IAB. Names within this zone are to be delegated to parties according to the ITU recommendation E.164. The names allocated should be hierarchic in accordance with ITU Recommendation E.164, and the codes should assigned in accordance with that Recommendation. Delegations in the zone (not delegations in delegated domains of should be done after Expert Review, and the IESG will appoint a designated expert.

34 34 ENUM Status as of Jan 10, 2001 (done) Base spec published as RFC 2916 delegated to RIPE-NCC ITU SG2/WP1/2 liaison statement: Member state can inform ITU on entry of numbers in DNS, provision of E.164 information

35 35 ENUM Status as of Jan 10, 2001 (not done) Delegation of domains below to managing entities that are appointed by member states National issues

36 36 ENUM Resources NAPTR Resource Records (RFC 2915) ENUM Specification (RFC 2916) Liaison Statement (RFC 3026) IAB on need for unique root (RFC 2826) IAB Statement on ARPA domains.txt My address:

Download ppt "1ENUM ENUM Technical issues / DNS Patrik Fältström Area Director, Applications Area, IETF"

Similar presentations

Ads by Google