20070517_mipshop_charter_original.txt | 20070517_mipshop_charter_revised.txt | |||
---|---|---|---|---|
Mobility for IP: Performance, Signaling and Handoff Optimization (mipshop) | Mobility for IP: Performance, Signaling and Handoff Optimization (MIPSHOP) | |||
Description of Working Group: | Description of Working Group: | |||
Mobile IPv6 enables IPv6 mobile nodes to continue using a given "home | Mobile IPv6 enables IPv6 mobile nodes to continue using a given "home | |||
address" in spite of changes in its point of attachment to the | address" in spite of changes in its point of attachment to the | |||
network. These changes may cause packet loss, and also represent | network. These changes may cause delay, packet loss, and also | |||
overhead traffic on the network. The previous MIPSHOP charter directed | represent overhead traffic on the network. The previous MIPSHOP WG | |||
the group to continue work (started by the Mobile IP Working group) on | worked on two technologies to address these issues. Hierarchical | |||
two technologies to address these issues. Hierarchical Mobile IPv6 | Mobile IPv6 (HMIPv6, RFC 4140) reduces the amount and latency of | |||
(HMIPv6, RFC 4140) reduces the amount and latency of signaling between | signaling between a MN, its Home Agent and one or more correspondent | |||
a MN, its Home Agent and one or more correspondent nodes. Fast | nodes. Fast Handovers for Mobile IPv6 (FMIPv6, RFC 4068) reduces | |||
Handovers for Mobile IPv6 (FMIPv6, RFC 4068) reduces packet loss by | packet loss by providing fast IP connectivity as soon as the mobile | |||
providing fast IP connectivity as soon as the mobile node establishes | node establishes a new point of attachment at a new link. | |||
a new point of attachment at a new link. | ||||
As part of its previous set of work items, MIPSHOP published these two | As part of its previous set of work items, MIPSHOP published these two | |||
protocols as experimental RFCs. An information document on how FMIPv6 | protocols as experimental RFCs. Further implementation work by the | |||
can operate over IEEE 802.11 was also published as an informational | community has increased the understanding of how FMIPv6 behaves or | |||
RFC. Further implementation work by the community has increased the | should behave on other link layers, and in general. Similarly, further | |||
understanding of how FMIPv6 behaves or should behave on other link | implementation and experimentation with HMIPv6 has resulted in better | |||
layers, and in general. Similarly, further implementation and | understanding of the protocol. Accordingly, MIPSHOP will continue work | |||
experimentation with HMIPv6 has resulted in better understanding of | on HMIPv6 and FMIPv6 and the necessary extensions in order to publish | |||
the protocol. Accordingly, MIPSHOP will continue work on HMIPv6 and | them as proposed standards. | |||
FMIPv6 in order to prepare their publication as proposed standards. | ||||
Additionally, the IEEE 802.21 Media Independent Handoff (MIH) working | Additionally, the IEEE 802.21 Media Independent Handoff (MIH) working | |||
group aims at providing services to assist with handoffs between | group aims at providing services to assist with handoffs between | |||
heterogeneous link-layer technologies, and across IP subnet | heterogeneous link-layer technologies, and across IP subnet | |||
boundaries. The information exchanges defined by IEEE 802.21 are | boundaries. The information exchanges defined by IEEE 802.21 are | |||
classified as MI (Media Independent) Event Service (MIES), MI Command | classified as MI (Media Independent) Event Service (MIES), MI Command | |||
Service (MICS), and MI Information Service (MIIS). The MIIS provides | Service (MICS), and MI Information Service (MIIS). The MIIS provides | |||
topological and location-related information of service networks. The | topological and location-related information of service networks. The | |||
MIES provides timely communications of wireless environment | MIES provides timely communications of wireless environment | |||
information via the delivery of events originating across the | information via the delivery of events originating across the | |||
link-layer or farther away. The MICS is an analogous service for | link-layer or farther away. The MICS is an analogous service for | |||
commands which can change the state of the wireless link or of a | commands which can change the state of the wireless link or of a | |||
host's point of attachment, potentially triggering further event | host's point of attachment, potentially triggering further event | |||
generation. MIH services can be delivered through link-layer specific | generation. MIH services can be delivered through link-layer specific | |||
solutions and/or through a "layer 3 or above" protocol. MIPSHOP will | solutions and/or through a "layer 3 or above" protocol. MIPSHOP will | |||
define the delivery of information for MIH services for this latter | define the delivery of information for MIH services for this latter | |||
case. Notice that this allows the network information to reside | case. Notice that this allows the network information to reside | |||
anywhere (not necessarily across the link-layer hop), and enables MIH | anywhere (not necessarily across the link-layer hop), and enables MIH | |||
services even in the absence of the corresponding link-layer | services even in the absence of the corresponding link-layer support. | |||
support. An L2 or L3 based mechanism to identify a valid information | An L3 based mechanism to identify a valid information server is also | |||
server is also required; in particular for L3, we expect that any of | required. A liaison with IEEE 802.21 has been established, and access | |||
the several current L3 discovery mechanisms will be used. A liaison | to the IEEE 802.21 drafts is granted to mipshop members. Interested | |||
with IEEE 802.21 has been established, and access to the IEEE 802.21 | members need to send a request to the WG chairs in order to obtain a | |||
drafts is granted to mipshop members. Interested members need to send | copy of the current IEEE 802.21 draft. | |||
a request to the WG chairs in order to obtain a copy of the current | ||||
IEEE 802.21 draft. | ||||
There have been several proposals to improve upon the Return | ||||
Routability procedure defined in MIPv6 (RFC 3775), both in terms of | ||||
the security of the mechanism as well as with respect to its | ||||
performance. In particular, discussions within the MOBOPTS Research | ||||
Group of the IRTF have centered on reducing the round trip times | ||||
required to complete the procedure, and on increasing the length of | ||||
time before the procedure needs to be run again. Some proposals are | ||||
mature enough that they will be taken over by MIPSHOP for | ||||
standardization. | ||||
The WG will be very proactive in seeking AD-coordinated security | The MOBOPTS Research Group in the IRTF is chartered to work on | |||
reviews of the drafts developed in the WG. | optimizations related to Mobile IPv6 and IP handoffs among other | |||
things. The MIPSHOP WG will take mature proposals from the MOBOPTS | ||||
group and standardize them in the IETF on a case-by-case basis. One | ||||
such proposal on improving the Mobile IPv6 Return Routability | ||||
procedure by reducing the round trip times required to complete the | ||||
procedure, and increasing the length of time before the procedure | ||||
needs to be run again, has already been taken up the MIPSHOP WG and | ||||
stadardized. | ||||
Scope of MIPSHOP: | Scope of MIPSHOP: | |||
The working group will: | The working group will: | |||
1. Revise the specification of HMIPv6 (RFC 4140) protocol to | 1. Revise the specification of HMIPv6 (RFC 4140) protocol to advance | |||
advance it to Proposed Standard. This implies: | it to Proposed Standard. This implies: | |||
* Work on MN-MAP security | * Define the use of IKEv2 for MN-MAP security | |||
* Streamline and refine the current HMIPv6 specification. | * Streamline and refine the current HMIPv6 specification. | |||
* Document: draft-ietf-mipshop-hmipv6-rev-XX.txt | Document: draft-ietf-mipshop-4140bis | |||
2. Revise the specification of FMIPv6 protocol (RFC 4068) to | 2. Revise the specification of FMIPv6 protocol (RFC 4068) to advance | |||
advance it to Proposed Standard. | it to Proposed Standard. | |||
* Work on MN-AR (access router) security using both the AAA | * Work on mobile node - access router security using both the AAA | |||
infrastructure, and keys derived from SeND | infrastructure, and keys derived from SeND | |||
Documents: draft-ietf-mipshop-handover-keys-aaa, | ||||
o Documents: | draft-ietf-mipshop-handover-key | |||
draft-ietf-mipshop-handover-keys-aaa-XX.txt, | ||||
draft-ietf-mipshop-handover-key-send-XX.txt | ||||
* Streamline and refine the current FMIPv6 specification | * Streamline and refine the current FMIPv6 specification | |||
(draft-ietf-mipshop-fmipv6-rev-XX.txt) | Document: draft-ietf-mipshop-fmipv6-rfc4068bis | |||
3. Work on the application of FMIPv6 on two examples link-layers | 3. Work on the application of FMIPv6 on two examples link-layers for | |||
for advancement as Informational RFCs: | advancement as Informational RFCs: | |||
* IEEE 802.16e (and WiMax), and | * IEEE 802.16e (and WiMax) | |||
* 3G CDMA 2K networks | * 3G CDMA 2K networks | |||
Documents: draft-ietf-mipshop-fh80216e, draft-ietf-mipshop-3gfh | ||||
* Documents: draft-ietf-mipshop-fh80216e-XX.txt, | 4. Work on areas of mutual interest to IEEE 802.21 and MIPSHOP: | |||
draft-ietf-mipshop-3gfh-XX.txt | ||||
4. Produce a document on improving MIPv6 Return Routability via | ||||
both Cryptographically Generated Addresses and Credit-based | ||||
Authorization for advancement as Proposed Standard | ||||
* Documents: draft-ietf-mipshop-cga-cba-XX.txt | ||||
5. Work on areas of mutual interest to IEEE 802.21 and MIPSHOP: | ||||
* Produce the required protocol enhancements or | ||||
specifications for IP-based support of Media-Independent | ||||
Information, Command and Event Services. | ||||
* Documents: draft-ietf-mipshop-mih-info-elements-XX.txt | * Complete the problem statement, and a specification on transport | |||
(information elements), | of IEEE 802.21 services over IP. | |||
draft-ietf-mipshop-mih-support-XX.txt (transport of 802.21 | Documents: draft-ietf-mipshop-mis-ps (Problem Satement), | |||
draft-ietf-mipshop-mih-support (transport of 802.21 | ||||
services over IP, including security aspects) | services over IP, including security aspects) | |||
Tackling further work, although possible, requires re-chartering. | 5. Standardize mature proposals from MOBOPTS Research Group. | |||
Adoption of specific proposals requires rechartering. | ||||
Goals and Milestones: | Goals and Milestones: | |||
Done Working Group Last Call on draft-ietf-mipshop-hmip-xx.txt | ||||
Done Working Group Last Call on draft-ietf-mipshop-lmm-requirements-XX.txt | Done Working Group Last Call on draft-ietf-mipshop-hmip | |||
Done Working Group Last Call on draft-ietf-mipshop-fmipv6-xx.txt | Done Working Group Last Call on draft-ietf-mipshop-lmm-requirements | |||
Done Discuss Last Call comments and security analyses at IETF 58 | Done Working Group Last Call on draft-ietf-mipshop-fmipv6 | |||
Done Submit draft draft-ietf-mipshop-lmm-requirements-XX.txt to IESG for consideration of publication as Informational | Done Submit draft-ietf-mipshop-lmm-requirements to IESG for publication as Informational | |||
Done Submit draft-ietf-mipshop-fmipv6-xx.txt to IESG for consideration of publication as Experimental | Done Submit draft-ietf-mipshop-fmipv6 to IESG for consideration of publication as Experimental | |||
Done Submit draft-ietf-mipshop-hmip-xx.txt to IESG for consideration of publication as Experimental | Done Submit draft-ietf-mipshop-hmip to IESG for consideration of publication as Experimental | |||
Done Working Group Last Call on draft-ietf-mipshop-80211fh-xx.txt for Informational | Done Working Group Last Call on draft-ietf-mipshop-80211fh for Informational | |||
Done Submit draft-ietf-mipshop-80211fh-xx.txt to IESG for consideration of publication as Informational | Done Submit draft-ietf-mipshop-80211fh to IESG for consideration of publication as Informational | |||
Done Working Group Last Call on draft-ietf-mipshop-cga-cba-XX.txt | Done Working Group Last Call on draft-ietf-mipshop-cga-cba | |||
Dec 2006 Working Group Last Call on draft-ietf-mipshop-3gfh-XX.txt | Done Submit draft-ietf-mipshop-cga-cba to IESG for publication as Proposed Standard | |||
Dec 2006 Working Group Last Call on draft-ietf-mipshop-handover-key-send-XX.txt | Done Working Group Last Call on draft-ietf-mipshop-mis-ps | |||
Jan 2007 Submit draft-ietf-mipshop-fmipv6-rfc4068bis-XX.txt to IESG for publication as Proposed Standard | Jun 2007 Working Group Last Call on draft-ietf-mipshop-fmipv6-rfc4068bis | |||
Feb 2007 Working Group Last Call on draft-ietf-mipshop-fh80216e-XX.txt | Jun 2007 Working Group Last Call on draft-ietf-mipshop-handover-key-send | |||
Feb 2007 Working Group Last Call on draft-ietf-mipshop-rfc4041bis-XX.txt | Jun 2007 Submit draft-ietf-mipshop-mis-ps to IESG for publication as Informational RFC | |||
Feb 2007 Working Group Last Call on draft-ietf-mipshop-mih-info-elements-XX.txt | Jul 2007 Working Group Last Call on draft-ietf-mipshop-rfc4041bis | |||
Feb 2007 Working Group Last Call on draft-ietf-mipshop-fmipv6-rfc4068bis-XX.txt | Aug 2007 Working Group Last Call on draft-ietf-mipshop-3gfh | |||
Mar 2007 Working Group Last Call on HMIPv6 Security draft | Aug 2007 Working Group Last Call on draft-ietf-mipshop-fh80216e | |||
Mar 2007 Working Group Last Call on draft-ietf-mipshop-handover-keys-aaa-XX.txt | Aug 2007 Submit draft-ietf-mipshop-fmipv6-rfc4068bis to IESG for publication as Proposed Standard | |||
Mar 2007 Submit draft-ietf-mipshop-cga-cba-XX.txt to IESG for publication as Proposed Standard | Aug 2007 Submit draft-ietf-mipshop-handover-key-send to IESG for publication as Proposed Standard | |||
Mar 2007 Submit draft-ietf-mipshop-3gfh-XX.txt to IESG for publication as Informational RFC | Sep 2007 Submit draft-ietf-mipshop-3gfh to IESG for publication as Informational RFC | |||
Apr 2007 Submit draft-ietf-mipshop-handover-key-send-XX.txt to IESG for publication as Proposed Standard | Oct 2007 Submit draft-ietf-mipshop-4140bis to IESG for publication as Proposed Standard | |||
Jun 2007 Submit draft-ietf-mipshop-fh80216e-XX.txt to IESG for publication as Informational RFC | Oct 2007 Submit draft-ietf-mipshop-fh80216e to IESG for publication as Informational RFC | |||
Jul 2007 Submit draft-ietf-mipshop-mih-info-elements-XX.txt to IESG for publication as Proposed Standard | Nov 2007 Working Group Last Call on draft-ietf-mipshop-mih-support | |||
Jul 2007 Submit draft-ietf-mipshop-hmipv6-rev-XX.txt to IESG for publication as Proposed Standard | Jan 2008 Submit draft-ietf-mipshop-mih-support to IESG for publication as Proposed Standard | |||
Aug 2007 Begin security review of draft-ietf-mipshop-mih-support-XX.txt | ||||
Sep 2007 Working Group Last Call on draft-ietf-mipshop-mih-support-XX.txt | ||||
Nov 2007 Submit draft on HMIPv6 security to IESG for publication as Proposed Standard | ||||
Nov 2007 Submit draft-ietf-mipshop-handover-key-aaa-XX.txt to IESG for publication as Proposed Standard | ||||
Jan 2008 Submit draft-ietf-mipshop-mih-support-XX.txt to IESG for publication as Proposed Standard | ||||
End of changes. 19 change blocks. | ||||
72 lines changed or deleted | 53 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/ |