Internet-Draft draft-ietf-dmm-mup-architecture-01.txt is now available. It is
a work item of the Distributed Mobility Management (DMM) WG of the IETF.

   Title:   Mobile User Plane Architecture for Distributed Mobility Management
   Authors: Satoru Matsushima
            Katsuhiro Horiba
            Yuya Kawakami
            Tetsuya Murakami
            Keyur Patel
            Jakub Horn
   Name:    draft-ietf-dmm-mup-architecture-01.txt
   Pages:   23
   Dates:   2025-10-20

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.

The IETF datatracker status page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-dmm-mup-architecture/

There is also an HTML version available at:
https://www.ietf.org/archive/id/draft-ietf-dmm-mup-architecture-01.html

A diff from the previous version is available at:
https://author-tools.ietf.org/iddiff?url2=draft-ietf-dmm-mup-architecture-01

Internet-Drafts are also available by rsync at:
rsync.ietf.org::internet-drafts


_______________________________________________
dmm mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to