Skip to main content

Mobile User Plane Architecture for Distributed Mobility Management
draft-mhkk-dmm-mup-architecture-02

Document Type Replaced Internet-Draft (individual)
Expired & archived
Authors Satoru Matsushima , Katsuhiro Horiba , Yuya Kawakami , Tetsuya Murakami , Keyur Patel , Jakub Horn
Last updated 2025-03-02
Replaces draft-mhkk-dmm-srv6mup-architecture
Replaced by draft-ietf-dmm-mup-architecture
RFC stream (None)
Intended RFC status (None)
Formats
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-dmm-mup-architecture
Telechat date (None)
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:

Abstract

This document defines the Mobile User Plane (MUP) architecture for Distributed Mobility Management. The requirements for Distributed Mobility Management described in [RFC7333] can be satisfied by routing fashion. In MUP Architecture, session information between the entities of the mobile user plane is turned to routing information so that mobile user plane can be integrated into dataplane. MUP architecture is designed to be pluggable user plane part of existing mobile service architectures, enabled by auto-discovery for the use plane. Segment Routing provides network programmability for a scalable option with it. While MUP architecture itself is independent from a specific dataplane protocol, several dataplane options are available for the architecture. This document describes IPv6 dataplane in Segment Routing case (SRv6 MUP) due to the DMM requirement, and is suitable for mobile services which require a large IP address space.

Authors

Satoru Matsushima
Katsuhiro Horiba
Yuya Kawakami
Tetsuya Murakami
Keyur Patel
Jakub Horn

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)