IP Interconnect and Infrastucture ENUM and the relevance on NGNs AKTK ENUM Wien, 16' Feber 2006

1
IP Interconnectand Infrastucture ENUMand the
relevance on NGNsAK-TK ENUMWien, 16. Feber 2006

• Richard Stastny, ÖFEG

The opinions expressed here may or may not be
that of my company
2
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

3
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

4
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-users device

5
Example IMS (TS 23.228)

• 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

6
Possible Public User Identities

• E.164 numbers
• SIP URIs defined by provider
• sip4319793321_at_telekom.at
• siprichard.stastny_at_aon.at
• SIP URIs with self-provided domains
• sip8431_at_kapsch.net
• siprichard.stastny_at_oefeg.at

7
ENUM is defined by the IETF

• 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. http//enum.nic.at )
• The purpose of ENUM is to enable the convergence
  between the PSTN and the Internet

8
ENUM in a nutshell
43 720 203 211

• take an E.164 phone number

• turn it into a FQDN

1.1.2.3.0.2.0.2.7.3.4.e164.arpa.

• query the DNS (for NAPTR)

• returns list of URIs

siprichard.stastny_at_iphone.at
mailtorichard.stastny_at_oefeg.at
sms tel[phone]
IN NAPTR 100 100 "u" E2Usip !.!SIPrichard_at_i
phone.at! .
9
ENUM Implementations
Delegations in e164.arpa as of February 15th, 2006

• 30 Greece
• 31 Netherlands
• 33 France Trial
• 350 Gibraltar
• 353 Ireland Trial
• 354 Iceland
• 358 Finland Trial
• 36 Hungary
• 374 Armenia
• 386 Slovenia requested
• 39 Italy
• 40 Romania
• 41 Switzerland
• 420 Czech Republic Trial?
• 421 Slovakia Trial?
• 423 Liechtenstein Trial
• 43 Austria
• 44 UK Trial
• 46 Sweden Trial

• 246 Diego Garcia
• 247 Ascension
• 290 Saint Helena
• 55 Brazil
• 61 Australia Trial
• 63 Philippines ?
• 66 Thailand
• 65 Singapore Trial
• 81 Japan Trial
• 82 Korea Trial
• 86 China Trial
• 88234 Global Networks ?
• 87810 VISIONng UPT
• 971 UAE

• 1 North America (US, CA, Jamaika)
• additional Asian countries (Taiwan) have trials,
  but not in .arpa

http//www.ripe.net/enum/request-archives/http/
/www.centr.org/kim/enum/index.html
10
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

11
SIP Session establishment
If this does not work, forget ENUM
IP based network
DNS
DNS SRV lookup providerB.net
SIP
SIP
server
server
sipbob_at_providerB.net
sipbob_at_providerB.net
session
sipalice_at_providerA.net
sipeve_at_providerA.net
sipeve_at_providerB.net
sipbob_at_providerB.net
12
Overall ETSI TISPAN IMS Architecture all
subsystems
Rf
/Ro
Ut
Rf
/Ro
Charging
Application Servers
Ut
Functions
Sh
Rf
/Ro
ISC
Dh
UPSF
Iw
SLF
IWF
Cx
Dx
Ib
P3
IMS / PSTN Simulation
PSTN Emulation (R2)
Mw
Mw/Mk/Mm
IBCF
Ic
I/S
-
CSCF
Mk
Mi
AGCF
P2
BGCF
Mk
Mw
Mr
Mj
Gq
'
Mg
e2
P
-
CSCF
SGF
MGCF
MRFC
Ie
Other IP Networks
P1
Gq
'
Gq
'
Network
Gm
SPDF
PSTN/ISDN
SPDF
Attachment
Resource Admission Control
Resource Admission Control
Mp
Mn
Subsystem
A-RACF
e4
MG
Re
Ia
MRFP
T
-
MGF
I
-
BGF
UE
BGF
RCEF
IP Transport (Access and Core)
CNG
-
13
ITU-T NGN System Architecture
14
IMS ?
15
E.164 Session establishment
What is ENUM adding?
IN NAPTR 0.1.4.0.2.4.0.8.7.3.4.e164.arpa. ?
... NAPTR ... "!.!sipbob_at_providerB.net!"
DNS
DNS SRV lookup providerB.net
SIP
SIP
server
server
tel[phone]
sipbob_at_providerB.net
session
sipalice_at_providerA.net
sipeve_at_providerA.net
sipeve_at_providerB.net
sipbob_at_providerB.net
16
What are the Benefits of ENUM?

• ENUM is using the DNS
• its there, it works, its global, it scales,
  its reliable, its 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)

17
So what ENUM should be used?
The ENUM Babuschkas
18
The ENUMs

• User ENUM
• Private ENUM
• Operator ENUM
• Enterprise ENUM
• Federation ENUM
• Carrier ENUM
• Infrastructure ENUM
• EMINEM

19
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

20
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

21
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?

22
The Future as seen by GSMA
23
Carrier DNS Architectures
Shows possible examples of the DNS
hierarchy which will vary by country
The carrier data is normally stored in a database
and the DNS datafill generated when the DNS is
updated
Master Root Server (Tier 0)
IPX B
Slave Root Server (Tier 0)
Country Y
Country Z
Country X
Central Authority
Central Authority
Mobile Operator
Fixed Operator
Mobile Operator
Fixed Operator
24
IPI (IP Inter-working) goals

• Create environment to grow IP services
• Ensure customer centric sustainable model
• Introduce a fair distribution of value
• Foster continuous market growth
• Establish alternatives to access-only based
  inter-working
• Ensure several models available in the market

25
Some Companies Involved
Additional IPI project supporters
SIP trial project
Total approx 50 companies actively involved in
trials
26
(No Transcript)
27
SIP Forum - IP PBX/SP Interop
28
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

29
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
• WG established 8. Feber 2006

30
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.

31
Scope ENUM and SPEERMINT
Infrastructure ENUM
ENUM Lookup
I-ENUM
Policy Database
Policy Lookup
SPEERMINT
32
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

33
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.

34
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

35
Next Activities

• ETSI TISPAN WG4
• WI 4006 on Interconnect
• WI 4009 to update TS 102 172 for Infrastructure
  ENUM
• Joint Meeting with GSMA (March 1st, London)
• IETF65 in Dallas, March 2006
• ENUM, SPEERMINT
• NP Conference, London, March 2006
• ENUM Summit, IQPC, Boston, April 2006
• ITU-T SG2, Geneva, May 2006
• Infrastructure ENUM and IP Interconnect, Marcus
  Evans, London, June 2006,

36
The End

• Thank you

Richard Stastny ÖFEG 43 664 420
4100 richard.stastny_at_oefeg.at http//voipandenum.b
logspot.com