1、 ETSI TR 102 055 V1.1.1 (2005-05)Technical Report Telecommunications and Internet converged Services andProtocols for Advanced Networking (TISPAN);ENUM scenarios for user and infrastructure ENUMETSI ETSI TR 102 055 V1.1.1 (2005-05) 2 Reference DTR/TISPAN-04001 Keywords ENUM, USER ETSI 650 Route des
2、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 from:
3、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 th
4、e 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 at
5、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 copyright
6、 and the foregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2005. All rights reserved. DECTTM, PLUGTESTSTM and UMTSTM are Trade Marks of ETSI registered for the benefit of its Members. TIPHONTMand the TIPHON logo are Trade Marks currently being
7、 registered by ETSI for the benefit of its Members. 3GPPTM is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. ETSI ETSI TR 102 055 V1.1.1 (2005-05) 3 Contents Intellectual Property Rights4 Foreword.4 1 Scope 5 2 References 5 3 Definitions and a
8、bbreviations.6 3.1 Definitions6 3.2 Abbreviations .8 4 Introduction 8 4.1 ENUM in e164.arpa .8 4.2 Infrastructure ENUM .9 4.3 Major differences between Infrastructure ENUM and ENUM in e164.arpa9 4.4 Choice of an domain apex for Infrastructure ENUM .10 5 Types of Infrastructure ENUM 11 5.1 CSP-intern
9、al Infrastructure ENUM11 5.2 CSP-shared Infrastructure ENUM11 5.3 Global (or Common) Infrastructure ENUM.12 6 Authentication aspects12 7 Architectural options 12 8 A possible evolution path.13 9 Likely Infrastructure ENUM usage scenarios 15 9.1 Private Infrastructure ENUM only (Step 2)15 9.2 Private
10、 Infrastructure ENUM with IP-based Interconnect (Step 3)16 9.3 Shared Infrastructure ENUM with Extranet (Step 4) .16 9.4 Shared Infrastructure ENUM on the Internet (Step 5b)18 Annex A: Architectural models 20 A.1 Model A20 A.2 Model B21 A.3 Model C22 A.4 Model D23 A.5 Model E24 History 25 ETSI ETSI
11、TR 102 055 V1.1.1 (2005-05) 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 members and non-members, and can be found in ETSI SR 0
12、00 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:/webapp.etsi.org/IPR/home.asp). Pursuant to the ETSI IPR Pol
13、icy, 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 become, essential to the present document. Foreword This Tec
14、hnical Report (TR) has been produced by ETSI Technical Committee Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN). ETSI ETSI TR 102 055 V1.1.1 (2005-05) 5 1 Scope The present document identifies a range of issues which occur if providers of communicat
15、ion services and networks (called Communication Service Providers (CSP) within the present document) consider using the concepts developed in RFC 3761 16 (ENUM) for infrastructure purposes. Such an approach would result in the application of the ENUM concept to the provision of information for route
16、ing (both internally and for the interconnection of networks - also called peering), including information for number portability, freephone and other number or address translation capabilities, SMS and MMS, etc. It considers the likely steps along the way and where possible, identifies alternative
17、options and approaches. It will specifically identify: Issues which occur if providers of IMS-based NGNs consider peering traffic with each other via Points-of-Interconnect based on IP technology, by using E.164 numbers to address end-points they are hosting for their subscribers. Issues which occur
18、 if providers of IMS-based NGNs consider peering traffic with other providers e.g. IMS-based PLMNs and also with providers on the Internet. Out-of-scope are requirements for using Infrastructure ENUM for peering of transit traffic not targeted for end-points within the providers control. 2 Reference
19、s For the purposes of this Technical Report (TR), the following references apply: NOTE: The present document is based additionally on “Work in Progress“ at the IETF, documented in Internet Drafts. This is especially valid for the definitions of the “ENUMservices“ in the NAPTR RR, which are based on
20、the definitions in RFC 3761 16. 1 ITU-T Recommendation E.164: “The international public telecommunication numbering plan“. 2 ETSI TS 102 051: “ENUM Administration in Europe“. 3 IETF RFC 1034: “Domain Names - Concepts and Facilities“. 4 IETF RFC 1035: “Domain Names - Implementation and Specification“
21、. 5 IETF RFC 1123: “Requirements for Internet Hosts - Application and Support“. 6 IETF RFC 1591: “Domain Name System Structure and Delegation“. 7 IETF RFC 1738: “Uniform Resource Locators (URL)“. 8 IETF RFC 2181: “Clarifications to the DNS Specification“. NOTE: Updates: IETF RFC 1034, IETF RFC 1035,
22、 IETF RFC 1123. 9 IETF RFC 2182: “Selection and Operation of Secondary DNS Servers“. 10 IETF RFC 2255: “The LDAP URL Format“. 11 IETF RFC 2368: “The mailto URL scheme“. 12 IETF RFC 2396: “Uniform Resource Identifiers (URI): Generic Syntax“. 13 IETF RFC 2616: “Hypertext Transfer Protocol - HTTP/1.1“.
23、 14 IETF RFC 3966: “The tel URI for Telephone Numbers“. 15 IETF RFC 2818: “HTTP Over TLS“. ETSI ETSI TR 102 055 V1.1.1 (2005-05) 6 16 IETF RFC 3761: “The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application (ENUM)“. 17 IETF RFC 3261: “SIP: Session Initia
24、tion Protocol“. 18 IETF RFC 3401: “Dynamic Delegation Discovery System (DDDS) Part One: The Comprehensive DDDS“. 19 IETF RFC 3402: “Dynamic Delegation Discovery System (DDDS) Part Two: The Algorithm“. 20 IETF RFC 3403: “Dynamic Delegation Discovery System (DDDS). Part Three: The Domain Name System (
25、DNS) Database“. 21 IETF RFC 3405: “Dynamic Delegation Discovery System (DDDS) Part Five: URI.ARPA Assignment Procedures“. 22 IETF RFC 3508: “H.323 Uniform Resource Locator (URL) Scheme Registration“. 23 IETF RFC 3762: “Telephone Number Mapping (ENUM) Service Registration for H.323“. 24 IETF RFC 3764
26、: “Enumservice Registration for Session Initiation Protocol (SIP) Addresses-of-Record“. 25 IETF RFC 3861: “Address Resolution for Instant Messaging and Presence“. 26 ETSI TS 102 172: “Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Minimum requireme
27、nts for interoperability of ENUM implementations“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the following terms and definitions apply: Address-of-Record (AoR): within SIP, an address-of-record represents an identity of the user, generally a long-term
28、identity, and it does not have a dependency on any device; users can move between devices or even be associated with multiple devices at one time whilst retaining the same address-of-record NOTE: A simple URI, generally of the form “sip:“, is used for an address-of-record. apex: name of a delegation
29、 point in the DNS. For example, the zone apex for the public ENUM name space is e164.arpa border element: generic term used for any device separating intranets, extranets and the public Internet NOTE: It may consist of firewalls, session border controllers and may provide Network Address Translation
30、 (NAT) functions. Communication Service Provider (CSP): any entity providing communications services using E.164 numbers to “End Users“ and using an infrastructure to provide routeing capabilities NOTE: The “End Users“ may be on the Internet, within an IMS based NGN or even on the PSTN. domain: set
31、of names within the DNS consisting of a single domain name and all the domain names below it E.164: International Public Telecommunications Numbering Plan E164 number: number taken from the International Public Telecommunications Numbering Plan ENUM: protocol developed by the IETF as RFC 3761 16 to
32、be used within e164.arpa ETSI ETSI TR 102 055 V1.1.1 (2005-05) 7 ENUMservice: parameter held in the Service Field of a NAPTR Resource Record associated with the ENUM DDDS Application that indicates the class of functionality a given URI Scheme offers NOTE: According to RFC 3761 16 an “ENUMservice“ i
33、s defined in an RFC and officially registered with IANA (see http:/www.iana.org/assignments/enum-services). End user: entity using the services provided by the CSP. This may be IP Communication services including Infrastructure ENUM ENUM End User: entity using ENUM services in e164.arpa extranet: an
34、y IP network within the full control of a group (confederation) of CSPs. It is both separated from the intranets of the participating CSPs and from the public Internet by border elements NOTE: It may or may not have an IP address space part of the public IP address space. Here only the extranet cont
35、aining the DNS and Infrastructure ENUM is of concern. infrastructure ENUM: See clause 4, “Introduction“. Other terms used are Carrier ENUM or Operator ENUM. intranet: any IP network within the full control of an CSP NOTE: It is separated from other IP networks (extranets or the public Internet) by o
36、ne or more border elements. It may or may not have an IP address space part of the public IP address space. Naming Authority Pointer Resource Record (NAPTR): Naming Authority Pointer Resource Record is a DNS Resource Record type specified in RFC 3403 20 that can be used to generate URIs Number Porta
37、bility: ability of an end user to change location within a geographic area, between service providers or services, without changing their number NOTE: This must be in accordance with the portability requirements pertaining to each specific type of E.164 number. Point-of-Interconnect (PoI): access po
38、int between two networks NOTE: The PoI may be any type of border element such as session-border-controller, ingress gateways, SIP server, gatekeeper, etc. or the VoIP servers may be reached directly via the Internet. private name space: name space in the DNS which is private to a CSP and is typicall
39、y only visible to an organizations internal network public name space: name space in the DNS that is visible on the public Internet shared name space: name space in the DNS that is visible to a group of CSPs but not visible to the Internet tier: delegation point within DNS for administrative or tech
40、nical purposes. In the present document the Tier 0 is the global Apex for an instance of Infrastructure ENUM NOTE: Depending on the model and architecture used in an instance of Infrastructure ENUM there may be one or more Tiers. Uniform Resource Identifier (URI): compact string of characters for id
41、entifying an abstract or physical resource (e.g. an application) NOTE: An URI is used within a NAPTR Resource Record to point to a specific application. Uniform Resource Identifier (URI) Schemes: in the Uniform Resource Identifier (URI) definition (RFC 2396 12, RFC 1738 7) there is a field, called “
42、scheme“, to identify the type of resource NOTE: URI Schemes are defined in RFCs and officially registered with the IANA (see http:/www.iana.org/assignments/uri-schemes). ETSI ETSI TR 102 055 V1.1.1 (2005-05) 8 3.2 Abbreviations For the purposes of the present document, the following abbreviations ap
43、ply: AoR Address-of-Record CSP Communication Service Provider DNS Domain Name System IAB Internet Architecture Board IETF Internet Engineering Task Force IP Internet Protocol ISUP ISDN User Part MMS Multi-Media Message Service NAPTR Naming Authority PoinTer resource Record NAT Network Address Transl
44、ator NGN Next Generation Network NS NameServer PLMN Public Land Mobile Networks PoI Point of Interconnect PSTN Public Switched Telephone Network RFC Request For Comment (IETF related standard) RRs (DNS) Resource RecordsSCN Switched Circuit Network SIP Session Initiation Protocol SMS Short Message Se
45、rvice TDM Time Division Multiplex (a synonym for circuit-switched networks) URI Uniform Resource Identifier URL Uniform Resource Locator VPN Virtual Private Network 4 Introduction It is necessary to understand the fundamental differences between ENUM in e164.arpa and Infrastructure ENUM as discussed
46、 in the present document. 4.1 ENUM in e164.arpa RFC 3761 16 together with RFC 3403 20 defines the ENUM protocol and the NAPTR records. RFC 3761 16 discusses the use of the Domain Name System (DNS) 2, 3 for storage of E.164 numbers and how DNS can be used for identifying available services connected
47、to one E.164 number. Through transformation of E.164 numbers in the international format 1, into DNS names and the use of existing DNS services like delegation through NS records and NAPTR records, one can look up what services are available for a specific E.164 number in a decentralized way with di
48、stributed management of the different levels in the lookup process. RFC 3761 16 states in the introduction: “The domain “e164.arpa“ is being populated in order to provide the infrastructure in DNS for storage of E.164 numbers. In order to facilitate distributed operations, this domain is divided int
49、o subdomains. Holders of E.164 numbers which want to be listed in DNS should contact the appropriate zone administrator according to the policy which is attached to the zone. One should start looking for this information by examining the SOA resource record associated with the zone, just like in normal DNS operations. Of course, as with other domains, policies for such listings will be controlled on a subdomain basis and may differ in different parts of the world.“ This implie
