%% You should probably cite draft-mhkk-dmm-mup-architecture instead of this I-D.
@techreport{mhkk-dmm-srv6mup-architecture-05,
    number =    {draft-mhkk-dmm-srv6mup-architecture-05},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-mhkk-dmm-srv6mup-architecture/05/},
    author =    {Satoru Matsushima and Katsuhiro Horiba and Ashiq Khan and Yuya Kawakami and Tetsuya Murakami and Keyur Patel and Miya Kohno and Teppei Kamata and Pablo Camarillo and Jakub Horn and Daniel Voyer and Shay Zadok and Israel Meilik and Ashutosh Agrawal and Kumaresh Perumal},
    title =     {{Mobile User Plane Architecture using Segment Routing for Distributed Mobility Management}},
    pagetotal = 21,
    year =      2023,
    month =     mar,
    day =       13,
    abstract =  {This document defines the Mobile User Plane (MUP) architecture using Segment Routing (SR) for Distributed Mobility Management. The requirements for Distributed Mobility Management described in {[}RFC7333{]} can be satisfied by routing fashion. Mobile services are deployed over several parts of IP networks. An SR network can accommodate a part of those networks, or all those networks. IPv6 dataplane option (SRv6) is suitable for both cases especially for the latter case thanks to the large address space, so this document illustrates the MUP deployment cases with IPv6 dataplane. MUP Architecture can incorporate existing session based mobile networks. By leveraging Segment Routing, mobile user plane can be integrated into the dataplane. In that routing paradigm, session information between the entities of the mobile user plane is turned to routing information.},
}