%% You should probably cite rfc8743 instead of this I-D.
@techreport{kanugovi-intarea-mams-framework-02,
    number =    {draft-kanugovi-intarea-mams-framework-02},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-kanugovi-intarea-mams-framework/02/},
    author =    {Satish Kanugovi and Florin Baboescu and Jing Zhu and Julius Mueller and SungHoon Seo},
    title =     {{Multiple Access Management Services}},
    pagetotal = 139,
    year =      2018,
    month =     sep,
    day =       4,
    abstract =  {In multiconnectivity scenarios the end-user devices can simultaneously connect to multiple networks based on different access technologies and network architectures like WiFi, LTE, DSL. Both the quality of experience of the users and the overall network utilization and efficiency may be improved through a smart selection and combination of access and core network paths that can dynamically adapt to changing network conditions. The document presents a unified problem statement and introduces a solution for managing multiconnectivity. The solution has been developed based on the authors' experience in multiple standards bodies including the IETF and 3GPP and is not an Internet Standard. It describes the requirements, solution principles and the architectural framework that ensures best performance and can be easily implemented in a wide variety of multiconnectivity deployments. It specifies the the protocol multi-access management to 1) flexibly select the best combination of access and core network paths for uplink and downlink, as well as 2) determining the user plane treatment and traffic distribution over the selected links ensuring better network efficiency and enhanced application performance.},
}