Multiple Access Management Services Multi-Access Management Services
RFC 8743, “Multiple Access Management Services Multi-Access Management Services”, is an Informational document published in March 2020 by S. Kanugovi, F. Baboescu, J. Zhu, S. Seo. The canonical text is published by the RFC Editor.
Abstract
In multiconnectivity scenarios, the clients can simultaneously connect to multiple networks based on different access technologies and network architectures like Wi-Fi, LTE, and DSL. Both the quality of experience of the users and the overall network utilization and efficiency may be improved through the smart selection and combination of access and core network paths that can dynamically adapt to changing network conditions.
This document presents a unified problem statement and introduces a solution for managing multiconnectivity. The solution has been developed by the authors based on their experiences in multiple standards bodies, including the IETF and the 3GPP. However, this document is not an Internet Standards Track specification, and it does not represent the consensus opinion of the IETF.
This document describes requirements, solution principles, and the architecture of the Multi-Access Management Services (MAMS) framework. The MAMS framework aims to provide best performance while being easy to implement in a wide variety of multiconnectivity deployments. It specifies the protocol for (1) flexibly selecting the best combination of access and core network paths for the uplink and downlink, and (2) determining the user-plane treatment (e.g., tunneling, encryption) and traffic distribution over the selected links, to ensure network efficiency and the best possible application performance.
What “Informational” means
Published for the general information of the community. It does not define an IETF standard and carries no standards-track status.
The canonical text of RFC 8743 is hosted at rfc-editor.org. Available in HTML,TXT,PDF,XML.
- RFC 8742 Concise Binary Object Representation Sequences
- RFC 8744 Issues and Requirements for Server Name Identification Encryption in TLS
- RFC 8741 Ability for a Stateful Path Computation Element to Request and Obtain Control of a Label Switched Path
- RFC 8745 Path Computation Element Communication Protocol Extensions for Associating Working and Protection Label Switched Paths with Stateful PCE
- RFC 8740 Using TLS 1.3 with HTTP/2
- RFC 8746 Concise Binary Object Representation Tags for Typed Arrays
- RFC 8739 Support for Short-Term, Automatically Renewed Certificates in the Automated Certificate Management Environment
- RFC 8747 Proof-of-Possession Key Semantics for CBOR Web Tokens