idnits 2.17.1 draft-sijeon-dmm-deployment-models-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: ---------------------------------------------------------------------------- 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 doesn't use any RFC 2119 keywords, yet has text resembling RFC 2119 boilerplate text. -- The document date (March 21, 2016) is 2955 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) == Outdated reference: A later version (-14) exists of draft-ietf-dmm-fpc-cpdp-01 == Outdated reference: A later version (-09) exists of draft-bernardos-dmm-pmip-06 == Outdated reference: A later version (-06) exists of draft-matsushima-stateless-uplane-vepc-05 Summary: 0 errors (**), 0 flaws (~~), 5 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 DMM Working Group S. Jeon 3 Internet-Draft Instituto de Telecomunicacoes 4 Intended status: Standards Track Y. Kim 5 Expires: September 22, 2016 Soongsil University 6 March 21, 2016 8 Deployment Models for Distributed Mobility Management 9 draft-sijeon-dmm-deployment-models-02.txt 11 Abstract 13 This document presents available deployment models for distributed 14 mobility management networks, consisted of mobility management 15 functions: anchoring function, location management, and forwarding 16 management functions defined in RFC7429. Some of the functions are 17 modified on a need to allow potential deployment scenarios support. 19 Status of This Memo 21 This Internet-Draft is submitted in full conformance with the 22 provisions of BCP 78 and BCP 79. 24 Internet-Drafts are working documents of the Internet Engineering 25 Task Force (IETF). Note that other groups may also distribute 26 working documents as Internet-Drafts. The list of current Internet- 27 Drafts is at http://datatracker.ietf.org/drafts/current/. 29 Internet-Drafts are draft documents valid for a maximum of six months 30 and may be updated, replaced, or obsoleted by other documents at any 31 time. It is inappropriate to use Internet-Drafts as reference 32 material or to cite them other than as "work in progress." 34 This Internet-Draft will expire on September 22, 2016. 36 Copyright Notice 38 Copyright (c) 2016 IETF Trust and the persons identified as the 39 document authors. All rights reserved. 41 This document is subject to BCP 78 and the IETF Trust's Legal 42 Provisions Relating to IETF Documents 43 (http://trustee.ietf.org/license-info) in effect on the date of 44 publication of this document. Please review these documents 45 carefully, as they describe your rights and restrictions with respect 46 to this document. Code Components extracted from this document must 47 include Simplified BSD License text as described in Section 4.e of 48 the Trust Legal Provisions and are provided without warranty as 49 described in the Simplified BSD License. 51 Table of Contents 53 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 54 2. Conventions and Terminology . . . . . . . . . . . . . . . . . 2 55 3. Deployment Models . . . . . . . . . . . . . . . . . . . . . . 3 56 3.1. D1: Distributed AM, LM, and FM (with centralized LM) - 57 All-in-One . . . . . . . . . . . . . . . . . . . . . . . 3 58 3.2. D2: Distributed AF-DP, LM and FM with centralized AF-CP 59 (+ LM) . . . . . . . . . . . . . . . . . . . . . . . . . 4 60 3.3. D3: Distributed AF-DP and FM-DP with centralized AF-CP, 61 LM, and FM-CP . . . . . . . . . . . . . . . . . . . . . . 5 62 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6 63 5. Security Considerations . . . . . . . . . . . . . . . . . . . 6 64 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 7 65 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 7 66 7.1. Normative References . . . . . . . . . . . . . . . . . . 7 67 7.2. Informative References . . . . . . . . . . . . . . . . . 7 68 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8 70 1. Introduction 72 This draft presents available deployment models consisted of mobility 73 management functions defined in [RFC7429], for distributed mobility 74 management (DMM) networks. With the mobility management functions in 75 [RFC7429], i.e. anchor function (AF), location management function 76 (LM), and forwarding management function (FM), centralized mobility 77 management solutions such as Mobile IP (MIP), Hierarchical Mobile 78 IPv6 (HMIPv6), and Proxy Mobile IPv6 (PMIPv6) have been described and 79 decomposed by functional aspects, trying to analyze gaps from the 80 requirements for DMM [RFC7333]. In this draft, with the functions, 81 we sketch and describe the deployment models for DMM networks, 82 accommodating the possible DMM solutions as well as providing an 83 insight to understand the potentials of DMM. We also describe where 84 the presented deployment models are substantiated with solution 85 proposals submitted in DMM WG. 87 2. Conventions and Terminology 89 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL","SHALL NOT", 90 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 91 document are to be interpreted as described in [RFC2119]. 93 Following terms come from [RFC7429] with modified definition in the 94 AF. 96 Anchoring Function (AF) is defined as a combined control-plane and 97 data-plane functions. For the control-plane function, it allocates 98 an IP address, i.e., Home Address (HoA), or prefix, i.e., Home 99 Network Prefix (HNP) a mobile node, topologically anchored by the 100 advertising node. That is, the anchor node is able to advertise a 101 connected route into the routing infrastructure for the allocated IP 102 prefixes. It also takes a data-plane anchor point where packets 103 destined to the IP address or IP prefix allocated by the anchor 104 should pass through. 106 The AF can be deployed in a decoupled way, i.e. separated control 107 plane and data plane. In that case, following two terms - AF Control 108 Plane (AF-CP) and AF Data Plane (AF-DP) - are used. AF-CP is 109 responsible of allocating the IP address and advertising a connected 110 route for an associated terminal while AF-DP is responsible of 111 anchoring received data packets destined to the IP address allocated 112 by the anchor. 114 Internetwork Location Management (LM) is a control-plane function, 115 which manages and keeps track of the internetwork location of an MN. 116 The location information may be a binding of the advertised IP 117 address/prefix, e.g., HoA or HNP, to the IP routing address of the 118 MN, or it may be a binding of a node that can forward packets 119 destined to the MN. Note that the LM could belong to the AF-CP, as 120 it is done in several solutions, i.e. Mobile IP (MIP) and Proxy 121 Mobile IPv6 (PMIPv6). However, in this draft, each function is 122 indicated distinctively, as those functions could be deployed in 123 different locations to allow advanced control and smooth evolution 124 for DMM. 126 Forwarding Management (FM) function performs packet interception and 127 forwarding to/from the IP address/prefix assigned to the MN, based on 128 the internetwork location information, either to the destination or 129 to some other network element that knows how to forward the packets 130 to their destination. Following the FM definition in [RFC7429], it 131 may be split into the control plane (FM-CP) and data plane (FM-DP). 133 3. Deployment Models 135 We specify and analyze expected use cases where the MN tries to 136 initiate an application. 138 3.1. D1: Distributed AM, LM, and FM (with centralized LM) - All-in-One 139 +--------------------------+ 140 | (LM) | 141 +--------------------------+ 142 ^ ^ 143 | | 144 | (a) | 145 v v 146 +-------------+ (b) +-------------+ 147 |AF + LM + FM | <----> |AF + LM + FM | 148 +-------------+ +-------------+ 150 +------+ 151 | MN | 152 +------+ 154 Figure 1. Distributed AM, LM, and FM functions (with centralized LM) 156 In this deployment model, AF, LM, and FM functions are co-located in 157 every mobility router deployed at edge. This model can be called 158 All-in-One for DMM. Depending on the use of the central LM, the 159 model can be distinguished into fully distributed or partially 160 distributed. In the partially distributed case, interface (a), 161 between the centralized LM and the mobility routers shown in Fig. 1, 162 is could be used for querying necessary mapping information by the 163 edge mobility routers. Interface (b), between the mobility routers 164 shown in Fig. 1, is used for conveying control signaling messages to 165 control a forwarding path between them. Solutions following the 166 given model could be [I-D.seite-dmm-dma][I-D.bernardos-dmm-pmip]. 168 3.2. D2: Distributed AF-DP, LM and FM with centralized AF-CP (+ LM) 169 +--------------------------+ 170 | AF-CP (+ LM) | 171 +--------------------------+ 172 ^ ^ 173 | | 174 |(a) | 175 v v 176 +-----------+ +-----------+ 177 | AF-DP | (b) | AF-DP | 178 | LM + FM | <-----> | LM + FM | 179 +-----------+ +-----------+ 181 +------+ 182 | MN | 183 +------+ 185 Figure 2. Distributed AF-DP, LM and FM functions with centralized 186 AF-CP (+ LM) 188 In this model, we distinguish AF with AF Control Plane (AF-CP) and AF 189 Data Plane (AF-DP). AF-DP is distributed with LM and FM into 190 deployed mobility routers while AF-CP is centralized in a single 191 entity, following a trend of separation of control and user plane for 192 mobility management. For an extensive scenario support, LM may be 193 co-located with the AF-CP. AF-DP is determined by the AF-CP. One 194 possible solution could be to use such as User-Plane Address option 195 to deliver AF-DP IP address serving router or terminal should 196 contact, as proposed in [RFC7389]. Interface (a) shown in Fig. 2 is 197 used to control AF-DP function, with signaling messages or 198 configuration information. Interface (b) shown in Fig. 2 is used for 199 establish and control the forwarding path between the mobility 200 routers. 202 3.3. D3: Distributed AF-DP and FM-DP with centralized AF-CP, LM, and 203 FM-CP 204 +--------------------------+ 205 | AF-CP + LM + FM-CP | 206 +--------------------------+ 207 ^ ^ 208 | | 209 | (a) | 210 v v 211 +---------------+ +---------------+ 212 | AF-DP + FM-DP | | AF-DP + FM-DP | 213 +---------------+ +---------------+ 215 +------+ 216 | MN | 217 +------+ 219 Figure 3. Distributed AF-DP and FM-DP with centralized AF-CP, LM, 220 and FM-CP 222 In the model, separation of FM Control Plane (FM-CP) and FM Data 223 Plane (FM-DP) is applied with the separation of AF-CP and AF-DP. The 224 LM is located at the central entity. Comparing D3 with D2, D3 can 225 provide smooth and flexible forwarding path management between the 226 AF-DP of an allocated IP address and the current serving router where 227 the terminal is attached. Interface (a) shown in Fig. 3 is used to 228 control AF-DP and FM-DP function by the respective control functions, 229 AF-CP and FM-CP, with signaling messages or configuration 230 information. [I-D.ietf-dmm-fpc-cpdp] presents a framework that can 231 facilitate forwarding policy configuration, based on D3 model, 232 imparting a role and characteristics of a mobility router as well as 233 configuring a forwarding path. 234 [I-D.matsushima-stateless-uplane-vepc] may be subject to D3 model, 235 the control functions in vEPC delivers Route Update to EPC Edge 236 Routers, to configure a data-plane routing path. 238 4. IANA Considerations 240 This document makes no request of IANA. 242 5. Security Considerations 244 T.B.D. 246 6. Acknowledgements 248 7. References 250 7.1. Normative References 252 [I-D.ietf-dmm-fpc-cpdp] 253 Liebsch, M., Matsushima, S., Gundavelli, S., and D. Moses, 254 "Protocol for Forwarding Policy Configuration (FPC) in 255 DMM", draft-ietf-dmm-fpc-cpdp-01 (work in progress), July 256 2015. 258 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 259 Requirement Levels", BCP 14, RFC 2119, 260 DOI 10.17487/RFC2119, March 1997, 261 . 263 [RFC7389] Wakikawa, R., Pazhyannur, R., Gundavelli, S., and C. 264 Perkins, "Separation of Control and User Plane for Proxy 265 Mobile IPv6", RFC 7389, DOI 10.17487/RFC7389, October 266 2014, . 268 7.2. Informative References 270 [I-D.bernardos-dmm-pmip] 271 Bernardos, C., Oliva, A., and F. Giust, "A PMIPv6-based 272 solution for Distributed Mobility Management", draft- 273 bernardos-dmm-pmip-06 (work in progress), March 2016. 275 [I-D.matsushima-stateless-uplane-vepc] 276 Matsushima, S. and R. Wakikawa, "Stateless user-plane 277 architecture for virtualized EPC (vEPC)", draft- 278 matsushima-stateless-uplane-vepc-05 (work in progress), 279 September 2015. 281 [I-D.seite-dmm-dma] 282 Seite, P., Bertin, P., and J. Lee, "Distributed Mobility 283 Anchoring", draft-seite-dmm-dma-07 (work in progress), 284 February 2014. 286 [RFC7333] Chan, H., Ed., Liu, D., Seite, P., Yokota, H., and J. 287 Korhonen, "Requirements for Distributed Mobility 288 Management", RFC 7333, DOI 10.17487/RFC7333, August 2014, 289 . 291 [RFC7429] Liu, D., Ed., Zuniga, JC., Ed., Seite, P., Chan, H., and 292 CJ. Bernardos, "Distributed Mobility Management: Current 293 Practices and Gap Analysis", RFC 7429, 294 DOI 10.17487/RFC7429, January 2015, 295 . 297 Authors' Addresses 299 Seil Jeon 300 Instituto de Telecomunicacoes 301 Campus Universitario de Santiago 302 Aveiro 3810-193 303 Portugal 305 Email: seiljeon@av.it.pt 307 Younghan Kim 308 Soongsil University 309 369, Sangdo-ro, Dongjak-gu 310 Seoul 156-743 311 Korea 313 Email: younghak@ssu.ac.kr