idnits 2.17.1 draft-ietf-dmm-ondemand-mobility-11.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 8 instances of too long lines in the document, the longest one being 17 characters in excess of 72. 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 seems to have RFC 2119 boilerplate text. -- The document date (June 24, 2017) is 2497 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 ---------------------------------------------------------------------------- == Unused Reference: 'RFC6724' is defined on line 562, but no explicit reference was found in the text == Outdated reference: A later version (-07) exists of draft-sijeon-dmm-use-cases-api-source-06 -- Obsolete informational reference (is this intentional?): RFC 6824 (Obsoleted by RFC 8684) Summary: 1 error (**), 0 flaws (~~), 4 warnings (==), 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: December 26, 2017 Intel 6 K. Kweon 7 J. Lee 8 J. Park 9 Samsung 10 S. Jeon 11 Sungkyunkwan University 12 June 24, 2017 14 On Demand Mobility Management 15 draft-ietf-dmm-ondemand-mobility-11 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 http://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 December 26, 2017. 44 Copyright Notice 46 Copyright (c) 2017 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 (http://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 6. Summary of New Definitions . . . . . . . . . . . . . . . . . 11 74 6.1. New APIs . . . . . . . . . . . . . . . . . . . . . . . . 11 75 6.2. New Flags . . . . . . . . . . . . . . . . . . . . . . . . 11 76 7. Security Considerations . . . . . . . . . . . . . . . . . . . 12 77 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12 78 9. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 12 79 10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 12 80 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 12 81 11.1. Normative References . . . . . . . . . . . . . . . . . . 12 82 11.2. Informative References . . . . . . . . . . . . . . . . . 13 83 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 14 85 1. Introduction 87 In the context of Mobile IP [RFC5563][RFC6275][RFC5213][RFC5944], the 88 following two attributes are defined for IP service provided to 89 mobile hosts: 91 IP session continuity: The ability to maintain an ongoing IP session 92 by keeping the same local end-point IP address throughout the session 93 despite the mobile host changing its point of attachment within the 94 IP network topology. The IP address of the host may change between 95 two independent IP sessions, but that does not jeopardize its IP 96 session continuity. IP session continuity is essential for mobile 97 hosts to maintain ongoing flows without any interruption. 99 IP address reachability: The ability to maintain the same IP address 100 for an extended period of time. The IP address stays the same across 101 independent IP sessions, and even in the absence of any IP session. 102 The IP address may be published in a long-term registry (e.g., DNS), 103 and is made available for serving incoming (e.g., TCP) connections. 104 IP address reachability is essential for mobile hosts to use 105 specific/published IP addresses. 107 Mobile IP is designed to provide both IP session continuity and IP 108 address reachability to mobile hosts. Architectures utilizing these 109 protocols (e.g., 3GPP, 3GPP2, WIMAX) ensure that any mobile host 110 attached to the compliant networks can enjoy these benefits. Any 111 application running on these mobile hosts is subjected to the same 112 treatment with respect to IP session continuity and IP address 113 reachability. 115 It should be noted that in reality not every application may need 116 these benefits. IP address reachability is required for applications 117 running as servers (e.g., a web server running on the mobile host). 118 But, a typical client application (e.g., web browser) does not 119 necessarily require IP address reachability. Similarly, IP session 120 continuity is not required for all types of applications either. 121 Applications performing brief communication (e.g., ping) can survive 122 without having IP session continuity support. 124 Achieving IP session continuity and IP address reachability with 125 Mobile IP incurs some cost. Mobile IP protocol forces the mobile 126 host's IP traffic to traverse a centrally-located router (Home Agent, 127 HA), which incurs additional transmission latency and use of 128 additional network resources, adds to the network CAPEX and OPEX, and 129 decreases the reliability of the network due to the introduction of a 130 single point of failure [RFC7333]. Therefore, IP session continuity 131 and IP address reachability should be provided only when necessary. 133 Furthermore, when an application needs session continuity, it may be 134 able to satisfy that need by using a solution above the IP layer, 135 such as MPTCP [RFC6824], SIP mobility [RFC3261], or an application- 136 layer mobility solution. These higher-layer solutions are not 137 subject to the same issues that arise with the use of Mobile IP since 138 they can utilize the most direct data path between the end-points. 139 But, if Mobile IP is being applied to the mobile host, the higher- 140 layer protocols are rendered useless because their operation is 141 inhibited by Mobile IP. Since Mobile IP ensures that the IP address 142 of the mobile host remains fixed (despite the location and movement 143 of the mobile host), the higher-layer protocols never detect the IP- 144 layer change and never engage in mobility management. 146 This document proposes a solution for applications running on mobile 147 hosts to indicate whether they need IP session continuity or IP 148 address reachability. The network protocol stack on the mobile host, 149 in conjunction with the network infrastructure, would provide the 150 required type of IP service. It is for the benefit of both the users 151 and the network operators not to engage an extra level of service 152 unless it is absolutely necessary. It is expected that applications 153 and networks compliant with this specification would utilize this 154 solution to use network resources more efficiently. 156 2. Notational Conventions 158 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 159 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 160 document are to be interpreted as described in [RFC2119]. 162 3. Solution 164 3.1. Types of IP Addresses 166 Four types of IP addresses are defined with respect to mobility 167 management. 169 - Fixed IP Address 171 A Fixed IP address is an address with a guarantee to be valid for a 172 very long time, regardless of whether it is being used in any packet 173 to/from the mobile host, or whether or not the mobile host is 174 connected to the network, or whether it moves from one point-of- 175 attachment to another (with a different IP prefix) while it is 176 connected. 178 Fixed IP addresses are required by applications that need both IP 179 session continuity and IP address reachability. 181 - Session-lasting IP Address 183 A session-lasting IP address is an address with a guarantee to be 184 valid throughout the IP session(s) for which it was requested. It is 185 guaranteed to be valid even after the mobile host had moved from one 186 point-of-attachment to another (with a different IP prefix). 188 Session-lasting IP addresses are required by applications that need 189 IP session continuity but do not need IP address reachability. 191 - Non-persistent IP Address 193 This type of IP address does not provide IP session continuity nor IP 194 address reachability. The IP address is created from an IP prefix 195 that is obtained from the serving IP gateway and is not maintained 196 across gateway changes. In other words, the IP prefix may be 197 released and replaced by a new one when the IP gateway changes due to 198 the movement of the mobile host forcing the creation of a new source 199 IP address with the updated allocated IP prefix. 201 - Graceful Replacement IP Address 203 In some cases, the network cannot guarantee the validity of the 204 provided IP prefix throughout the duration of the IP session, but can 205 provide a limited graceful period of time in which both the original 206 IP prefix and a new one are valid. This enables the application some 207 flexibility in the transition from the existing source IP address to 208 the new one. 210 This gracefulness is still better than the non-persistence type of 211 address for applications that can handle a change in their source IP 212 address but require that extra flexibility. 214 Applications running as servers at a published IP address require a 215 Fixed IP Address. Long-standing applications (e.g., an SSH session) 216 may also require this type of address. Enterprise applications that 217 connect to an enterprise network via virtual LAN require a Fixed IP 218 Address. 220 Applications with short-lived transient IP sessions can use Session- 221 lasting IP Addresses. For example: Web browsers. 223 Applications with very short IP sessions, such as DNS clients and 224 instant messengers, can utilize Non-persistent IP Addresses. Even 225 though they could very well use Fixed or Session-lasting IP 226 Addresses, the transmission latency would be minimized when a Non- 227 persistent IP Addresses are used. 229 Applications that can tolerate a short interruption in connectivity 230 can use the Graceful-replacement IP addresses. For example, a 231 streaming client that has buffering capabilities. 233 3.2. Granularity of Selection 235 IP address type selection is made on a per-socket granularity. 236 Different parts of the same application may have different needs. 237 For example, the control-plane of an application may require a Fixed 238 IP Address in order to stay reachable, whereas the data-plane of the 239 same application may be satisfied with a Session-lasting IP Address. 241 3.3. On Demand Nature 243 At any point in time, a mobile host may have a combination of IP 244 addresses configured. Zero or more Non-persistent, zero or more 245 Session-lasting, zero or more Fixed and zero or more Graceful- 246 Replacement IP addresses may be configured by the IP stack of the 247 host. The combination may be as a result of the host policy, 248 application demand, or a mix of the two. 250 When an application requires a specific type of IP address and such 251 an address is not already configured on the host, the IP stack shall 252 attempt to configure one. For example, a host may not always have a 253 Session-lasting IP address available. When an application requests 254 one, the IP stack shall make an attempt to configure one by issuing a 255 request to the network (see Section 3.4 below for more details). If 256 the operation fails, the IP stack shall fail the associated socket 257 request and return an error. If successful, a Session-lasting IP 258 Address gets configured on the mobile host. If another socket 259 requests a Session-lasting IP address at a later time, the same IP 260 address may be served to that socket as well. When the last socket 261 using the same configured IP address is closed, the IP address may be 262 released or kept for future applications that may be launched and 263 require a Session-lasting IP address. 265 In some cases it might be preferable for the mobile host to request a 266 new Session-lasting IP address for a new opening of an IP session 267 (even though one was already assigned to the mobile host by the 268 network and might be in use in a different, already active IP 269 session). It is outside the scope of this specification to define 270 criteria for choosing to use available addresses or choosing to 271 request new ones. It supports both alternatives (and any 272 combination). 274 It is outside the scope of this specification to define how the host 275 requests a specific type of prefix and how the network indicates the 276 type of prefix in its advertisement or in its reply to a request). 278 The following are matters of policy, which may be dictated by the 279 host itself, the network operator, or the system architecture 280 standard: 282 - The initial set of IP addresses configured on the host at boot 283 time. 285 - Permission to grant various types of IP addresses to a requesting 286 application. 288 - Determination of a default address type when an application does 289 not make any explicit indication, whether it already supports the 290 required API or it is just a legacy application. 292 3.4. Conveying the Desired Address Type 294 [RFC5014] introduced the ability of applications to influence the 295 source address selection with the IPV6_ADDR_PREFERENCE option at the 296 IPPROTO_IPV6 level. This option is used with setsockopt() and 297 getsockopt() calls to set/get address selection preferences. 299 Extending this further by adding more flags does not work when a 300 request for an address of a certain type results in requiring the IP 301 stack to wait for the network to provide the desired source IP prefix 302 and hence causing the setsockopt() call to block until the prefix is 303 allocated (or an error indication from the network is received). 305 Alternatively a new Socket API is defined - getsc() which allows 306 applications to express their desired type of session continuity 307 service. The new getsc() API will return an IPv6 address that is 308 associated with the desired session continuity service and with 309 status information indicating whether or not the desired service was 310 provided. 312 An application that wishes to secure a desired service will call 313 getsc() with the service type definition and a place to contain the 314 provided IP address, and call bind() to associate that IP address 315 with the Socket (See code example in Section 4 below). 317 When the IP stack is required to use a source IP address of a 318 specified type, it can use an existing address, or request a new IP 319 prefix (of the same type) from the network and create a new one. If 320 the host does not already have an IPv6 prefix of that specific type, 321 it must request one from the network. 323 Using an existing address from an existing prefix is faster but might 324 yield a less optimal route (if a hand-off event occurred after its 325 configuration). On the other hand, acquiring a new IP prefix from 326 the network may be slower due to signaling exchange with the network. 328 Applications can control the stack's operation by setting a new flag 329 - ON_NET flag - which directs the IP stack whether to use a 330 preconfigured source IP address (if exists) or to request a new IPv6 331 prefix from the current serving network and configure a new IP 332 address. 334 This new flag is added to the set of flags in the 335 IPV6_ADDR_PREFERENCES option at the IPPROTO_IPV6 level. It is used 336 in setsockopt() to set the desired behavior. 338 4. Usage example 340 The following example shows the code for creating a Stream socket 341 (TCP) with a Session-Lasting source IP address: 343 #include 344 #include 346 // Socket information 347 int s ; // Socket id 349 // Source information (for secsc() and bind()) 350 sockaddr_in6 sourceInfo // my address and port for bind() 351 in6_addr sourceAddress // will contain the provisioned source 352 // IP address 353 uint8_t sc_type = IPV6_REQUIRE_SESSION_LASTING_IP ; 354 // For requesting a Session-Lasting 355 // source IP address 357 // Destination information (for connect()) 358 sockaddr_in6 serverInfo ; // server info for connect() 360 // Create an IPv6 TCP socket 361 s = socket(AF_INET6, SOCK_STREAM, 0) ; 362 if (s!=0) { 363 // Handle socket creation error 364 // ... 365 } // if socket creation failed 366 else { 367 // Socket creation is successful 368 // The application cannot connect yet, since it wants to use a 369 // Session-Lasting source IP address It needs to request the 370 // Session-Lasting source IP before connecting 371 if (setsc(s, &sourceAddress, &sc_type)) == 0){ 372 // setting session continuity to Session Lasting is successful 373 // sourceAddress now contains the Session-Lasting source IP 374 // address 376 // Bind to that source IP address 377 sourceInfo.sin6_family = AF_INET6 ; 378 sourceInfo.sin6_port = 0 // let the stack choose the port 379 sourceInfo.sin6_address = sourceAddress ; 380 // Use the source address that was 381 // generated by the setsc() call 382 if (bind(s, &sourceInfo, sizeof(sourceInfo))==0){ 383 // Set the desired server's information for connect() 384 serverInfo.sin6_family = AF_INET6 ; 385 serverInfo.sin6_port = SERVER_PORT_NUM ; 386 serverAddress.sin6_addr = SERVER_IPV6_ADDRESS ; 388 // Connect to the server 389 if (connect(s, &serverInfo, sizeof(serverInfo))==0) { 390 // connect successful (3-way handshake has been completed 391 // with Session-Lasting source address. 392 // Continue application functionality 393 // ... 394 } // if connect() is successful 395 else { 396 // connect failed 397 // ... 398 // Application code that handles connect failure and closes 399 // the socket 400 // ... 401 } // if connect() failed 402 } // if bind() successful 403 else { 404 // bind() failed 405 // ... 406 // Application code that handles bind failure and closes 407 // the socket 408 // ... 409 } // if bind() failed 410 } // if setsc() was successful and of a Session-Lasting source address was provided 411 else { 412 // application code that does not use Session-lasting IP address 413 // The application may either connect without the desired 414 // Session-lasting service, or close the socket 415 //... 416 } // if setsc() failed 417 } // if socket was created successfully 419 // The rest of the application's code 420 // ... 422 5. Backwards Compatibility Considerations 424 Backwards compatibility support is required by the following 3 types 425 of entities: 427 - The Applications on the mobile host 429 - The IP stack in the mobile host 431 - The network infrastructure 433 5.1. Applications 435 Legacy applications that do not support the OnDemand functionality 436 will use the legacy API and will not be able to take advantage of the 437 On-Demand Mobility feature. 439 Applications using the new OnDemand functionality must be aware that 440 they may be executed in legacy environments that do not support it. 441 Such environments may include a legacy IP stack on the mobile host, 442 legacy network infrastructure, or both. In either case, the API will 443 return an error code and the invoking applications may just give up 444 and use legacy calls. 446 5.2. IP Stack in the Mobile Host 448 New IP stacks must continue to support all legacy operations. If an 449 application does not use On-Demand functionality, the IP stack must 450 respond in a legacy manner. 452 If the network infrastructure supports On-Demand functionality, the 453 IP stack should follow the application request: If the application 454 requests a specific address type, the stack should forward this 455 request to the network. If the application does not request an 456 address type, the IP stack must not request an address type and leave 457 it to the network's default behavior to choose the type of the 458 allocated IP prefix. If an IP prefix was already allocated to the 459 host, the IP stack uses it and may not request a new one from the 460 network. 462 5.3. Network Infrastructure 464 The network infrastructure may or may not support the On-Demand 465 functionality. How the IP stack on the host and the network 466 infrastructure behave in case of a compatibility issue is outside the 467 scope of this API specification. 469 6. Summary of New Definitions 471 6.1. New APIs 473 setsc() enables applications to request a specific type of source IP 474 address in terms of session continuity. Its definition is: 476 int setsc (int sockfd, in6_addr *sourceAddress, sc_type addressType) ; 478 Where: 479 - sockfd - is the socket descriptor of the socket with which a 480 specific address type is associated 481 - sourceAddress - is a pointer to an area allocated for setsc() to place 482 the generated source IP address of the desired session 483 continuity type 484 - addressType - Is the desired type of session continuity service. 485 It is a 3-bit field containing one of the following 486 values: 487 0 - Reserved 488 1 - FIXED_IPV6_ADDRESS 489 2 - SESSION_LASTING_IPV6_ADDRESS 490 3 - NON_PERSISTENT_IPV6_ADDRESS 491 4 - GRACEFUL_REPLACEMENT_IPV6_ADDRESS 492 5-7 - Reserved 494 setsc() returns the status of the operation: 495 - 0 - Address was successfully generated 496 - EAI_REQUIREDIPNOTSUPPORTED - the required service type is not supported 497 - EAI_REQUIREDIPFAILED - the network could not fulfill the desired request 499 6.2. New Flags 501 The following flag is added to the list of flags in the 502 IPV6_ADDR_PREFERENCE option at the IPPROTO6 level: 504 IPV6_REQUIRE_SRC_ON_NET - set IP stack address allocation behavior 506 If set, the IP stack will request a new IPv6 prefix of the desired 507 type from the current serving network and configure a new source IP 508 address. If reset, the IP stack will use a preconfigured one if it 509 exists. If there is no preconfigured IP address of the desired type, 510 a new prefix will be requested and used for creating the IP address. 512 7. Security Considerations 514 The setting of certain IP address type on a given socket may be 515 restricted to privileged applications. For example, a Fixed IP 516 Address may be provided as a premium service and only certain 517 applications may be allowed to use them. Setting and enforcement of 518 such privileges are outside the scope of this document. 520 8. IANA Considerations 522 This document has no IANA considerations. 524 9. Contributors 526 This document was merged with [I-D.sijeon-dmm-use-cases-api-source]. 527 We would like to acknowledge the contribution of the following people 528 to that document as well: 530 Sergio Figueiredo 531 Altran Research, France 532 Email: sergio.figueiredo@altran.com 534 Younghan Kim 535 Soongsil University, Korea 536 Email: younghak@ssu.ac.kr 538 John Kaippallimalil 539 Huawei, USA 540 Email: john.kaippallimalil@huawei.com 542 10. Acknowledgements 544 We would like to thank Wu-chi Feng, Alexandru Petrescu, Jouni 545 Korhonen, Sri Gundavelli, Dave Dolson and Lorenzo Colitti for their 546 valuable comments and suggestions on this work. 548 11. References 550 11.1. Normative References 552 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 553 Requirement Levels", BCP 14, RFC 2119, 554 DOI 10.17487/RFC2119, March 1997, 555 . 557 [RFC5014] Nordmark, E., Chakrabarti, S., and J. Laganier, "IPv6 558 Socket API for Source Address Selection", RFC 5014, 559 DOI 10.17487/RFC5014, September 2007, 560 . 562 [RFC6724] Thaler, D., Ed., Draves, R., Matsumoto, A., and T. Chown, 563 "Default Address Selection for Internet Protocol Version 6 564 (IPv6)", RFC 6724, DOI 10.17487/RFC6724, September 2012, 565 . 567 11.2. Informative References 569 [I-D.sijeon-dmm-use-cases-api-source] 570 Jeon, S., Figueiredo, S., Kim, Y., and J. Kaippallimalil, 571 "Use Cases and API Extension for Source IP Address 572 Selection", draft-sijeon-dmm-use-cases-api-source-06 (work 573 in progress), March 2017. 575 [RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, 576 A., Peterson, J., Sparks, R., Handley, M., and E. 577 Schooler, "SIP: Session Initiation Protocol", RFC 3261, 578 DOI 10.17487/RFC3261, June 2002, 579 . 581 [RFC5213] Gundavelli, S., Ed., Leung, K., Devarapalli, V., 582 Chowdhury, K., and B. Patil, "Proxy Mobile IPv6", 583 RFC 5213, DOI 10.17487/RFC5213, August 2008, 584 . 586 [RFC5563] Leung, K., Dommety, G., Yegani, P., and K. Chowdhury, 587 "WiMAX Forum / 3GPP2 Proxy Mobile IPv4", RFC 5563, 588 DOI 10.17487/RFC5563, February 2010, 589 . 591 [RFC5944] Perkins, C., Ed., "IP Mobility Support for IPv4, Revised", 592 RFC 5944, DOI 10.17487/RFC5944, November 2010, 593 . 595 [RFC6275] Perkins, C., Ed., Johnson, D., and J. Arkko, "Mobility 596 Support in IPv6", RFC 6275, DOI 10.17487/RFC6275, July 597 2011, . 599 [RFC6824] Ford, A., Raiciu, C., Handley, M., and O. Bonaventure, 600 "TCP Extensions for Multipath Operation with Multiple 601 Addresses", RFC 6824, DOI 10.17487/RFC6824, January 2013, 602 . 604 [RFC7333] Chan, H., Ed., Liu, D., Seite, P., Yokota, H., and J. 605 Korhonen, "Requirements for Distributed Mobility 606 Management", RFC 7333, DOI 10.17487/RFC7333, August 2014, 607 . 609 Authors' Addresses 611 Alper Yegin 612 Actility 613 Istanbul 614 Turkey 616 Email: alper.yegin@actility.com 618 Danny Moses 619 Intel Corporation 620 Petah Tikva 621 Israel 623 Email: danny.moses@intel.com 625 Kisuk Kweon 626 Samsung 627 Suwon 628 South Korea 630 Email: kisuk.kweon@samsung.com 632 Jinsung Lee 633 Samsung 634 Suwon 635 South Korea 637 Email: js81.lee@samsung.com 639 Jungshin Park 640 Samsung 641 Suwon 642 South Korea 644 Email: shin02.park@samsung.com 645 Seil Jeon 646 Sungkyunkwan University 647 Suwon 648 South Korea 650 Email: seiljeon@skku.edu