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.4 TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (03/2017) SERIES F: NON-TELEPHONE TELECOMMUNICATION SERVICES Multimedia services Requirements for deployment of information-centric networks Recommendation ITU-T F.746
2、.4 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 telex service F
3、.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 facsimile service F.16
4、0F.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.599 DATA TRANSMIS
5、SION 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.4 (03/2017) i Recommendation ITU-T F.74
6、6.4 Requirements for deployment of information-centric networks Summary Recommendation ITU-T F.746.4 describes the scenarios and requirements for deployment of information-centric networks (ICNs). The deployment supports flexible methods for deploying various ICN instances on a single network servic
7、e provider (NSP) network, deploying an ICN instance over multiple NSP networks, and interoperating between different ICN instances. The framework requires decoupling of the data plane and the control plane; in addition, one or more switches and controllers supporting such deployment are required. Th
8、e software and hardware resources in the switches and controllers are required to be virtualized and to be used to create ICN instances. There exist appropriate inter-ICN service provider interfaces to facilitate interoperations of two ICN instances. History Edition Recommendation Approval Study Gro
9、up Unique ID* 1.0 ITU-T F.746.4 2017-03-01 16 11.1002/1000/13179 Keywords Deployment, information-centric networks, interoperation, software-defined networking. * To access the Recommendation, type the URL http:/handle.itu.int/ in the address field of your web browser, followed by the Recommendation
10、s unique ID. For example, http:/handle.itu.int/11.1002/1000/11830-en. ii Rec. ITU-T F.746.4 (03/2017) FOREWORD The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telec
11、ommunication 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. The World Telecommunication Standardization A
12、ssembly (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 Resolution 1. In some areas of information technology
13、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 a recognized operating agency. Compliance wit
14、h 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. The words “shall“ or some other obligatory
15、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 possibility that the practice or implementation of th
16、is 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 Recommendation development process. As of the dat
17、e 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 information and are therefore strongly urged to consult
18、 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 F.746.4 (03/2017) iii Table of Contents Page 1 Scope . 1 2 References . 1 3 Definiti
19、ons 1 3.1 Terms defined elsewhere 1 3.2 Terms defined within this document 1 4 Abbreviations and acronyms 1 5 Convention 2 6 Background . 2 7 Requirements for the deployment of ICNs . 3 7.1 General requirements 3 7.2 Requirements for the switch supporting the deployment . 3 7.3 Requirements for the
20、controller supporting the deployment 3 8 A framework for deployment of an ICN 4 8.1 Switch supporting the deployment . 4 8.2 Controller supporting the deployment 5 9 Security considerations . 5 Annex A Scenarios of ICN deployment . 6 A.1 Scenario of a single ICN instance over multiple NSP networks 6
21、 A.2 Scenario of multiple ICN instances on a single NSP network . 7 A.3 Scenario of interoperation between ICN instances 8 Bibliography. 9 Rec. ITU-T F.746.4 (03/2017) 1 Recommendation ITU-T F.746.4 Requirements for deployment of information-centric networks 1 Scope This Recommendation describes the
22、 scenarios and requirements for deployment of information-centric networks (ICNs). The deployment supports flexible methods for deploying various ICN instances on a single network service provider (NSP) network, deploying an ICN instance over multiple NSP networks, and interoperating between differe
23、nt ICN instances. This Recommendation describes scenarios and common requirements for the deployment of ICNs. It also presents the framework for the deployment. This Recommendation covers the following: scenarios of the deployment of an ICN; requirements of the deployment of an ICN and its key compo
24、nents; framework for the deployment of an ICN. 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 publication, the editions indicated were valid. All Recommendati
25、ons 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 currently valid ITU-T Recommendations is regularly publis
26、hed. 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.3001 Recommendation ITU-T Y.3001 (2011), Future networks: Objectives and design goals. 3 Definitions 3.1 Terms defined elsewhere This Recommendation uses t
27、he following term defined elsewhere: 3.1.1 future network ITU-T Y.3001: A network able to provide services, capabilities, 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
28、 heterogeneous collection of new component networks or of new and existing component networks that is operated as a single network. 3.2 Terms defined within this document None. 4 Abbreviations and acronyms This Recommendation uses the following abbreviations and acronyms: API Application Programming
29、 Interface CONET Content Networking FN Future Network 2 Rec. ITU-T F.746.4 (03/2017) ICN Information-Centric Network NDN Named Data Networking NetInf Network of information NSP Network Service Provider PURSUIT PublishSubscribe Internet Technology SDN Software-Defined Networking 5 Convention In this
30、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 recommended“ indicates a requirement which is recommended but not absolutely req
31、uired. Thus this requirement need not be present to claim conformance. 6 Background In recent years, future networks (FNs) as described in ITU-T Y.3001 have attracted considerable attention from both academia and industry. One FN objective is data awareness, which enables retrieval of data regardles
32、s of their location. To achieve this objective, the concept of information-centric networks (ICNs) has been proposed together with various ICN architectures b-ITU-T Y.3033, b-Dannewitz, b-Jacobson, b-Srel, b-Seskar, b-Detti. The next major challenge is to convince network service providers (NSPs) ar
33、ound the globe to adopt the concept of ICN and to deploy ICN-enabled networks. To achieve this goal, many prototypes and testbeds have been developed. In general, these proof-of-concept systems can be implemented by two approaches: overlay and non-overlay. With the first approach, some special overl
34、ay nodes are deployed to deal with ICN protocol-related operations on top of an existing physical network. For example, overlay-based systems have been developed for named data networking (NDN) b-Jacobson and network of information (NetInf) b-Dannewitz. In contrast, in the non-overlay approach, ICN
35、functions are implemented in routers directly. For instance, the prototype of PublishSubscribe Internet Technology (PURSUIT) b-Srel has been developed based on the Click modular router b-Kohler, which allows network designers to create their own routers based on general-purpose personal computer har
36、dware. Besides that, some ICN projects, such as MobilityFirst b-Seskar and content networking (CONET) b-Detti, developed their prototypes based on software-defined networking (SDN), which provides programmability to networks. Despite the importance of these prototypes, the deployment of ICN is still
37、 an open question. One obvious reason is that there are too many ICN candidates, which have different design principles and various technical details in terms of naming, routing, and so on. Taking content access as an example, while most ICN architectures are based on the assumption that a user will
38、 initiate a request and expect to access the content object as soon as possible, the PURSUIT project is based on the publishsubscribe model, in which both publisher and subscriber register on the ICN, and the publisher can push content whenever it is generated. Clearly, these two approaches can be a
39、pplied by different types of application to optimize their performance. As each ICN architecture has its own pros and cons and is best suited to some particular application requirements, various ICN architectures will be adopted. On the other hand, different ICN service Rec. ITU-T F.746.4 (03/2017)
40、3 providers can also implement their own ICN instances to provide specific services for users. For instance, one ICN service provider provides streaming service and another ICN service provider provides instant message service. Thus, various ICN instances will coexist on top of the same physical net
41、work. Nevertheless, existing ICN prototypes only focus on the implementation of individual ICN architectures. Neither the coexistence of multiple ICN instances in the same physical network nor the requirement for interoperation of different ICN instances is considered. This Recommendation focuses on
42、 the issue of the deployment of ICNs, including the scenarios, requirements and framework. 7 Requirements for the deployment of ICNs 7.1 General requirements GEN-01: The deployment framework is required to decouple the data plane and the control plane. One or multiple switches and controllers suppor
43、ting such deployment are required. GEN-02: The deployment framework is required to virtualize the resources of network infrastructure to facilitate ICN implementation and coexistence. That is, the software and hardware resources in switches and controllers are required to be virtualized and to be pr
44、ovided to ICN instances. GEN-03: The deployment framework is required to define appropriate inter-ICN service provider interfaces to facilitate interoperations between two ICN instances. GEN-04: The deployment framework is required to provide basic general functions, including name-based routing, in
45、-network cache management and content-based security. 7.2 Requirements for the switch supporting the deployment DS-01: A switch is required to support general ICN-related operations and to process received packets according to the defined rules configured by control programs (i.e., ICN instances). T
46、he general ICN-related operations include name-based routing, in-network caching and content-based security. DS-02: A switch is required to provide the following primitive functions: forwarding packets and caching traversed content. DS-03: A switch is required to support virtualization for the imple
47、mentation and coexistence of multiple ICN instances in the data plane. That is, the forwarding table and storage of the switch require allocation to different ICN instances to guarantee the required service quality. Packets belonging to different ICN instances require delivery to the appropriate con
48、trol program and forwarding to appropriate interfaces. DS-04: A switch is required to provide interfaces for ICN instances to manipulate the allocated resources, including the forwarding table and storage. DS-05: A switch is recommended to provide the general ICN-related functions as modules. DS-06:
49、 A switch is recommended to support interoperation, including re-encapsulating packets and sending requests according to the rules configured by the control programs. 7.3 Requirements for the controller supporting the deployment DC-01: A controller is required to provide interfaces for an ICN service provider to deploy their own ICN instances in the control plane with full control of the physical resources. 4 Rec. ITU-T F.746.4 (03/2017) DC-02: A controller is required to support virtualization for the c
