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 Y.3071 TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (03/2017) SERIES Y: GLOBAL INFORMATION INFRASTRUCTURE, INTERNET PROTOCOL ASPECTS, NEXT-GENERATION NETWORKS, INTERNET OF THINGS AND SMART CITIES Future networks Data awa
2、re networking (information centric networking) Requirements and capabilities Recommendation ITU-T Y.3071 ITU-T Y-SERIES RECOMMENDATIONS GLOBAL INFORMATION INFRASTRUCTURE, INTERNET PROTOCOL ASPECTS, NEXT-GENERATION NETWORKS, INTERNET OF THINGS AND SMART CITIES GLOBAL INFORMATION INFRASTRUCTURE Genera
3、l Y.100Y.199 Services, applications and middleware Y.200Y.299 Network aspects Y.300Y.399 Interfaces 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
4、Y.1000Y.1099 Services and applications Y.1100Y.1199 Architecture, access, network capabilities and resource 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 maintenan
5、ce Y.1700Y.1799 Charging Y.1800Y.1899 IPTV over NGN Y.1900Y.1999 NEXT GENERATION NETWORKS Frameworks 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: Interopera
6、bility of services and networks in NGN Y.2250Y.2299 Enhancements to NGN Y.2300Y.2399 Network management 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.29
7、00Y.2999 FUTURE NETWORKS Y.3000Y.3499 CLOUD COMPUTING Y.3500Y.3999 INTERNET OF THINGS AND SMART CITIES AND COMMUNITIES General Y.4000Y.4049 Definitions and terminologies Y.4050Y.4099 Requirements and use cases Y.4100Y.4249 Infrastructure, connectivity and networks Y.4250Y.4399 Frameworks, architectu
8、res and protocols Y.4400Y.4549 Services, applications, computation and data processing Y.4550Y.4699 Management, control and performance Y.4700Y.4799 Identification and security Y.4800Y.4899 Evaluation and assessment Y.4900Y.4999 For further details, please refer to the list of ITU-T Recommendations.
9、 Rec. ITU-T Y.3071 (03/2017) i Recommendation ITU-T Y.3071 Data aware networking (information centric networking) Requirements and capabilities Summary Recommendation ITU-T Y.3071 specifies the requirements and capabilities of data aware networking (DAN) to realize the use cases and scenarios descri
10、bed in Supplement 35 to the ITU-T Y-series Recommendations, which are expected to be major applications/services provided on DAN. One of the objectives reflecting emerging requirements for future networks is data awareness as specified in Recommendation ITU-T Y.3001. DAN is expected to have capabili
11、ties optimized to handle enormous amounts of data and to enable users to access desired data safely, easily, quickly and accurately, regardless of their location. DAN can be described as networking whose central aim is retrieving information, i.e., information centric networking (ICN). History Editi
12、on Recommendation Approval Study Group Unique ID* 1.0 ITU-T Y.3071 2017-03-29 13 11.1002/1000/13253 Keywords DAN, data awareness, data aware networking, future networks, ICN, information centric networking. * To access the Recommendation, type the URL http:/handle.itu.int/ in the address field of yo
13、ur web browser, followed by the Recommendations unique ID. For example, http:/handle.itu.int/11.1002/1000/11830-en. ii Rec. ITU-T Y.3071 (03/2017) FOREWORD The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and com
14、munication 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.
15、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 Resolutio
16、n 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
17、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 met
18、. 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 possibil
19、ity 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 Reco
20、mmendation 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 informatio
21、n and are therefore strongly urged to consult the TSB patent database at http:/www.itu.int/ITU-T/ipr/. ITU 2017 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 Y.3071 (03/2017) iii Table of Contents
22、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 Justification . 2 7 Requirements for DAN . 3 7.1 Forwarding . 3 7.2 Routing . 3 7.3 Mobility 3 7.4 Security . 4 7.5 Management
23、 . 4 7.6 Miscellaneous . 4 7.7 Use case specific . 5 8 Capabilities of DAN . 6 8.1 Configuration of DAN components . 6 8.2 Capabilities . 6 9 Security considerations . 8 10 Environmental considerations 8 Bibliography. 9 Rec. ITU-T Y.3071 (03/2017) 1 Recommendation ITU-T Y.3071 Data aware networking
24、(information centric networking) Requirements and capabilities 1 Scope This Recommendation specifies the requirements of data aware networking (information centric networking) derived from the use cases and scenarios described in b-ITU-T Y.Sup. 35. One of the objectives reflecting emerging requireme
25、nts for future networks is data awareness as specified in ITU-T Y.3001. This Recommendation identifies the capabilities to fulfil the requirements and describes the components including their corresponding capabilities. 2 References The following ITU-T Recommendations and other references contain pr
26、ovisions which, through reference in this text, constitute provisions of 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 poss
27、ibility of applying the most recent edition of the Recommendations and other 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 Recomm
28、endation. ITU-T Y.3001 Recommendation ITU-T Y.3001 (2011), Future networks: Objectives and design goals. ITU-T Y.3031 Recommendation ITU-T Y.3031 (2012), Identification framework in future networks. ITU-T Y.3033 Recommendation ITU-T Y.3033 (2014), Framework of data aware networking for future networ
29、ks. ITU-T Y.3034 Recommendation ITU-T Y.3034 (2015), Architecture for interworking of heterogeneous component networks in ID/locator split-based future networks. ITU-T M.3400 Recommendation ITU-T M.3400 (2000), TMN management functions. 3 Definitions 3.1 Terms defined elsewhere This Recommendation u
30、ses the following terms defined elsewhere: 3.1.1 access control b-ITU-T X.800: The prevention of unauthorized use of a resource, including the prevention of use of a resource in an unauthorized manner. 3.1.2 authorization b-ITU-T X.800: The granting of rights, which includes the granting of access b
31、ased on access rights. 3.1.3 availability b-ITU-T X.800: The property of being accessible and useable upon demand by an authorized entity. 3.1.4 data ID ITU-T Y.3033: An identifier used to identify a data object. It has a form of a series of digits, characters and symbols or any of these combination
32、s, which generally do not have any meaning. NOTE In this Recommendation, the terms “data ID“ and “ID“ are used interchangeably. 2 Rec. ITU-T Y.3071 (03/2017) 3.1.5 data integrity b-ITU-T X.800: The property that data has not been altered or destroyed in an unauthorized manner. 3.1.6 data name ITU-T
33、Y.3033: A string of alpha-numeric characters that is used to identify the data object. A data 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 In this Recommendation, the terms “data name“, “NDO name“, and sim
34、ply “name“ are used interchangeably. 3.1.7 data origin authentication b-ITU-T X.800: The corroboration that the source of data received is as claimed. 3.1.8 named data object (NDO) b-ITU-T Y.Sup. 35: A data object that is identifiable by a name. 3.1.9 peer-entity authentication b-ITU-T X.800: The co
35、rroboration that a peer entity in an association is the one claimed. 3.2 Terms defined in this Recommendation This Recommendation defines the following terms: 3.2.1 DAN element: A network component that forwards messages to producers, consumers, and other data aware networking (DAN) elements. 3.2.2
36、DAN realm: A set of data aware networking (DAN) elements operated under one DAN realization and managed by an organization. Different DAN realms may adopt different DAN realizations such as naming convention, communication models including push and pull models and name resolution mechanisms. 3.2.3 N
37、DO consumer: A component that makes requests on named data objects (NDOs). 3.2.4 NDO producer: A component holding named data objects (NDOs) and make them reachable by corresponding requests. An NDO producer may be an actual owner of the NDO or a delegate of the actual owner. 4 Abbreviations and acr
38、onyms This Recommendation uses the following abbreviations and acronyms: APL Application DAN Data Aware Networking ICN Information Centric Networking ID Identifier NDO Named Data Object 5 Conventions None. 6 Justification It is essential to define the capabilities of DAN to bring its concept into re
39、ality. Several use case scenarios for DAN have been introduced in b-ITU-T Y.Sup. 35, which can be realized in different ways, e.g., with different combinations of capabilities. This aspect encourages the identification of the capabilities of DAN to realize various use case scenarios. Rec. ITU-T Y.30
40、71 (03/2017) 3 For this reason, this Recommendation intends to specify the requirements of DAN that are derived from the use case scenarios, and then defines its capabilities considering previously performed studies, such as those on communication based on name or identifier (ID) in ITU-T Y.3031 ITU
41、-T Y.3033 ITU-T Y.3034. Understanding the requirements and components of DAN enables the enrichment of the process of developing additional use case scenarios. 7 Requirements for DAN 7.1 Forwarding NDO name based forwarding function: It is required that a request be forwarded by attaching the name o
42、r ID of the NDO to the request. Request aggregation function: It is recommended that DAN elements be equipped with the function to aggregate requests to the same NDO to reduce network traffic and server load. Subscription: DAN is required to provide a mechanism for an NDO consumer to register descri
43、ption(s) to identify one or more NDOs that the consumer is interested in receiving when they are published. Publication: DAN is required to provide a mechanism for an NDO producer to publish NDOs to the network. The published NDOs may be distributed to consumers whose subscription matches the publis
44、hed NDOs. Packet forwarding loop avoidance function: DAN is required to have functions to avoid or resolve packet forwarding loops. 7.2 Routing NDO registration function: It is required that the unique name or ID of an NDO be registered to DAN so that NDO consumers can access the NDO with the name o
45、r ID. NDO location resolution function: DAN optionally provides the facility for a DAN element to ask for a forwarding direction when the DAN element cannot judge the forwarding direction of a request for an NDO. Advertisement function for the availability of NDOs: It is required that availability i
46、nformation of NDOs be disseminated to help in the choice of the correct direction of request forwarding. Network selection function for requests to reach an NDO: It is required that appropriate network interfaces be selected to forward requests in order to reach a specified NDO. 7.3 Mobility Consume
47、r mobility: DAN is required to provide a mechanism for a consumer to maintain undisrupted message flows while the consumer is in motion. NDO mobility: DAN is required to provide a mechanism for NDOs to re-locate without disrupting NDO availability when the NDOs change their locations. 4 Rec. ITU-T Y
48、.3071 (03/2017) Network mobility: DAN optionally provides an efficient mechanism for a network to maintain seamless network connection for its mobility. 7.4 Security Access control: It is required that DAN be equipped with a mechanism to examine and confirm the authenticity of consumers and that NDO
49、 be accessible only by the authorized consumers. Network security function from malicious attacks: DAN is required to have a mechanism to protect its functions from malicious network attacks. NDO availability: DAN is required to provide a mechanism to ensure that the NDOs published in networks are available for authorized consumers. NDO origin authentication: DAN is required to be equipped with a mechanism to examine and confirm the authenticity of the owners
