Please check this updated REQ1 in draft-ietf-dmm-requirements-02:
REQ2: Transparency to Upper Layers when needed
DMM solutions MUST provide transparent mobility support above
the IP layer when needed. Such transparency is needed, for
example, when, upon change of point of attachment to the
Internet, an application flow cannot cope with a change in the
IP address. Otherwise, support for maintaining a stable home
IP address or prefix during handovers may be declined.
Motivation: The motivation of this requirement is to enable
more efficient use of network resources and more efficient
routing by not maintaining context at the mobility anchor when
there is no such need.
This requirement addresses the problems PS5 as well as the other
related problem O-PS1.
PS5: Wasting resources to provide mobility support to nodes that do
not need such support
IP mobility support is not always required, and not every
parameter of mobility context is always used. For example,
some applications do not need a stable IP address during a
handover to maintain IP session continuity. Sometimes, the
entire application session runs while the terminal does not
change the point of attachment.
O-PS1: Mobility signaling overhead with peer-to-peer communication
Wasting resources when mobility signaling (e.g., maintenance
of the tunnel, keep alive, etc.) is not turned off for peer-
to-peer communication. Peer-to-peer communications have
particular traffic patterns that often do not benefit from
mobility support from the network. Thus, the associated
mobility support signaling (e.g., maintenance of the tunnel,
keep alives, etc.) wastes network resources for no
application gain. In such a case, it is better to enable
mobility support selectively.
H Anthony Chan
_______________________________________________
dmm mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/dmm
