[DMM] RFC 9433 on Segment Routing over IPv6 for the Mobile User Plane
rfc-editor@rfc-editor.org Fri, 21 July 2023 23:24 UTC
Return-Path: <wwwrun@rfcpa.amsl.com>
X-Original-To: dmm@ietfa.amsl.com
Delivered-To: dmm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F18F0C151522; Fri, 21 Jul 2023 16:24:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.855
X-Spam-Level:
X-Spam-Status: No, score=-0.855 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, RDNS_NONE=0.793, SPF_PASS=-0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id k5P71kXTHWAZ; Fri, 21 Jul 2023 16:24:10 -0700 (PDT)
Received: from rfcpa.amsl.com (unknown [50.223.129.200]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 530A3C151095; Fri, 21 Jul 2023 16:24:10 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 27D1E1ECFA2E; Fri, 21 Jul 2023 16:24:10 -0700 (PDT)
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, dmm@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20230721232410.27D1E1ECFA2E@rfcpa.amsl.com>
Date: Fri, 21 Jul 2023 16:24:10 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmm/ibRbya6PVfGyz3cs7EkxJd4pwOY>
Subject: [DMM] RFC 9433 on Segment Routing over IPv6 for the Mobile User Plane
X-BeenThere: dmm@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Distributed Mobility Management Working Group <dmm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmm>, <mailto:dmm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmm/>
List-Post: <mailto:dmm@ietf.org>
List-Help: <mailto:dmm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dmm>, <mailto:dmm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Jul 2023 23:24:14 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 9433
Title: Segment Routing over IPv6 for
the Mobile User Plane
Author: S. Matsushima, Ed.,
C. Filsfils,
M. Kohno,
P. Camarillo, Ed.,
D. Voyer
Status: Informational
Stream: IETF
Date: July 2023
Mailbox: satoru.matsushima@g.softbank.co.jp,
cf@cisco.com,
mkohno@cisco.com,
pcamaril@cisco.com,
daniel.voyer@bell.ca
Pages: 29
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-dmm-srv6-mobile-uplane-24.txt
URL: https://www.rfc-editor.org/info/rfc9433
DOI: 10.17487/RFC9433
This document discusses the applicability of Segment Routing over
IPv6 (SRv6) to the user plane of mobile networks. The network
programming nature of SRv6 accomplishes mobile user-plane functions
in a simple manner. The statelessness of SRv6 and its ability to
control both service layer path and underlying transport can be
beneficial to the mobile user plane, providing flexibility,
end-to-end network slicing, and Service Level Agreement (SLA) control
for various applications.
This document discusses how SRv6 could be used as the user plane of
mobile networks. This document also specifies the SRv6 Endpoint
Behaviors required for mobility use cases.
This document is a product of the Distributed Mobility Management Working Group of the IETF.
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