Deployment of Control-/Data-Plane separation in DMM

Document Type Expired Internet-Draft (individual)
Last updated 2016-01-07 (latest revision 2015-07-06)
Stream (None)
Intended RFC status (None)
Expired & archived
pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at


The DMM working group is currently looking at solutions for mobility management based on control and data plane separation. In this context, the network entities in charge for the mobility control function are separated from the data plane nodes, responsible mainly for, but not limited to, data packet forwarding. This vision allows for the design of different interaction methods between the mobility control function and the data plane nodes. One of such mechanisms being currently discussed devises an SDN-based abstraction layer between control and data planes, embodied by an SDN Network Controller. This latter interfaces to the mobility control function through a north-bound interface (NBI), and programs the underneath infrastructure through a south-bound interface (SBI), e.g., OpenFlow. This draft describes multiple deployment scenarios for NBI and SBI interworking, given that multiple network controllers could be deployed in order to meet performance requirements e.g., related to latency.


Fabio Giust (
Marco Liebsch (

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