Hello,
Thank you Kostas for this rewrite. The charter reads better now.
Please see below for few comments.
On Jul 30, 2014, at 11:20 AM, Jouni Korhonen wrote:
> Folks,
>
> A major rewrite of the charter is in github (and below). Thanks to Kostas
> providing excellent feedbask on the text. Comments are welcome.
>
>
>
> Description of Working Group:
>
> Mobility management solutions lie at the center of the wireless Internet
> and enable mobile devices to partake in IP networks anytime and
> anywhere. The IETF Distributed Mobility Management (DMM) working group
> (WG) specifies solutions for IP networks so that traffic can be
> expedited between mobile and correspondent nodes. DMM solutions aim for
> transparency above the IP layer, including maintenance of active
> transport level sessions when mobile hosts or mobile networks change
> their point of attachment to the Internet.
>
> Wireless network deployments have traditionally relied on hierarchical
> schemes that often lead to centralized deployment models, where a small
> number of mobility anchors manage both mobility and reachability for a
> mobile node. The DMM WG will consider the latest developments in mobile
> networking research and operational practice (i.e. flat network
> architectures, the impact of virtualization, new deployment needs as
> wireless access technologies evolve in the coming years) and will
> describe how distributed mobility management addresses the new needs in
> this area better than previously standardized solutions.
>
> A topic of particular focus will be mobility anchoring in this new
> context, and the DMM working group is chartered to work on
> maintenance-oriented extensions of the Mobile IPv6 protocol family (RFC
> 5213, RFC 5844, RFC , RFC 5568, and RFC 6275) as well as new
> approaches which capitalize on other protocols specified by the IETF.
> When extending protocols that are not based on Mobile IP, DMM solutions
> will be have to be reviewed by the corresponding WGs.
>
> IPv6 is assumed to be present in both the mobile host/router and the
> access networks. DMM solutions are primarily targeted at IPv6
> deployments and are not required to support IPv4, in particular for the
> case where private IPv4 addresses and/or NATs are used. DMM solutions
> must maintain backward compatibility: If the network or the mobile
> host/router does not support the distributed mobility management
> protocol that should not prevent the mobile host/router gaining basic
> access (i.e., nomadic) to the network.
>
> Contrary to earlier IP mobility protocols, mobility management signaling
> paths and end-user traffic forwarding paths may differ. Further,
> mobility-related functions may be located in separate network nodes.
> DMM
> solutions should not distinguish between physical or virtualized
> networking functions. Whenever applicable, clarifications and additional
> features/capabilities for specific networking function deployment
> models, e.g. in virtualized environments, are in-scope and encouraged.
> Solutions may also specify the selection between the care-of addresses
> and home address(es)/prefix(es) for different application use cases.
>
> Work items related to distributed mobility management include:
>
> o Distributed mobility management deployment models and scenarios:
>describe the target high-level network architectures and
>deployment models where distributed mobility management
>protocol solutions could apply.
>
Can someone elaborate on what kind of information will go into such a document?
> o Enhanced mobility anchoring: define protocol solutions for a
>gateway and mobility anchor assignment and mid-session mobility
>anchor switching that go beyond what has been specified, for
>example, in RFC 6097, 6463, and 5142. Traffic steering
>associated with the anchor switch is also in-scope if deemed
>appropriate.
>
> o Forwarding path and signaling management: the function
>that handles mobility management signaling interacts with the
>DMM network elements for managing the forwarding state
>associated with a mobile node's IP traffic. These two functions
>may or may not be collocated. Furthermore, the forwarding state
>may also be distributed into multiple network elements instead
>of a single network element (e.g., anchor). Protocol extensions
>or new protocols will be specified to allow the above mentioned
>forwarding path and signalling management.
>
I cannot separate "mobility anchoring" from "fwding path and signaling
management".
Wherever you want to set your anchor or move your anchor to, you'd need
signaling and setting up data path. The two are inseparable.
Having said that, I'm OK to keep the current work item descriptions and
finalize rechartering. Once we have detailed discus
