Folks, I would like to discuss the demand for DMM traffic steering as preparation for Toronto.
DMM enables smart deployment and selection of network components serving as User-Plane anchor to the mobile node. The MN's IP address or prefix (HNP/HoA) is assigned to the selected anchor and bound to the MN's locator (CoA, pCoA, ..) Now, there are two cases: (1) Selected anchor is in the network of the MN's HoA/HNP (topologically correct address) (2) Selected anchor is not in the network of the MN's HoA/HNP (topologically incorrect address) Case (1) is what IP mobility assumed so far. Default routes in the transport network deliver the packet into the network which hosts the MN's assigned anchor. Case (2) can happen in 2 cases: (a) MN gets assigned a new anchor mid-session but wants to keep its HoA/HNP. That's what has been called so far anchor re-location (b) MN has a stable IP address (e.g. profile-bound) but the network wants to select an anchor according to the requested service, i.e. anchor should be close to a local server or CDN cache. In that case the MN's IP address will be topologically incorrect from the very beginning of its attachment. All cases (a) and (b) may require steering the MN's traffic according to a host policy, as the route deviates from the default. First questions we may rise: I) Are we on the same page regarding the above cases? II) What comes first in DMM: IP address configuration or anchor selection? Hope we can discuss some opinions ahead of the meeting. marco
_______________________________________________ dmm mailing list dmm@ietf.org https://www.ietf.org/mailman/listinfo/dmm
