idnits 2.17.1 draft-kanugovi-intarea-mams-protocol-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 : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) 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 (January 20, 2017) is 2646 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) No issues found here. Summary: 1 error (**), 0 flaws (~~), 2 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 INTAREA S. Kanugovi 3 Internet-Draft S. Vasudevan 4 Intended status: Standards Track Nokia 5 Expires: July 24, 2017 F. Baboescu 6 Broadcom 7 J. Zhu 8 Intel 9 S. Peng 10 Huawei 11 January 20, 2017 13 Multiple Access Management Services 14 draft-kanugovi-intarea-mams-protocol-02 16 Abstract 18 A communication network includes an access network segment that 19 delivers data to/from the users and an associated core network 20 segment providing connectivity with the application servers. 21 Multiconnectivity scenarios are common where an end-user device can 22 simultaneously connect to multiple communication networks based on 23 different technology implementations and network architectures like 24 WiFi, LTE, DSL. A smart selection and combination of access and core 25 network paths that can dynamically adapt to changing network 26 conditions can improve quality of experience for a user in such a 27 Multiconnectivity scenario and improve overall network utilization 28 and efficiency. This document presents the problem statement and 29 proposes solution principles. It specifies the requirements and 30 reference architecture for a multi-access management services 31 framework that can be used to flexibly select the best combination of 32 access and core network paths for uplink and downlink, as well as the 33 flexible usage of uplink and downlink, ensuring better network 34 efficiency and enhanced application performance. 36 Status of This Memo 38 This Internet-Draft is submitted in full conformance with the 39 provisions of BCP 78 and BCP 79. 41 Internet-Drafts are working documents of the Internet Engineering 42 Task Force (IETF). Note that other groups may also distribute 43 working documents as Internet-Drafts. The list of current Internet- 44 Drafts is at http://datatracker.ietf.org/drafts/current/. 46 Internet-Drafts are draft documents valid for a maximum of six months 47 and may be updated, replaced, or obsoleted by other documents at any 48 time. It is inappropriate to use Internet-Drafts as reference 49 material or to cite them other than as "work in progress." 51 This Internet-Draft will expire on July 24, 2017. 53 Copyright Notice 55 Copyright (c) 2017 IETF Trust and the persons identified as the 56 document authors. All rights reserved. 58 This document is subject to BCP 78 and the IETF Trust's Legal 59 Provisions Relating to IETF Documents 60 (http://trustee.ietf.org/license-info) in effect on the date of 61 publication of this document. Please review these documents 62 carefully, as they describe your rights and restrictions with respect 63 to this document. Code Components extracted from this document must 64 include Simplified BSD License text as described in Section 4.e of 65 the Trust Legal Provisions and are provided without warranty as 66 described in the Simplified BSD License. 68 Table of Contents 70 1. Conventions used in this document . . . . . . . . . . . . . . 3 71 2. Contributing Authors . . . . . . . . . . . . . . . . . . . . 3 72 3. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 73 4. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4 74 5. Problem Statement . . . . . . . . . . . . . . . . . . . . . . 5 75 6. Solution Principles . . . . . . . . . . . . . . . . . . . . . 5 76 7. Requirements . . . . . . . . . . . . . . . . . . . . . . . . 6 77 7.1. Access technology agnostic interworking . . . . . . . . . 6 78 7.2. Support common transport deployments . . . . . . . . . . 6 79 7.3. Independent Access path selection for Uplink and Downlink 6 80 7.4. Core selection independent of uplink and downlink access 6 81 7.5. Adaptive network path selection . . . . . . . . . . . . . 7 82 7.6. Multipath support and Aggregation of access link 83 capacities . . . . . . . . . . . . . . . . . . . . . . . 7 84 7.7. Scalable mechanism based on user plane interworking . . . 7 85 7.8. Separate Control and Data plane functions . . . . . . . . 7 86 7.9. Lossless Path (Connection) Switching . . . . . . . . . . 8 87 7.10. Concatenation and Fragmentation to adapt to MTU 88 differences . . . . . . . . . . . . . . . . . . . . . . . 8 89 7.11. Configuring network middleboxes based on negotiated 90 protocols . . . . . . . . . . . . . . . . . . . . . . . . 8 91 7.12. Policy based Optimal path selection . . . . . . . . . . . 8 92 7.13. MAMS Control signaling . . . . . . . . . . . . . . . . . 8 93 7.14. Service discovery and reachability . . . . . . . . . . . 9 94 8. MAMS Reference Architecture . . . . . . . . . . . . . . . . . 9 95 9. Solution Principles . . . . . . . . . . . . . . . . . . . . . 11 96 10. Implementation considerations . . . . . . . . . . . . . . . . 13 97 11. Applicability to Mobile Edge Computing . . . . . . . . . . . 13 98 12. Security Considerations . . . . . . . . . . . . . . . . . . . 14 99 12.1. Data and Control plane security . . . . . . . . . . . . 14 100 13. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 14 101 14. References . . . . . . . . . . . . . . . . . . . . . . . . . 14 102 14.1. Normative References . . . . . . . . . . . . . . . . . . 14 103 14.2. Informative References . . . . . . . . . . . . . . . . . 15 104 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 15 106 1. Conventions used in this document 108 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 109 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 110 document are to be interpreted as described in [RFC2119]. 112 2. Contributing Authors 114 The editors gratefully acknowledge the following additional 115 Contributors in alphabetical order: Hannu Flinck/Nokia, Nurit 116 Sprecher/Nokia 118 3. Introduction 120 Multi Access Management Services (MAMS) is a programmable framework 121 that provides mechanisms for flexible selection of network paths in a 122 multi-access communication environment, based on application needs, 123 which can leverage network intelligence and policies to dynamically 124 adapt to changing network/link conditions. The network path 125 selection and configuration procedures use the user plane to exchange 126 data between the functional elements in the network and the end-user 127 device without any impact to the control plane signaling schemes of 128 each individual access network. For example, in a multi-access 129 network with LTE and WiFi technologies, existing LTE and existing 130 WiFi signaling procedures will be used to setup the LTE and WiFi 131 connections, respectively. The proposed MAMS framework offers the 132 capabilities of smart selection and flexible combination of access 133 paths and core network paths. It is a broad programmable framework 134 providing functions beyond just sharing network policies, e.g. in 135 comparison to ANDSF that provides policies/rules for assisting 3GPP 136 devices to discover and select available access networks, that allows 137 choosing and configuring user plane protocols and treatment depending 138 on needs of the application. 140 The document presents the requirements, solution principles and 141 functional architecture for the MAMS framework. MAMS mechanisms are 142 not dependent on any specific network and transport protocols like 143 TCP, UDP, GRE, MPTCP etc. It co-exists and complements the existing 144 protocols by providing a way to negotiate and configure the protocols 145 based on client and network capabilities. Further it allows 146 exchanges of network state information and leveraging network 147 intelligence to optimize the performance of such protocols. 149 An important goal for MAMS is to ensure that there is minimal or no 150 dependency on the actual access technologies of the participating 151 links, beyond the fact that the MAMS functional elements can be 152 placed in the user plane. This allows the scheme to be future proof, 153 for addition of new access technologies and for independent 154 technology evolution of the existing access and core networks. 156 4. Terminology 158 "Client": The end-user device supporting connections with multiple 159 access nodes, possibly over different access technologies. 161 "Multiconnectivity Client": A client with multiple network 162 connections. 164 "Access network": The segment in the network that delivers user data 165 packets to the client via an access link like WiFi airlink, LTE 166 airlink, or DSL. 168 "Core": The functional element that anchors the client's IP address 169 used for communication with applications via the network. 171 "User Plane Gateway": The functional element that can intercept and 172 route user data packets. 174 "Network Connection manager"(NCM): A functional entity in the network 175 that oversees distribution of data packets over the multiple 176 available access and core network paths. 178 "Client Connection Manager" (CCM): A functional entity in the client 179 that exchanges MAMS Signaling with the Network Connection Manager and 180 configures the multiple network paths for transport of user data. 182 "Network Multi Access Data Proxy" (N-MADP): This functional entity in 183 the network handles the user data traffic forwarding across multiple 184 network paths. N-MADP is responsible for MAMS related user-plane 185 functionalities in the network. 187 "Client Multi Access Data Proxy" (C-MADP): This functional entity in 188 the client handles the user data traffic forwarding across multiple 189 network paths. C-MADP is responsible for MAMS related user-plane 190 functionalities in the client. 192 5. Problem Statement 194 Typically, an end-user device has access to multiple communication 195 networks based on different technologies, say LTE, WiFi, DSL, 196 MuLTEfire, for accessing application services. Different 197 technologies exhibit benefits and limitations in different scenarios. 198 For example, WiFi leverages the large spectrum available in 199 unlicensed spectrum to deliver high capacities at low cost in 200 uncongested scenarios with small user population, but can show 201 significant degradation in application performance in congested 202 scenarios with large user population. Another example is LTE 203 network, the capacity of which is often constrained by high cost and 204 limited availability of the licensed spectrum, but offers predictable 205 service even in multi-user scenarios due to controlled scheduling and 206 licensed spectrum usage. 208 Additionally, the use of a particular access network path is often 209 coupled with the use of its associated core network. For example, in 210 an enterprise that has deployed WiFi and LTE communications network, 211 enterprise applications, like printers, Corporate Audio and Video 212 conferencing, are accessible only via WiFi access connected to the 213 enterprise hosted WiFi core, whereas the LTE access can be used to 214 get LTE operator core anchored services including access to public 215 Internet. 217 Application performance in different scenarios, therefore becomes 218 dependent on the choice of the communication networks based on 219 different technologies (e.g. WiFi and LTE) due to the tight coupling 220 of the access and the core network paths. Therefore to achieve the 221 best possible application performance in a wide range of possible 222 scenarios, a framework is needed that allows the selection and 223 flexible combination of access and core network paths for uplink and 224 downlink data delivery. 226 For example, in uncongested scenarios, it would be beneficial to use 227 WiFi access in both uplink and downlink for connecting to enterprise 228 applications. Whereas in congested scenarios, where use of WiFi in 229 uplink by multiple users can lead to degraded capacity and increased 230 delays due to contention, it would be beneficial to use scheduled LTE 231 as uplink combined with WiFi as downlink. 233 6. Solution Principles 235 This document proposes a Multiple Access Management Services(MAMS) 236 framework for dynamic selection and flexible combination of access 237 and core network paths as uplink and downlink for a device connected 238 to multiple communication networks. The multiple communication 239 networks interwork at the user plane. The selection of paths is 240 based on negotiation of capabilities (of device and network) and 241 network link quality between the user plane functional elements at 242 the end-user device/client (C-MADP) and the network (N-MADP).NCM has 243 the intelligence to setup and offer the best network path based on 244 device and network capabilities, application needs and knowledge of 245 the network state. 247 The NCM communicates with the Client Connection Manager (CCM), a 248 functional element in the device, for negotiation, sharing 249 information on the network path conditions, and configuring usage of 250 the network paths. The messages between the NCM and CCM are carried 251 as user plane data over any of the available network paths between 252 the NCM and CCM. 254 7. Requirements 256 The requirements set out in this section are for the definition of 257 behavior of the MAMS mechanism and the related functional elements. 259 7.1. Access technology agnostic interworking 261 The access nodes can be of different technology types like LTE, WiFi 262 etc. Since MAMS routes user plane data packets at the IP layer, 263 which makes it agnostic to the type of underlying technology used at 264 the access nodes. 266 7.2. Support common transport deployments 268 The network path selection and user data distribution should work 269 transparently across transport deployments that include e2e IPsec, 270 VPNs, and middleboxes like NATs and proxies. 272 7.3. Independent Access path selection for Uplink and Downlink 274 IP layer routing enables the client to transmit on uplink using one 275 access and receive data on downlink using another access, allowing 276 client and network connection manager to select the access paths for 277 uplink and downlink independent of each other. 279 7.4. Core selection independent of uplink and downlink access 281 A client is able to flexibly select the Core, independent of the 282 access paths used to reach the Core, depending on the application 283 needs. 285 7.5. Adaptive network path selection 287 The MAMS functional elements have the ability to determine the 288 quality of each of the network paths, e.g. access link delay and 289 capacity. The network path quality information is fed into the logic 290 for selection of combination of network paths to be used for 291 transporting user data. The path selection algorithm can use network 292 path quality information, in addition to other considerations like 293 network policies, for optimizing network usage and enhancing QoE 294 delivered to the user. 296 7.6. Multipath support and Aggregation of access link capacities 298 MAMS supports distribution and aggregation of user data across 299 multiple network paths at the IP layer. MAMS allows the client to 300 leverage the combined capacity of the multiple network connections by 301 enabling simultaneous transport of user data over multiple network 302 paths. If required, packet re-ordering is done at the receiver, 303 client(C-MADP) and/or the network (N-MADP), when user data packets 304 are received out of order. MAMS allows flexibility to choose the 305 flow steering and aggregation protocol based on capabilities 306 supported by the client and the network data plane entities, C-MADP 307 and N-MADP respectively. A MAMS multi-connection aggregation 308 solution should support existing transport and network layer 309 protocols like TCP, UDP, GRE. If flow aggregation functions are 310 realized using existing protocols such as Multi-Path TCP(MPTCP) and 311 SCTP, MAMS framework should allow use and configuration of these 312 aggregation protocols. 314 7.7. Scalable mechanism based on user plane interworking 316 The mechanism is based on user plane interworking, requiring only 317 that the MAMS functional elements (NCM and N-MADP) should be added in 318 the user plane path between the client and the network. The 319 interworking functionality is based on generically available routing 320 and tunneling capabilities. This makes solution easy to deploy and 321 scale when different networks are added and removed. 323 7.8. Separate Control and Data plane functions 325 The client negotiates with a network connection manager on the choice 326 of access for both uplink and downlink, as well as the Core. The 327 network connection manager configures the actual user plane data 328 distribution function. This allows common control protocol to be 329 used with multiple and potentially different user plane (e.g. 330 tunneling) protocols, thus maintaining a clear separation between the 331 control and data plane functions. This makes the MAMS framework 332 scalable and extensible, e.g. by being amenable to SDN based 333 architecture and implementations. 335 7.9. Lossless Path (Connection) Switching 337 When switching data traffic from one path (connection) to another, 338 packets may be lost or delivered out-of-order, which will have 339 negative impacts on the performance of higher layer protocols, e.g. 340 TCP. MAMS should provide necessary mechanisms to ensure in-order 341 delivery at the receiver, as well as support retransmissions at the 342 transmitter during path switching. 344 7.10. Concatenation and Fragmentation to adapt to MTU differences 346 MAMS should support heterogeneous access networks, which may have 347 different MTU sizes. Moreover, tunneling protocols also have a big 348 impact on the MTU size. Hence, MAMS should support concatenation 349 such that multiple IP packets may be encapsulated into a single 350 packet to improve efficiency. MAMS should also support fragmentation 351 such that a single IP packet may be fragmented and encapsulated into 352 multiple ones to avoid IP fragmentation. 354 7.11. Configuring network middleboxes based on negotiated protocols 356 MAMS enables identification of the optimal parameters that may be 357 used for configuring the middle-boxes, like binding expiry times and 358 supported MTUs, for efficient operation of the user plane protocols, 359 depending on the data plane related parameters negotiated between the 360 client and the network, e.g. Configuring longer binding expiry time 361 in NATs when UDP transport is used in contrast to the scenario where 362 TCP is configured at the transport layer. 364 7.12. Policy based Optimal path selection 366 MAMS framework should support consideration of policies at the 367 client, in addition to guidance from the network in determination of 368 network paths selected for different application services. 370 7.13. MAMS Control signaling 372 MAMS control signaling is carried over the user plane and is 373 transparent to the transport protocols. MAMS should support delivery 374 of control signaling over the existing Internet protocols, e.g. TCP 375 or UDP. 377 7.14. Service discovery and reachability 379 MAMS offers the flexibility for the functional entity NCM to be 380 collocated with any of the network elements and reachable via any of 381 the available user plane paths. MAMS framework allows the 382 flexibility for the CCM to choose one of the available NCMs and 383 exchange control plane signaling over any of the available user plane 384 paths. The choice of NCM can be based on considerations like, but 385 not limited to, quality of link through which the NCM is reachable, 386 Client preference, or pre-configuration etc. 388 8. MAMS Reference Architecture 390 +---------------------------------------------------+ 391 ! +---------------+ +---------------+ ! 392 ! ! ! ! ! ! 393 ! !Core(IP anchor)! !Core(IP anchor)! ! 394 ! !(network n) ! !(network 1) ! ! 395 ! ! ! ! ! ! 396 ! +---------------+ +---------------+ ! 397 ! +-----------------------+ ! 398 ! ! +-----+ +------+ ! ! 399 ! ! ! NCM ! !N-MADP| ! ! 400 ! ! +-----+ +------+ ! ! 401 ! +-----------------------+ ! 402 ! ! 403 ! +-----------+ +---------------+ ! 404 ! ! ! ! ! ! 405 ! ! ! ! ! ! 406 ! !access ! !access ! ! 407 ! !(network n)! !(network 1) ! ! 408 ! ! ! ! ! ! 409 ! +-----------+ +---------------+ ! 410 +---------------------------------------------------+ 412 +-----------------+ 413 ! +------+ +-----+! 414 ! |C-MADP| ! CCM !! 415 ! +------+ +-----+! 416 ! Client ! 417 +-----------------+ 419 Figure 1: MAMS Reference Architecture 421 Figure 1 illustrates MAMS architecture for the scenario of a client 422 served by multiple (n) networks. The NCM and N-MADP, functional 423 elements, are introduced for supporting MAMS mechanisms. The 424 architecture is extendable to combine any number of networks, as well 425 as any choice of participating network types (e.g. LTE, WLAN, 426 MuLTEfire, DSL) and deployment architectures (e.g. with user plane 427 gateway function at the access edge). 429 The N-MADP entity, at the network, handles the user data traffic 430 forwarding across multiple network paths, as well as other user-plane 431 functionalities, e.g. encapsulation, fragmentation, concatenation, 432 reordering, retransmission, etc. N-MADP is the distribution node for 433 uplink and downlink data delivery with visibility of packets at the 434 IP layer. There can be multiple N-MADP entities in the network, e.g. 435 to load balance across clients. A single client can also be served 436 by multiple N-MADP instances, e.g to address different user plane 437 requirements of multiple applications running on the client. 438 Identification and distribution rules for different user data traffic 439 types at the N-MADP are configured by the NCM. The NCM configures 440 the data delivery paths, access links, and user plane protocols to be 441 used by N-MADP for downlink user data traffic. The CCM configures 442 the data delivery paths, access links, and user plane protocols to be 443 used by C-MADP for uplink user data traffic based on the signaling 444 exchanged with NCM. In the UL, NCM allows selection of the core 445 network path to be used by N-MADP to route uplink user data. 447 The scheduling and load balancing algorithm at the N-MADP is 448 configured by the NCM, based on static and/or dynamic network 449 policies like assigning access and core paths for specific user data 450 traffic type, data volume based percentage distribution, and link 451 availability and feedback information from exchange of MAMS signaling 452 with the CCM at the Client. 454 At the client, the Client Connection Manager (CCM) manages the 455 multiple network connections. CCM is responsible for exchange of 456 MAMS signaling messages with the NCM for supporting functions like UL 457 and DL user network path configuration for transporting user data 458 packets, link probing and reporting to support adaptive network path 459 selection by NCM. In the downlink, for the user data received by the 460 client, it configures C-MADP such that application data packet 461 received over any of the accesses to reach the appropriate 462 application on the client. In the uplink, for the data transmitted 463 by the client, it configures the C-MADP to determine the best access 464 links to be used for uplink data based on a combination of local 465 policy and network policy delivered by the NCM. The C-MADP entity 466 handles all MAMS-specific user-plane functionalities at the client, 467 e.g. encapsulation, fragmentation, concatenation, reordering, 468 retransmissions, etc. C-MADP is configured by CCM based on signaling 469 exchange with NCM and local policies at the client. 471 A user plane tunnel, e.g. IPsec, may be needed for transporting user 472 data packets between the N-MADP at the network and the C-MADP at the 473 client. The user plane tunnel is needed to ensure security and 474 routability of the user plane packets between the N-MADP and the 475 C-MADP. The most common implementation of the user plane tunnel is 476 the IPsec. C-MADP receives the configuration from CCM indicates, to 477 C-MADP, the access network interfaces over which the IPsec tunnel 478 needs to be established, and for each of the indicated interfaces, 479 the parameters (e.g. N-MADP IPsec endpoint IP address reachable via 480 the indicated access network interface) for setting up the IPsec 481 tunnel. C-MADP sets up the IPsec tunnel with the N-MADP via each of 482 the indicated access network interfaces, using appropriate signaling, 483 say IKEv2 and parameters provided by the CCM. In deployments where 484 N-MADP and the client are connected via a secure and direct IP path, 485 user plane tunnel may not be needed. Note that the method for 486 transporting user data packets between the N-MADP and the C-MADP 487 should be general, based on the existing protocols, and consider 488 minimizing overhead. 490 9. Solution Principles 491 +----------------------------------------+ 492 | MAMS enabled Network of Networks | 493 | +-----+ +-----+ +-----+ +------+ 494 +-----------------+ | | | | | | | | || 495 | Client | | |Netwo| |Netwo| | | | || 496 | +-----+ +-----+ | | |rk 1 | |rk 2 + |NCM | N-MADP|| 497 | C-MADP |CCM | | | |(LTE)| |(WiFi) | | | || 498 | +-----+ +-----+ | | +-----+ +-----+ +-----+ +------| 499 -+----------------+ +----------------------------------------+ 500 | | | | | | | 501 | | | | | | | 502 | | 1.SETUP CONNECTION| | | | 503 |<-----------+------------>| | | | 504 | | | + + | | 505 | | | 2. MAMS Capabilities Exchange | | 506 | | |<-------------+----------+-------->| | 507 | | | | | | | 508 | | + | | | | 509 | | 3. SETUP CONNECTION | | | 510 |<--+-------------------------------->| | | 511 | 4c. Config| 4a. NEGOTIATE NETWORK PATHS, FLOW |4b. Config| 512 | C-MADP | PROTOCOL AND PARAMETERS | |N-MADP | 513 | |<----->|<-------------+----------+-------->|<-------->| 514 | | | + + | | 515 | | |5. ESTABLISH USER PLANE PATH ACCORDING TO | 516 | | | SELECTED FLOW PROTOCOL | | | 517 | |<---------------------+----------+------------------->| 518 | | | | | | | 519 + + + + + + + 521 Figure 2: MAMS call flow 523 Figure 2 illustrates the MAMS signaling mechanism for negotiation of 524 network paths and flow protocols between the client and the network. 525 In this example scenario, the client is connected to two networks 526 (say LTE and WiFi). 528 1. UE connects to network 1 and gets an IP address assigned by 529 network 1. 530 2. CCM communicates with NCM functional element via the network 1 531 connection and exchanges capabilities and parameters for MAMS 532 operation. Note: The NCM credentials (e.g. NCM IP Address) can 533 be made known to the UE by pre-provisioning. 534 3. Client sets up connection with network 2 and gets an IP address 535 assigned by network 2. 536 4. CCM and NCM negotiate capabilities and parameters for 537 establishment of network paths, which are then used to configure 538 user plane functions N-MADP at the network and C-MADP at the 539 client. 541 4a. CCM and NCM negotiate network paths, flow routing and 542 aggregation protocols, and related parameters. 544 4b. NCM communicates with the N-MADP to exchange and configure 545 flow aggregation protocols, policies and parameters in alignment 546 with those negotiated with the CCM. 548 4c. CCM communicates with the C-MADP to exchange and configure 549 flow aggregation protocols, policies and parameters in alignment 550 with those negotiated with the NCM. 552 5. C-MADP and N-MADP establish the user plane paths, e.g. using IKE 553 [RFC7296] signaling, based on the negotiated flow aggregation 554 protocols and parameters specified by NCM. 556 CCM and NCM can further exchange messages containing access link 557 measurements for link maintenance by the NCM. NCM evaluates the link 558 conditions in the UL and DL across LTE and WiFi, based on link 559 measurements reported by CCM and/or link probing techniques and 560 determines the UL and DL user data distribution policy. NCM and CCM 561 also negotiate application level policies for categorizing 562 applications, e.g. based on DSCP, Destination IP address, and 563 determining which of the available network paths, needs to be used 564 for transporting data of that category of applications. NCM 565 configures N-MADP and CCM configures C-MADP based on the negotiated 566 application policies. CCM may apply local application policies, in 567 addition to the application policy conveyed by the NCM. 569 10. Implementation considerations 571 MAMS builds on commonly available functions available on terminal 572 devices that can be delivered as a software update over the popular 573 end-user device operating systems, enabling rapid deployment and 574 addressing the large deployed device base. 576 11. Applicability to Mobile Edge Computing 578 Mobile edge computing (MEC) is an access-edge cloud platform being 579 standardized at ETSI, whose initial focus was to improve quality of 580 experience by leveraging intelligence at cellular (e.g. 3GPP 581 technologies like LTE) access edge, and the scope is now being 582 extended to support access technologies beyond 3GPP. This 583 applicability of the framework described in this document to the MEC 584 platform has been evaluated and tested in different network 585 configurations. 587 The NCM and N-MADP are hosted on the MEC cloud server that is located 588 in the user plane path at the edge of multi-technology access 589 networks, and in a particular large venue use case at the edge of LTE 590 and Wi-Fi access networks. The NCM and CCM negotiate the network 591 path combinations based on application needs and the necessary user 592 plane protocols to manage the multiple paths. The network conditions 593 reported by the CCM to the NCM is used in addition to Radio Analytics 594 application residing at the MEC to configure the uplink and downlink 595 access paths according to changing radio and congestion conditions. 597 The aim of these enhancements is to improve the end-user's quality of 598 experience by leveraging the best network path based on application 599 needs and network conditions, and building on the advantages of 600 significantly reduced latency and the dynamic and real-time exposure 601 of radio network information available at the MEC. 603 12. Security Considerations 605 This section details the security considerations for the MAMS 606 framework. 608 12.1. Data and Control plane security 610 Signaling messages and the user data in MAMS framework rely on the 611 security of the underlying network transport paths. When this cannot 612 be assumed, network connection manager configures use of protocols, 613 like IPsec [RFC4301] [RFC3948], for securing user data and MAMS 614 signaling messages. 616 13. Contributors 618 This protocol is the outcome of work by many engineers, not just the 619 authors of this document. In alphabetical order, the contributors to 620 the project are: Barbara Orlandi, Bongho Kim,David Lopez-Perez, Doru 621 Calin, Jonathan Ling, Krishna Pramod A., Lohith Nayak, Michael 622 Scharf. 624 14. References 626 14.1. Normative References 628 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 629 Requirement Levels", BCP 14, RFC 2119, 630 DOI 10.17487/RFC2119, March 1997, 631 . 633 [RFC4301] Kent, S. and K. Seo, "Security Architecture for the 634 Internet Protocol", RFC 4301, DOI 10.17487/RFC4301, 635 December 2005, . 637 14.2. Informative References 639 [RFC3948] Huttunen, A., Swander, B., Volpe, V., DiBurro, L., and M. 640 Stenberg, "UDP Encapsulation of IPsec ESP Packets", 641 RFC 3948, DOI 10.17487/RFC3948, January 2005, 642 . 644 [RFC7296] Kaufman, C., Hoffman, P., Nir, Y., Eronen, P., and T. 645 Kivinen, "Internet Key Exchange Protocol Version 2 646 (IKEv2)", STD 79, RFC 7296, DOI 10.17487/RFC7296, October 647 2014, . 649 Authors' Addresses 651 Satish Kanugovi 652 Nokia 654 Email: satish.k@nokia.com 656 Subramanian Vasudevan 657 Nokia 659 Email: vasu.vasudevan@nokia.com 661 Florin Baboescu 662 Broadcom 664 Email: florin.baboescu@broadcom.com 666 Jing Zhu 667 Intel 669 Email: jing.z.zhu@intel.com 671 Shuping Peng 672 Huawei 674 Email: pengshuping@huawei.com