Protocol Action: 'IPv4 Support for Proxy Mobile IPv6' to Proposed Standard

The IESG <> Mon, 15 March 2010 16:38 UTC

Return-Path: <>
Received: by (Postfix, from userid 30) id A719D3A6AE0; Mon, 15 Mar 2010 09:38:55 -0700 (PDT)
X-idtracker: yes
From: The IESG <>
To: IETF-Announce <>
Subject: Protocol Action: 'IPv4 Support for Proxy Mobile IPv6' to Proposed Standard
Message-Id: <>
Date: Mon, 15 Mar 2010 09:38:55 -0700 (PDT)
Cc: Internet Architecture Board <>, netlmm mailing list <>, netlmm chair <>, RFC Editor <>
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IETF announcement list. No discussions." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 15 Mar 2010 16:38:55 -0000

The IESG has approved the following document:

- 'IPv4 Support for Proxy Mobile IPv6 '
   <draft-ietf-netlmm-pmip6-ipv4-support-18.txt> as a Proposed Standard

This document is the product of the Network-based Localized Mobility Management Working Group. 

The IESG contact persons are Jari Arkko and Ralph Droms.

A URL of this Internet-Draft is:

Technical Summary

   The Proxy Mobile IPv6 specification in RFC 5213 describes network 
   based mobility management for IPv6 hosts across IPv6 network
   domains. This document describes the necessary extensions to
   RFC 5213 to support IPv4-only and dual stacked hosts. It also
   supports IPv4 network traversal between the Mobile Access Gateway
   (MAG) in the access network and the Local Mobility Anchor (LMA).

Working Group Summary

   There is a consensus in the NETLMM WG for publication as a
   proposed standard.

Document Quality

  The document has gone through various reviews and a successful WGLC. 
  Significant discussions occurred due to AD review comments, and later,
  due to additional issues raised on DHCP usage. These were resolved
  and the draft can now go forward.


   Responsible AD is Jari Arkko and the document shepherd is
   Vidya Narayanan.

RFC Editor Note

   Please change in Section 4.2.2:

   o The Proxy Binding Update message MUST be sent over IPv4 as  
desribed in Section