idnits 2.17.1 draft-sun-dmm-ondemand-cp-orchestration-01.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 : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (October 22, 2018) is 2007 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Outdated reference: A later version (-14) exists of draft-ietf-dmm-fpc-cpdp-12 Summary: 0 errors (**), 0 flaws (~~), 2 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 DMM WG K. Sun 2 Internet Draft Y. Kim 3 Intended status: Informational S. Jeon 4 Expires: March 2019 Soongsil Univ. 5 October 22, 2018 7 On-demand DMM control plane orchestration 8 draft-sun-dmm-ondemand-cp-orchestration-01.txt 10 Abstract 11 This document describes the required functionalities of mobility 12 controller in the management and orchestration perspective for the 13 on-demand DMM service. 15 Status of this Memo 16 This Internet-Draft is submitted in full conformance with the 17 provisions of BCP 78 and BCP 79. 18 Internet-Drafts are working documents of the Internet Engineering 19 Task Force (IETF). Note that other groups may also distribute 20 working documents as Internet-Drafts. The list of current Internet- 21 Drafts is at https://datatracker.ietf.org/drafts/current/. 23 Internet-Drafts are draft documents valid for a maximum of six 24 months and may be updated, replaced, or obsoleted by other documents 25 at any time. It is inappropriate to use Internet-Drafts as 26 reference material or to cite them other than as "work in progress." 28 This Internet-Draft will expire on March 21, 2019. 30 Copyright Notice 32 Copyright (c) 2018 IETF Trust and the persons identified as the 33 document authors. All rights reserved. 34 This document is subject to BCP 78 and the IETF Trust's Legal 35 Provisions Relating to IETF Documents 36 (https://trustee.ietf.org/license-info) in effect on the date of 37 publication of this document. Please review these documents 38 carefully, as they describe your rights and restrictions with 39 respect to this document. Code Components extracted from this 40 document must include Simplified BSD License text as described in 41 Section 4.e of the Trust Legal Provisions and are provided without 42 warranty as described in the Simplified BSD License. 44 Table of Contents 46 1. Introduction ................................................ 2 47 2. Terminologies ............................................... 3 48 3. DMM Service Management by Mobility Controller ............... 3 49 3.1. DMM Service Instantiation .............................. 3 50 3.2. DMM Service Modification ............................... 3 51 3.3. DMM Service Release .................................... 5 52 4. DMM Service Orchestration by Mobility Controller ............ 5 53 4.1. DMM Service Description ................................ 5 54 4.2. CP/DP Selection ........................................ 5 55 4.3. DMM Service Monitoring ................................. 5 56 5. Security Considerations ..................................... 6 57 6. IANA Considerations ......................................... 6 58 7. References .................................................. 6 59 7.1. Normative References ................................... 6 60 7.2. Informative References ................................. 6 61 8. Acknowledgments ............................................. 6 63 1. Introduction 65 The DMM deployment models draft presents available DMM deployment 66 models and architectural considerations [I-D.ietf-dmm-deployment- 67 models]. One of the deployment models is with the on-demand control 68 plane orchestration mode, which allows control-plane agent/node, 69 i.e., CPA/CPN to be assigned and selected on demand. The potential 70 of the on-demand control plane orchestration mode is to facilitate 71 DMM-as-a-Service (DMMaaS) that meets diverse needs of service 72 operators and enterprise, not being limited to the provision of 73 uniform DMM Services. 75 The main component in the on-demand control plane orchestration mode 76 is the Mobility Controller, which is in charge of determining and 77 assigning appropriate control plane nodes while orchestrating them 78 by taking into consideration mobility-centric control plane 79 requirements and issues. 81 In this draft, we specify the functionality of Mobility Controller, 82 in the management and orchestration perspective. In the management, 83 the requirements for DMM Service initiation, DMM Service 84 modification, DMM Service release are described. In the 85 orchestration, the requirements for DMM Service description, CP/DP 86 selection for DMM Service and DMM Service monitoring are described. 88 2. Terminologies 90 This document is based on terminologies defined in 91 [I-D.ietf-dmm-deployment-models], [I-D.ietf-dmm-fpc-cpdp]. 92 In addition, following term is defined as follows. 94 DMM Service: Description of the relationship between DMM control 95 plane and data plane components and configurations for providing 96 mobility service to specific user group or tenant network. DMM 97 service functions can be implemented stand-alone service or combined 98 with other functions (e.g. gateway functions which is not related to 99 mobility). Multiple DMM Service can be deployed in a network domain. 101 3. DMM Service Management by Mobility Controller 103 This section describes DMM Service management in terms of DMM 104 Service instantiation, DMM Service modification, DMM Service 105 release, based on an operational procedure shown in Fig. 1. 107 3.1. DMM Service Instantiation 109 Once Mobility Controller launches a DMM Service, it should determine 110 necessary control plane functions for the requested DMM Service and 111 let them get ready for running the operation. The control plane 112 functions should be newly instantiated or chosen with already 113 running ones. For the service instantiation, several steps should be 114 checked and determined. First, an interface between Home-CPA and 115 Access-CPN should be determined, i.e., choosing what control plane 116 protocol to be used. It can be determined based on a DMM Service 117 template chosen from a DMM Service description repository. Suppose 118 that the Home-CPA and Access-CPN are with the FPC interface as a FPC 119 client, defined in [I-D.ietf-dmm-fpc-cpdp]. The Home-CPA and 120 Access-CPN configure the Home-DPN and Access-DPN via Routing 121 Controller working as a FPC agent. 123 3.2. DMM Service Modification 125 While DMM Service runs, Mobility Controller should be able to modify 126 the topology or connectivity between control plane functions. One of 127 the DMM Service modification examples is anchor switching, which can 128 be called CPA switching, replacing a failed Home-CPA or a Home-CPA 129 with a long routing distance from the mobile node (MN). Once 130 Mobility Controller detects a failure of Home-CPA, it should be able 131 to allocate a new Home-CPA function, which should then able to 132 retrieve mobility binding information and configuration parameters 133 from the previous Home-CPA. After the anchor switching procedure is 134 complete, interfacing the new Home-CPA with other CP and DP 135 functions (e.g. Access-CPN, Home-DPA) is required. 137 +----------+ +------------+ +------------+ +----------+ 138 | Mobility | | Home-CPA | | Access-CPN | | Routing | 139 |Controller| |(FPC Client)| | (FPC Agent)| |Controller| 140 +----------+ +------------+ +------------+ +----------+ 141 | | | | 142 Launching | | | 143 DMM Service | | | 144 | | | | 145 Select CP | | | 146 | | | | 147 | Home-CPA | | | 148 | Configuration| | | 149 +------------->| | | 150 | Access-CPN Configuration | | 151 +----------------------------->| | 152 | | CP Signaling | | 153 | |<------------->| | 154 | | | | 155 | | Home-DPA Configuration | 156 | +----------------------------->| 157 | | | Access-DPN | 158 | | | Configuration| 159 | | +------------->| 160 | | | | 161 | | | DP Configuration 162 | | | | 163 | | CP-DP Connection | 164 | |<---------------------------->| 165 | | CP-DP Connection| 166 | | |<------------>| 167 | DMM Service Launching Complete | 168 |<-------------+---------------+ | 169 | | | | 170 DMM Service | | | 171 Running | | | 172 | | | | 174 Figure 1. DMM Service Instantiation Procedure 176 3.3. DMM Service Release 178 For the DMM Service release, the Mobility Controller should request 179 the release of functional resource of the relevant DMM entities 180 while cleaning the information and parameters configured on them for 181 the DMM Service. Once the release request is received by the 182 Mobility Controller, the Home-CPA is required to stop location 183 tracking of the mobility sessions served and delete the information 184 related to MNs and IP sessions. Access-CPN is required to delete the 185 information related to MNs and IP sessions served. For the service 186 release of data plane nodes, the Mobility Controller is required to 187 request the initialization of forwarding state on the data plane 188 nodes such as Home-DPN and Access-DPN(s) to the Routing Controller. 190 4. DMM Service Orchestration by Mobility Controller 192 This section describes DMM Service orchestration in terms of DMM 193 Service description, CP/DP selection, DMM Service monitoring. 195 4.1. DMM Service Description 197 For the DMM service description, number of Home-CPA and Access-CPN, 198 DMM Service topology, protocols between control plane nodes should 199 be described in the chosen DMM service template. The Mobility 200 Controller should be able to understand a given DMM Service 201 description and translate it for the DMM Service configuration. For 202 example, DMM service description can be specified depended on types 203 of DP protocol(e.g. SRv6, ILA, etc.) or CP protocol(MIP, PMIP, etc.) 205 4.2. CP/DP Selection 207 The Mobility Controller is required to select appropriate CP/DP 208 functions, based on a requested DMM Service. The selection can be 209 based on an capabilities(e.g. protocol), operator's policy, optimal 210 path computation, handover performance such as lower latency, lower 211 packet loss, and so on. The current load information of CP/DP nodes 212 can also be considered for load balancing of the nodes. 214 4.3. DMM Service Monitoring 216 For the reliable DMM Service support, DMM Service monitoring is 217 essentially required. The monitoring includes the current routing 218 path whether it is optimized or not. Depending on determination of 220 routing path optimality, the Mobility Controller may be required to 221 reselect or relocate Home-CPA and Home-DPN functions, by an 222 appropriate measure, e.g., anchor switching procedure as described 223 in Section 3.2. 225 5. Security Considerations 227 TBD 229 6. IANA Considerations 231 TBD 233 7. References 235 7.1. Normative References 237 [I-D.ietf-dmm-deployment-models] Gundavelli, S. and Jeon, S., "DMM 238 Deployment Models and Architectural Considerations", 239 draft-ietf-dmm-deployment-models-04, May 2018. 241 [I-D.ietf-dmm-fpc-cpdp] Matsushima, S., Bertz, L., Liebsch, M., 242 Gundavelli, S., Moses, D. and Perkins, C., "Protocol for 243 Forwarding Policy Configuration (FPC) in DMM", draft-ietf- 244 dmm-fpc-cpdp-12, June 2018. 246 7.2. Informative References 248 8. Acknowledgments 249 Authors' Addresses 251 Kyoungjae Sun 252 Soongsil University 253 369 Sangdo-ro, Dongjak-gu 254 Seoul, Korea 256 Email: gomjae@dcn.ssu.ac.kr 258 Younghan Kim 259 Soongsil University 260 369 Sangdo-ro, Dongjak-gu 261 Seoul, Korea 263 Email: younghak@ssu.ac.kr 265 Seil Jeon 266 Soongsil University 267 369 Sangdo-ro, Dongjak-gu 268 Seoul, Korea 269 Email: sijeon@dcn.ssu.ac.kr