[rfc-dist] RFC 9188 on Generic Multi-Access (GMA) Encapsulation Protocol
rfc-editor@rfc-editor.org Fri, 11 February 2022 07:35 UTC
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6239B3A0D49 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Thu, 10 Feb 2022 23:35:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.9
X-Spam-Level:
X-Spam-Status: No, score=-2.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, 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 MOYnGlTI7X2r for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Thu, 10 Feb 2022 23:35:20 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1581D3A0D55 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Thu, 10 Feb 2022 23:35:17 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 2CF14215785; Thu, 10 Feb 2022 23:35:17 -0800 (PST)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 499) id 900ABE52EF; Thu, 10 Feb 2022 23:35:15 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org
Message-Id: <20220211073515.900ABE52EF@rfc-editor.org>
Date: Thu, 10 Feb 2022 23:35:15 -0800
Subject: [rfc-dist] RFC 9188 on Generic Multi-Access (GMA) Encapsulation Protocol
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.34
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: rfc-dist <rfc-dist-bounces@rfc-editor.org>
A new Request for Comments is now available in online RFC libraries.
RFC 9188
Title: Generic Multi-Access (GMA) Encapsulation Protocol
Author: J. Zhu,
S. Kanugovi
Status: Experimental
Stream: Independent
Date: February 2022
Mailbox: jing.z.zhu@intel.com,
satish.k@nokia.com
Pages: 15
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-zhu-intarea-gma-14.txt
URL: https://www.rfc-editor.org/info/rfc9188
DOI: 10.17487/RFC9188
A device can be simultaneously connected to multiple networks, e.g.,
Wi-Fi, LTE, 5G, and DSL. It is desirable to seamlessly combine the
connectivity over these networks below the transport layer (L4) to
improve the quality of experience for applications that do not have
built-in multi-path capabilities. Such optimization requires
additional control information, e.g., a sequence number, in each
packet. This document presents a new lightweight and flexible
encapsulation protocol for this need. The solution has been developed
by the authors based on their experiences in multiple standards
bodies including the IETF and 3GPP. However, this document is not an
Internet Standard and does not represent the consensus opinion of the
IETF. This document will enable other developers to build
interoperable implementations in order to experiment with the
protocol.
EXPERIMENTAL: This memo defines an Experimental Protocol for the
Internet community. It does not specify an Internet standard of any
kind. Discussion and suggestions for improvement are requested.
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
_______________________________________________
rfc-dist mailing list
rfc-dist@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-dist
http://www.rfc-editor.org