I do not know your definition of approach vs solution, but one can argue DMM itself is about a deployment model and an approach. I always insisted its less of a protocol work and more about a tying many aspects. So, what we have been discussing is a solution approach which has the essential properties of CP/DP separation, aspect of optimized/stateless data plane, application specific gateway allocations .. etc and that at the end is an approach for realizing DMM.
Sri On 7/17/14 10:59 AM, "Alper Yegin" <alper.ye...@yegin.org> wrote: >Intense readingŠ :-) Lot of abstractions, which I can only follow by >relating to specific solutions. > >In my understanding, what Sri is describing is about "how to apply UP/CP >separation to various DMM solutions". >In the examples I see a number of DMM solutions defined with UP/CP >separation using Sri's terminology (e.g., per-flow mobility, access >network anchoring, host-specific route based solutions, etc). > >So, it's not a solution by itself, but it's an approach that can be >applied to various solution techniques to SDNize them. >And that indeed has value. > >Alper > > > > > > > > > > > > > > > > > _______________________________________________ dmm mailing list dmm@ietf.org https://www.ietf.org/mailman/listinfo/dmm
