1 / 8

ENUM Ad Hoc Meeting Douglas Ranalli Founder, Chief Strategy Officer dranalli@netnumber

ENUM Ad Hoc Meeting Douglas Ranalli Founder, Chief Strategy Officer dranalli@netnumber.com February 12, 2001. History. June 1997 : Unifi directory services program. 1998 – 1999 : Early work with voice messaging EMA and VMA joint initiative. Lucent, Nortel, Comverse, Siemens, Unisys, etc.

kairos
Télécharger la présentation

ENUM Ad Hoc Meeting Douglas Ranalli Founder, Chief Strategy Officer dranalli@netnumber

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 Ad Hoc Meeting Douglas Ranalli Founder, Chief Strategy Officer dranalli@netnumber.com February 12, 2001

  2. History • June 1997: Unifi directory services program. • 1998 – 1999: Early work with voice messaging • EMA and VMA joint initiative. • Lucent, Nortel, Comverse, Siemens, Unisys, etc. • October 1999: NetNumber stand-alone • Raised $9.5 million VC funding. • May 2000: First production release • November 2000: ENUM compliant

  3. Current View • Pro competition – not against “e164.arpa”. • Clear value in ENUM as a technical standard. • Not convinced that an “exclusive” “e164.arpa” implementation is a winner for the industry. • NetNumber’s focus is on the adoption of ENUM in the market. • ENUM service provider.

  4. ENUM Challenges • Tier-1 Challenge: • “e164.arpa” is a distributed solution • Administration by every ITU Member State • No guarantee of efficient deployment • Tier-2 Challenge: • Tier-1 points to a single Tier-2 • No guarantee that an exclusive Tier-2 provider will provide access to NAPTR records.

  5. “e164.arpa” Market Risks • Time to market • How long will “e164.arpa” take to evolve? • Participation consistency • Will “e164.arpa” yield a global solution? • Policy consistency • Who gets to run Tier-2 under “e164.arpa”? • Will every country agree on a competitive structure? • Pricing consistency • Will pricing promote the growth of ENUM? • Will many small providers be efficient?

  6. Competitive Alternative Embrace three types of ENUM services • Private ENUM “e164.company.com” • Commercial ENUM “e164.com” • Public ENUM “e164.arpa” • ENUM Resolver isolates application. • Customer defines set of domains to query • Resolver returns full set of addresses. • Common Requirement • Validation of subscriber intent

  7. Will Competition Help? • Time to market • How long will “e164.arpa” take to evolve? • Participation consistency • Will “e164.arpa” yield a global solution? • Policy consistency • Will every country agree on a competitive structure? • Pricing consistency • Will pricing promote the growth of ENUM?

  8. Conclusion • Embrace competitive environment • Participate in “e164.arpa” if consistent with US policy. • Explore regulatory environment in US around “ENUM validation”.

More Related