RFC 8822 on 5G Wireless Wireline Convergence User Plane Encapsulation (5WE)
rfc-editor@rfc-editor.org Sat, 17 April 2021 19:23 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 A55A73A2E06 for <ietf-announce@ietfa.amsl.com>; Sat, 17 Apr 2021 12:23:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 sW9nTtjiCnM6 for <ietf-announce@ietfa.amsl.com>; Sat, 17 Apr 2021 12:23:02 -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 75E533A2DFF for <ietf-announce@ietf.org>; Sat, 17 Apr 2021 12:23:02 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id BAC4EF407BD; Sat, 17 Apr 2021 12:22:45 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8822 on 5G Wireless Wireline Convergence User Plane Encapsulation (5WE)
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: <20210417192245.BAC4EF407BD@rfc-editor.org>
Date: Sat, 17 Apr 2021 12:22:45 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/4NsdB0wOUot2BK24NHc1AGBvcYk>
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: Sat, 17 Apr 2021 19:23:08 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8822
Title: 5G Wireless Wireline Convergence User
Plane Encapsulation (5WE)
Author: D. Allan, Ed.,
D. Eastlake,
D. Woolley
Status: Informational
Stream: IETF
Date: April 2021
Mailbox: david.i.allan@ericsson.com,
d3e3e3@gmail.com,
david.woolley@team.telstra.com
Pages: 8
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-allan-5g-fmc-encapsulation-08.txt
URL: https://www.rfc-editor.org/info/rfc8822
DOI: 10.17487/RFC8822
As part of providing wireline access to the 5G Core (5GC), deployed
wireline networks carry user data between 5G residential gateways and
the 5G Access Gateway Function (AGF). The encapsulation method
specified in this document supports the multiplexing of traffic for
multiple PDU sessions within a VLAN-delineated access circuit,
permits legacy equipment in the data path to inspect certain packet
fields, carries 5G QoS information associated with the packet data,
and provides efficient encoding. It achieves this by specific points
of similarity with the Point-to-Point Protocol over Ethernet (PPPoE)
data packet encapsulation (RFC 2516).
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