[Mip4] Protocol Action: 'Mobile IPv4 Traversal Across IPsec-based VPN Gateways' to Proposed Standard
The IESG <iesg-secretary@ietf.org> Mon, 14 April 2008 20:01 UTC
Return-Path: <mip4-bounces@ietf.org>
X-Original-To: mip4-archive@optimus.ietf.org
Delivered-To: ietfarch-mip4-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 87BA23A6EE4; Mon, 14 Apr 2008 13:01:03 -0700 (PDT)
X-Original-To: mip4@ietf.org
Delivered-To: mip4@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 30) id 4CA063A67E2; Mon, 14 Apr 2008 13:01:01 -0700 (PDT)
X-idtracker: yes
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Message-Id: <20080414200102.4CA063A67E2@core3.amsl.com>
Date: Mon, 14 Apr 2008 13:01:02 -0700
Cc: mip4 chair <mip4-chairs@tools.ietf.org>, Internet Architecture Board <iab@iab.org>, mip4 mailing list <mip4@ietf.org>, RFC Editor <rfc-editor@rfc-editor.org>
Subject: [Mip4] Protocol Action: 'Mobile IPv4 Traversal Across IPsec-based VPN Gateways' to Proposed Standard
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mip4>, <mailto:mip4-request@ietf.org?subject=unsubscribe>
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>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org
The IESG has approved the following document: - 'Mobile IPv4 Traversal Across IPsec-based VPN Gateways ' <draft-ietf-mip4-vpn-problem-solution-05.txt> as a Proposed Standard This document is the product of the Mobility for IPv4 Working Group. The IESG contact persons are Jari Arkko and Mark Townsley. A URL of this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-mip4-vpn-problem-solution-05.txt Technical Summary This document outlines a solution for the Mobile IPv4 and IPsec coexistence problem for enterprise users. The solution consists of an applicability statement for using Mobile IPv4 and IPsec for session mobility in corporate remote access scenarios, and a required mechanism for detecting the trusted internal network securely. The solution requires only changes to the mobile node; changes to Mobile IPv4 or IPsec protocols, the VPN gateway, or the home agent are not required. Working Group Summary This is a product of the MIP4 WG, and has the backing of the WG. It has emerged from the work done by the VPN traversal design team. Protocol Quality This specification has been reviewed by Henrik Levkowetz, Vijay Deverapalli, Jari Arkko, and members of the MIP4 WG. Note to RFC Editor In Section 5.2, change: OLD: The overhead consists of the following: NEW: The maximum overhead of 97 octets in the 'cvc' access mode consists of the following: Also, please change s/abovementioned/above mentioned and s/untypical/atypical throughout the document. Add to the end of the IANA Considerations section: Allocation of new Sub-Type values can be made via Expert Review and Specification Required [I-D.narten-iana- considerations-rfc2434bis]. And add draft-narten as a new normative reference. -- Mip4 mailing list: Mip4@ietf.org Web interface: https://www.ietf.org/mailman/listinfo/mip4 Charter page: http://www.ietf.org/html.charters/mip4-charter.html Supplemental site: http://www.mip4.org/