1、 ETSI TS 102 172 V1.2.1 (2005-04)Technical Specification Telecommunications and Internet converged Services andProtocols for Advanced Networking (TISPAN);Minimum requirements for interoperability ofENUM implementationsETSI ETSI TS 102 172 V1.2.1 (2005-04) 2 Reference RTS/TISPAN-04003 Keywords enum,
2、interoperability ETSI 650 Route des 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 prese
3、nt document can be downloaded from: 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 o
4、f dispute, the reference shall be 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 o
5、ther ETSI documents is available 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
6、by written permission. The copyright 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
7、logo are Trade Marks currently being 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 TS 102 172 V1.2.1 (2005-04) 3 Contents Intellectual Property Rights4 Foreword.4 1 Scope
8、5 2 References 5 3 Definitions and abbreviations.6 3.1 Definitions6 3.2 Abbreviations .9 4 Introduction 9 5 General objectives of ENUM implementations .10 6 Interoperability of ENUM implementations 11 6.1 Constraints in national implementations 11 6.2 Interoperability in ENUM implementations.13 7 Ad
9、ministrative requirements for interoperability of ENUM implementations 14 8 DNS requirements for interoperability of ENUM15 9 Harmonization of the “ENUMservice“ field in the NAPTR Records 16 9.1 Background to minimum requirements for NAPTR use 16 9.2 General conditions16 9.3 Format and processing of
10、 NAPTR records.17 9.4 “ENUMservices“ and associated URI Schemes .18 9.4.1 Minimum set of “ENUMservices“18 9.4.1.1 “ENUMservices“ for Interactive Media-stream Exchange19 9.4.1.2 “ENUMservices“ for Discrete (non-session related) Messages 19 9.4.1.3 “ENUMservices“ for Information Source .20 9.4.1.4 “EN
11、UMservices“ for Service Resolution Services20 9.4.1.5 “ENUMservices“ for Session-oriented Message Exchanges.21 9.4.1.6 “ENUMservices“ for Instant Information Display - Announcement.21 9.4.1.7 “ENUMservice“ for Redirection .21 9.4.1.8 “ENUMservice“ void 22 9.4.2 Additional “ENUMservices“ 22 9.4.2.1 “
12、ENUMservices“ for Location Information 23 9.4.2.2 “ENUMservices“ for Public Key Information 23 10 Processing of retrieved information by ENUM Clients .23 10.1 All ENUM Clients23 10.2 ENUM enabled Clients for specific applications .23 10.3 Examples of specific ENUM enabled Application Clients 24 10.3
13、.1 ENUM enabled gateway from the PSTN to the Internet 24 10.3.2 ENUM enabled SIP Client24 10.3.3 ENUM enabled H323 Client.24 10.3.4 ENUM enabled Email Client24 10.3.5 ENUM enabled Web Browser 25 10.3.6 ENUM enabled FTP Client.25 10.3.7 ENUM enabled FAX Client25 10.3.8 ENUM enabled SMS Client .25 10.
14、3.9 ENUM enabled Location Client .25 Annex A (informative): Background to NAPTR Resource Records26 Annex B (informative): Bibliography.29 History 30 ETSI ETSI TS 102 172 V1.2.1 (2005-04) 4 Intellectual Property Rights IPRs essential or potentially essential to the present document may have been decl
15、ared 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 000 314: “Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respect of ETSI standards“, which
16、 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 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
17、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 Technical Specification (TS) has been produced by ETSI Technical Committee Telecommunications and Internet converged Services and Protocols for
18、Advanced Networking (TISPAN). ETSI ETSI TS 102 172 V1.2.1 (2005-04) 5 1 Scope The present document contains general guidance on (User) ENUM implementations as defined in RFC 3761 16 and in TS 102 051 2 “ENUM Administration in Europe“ and the specification for: The format, contents and meaning of the
19、 information in the NAPTR records that are held by the ENUM Tier 2 Nameserver providers and accessible by DNS. The ways in which ENUM client software should interpret and act upon information obtained from NAPTR records. The present document is intended to enable interoperability between ENUM implem
20、entations that are organized in different countries. This interoperability enables: The same ENUM client software to work with NAPTR records generated by different national implementations and this in turn will enable applications that use ENUM to access details of ENUM subscribers in more than one
21、country without additional modifications. Organizations to function as ENUM Registrars and ENUM Tier 2 Nameserver Provider in more than one national implementation. The present document will therefore add economies of scope to the ENUM implementations that will benefit ENUM subscribers, providers, a
22、pplication service providers and ENUM users. The present document is Version 2 of the Technical Specification (TS) and incorporates already some results obtained from trials performed in some countries. It may serve therefore with some caution also as a basis for first commercial deployments, keepin
23、g in mind that still not all enumservices are available as IETF RFCs and registered with IANA, The intention is to review the present document based on the experience gained from future implementations and if necessary. 2 References The following documents contain provisions which, through reference
24、 in this text, constitute provisions of the present document. 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. For a non-specific reference, the latest version appl
25、ies. Referenced documents which are not found to be publicly available in the expected location might be found at http:/docbox.etsi.org/Reference. NOTE 1: The present document is based additionally on “Work in Progress“ at the IETF, documented in Internet Drafts. This is especially valid for the def
26、initions of the “ENUMservices“ in the NAPTR RR, which are based on 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“.
27、 4 IETF RFC 1035: “Domain names - implementation and specification“. 5 IETF RFC 1123: “Requirements for Internet Hosts - Application and Support“. 6 IETF RFC 1591: “Domain Name System Structure and Delegation“. ETSI ETSI TS 102 172 V1.2.1 (2005-04) 6 7 IETF RFC 1738: “Uniform Resource Locators (URL)
28、“. 8 IETF RFC 2181: “Clarifications to the DNS Specification“. 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 3986: “Uniform Resource Identifier (URI): Generic Syntax“. 13 IETF RFC 2
29、616: “Hypertext Transfer Protocol - HTTP/1.1“. 14 IETF RFC 3966: “The tel URI for Telephone Numbers“. 15 IETF RFC 2818: “HTTP Over TLS“. 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
30、Initiation 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 Sys
31、tem (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
32、 3764: “enumservice registration for Session Initiation Protocol (SIP) Addresses-of-Record“. 25 IETF RFC 3861: “Address Resolution for Instant Messaging and Presence“. 26 IETF RFC 2671: “Extension Mechanisms for DNS (EDNS0)“. 27 IETF RFC 2915: “The Naming Authority Pointer (NAPTR) DNS Resource Recor
33、d“. 28 IETF RFC 2532: “Extended Facsimile Using Internet Mail“. 29 IETF RFC 3965: “A Simple Mode of Facsimile Using Internet Mail“. NOTE 2: Also some of the above referenced URI Schemes are currently in the process of being updated. 3 Definitions and abbreviations 3.1 Definitions For the purposes of
34、 the present document, the terms and definitions given in TS 102 051 2, with the exception of ENUM End User and ENUM Subscriber and the following apply: NOTE: The term ENUM End user is not used within the present document, ENUM User and ENUM Subscriber are defined as follows. ETSI ETSI TS 102 172 V1
35、.2.1 (2005-04) 7 ENUM Subscriber: assignee of an E.164 number who has agreed to insert its E.164 number in the ENUM DNS-based architecture and who requests population of an ENUM domain NOTE: The ENUM subscriber has full control over the provision and content of the NAPTR Resource Records in the ENUM
36、 Tier 2 Nameserver provider. The ENUM Subscriber is called ENUM End User in TS 102 051 2. ENUM User: person or entity who is querying the ENUM DNS-based architecture using an ENUM-enabled Application Client or an ENUM Client NOTE: The ENUM User may be aware only of the application and not of the use
37、 of ENUM by the application. In addition, the following terms and definitions apply: Application Client: function that provides a user access to the Application Server, e.g. a VoIP client or e-mail client Application Server: function provided by an Application Service Provider to communicate with th
38、e Application Client Communication Service Provider (CSP): any entity providing communications services using E.164 numbers to “End Users“ and using an infrastructure to provide routing capabilities NOTE: The “End Users“ may be on the Internet, within an IMS based NGN or even on the PSTN. ENUM Clien
39、t: function that provides access to the DNS which will then return information in the form of NAPTR records NOTE: This could take several forms e.g. it may reside as client software on an intelligent terminal used directly by the ENUM User or be network based, provided upstream as part of the facili
40、ties offered by an Application Service Provider. ENUM Client Supplier: entity supplying the ENUM Client ENUM enabled Application Client: Application Client querying ENUM directly for NAPTR Resource Records ENUM enabled Application Server: Application Server that is using ENUM Clients as part of thei
41、r application, e.g. an email server that translates phone numbers in the To:/RCPT fields into their ENUM stored mailto: values “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
42、 Scheme offers NOTE: According to RFC 3761 16 an “ENUMservice“ is defined in an RFC and officially registered with IANA (see http:/www.iana.org/assignments/enum-services). The following “ENUMservices“ are currently registered with IANA: sip RFC 3764 24 h323 RFC 3762 23 The following “ENUMservices“ a
43、re in contained in the following I-Ds: voice:sip - voice:h323 - voice:tel draft-brandner-enumservice-vovi-02 video:sip - video:h323 - video:tel draft-brandner-enum-service-vovi-02 email:mailto draft-ietf-enum-msg-03 fax:tel draft-ietf-enum-msg-03 sms:tel draft-ietf-enum-msg-03 sms:sip - sms:sips - s
44、ms:mailto draft-ietf-enum-msg-03 ems:tel draft-ietf-enum-msg-03 ems:sip - ems:sips - ETSI ETSI TS 102 172 V1.2.1 (2005-04) 8 ems:mailto draft-ietf-enum-msg-03 mms:tel draft-ietf-enum-msg-03 mms:sip - mms:sips - mms:mailto draft-ietf-enum-msg-03 ifax:mailto draft-ietf-fax-faxservice-enum-03 web:http
45、draft-ietf-enum-webft-01 web:https draft-ietf-enum-webft-01 ft:ftp draft-ietf-enum-webft-01 pres draft-ietf-pres-01 ann:sip - ann:h323 - ann:tel - ann:http - ann:ftp - enum - void:mailto draft-ietf-enum-void-01 void:http draft-ietf-enum-void-01 void:mailto draft-ietf-enum-void-01 loc:http - key:ldap
46、 - key:http - Infrastructure ENUM: Infrastructure ENUM is about publishing the information with E.164 numbers that a Communication Service Provider (CSP) is hosting to either a group of selected peers or to all other CSPs. Naming Authority Pointer Resource Record (NAPTR): DNS Resource Record type sp
47、ecified in RFC 3403 that can be used to generate URIs Resource Record: element within the Domain Names System (DNS) containing a data item associated with a domain name Uniform Resource Identifier (URI): compact string of characters for identifying an abstract or physical resource (e.g. an applicati
48、on) 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 3986, RFC 1738) there is a field, called “scheme“, to identify the type of resource. NOTE: URI Schemes are d
49、efined in RFCs and officially registered with the IANA (see http:/www.iana.org/assignments/uri-schemes). The following registered URI Schemes are used within the present document: ftp File Transfer Protocol RFC 1738 7 http Hypertext Transfer Protocol RFC 2616 13 mailto Electronic mail address RFC 2368 11 sip, sips Session Initiation Protocol RFC 3261 17 tel Telephone RFC 3966 14 ldap Lightweight Directory Access Protocol RFC 2255 10 https Hypert
