Tekelecs opinion on Change orders NANC 400 and NANC 401 ENUM.

Slides:



Advertisements
Similar presentations
© ag-projects.com NAPTR Record Manipulation.
Advertisements

AG Projects Miami - June 2005 ENUM Tier 2 Provisioning techniques Linking ENUM with external systems Adrian Georgescu AG Projects.
AG Projects ENUM provisioning - Jan 2006 Telecom Signaling Networks and Service Forum January 18, 2006 Amsterdam.
AG Projects RIPE 51 - October 2005 ENUM provisioning techniques Adrian Georgescu AG Projects.
ENUM Overview – July The ENUM Objective Mapping PSTN addresses into the IP world ENUM allow any IP device to establish whether an E.164 telephone.
Implications of ENUM Geoff Huston Office of the CTO September 2002.
CC1 ENUM LLC Presentation to the NANC March 15, 2005 Karen Mulberry Chairman
1 Number Portability Administration Center Change Orders NANC 399 & NANC 400 NANC Meeting March 15, 2005 Tom McGarry NeuStar, Inc.
NAPM LLC MEMBERSHIP INTRODUCTION
VoIP and Number Portability: Perceived v. Real Problems Tom Kershaw Vice President, VoIP VeriSign.
NANC Change Order 400 Joint FoN/LNPA WG Meeting April 14, 2005 Tom McGarry NeuStar, Inc.
Enum is a Domain Name Tom McGarry NeuStar
NANC Future of Numbering (FoN) Working Group July 18, 2006 Co-Chairs James Castagna, Verizon John Cummings, Vonage Don Gray, Nebraska PSC.
International Telecommunication Union ENUM Issues and Solutions Houlin Zhao Director Telecommunication Standardization Bureau International Telecommunication.
2001_03_28 SG A contribution– 1 Dept of State ITAC-T Advisory Committee SG-A Ad Hoc Meeting on ENUM March 28th & 29th, 2001 ENUM CONTRIBUTION TITLE: ENUM.
SG-A Ad Hoc - ENUM Jordyn A. Buchanan Register.com February 12, 2001.
2/12/2001 ENUM Administration Penn Pfautz AT&T
ENUM Ad Hoc Meeting Douglas Ranalli Founder, Chief Strategy Officer February 12, 2001.
Support and Transparent Process for ENUM Designated Zone implementations for the USA Before the Dept of State ITAC-T Advisory Committee SG-A AdHoc Meeting.
ENUM Administration Issues
Number Portability Impacts on IP & Telecoms Interworking James Yu NeuStar, Inc.
North American Numbering Council (NANC) - J. Scott MarcusSlide 1December 4, 2004 Technology, the Internet and the Demand for NANP Numbers J. Scott Marcus.
Slide title In CAPITALS 50 pt Slide subtitle 32 pt Infrastructure ENUM David Seaton Director Product Marketing Ericsson.
1 IP Telephony (VoIP) CSI4118 Fall Introduction (1) A recent application of Internet technology – Voice over IP (VoIP): Transmission of voice.
Saif Bin Ghelaita Director of Technologies & Standards TRA UAE
ENUM - The UK experience so far Tony Holmes BT Chairman of UK ENUM Group NICC Open Forum 2003.
1 Copyright © 2012 Telcordia Technologies, Inc All Rights Reserved Telcordia IP Interconnection ENUM Registry Solution John P. Malyar Chief Architect Adam.
THIS IS THE WAY ENUM Variants Jim McEachern Carrier VoIP Standards Strategy THIS IS.
North American Portability Management LLC 1 NAPM LLC MEMBERSHIP INTRODUCTION.
Carrier/Infrastructure ENUM Requirements draft-lind-infrastructure-enum-reqs-01.
© 2004 AT&T, All Rights Reserved. The world’s networking company SM An Evolution Path for Numbering and Interconnection Future Of Numbering Symposium November.
International Telecommunication Union ITU Perspective on ENUM Robert Shaw ITU Internet Strategy and Policy Advisor ICANN Rio de Janeiro, Brazil March 25,
ENUM Chris Wong Converging Services Branch International Training Program 7 September 2006.
August 13-14, 2002 Washington, DC Gary Richenaker Chair ENUM Forum
Understanding ENUM & Current Status Network Planning August 21, 2001
ENUM Primer November 4, 2004 Tom McGarry - NeuStar
1 IETF – ENUM US Government Briefing Richard Shockey IETF ENUM Work Group Chair Senior Technical Industry Liaison NeuStar, Inc Vermont Avenue N.W.
© 2008 AT&T Knowledge Ventures. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Knowledge Ventures. 1 Video Relay Service and Assignment.
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.
February 25, Infrastructure-ENUM Secure, Private, Next Generation Addressing Infrastructure Douglas J. Ranalli Founder, Chief Strategy Officer NetNumber,
1 NGN Issues - Numbering and Addressing Peter Darling ACIF NGN FOG No. 3.
AG ProjectsDenic ENUM day Number portability Using ENUM and SIP Adrian Georgescu AG Projects
ENUM Update for voipeer BOF Richard Shockey ENUM co-chair IETF 63 Paris.
Industry Canada 1 Bob Leafloor Colman Ho Peter Chau Industry Canada January 2003 (ENUM) T E lephone NU mber M apping.
© Copyright 2007 Arbinet-thexchange, Inc. All Rights Reserved. Voice Peering Steve Heap Chief Technology Officer.
Slide 1 Nicklas Beijar - TRIP, ENUM and Number Portability TRIP, ENUM and Number Portability Nicklas Beijar
© Copyright 2007 Arbinet-thexchange, Inc. All Rights Reserved. VoIP Peering Pilot Using the Internet2 Backbone.
ENUM Services and their Provisioning Submitted by VeriSign, Inc and Telcordia Technologies, Inc Available at
© 2004 AT&T, All Rights Reserved. The world’s networking company SM VoIP, Portability, and the Evolution of Addressing LNPA & Future of Numbering Working.
1 ENUM’s Role in VoIP IP Telephony Conference & Expo Miami February 12, 2004 Sheri Jenkinson VeriSign Communication Services Product Manager - ENUM
1 Barriers to Enum What VoIP providers ask about Enum Dr. Dorgham Sisalem.
IP Network Clearinghouse Solutions ENUM IP-Enabling The Global Telephone Directory Frank Estes Vice President , ext 224
AG ProjectsVON Boston - Fall 2005 Number portability Using ENUM and SIP Adrian Georgescu AG Projects
Slide 1 Nicklas Beijar - TRIP, ENUM and Number Portability TRIP, ENUM and Number Portability Nicklas Beijar
1 Industry Numbering Committee (INC) Report to the NANC Natalie McNamer, INC Chair Dana Crandall, INC Vice Chair February 21, 2013.
Patrik Fältström. ITU Tutorial Workshop on ENUM. Feb 8, 2002, Geneva Explanation of ENUM (RFC 2916) Patrik Fältström Area Director, Applications Area,
Page 1IETF 63 ENUM WG IETF 63 – ENUM WG IANA Registration for an Enumservice Containing Number Portability and PSTN Signaling Information 5 August 2005.
International Telecommunication Union ENUM Organizational Perspectives Richard Hill, for Houlin Zhao Director Telecommunication Standardization Bureau.
1 Introduction to ENUM Technical and operational aspects Marco Bernardi NeuStar, Inc
ENUM Tutorial ENUM Forum June 3, 2003 Steven D. Lind, AT&T GEN0075R0.
18 January 2006 Copenhagen ERO - TISPAN WG4 meeting
Carrier/Infrastructure ENUM Requirements draft-lind-infrastructure-enum-reqs-01.
Using NPAC as the ENUM Registry
Technical and Operational Aspects
Default cover design. Current Routing Solutions supporting the Interconnection of Carrier IP –based Multimedia Services in North America IPNNI
SIR Basics – 1 Shared Registration System (SRS)
Implementation of ENUM on telecommunication networks
Routing Considerations
Industry Numbering Committee (INC) Report to the NANC
Presentation transcript:

Tekelecs opinion on Change orders NANC 400 and NANC 401 ENUM

Tekelec Proprietary 05 | 2 Phone Number Carrier Database Query Response LNP Compared to ENUM (High level) Problem Statement is the same LNP resolves a Phone Number to LRN (carrier) in the PSTN Tier I Public ENUM resolves a phone number to a Name Server (e.g. carrier) in 3G Tier II Public ENUM provides the device the subscriber wants to be contacted on Tier I Private ENUM can resolve a phone number to a non e164.arpa carrier domain (e.g. NANC 400,401) Tier I Private ENUM should be competitive (Who owns the phone number?)

Tekelec Proprietary 05 | 3 Tekelec Issues with NANC 400 and 401 DPC/SSN is not analogous to URI Is an IP address analogous to a telephone number, really? DPC/SSN was implemented in NPAC for SMS portability Most Carriers do not use SS7 to deliver inter-carrier SMS. ENUM data and LNP data used by separate applications Why tie provisioning of future application to existing CMIP interface? Unnecessarily increases complexity of performance analysis and data modifications

Tekelec Proprietary 05 | 4 Tekelec Issues with NANC 400 and 401 ENUM data being placed in a government mandated system controlled by a monopoly Contradicts ENUM LLC and Forum drivers for Tier I ENUM Understand that NeuStar may be providing a private ENUM service today for inter-carrier MMS – how does this relate? Large impact on existing LNP architecture If NANC 400 passes, Tekelec will adjust as necessary but industry must then not retract approval. Competitive benefit for Tekelec given LNP footprint

Tekelec Proprietary 05 | 5 Backup

Tekelec Proprietary 05 | 6 LNP Compared to ENUM (Details) ENUM actually works very differently than LNP Call processing LNP is SS7 based Query/Response NPAC is not in the call path ENUM is DNS based Query/Response Tier I ENUM is in the call path Provisioning: The NPAC provisions routing information into service providers routing DBs. Carriers use that routing information within their own networks to route calls and SS7 messages ENUM provisions a DNS server, called Tier 1. Users (e.g., carriers) query that DNS server which points them to another server, called Tier II, to retrieve the routing data

Tekelec Proprietary 05 | 7 LNP Compared to ENUM (Details) Control over ENUM is very different than LNP Entities Involved in the Service NPAC - the NPAC, the LLC and the NPAC Users ENUM – consumers (i.e., registrants), registrars, ENUM LLC, Tier 1 providers, Tier II providers, application service providers, etc. Regulatory Oversight: The FCC has oversight of NP ENUM receives oversight from the DoC, FCC, State Dept., FTC, and ITU-T. The IAB and the 18 other countries within CC1 provide policy-related input. Access to Data : NP data is only available to NPAC Users ENUM, like the DNS, is potentially a public resource (anyone can query)

Tekelec Proprietary 05 | 8 There are no mechanisms within ENUM to account for LNP There is no concept of a service provider/SPID (i.e., carrier) in public ENUM, only registrars and registrants The public ENUM record could be changed at either Tier 1 or Tier 2 to reflect the change in carrier Any changes in an public ENUM record requires the approval (opt-in) of the consumer (registrant) Its possible that a carrier could port a number but would be unable to modify public ENUM records Its possible that a consumer would not allow the carrier to change their public ENUM record LNP – ENUM Interaction (Details)