RFC 9433: Segment Routing over IPv6 for the Mobile User Plane
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC9433
- Published
- July 2023
- Authors
- S. Matsushima; C. Filsfils; M. Kohno; P. Camarillo; D. Voyer
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- int
- Pages
- 29
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9434Drone Remote Identification Protocol (DRIP) ArchitectureCurrent
July 2023
- RFC 9428Transmission of IPv6 Packets over Near Field CommunicationCurrent
July 2023
- RFC 9441Static Context Header Compression (SCHC) Compound Acknowledgement (ACK)Current
July 2023
- RFC 9442Static Context Header Compression (SCHC) over Sigfox Low-Power Wide Area Network (LPWAN)Current
July 2023
- RFC 9453Applicability and Use Cases for IPv6 over Networks of Resource-constrained Nodes (6lo)Current
September 2023
- RFC 9461Service Binding Mapping for DNS ServersCurrent
November 2023
- RFC 9462Discovery of Designated ResolversCurrent
November 2023
- RFC 9463DHCP and Router Advertisement Options for the Discovery of Network-designated Resolvers (DNR)Current
November 2023
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?