idnits 2.17.1 draft-cheng-teas-network-slice-usecase-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 76 instances of too long lines in the document, the longest one being 50 characters in excess of 72. ** The abstract seems to contain references ([I-D.ietf-teas-ietf-network-slice-definition]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == Line 225 has weird spacing: '...strator admi...' == Line 227 has weird spacing: '...perator moni...' == The document doesn't use any RFC 2119 keywords, yet seems to have RFC 2119 boilerplate text. -- The document date (February 20, 2021) is 1154 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Outdated reference: A later version (-01) exists of draft-ietf-teas-ietf-network-slice-definition-00 Summary: 2 errors (**), 0 flaws (~~), 5 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 IDR Working Group 3 Internet-Draft 4 Intended status: Informational W. Cheng 5 Expires: August 24, 2021 W. Jiang 6 China Mobile 7 R. Chen 8 ZTE Corporation 9 L. Gong 10 China Mobile 11 C. F 12 H3C Corporation 13 Sh. Peng 14 ZTE Corporation 15 February 20, 2021 17 IETF Network Slice use cases 18 draft-cheng-teas-network-slice-usecase-00 20 Abstract 22 This draft supplements the usecase described in 23 [I-D.ietf-teas-ietf-network-slice-definition] from the perspective of 24 the operator.In specific,it mainly includes two types of the network 25 slice customers from the perspective of operators: 27 o End-to-end slicing cloud-network collaboration 29 o The branch departments that use slices within the operator. 31 Status of This Memo 33 This Internet-Draft is submitted in full conformance with the 34 provisions of BCP 78 and BCP 79. 36 Internet-Drafts are working documents of the Internet Engineering 37 Task Force (IETF). Note that other groups may also distribute 38 working documents as Internet-Drafts. The list of current Internet- 39 Drafts is at https://datatracker.ietf.org/drafts/current/. 41 Internet-Drafts are draft documents valid for a maximum of six months 42 and may be updated, replaced, or obsoleted by other documents at any 43 time. It is inappropriate to use Internet-Drafts as reference 44 material or to cite them other than as "work in progress." 46 This Internet-Draft will expire on August 24, 2021. 48 Copyright Notice 50 Copyright (c) 2021 IETF Trust and the persons identified as the 51 document authors. All rights reserved. 53 This document is subject to BCP 78 and the IETF Trust's Legal 54 Provisions Relating to IETF Documents 55 (https://trustee.ietf.org/license-info) in effect on the date of 56 publication of this document. Please review these documents 57 carefully, as they describe your rights and restrictions with respect 58 to this document. Code Components extracted from this document must 59 include Simplified BSD License text as described in Section 4.e of 60 the Trust Legal Provisions and are provided without warranty as 61 described in the Simplified BSD License. 63 Table of Contents 65 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 66 2. Requirements notation . . . . . . . . . . . . . . . . . . . . 3 67 3. Network Slice use cases . . . . . . . . . . . . . . . . . . . 3 68 3.1. cloud-network service for enterprise . . . . . . . . . . 3 69 3.2. The branch departments that use slices within the 70 operator. . . . . . . . . . . . . . . . . . . . . . . . . 5 71 3.2.1. Network Slice resource management . . . . . . . . . . 5 72 3.2.2. Domain governance of network slice . . . . . . . . . 6 73 4. Security Considerations . . . . . . . . . . . . . . . . . . . 7 74 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7 75 6. Normative References . . . . . . . . . . . . . . . . . . . . 7 76 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 7 78 1. Introduction 80 [I-D.ietf-teas-ietf-network-slice-definition] defines the concept of 81 IETF network slices that provide connectivity coupled with a set of 82 specific commitments of network resources between a number of 83 endpoints over a shared network infrastructure and describes a number 84 of use-cases benefiting from network slicing including: 86 o 5G network slicing 88 o Network wholesale services 90 o Network sharing among operators 92 o NFV connectivity and Data Center Interconnect 94 In the document also clearly stated services that might benefit from 95 the network slices include but not limited to the above use-cases. 97 This document supplements two use-cases from the perspective of 98 operators. In specific, it mainly includes two types of the network 99 slice customers from the perspective of operators: 101 o End-to-end slicing cloud-network collaboration 103 o The branch departments that use slices within the operator. 105 2. Requirements notation 107 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 108 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 109 document are to be interpreted as described in [RFC2119]. 111 3. Network Slice use cases 113 3.1. cloud-network service for enterprise 114 +------------------------------------------+ 115 | Consumer higher level operation system | 116 +----------------| (e.g E2E network slice orchestrator) |-------------+ 117 | +------------------------------------------+ | 118 | A A | 119 | | | | 120 | | | | 121 | | | | 122 V V V V 123 |----------------| |-------------------| |-----------------| |-----------------| 124 | MAN Slice | | Edge Cloud | | Backbone Slice | | DC Slice | 125 | Controller | | Slice Controller | | Controller | | Controller | 126 |----------------| |-------------------| |-----------------| |-----------------| 127 | | | | 128 | | | | 129 V | V | 130 ............... | .................. | 131 : MAN : | : IP Backbone : V 132 CPE PE PE : | PE PE .............. 133 |----| |-----| |-----| | |-----| |-----| : DC Network : 134 | NS1o---|o---o|.--- |o---o|-------|-------------|o---o|----------|o---o|-----o : 135 | NS2o---|o---o|.\-- |o---o|-------|-------------|o---o|----------|o---o|-----o : 136 |----| |-----| \\ |-----| | |-----| |-----| :............: 137 : \\ : | : : 138 :.......\\....: | :................: 139 \\ V 140 \\ ................. 141 \ o Edge Cloud : 142 \o : 143 : : 144 : : 145 :...............: 146 Figure 1 148 A cloud-network service for enterprise will involve several domains, 149 each with its own controller. MAN, Edge Cloud, IP Backbone and DC 150 domains need to be coordinated in order to deliver a cloud-network 151 service for enterprise. 153 In Figure 1, the network operator has created two E2E network slices, 154 there are two types of traffic from the client, and each traffic is 155 mapped to different slice, which is NS1 and NS2.Each NS with its own 156 MAN, Edge Cloud, IP Backbone and DC network slices. The mechanism 157 used to establish network slices in different domains and map the 158 traffic to a network slice is outside the scope of this document. 160 3.2. The branch departments that use slices within the operator. 162 |---------------| |-----------------| |-------------| 163 | A network | | Backbone Slice | | N network | 164 | Controller | | Controller | | Controller | 165 |---------------| |-----------------| |-------------| 166 | | | 167 |------------------------------------|--------------------------------| 168 | | .---------------------------------------. | | 169 | | / IP Backbone Network \ | | 170 | | \ / | | 171 | | `---------------------------------------' | | 172 | -------| |--------| | 173 | .-------------. .-------------. | 174 | / sub-company A \ / sub-company N \ | 175 | \ network / ...... \ network / | 176 | `-------------' `-------------' | 177 | Operator IP network | 178 |---------------------------------------------------------------------| 179 Figure 2 181 There are multiple sub-company network and IP Backbone network in an 182 operator IP network, each with its own slice controller. Sub-company 183 network can be the branches of the operator using slices. 185 IP Backbone network slice is orchestrated by the IP Backbone network 186 orchestrator, and the path is calculated through the IP Backbone 187 network slice controller. 189 For network slicing inside the local branch (sub-company network in 190 the figure) is orchestrated through the orchestrator of the sub- 191 company network. The sub-company network slice controller performs 192 unified control and path calculation for the sub-company network. 193 The path calculation and control of slices related to the IP Backbone 194 are sent to the IP Backbone network slice controller through the 195 eastbound and westbound interfaces, and the IP Backbone network slice 196 controller controls and calculates the path. 198 3.2.1. Network Slice resource management 199 |-----------------------------------------------------------------------------------------------| 200 | Resource Type | Orchestrator resource management | 201 |-----------------------------------------------------------------------------------------------| 202 | Slice ID | Unified resource orchestration and planning, plan Slice ID by sub-company. | 203 | | The orchestrator ensures that the IDs do not conflict with each other. | 204 |-----------------------------------------------------------------------------------------------| 205 | Node SID | Unified resource orchestration and planning. A unified coding mode is | 206 | | recommended. | 207 |-----------------------------------------------------------------------------------------------| 208 |SR Policy Color| Unified resource orchestration and planning, and resource pool allocation. | 209 |-----------------------------------------------------------------------------------------------| 210 | VPN name | Unified resource orchestration and planning. Perform unified resource conflict| 211 | | detection. VPN name within the same network element shall not be repeated. | 212 |-----------------------------------------------------------------------------------------------| 213 | VLAN sub-intf | Unified resource orchestration and planning: Resources are divided for VLAN | 214 | | sub-interfaces under the same physical interface. | 215 |-----------------------------------------------------------------------------------------------| 217 3.2.2. Domain governance of network slice 219 |----------------------------------------------------------------------------------------------| 220 | V 221 | |-------------------| .--------. 222 .--------. .---------. | V / Operation\ 223 / Operation\ / Role \-------| . --------------------------. \ Set / 224 \ Set / \ management/ . Security System . .--------. `--------' .--------. 225 `--------' `---------' . administrator administrator . / Role Set \ ...... / Role Set \ 226 A A | / \------> \ A / \ N / 227 | | |--------| \ Maintainer Operator monitor / ` -------' ` -------' 228 | | V . . /\ / | 229 | .--------. .---------. ` --------------------------' / \ / | 230 |--------/ Operation\ / User \ .------------------------. V V / V 231 \ Set / \ management/---> . All user User Group . .-----. .-----. V .-----. 232 `--------' `--------' / \--> / User \ / User \...... / User \ 233 \ Current / \ A / \ B / \ N / 234 . Login User Locked User . ` ----' ` ----' ` ----' 235 `-----------------------' | / \ | 236 V V \ V 237 .-------------. V .-------------. 238 / sub-company A \ ...... / sub-company N \ 239 \ network / \ network / 240 `-------------' `-------------' 242 Role-based user rights management uses the role template to quickly 243 allocate user rights, and provides network resources and sub-network 244 slice resources for different users. 246 4. Security Considerations 248 TBD 250 5. IANA Considerations 252 This document does not have any requests for IANA allocation. This 253 section may be removed before the publication of the draft. 255 6. Normative References 257 [I-D.ietf-teas-ietf-network-slice-definition] 258 Rokui, R., Homma, S., Makhijani, K., Contreras, L., and J. 259 Tantsura, "Definition of IETF Network Slices", draft-ietf- 260 teas-ietf-network-slice-definition-00 (work in progress), 261 January 2021. 263 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 264 Requirement Levels", BCP 14, RFC 2119, 265 DOI 10.17487/RFC2119, March 1997, 266 . 268 Authors' Addresses 270 Weiqiang Cheng 271 China Mobile 272 Beijing 273 CN 275 Email: chengweiqiang@chinamobile.com 277 Wenying Jiang 278 China Mobile 279 Beijing 280 CN 282 Email: jiangwenying@chinamobile.com 283 Ran Chen 284 ZTE Corporation 286 Email: chen.ran@zte.com.cn 288 Liyan Gong 289 China Mobile 290 Beijing 291 CN 293 Email: gongliyan@chinamobile.com 295 Chi Fan 296 H3C Corporation 298 Email: fanchi@h3c.com 300 Shaofu Peng 301 ZTE Corporation 303 Email: peng.shaofu@zte.com.cn