idnits 2.17.1 draft-ietf-dmm-ondemand-mobility-14.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 (March 19, 2018) is 2229 days in the past. Is this intentional? -- Found something which looks like a code comment -- if you have code sections in the document, please surround them with '' and '' lines. Checking references for intended status: Informational ---------------------------------------------------------------------------- -- Obsolete informational reference (is this intentional?): RFC 6824 (Obsoleted by RFC 8684) Summary: 0 errors (**), 0 flaws (~~), 1 warning (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 DMM Working Group A. Yegin 3 Internet-Draft Actility 4 Intended status: Informational D. Moses 5 Expires: September 20, 2018 Intel 6 K. Kweon 7 J. Lee 8 J. Park 9 Samsung 10 S. Jeon 11 Sungkyunkwan University 12 March 19, 2018 14 On Demand Mobility Management 15 draft-ietf-dmm-ondemand-mobility-14 17 Abstract 19 Applications differ with respect to whether they need IP session 20 continuity and/or IP address reachability. The network providing the 21 same type of service to any mobile host and any application running 22 on the host yields inefficiencies. This document describes a 23 solution for taking the application needs into account by selectively 24 providing IP session continuity and IP address reachability on a per- 25 socket basis. 27 Status of This Memo 29 This Internet-Draft is submitted in full conformance with the 30 provisions of BCP 78 and BCP 79. 32 Internet-Drafts are working documents of the Internet Engineering 33 Task Force (IETF). Note that other groups may also distribute 34 working documents as Internet-Drafts. The list of current Internet- 35 Drafts is at https://datatracker.ietf.org/drafts/current/. 37 Internet-Drafts are draft documents valid for a maximum of six months 38 and may be updated, replaced, or obsoleted by other documents at any 39 time. It is inappropriate to use Internet-Drafts as reference 40 material or to cite them other than as "work in progress." 42 This Internet-Draft will expire on September 20, 2018. 44 Copyright Notice 46 Copyright (c) 2018 IETF Trust and the persons identified as the 47 document authors. All rights reserved. 49 This document is subject to BCP 78 and the IETF Trust's Legal 50 Provisions Relating to IETF Documents 51 (https://trustee.ietf.org/license-info) in effect on the date of 52 publication of this document. Please review these documents 53 carefully, as they describe your rights and restrictions with respect 54 to this document. Code Components extracted from this document must 55 include Simplified BSD License text as described in Section 4.e of 56 the Trust Legal Provisions and are provided without warranty as 57 described in the Simplified BSD License. 59 Table of Contents 61 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 62 2. Notational Conventions . . . . . . . . . . . . . . . . . . . 4 63 3. Solution . . . . . . . . . . . . . . . . . . . . . . . . . . 4 64 3.1. Types of IP Addresses . . . . . . . . . . . . . . . . . . 4 65 3.2. Granularity of Selection . . . . . . . . . . . . . . . . 5 66 3.3. On Demand Nature . . . . . . . . . . . . . . . . . . . . 6 67 3.4. Conveying the Desired Address Type . . . . . . . . . . . 7 68 4. Usage example . . . . . . . . . . . . . . . . . . . . . . . . 8 69 5. Backwards Compatibility Considerations . . . . . . . . . . . 10 70 5.1. Applications . . . . . . . . . . . . . . . . . . . . . . 10 71 5.2. IP Stack in the Mobile Host . . . . . . . . . . . . . . . 10 72 5.3. Network Infrastructure . . . . . . . . . . . . . . . . . 10 73 5.4. Merging this work with RFC5014 . . . . . . . . . . . . . 11 74 6. Summary of New Definitions . . . . . . . . . . . . . . . . . 11 75 6.1. New APIs . . . . . . . . . . . . . . . . . . . . . . . . 11 76 6.2. New Flags . . . . . . . . . . . . . . . . . . . . . . . . 12 77 7. Security Considerations . . . . . . . . . . . . . . . . . . . 13 78 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13 79 9. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 13 80 10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 13 81 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 13 82 11.1. Normative References . . . . . . . . . . . . . . . . . . 13 83 11.2. Informative References . . . . . . . . . . . . . . . . . 14 84 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 15 86 1. Introduction 88 In the context of Mobile IP [RFC5563][RFC6275][RFC5213][RFC5944], the 89 following two attributes are defined for IP service provided to 90 mobile hosts: 92 IP session continuity: The ability to maintain an ongoing IP session 93 by keeping the same local end-point IP address throughout the session 94 despite the mobile host changing its point of attachment within the 95 IP network topology. The IP address of the host may change between 96 two independent IP sessions, but that does not jeopardize its IP 97 session continuity. IP session continuity is essential for mobile 98 hosts to maintain ongoing flows without any interruption. 100 IP address reachability: The ability to maintain the same IP address 101 for an extended period of time. The IP address stays the same across 102 independent IP sessions, and even in the absence of any IP session. 103 The IP address may be published in a long-term registry (e.g., DNS), 104 and is made available for serving incoming (e.g., TCP) connections. 105 IP address reachability is essential for mobile hosts to use 106 specific/published IP addresses. 108 Mobile IP is designed to provide both IP session continuity and IP 109 address reachability to mobile hosts. Architectures utilizing these 110 protocols (e.g., 3GPP, 3GPP2, WIMAX) ensure that any mobile host 111 attached to the compliant networks can enjoy these benefits. Any 112 application running on these mobile hosts is subjected to the same 113 treatment with respect to IP session continuity and IP address 114 reachability. 116 It should be noted that in reality not every application may need 117 these benefits. IP address reachability is required for applications 118 running as servers (e.g., a web server running on the mobile host). 119 But, a typical client application (e.g., web browser) does not 120 necessarily require IP address reachability. Similarly, IP session 121 continuity is not required for all types of applications either. 122 Applications performing brief communication (e.g., ping) can survive 123 without having IP session continuity support. 125 Achieving IP session continuity and IP address reachability with 126 Mobile IP incurs some cost. Mobile IP protocol forces the mobile 127 host's IP traffic to traverse a centrally-located router (Home Agent, 128 HA), which incurs additional transmission latency and use of 129 additional network resources, adds to the network CAPEX and OPEX, and 130 decreases the reliability of the network due to the introduction of a 131 single point of failure [RFC7333]. Therefore, IP session continuity 132 and IP address reachability SHOULD be provided only when necessary. 134 Furthermore, when an application needs session continuity, it may be 135 able to satisfy that need by using a solution above the IP layer, 136 such as MPTCP [RFC6824], SIP mobility [RFC3261], or an application- 137 layer mobility solution. These higher-layer solutions are not 138 subject to the same issues that arise with the use of Mobile IP since 139 they can utilize the most direct data path between the end-points. 140 But, if Mobile IP is being applied to the mobile host, the higher- 141 layer protocols are rendered useless because their operation is 142 inhibited by Mobile IP. Since Mobile IP ensures that the IP address 143 of the mobile host remains fixed (despite the location and movement 144 of the mobile host), the higher-layer protocols never detect the IP- 145 layer change and never engage in mobility management. 147 This document proposes a solution for applications running on mobile 148 hosts to indicate whether they need IP session continuity or IP 149 address reachability. The network protocol stack on the mobile host, 150 in conjunction with the network infrastructure, provides the required 151 type of IP service. It is for the benefit of both the users and the 152 network operators not to engage an extra level of service unless it 153 is absolutely necessary. It is expected that applications and 154 networks compliant with this specification will utilize this solution 155 to use network resources more efficiently. 157 2. Notational Conventions 159 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 160 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 161 document are to be interpreted as described in [RFC2119]. 163 3. Solution 165 3.1. Types of IP Addresses 167 Four types of IP addresses are defined with respect to mobility 168 management. 170 - Fixed IP Address 172 A Fixed IP address is an address with a guarantee to be valid for a 173 very long time, regardless of whether it is being used in any packet 174 to/from the mobile host, or whether or not the mobile host is 175 connected to the network, or whether it moves from one point-of- 176 attachment to another (with a different IP prefix) while it is 177 connected. 179 Fixed IP addresses are required by applications that need both IP 180 session continuity and IP address reachability. 182 - Session-lasting IP Address 184 A session-lasting IP address is an address with a guarantee to be 185 valid throughout the IP session(s) for which it was requested. It is 186 guaranteed to be valid even after the mobile host had moved from one 187 point-of-attachment to another (with a different IP prefix). 189 Session-lasting IP addresses are required by applications that need 190 IP session continuity but do not need IP address reachability. 192 - Non-persistent IP Address 194 This type of IP address does not provide IP session continuity nor IP 195 address reachability. The IP address is created from an IP prefix 196 that is obtained from the serving IP gateway and is not maintained 197 across gateway changes. In other words, the IP prefix may be 198 released and replaced by a new one when the IP gateway changes due to 199 the movement of the mobile host forcing the creation of a new source 200 IP address with the updated allocated IP prefix. 202 - Graceful Replacement IP Address 204 In some cases, the network cannot guarantee the validity of the 205 provided IP prefix throughout the duration of the IP session, but can 206 provide a limited graceful period of time in which both the original 207 IP prefix and a new one are valid. This enables the application some 208 flexibility in the transition from the existing source IP address to 209 the new one. 211 This gracefulness is still better than the non-persistence type of 212 address for applications that can handle a change in their source IP 213 address but require that extra flexibility. 215 Applications running as servers at a published IP address require a 216 Fixed IP Address. Long-standing applications (e.g., an SSH session) 217 may also require this type of address. Enterprise applications that 218 connect to an enterprise network via virtual LAN require a Fixed IP 219 Address. 221 Applications with short-lived transient IP sessions can use Session- 222 lasting IP Addresses. For example: Web browsers. 224 Applications with very short IP sessions, such as DNS clients and 225 instant messengers, can utilize Non-persistent IP Addresses. Even 226 though they could very well use Fixed or Session-lasting IP 227 Addresses, the transmission latency would be minimized when a Non- 228 persistent IP Addresses are used. 230 Applications that can tolerate a short interruption in connectivity 231 can use the Graceful-replacement IP addresses. For example, a 232 streaming client that has buffering capabilities. 234 3.2. Granularity of Selection 236 IP address type selection is made on a per-socket granularity. 237 Different parts of the same application may have different needs. 238 For example, the control-plane of an application may require a Fixed 239 IP Address in order to stay reachable, whereas the data-plane of the 240 same application may be satisfied with a Session-lasting IP Address. 242 3.3. On Demand Nature 244 At any point in time, a mobile host may have a combination of IP 245 addresses configured. Zero or more Non-persistent, zero or more 246 Session-lasting, zero or more Fixed and zero or more Graceful- 247 Replacement IP addresses may be configured by the IP stack of the 248 host. The combination may be as a result of the host policy, 249 application demand, or a mix of the two. 251 When an application requires a specific type of IP address and such 252 an address is not already configured on the host, the IP stack SHALL 253 attempt to configure one. For example, a host may not always have a 254 Session-lasting IP address available. When an application requests 255 one, the IP stack SHALL make an attempt to configure one by issuing a 256 request to the network (see Section 3.4 below for more details). If 257 the operation fails, the IP stack SHALL fail the associated socket 258 request and return an error. If successful, a Session-lasting IP 259 Address gets configured on the mobile host. If another socket 260 requests a Session-lasting IP address at a later time, the same IP 261 address may be served to that socket as well. When the last socket 262 using the same configured IP address is closed, the IP address may be 263 released or kept for future applications that may be launched and 264 require a Session-lasting IP address. 266 In some cases it might be preferable for the mobile host to request a 267 new Session-lasting IP address for a new opening of an IP session 268 (even though one was already assigned to the mobile host by the 269 network and might be in use in a different, already active IP 270 session). It is outside the scope of this specification to define 271 criteria for choosing to use available addresses or choosing to 272 request new ones. It supports both alternatives (and any 273 combination). 275 It is outside the scope of this specification to define how the host 276 requests a specific type of prefix and how the network indicates the 277 type of prefix in its advertisement or in its reply to a request). 279 The following are matters of policy, which may be dictated by the 280 host itself, the network operator, or the system architecture 281 standard: 283 - The initial set of IP addresses configured on the host at boot 284 time. 286 - Permission to grant various types of IP addresses to a requesting 287 application. 289 - Determination of a default address type when an application does 290 not make any explicit indication, whether it already supports the 291 required API or it is just a legacy application. 293 3.4. Conveying the Desired Address Type 295 [RFC5014] introduced the ability of applications to influence the 296 source address selection with the IPV6_ADDR_PREFERENCE option at the 297 IPPROTO_IPV6 level. This option is used with setsockopt() and 298 getsockopt() calls to set/get address selection preferences. 300 Extending this further by adding more flags does not work when a 301 request for an address of a certain type results in requiring the IP 302 stack to wait for the network to provide the desired source IP prefix 303 and hence causing the setsockopt() call to block until the prefix is 304 allocated (or an error indication from the network is received). 306 Alternatively a new Socket API is defined - getsc() which allows 307 applications to express their desired type of session continuity 308 service. The new getsc() API will return an IPv6 address that is 309 associated with the desired session continuity service and with 310 status information indicating whether or not the desired service was 311 provided. 313 An application that wishes to secure a desired service will call 314 getsc() with the service type definition and a place to contain the 315 provided IP address, and call bind() to associate that IP address 316 with the Socket (See pseudo-code example in Section 4 below). 318 When the IP stack is required to use a source IP address of a 319 specified type, it can use an existing address, or request a new IP 320 prefix (of the same type) from the network and create a new one. If 321 the host does not already have an IPv6 prefix of that specific type, 322 it MUST request one from the network. 324 Using an existing address from an existing prefix is faster but might 325 yield a less optimal route (if a hand-off event occurred after its 326 configuration). On the other hand, acquiring a new IP prefix from 327 the network may be slower due to signaling exchange with the network. 329 Applications can control the stack's operation by setting a new flag 330 - ON_NET flag - which directs the IP stack whether to use a 331 preconfigured source IP address (if exists) or to request a new IPv6 332 prefix from the current serving network and configure a new IP 333 address. 335 This new flag is added to the set of flags in the 336 IPV6_ADDR_PREFERENCES option at the IPPROTO_IPV6 level. It is used 337 in setsockopt() to set the desired behavior. 339 4. Usage example 341 The following example shows pseudo-code for creating a Stream socket 342 (TCP) with a Session-Lasting source IP address: 344 #include 345 #include 347 // Socket information 348 int s ; // Socket id 350 // Source information (for secsc() and bind()) 351 sockaddr_in6 sourceInfo // my address and port for bind() 352 in6_addr sourceAddress // will contain the provisioned 353 // source IP address 354 uint8_t sc_type = IPV6_REQUIRE_SESSION_LASTING_IP ; 355 // For requesting a Session-Lasting 356 // source IP address 358 // Destination information (for connect()) 359 sockaddr_in6 serverInfo ; // server info for connect() 361 // Create an IPv6 TCP socket 362 s = socket(AF_INET6, SOCK_STREAM, 0) ; 363 if (s!=0) { 364 // Handle socket creation error 365 // ... 366 } // if socket creation failed 367 else { 368 // Socket creation is successful 369 // The application cannot connect yet, since it wants to use 370 // a Session-Lasting source IP address It needs to request 371 // the Session-Lasting source IP before connecting 372 if (setsc(s, &sourceAddress, &sc_type)) == 0){ 373 // setting session continuity to Session Lasting is 374 // Successful. sourceAddress now contains the Session- 375 // LAsting source IP address 377 // Bind to that source IP address 378 sourceInfo.sin6_family = AF_INET6 ; 379 sourceInfo.sin6_port = 0 // let the stack choose the port 380 sourceInfo.sin6_address = sourceAddress ; 381 // Use the source address that was 382 // generated by the setsc() call 383 if (bind(s, &sourceInfo, sizeof(sourceInfo))==0){ 384 // Set the desired server's information for connect() 385 serverInfo.sin6_family = AF_INET6 ; 386 serverInfo.sin6_port = SERVER_PORT_NUM ; 387 serverAddress.sin6_addr = SERVER_IPV6_ADDRESS ; 389 // Connect to the server 390 if (connect(s, &serverInfo, sizeof(serverInfo))==0) { 391 // connect successful (3-way handshake has been 392 // completed with Session-Lasting source address. 393 // Continue application functionality 394 // ... 395 } // if connect() is successful 396 else { 397 // connect failed 398 // ... 399 // Application code that handles connect failure and 400 // closes the socket 401 // ... 402 } // if connect() failed 403 } // if bind() successful 404 else { 405 // bind() failed 406 // ... 407 // Application code that handles bind failure and 408 // closes the socket 409 // ... 410 } // if bind() failed 411 } // if setsc() was successful and of a Session-Lasting 412 // source IP address was provided 413 else { 414 // application code that does not use Session-lasting IP 415 // address. The application may either connect without 416 // the desired Session-lasting service, or close the 417 // socket... 418 } // if setsc() failed 419 } // if socket was created successfully 421 // The rest of the application's code 422 // ... 424 5. Backwards Compatibility Considerations 426 Backwards compatibility support is REQUIRED by the following 3 types 427 of entities: 429 - The Applications on the mobile host 431 - The IP stack in the mobile host 433 - The network infrastructure 435 5.1. Applications 437 Legacy applications that do not support the OnDemand functionality 438 will use the legacy API and will not be able to take advantage of the 439 On-Demand Mobility feature. 441 Applications using the new OnDemand functionality MUST be aware that 442 they may be executed in legacy environments that do not support it. 443 Such environments may include a legacy IP stack on the mobile host, 444 legacy network infrastructure, or both. In either case, the API will 445 return an error code and the invoking applications may just give up 446 and use legacy calls. 448 5.2. IP Stack in the Mobile Host 450 New IP stacks MUST continue to support all legacy operations. If an 451 application does not use On-Demand functionality, the IP stack MUST 452 respond in a legacy manner. 454 If the network infrastructure supports On-Demand functionality, the 455 IP stack SHOULD follow the application request: If the application 456 requests a specific address type, the stack SHOULD forward this 457 request to the network. If the application does not request an 458 address type, the IP stack MUST NOT request an address type and leave 459 it to the network's default behavior to choose the type of the 460 allocated IP prefix. If an IP prefix was already allocated to the 461 host, the IP stack uses it and may not request a new one from the 462 network. 464 5.3. Network Infrastructure 466 The network infrastructure may or may not support the On-Demand 467 functionality. How the IP stack on the host and the network 468 infrastructure behave in case of a compatibility issue is outside the 469 scope of this API specification. 471 5.4. Merging this work with RFC5014 473 [RFC5014] defines new flags that may be used with setsockopt() to 474 influence source IP address selection for a socket. The list of 475 flags include: source home address, care-of address, temporary 476 address, public address CGA (Cryptographically Created Address) and 477 non-CGA. When applications require session continuity service and 478 use setsc() and bind(), they SHOULD NOT set the flags specified in 479 [RFC5014]. 481 However, if an application sets a specific option using setsockopt() 482 with one of the flags specified in [RFC5014] and also selects a 483 source IP address using setsc() and bind() the IP address that was 484 generated by setsc() and bound using bind() will be the one used by 485 traffic generated using that socket and options set by setsockopt() 486 will be ignored. 488 If bind() was not invoked after setsc() by the application, the IP 489 address generated by setsc() will not be used and traffic generated 490 by the socket will use a source IP address that complies with the 491 options selected by setsockopt(). 493 6. Summary of New Definitions 495 6.1. New APIs 497 setsc() enables applications to request a specific type of source IP 498 address in terms of session continuity. Its definition is: 500 int setsc(int sockfd, in6_addr *sourceAddress, sc_type addressType); 502 Where: 503 - sockfd - is the socket descriptor of the socket with which 504 a specific address type is associated 505 - sourceAddress - is a pointer to an area allocated for setsc() to 506 place the generated source IP address of the 507 desired session continuity type 508 - addressType - Is the desired type of session continuity service. 509 It is a 3-bit field containing one of the 510 following values: 511 0 - Reserved 512 1 - FIXED_IPV6_ADDRESS 513 2 - SESSION_LASTING_IPV6_ADDRESS 514 3 - NON_PERSISTENT_IPV6_ADDRESS 515 4 - GRACEFUL_REPLACEMENT_IPV6_ADDRESS 516 5-7 - Reserved 518 setsc() returns the status of the operation: 519 - 0 - Address was successfully generated 520 - EAI_REQUIREDIPNOTSUPPORTED - the required service type is not 521 supported 522 - EAI_REQUIREDIPFAILED - the network could not fulfill the desired 523 request 525 setsc() MAY block the invoking thread if it triggers the TCP/IP stack 526 to request a new IP prefix from the network to construct the desired 527 source IP address. If an IP prefix with the desired session 528 continuity features already exists (was previously allocated to the 529 mobile host) and the stack is not required to request a new one as a 530 result of setting the IPV6_REQUIRE_SRC_ON_NET flag (defined below), 531 setsc() MAY return immediately with the constructed IP address and 532 will not block the thread. 534 6.2. New Flags 536 The following flag is added to the list of flags in the 537 IPV6_ADDR_PREFERENCE option at the IPPROTO6 level: 539 IPV6_REQUIRE_SRC_ON_NET - set IP stack address allocation behavior 541 If set, the IP stack will request a new IPv6 prefix of the desired 542 type from the current serving network and configure a new source IP 543 address. If reset, the IP stack will use a preconfigured one if it 544 exists. If there is no preconfigured IP address of the desired type, 545 a new prefix will be requested and used for creating the IP address. 547 7. Security Considerations 549 The setting of certain IP address type on a given socket may be 550 restricted to privileged applications. For example, a Fixed IP 551 Address may be provided as a premium service and only certain 552 applications may be allowed to use them. Setting and enforcement of 553 such privileges are outside the scope of this document. 555 8. IANA Considerations 557 This document has no IANA considerations. 559 9. Contributors 561 This document was merged with [I-D.sijeon-dmm-use-cases-api-source]. 562 We would like to acknowledge the contribution of the following people 563 to that document as well: 565 Sergio Figueiredo 566 Altran Research, France 567 Email: sergio.figueiredo@altran.com 569 Younghan Kim 570 Soongsil University, Korea 571 Email: younghak@ssu.ac.kr 573 John Kaippallimalil 574 Huawei, USA 575 Email: john.kaippallimalil@huawei.com 577 10. Acknowledgements 579 We would like to thank Wu-chi Feng, Alexandru Petrescu, Jouni 580 Korhonen, Sri Gundavelli, Dave Dolson and Lorenzo Colitti for their 581 valuable comments and suggestions on this work. 583 11. References 585 11.1. Normative References 587 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 588 Requirement Levels", BCP 14, RFC 2119, 589 DOI 10.17487/RFC2119, March 1997, 590 . 592 [RFC5014] Nordmark, E., Chakrabarti, S., and J. Laganier, "IPv6 593 Socket API for Source Address Selection", RFC 5014, 594 DOI 10.17487/RFC5014, September 2007, 595 . 597 11.2. Informative References 599 [I-D.sijeon-dmm-use-cases-api-source] 600 Jeon, S., Figueiredo, S., Kim, Y., and J. Kaippallimalil, 601 "Use Cases and API Extension for Source IP Address 602 Selection", draft-sijeon-dmm-use-cases-api-source-07 (work 603 in progress), September 2017. 605 [RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, 606 A., Peterson, J., Sparks, R., Handley, M., and E. 607 Schooler, "SIP: Session Initiation Protocol", RFC 3261, 608 DOI 10.17487/RFC3261, June 2002, 609 . 611 [RFC5213] Gundavelli, S., Ed., Leung, K., Devarapalli, V., 612 Chowdhury, K., and B. Patil, "Proxy Mobile IPv6", 613 RFC 5213, DOI 10.17487/RFC5213, August 2008, 614 . 616 [RFC5563] Leung, K., Dommety, G., Yegani, P., and K. Chowdhury, 617 "WiMAX Forum / 3GPP2 Proxy Mobile IPv4", RFC 5563, 618 DOI 10.17487/RFC5563, February 2010, 619 . 621 [RFC5944] Perkins, C., Ed., "IP Mobility Support for IPv4, Revised", 622 RFC 5944, DOI 10.17487/RFC5944, November 2010, 623 . 625 [RFC6275] Perkins, C., Ed., Johnson, D., and J. Arkko, "Mobility 626 Support in IPv6", RFC 6275, DOI 10.17487/RFC6275, July 627 2011, . 629 [RFC6824] Ford, A., Raiciu, C., Handley, M., and O. Bonaventure, 630 "TCP Extensions for Multipath Operation with Multiple 631 Addresses", RFC 6824, DOI 10.17487/RFC6824, January 2013, 632 . 634 [RFC7333] Chan, H., Ed., Liu, D., Seite, P., Yokota, H., and J. 635 Korhonen, "Requirements for Distributed Mobility 636 Management", RFC 7333, DOI 10.17487/RFC7333, August 2014, 637 . 639 Authors' Addresses 641 Alper Yegin 642 Actility 643 Istanbul 644 Turkey 646 Email: alper.yegin@actility.com 648 Danny Moses 649 Intel Corporation 650 Petah Tikva 651 Israel 653 Email: danny.moses@intel.com 655 Kisuk Kweon 656 Samsung 657 Suwon 658 South Korea 660 Email: kisuk.kweon@samsung.com 662 Jinsung Lee 663 Samsung 664 Suwon 665 South Korea 667 Email: js81.lee@samsung.com 669 Jungshin Park 670 Samsung 671 Suwon 672 South Korea 674 Email: shin02.park@samsung.com 676 Seil Jeon 677 Sungkyunkwan University 678 Suwon 679 South Korea 681 Email: seiljeon@skku.edu