Re: [MEXT] suggest charter item for distributed mobility work

[Sri Gundavelli <[e-mail]>]

Hi Jari:

Thanks for the updated charter text. This looks good to me. Just couple of
comments. 

* The approach of closest home agent selection is one aspect of the DMM
proposal. I assumed it includes other aspects such as CP/DP separation.
Does the charter text gives such provision for such extensions ?
* The BOF discussed the chained models around CMIP/PMIP mobility domains and
the optimized routing paths in such context. The potential extensions should
be applicable to both client-based/network-based and chained mobility
models. 
* There were some issues that were raised around CP/DP separation and around
the distributed deployment models. There should be analysis on the issues
around such deployment models, in relation to centralized models that are
deployed today.

If the charter text broadly allows for some work around this, probably it
should be fine. Finally, glad to see this work not defining a new protocol
suite. But bringing value to the existing protocols.


Regards
Sri


On 1/11/11 2:54 AM, "Jari Arkko" <[e-mail]> wrote:

> All,
> 
> I have been thinking about what to do about the distributed mobility
> work since our meeting in Beijing. My suggestion is to add a work item
> to the MEXT charter. Here's the proposed new item:
> 
> Jari
> 
> 
> Mobility EXTensions for IPv6 (mext)
> -----------------------------------
> 
>  Current Status: Active
> 
>  Chairs:
>      Marcelo Bagnulo <[e-mail]>
>      Julien Laganier <[e-mail]>
> 
>  Internet Area Directors:
>      Ralph Droms <[e-mail]>
>      Jari Arkko <[e-mail]>
> 
>  Internet Area Advisor:
>      Jari Arkko <[e-mail]>
> 
>  Mailing Lists:
>      General Discussion: [e-mail]
>      To Subscribe:       https://www.ietf.org/mailman/listinfo/mext
>      Archive:            http://www.ietf.org/mail-archive/web/mext
> 
> Description of Working Group:
> 
>   Mobile IPv6 specifies routing support which permits an IPv6 host to
>   continue using its home address as it moves around the Internet,
>   enabling continuity of sessions. Mobile IPv6 supports transparency above
>   the IP layer, including maintenance of active transport level sessions.
>   In addition, network mobility (NEMO) mechanisms built on top of Mobile
>   IPv6 allow managing the mobility of an entire network, as it changes its
>   point of attachment to the Internet. The base specifications consist of:
> 
>   o RFC 3775 (Mobile IPv6)
>   o RFC 3963 (NEMO)
>   o RFC 4877 (Mobile IPv6 Operation with IKEv2)
>   o RFC 5555 (Dual Stack Mobile IPv6)
>   o RFC 5648 (Multiple Care-of Addresses Registration)
>   o RFC 5846 (Binding Revocation)
>   o RFC-to-be (Flow Binding Policy Transport and Flow Binding Policy Format)
> 
>   The MEXT Working Group continues the work of the former MIP6, NEMO, and
>   MONAMI6 Working Groups.
> 
>   The primary goal of MEXT will be to enhance base IPv6 mobility by
>   continuing work on developments that are required for wide-scale
>   deployments and specific deployment scenarios. Additionally, the working
>   group will ensure that any issues identified by implementation and
>   interoperability experience are addressed, and that the base
>   specifications are maintained. The group will also produce informational
>   documentation, such as design rationale documents or description of
>   specific issues within the protocol.
> 
>   The MEXT WG will also explore experimental alternative security
>   mechanisms. The security mechanism specified in the existing standard
>   track RFCs (RFC3775bis, RFC4877) remains the mandatory to implement
>   mechanism that guarantees interoperability between different
>   implementations. The MEXT WG is chartered to deliver one or more
>   experimental alternative mechanisms. All the alternative solutions will
>   be published as experimental RFCs.
> 
>   The working group will also work on operational considerations on
>   setting up Mobile IPv6 networks so that traffic is distributed
>   in an optimal way, for instance by using existing protocol mechanisms
>   to select the closest home agents for new clients.
> 
>   In addition, the working group will bring to completion earlier work on
>   prefix delegation for NEMO, RADIUS  support for Mobile IPv6, Mobile IPv6
>   operation with firewalls, and home agent reliability specifications.
> 
>   Work items related to base specification maintenance include: Create and
>   maintain issue lists that are generated on the basis of implementation
>   and interoperability experience. Address specific issues with specific
>   updates or revisions of the base specification. Currently known specific
>   issues include support for overlapping (private) IPv4 home addresses,
>   negotiation of the protection required for payload traffic, and
>   discovery of the home agent address in IPv4-only networks.
> 
> 
> Goals and Milestones:
>   Jun 2011 - Submit I-D 'Mobile IPv6 Operation with Firewalls' to IESG for
> publication as Informational.
>   Jun 2011 - Submit I-D 'Home agent reliability' to IESG for publication as a
> Proposed Standard.
>   Aug 2011 - Submit I-Ds on alternative security mechanisms to the IESG for
> publication as Experimental.
>   Sep 2011 - Submit I-D 'Overlapping IPv4 address support' to IESG for
> publication as Proposed Standard.
>   Sep 2011 - Submit I-D 'Home agent discovery in IPv4-only networks via DHCP'
> to IESG for publication as Proposed Standard.
>   Oct 2011 - Submit I-D 'Operational considerations for distributed use of
> Mobile IPv6' for publication as Informational
>   Dec 2011 - Submit I-D 'Negotiation of the protection for payload traffic' to
> IESG for publication as Proposed Standard.
>   Dec 2011 - Submit the I-D 'RADIUS Mobile IPv6 Support' to IESG for
> publication as a proposed standard.
> 
> 
>             
>  charterjan2011.txt   charterjan2011withdmm.txt
>   
> skipping to change at line 60 skipping to change at line 60
>   specific issues within the protocol.   specific issues within the protocol.
>   
>   The MEXT WG will also explore experimental alternative security   The MEXT
> WG will also explore experimental alternative security
>   mechanisms. The security mechanism specified in the existing standard
> mechanisms. The security mechanism specified in the existing standard
>   track RFCs (RFC3775bis, RFC4877) remains the mandatory to implement   track
> RFCs (RFC3775bis, RFC4877) remains the mandatory to implement
>   mechanism that guarantees interoperability between different   mechanism
> that guarantees interoperability between different
>   implementations. The MEXT WG is chartered to deliver one or more
> implementations. The MEXT WG is chartered to deliver one or more
>   experimental alternative mechanisms. All the alternative solutions will
> experimental alternative mechanisms. All the alternative solutions will
>   be published as experimental RFCs.   be published as experimental RFCs.
>   
>  
>    The working group will also work on operational considerations on
>    setting up Mobile IPv6 networks so that traffic is distributed
>    in an optimal way, for instance by using existing protocol mechanisms
>    to select the closest home agents for new clients.
>                  
>   In addition, the working group will bring to completion earlier work on   In
> addition, the working group will bring to completion earlier work on
>   prefix delegation for NEMO, RADIUS  support for Mobile IPv6, Mobile IPv6
> prefix delegation for NEMO, RADIUS  support for Mobile IPv6, Mobile IPv6
>   operation with firewalls, and home agent reliability specifications.
> operation with firewalls, and home agent reliability specifications.
>   
>   Work items related to base specification maintenance include: Create and
> Work items related to base specification maintenance include: Create and
>   maintain issue lists that are generated on the basis of implementation
> maintain issue lists that are generated on the basis of implementation
>   and interoperability experience. Address specific issues with specific   and
> interoperability experience. Address specific issues with specific
>   updates or revisions of the base specification. Currently known specific
> updates or revisions of the base specification. Currently known specific
>   issues include support for overlapping (private) IPv4 home addresses,
> issues include support for overlapping (private) IPv4 home addresses,
>   negotiation of the protection required for payload traffic, and
> negotiation of the protection required for payload traffic, and
>   discovery of the home agent address in IPv4-only networks.   discovery of
> the home agent address in IPv4-only networks.
>   
> Goals and Milestones: Goals and Milestones:
>  
>   Done     - Submit I-D 'Mobile IPv6 Vendor Specific Option' to IESG for
> publication as a Proposed Standard   Jun 2011 - Submit I-D 'Mobile IPv6
> Operation with Firewalls' to IESG for publication as Informational.
>   Done     - Submit I-D 'Mobile IPv6 Experimental Allocations' to IESG for
> publication as a Proposed Standard   Jun 2011 - Submit I-D 'Home agent
> reliability' to IESG for publication as a Proposed Standard.
>   Done     - Submit I-D 'Mobile IPv6 Dual-Stack Operation' to IESG for
> publication as a Proposed Standard.
>   Done     - Submit I-D 'Motivation for Authentication I-D' to IESG for
> publication as Informational.
>   Done     - Submit Multiple CoA Registration to IESG
>   Done     - Submit I-D 'Goals for AAA HA Interface' to IESG for publication
> as Informational.
>   Done     - Submit -00 draft on Route Optimization Needs for Automobile and
> Highway Deployments
>   Done     - Submit -00 draft on Route Optimization Needs for Aircraft and
> Spacecraft Deployments
>   Done     - Submit I-D 'Mobility Header Home Agent Switch Message' to IESG
> for publication as a Proposed Standard
>   Done     - Submit final doc on Route Optimization Needs for Aircraft and
> Spacecraft Deployments, for Informational
>   Done     - Submit 00 draft on Binding Revocation
>   Done     - Submit the final doc on MIB for NEMO Basic Support to the IESG,
> for Proposed Standard
>   Done     - Submit draft on Binding Revocation to IESG
>   Done     - Submit I-D(s) related to specific updates and corrections of RFC
> 3775 to IESG for publication as Proposed Standard.
>   Done     - Submit the final doc on Prefix Delegation for NEMO to the IESG,
> for Proposed Standard
>   Dec 2010 - Submit the I-D 'RADIUS Mobile IPv6 Support' to IESG for
> publication as a proposed standard.
>   Jan 2011 - Submit I-D 'Mobile IPv6 Operation with Firewalls' to IESG for
> publication as Informational.
>   Jan 2011 - Submit I-D 'Home agent reliability' to IESG for publication as a
> Proposed Standard.
>   Aug 2011 - Submit I-Ds on alternative security mechanisms to the IESG for
> publication as Experimental.   Aug 2011 - Submit I-Ds on alternative security
> mechanisms to the IESG for publication as Experimental.
>   Sep 2011 - Submit I-D 'Overlapping IPv4 address support' to IESG for
> publication as Proposed Standard.   Sep 2011 - Submit I-D 'Overlapping IPv4
> address support' to IESG for publication as Proposed Standard.
>   Sep 2011 - Submit I-D 'Home agent discovery in IPv4-only networks via DHCP'
> to IESG for publication as Proposed Standard.   Sep 2011 - Submit I-D 'Home
> agent discovery in IPv4-only networks via DHCP' to IESG for publication as
> Proposed Standard.
>  
>    Oct 2011 - Submit I-D 'Operational considerations for distributed use of
> Mobile IPv6' for publication as Informational
>   Dec 2011 - Submit I-D 'Negotiation of the protection for payload traffic' to
> IESG for publication as Proposed Standard.   Dec 2011 - Submit I-D
> 'Negotiation of the protection for payload traffic' to IESG for publication as
> Proposed Standard.
>  
>    Dec 2011 - Submit the I-D 'RADIUS Mobile IPv6 Support' to IESG for
> publication as a proposed standard.
>   
>  End of changes. 4 change blocks.
> 18 lines changed or deleted 8 lines changed or added
> This html diff was produced by rfcdiff 1.32. The latest version is available
> from http://www.levkowetz.com/ietf/tools/rfcdiff/
> 
> _______________________________________________
> MEXT mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/mext