WG Action: RECHARTER: Mobility EXTensions for IPv6 (mext)
The Mobility EXTensions for IPv6 (mext) working group in the Internet Area of the IETF has been rechartered. For additional information, please contact the Area Directors or the working group Chairs. Mobility EXTensions for IPv6 (mext) --- Current Status: Active Last updated: 2011-01-11 Chairs: Marcelo Bagnulo marc...@it.uc3m.es Julien Laganier juli...@qualcomm.com Internet Area Directors: Ralph Droms rdroms.i...@gmail.com Jari Arkko jari.ar...@piuha.net Internet Area Advisor: Jari Arkko jari.ar...@piuha.net Mailing Lists: General Discussion: m...@ietf.org 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 (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. ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
WG Action: RECHARTER: Mobility EXTensions for IPv6 (mext)
The Mobility EXTensions for IPv6 (mext) working group in the Internet Area of the IETF has been rechartered. For additional information, please contact the Area Directors or the working group Chairs. Mobility EXTensions for IPv6 (mext) - Status: Active Working Group Chairs: Marcelo Bagnulo (marc...@it.uc3m.es) Julien Laganier (juli...@qualcomm.com) Internet Area Directors: Ralph Droms (rdroms.i...@gmail.com) Jari Arkko (jari.ar...@piuha.net) Internet Area Advisor: Jari Arkko (jari.ar...@piuha.net) Mailing Lists: General Discussion: m...@ietf.org 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 (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. 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: Dec 2010 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. Dec 2010 Submit I-D(s) related to specific updates and corrections of RFC 3775 to IESG for publication as Proposed Standard. Jan 2011 Submit I-D 'Home agent reliability' to IESG for publication as a Proposed Standard. Jan 2011 Submit I-D 'Mobile IPv6 Operation with Firewalls' to IESG for publication as Informational. 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. Dec 2011 Submit I-D 'Negotiation of the protection for payload traffic' to IESG for publication as Proposed Standard. ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
WG Action: RECHARTER: Mobility EXTensions for IPv6 (mext)
The charter of the Mobility EXTensions for IPv6 (mext) working group in
the Internet Area of the IETF has been updated. For additional
information, please contact the Area Directors or the working group
Chairs.
Mobility EXTensions for IPv6 (mext)
---
Last Modified: 2008-05-08
Additional information is available at tools.ietf.org/wg/mext
Chair(s):
Julien Laganier ([EMAIL PROTECTED])
Marcelo Bagnulo ([EMAIL PROTECTED])
Internet Area Director(s):
Jari Arkko ([EMAIL PROTECTED])
Mark Townsley ([EMAIL PROTECTED])
Internet Area Advisor:
Jari Arkko ([EMAIL PROTECTED])
Mailing Lists:
General Discussion: [EMAIL PROTECTED]
To Subscribe: https://www1.ietf.org/mailman/listinfo/mext
Archive: http://www1.ietf.org/mail-archive/web/mext/current
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)
The MEXT Working Group continues the work of the former MIP6, NEMO,
and MONAMI6 Working Groups.
The primary goal of MEXT will be to (A) enhance base IPv6 mobility by
continuing work on developments that are required for wide-scale
deployments and specific deployment scenarios. Additionally, (B) the
working group will ensure that any issues identified by implementation
and interoperability experience are addressed, and that the base
specifications are maintained. (C) The group will also produce
informational documentation, such as design rationale documents or
description of specific issues within the protocol.
Deployment considerations call for (A.1) solutions to enable
dual-stack operation, (A.2) mechanisms to support high-availability
home agents, (A.3) allowing the use of multiple interfaces in mobile
nodes, (A.4) ways to employ Mobile IPv6 in the presence of firewalls,
(A.5) address the specific needs of automotive and aviation
communities for route optimisation in network mobility, (A.6)
support for AAA is needed as a continuation of earlier work on
bootstrapping, (A.7) revocation of binding, (A.8) generic
notification message format and (A.9) extended DMSIP home
network support .
Work items related to large scale deployment include:
(A.1) A Solution for Mobile IPv6 and NEMO session continuity for dual
stack hosts which attach to IPv4 access networks. Additionally
provide a mechanism for carrying IPv4 packets via the Home agent
for Mobile IPv6 or NEMO capable dual-stack hosts.
(A.2) A protocol based solution for enhancing the reliability of home
agents and a method to force a host/router to switch home agents.
A mechanism to force an MN to switch the HA that is currently
serving it. This is required in deployments where the HA needs to
be taken offline for maintenance.
(A.3) Use of multiple interfaces.
Today, the protocols do not provide suppport for simultaneous
differentiated use of multiple access technologies. Several
proposals exist for such support, and some of them have been
implemented and tested.
When a mobile host/router uses multiple network interfaces
simultaneously, or when multiple prefixes are available on a
single network interface, the mobile host/router would end up
with multiple Care-of Addresses (CoAs). In addition, the Home
Agent might be attached to multiple network interfaces, or to a
single network interface with multiple prefixes, hence resulting
in the option to use multiple IP addresses for the Home
Agent. This could result in the possibility of using a multitude
of bi-directional tunnels between pairs of {Home Agent address,
CoA} and a number of associated issues: establishment, selection
and modification of multiple simultaneous tunnels.
The objective of the WG is to produce a clear problem statement
and to produce standard track specifications to the problems
associated with the simultaneous use of multiple addresses for
either mobile hosts using Mobile IPv6 or mobile routers using
NEMO Basic Support and their variants (FMIPv6, HMIPv6,
etc). Where the effects of having multiple prefixes on a single
interface is identical to the effects of having multiple
interfaces each with a single prefix, the WG will consider a
generalized approach to cater for multiple prefixes available to
a mobile host/router.
The WG uses existing tunneling mechanisms defined for Mobile
IPv6. The involved nodes need to select which tunnel instance
to use when multiple ones are available due to multiple
addresses on either end. But the WG does not plan to define a
new mechanism for this, but rather document how to use
