1 / 19

ENUM?

ENUM?. “.

ulani
Download Presentation

ENUM?

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. ENUM? “ Telephone Number Mapping (ENUM or Enum, from TElephone NUmber Mapping) is a suite of protocols to unify the telephone numbering system E.164 with the Internet addressing system DNS by using an indirect lookup method, to obtain NAPTR records. The records are stored at a DNS database. ”

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

  3. 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?

  4. 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?

  5. Today, Many Addresses tel:+46-8-971234 mailto:paf@example.com tel:+46-706051234 sip:paf@example.com

  6. With ENUM, Only One tel:+46-8-971234 mailto:paf@example.com ENUM tel:+46-706051234 tel:+46-706051234 sip:paf@example.com Give this number to friends: +46-8-971234

  7. Solution in short • Put domain names derived from telephone numbers in the global domainname 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 URI’s for the communication

  8. NAPTR NAPTR stands for Naming Authority Pointer and is a newer type of DNS record that supports regular expression based rewriting. Several NAPTR records can be chained together creating fairly sophisticated URL rewriting rules. A record can go through any number of rewrites before reaching a terminal condition. • take phone number +46-8-6859131 • turn into domain name 1.3.1.9.5.8.6.8.6.4.e164.arpa. • ask the DNS mailto:paf@cisco.com • return list of URI’s sip:paf@cisco.com

  9. Network

  10. ENUMEnabledApplications Provisioning DomainNameSystem Authentication &ValidationEntities Tier 0 Registrar Registry Tier 1 • voice • fax • messaging & presence • email • web pages ApplicationServiceProvider Tier 2

  11. The Public ENUM Infrastructure UK_enum.com (4.4.e164.arpa) nsnanp.enum.com (3.7.9.1.e164.arpa) e164.att.net e164.arpa Tier 0 (Country Code Registry) $ORIGIN e164.arpa. 3.7.9.1 IN NS nsnanp.enum.com . 4.4 IN NS UK_enum.com . … … Tier 1 (Telephone Number Registry) $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) $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)

  12. Delegation of Country Codein Tier 0 • Draft Recommendation E.A-ENUM in progress • Interim Procedures in place between IAB/ISOC and ITU-TSB • Use of e164.arpa pending outcome of Recommendation • Country Code must be valid and assigned • Position of National Numbering Administrator must be known and must opt-in • Similar situation for shared Network codes and codes for Groups of Countries (e.g., ETNS)

  13. Requirements Document • Reference Architecture • Tier 1 Registry Operations, Security, & Admin • Tier 1 Performance Specifications • Privacy Considerations • Provisioning • Registrar Requirements • Authentication & Authorization • Tier 2 Requirements & Guidelines • Conflict Resolution • Issues Out of Scope

  14. Reference Architecture Root Tier 0 Tier 1 Registry Registrant Registrar Tier 2 Provider

  15. Reference Architecture • Registrar • Registrant • Tier 1 Registry • Does not address non geographic numbers • Tier 2 Service Provider • Tier 2 contains the NAPTR records or delegations • Interfaces • Issue: • One or More Tier 1 Providers • Delegation at Tier 0 by NPA

  16. Tier 1 Aspects • Tier 1 Operations • Zone Information (aka zone files) • ContactInfo (aka WhoIs) • Reporting, backup, escrow & performance requirements • Performance Aspects • DNS Performance • EPP Interfaces • Tier 1 Security • Administrative Aspects • Dispute Resolution • Data Collection and Privacy

  17. Provisioning Authentication & Validation Entities Tier 1 Registry Registrant Registrar Tier 2 Nameserver Application Service Provider

  18. Provisioning Aspects • Registrar Requirements • Registrant Validation & Authentication • Dispute Resolution • Registrar Infrastructure Requirements • Recommended Practices & Requirements • Various Scenarios • Information Flows • Tier 2 • Mostly Guidelines – Some Requirements • Tier 2 may be self-provided or from a commercial 3rd party • Interfaces & Interactions • Performance Recommendations

  19. Future Actions • Address implementation issues • Contracting model • Integration/separation of North American countries • Number of Tier 1 operators • Address Non-geographic numbers (specifically 8YY Toll Free) • Can’t be cleanly separated by North American country • Has unique provisioning requirements

More Related