INTRODUCTION TO ITUITU--TT Products and Tools relating to Numbering Resolution 20 Resolution 47 RltiResolution 49 Resolution 60

Martha Onyeajuwa INTRODUCTION TO ITU-T Products and Toolsrelilating to Numbibering

Resolution 20 Resolution 47 Resolution 49 Resolution 60 RESOLUTION 20 – PROCEDURES FOR ALLOCATION AND MANAGEMENT OF INTERNATIONAL TELECOMMUNICATION NUMBERING, NAMING, ADDRESSING AND IDENTIFICATION RESOURCES RESOLUTION 20

¾The role of the TSB Director and ITU Member States with respect to the allocation and management of numbering resources is defined in Resolution 20

¾ It is inthecommoninterest of ITU-T member states and sector members that the recommendations and guidelines for international telecommunication numbering,g naming,g addressing and identification resources should be known, recognized and applied to all and used to build and maintain confidence of all in the related services ¾ All ITU member states should fully be aware of WTSA- 04 reso lut ion 20 so as to properl y appl y th e rel evant ITU-T recommendations and guidelines for International telecommunication numbering, naming, addressing and identification resources

¾ Procedures governing the allocation and management of International numbering, naming, addressing and identification resources developed by ITU member states should be in accordance with the relevant E,F,Q, and X series f ITU-T recommendations.

¾ Participation of National Regulatory authorities in ITU member states, responsible for allocation of numbering, naming, addressing and identification resource including Q708 signaling area network codes and X 121 data country codes in Studyyp Group 2 relevant activities A Simple Procedure for Allocation and Management of EE..164164numbering plan

¾ Eligibility o Only for telecommunication operators licensed by the National Regulatory Authority (NRA) to provide a telecommunications service that require a numbering capacity.

¾ Submission of an application form to the NRA o telecommunications operators already in possession of individual license; o new applicant for an individual license. ¾ Content of the Application form o Data for identification of the applicant o Number of valid licenses o Type of telecommunications services for which the applicant has individual licenses or has submitted an application for licensing o Type of the telecommunications service for which the numbering capacity will be used o Number block of interest to the applicant o The duration for usage of the number bloc o Coverage area required for the service o Date of commencement for use of applied number ¾ Justification of need Applicants to submit o proofs of need for the new numbering capacity o detailed report about the utilization of the previously allocated numbering capacity o plan for the future utilization of the numbering capacity

¾ If any short fall is observed while processing the application form, the NRA sends the applicant a written notification.Thereof, the applicant must update his documentation in compliance with the requirements within the stipulated time frame. Otherwise his application will not be considered for number allocation. ¾ Assessment of the submitted Application form by the NRA takes into account o the valid individual license of the applicant o the requirement for equal treatment and fair competition o the established structure of the NNP and the available numbering capacity o the value of the request made by the applicant o Applicant Indebtedness o Others ¾ Content of Individual License

oThe allocated numbering capacity, its designation, period of usage, rules and procedures of the second assignment to end users, etc are specified in the individual licenses issued to the new applicant or as an amendment to an existing license.

¾ Number Database

oThe NRA records the allocated number capacity, its user and period/area of usage into the number database accessible to the public. ¾ Rights and obligations of the licensed operator with resppgect to the usage of the allocated cap pyacity.

oAny licensed operator authorized to use a numbering capacity from the NNP must observe the terms and conditions specified in the individual licenses. o Licensed operator does not have right of property over the allocated numbering capacity. o The operator authorized to use allocated numbering capacity must pay fees appropritiate to theallocat ed resources. o The licensed operator must maintain a database of the secondary assignment, reserved and free number space of the allocation he received from the NRA. o If operator wishes to close his business he must notify the NRA within the time frame to be specified in his license condition. Management of E.164 numbering resources

¾ Regulators o Develop an efficient and dynamic allocation procedure that is appropriate for your environment o Reserve high percentage of Number space for future unanticippgated needs and convergence issues o Provide fair and equitable distribution of numbering resources to the industry o Develop appropriate practices and controls to ensure that operators are not abusing allocated or unallocated numbering resources Management of E.164 numbering resources

¾ Operators o Follow regulations and guidelines in distribution of o numbering resources o MiMainta in adequate record s to track how resources are used . o Exercise restraint in requests for excess capacity o Manage inventory so that resources are available o when needed o Reclaim unused resources for re-assignment purposes MANAGEMENT OF NUMBERING CAPACITY (Consequences of Poor Management)

¾ Number resource may be exhaust

¾ Consumers are likely to be Confuse

¾ Delay and rework of new service activation

¾ Disruption of existing service

¾ Delay in introduction of new services

¾ Lack of a fair competitive environment

¾ Disincentive for investment in Telecom Services RESOLUTION 47 – Countryyp Code Top--levellevel Domain Names (cc TLD) RESOLUTION 47

General

¾ ITU-T member states and sector members are invited to contribute to the studies/activities of Study Group 2 on country code top-level domain names.

¾ They are further invited to take appropriate steps within their legal frameworks to ensure that issues related to delegation of Country Code top-level domains are resolved. Resolution 47 – Country Code TopTop--levellevel Domain Names ((ccTLDccTLD)) y What is Domain Names System The System (“DNS”) is a distributed hierarchical look up services used on to translate between domain names and IP address which consists of: o DNS Data o Name Server o And a Prot oc ol used to retrieve data from the servers y Clients of the DNS o Web browsers o Mail transfer agents o OhOther name servers RESOLUTION 47 – Country Code TopTop--levellevel Domain Names (cc TLD)

¾ Domain names o It provides higher level naming scheme for the internet o It include top level domain (TLD) eg “com”, “edu”, “int”, “org” followed by subdomains o The last portion of a host name; example itu. int. www.itu.int (is the top level domain (TLD) which a host belongs

¾ Geographic TLD (ccTLD) ¾ 2 characters codes their indicate the country, eg • be for Belgium • cn for China • us for USA RESOLUTION 47 – Country Code TopTop--levellevel Domain Names (cc TLD) RESOLUTION 47 – Country Code TopTop--levellevel Domain Names (cc TLD) --ContinueContinue

y The root mode of the Internet name space consists of a single File, the root zone file - All Internet top level domains has two pointers master (primary)

y Top of the DNS ddtbatabase; - 13 root name servers consisting of a primary server, “a root-server.net” and 12 secondary name servers RESOLUTION 47 – Country Code TopTop--levellevel Domain Names (cc TLD) -Contd y The location of the 13 root name servers are shown in the diagram below. Ten are in USA while the rest are located in Japan, Sweden and United Kingdom RESOLUTION 47 – Country Code TopTop--levellevel Domain Names (cc TLD) -Contd Points for discussion y Role of Intergovernmental organizations in the coordination of Internet related public policy issuer y Role by International organizations in development of Internet –related technical standards and relevant policy y Acti v it ies o f Stu dy Group 2 rel ati ng to Country Code top-level domain names RESOLUTION 49 -ENUM- ENUM Resolution 49 –ENUM– ENUM

¾ There is continuing progress towards integration of telecommunication and the internet through the work of Study Group 2 concerning ENUM continues. ¾ The SG2 is instructed to study how ITU could have administrative control over changes that could relate to the international telecommunication resources (includin g namin g, numberin g, addressin g and routing) used for ENUM. ¾ ITU member states are invited to contribute in the activ it ies of the SG2 and also to tak e necessary steps within their national legal framework to ensure implementation of resolution 49. What is ENUM?

y ENUM = Electronic – Key to Deliver Converged Services y ENUM is one of the enablers of circuit-switched & packet network convergence ⁻ Defined by Internet Engineering Task force (IETF) ⁻ Translates an E.164 number into Internet domain names y ENUM is about new service creation ⁻ Allows use of telephone numbers in various communication media, e.g. e-mail,VoIP ⁻ Can easily facilitate penetration of applications into mass market y Defines use of DNS resource records to find optional ⁻ Email addresses, Fax messages ⁻ Voice over IP SIP/H.323 servers, Voice mail servers How would E.164 numbers be mapped into the DNS?

¾ Reverse map digits in an E.164 number into separate DNS “names” ¾ Concatenate with “ENUM root zone” (as an example, foo.tld) ¾ For example: ⁻ - +33 1 40 20 51 51 = 1.5.1.5.0.2.0.4.1.3.3.E164.TLD 1.5.1.5.0.2.0.4.1.3.3.E164.arpa Sample of ENUM Architecture

Root arpa, com, edu, org, net

Tier 0 e164.arpa International

National Tier 1 1.e164.arpa (country code) Registrars Registry 1…n 46239283791e164arp4.6.2.3.9.2.8.3.7.9.1.e164.arp a Tier 2 NAPTR Record Registry users sip: [email protected] mailto: [email protected] ENUM Architecture Contd..

y ENUM is based on a layered architecture to follow DNS hierarchy and ensure proper competition y Three layers: Tier0, Tier1 and Tier2 y Tier0 functions <> Administration and technical management of ENUM domai n ⁻ Tier0 Registry is an international registry containing ppg(ointers to authoritative national registries (Tier1 Registries) y Tier1 functions <> Management and operation of ENUM in th e country (or porti on of it) ident ifie d by a country code ENUM Architecture Contd

y Tier2 functions <> Provision of ENUM service ⁻ Tier2 Registrar is the commercial interface with the ENUM subscriber and it is involved in the validation process (E.164 number, user identity) Tier2 is open to competition y How Tier1 and Tier2 functi ons are impl emented is a national matter Why ENUM Is Important To Regulators

¾ Mapping of telephone numbers onto Internet ¾ Could allow conventional telephones to call IP terminals (PCs) ¾ Another option is to assign number resources to IP terminals (e.g. Japan, Korea) ¾ Should telephone numbers used in this way be subject to government oversight and regulation ¾ Who shou ld exercise contro l over tel eph one numbers used in this way? Roles and Responsibilities

¾ Most ENUM service and administrative decisions are national issues under purview of ITU Member States, since most E.164 resources are utilized nationally ¾ ITU has defined interim procedures for trials ¾ ITU ensures th at Memb er States specifi ca lly opt-in for their E.164 country code resources to be placed in the DNS ITU Responsibilities

¾ Define and implement administrative procedures that coordinate del egati ons of E.164 numb eri ng resources into the agreed DNS name servers ¾ Draft Recommendation E.A-ENUM is being prepared by Study Group 2 for approval Policy and operational issues for ENUM imp le men ta tion

Most of the issues related to ENUM implementation are nationa l issues, to be add ressed at th e nati onal level . The issues include the following: y How to authenticate the identity of the subscriber for ENUM services? y Who are ENUM registrars and what are they responsible for? y How to validate ENUM data for potential subscribers (Add-modify-Delete) in the NAPTR list of services and preferences? Policy and operational issues for ENUM

imp le men ta tion contd y How are data provisioned in the country code name servers? y How to obtain end-user agreement if necessary to a number in DNS? y How to harden the ENUM zone data against data mining, especially for the purposes of spam? y Competition models amongst suppliers of ENUM services and related portability issues Privacy Issues

¾ Need to obtain end-user agreement to enter number in DNS, depending on national data-protection laws ¾ Hardening the ENUM zone data against data mining, especially for the purposes of spam? ¾ But hard to stop ENUM name servers being harvested for resources bound to an E.164 number ENUM Benefits

¾ Operators ⁻ New revenue opportunities ⁻ Lower cost to launch new converged IP services ⁻ Shorter time to market ⁻ Cross traditional service boundaries and leverage entire business infrastructure to gain a competitive advantage ¾ Customers ⁻ Wider choice of converged services and communications preferences ⁻ Benefit from increased competition, lower prices ⁻ Increased IP service coverage ⁻ Ease-of-use based on familiarity with TN-based services Limitations of ‘standard’ ENUM

¾ ENUM provides a translation from the dialed E.164 number into URIs ¾ It does not take account of point of origin of a call ¾ Therefore no ability to route on point of origin ⁻ Routing of emergency calls ⁻ Routin g to an appr opriat e poin t of in ter conne ct ITU Future ENUM Activities

¾ Cooperate with IAB/IETF to make final choice of TLD (currently e164.arpa), registry, requirements for registry operations ¾ Continue interim administration ¾ Determine ITU-T Recommendation E.A-ENUM, May 2005? Summary: What ENUM is and is not

¾ ENUM IS: ⁻ A partial mapping of E.164 numbers to domain names that define a set of services identified by a URI labels ◦ ENUM can be used for other telephony (like) services ∙ Fax ∙ SMS, MMS ∙ Paging ∙ Instant Messaging Summary: What ENUM is and is not contd. y ENUM IS NOT: ⁻ A directory ⁻ A search service ⁻ A transport service ⁻ A telephony service or voice encoding method ⁻ A rendezvous protocol y It’s not just about SIP (Session Initiation Protocol) ⁻ SIP gateways are often the targets of NAPTR records y Or just Voice over IP (VoIP) ⁻ Not just voice traffic ⁻ Not just about IP-based services What ENUM is and is not contd..

y ENUM is a protocol ⁻ Simp le concep t: use DNS to resol ve add ress based on telephone number ⁻ ENUM provides destination domain What ENUM is and is not contd..

y BUT it does not address end-to-end service delivery issues ⁻ What QoS rul es appl y? ∙ SLA with the terminating carrier? ⁻ What protocol/variations are used ∙ SIP vs. H323 ∙ G711? ⁻ What route to take? ∙ Least cost route? ∙ Different rates depending on the carrier selected? ⁻ What security policy/keys are needed? Summary: Truth About ENUM

¾ Key ENUM Success Requirements Include: o Carrier grade, secure system o Standards Compliance (e.g. ENUM, SIP, etc.) o Interoperability with other registries o Portability, PSTN integration o Extensible to other IP services o IMS compatibility and interoperability ¾ Select a solution architecture that is robust and flexible enough to support your VVIP/IPoIP/IP services strategy Summary: Truth About ENUM contd

¾ ENUM is here now – start planning how to deploy as part of VoIP interconnection planning ¾ Different flavors of ENUM will co-exist and inter-work but traditional carriers will likely gravitate to Carrier and Private ENUM implementations Resolution 60- Responding to Challenges of the evolution of the numberinggy system and its convergence with IP-based Systems/ networks General

¾ The Study Group 2 in liaison with the other relevant Stu dy Groups will stu dy t he necessary requ irements; including administrative requirement for the structure and maintenance of telecommunication identification/numbering resources in relation to the deployment of IP-based networks and the transition to NGN. General contd

¾ The study Group 2, other relevant study groups and the regional groups will develop guidelines and framework as a basis for new applications emanating from the convergence of the International telecommunication numbering system and IP-based system. ¾ Member states and sector members are invited to contribute to the above activities taken their national concerns and experience itinto account. Challenges of Converged Services on User Ident ificati on

¾ Telephone numbers remain a key identification mechanism for users to find each other ¾ With convergence, there are more ways to identify a user – email address, URL, IM buddy name Issues of Convergence

¾ Problems of addressing calls that pass from one network service to another: ¾ Now widely possible to originate calls from IP address- based networks to other networks ¾ But uncommon to terminate calls from other networks to IP address-based networks ¾ To access a subscriber on an IP address-based network, some sort of global addressing scheme across PSTN and IP address-based networks needed ¾ ENUM is one (of many possible solution(s)… Converged Services and Number Allocation

¾ Assign number for converged services (e.g., VoIP) ¾ Assess the implications of the choice of different numbering schemes for interoperability and interconnection between PSTN and IP networks ¾ Understand the legislative and regulatory issues around VoIP and the implications for number portability ¾ Nomadicity as it relates to number portability Imppgacts of Converged Services on Numbering

¾ Numbering should be technology neutral ¾ Choice of number ranges interacts with operators commercial objectives ¾ Possible number ranges: ¾ Geographic ¾ Mobile ¾ Personal ¾ Corporate ¾ New ¾ Shared cost & premium rate services subject to consuliltation wihith idindustry sta khldkeholders Points for discussion

¾ Eliminate regulatory distinctions between: ◦ Contents & Conduit ◦ Fixe and mobile ¾ Apply uniform regulatory framework, irrespective of technology:

o Open access

o Universal Access

o Flexible access Thank you for your attention

Questions?