1January 2006Richard Stastny Developments around Infrastucture ENUM and their relevance on NGNs Workshop on NGN Interconnection and Numbering TRIS – TISPAN.

Slides:



Advertisements
Similar presentations
Slide title In CAPITALS 50 pt Slide subtitle 32 pt Infrastructure ENUM David Seaton Director Product Marketing Ericsson.
Advertisements

THIS IS THE WAY ENUM Variants Jim McEachern Carrier VoIP Standards Strategy THIS IS.
August 2005IETF 63 VOIPEER1 Issues in Numbering, Naming and Addressing voipeer BoF IETF 63 – Paris, August 2005 Richard Stastny ÖFEG.
Carrier/Infrastructure ENUM Requirements draft-lind-infrastructure-enum-reqs-01.
1October 2004Richard Stastny Introduction to ENUM Domain Pulse Vienna, February 4th, 2005 Richard Stastny, ÖFEG* * The opinions expressed here may or may.
UK ENUM Jay Daley, Nominet UK. ENUM explained Nominet and ENUM.
Numbering for VoIP and other IP Communications draft-stastny-enum-numbering-voip-00 IETF #58 Minneapolis, MN.
ENUM Chris Wong Converging Services Branch International Training Program 7 September 2006.
A Gateway For SIP Event Interworking - Sasu Tarkoma & Thalainayar Balasubramanian Ramya.
IETF 63 - Paris VOIPPEER BoF A Broadband Service Provider’s Perspective on VoIP Peering August 5, 2005 Presented by Jason Livingood.
C1 - UNCLASSIFIED V1.0 R&D 1Vodafone Group PLC27-28 July 2010 Challenges related to SIP session peering - an operator perspective Nick Russell Vodafone.
Ernst Langmantel Technical Director, Austrian Regulatory Authority for Broadcasting and Telecommunication (RTR GmbH) The opinions expressed in this presentation.
Document IPW-41 IP and Telecoms Interworking Workshop N umbering, Naming Addressing and Routing IETF EMUM WG Proposal International Telecommunication Union.
ENUM Overview Richard Shockey IETF ENUM WG Co-Chair Director – Member of Technical Staff NeuStar, Inc Center Oak Plaza Sterling VA USA
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.
The Austrian ENUM Trial is closing down 59 th IETF Seoul, South Korea, March 3 rd, 2004 Richard STASTNY ÖFEG, Postbox 147, 1103-Vienna enum:
1 NGN Issues - Numbering and Addressing Peter Darling ACIF NGN FOG No. 3.
PSTN – User ENUM – „Infrastructure ENUM“ An ETSI View Richard Stastny IETF60 San Diego.
AG ProjectsDenic ENUM day Number portability Using ENUM and SIP Adrian Georgescu AG Projects
RIPE64 Enum Working Group DE-CIX NGN Services.
VoIP and ENUM The Austrian Trial IETF #57 Vienna July 2003 Richard STASTNY ÖFEG/TELEKOM AUSTRIA, Postbox 147, 1103-Vienna enum:
ENUM Update for voipeer BOF Richard Shockey ENUM co-chair IETF 63 Paris.
12 January 2006 CDG Conference Call Integrating Existing Number Portability Solutions in Carrier-ENUM Douglas Ranalli, NetNumber, Inc.
Benefits of VoIP Peering in a Challenging Economy (SP-10) Tuesday - 02/03/09 4:00-4:45pm Mark Benisz, VP Americas, XConnect Global Networks.
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
Session Initiation Protocol (SIP). What is SIP? An application-layer protocol A control (signaling) protocol.
© Copyright 2007 Arbinet-thexchange, Inc. All Rights Reserved. VoIP Peering Pilot Using the Internet2 Backbone.
©Stephen Kingham SIP Peering SIP Workshop APAN Taipei Taiwan 23rd Aug 2005 By Stephen Kingham
© 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 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
1October 2005Richard Stastny ENUM Linking the VoIP Islands together The Future of VoIP ISOC.nl and AG Next Den Haag, 14. October 2005 Richard Stastny,
CP-a Emergency call stage 2 requirements - A presentation of the requirements from 3GPP TS Keith Drage.
Peering Considerations for Directory Assistance and Operator Services - John Haluska Telcordia SPEERMINT, IETF 68 Prague, Czech Republic 20 March 2007.
DNS SRV and NAPTR Use for SPEERMINT - Tom Creighton, Gaurav Khandpur Comcast SPEERMINT Intermin Meeting Philadelphia Sept
The State of VoIP Peering Charles Studt Director of Product Management, VoEX.
7/6/20061 Speermint Use Case for Cable IETF 66 Yiu L. Lee JULY 2006.
1 SPEERMINT Use Cases for Cable IETF 66 Montreal 11 JULY 2006 Presented by Yiu L. Lee.
Omar A. Abouabdalla Network Research Group (USM) SIP – Functionality and Structure of the Protocol SIP – Functionality and Structure of the Protocol By.
Intelligent Interconnects in the VoIP Peering Environment
Slide 1 Nicklas Beijar - TRIP, ENUM and Number Portability TRIP, ENUM and Number Portability Nicklas Beijar
Peering: A Minimalist Approach Rohan Mahy IETF 66 — Speermint WG.
Requirements for SIP-based VoIP Interconnection (BCP) draft-natale-sip-voip-requirements-00.txt Bob Natale For Consideration by the.
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.
Page 1 IETF Speermint Working Group Speermint Requirements/Guidelines for SIP session peering draft-ietf-speermint-requirements-02 IETF 69 - Monday July.
1 VoIP Peering Peering, it’s not just for IP anymore Kingsley Hill XConnect Global Networks, Ltd VP for Strategic Federations.
Session Peering Use Cases for Federations David Schwartz – Kayote Networks Eli Katz - XConnect Jeremy Barkan - Digitalshtick draft-schwartz-speermint-use-cases-federations-00.txt.
VoIP and ENUM Short Introduction AK-TK Workshop ÖFEG, March 11th, 2004 Richard STASTNY ÖFEG, Postbox 147, 1103-Vienna tel:
ENUM WG mini-BOF Setting the Stage Richard Shockey IETF 60 San Diego.
Enumservice VOID draft-stastny-enum-void-00 Richard Stastny Lawrence Conroy IETF60 San Diego.
IETF-62 draft-johnston-enum-conf-service-00 1 IANA Registration for ENUMservices ‘conf-web’ and ‘conf-uri’ Alan Johnston.
S. Ali, K. Cartwright, D. Guyton, A. Mayrhofer, J-F. Mulé Data for Reachability of Inter/tra-NetworK SIP (drinks) DRINKS WG draft-mule-drinks-proto-02.
Page 1 IETF DRINKS Working Group Data Model and Protocol Requirements for DRINKS IETF 72 - Thursday July Tom Creighton -
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.
Numbering and Interconnection Options
IP Telephony (VoIP).
THIS IS THE WAY ENUM Variants Jim McEachern
Using NPAC as the ENUM Registry
Default cover design. Current Routing Solutions supporting the Interconnection of Carrier IP –based Multimedia Services in North America IPNNI
The Domain Policy DDDS Application
Jean-François Mulé CableLabs
Implementation of ENUM on telecommunication networks
August 5, 2005 Presented by Jason Livingood
Agenda Overview Extending the Reach of VoIP Application Examples Standards and Other Resources Summary.
ENUM successes – failures - alternatives
Presentation transcript:

1January 2006Richard Stastny Developments around Infrastucture ENUM and their relevance on NGNs Workshop on NGN Interconnection and Numbering TRIS – TISPAN WG4 Copenhagen, 18. January 2006 Richard Stastny, ÖFEG* * The opinions expressed here may or may not be that of my company

January 2006Richard Stastny2 Content NGN/IP Interconnect – VoIP Peering –Some definitions What is ENUM? What kind of ENUM? –Infrastructure ENUM Recent IETF developments –ENUM WG –SPEERMINT WG Benefits in a nutshell

January 2006Richard Stastny3 Definitions What are NGNs? –IP-based “networks” –“Service provider” “networks” offering real-time or near realtime IP communications –“Enterprise networks” –etc. –  Administrative Domains What is Interconnection between NGNs? –a user registered in one administrative domain is able to contact (establish a session to) an user registered in a different administrative domain by using a Public User Identity (Address-of-Record, E.164 Number) –preferably via IP

January 2006Richard Stastny4 NGN/IP Interconnect (VoIP Peering) If we take the All-IP paradigm seriously, we have two basic requirements: –Any real-time communication originating on IP and terminating on IP MUST stay on IP end-to-end –This implies, it MUST NOT use the PSTN/ISDN to interconnect. Benefits are: –improved end-to-end functionality (BB codecs, IM, video, conferencing, presence, …) –Improved end-to-end QoS –No additional cost beside of IP-access –convergence possible at the end-user’s device

January 2006Richard Stastny5 Example IMS (TS ) Public User Identities –something one may put on a business card  a SIP URI or a TEL URI (in E.164 format) Routing* within IMS shall use SIP URIs –(converted via DNS to IP addresses – RFC3263) –TEL URIs will require conversion to SIP URIs (via ENUM)  Interconnection between IMS must be possible by using SIP URIs only * Routing = finding the next hop

January 2006Richard Stastny6 Possible Public User Identities E.164 numbers SIP URIs defined by provider: SIP URIs with self-provided domains:

January 2006Richard Stastny7 Electronic or E.164 NUMber mapping is defined by the Internet Engineering Task Force (IETF) in RFC3761 as: the mapping of „Telephone Numbers“ to Uniform Resource Identifiers (URIs) using the Domain Name System (DNS) in the domain e164.arpa –URIs are used to identify resources on the Internet (e.g. ) The purpose of ENUM is to enable the convergence between the PSTN and the Internet ENUM is defined by the IETF

January 2006Richard Stastny8 ENUM in a nutshell take an E.164 phone number turn it into a FQDN e164.arpa. returns list of URIs query the DNS (for NAPTR) sms tel: IN NAPTR "u" “E2U+sip“

January 2006Richard Stastny9 The basic idea of ENUM (RFC3671) The basic idea of ENUM was –to allow end-users –to opt-in with their EXISTING phone- numbers on the PSTN –into e164.arpa –to provide OTHER end-users with the capability –to look up contact URIs on the Internet the above end-user wants to link to this number This kind of ENUM is called User ENUM

January 2006Richard Stastny10 SIP Session establishment SIP server SIP server session DNS SRV lookup providerB.net IP –based network If this does not work, forget ENUM DNS

January 2006Richard Stastny11

January 2006Richard Stastny12 E.164 Session establishment SIP server SIP server tel: session DNS SRV lookup providerB.net DNS IN NAPTR e164.arpa. ?... NAPTR... What is ENUM adding? ENUM DNS

January 2006Richard Stastny13 What are the Benefits of ENUM? ENUM is using the DNS –it’s there, it works, it’s global, it scales, it’s reliable, it’s open, anyone can use it… –saving CAPEX Enables the originating administrative domain to do an All Call Query (ACQ) to find the destination network –Ultimate solution in Number Portability Provisioning is done only by the destination (recipient) administrative domain for the E.164 numbers this domain is hosting –Saving OPEX Enables all multimedia (MM) services for E.164 numbers for all sessions on IP end-to-end –Enables convergence (whatever that means)

January 2006Richard Stastny14 So what ENUM should be used? The ENUM Babuschka‘s

January 2006Richard Stastny15 The “ENUMs” User ENUM Private ENUM Operator ENUM Enterprise ENUM Federation ENUM Carrier ENUM Infrastructure ENUM EMINEM

January 2006Richard Stastny16 User ENUM User ENUM requires –country opt-in –end-user opt-in “Service providers” have no say in User ENUM So Service Providers using IP-based technology need other solutions to be able to Interconnect –via IP-based technology and –using E.164 Numbers

January 2006Richard Stastny17 Private ENUM Also called: –Operator ENUM –Enterprise ENUM An administrative domain is setting up their own private ENUM DNS –May be used in addition to other solutions to route within own network But does not solve the Interconnect problem with other administrative domains AND –requires extensive provisioning

January 2006Richard Stastny18 Federation ENUM This is currently how “service providers” interconnect on IP: Variants: –Private ENUM in a “walled garden” extranet (GSMA) –SIP Exchange with restricted access on the Internet (Cable providers, XConnect, SIP-IX, …) –public tree not in „e164.arpa“ (e164.info) Advantages: –No user opt-in, NO REGULATORS INVOLVED, intrinsic peering agreements, savings in CAPEX, OPEX, MM-services Disadvantages: –limited reach, –no global solution, –how to peer with other federations?

January 2006Richard Stastny19 Public Infrastructure ENUM If Infrastructure ENUM is intended to allow the mapping of any E.164 number –that can be reached via IP –even if it terminates on the PSTN –to a SIP URI, Infrastructure ENUM must be in the public DNS. But this is useless, if the resulting SIP URI cannot be reached So for Infrastructure ENUM also a global IP Interconnect (VoIP Peering) regime is required. ENUM is an applet to VoIP Peering

January 2006Richard Stastny20 Standardisation in IETF Two recent major developments in IETF regarding (VoIP) Interconnect: –ENUM WG extended scope to include Infrastructure ENUM –Voipeer BoFs to create new SPEERMINT WG Session PEERing for Multimedia INTerconnect

January 2006Richard Stastny21 Separation of Scope The ENUM WG is primarily concerned with the acquisition of Call Routing Data (CRD) e.g. a SIP URI, while the SPEERMINT WG is focused on the use of such CRD. Importantly, the CRD can be derived from ENUM (i.e., an E.164 DNS entry), or via any other mechanism available to the user.

January 2006Richard Stastny22 Scope ENUM and SPEERMINT Infrastructure ENUM Policy Database Number SIP URI Routing Parameter ENUM Lookup Policy Lookup I-ENUM SPEERMINT

January 2006Richard Stastny23 Current I-Ds in ENUM WG Carrier/Infrastrucure ENUM Requirements –draft-lind-infrastructure-enum-reqs-01 Combined User and Carrier ENUM in the e164.arpa tree –draft-haberler-carrier-enum-01 IANA Registration for an Enumservice Containing PSTN Signaling Information –draft-ietf-enum-pstn-02

January 2006Richard Stastny24 Current I-Ds in SPEERMINT Terminology for Describing VoIP Peering and Interconnect –draft-meyer-voipeer-terminology-01 Publishing SIP Peering Policy –draft-lendl-sip-peering-policy-00 –This documents proposes the use of DNS entries to publish a SIP proxy's policy for accepting incoming calls. Such published policies can be used to selectively establish peering relationships between VoIP service providers.

January 2006Richard Stastny25 Benefits in a nutshell The major benefits of Infrastructure ENUM and SPEERMINT for (VoIP) carriers and (VoIP) service providers is to save costs: Minimal CAPEX for setting up the required infrastructure to provide the routing data Minimal OPEX for maintaining routing data: –Announce the E.164 numbers you host (in ENUM) –Announce the domains you host (in DNS) –(make bilateral or multilateral peering agreements) –Query ENUM and DNS to find any other destination provider

January 2006Richard Stastny26 The End Thank you Richard Stastny ÖFEG