Skip to main content

Interactions between PMIPv6 and MIPv6: scenarios and related issues

Document Type Replaced Internet-Draft (individual)
Expired & archived
Author Gerardo Giaretta
Last updated 2007-11-16
Replaced by RFC 6612
RFC stream (None)
Intended RFC status (None)
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-netlmm-mip-interactions
Telechat date (None)
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:


The scenarios where Proxy Mobile IPv6 (PMIPv6) and Mobile IPv6 (MIPv6) protocols interact with each other need special considerations. An analysis of all the scenarios that involve this interaction is necessary in order to provide guidelines to PMIPv6 protocol design and applicability. This document describes all identified possible scenarios, which require an interaction between PMIPv6 and MIPv6 and discusses all issues related to these scenarios. Solutions to enable these scenarios are also described.Requirements Language The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [RFC2119].


Gerardo Giaretta

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)