Concluded WG Mobility EXTensions for IPv6 (mext)
Note: The data for concluded WGs is occasionally incorrect.
| WG | Name | Mobility EXTensions for IPv6 | |
|---|---|---|---|
| Acronym | mext | ||
| Area | Internet Area (int) | ||
| State | Concluded | ||
| Charter | charter-ietf-mext-06 | ||
| Document dependencies | |||
| Additional resources | Issue tracker, Wiki | ||
| Personnel | Chairs | Jouni Korhonen, Julien Laganier | |
| Mailing list | Address | mext@ietf.org | |
| To subscribe | https://www.ietf.org/mailman/listinfo/mext | ||
| Archive | https://mailarchive.ietf.org/arch/browse/mext |
Final Charter for 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.
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.
Milestones
| Date | Milestone | Associated documents |
|---|---|---|
| Mar 2013 | Evaluate the need for further work based on the identified gaps and revise the milestones and/or the charter of the group | |
| Mar 2013 | Submit I-D 'Gap Analysis' to the IESG for consideration as an Informational RFC. | |
| Jan 2013 | Submit I-D 'Solution Requirements' to the IESG for consideration as an Informational RFC. | |
| Jan 2013 | Submit I-D 'Practices ' to the IESG for consideration as an Informational RFC. | |
| Nov 2012 | Evaluate the need for additional working group document(s) for extensions to fill the identified gaps. | |
| Aug 2012 | Submit I-D 'Practices and Gap Analysis' as a working group document. To be Informational RFC. | |
| Aug 2012 | Submit I-D 'Solution Requirements' as a working group document. To be Informational RFC. |
Done milestones
| Date | Milestone | Associated documents |
|---|---|---|
| Done | Submit the final doc on Prefix Delegation for NEMO to the IESG, for Proposed Standard | |
| Done | Submit I-D(s) related to specific updates and corrections of RFC 3775 to IESG for publication as Proposed Standard. | |
| Done | Submit draft on Binding Revocation to IESG | |
| Done | Submit the final doc on MIB for NEMO Basic Support to the IESG, for Proposed Standard | |
| Done | Submit 00 draft on Binding Revocation | |
| Done | Submit final doc on Route Optimization Needs for Aircraft and Spacecraft Deployments, for Informational | |
| Done | Submit I-D 'Mobility Header Home Agent Switch Message' to IESG for publication as a Proposed Standard | |
| 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 'Motivation for Authentication I-D' to IESG for publication as Informational. | |
| Done | Submit I-D 'Mobile IPv6 Dual-Stack Operation' to IESG for publication as a Proposed Standard. | |
| Done | Submit I-D 'Mobile IPv6 Experimental Allocations' to IESG for publication as a Proposed Standard | |
| Done | Submit Multiple CoA Registration to IESG | |
| Done | Submit I-D 'Mobile IPv6 Vendor Specific Option' to IESG for publication as a Proposed Standard |