1 / 14

ENUM in the U.S. Ken Hansen & James Yu NeuStar, Inc. February 24, 2003

ENUM in the U.S. Ken Hansen & James Yu NeuStar, Inc. February 24, 2003. ENUM is a scheme that put telephone number into the Domain Name System (DNS) in a single “golden tree” domain so that resources or end point addresses associated with that telephone number can be resolved in the IP domain.

hollye
Download Presentation

ENUM in the U.S. Ken Hansen & James Yu NeuStar, Inc. February 24, 2003

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 in the U.S. Ken Hansen & James Yu NeuStar, Inc. February 24, 2003

  2. ENUM is a scheme that put telephone number into the Domain Name System (DNS) in a single “golden tree” domain so that resources or end point addresses associated with that telephone number can be resolved in the IP domain What is ENUM?

  3. Simple ENUM Call Flow SIP ENUM Global Directory (DNS) Equates +1-202-555-1234 to sip:mark@carrier.net to enable Voice over IP using SIP 3. DNS returns NAPTR record containing SIP URL to Calling Party UA 2. Calling party proxy UAC queries DNS for location of end point 1. The caller simply dials the person’s normal telephone number 4. Calling party UA connects the call

  4. U.S. ENUM Forum Structure ENUM Forum Leadership Team Task Groups Special Groups - Applications - Architecture & Infrastructure - Interoperability - Privacy & Security - Provisioning - External Communications - Legal Experts

  5. What Has Happened in the U.S. -ENUM Forum • Specification approved on 2/11 http://www.enum-forum.org/documents/6000_0_9 Letter ballot comments to be resolved • Issues not addressed in the specification: • Non-geographic numbers (e.g., toll free numbers) • Non-US 1+NPA codes • Registrar accreditation • Single vs. multiple Tier 1 Registries • On 2/13/03, ENUM Forum members met with NTIA, FCC and FTC to discuss next steps • Plan to work on non-geographic numbers next

  6. ENUM Forum Specification Covers • Reference architecture • Tier 1 Registry requirements • ENUM Registrar requirements • Tier 2 Provider guidelines • Provisioning scenarios and procedures • Authentication & authorization • Privacy considerations • Dispute resolution

  7. What Has Happened in the U.S. -US Government • In 9/01 ITU-T SG2 meeting, U.S. expressed its support for ITU-T’s work on RFC2916, which designate e164.arpa • In 8/02, NTIA held a forum on ENUM benefits and challenges • In 2/03, NTIA pledged active U.S. government participation in the global ENUM effort • Internationally - formally opt in to e164.arpa after addressing certain key preliminary issues regarding US implementation of ENUM • Domestically - ensure that ENUM can be implemented in a pro-consumer, secure and competitive manner NTIA is to lead the ENUM effort within the US government

  8. US Government Principles on ENUM • Preserve national sovereignty on ENUM implementation • Support competition among all players • Promote innovation on advanced services • Protect users’ security and privacy • Minimize regulation for a global ENUM approach • Preserve opportunity for alternative deployments • Allow for interoperability with alternative deployments • Preserve stability and security of Internet and telecommunications systems

  9. US Government Agencies That May Be Involved in Joint ENUM Effort • National Telecommunications & Information Administration (NTIA) • Federal Communications Commission (FCC) • Federal Trade Commission (FTC) • Department of State • Department of Justice • Department of Homeland Security It involves numbering, Internet, security and privacy!

  10. Reference Model for End User ENUM Provisioning in the U.S. Tier 1 Registry Application Service Provider Enum Registrar Tier 2 Provider ENUM Registrant or Broker/Agent

  11. ENUM vs. Existing DNS ENUM is not much different from the existing DNS process except the following: • ENUM Registrar must validate ENUM Registrant’s identity and that he/she is indeed the current TN assignee • Tier 1 Registry, ENUM Registrar and Tier 2 Provider must automatically handle number changes (e.g., area code split, code expansion) • ENUM Registrant’s right to use an ENUM domain name is tied to if he/she owns/controls the TN • No IPR issue; dispute resolution is simpler • TN disconnect means no ENUM service on that TN

  12. Benefits of ENUM for Communities of Interest : The Corporate 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

  13. ENUM Enterprise Architecture Model #1 Enterprise IP PBX to Enterprise IP PBX ENUM Query by PBX or Edge Proxy ENUM IP Enhanced PBX IP Enhanced PBX Internet Enterprise Domain Boundary

  14. Questions? ken.hansen@neustar.biz james.yu@neustar.biz

More Related