[Mip4] WG Action: RECHARTER: Mobility for IPv4 (mip4)
The IESG <iesg-secretary@ietf.org> Wed, 08 October 2003 16:06 UTC
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA25120 for <mip4-archive@odin.ietf.org>; Wed, 8 Oct 2003 12:06:27 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A7GpB-00073A-5p for mip4-archive@odin.ietf.org; Wed, 08 Oct 2003 12:06:06 -0400
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h98G65Wd027100 for mip4-archive@odin.ietf.org; Wed, 8 Oct 2003 12:06:05 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A7GpB-000731-1t for mip4-web-archive@optimus.ietf.org; Wed, 08 Oct 2003 12:06:05 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA25100 for <mip4-web-archive@ietf.org>; Wed, 8 Oct 2003 12:05:55 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A7Gp9-0000KU-00 for mip4-web-archive@ietf.org; Wed, 08 Oct 2003 12:06:03 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1A7Gp9-0000KR-00 for mip4-web-archive@ietf.org; Wed, 08 Oct 2003 12:06:03 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A7Gp7-00072E-WD; Wed, 08 Oct 2003 12:06:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A7GTE-0005GK-4T for mip4@optimus.ietf.org; Wed, 08 Oct 2003 11:43:24 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA23584; Wed, 8 Oct 2003 11:42:29 -0400 (EDT)
Message-Id: <200310081542.LAA23584@ietf.org>
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce:;
Cc: Henrik Levkowetz <henrik@levkowetz.com>, Pete McCann <mccap@lucent.com>, mip4@ietf.org
Date: Wed, 08 Oct 2003 11:42:29 -0400
Subject: [Mip4] WG Action: RECHARTER: Mobility for IPv4 (mip4)
Sender: mip4-admin@ietf.org
Errors-To: mip4-admin@ietf.org
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mip4>, <mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mip4>, <mailto:mip4-request@ietf.org?subject=subscribe>
The charter of the Mobility for IPv4 (mip4) 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. Note: the only substantative change to this charter relative to the existing charter is the addition of the following item: > 7. Experimental message types and extensions for Mobile IPv4 in > accordance with draft-narten-iana-experimental-allocations-03.txt > have been proposed in > draft-patel-mobileip-experimental-messages-01.txt. The work group > will take on and complete this specification. Mobility for IPv4 (mip4) ------------------------ Current Status: Active Working Group Chair(s): Henrik Levkowetz <henrik@levkowetz.com> Pete McCann <mccap@lucent.com> Internet Area Director(s): Thomas Narten <narten@us.ibm.com> Margaret Wasserman <margaret.wasserman@nokia.com> Mailing list: mip4@ietf.org To Subscribe: mip4-request@ietf.org In Body or Subject: subscribe Archive: https://www1.ietf.org/mail-archive/working-groups/mip4/current/ DESCRIPTION: IP mobility support for IPv4 nodes (hosts and routers) is specified in RFC3344. RFC 3344 mobility allows a node to continue using its "permanent" home address as it moves around the internet. The Mobile IP protocols support transparency above the IP layer, including maintenance of active TCP connections and UDP port bindings. Besides the basic Mobile IPv4 (MIPv4) protocols, several other drafts deal with concerns such as optimization, security, extensions, AAA support, and deployment issues. Mobile IPv4 is currently being deployed on a wide basis (e.g., in cdma2000 networks). The scope of the deployment is on a fairly large scale and accordingly, the MIP4 WG will focus on deployment issues and on addressing known deficiencies and shortcomings in the protocol that have come up as a result of deployment experience. Specifically, the working group will complete the work items to facilitate interactions with AAA environments, interactions with enterprise environments when Mobile IPv4 is used therein, and updating existing protocol specifications in accordance with deployment needs and advancing those protocols that are on the standards track. Work expected to be done by the MIP4 WG as proposed by this charter is as follows: 1. MIPv4 has been a proposed standard for several years. It has been adopted by other standard development organizations and has been deployed commercially. One of the next steps for the WG is to advance the protocol to draft standard status. As part of advancing base Mobile IP specs to DS, the Mobile IPv4 NAI RFC (2794) will also be progressed towards DS. 2. Key exchange using AAA infrastructures for setting up security associations defined in RFC3344 will be completed. 3. The AAA WG, which is currently dealing with the Diameter Mobile IP application, requires the AAA NAI for Mobile IPv4. This work will be completed by the WG. The MIP4 WG will also work with the AAA WG to ensure that the Diameter Mobile IP application is aligned with WG requirements. 4. Home agent assignment at the time of mobile-ip registration, rather than preconfigured for the mobile node, has been proposed in draft-kulkarni-mobileip-dynamic-assignment-01.txt. The WG will take on the task of completing this. The ability to switch the home agent assigned to a mobile node while registered will also be considered as part of this task. 5. Work items that are pending from the previous Mobile IP WG, which will be completed by the MIP4 WG, are RFC3012bis (Challenge-response mechanism), low-latency handover draft to experimental status and the completion of the MIB for the revised base Mobile IP specification (2006bis). 6. The MIP4 WG will also complete the work on Mobile IPv4 interactions in VPN scenarios. This work will involve identifying the requirements and a solution development for Mobile IPv4 operation in the presence of IPsec VPN's. 7. Experimental message types and extensions for Mobile IPv4 in accordance with draft-narten-iana-experimental-allocations-03.txt has been proposed in draft-patel-mobileip-experimental-messages-01.txt. The work group will take on and complete this specification. Other potential work items may be identified in the future but will require an appropriate recharter. Goals and Milestones: Aug 03 AAA Keys for MIPv4 to IESG Sep 03 MIPv4 VPN interaction problem statement to IESG Sep 03 Low latency handover to experimental Oct 03 Revised MIPv4 Challenge/Response (3012bis) to IESG Oct 03 Advance RFC 2794 (NAI Extension specification) to IESG for Draft Standard Nov 03 Revised MIB for MIPv4 to IESG Dec 03 Revised MIPv4 specification to IESG for Draft Standard Jan 04 Dynamic Home Agent assignment protocol solution to IESG Jan 04 MIPv4 experimental extensions and message draft to IESG Feb 04 MIPv4 VPN Solution to IESG -- Mip4 mailing list Mip4@ietf.org https://www.ietf.org/mailman/listinfo/mip4
- [Mip4] WG Action: RECHARTER: Mobility for IPv4 (m… The IESG
- Status of Regional MIPv4 (Re: [Mip4] WG Action: R… Seok J. Koh
- Re: Status of Regional MIPv4 (Re: [Mip4] WG Actio… Henrik Levkowetz
- [Mip4] WG Action: RECHARTER: Mobility for IPv4 (m… The IESG
- [Mip4] WG Action: RECHARTER: Mobility for IPv4 (m… The IESG
- [Mip4] WG Action: RECHARTER: Mobility for IPv4 (m… IESG Secretary
- Re: [Mip4] WG Action: RECHARTER: Mobility for IPv… Pete McCann
- RE: [Mip4] WG Action: RECHARTER: Mobility for IPv… Kent Leung (kleung)
- RE: [Mip4] WG Action: RECHARTER: Mobility for IPv… Tsirtsis, George
- Re: [Mip4] WG Action: RECHARTER: Mobility for IPv… Pete McCann
- RE: [Mip4] WG Action: RECHARTER: Mobility for IPv… Tsirtsis, George
- Re: [Mip4] WG Action: RECHARTER: Mobility for IPv… Behcet Sarikaya
- Re: [Mip4] WG Action: RECHARTER: Mobility for IPv… Alexandru Petrescu
- Re: [Mip4] WG Action: RECHARTER: Mobility for IPv… Alexandru Petrescu
- Re: comments on draft-tsirtsis-v4v6-mipv4 (was: [… Alexandru Petrescu
- RE: comments on draft-tsirtsis-v4v6-mipv4 (was: [… Tsirtsis, George
- Re: comments on draft-tsirtsis-v4v6-mipv4 (was: [… Alexandru Petrescu
- RE: comments on draft-tsirtsis-v4v6-mipv4 (was: [… Tsirtsis, George
- Re: comments on draft-tsirtsis-v4v6-mipv4 (was: [… Alexandru Petrescu
- [Mip4] WG Action: RECHARTER: Mobility for IPv4 (m… IESG Secretary
- [Mip4] WG Action: RECHARTER: Mobility for IPv4 (m… IESG Secretary
- Re: [Mip4] WG Action: RECHARTER: Mobility for IPv… Sri Gundavelli
- Re: [Mip4] WG Action: RECHARTER: Mobility for IPv… Alexandru Petrescu
- Re: [Mip4] WG Action: RECHARTER: Mobility for IPv… Alexandru Petrescu