idnits 2.17.1 draft-liu-icn-implementation-sdn-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** There are 2 instances of too long lines in the document, the longest one being 4 characters in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (August 09, 2013) is 3885 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Unused Reference: 'RFC2119' is defined on line 252, but no explicit reference was found in the text == Unused Reference: 'DON' is defined on line 263, but no explicit reference was found in the text == Unused Reference: 'ICN' is defined on line 266, but no explicit reference was found in the text == Unused Reference: 'NBN' is defined on line 269, but no explicit reference was found in the text Summary: 1 error (**), 0 flaws (~~), 5 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group W. Liu 3 Internet-Draft Huawei Technologies 4 Intended status: Informational J. Ren 5 Expires: February 10, 2014 J. Wang 6 City University of Hong Kong 7 August 09, 2013 9 A Unified Framework for Software-Defined Information-Centric Network 10 draft-liu-icn-implementation-sdn-00 12 Abstract 14 This document aims at discussing some research issues about the 15 implementation of information-centric network (ICN) architectures. 16 Towards this end, we first review the implementation methods employed 17 by various ICNs and discuss the potential problems of these 18 implementations. Then we propose a unified framework for ICN 19 implementation based on Software-Defined Networking (SDN) technique 20 which can facilitate the implementation of any ICN architecture and 21 interoperability among different ICN architectures. 23 Status of This Memo 25 This Internet-Draft is submitted in full conformance with the 26 provisions of BCP 78 and BCP 79. 28 Internet-Drafts are working documents of the Internet Engineering 29 Task Force (IETF). Note that other groups may also distribute 30 working documents as Internet-Drafts. The list of current Internet- 31 Drafts is at http://datatracker.ietf.org/drafts/current/. 33 Internet-Drafts are draft documents valid for a maximum of six months 34 and may be updated, replaced, or obsoleted by other documents at any 35 time. It is inappropriate to use Internet-Drafts as reference 36 material or to cite them other than as "work in progress." 38 This Internet-Draft will expire on February 10, 2014. 40 Copyright Notice 42 Copyright (c) 2013 IETF Trust and the persons identified as the 43 document authors. All rights reserved. 45 This document is subject to BCP 78 and the IETF Trust's Legal 46 Provisions Relating to IETF Documents 47 (http://trustee.ietf.org/license-info) in effect on the date of 48 publication of this document. Please review these documents 49 carefully, as they describe your rights and restrictions with respect 50 to this document. Code Components extracted from this document must 51 include Simplified BSD License text as described in Section 4.e of 52 the Trust Legal Provisions and are provided without warranty as 53 described in the Simplified BSD License. 55 Table of Contents 57 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 58 2. ICN implementation . . . . . . . . . . . . . . . . . . . . . 3 59 2.1. ICN over IP . . . . . . . . . . . . . . . . . . . . . . . 3 60 2.2. ICN over L2 . . . . . . . . . . . . . . . . . . . . . . . 3 61 2.3. ICN over virtualized network . . . . . . . . . . . . . . 4 62 3. Software-Defined Networking . . . . . . . . . . . . . . . . . 4 63 4. A unified framework for software-defined information-centric 64 network . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 65 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6 66 6. Security Considerations . . . . . . . . . . . . . . . . . . . 6 67 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 6 68 7.1. Normative References . . . . . . . . . . . . . . . . . . 6 69 7.2. Informative References . . . . . . . . . . . . . . . . . 6 70 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 7 72 1. Introduction 74 To provide more efficient information dissemination, many studies are 75 driven to redesign the current Internet architecture. Information- 76 centric network (ICN) is one of these works. In ICN, the information 77 name is unique and independent of locations, applications, storages 78 and distribution approaches, which allows ubiquitous information 79 retrieval. 81 Based on this basic concept, many ICN architectures have been 82 proposed, for example, NDN [NDN], NetInf [NetInf], and the publish- 83 subscribe Internet (PSI) architecture [PSI]. To retrieve named 84 information, various advanced transmission techniques are introduced, 85 including name-based routing, name-based resolution, multicast and 86 etc. To fully support these techniques, dramatic changes to the 87 network devices deployed in current Internet are needed, which may 88 lead to challenge of ICNs implementation. 90 Typically, the ICN deployment schemes can be classified into three 91 categories: 1). ICN over IP, which encapsulate ICN protocol data in 92 IP (or UDP/TCP) packets or take ICN protocol information using IP 93 options; 2) ICN over L2, which completely replace IP layer and 94 directly use data link protocol (such as PPP, Ethernet, IEEE 802.x) 95 to deliver data between neighbors; 3) ICN over virtualized network, 96 which exploit network virtualization technologies, such as software- 97 defined networking (SDN), to implement ICNs. 99 Although these schemes have both advantages and disadvantages, most 100 works on ICN implementation focus on how to implement a particular 101 ICN architecture. However, different ICN architecture employ 102 different transmission techniques and packet format, which is not 103 easy for the co-existence and inter-operability of different ICNs. 104 Thus, a unified framework for ICN implementation is needed to fast 105 deploy different ICNs, which may further support the inter- 106 operability among different ICNs. 108 This document first surveys several implementation methods and aims 109 to analyze the advantages and disadvantages of these methods. Then, 110 we propose a unified framework for ICN implementation based on 111 Software-Defined Networking techniques, which can support fast 112 implementation of various ICNs . 114 2. ICN implementation 116 This section presents several implementation schemes. For each 117 scheme, existing papers are survey to analyze the advantages and 118 disadvantages. 120 2.1. ICN over IP 122 The most popular way is implementing ICNs as the overlay, in the same 123 way that Internet implement over the telecommunication network. For 124 example, the NDN prototype, CCNx, is implemented in an overlay on 125 existing IP networks. The advantage is that only a few nodes need to 126 be updated for supporting new ICN-related operations, which enables 127 fast deployment. The disadvantage of this scheme is the performance 128 of ICNs is limited as the performance can be affected by the 129 performance of the underlayer network. 131 2.2. ICN over L2 133 ICN over L2 means using ICN to replace IP layer. The prototype of 134 PURSUIT, blackadder, is implemented based on CLINK router and can be 135 run over Ethernet. It also design a new forwarding technique to 136 achieve efficient multicast with line speed. CRoWN introduces ICN 137 concept in Vehicular Ad hoc Networks [CRoWN]. It is implemented on 138 top of the IEEE 802.11p standard layers. The advantage is that ICN 139 can fully exploit the resource of underlayer networks can achieve 140 better performance. The disadvantage is that it is difficult to 141 widely deployment. 143 2.3. ICN over virtualized network 145 ICN over virtualized network is to exploit some virtualization 146 techniques for implementation. One of the potential techniques is 147 SDN. The main characteristic of SDN is the decoupling of control 148 plane and data plane, which makes the data plane much more simple and 149 elegant compared to the traditional networks. CONET, one of ICNs, is 150 implemented over OpenFlow (the most popular SDN instantiation) 151 [CONET]. The OpenFlow is extended to support ICN-related operations. 152 The advantage is that the decoupling enables the fast deployment of 153 ICNs with fully supporting ICNs features. However, existing works 154 focus on how to implement a particular ICN architecture. 156 3. Software-Defined Networking 158 Software-Defined Networking (SDN) is an emerging paradigm which 159 decouples the control plane that makes decision, including packets 160 routing and procession, from the data plane that forwards packets to 161 the desired destination [SDN]. With this separation, SDN allows 162 network administrators to specify more complex network services 163 (e.g., security, resource control, and prioritization) more easily 164 through the programmable central control of network traffic without 165 reprograming the underlying hardware devices. It also makes network 166 configurations easier to configure, manage, troubleshoot, and debug. 168 SDN has attracted significant attention in both the academia and the 169 industry. Many researches have been proposed to exploit SDN to 170 implement traffic engineering, security and so on, which is more 171 complex in traditional Internet. Many industry group, including Open 172 Networking Foundation (ONF) and IRTF Software-Defined Networking 173 Research Group (SDNRG), has been set up to lead the advancement of 174 SDN and standardizing critical elements of the SDN architecture. 175 There are some SDN pilots in industry. For example, Google has 176 implemented its inter-data center based on SDN. 178 4. A unified framework for software-defined information-centric network 180 This section describes the unified framework proposed in this paper 181 for enabling ICN implementation. This framework was designed as a 182 flexible solution and capable of modularizing ICN architecture. The 183 most important functions of ICNs are abstracted from various works 184 and modularized in the framework. 186 Figure 1 is the overview of our framework. The function modules are 187 extracted from various ICN proposals. 189 Please view in a fixed-width font such as Courier. 191 Please view in a fixed-width font such as Courier. 193 +----------------------+ +----------------------+ 194 | | | | 195 | ICN protocol A | | ICN protocol B | 196 | +------------------+ | | +------------------+ | 197 | | cache management | | | | optimization | | 198 | +------------------+ | | +------------------+ | 199 | | routing | | | | routing | | 200 | +------------------+ | | +------------------+ | 201 | |content management| | | |content management| | 202 Control | +------------------+ | | +------------------+ | 203 Program +----------------------+ +----------------------+ 204 ------------------------------------------------------------------------ 206 +---------------+ +----------------------+ 207 | Protocol | |Network Virtualization| 208 | | +----------------------+ 209 | Recognization | | Topology Management | 210 Controller +---------------+ +----------------------+ 211 ------------------------------------------------------------------------ 212 +------------------+ 213 Switch | +--------------+ | 214 +------------------+ | | Label Mapping| | 215 | +--------------+ | | +--------------+ | 216 | | Cache | | | | Cache | | 217 | +--------------+ | | +--------------+ | 218 | | Forwarding | | | | Forwarding | | 219 | +--------------+ | | +--------------+ | 220 | Switch | | Access Switch | 221 +------------------+ +------------------+ 223 the overview of the unified framework 225 Based on Software-Defined Networking, the proposed framework contains 226 three components: switch, controller and control programs. Switches 227 forward packets according to its flow entries and cache packet 228 following its cache policy. A special switch, called access switch, 229 can encapsulate the original ICN packet according to mapping rules 230 configured by the controller. (to do. The interface between switches 231 and the controller). The controller can collect the topology 232 information from switches to form a global map of the network and 233 then slice the network resource for different control program. The 234 controller will receive the packet which cannot be routed by the 235 switches. It can recognize the packet protocol and send the packet 236 to the corresponding control program. (to do). Each control program 237 implements a particular ICN protocol. It will receive the packet 238 from the controller and execute protocol-related operations. (to do). 240 5. IANA Considerations 242 This document makes no request of IANA. 244 6. Security Considerations 246 Security issues are not discussed in this memo. 248 7. References 250 7.1. Normative References 252 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 253 Requirement Levels", BCP 14, RFC 2119, March 1997. 255 7.2. Informative References 257 [CONET] L. Veltri, et al., ., "Supporting Information-Centric 258 Functionality in software defined networks", 2012. 260 [CRoWN] M. Amadeo, et al., ., "CRoWN: Content-Centric Networking 261 in Vehicular Ad Hoc Networks", 2012. 263 [DON] T. Koponen, et al., ., "A data-oriented (and beyond) 264 network architecture", 2007. 266 [ICN] B. Ahlgren, et al., ., "A survey of information-centric 267 networking", 2012. 269 [NBN] V. Jacobson, et al., ., "Networking named content", 2009. 271 [NDN] V, Jacobson, et al., ., "Networking named content", 2009. 273 [NetInf] C. Dannewitz, ., "NetInf: An Information-Centric Design 274 for the Future Internet", 2011. 276 [PSI] P. Jokela, et al., ., "LIPSIN: line speed publish/ 277 subscribe inter-networking", 2011. 279 [SDN] N. McKeown, et al., ., "OpenFlow: enabling innovation in 280 campus networks", 2008. 282 Authors' Addresses 284 Will(Shucheng) Liu 285 Huawei Technologies 286 Bantian, Longgang District 287 Shenzhen 518129 288 P.R. China 290 Email: liushucheng@huawei.com 292 Jing Ren 293 City University of Hong Kong 294 Tat Chee Avenue 295 Hong Kong 296 P.R. China 298 Email: jingren@cityu.edu.hk 300 JianPing Wang 301 City University of Hong Kong 302 Tat Chee Avenue 303 Hong Kong 304 P.R. China 306 Email: jianwang@cityu.edu.hk