8
ENUM Ad Hoc Meeting Douglas Ranalli Founder, Chief Strategy Officer [email protected] February 12, 2001

ENUM Ad Hoc Meeting Douglas Ranalli Founder, Chief Strategy Officer [email protected] February 12, 2001

Embed Size (px)

Citation preview

Page 1: ENUM Ad Hoc Meeting Douglas Ranalli Founder, Chief Strategy Officer dranalli@netnumber.com February 12, 2001

ENUM Ad Hoc Meeting

Douglas Ranalli

Founder, Chief Strategy Officer

[email protected]

February 12, 2001

Page 2: ENUM Ad Hoc Meeting Douglas Ranalli Founder, Chief Strategy Officer dranalli@netnumber.com February 12, 2001

HistoryHistory

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

Page 3: ENUM Ad Hoc Meeting Douglas Ranalli Founder, Chief Strategy Officer dranalli@netnumber.com February 12, 2001

Current ViewCurrent 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.

Page 4: ENUM Ad Hoc Meeting Douglas Ranalli Founder, Chief Strategy Officer dranalli@netnumber.com February 12, 2001

ENUM ChallengesENUM 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.

Page 5: ENUM Ad Hoc Meeting Douglas Ranalli Founder, Chief Strategy Officer dranalli@netnumber.com February 12, 2001

““e164.arpa” Market Riskse164.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?

Page 6: ENUM Ad Hoc Meeting Douglas Ranalli Founder, Chief Strategy Officer dranalli@netnumber.com February 12, 2001

Competitive AlternativeCompetitive 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

Page 7: ENUM Ad Hoc Meeting Douglas Ranalli Founder, Chief Strategy Officer dranalli@netnumber.com February 12, 2001

Will Competition Help?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?

Page 8: ENUM Ad Hoc Meeting Douglas Ranalli Founder, Chief Strategy Officer dranalli@netnumber.com February 12, 2001

ConclusionConclusion

Embrace competitive environment

Participate in “e164.arpa” if consistent with US policy.

Explore regulatory environment in US around “ENUM validation”.