RFC 8743 on Multiple Access Management Services Multi-Access Management Services (MAMS)
rfc-editor@rfc-editor.org Wed, 25 March 2020 19:09 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1C2BE3A0F39 for <ietf-announce@ietfa.amsl.com>; Wed, 25 Mar 2020 12:09:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dbj4FwVLLuCO for <ietf-announce@ietfa.amsl.com>; Wed, 25 Mar 2020 12:09:32 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 820ED3A0FA9 for <ietf-announce@ietf.org>; Wed, 25 Mar 2020 12:08:21 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 03E36F406D4; Wed, 25 Mar 2020 12:08:11 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8743 on Multiple Access Management Services Multi-Access Management Services (MAMS)
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20200325190811.03E36F406D4@rfc-editor.org>
Date: Wed, 25 Mar 2020 12:08:11 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/gz9oRpHdDoN9sXzSmsin88ecH5k>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 Mar 2020 19:09:44 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8743
Title: Multiple Access Management Services Multi-Access
Management Services (MAMS)
Author: S. Kanugovi,
F. Baboescu,
J. Zhu,
S. Seo
Status: Informational
Stream: Independent
Date: March 2020
Mailbox: satish.k@nokia-bell-labs.com,
florin.baboescu@broadcom.com,
jing.z.zhu@intel.com,
sh.seo@kt.com
Pages: 143
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-kanugovi-intarea-mams-framework-04.txt
URL: https://www.rfc-editor.org/info/rfc8743
DOI: 10.17487/RFC8743
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.
INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC