1、 I n t e r n a t i o n a l T e l e c o m m u n i c a t i o n U n i o n ITU-T F.746.6 TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (12/2017) SERIES F: NON-TELEPHONE TELECOMMUNICATION SERVICES Multimedia services Requirements for a name resolution service in information-centric networks Recommendat
2、ion ITU-T F.746.6 ITU-T F-SERIES RECOMMENDATIONS NON-TELEPHONE TELECOMMUNICATION SERVICES TELEGRAPH SERVICE Operating methods for the international public telegram service F.1F.19 The gentex network F.20F.29 Message switching F.30F.39 The international telemessage service F.40F.58 The international
3、telex service F.59F.89 Statistics and publications on international telegraph services F.90F.99 Scheduled and leased communication services F.100F.104 Phototelegraph service F.105F.109 MOBILE SERVICE Mobile services and multidestination satellite services F.110F.159 TELEMATIC SERVICES Public facsimi
4、le service F.160F.199 Teletex service F.200F.299 Videotex service F.300F.349 General provisions for telematic services F.350F.399 MESSAGE HANDLING SERVICES F.400F.499 DIRECTORY SERVICES F.500F.549 DOCUMENT COMMUNICATION Document communication F.550F.579 Programming communication interfaces F.580F.59
5、9 DATA TRANSMISSION SERVICES F.600F.699 MULTIMEDIA SERVICES F.700F.799 ISDN SERVICES F.800F.849 UNIVERSAL PERSONAL TELECOMMUNICATION F.850F.899 ACCESSIBILITY AND HUMAN FACTORS F.900F.999 For further details, please refer to the list of ITU-T Recommendations. Rec. ITU-T F.746.6 (12/2017) i Recommenda
6、tion ITU-T F.746.6 Requirements for a name resolution service in information-centric networks Summary Recommendation ITU-T F.746.6 describes the requirements for a flexible name resolution service in information-centric networks (ICN). It also describes the functional modules, i.e., name resolution
7、service access control module, namespace management module, interoperation module and resolution engine module, of name resolution service in ICN. The name resolution service can support name resolution for any particular ICN instance independently. It also can facilitate interoperation between ICN
8、instances with their own namespaces. History Edition Recommendation Approval Study Group Unique ID* 1.0 ITU-T F.746.6 2017-12-14 16 11.1002/1000/13428 Keywords Information-centric networks, name resolution. * To access the Recommendation, type the URL http:/handle.itu.int/ in the address field of yo
9、ur web browser, followed by the Recommendations unique ID. For example, http:/handle.itu.int/11.1002/1000/11830-en. ii Rec. ITU-T F.746.6 (12/2017) FOREWORD The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and co
10、mmunication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis.
11、 The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resoluti
12、on 1. In some areas of information technology which fall within ITU-Ts purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. NOTE In this Recommendation, the expression “Administration“ is used for conciseness to indicate both a telecommunication administration and
13、 a recognized operating agency. Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are me
14、t. The words “shall“ or some other obligatory language such as “must“ and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. INTELLECTUAL PROPERTY RIGHTSITU draws attention to the possibi
15、lity that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Rec
16、ommendation development process. As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest informati
17、on and are therefore strongly urged to consult the TSB patent database at http:/www.itu.int/ITU-T/ipr/. ITU 2018 All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. Rec. ITU-T F.746.6 (12/2017) iii Table of Content
18、s Page 1 Scope . 1 2 References . 1 3 Definitions 1 3.1 Terms defined elsewhere 1 3.2 Terms defined in this Recommendation . 2 4 Abbreviations and acronyms 2 5 Conventions 2 6 Motivation . 2 7 Functional modules of name resolution service in ICN . 3 7.1 Name resolution service access control module
19、. 3 7.2 Namespace management module . 3 7.3 Interoperation module 4 7.4 Resolution engine module 4 8 Requirements for name resolution service in ICN . 4 8.1 General requirements 4 8.2 Requirements for NRS access control module . 4 8.3 Requirements for namespace management module . 4 8.4 Requirements
20、 for interoperation module 4 8.5 Requirements for resolution engine module . 5 9 Security consideration 5 Annex A Scenarios for name resolution services in ICN . 6 A.1 Scenario of providing name resolution service for two ICN instances independently . 6 A.2 Scenario of providing name resolution serv
21、ice for interoperation between two ICN instances . 6 Appendix I Survey of name resolution schemes used in Internet and information-centric networks 8 Bibliography. 9 Rec. ITU-T F.746.6 (12/2017) 1 Recommendation ITU-T F.746.6 Requirements for a name resolution service in information-centric networks
22、 1 Scope This Recommendation describes the requirements for a flexible name resolution service for information-centric networks (ICN). It defines the key functional modules for name resolution service in ICN. This Recommendation covers the following: capabilities of name resolution service in ICN; r
23、equirements for name resolution service in ICN; scenarios of name resolution service for ICN instances. 2 References The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publica
24、tion, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the
25、currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. ITU-T F.746.4 Recommendation ITU-T F.746.4 (2017), Requirements for deployment of information-centric netw
26、orks. ITU-T Y.3033 Recommendation ITU-T Y.3033 (2014), Framework of data aware networking for future networks. 3 Definitions 3.1 Terms defined elsewhere This Recommendation uses the following term defined elsewhere: 3.1.1 future network (FN) b-ITU-T Y.3001: A network able to provide services, capabi
27、lities, and facilities difficult to provide using existing network technologies. A future network is either: a) A new component network or an enhanced version of an existing one, or b) A heterogeneous collection of new component networks or of new and existing component networks that is operated as
28、a single network. NOTE 1 The plural form “Future Networks“ (FNs) is used to show that there may be more than one network that fits the definition of a future network. NOTE 2 A network of type b may also include networks of type a. NOTE 3 The label assigned to the final federation may, or may not, in
29、clude the word “future“, depending on its nature relative to any preceding network and similarities thereto. NOTE 4 The word “difficult“ does not preclude some current technologies from being used in future networks. NOTE 5 In the context of this Recommendation, the word “new“ applied to a component
30、 network means that the component network is able to provide services, capabilities, and facilities that are difficult or impossible to provide using existing network technologies. 2 Rec. ITU-T F.746.6 (12/2017) 3.2 Terms defined in this Recommendation This Recommendation defines the following term:
31、 3.2.1 name resolution: The process by which, given an initial name and an initial naming context, an association between a name and the entity designated by the initial name can be found (adapted from b-ITU-T X.902). NOTE The name resolution process does not necessarily provide sufficient informati
32、on to interact with the designated entity. 4 Abbreviations and acronyms This Recommendation uses the following abbreviations and acronyms: DNS Domain Name System GNRS Global Name Resolution Service GUID Globally Unique Identifier ICN Information-Centric Networks NAT Network Address Translation NDN N
33、amed Data Networking NRS Name Resolution Service 5 Conventions In this Recommendation: The expression “is required to“ indicates a requirement which must be strictly followed and from which no deviation is permitted if conformance to this Recommendation is to be claimed. The expression “is recommend
34、ed“ indicates a requirement which is recommended but not absolutely required. Thus, this requirement need not be present to claim conformance. The keywords “can optionally“ indicate an optional requirement which is permissible, without implying any sense of being recommended. This term is not intend
35、ed to imply that the vendors implementation must provide the option and the feature can be optionally enabled by the network operator / service provider. Rather, it means the vendor may optionally provide the feature and still claim conformance with the specification. 6 Motivation Information-centri
36、c networks (ICN) is a promising technology for future Internet design with which a user can directly obtain a content object by its name (or identification) without specifying the location of the content object. In recent years, various ICN solutions have been proposed with their own namespaces such
37、 as named data networking (NDN) b-Jacobson, MobilityFirst b-Seskar and publish subscribe Internet technology (PURSUIT) b-Fotiou. To identify different objects from their associated names, a name resolution service is needed. Different name resolution schemes are adopted for different ICN solutions,
38、such as the rendezvous system in PURSUIT b-Fotiou and global name resolution service (GNRS) system in MobilityFirst b-Seskar. Various name resolution schemes differ from each other from the perspectives of resolution policies and management mechanisms. The comparison of resolution policies and manag
39、ement mechanisms among various existing name resolution schemes in the current Internet and ICN are shown in Table I.1 (see Appendix I). Rec. ITU-T F.746.6 (12/2017) 3 As described in ITU-T F.746.4, each solution has its own pros and cons and is best suited to some particular application requirement
40、s. Different ICN service providers may deploy their own ICN instances with their own namespaces on top of the same physical network. To support the coexistence of various ICN instances on the same physical network, and to enable the potential interoperation among different ICN instances that employ
41、different namespaces, a flexible name resolution service for information-centric networks is needed. This name resolution service provides dynamic resolution that allows the administrator of ICN instances to flexibly specify namespaces with their private naming schemes and resolution policies. Furth
42、ermore, this name resolution service is required to support any particular ICN instance independently, which means that internal-mapping relationships between multiple namespaces of the same ICN instance are maintained independently. It is also recommended that this name resolution service facilitat
43、e interoperation between different ICN instances with their own namespaces, which means the cross-mapping relationships between the multiple namespaces belonging to different ICN instances will be maintained. 7 Functional modules of name resolution service in ICN As shown in Figure 7-1, the name res
44、olution service in ICN includes four functional modules: name resolution service (NRS) access control module, namespace management module, resolution engine module and interoperation module. This clause addresses the capabilities of these functional modules. Figure 7-1 Functional modules of name res
45、olution service 7.1 Name resolution service access control module The NRS access control module offers the capabilities of authentication and authorization. As there are multiple ICN instances coexisting in the same physical network, to safeguard the sensitive namespace information of each ICN insta
46、nce, the administrators of the ICN instances must be authenticated and authorized to explore the capabilities provided by the namespace management module and interoperation module. 7.2 Namespace management module The namespace management module is responsible for enabling the administrators of ICN i
47、nstances flexibly to manage their own namespaces and specify their resolution policies. With this module, an administrator of the ICN instance can define namespaces with a particular naming scheme and indicate the scope of the namespace based on their design principles. The administrator can also cr
48、eate and update the names and the internal-mapping relationships between multiple namespaces of the same ICN instance. 4 Rec. ITU-T F.746.6 (12/2017) 7.3 Interoperation module An object has different names in different ICN instances. The interoperation module maintains the cross-mapping relationship
49、s between the multiple namespaces belonging to different ICN instances. The administrator of the ICN instance can indicate objects to which access by other ICN instance(s) is allowed. The interoperation modules of different ICN instances exchange with each other the names of the objects that can be accessed by other ICN instance(s). 7.4 Resolution engine module The resolution engine module uses the information and polices maintained in the namespace management module and interoperation module to accompl
