idnits 2.17.1 draft-kim-nmrg-pdns-02.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: ---------------------------------------------------------------------------- == There are 4 instances of lines with non-ascii characters in the document. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** There are 20 instances of lines with control characters in the document. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == Line 75 has weird spacing: '...ficient manag...' -- The document date (October 2020) is 1288 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) -- Looks like a reference, but probably isn't: 'Figure 1' on line 136 -- Possible downref: Non-RFC (?) normative reference: ref. '1' -- Possible downref: Non-RFC (?) normative reference: ref. '2' -- Possible downref: Non-RFC (?) normative reference: ref. '3' -- Possible downref: Non-RFC (?) normative reference: ref. '4' Summary: 1 error (**), 0 flaws (~~), 3 warnings (==), 6 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 NMRG Kim, Seokhyun 2 Internet-Draft Samsung Electronics 3 Intended status: Standards Track Jang, Hyeonjoon 4 Expires: March 15, 2021 KAIST 5 October 2020 7 Software-Defined Networking based Policy Driven 8 Network Slicing System 9 draft-kim-nmrg-pdns-02 11 Abstract 13 With the advent of Software-Defined Networking(SDN), the network 14 environment has changed greatly to focus on users, and network 15 virtualization technology has made great progress. However, networks 16 that are getting bigger and more advanced have become more and more 17 complex and difficult to use SDN. In such an environment, a network 18 system that users can easily access and use is required. 19 In this document we propose a more advanced policy-based network 20 virtualization system that allows users to select policies and 21 provide networks accordingly, rather than a system that simply 22 virtualizes a network and shares it with each user. 24 Status of this Memo 26 This Internet-Draft is submitted in full conformance with the 27 provisions of BCP 78 and BCP 79. 29 Internet-Drafts are working documents of the Internet Engineering 30 Task Force (IETF). Note that other groups may also distribute 31 working documents as Internet-Drafts. The list of current Internet- 32 Drafts is at http://datatracker.ietf.org/drafts/current/. 34 Internet-Drafts are draft documents valid for a maximum of six 35 months and may be updated, replaced, or obsoleted by other 36 documents at any time. It is inappropriate to use Internet-Drafts 37 as reference material or to cite them other than as 38 "work in progress." 40 This Internet-Draft will expire on March 15, 2021. 42 Copyright Notice 44 Copyright (c) 2020 IETF Trust and the persons identified as the 45 document authors. All rights reserved. 47 This document is subject to BCP 78 and the IETF Trust's Legal 48 Provisions Relating to IETF Documents 49 (http://trustee.ietf.org/license-info) in effect on the date of 50 publication of this document. Please review these documents 51 carefully, as they describe your rights and restrictions with respect 52 to this document. Code Components extracted from this document must 53 include Simplified BSD License text as described in Section 4.e of 54 the Trust Legal Provisions and are provided without warranty as 55 described in the Simplified BSD License. 57 Table of Contents 59 1. Introduction . . . . . . . . . . . . . . . . . . . .. . . . . . 2 60 2. SDN-based Network Virtualization. . . . . . . . . . . . . . . . 3 61 3. Policy-Driven Network Slicing using SDN. . . . . . . . . . . . . 3 62 4. IANA Considerations . . . . . . .. . . . . . . . . . . . . . . 4 63 5. Security Considerations . . . . . . . . . . . . . . . . . . . 4 64 6. References . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 65 6.1. Normative References . . . . . . . . . . . . . . . . . . . . . 4 66 6.2. Informative References . . . . . .. . . . . . . . . . . . . . 4 67 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 4 68 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . . 5 70 1. Introduction 72 Recently, the scale of the network is growing rapidly as more and more 73 various kinds of devices are being connected. Software-Defined 74 Networking(SDN) and network virtualization technology using SDN are 75 being studied as a technology for flexible and efficient management of 76 such networks, but the larger the networks, the network management with 77 SDN becomes more and more complex, which increases the burden on the 78 user. In this document, we propose a policy-based network virtualizati- 79 on system that delivers user packets according to a policy prepared in 80 advance by the network administrator for ease of use by users. 82 2. SDN-based Network Virtualization 84 Nowadays SDN has led the change from the existing producer-centered 85 networks to the user-centered networks[1]. After the advent of SDN-based 86 network virtualization technology such as Flowvisor[2], the gap between 87 the virtual network topology and the real network topology is reduced[3] 88 ,and the network users' conveniene were promoted by integrating the APIs 89 of the network controllers[4]. However, as the network grows network 90 management using SDN becomes more and more complex to respond to changes 91 in various situations(e.g., loop prevention, ...), which is no exception 92 to virtualized networks. As a result, users of the SDN network need a 93 lot of time and effort compared to the existing producer-centered 94 networks. 96 +----------------+ 97 | SDN Controller | 98 +----------------+ 99 Λ | 100 +--OpenvSwitch-----------------|---V--------------+ Packets 101 | +----------------+ +--------------------+ | Out 102 -----------> | Policy Checker |---->| Look up flow | ----------> 103 Packets in | +----------------+ +--------------------+ | 104 | | Λ Λ | | 105 | V | | V | 106 | +----------------+ +-----------+ +----------+ | 107 | | Packet | | Policy | | Marker | | 108 | | Classfier | | Marker | | Remover | | 109 | +----------------+ | Generator | +----------+ | 110 | | +-----------+ | 111 | | Λ | 112 | V | | 113 | +----------------------------------+ | 114 | | Policy Matcher | | 115 | +-------|----------------Λ---------+ | 116 +---------|----------------|----------------------+ 117 V | 118 +-----------------------------------+ 119 | Policy-Tenant Matching Database | 120 +-----------------------------------+ 122 Figure 1: Policy Driven Network Slicing System Architecture 124 3. Policy-Driven Network Slicing using SDN 126 Policy-Driven Network Slicing(PDNS) is designed to maximize the conveni- 127 ence of network users, which is and advantage of the existing producer 128 centered network, while ensuring the flexibility of the network using 129 SDN. A network administrator who provides a virtual network presents 130 various policies (ex. security level, topology, network function) that 131 users can use. Network users choose their own policy and use the 132 network. The administrator downloads and stores this user-specific 133 policy for each OVS, and delivers the user-specific packet to the 134 algorithm appropriate to the policy. 136 [Figure 1] shows a PDNS system where each switch in the network is 137 classified by matching the user's policy. For this classification, the 138 network adds a policy marker to the user's packet. When each switch 139 receives a packet, if the Policy Checker checks whether there is a 140 Policy Marker, it delivers the packet according to the corresponding 141 policy. If not, packet classifier analyzes which packet is, and policy 142 matcher compares it with user's DB to determine which policy, add 143 policy maker to packet, and deliver packet according to policy. 144 If there is a rule, the transmitted packet is transmitted according to 145 the rule, if not, it is transmitted to the controller and assigned the 146 rule. The controller refers to the policy marker of the received packet, 147 and if the packet is delivered from the network to the end user or 148 another network last in the relevant policy, it removes the policy 149 marker and delivers the packet. 151 4. IANA Considerations 153 There are no IANA considerations related to this document. 155 5. Security Considerations 157 There are no security considerations related to this document. 159 6. References 161 6.1. Normative References 163 [1] McKeown, Nick, et al. "OpenFlow: enabling innovation in campus 164 networks." ACM SIGCOMM Computer Communication Review 38.2 165 (2008): 69-74. 167 [2] Sherwood, Rob, et al. "Flowvisor: A network virtualization 168 layer." OpenFlow Switch Consortium, Tech. Rep 1 (2009): 13 170 [3] Corin, Roberto Doriguzzi, et al. "Vertigo: Network virtualizat 171 ion and beyond." Software Defined Networking (EWSDN), 2012 172 European Workshop on. IEEE, 2012 174 [4] Drutskoy, Dmitry, Eric Keller, and Jennifer Rexford. 175 "Scalable network virtualization in software-defined networks" 176 IEEE Internet Computing 17.2 (2013): 20-27. 178 6.2. Informative References 180 7. Acknowledgements 182 This work was supported by Institute for Information & communications 183 Technology Promotion(IITP) grant funded by the Korea government(MSIT) 184 (No.2015-0-00557, Resilient/Fault-Tolerant Autonomic Networking Based 185 on Physicality, Relationship and Service Semantic of IoT Devices) 186 Authors' Addresses 188 Seokhyun Kim 189 Samsung Electronics, 190 Suwon, South Korea 191 Phone: +82 (0)42 350 5473 192 Email: sh.kim@netsys.kaist.ac.kr 194 Hyeonjoon Jang 195 Electrical Engineering Department, 196 Korea Advanced Institute of Science and Technology(KAIST) 197 Daejeon, South Korea 198 Phone: +82 (0)42 350 5473 199 Email: thefelix@kaist.ac.kr