draft-ietf-netlmm-mip-interactions-05.txt   draft-ietf-netlmm-mip-interactions-06.txt 
NETLMM Working Group G. Giaretta, Ed. NETLMM Working Group G. Giaretta, Ed.
Internet-Draft Qualcomm Internet-Draft Qualcomm
Intended status: Informational April 30, 2010 Intended status: Informational May 03, 2010
Expires: November 1, 2010 Expires: November 4, 2010
Interactions between PMIPv6 and MIPv6: scenarios and related issues Interactions between PMIPv6 and MIPv6: scenarios and related issues
draft-ietf-netlmm-mip-interactions-05 draft-ietf-netlmm-mip-interactions-06
Abstract Abstract
The use of Proxy Mobile IPv6 (PMIPv6) and Mobile IPv6 (MIPv6) in the The use of Proxy Mobile IPv6 (PMIPv6) and Mobile IPv6 (MIPv6) in the
same network requires some care. This document discusses scenarios same network requires some care. This document discusses scenarios
where such mixed usage is appropriate and points out the need for where such mixed usage is appropriate and points out the need for
interaction between the two mechanisms. Solutions and interaction between the two mechanisms. Solutions and
recommendations to enable these scenarios are also described. recommendations to enable these scenarios are also described.
Requirements Language Requirements Language
skipping to change at page 1, line 40 skipping to change at page 1, line 40
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on November 1, 2010. This Internet-Draft will expire on November 4, 2010.
Copyright Notice Copyright Notice
Copyright (c) 2010 IETF Trust and the persons identified as the Copyright (c) 2010 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 17, line 10 skipping to change at page 17, line 10
flag R in the last BU) is still forwarded to the CoA present in the flag R in the last BU) is still forwarded to the CoA present in the
MIPv6 BCE. When the mobile node wants to use the HoA directly from MIPv6 BCE. When the mobile node wants to use the HoA directly from
the home link, it sends a de-registration message and at that point the home link, it sends a de-registration message and at that point
only the PMIPv6 binding cache entry is present. only the PMIPv6 binding cache entry is present.
4.3. Solutions related to scenario B 4.3. Solutions related to scenario B
The solution for this scenario depends on the access network being The solution for this scenario depends on the access network being
able to determine that a particular mobile node wants to use Mobile able to determine that a particular mobile node wants to use Mobile
IPv6. This requires a solution at the system level for the access IPv6. This requires a solution at the system level for the access
network and is out of scope of this document. network and may require knowledge of the detailed configuration and
software capabilities of every mobile node in the system. These
issues are out of scope of this document
5. Security Considerations 5. Security Considerations
Scenarios A.1 and B described in Section 3 do not introduce any Scenarios A.1 and B described in Section 3 do not introduce any
security considerations in addition to those described in [pmipv6- security considerations in addition to those described in [pmipv6-
draft] or [RFC3775]. draft] or [RFC3775].
This document requires that the a home agent that also implements the This document requires that the a home agent that also implements the
PMIPv6 LMA functionality should allow both the mobile node and the PMIPv6 LMA functionality should allow both the mobile node and the
authorized MAGs to modify the binding cache entries for the mobile authorized MAGs to modify the binding cache entries for the mobile
 End of changes. 4 change blocks. 
5 lines changed or deleted 7 lines changed or added

This html diff was produced by rfcdiff 1.38. The latest version is available from http://tools.ietf.org/tools/rfcdiff/