RFC 8743: Multiple Access Management Services Multi-Access Management Services (MAMS)
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC8743
- Published
- March 2020
- Authors
- S. Kanugovi; F. Baboescu; J. Zhu; S. Seo
- Status
- INFORMATIONAL
- Stream
- INDEPENDENT
- Area
- —
- Pages
- 143
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8724SCHC: Generic Framework for Static Context Header Compression and FragmentationUpdated
April 2020
- RFC 9391Static Context Header Compression over Narrowband Internet of ThingsCurrent
April 2023
- RFC 8041Use Cases and Operational Experience with Multipath TCPCurrent
January 2017
- RFC 8677Name-Based Service Function Forwarder (nSFF) Component within a Service Function Chaining (SFC) FrameworkCurrent
November 2019
- RFC 7586The Scalable Address Resolution Protocol (SARP) for Large Data CentersCurrent
June 2015
- RFC 5171Cisco Systems UniDirectional Link Detection (UDLD) ProtocolCurrent
April 2008
- RFC 4562MAC-Forced Forwarding: A Method for Subscriber Separation on an Ethernet Access NetworkCurrent
June 2006
- RFC 2643Cabletron's SecureFast VLAN Operational ModelCurrent
August 1999
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?