1、 International Telecommunication Union ITU-T Y.3032TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (01/2014) SERIES Y: GLOBAL INFORMATION INFRASTRUCTURE, INTERNET PROTOCOL ASPECTS AND NEXT-GENERATION NETWORKS Future networks Configurations of node identifiers and their mapping with locators in futur
2、e networks Recommendation ITU-T Y.3032 ITU-T Y-SERIES RECOMMENDATIONS GLOBAL INFORMATION INFRASTRUCTURE, INTERNET PROTOCOL ASPECTS AND NEXT-GENERATION NETWORKS GLOBAL INFORMATION INFRASTRUCTURE General Y.100Y.199 Services, applications and middleware Y.200Y.299 Network aspects Y.300Y.399 Interfaces
3、and protocols Y.400Y.499 Numbering, addressing and naming Y.500Y.599 Operation, administration and maintenance Y.600Y.699 Security Y.700Y.799 Performances Y.800Y.899 INTERNET PROTOCOL ASPECTS General Y.1000Y.1099 Services and applications Y.1100Y.1199 Architecture, access, network capabilities and r
4、esource management Y.1200Y.1299 Transport Y.1300Y.1399 Interworking Y.1400Y.1499 Quality of service and network performance Y.1500Y.1599 Signalling Y.1600Y.1699 Operation, administration and maintenance Y.1700Y.1799 Charging Y.1800Y.1899 IPTV over NGN Y.1900Y.1999 NEXT GENERATION NETWORKS Frameworks
5、 and functional architecture models Y.2000Y.2099 Quality of Service and performance Y.2100Y.2199 Service aspects: Service capabilities and service architecture Y.2200Y.2249 Service aspects: Interoperability of services and networks in NGN Y.2250Y.2299 Enhancements to NGN Y.2300Y.2399 Network managem
6、ent Y.2400Y.2499 Network control architectures and protocols Y.2500Y.2599 Packet-based Networks Y.2600Y.2699 Security Y.2700Y.2799 Generalized mobility Y.2800Y.2899 Carrier grade open environment Y.2900Y.2999 FUTURE NETWORKS Y.3000Y.3499CLOUD COMPUTING Y.3500Y.3999 For further details, please refer
7、to the list of ITU-T Recommendations. Rec. ITU-T Y.3032 (01/2014) i Recommendation ITU-T Y.3032 Configurations of node identifiers and their mapping with locators in future networks Summary Recommendation ITU-T Y.3032 specifies the formats of node names and IDs, as well as their configuration method
8、. It then specifies the node names to IDs and locators mapping records storage and resolution mechanisms. History Edition Recommendation Approval Study Group Unique ID*1.0 ITU-T Y.3032 2014-01-13 13 11.1002/1000/12075-en Keywords Future networks, ID/locator mapping, ID/locator split, locators, node
9、ID. _ *To access the Recommendation, type the URL http:/handle.itu.int/ in the address field of your web browser, followed by the Recommendations unique ID. For example, http:/handle.itu.int/11.1002/1000/11830-en. ii Rec. ITU-T Y.3032 (01/2014) FOREWORD The International Telecommunication Union (ITU
10、) is the United Nations specialized agency in the field of telecommunications, information and communication 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 issu
11、ing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. 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 top
12、ics. The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 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
13、 “Administration“ is used for conciseness to indicate both a telecommunication administration and 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)
14、 and compliance with the Recommendation is achieved when all of these mandatory provisions are met. 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 Recomm
15、endation is required of any party. INTELLECTUAL PROPERTY RIGHTS ITU draws attention to the possibility 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
16、claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation 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 Re
17、commendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at http:/www.itu.int/ITU-T/ipr/. ITU 2014 All rights reserved. No part of this publication may be reproduced, by any means whatsoev
18、er, without the prior written permission of ITU. Rec. ITU-T Y.3032 (01/2014) iii Table of Contents 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 Abbreviation and acronyms 2 5 Conventions 2 6 Overview 3 7 Node names and ide
19、ntifiers 3 8 Locators 5 9 Node name to node ID and locator mapping storage and name resolution method . 5 9.1 DNR and HNR records registration and update procedure 6 9.2 Node name to node ID and locator mapping record retrieval procedure . 7 10 Environmental considerations 8 11 Security consideratio
20、ns . 9 Bibliography. 10 Rec. ITU-T Y.3032 (01/2014) 1 Recommendation ITU-T Y.3032 Configurations of node identifiers and their mapping with locators in future networks 1 Scope The scope of this Recommendation includes the following items: overview of node names, node IDs and locators for future netw
21、orks consideration of node name and node ID configuration specification of node name to node ID and locator mapping storage and resolution methods. 2 References The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of
22、 this Recommendation. At the time of publication, 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 o
23、ther references listed below. A list of the 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 Y.2015 Recommendation ITU-T Y.2015 (2009), General requi
24、rements for ID/locator separation in NGN. ITU-T Y.2022 Recommendation ITU-T Y.2022 (2011), Functional architecture for the support of host-based separation of node identifiers and routing locators in next generation networks. ITU-T Y.2057 Recommendation ITU-T Y.2057 (2012), Framework of node identif
25、ier and locator separation in IPv6-based next generation networks. ITU-T Y.3001 Recommendation ITU-T Y.3001 (2011), Future networks: Objectives and design goals. ITU-T Y.3021 Recommendation ITU-T Y.3021 (2012), Framework of energy saving for future networks. ITU-T Y.3031 Recommendation ITU-T Y.3031
26、(2012), Identification framework in future networks. 3 Definitions 3.1 Terms defined elsewhere This Recommendation uses the following terms defined elsewhere: 3.1.1 future network (FN) ITU-T Y.3001: A network able to provide services, capabilities and facilities difficult to provide using existing n
27、etwork 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 a single network. 3.1.2 identifier b-ITU-T Y.2091: An identi
28、fier is a series of digits, characters and symbols or any other form of data used to identify subscriber(s), user(s), network element(s), function(s), 2 Rec. ITU-T Y.3032 (01/2014) network entity(ies) providing services/applications, or other entities (e.g., physical or logical objects). 3.1.3 locat
29、or (LOC) ITU-T Y.2015: A locator is the network layer topological name for an interface or a set of interfaces. LOCs are carried in the IP address fields as packets traverse the network. NOTE In this Recommendation, locators are also referred to as location IDs. 3.1.4 node ID ITU-T Y.2015: A node ID
30、 is an identifier used at the transport and higher layers to identify the node as well as the endpoint of a communication session. A node ID is independent of the node location as well as the network to which the node is attached so that the node ID is not required to change even when the node chang
31、es its network connectivity by physically moving or simply activating another interface. The node IDs should be used at the transport and higher layers for replacing the conventional use of IP addresses at these layers. A node may have more than one node ID in use. NOTE This Recommendation specifies
32、 a node ID structure. 3.2 Terms defined in this Recommendation This Recommendation defines the following terms: 3.2.1 node: A node is a connection point that may be a network device, a user terminal or a process where data can be transmitted, received or forwarded. A node is identified by the node n
33、ame or node ID. 3.2.2 node name: A node name is a string of alphanumeric characters and symbols that is used to uniquely identify the node. A node name, which may have variable length, is usually configured in such a way that it would be easier to be read and remembered by humans. NOTE Node names ma
34、y also consist of human non-readable bit strings. 4 Abbreviation and acronyms This Recommendation uses the following abbreviations and acronyms: DHCP Dynamic Host Configuration Protocol DNR Domain Name Registry DNS Domain Name System FN Future Network HNR Host Name Registry ID Identifier NGN Next Ge
35、neration Network 5 Conventions None. Rec. ITU-T Y.3032 (01/2014) 3 6 Overview The base document for future networks (FNs), Recommendation ITU-T Y.3001, recommends that FNs provide a new identification structure to effectively support mobility and data access in a scalable manner. For mobility suppor
36、t, the node ID and node locator should not be embedded in the same number or value (see ITU-T Y.2015). That is, the node IDs and locators should be derived from different namespaces. A node should be able to change its locator without changing its ID. That is, the node ID to locator mapping should b
37、e able to be updated dynamically. Similarly for scalable data access, FNs should facilitate the storing or caching of data closer to a user and they should optimize data access by avoiding the same piece of data traversing the same link in the network multiple times. For this purpose, data need to b
38、e uniquely identified using a new identification scheme so that the network can use data identifiers for discovering, caching and routing. In addition to node IDs and data IDs, other IDs such as service IDs and user IDs would also be important for FNs. ITU-T Y.3031 has been accordingly developed rec
39、ently for specifying the identification framework and generic requirements for new identifiers in future networks. However, ITU-T Y.3031 does not recommend any specific ID structure or ID configuration and mapping mechanisms. Therefore, to complement ITU-T Y.3031, this Recommendation specifies node
40、names, node IDs, and their configuration methods and mapping with locators. Data ID formats and ID configuration methods will be specified by future Recommendations. The detailed specification of node names and node IDs is essential as future network research is highlighting the importance of the ID
41、/locator split-based design approach. In this approach, communication devices are assigned with their IDs and locators from different namespaces in order to overcome the limitations of the current Internet, which uses IP addresses as both IDs and locators, in supporting mobility, multi-homing, secur
42、ity and scalable routing. For introducing ID/locator split functions in NGN, ITU-T has already developed Recommendations ITU-T Y.2015, ITU-T Y.2022 and ITU-T Y.2057. Although these Recommendations mention the requirements of node IDs and locators and the functional architecture for using them in NGN
43、, they do not mention the format of node IDs and their configuration method. This Recommendation fills that gap. Moreover, this Recommendation also specifies a method for binding node IDs with locators. ITU-T Y.2022 and ITU-T Y.2057 mention the use of ID/locator binding or the mapping storage functi
44、on for storing and providing the node ID to locator mappings, but they lack the detailed architecture of the mapping storage system. This Recommendation fills this gap as well by introducing two types of mapping registries: host name registry (HNR) and domain name registry (DNR). The relationship be
45、tween the node ID and locator may be either temporary or persistent or both, depending on the type of locator and the communication environment. For example, in a mobile network, a node has a temporary locator which changes as the mobile node moves and attaches to a different network. Similarly, one
46、 node ID may relate to two or more locators at the same time, e.g., a node ID can be mapped to different locators if the node is multi-homed. 7 Node names and identifiers This clause presents a method for the configuration of node names and IDs. A node name and a node ID play similar roles in that t
47、hey both identify the node. The differences lie in their structures and usage. Node names are usually denoted by a variable-length string of alphanumeric characters and symbols, which may have some semantics so that they can be easily read and remembered by humans. Node IDs are usually denoted by st
48、rings of bits or alphanumeric characters that may not be easily memorized by humans. Node names are used during a communication initialization process to find node IDs and locators. On the other hand, node IDs are used as control information in communication protocols and packet headers to identify
49、sessions, packets, or communication endpoints. 4 Rec. ITU-T Y.3032 (01/2014) Y.3032(14)_F01Global node nameConcatenation functionNode ID Hash functionLocal node name Domain name*in hexadecimal notation(e.g., home )-pcParameterHash valuePrefixScopeVersion(e.g., )public key#(e.g., )mydomain.org(e.g., )home-pc#mydomain.org(e.g., 5645-4554-200101(e.g., 5645-4554-2001-1101-eid5-d483-911a-6f78-906a*)Concatenation function11eid5-d483-911a-6f78-906a*)Figure 1 Possible node name an
