Mobile IPv4 Traversal across IPsec-Based VPN Gateways
RFC 5265

Approval announcement
Draft of message to be sent after approval:

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: Internet Architecture Board <iab@iab.org>,
    RFC Editor <rfc-editor@rfc-editor.org>, 
    mip4 mailing list <mip4@ietf.org>, 
    mip4 chair <mip4-chairs@tools.ietf.org>
Subject: Protocol Action: 'Mobile IPv4 Traversal across 
         IPsec-Based VPN Gateways' to Proposed Standard 

The IESG has approved the following document:

- 'Mobile IPv4 Traversal across IPsec-Based VPN Gateways '
   <draft-ietf-mip4-vpn-problem-solution-06.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-06.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.