# Presentation: 683182

## 
IETF – ENUM
US Government Briefing

Richard Shockey
IETF ENUM Work Group Chair
Senior Technical Industry Liaison
NeuStar, Inc.
1120 Vermont Avenue N.W.
Washington DC, 20005
rich.shockey@neustar.com     202.533.2811

**IETF – ENUM**
**US Government Briefing**
**Richard Shockey**
**IETF ENUM Work Group Chair**
**Senior Technical Industry Liaison**
**NeuStar, Inc.**
**1120 Vermont Avenue N.W.**
**Washington DC, 20005**
**rich.shockey@neustar.com     202.533.2811**

## Who is NeuStar?

- North American Numbering Plan Administrator
- Manages all Telephone Numbers
- US Number Portability Administration
- Permits Telephone Numbers to be “ported” from one carrier to another.
- Number Pooling Administration in many states
- .BIZ TLD award winner at ICANN with Melbourne IT of Australia [ NeuLevel ]
- www.neustar.com

##  Problem Statement

- How do you find services on the Internet if you only have a telephone number [E.164]?
- Why ...Telephone Numbers are easy to use...
- Why ...Several billion devices have TN key pads.
- How can we enable new IP services while creating new competitive markets and protect consumer choice,etc?
- How can consumers and carriers have equal access to these new opportunities?
- How do we create a trusted TN based resource for information about those services?
- How do you make this simple, easy to use, without “reinventing the wheel”?

##  Solution  ENUM / DNS Directory Service

- Put telephone numbers into the global Domain Name System [DNS]
- ENUM WG formed and operates within in the Internet Engineering Task Force
- Core protocol work completed - RFC2916
- RFC2916 defines the use of DNS resource records  to find optional :
- E-mail addresses
- Voice over IP SIP / H.323 servers
- Voice Mail servers
- Fax Machines
- New and yet undefined services !

##  Why DNS?

- It’s there...
- It works... It’s global... It scales... It’s fast...  It’s open.
- ENUM enabled DNS creates a low cost, shared Service Control Point like infrastructure for IP services
- Goal – Telephone Number IN .... URL out
- Key to all TN related services offered by providers over IP
- ENUM is the tip of the PSTN – IP Convergence

##  How Does ENUM Work?

- Take a fully qualified E.164  telephone number and create a DNS entry in a _single_ highly defined and structured domain.
- The search for resources on the internet associated with   + 1 202-533-2811 becomes a DNS look up to: 1.1.8.2.3.3.5.2.0.2.1.e164.arpa
- The e164.arpa domain was selected by the Internet Architecture Board specifically for this purpose with the concurrence of the ITU
- Single domain structure under e164.arpa becomes the authoritative “root” for telephone numbers

## Simple ENUM Flow Chart

**SIP Proxies**

**ENUM Global Directory (DNS)**
**Equates 1(202) 533-2811 to sip:rich.shockey@carrier.net to enable Voice over IP using SIP **

**Proxy Queries DNS for SIP Address based on TN**

**Internet**

**DNS**

## What ENUM is not....

- ENUM is not about carrier selection (selection of carrier within a given service type)
- ENUM is not about telecom bypass
- An *alternative* to circuit switched technology
- ENUM does not change the Numbering Plan
- ENUM does not change ITU-E.164
- ENUM does not change telephony numbering or its assignments in anyway
- ENUM does not exhaust the NANP
- May conserve numbering resources
- ENUM is NOT about 911 services
- Opt-In system minimizes Privacy issues
- Consumer Name and Address not exposed to Net

##  How Does ENUM Work?

**Input:**
**  **$ORIGIN.**            1.1.8.2.3.3.5.2.0.2.1.**e164.arpa
**Output: NAPTR RR response**
**In this response the preferred contact method is SIP**
**                  **ord pr  fl      service                 re replacement
- IN NAPTR 10   10 "u" "sip+E2U"       "!^.*$!sip:rich.shockey@carrier.net!" .
- IN NAPTR 102 10 "u" "mailto+E2U"  "!^.*$!mailto:rich.shockey@neustar.com!" .
- IN NAPTR 102 10 "u" “fax-t37+E2U" "!^.*$!mailto:faxmachine4@neustar.com!" .
- IN NAPTR 102 10 "u" "tel+E2U“        "!^.*$!tel:+12025332811!" .
*Note: Consumers do not see this process !                            **	**ENUM protocol imbedded in devices and proxies.*

## ENUM DNS Hierarchy – A Model

- e164.arpa

- 1.e164.arpa

- 4.3. 2.1.3.3.5.2.0.2.1.
- e164.arpa->NAPTRs
- (ldap://ldap.z1.com)

-   PROXY OR DATABASE

- Based on country-code
- Delegated to nation-states

**...**

**...**

- Non-US NPAs

- US NPAs

**Tier 1**
**(One **
**Administrator per country)**

**Tier 2**
**(Designated by**
**the end user)**

- 4.3.2.1.3.3.5.2.0.2.1.
- e164.arpa->y1.com

**Tier 3**
**(Depending on**
**the service. SIP- **
**Voice Mail )**

**Tier 1 :Who is the subscriber designated authority for a given phone number? *****In the US this should resolve to the full 10 digits to satisfy portability concerns.***
**Tier 2: What services are available for a specific phone number. Use DNS resource records to provision services. RR’s can be hosted by service providers, enterprises or individuals.**

- RIPE CC – Based in Europe

## Applications

***Applications***

- Internet

- ENUM
- Directory

- Telephony
- Networks

_**Enabled Applications**_
-  Voice over IP
-  Unified Messaging
-  Instant Messaging
-  IP Fax
-  Personal Web Pages

_**E.164 Numbers**_
-  10 Digit
-  800
-  International
- Private Networks

_**Internet Domain Name Addresses**_

**DNS**

## Implementation Issues

- Protocol Work is done and approved as   IETF RFC 2916
- IETF – ITU Agree on delegation model - Liaison Statement issued by Study Group 2
- Nation State control by Country Code
- ITU will insure that Member States have authorized the inclusion of their Country Code in e164.arpa
- ITU to coordinate with RIPE NCC as the Root
- But  ITU is not in “Control” of e164.arpa
- IETF -  ITU jointly work together in moving forward
- How are the National Delegation Servers for each country to be managed?
-  Operational Requirements
-  Regulatory Requirements

## Next Steps...

- Industry Input needed from both Carriers and Vendor Community
- Technical
- Put ENUM capable DNS Resolver into Internet Telephony Products
- Create ENUM / DNS Operational Metrics
- Security - Redundancy
- Administrative
- Policy
- Operations
- Verifying the identity of the subscriber for ENUM services
- Validating ENUM data for potential users (E.164 number and list of services and preferences)
- Provisioning the data to the servers
- Telecom Industry Understands this class of resource

## Next Steps...

- Discussion today w/ U.S. Government representatives on how to move forward  .. Quickly
- US Government has sufficient authority to act
- Educational Process Ongoing
- Policy Option Development
- Existing Policy models in the PSTN offer guidance to :
- Promote Consistency with existing Number Plan and Portability requirements
- Prevent Number Slamming
- Prevent Number Hijacking
- Protect Consumers
- Equal Access to RR’s by all carriers and service providers
- International Regulators to be briefed
- This is not a US issue only
- Upcoming ITU Seminar Geneva Jan 18

## ENUM Resources

**ENUM Charter **
- http://www.ietf.org/html.charters/enum-charter.html
**ENUM Core Protocol  **
**ftp://ftp.isi.edu/in-notes/rfc2916.txt**
**ENUM  WG Requirements **
- http://www.ietf.org/internet-drafts/draft-ietf-enum-rqmts-01.txt
**ENUM Call Flows**
- http://www.ietf.org/internet-drafts/draft-lind-enum-callflows-01.txt
**ENUM Operations Issues**
- http://www.ietf.org/internet-drafts/draft-ietf-enum-operation-01.txt
**ENUM Administration in the United States**
**http://www.ietf.org/internet-drafts/draft-pfautz-yu-enum-adm-00.txt**
**Voice Profile for Internet Mail**
- ftp://ftp.isi.edu/in-notes/rfc2421.txt

## ENUM Resources

**IETF-ITU Liaison Statement**
**http://www.ietf.org/internet-drafts/draft-itu-sg2-liason-enum-01.txt**
**NAPTR Resource Records**
**ftp://ftp.isi.edu/in-notes/rfc2915.txt**
**A DDDS Database Using The Domain Name System**
- http://www.ietf.org/internet-drafts/ draft-ietf-urn-dns-ddds-database-01.txt
**Dynamic Delegation Discovery System (DDDS)**
- http://www.ietf.org/internet-drafts/ draft-ietf-urn-ddds-02.txt
**URI Resolution using the Dynamic Delegation Discovery System**
- http://www.ietf.org/internet-drafts/ draft-ietf-urn-uri-res-ddds-01.txt

## NeuStar view..

- ENUM _IS_ Convergence
- 	Will increase competition in telecom markets
-   “Great leap” for convergence
- ENUM fulfills the potential of IP networks
- NeuStar and the industry can begin a trials anytime
- ENUM must have a single, “golden” database for the U.S.
- DNS permits only one “authoritative” root
- one administrator at first level
- unlimited databases at lower, applications level

## NeuStar view....

- U.S. Government should internally decide on a contracting agency and submit an RFP for ENUM Administration in the US as soon as practical in free, fair and open competitive process
- Commercial Companies w/ capital resources
- Goals for Administration
- Promote U.S. Commercial interests
- Continue U.S. Internet Leadership
- Protection of Consumer interests
- System must be designed to assure security consumer choice
- Well-designed system can protect against hijacking, slamming and cramming, minimizing regulatory involvement
- Equal access provisions for multiple third party service creation