1、 ETSI TR 184 008 V2.1.1 (2009-02)Technical Report Telecommunications and Internet converged Services andProtocols for Advanced Networking (TISPAN);Infrastructure ENUM Options for a TISPAN IPXETSI ETSI TR 184 008 V2.1.1 (2009-02) 2 Reference DTR/TISPAN-04012-NGN-R2 Keywords DNS, enum ETSI 650 Route d
2、es Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 Siret N 348 623 562 00017 - NAF 742 C Association but non lucratif enregistre la Sous-Prfecture de Grasse (06) N 7803/88 Important notice Individual copies of the present document can be downloaded fro
3、m: http:/www.etsi.org The present document may be made available in more than one electronic version or in print. In any case of existing or perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF). In case of dispute, the reference shall be
4、 the printing on ETSI printers of the PDF version kept on a specific network drive within ETSI Secretariat. Users of the present document should be aware that the document may be subject to revision or change of status. Information on the current status of this and other ETSI documents is available
5、at http:/portal.etsi.org/tb/status/status.asp If you find errors in the present document, please send your comment to one of the following services: http:/portal.etsi.org/chaircor/ETSI_support.asp Copyright Notification No part may be reproduced except as authorized by written permission. The copyri
6、ght and the foregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2009. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTM, TIPHONTM, the TIPHON logo and the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members. 3GPPTM is a Tr
7、ade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. LTE is a Trade Mark of ETSI currently being registered for the benefit of its Members and of the 3GPP Organizational Partners. GSM and the GSM logo are Trade Marks registered and owned by the GSM Asso
8、ciation. ETSI ETSI TR 184 008 V2.1.1 (2009-02) 3 Contents Intellectual Property Rights4 Foreword.4 1 Scope 5 2 References 5 2.1 Normative references .5 2.2 Informative references5 3 Definitions and abbreviations.6 3.1 Definitions6 3.2 Abbreviations .7 4 Introduction 7 5 Types of ENUM.7 5.1 User ENUM
9、7 5.2 Infrastructure ENUM .8 5.2.1 Infrastructure ENUM within the public DNS .8 5.2.2 Infrastructure ENUM within private DNS9 6 Infrastructure ENUM requirements in TISPAN NGN.9 6.1 Top level requirements.9 6.2 Detailed Requirements .11 7 Architectural considerations.11 7.1 ENUM Architecture within T
10、ISPAN .12 7.2 Implementing ENUM using public or private Infrastructure .12 7.2.1 Using Public DNS (Public internet)12 7.2.2 Using Private DNS .13 7.3 Top level architecture.14 7.4 Routeing implementation within each carrier network and within national boundaries.16 8 Evaluation of options16 9 Conclu
11、sions and proposed way forward 17 History 18 ETSI ETSI TR 184 008 V2.1.1 (2009-02) 4 Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. The information pertaining to these essential IPRs, if any, is publicly available for ETSI
12、 members and non-members, and can be found in ETSI SR 000 314: “Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respect of ETSI standards“, which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server (http:/weba
13、pp.etsi.org/IPR/home.asp). Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or may becom
14、e, essential to the present document. Foreword This Technical Report (TR) has been produced by ETSI Technical Committee Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN). ETSI ETSI TR 184 008 V2.1.1 (2009-02) 5 1 Scope The present document provides an
15、overview of some of the relevant options that can be used to implement Infrastructure ENUM (I-ENUM), which in the present document is defined as the use of the technology specified in RFC 3761 i.1 by the carrier of record to map a telephone number into a URI. That URI then identifies a specific poin
16、t of interconnection to that communication providers network that could enable the originating party to establish communication over an IPX to the associated terminating party. An assessment of the options is given and recommendations made in order to provide a secure and reliable implementation of
17、I-ENUM for TISPAN networks to facilitate routeing and interconnection within NGNs. 2 References References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For a specific reference, subsequent revisions do not apply. Non-specific refere
18、nce may be made only to a complete document or a part thereof and only in the following cases: - if it is accepted that it will be possible to use all future changes of the referenced document for the purposes of the referring document; - for informative references. Referenced documents which are no
19、t found to be publicly available in the expected location might be found at http:/docbox.etsi.org/Reference. NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee their long term validity. 2.1 Normative references The following referenced docu
20、ments are indispensable for the application of the present document. For dated references, only the edition cited applies. For non-specific references, the latest edition of the referenced document (including any amendments) applies. Not applicable. 2.2 Informative references The following reference
21、d documents are not essential to the use of the present document but they assist the user with regard to a particular subject area. For non-specific references, the latest version of the referenced document (including any amendments) applies. i.1 IETF RFC 3761: “The E.164 to Uniform Resource Identif
22、iers (URI); Dynamic Delegation Discovery System (DDDS) Application (ENUM)“. i.2 IETF RFC 1034: “Domain Names - Concepts and Facilities“. i.3 IETF RFC 1035: “Domain Names - Implementation and Specification“. i.4 ITU-T Recommendation E.164: “The International Public Telecommunication Numbering Plan“.
23、i.5 ETSI ES 282 002: “Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); PSTN/ISDN Emulation Sub-system (PES); Functional architecture“. ETSI ETSI TR 184 008 V2.1.1 (2009-02) 6 i.6 IETF RFC 5067: “Infrastructure ENUM Requirements“. i.7 IETF RFC 3263: “
24、Session Initiation Protocol (SIP)“. i.8 IAB instructions to RIPE NCC. NOTE: Available at: http:/ i.9 ETSI TS 102 051: “ENUM Administration in Europe“. i.10 ETSI TR 184 007: “Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Naming/Numbering Address Re
25、solution (NAR)“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the following terms and definitions apply: Carrier of Record: the communication provider to which the E.164 number was allocated for end user assignment, whether by the National Regulatory Auth
26、ority (NRA) or the International Telecommunication Union (ITU), for instance a code under “International Networks“ (+882) or “Universal Personal Telecommunications (UPT)“ (+878); or if the number is ported, the communication provider to which the number was ported; or where numbers are assigned dire
27、ctly to end users, the communication provider that the end user number assignee has chosen to provide a Public Switched Telephone Network/Public Land Mobile Network (PSTN/PLMN) point-of-interconnect for the number. It is understood that the definition of carrier-of-record within a given jurisdiction
28、 is subject to modification by NRAs (National Regulatory Authorities). E.164 number: string of decimal digits that, for a geographic country code, uniquely identifies a subscriber or a point where a service is provided For the case of a global service code, it identifies the subscriber of the servic
29、e. For Networks, it identifies a subscriber of the Network. An international E.164 number can act in the “role“ of both a name and an address. Portability is reducing a numbers role as an address. Numbers are increasingly acting in the role of a name only. The number, which includes the country code
30、 and subsequent digits, but not the international prefix, contains the information necessary to route the call to this termination point on a public network (it may also contain the supplementary information necessary to forward it on a private network). NOTE: It is sometimes referred to as an “inte
31、rnational number“, “international public telecommunication number“ or “E.164 number“. Name Number Address Resolution (NAR): The terms “address resolution“ and “name resolution“ are synonymous and are used in the IP world in different manners: In IP network, there are two types of Address Resolutions
32、 defined: The first is the conversion from a domain name into an IP address (see DNS). The second is from the IP address to the Ethernet Address Resolution this is not in the scope of the present document. ETSI ETSI TR 184 008 V2.1.1 (2009-02) 7 Private: any arrangement between parties (specific to
33、a communication provider or shared between consenting groups of communication providers e.g. federation) that is outside of the public Internet TISPAN IPX:ETSI TISPAN defined inter-operator IP backbone network that is compliant with TISPAN standards and is transparent to subscribers NOTE: This is ab
34、le to support connectivity between any type of Service Provider, for interworking, a range of IP services on a bilateral basis with end-to-end QoS and interconnection charging. 3.2 Abbreviations For the purposes of the present document, the following abbreviations apply: CP Communications Provider D
35、DOS Distributed Denial Of Service attack DNS Domain Name System I-ENUM Infrastructure ENUM IPX IP Packet eXchange ITU International Telecommunications Union NAPTR Number Authority Pointer NAR Naming/Numbering Addressing Resolution NGN Next Generation Network PoI Point of Interconnection PSTN Public
36、Switched Telephone Network RRs Resource Records SIP Session Initiation Protocol URI Uniform Resource Identifier PLMN Public Land Mobile Network NRA National Regulatory Authoritie CC Country Code 4 Introduction Within ETSI TISPAN work is progressing on Next Generation Networks (NGNs). A Next Generati
37、on Network (NGN) is a packet-based network able to provide services including Telecommunication Services and is able to make use of multiple broadband, QoS-enabled transport technologies in which service-related functions are independent from underlying transport-related technologies. It offers unre
38、stricted access by users to different communication providers. It supports generalized mobility which will allow consistent and ubiquitous provision of services to users. The realization of those capabilities requires a numbering and routeing capability and the use of DNS protocols and functionality
39、. The present document focuses on the use of Infrastructure ENUM to map a telephone number into a URI that could identify a specific point of interconnection (PoI) to that communication providers network that could enable the originating party to establish communication with the associated terminati
40、ng part through an IPX. 5 Types of ENUM ENUM (RFC 3761 i.1) is a capability that transforms E.164 numbers into domain names and then uses the DNS (Domain Name System) to discover NAPTR records that specify the services available for a specific domain name. There are basically two broad variants of E
41、NUM, User ENUM and Infrastructure ENUM. 5.1 User ENUM User ENUM as originally defined was based on the end-user opt-in principle, where the explicit consent of the user who has the rights to use a specific telephone number is required in order to insert that number into the ENUM system. The user als
42、o has the right to specify the ENUM capabilities that are provided against that number e.g. what is inserted in the associated NAPTRs that facilitate the ENUM services delivered. The standardized implementation of User ENUM ETSI ETSI TR 184 008 V2.1.1 (2009-02) 8 utilizes the public Internet and the
43、 .e164.arpa domain name as specified within RFC 3761 i.1. Procedures about administration of User ENUM have been specified by ETSI i.9. 5.2 Infrastructure ENUM Infrastructure ENUM is defined in the present document as the use of the technology specified in RFC 3761 i.1 by the carrier of record to ma
44、p a telephone number into a URI that identifies a specific point of interconnection to that communication providers network that could enable the originating party to establish communication with the associated terminating party. Other concepts may also apply for I-ENUM in the NGN. The present docum
45、ent, also embraces the ENUM concept and protocol when it is implemented within a private DNS environment e.g. when it does not use the global public DNS. In either case no user data is inserted in the database. Only information required to identify the carrier responsible for the called number, or i
46、n some cases additional information to route the call is inserted within the database and remains under the control of the relevant carrier. Figure 1 depicts the main differences between user and infrastructure ENUM and variants within those categories. Types of User & Infrastructure ENUMUser ENUMIn
47、frastructure ENUMITU Administerede164.arpae164.arpa?User registers numberUser populates recordsUser is authenticatedUser possibly aware of ENUMCarrier registers number range/block Carrier populates & controls recordsAuthentication of carrier requiredEnd User unaware of ENUMOthers e.g. in enum.fooExt
48、ranetse.g. GSMAEnterprise/corporateOthers/privateFigure 1: Types of User and Infrastructure ENUM It shows that both User and Infrastructure ENUM can be provided in a number of forms. For User ENUM implementations could occur within a national environment using e164.arpa once the appropriate National
49、 Regulatory Authority has signalled their approval of this delegation to the ITU-TSB in accordance with the instructions issued by the Internet Architecture Board (IAB) to RIPE-NCC regarding how to proceed with any requests received by RIPE-NCC. Those instructions can be found at http:/ i.8 and at the ITU web site at http:/www.itu.int/ITU-T/inr/enum/procedures.html. A number of different but complimentary implementations of ENUM will exist using both p
