draft-ietf-netlmm-pmipv6-heartbeat-06.txt   draft-ietf-netlmm-pmipv6-heartbeat-07.txt 
NETLMM Working Group V. Devarapalli (ed.) NETLMM Working Group V. Devarapalli (ed.)
Internet-Draft WiChorus Internet-Draft WiChorus
Intended status: Standards Track R. Koodli (ed.) Intended status: Standards Track R. Koodli (ed.)
Expires: September 24, 2009 Starent Networks Expires: October 11, 2009 Starent Networks
H. Lim H. Lim
N. Kant N. Kant
Stoke Stoke
S. Krishnan S. Krishnan
Ericsson Ericsson
J. Laganier J. Laganier
DOCOMO Euro-Labs DOCOMO Euro-Labs
March 23, 2009 April 9, 2009
Heartbeat Mechanism for Proxy Mobile IPv6 Heartbeat Mechanism for Proxy Mobile IPv6
draft-ietf-netlmm-pmipv6-heartbeat-06.txt draft-ietf-netlmm-pmipv6-heartbeat-07.txt
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79. This document may not be modified, provisions of BCP 78 and BCP 79. This document may not be modified,
and derivative works of it may not be created, except to format it and derivative works of it may not be created, except to format it
for publication as an RFC or to translate it into languages other for publication as an RFC or to translate it into languages other
than English. than English.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
skipping to change at page 1, line 43 skipping to change at page 1, line 43
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."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on September 24, 2009. This Internet-Draft will expire on October 11, 2009.
Copyright Notice Copyright Notice
Copyright (c) 2009 IETF Trust and the persons identified as the Copyright (c) 2009 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 in effect on the date of Provisions Relating to IETF Documents in effect on the date of
publication of this document (http://trustee.ietf.org/license-info). publication of this document (http://trustee.ietf.org/license-info).
Please review these documents carefully, as they describe your rights Please review these documents carefully, as they describe your rights
and restrictions with respect to this document. and restrictions with respect to this document.
Abstract Abstract
Proxy Mobile IPv6 is a network-based mobility management protocol. Proxy Mobile IPv6 is a network-based mobility management protocol.
The mobility entities involved in the Proxy Mobile IPv6 protocol, the The mobility entities involved in the Proxy Mobile IPv6 protocol, the
Mobile Access Gateway (MAG) and the Local Mobility Anchor (LMA), Mobile Access Gateway (MAG) and the Local Mobility Anchor (LMA),
setup tunnels dynamically to manage mobility for a mobile node within setup tunnels dynamically to manage mobility for a mobile node within
the Proxy Mobile IPv6 domain. This document describes a heartbeat the Proxy Mobile IPv6 domain. This document describes a heartbeat
mechanism between the MAG and the LMA to detect failures quickly and mechanism between the MAG and the LMA to detect failures, quickly
take appropriate action. inform peers in the event of a recovery from node failures, and allow
a peer to take appropriate action.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4
3. Heartbeat Mechanism . . . . . . . . . . . . . . . . . . . . . 3 3. Heartbeat Mechanism . . . . . . . . . . . . . . . . . . . . . 4
3.1. Failure Detection . . . . . . . . . . . . . . . . . . . . 4 3.1. Failure Detection . . . . . . . . . . . . . . . . . . . . 5
3.2. Restart Detection . . . . . . . . . . . . . . . . . . . . 5 3.2. Restart Detection . . . . . . . . . . . . . . . . . . . . 6
3.3. Heartbeat Message . . . . . . . . . . . . . . . . . . . . 6 3.3. Heartbeat Message . . . . . . . . . . . . . . . . . . . . 7
3.4. Restart Counter Mobility Option . . . . . . . . . . . . . 7 3.4. Restart Counter Mobility Option . . . . . . . . . . . . . 8
4. Exchanging Heartbeat Messages over an IPv4 Transport 4. Exchanging Heartbeat Messages over an IPv4 Transport
Network . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Network . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
5. Configuration Variables . . . . . . . . . . . . . . . . . . . 8 5. Configuration Variables . . . . . . . . . . . . . . . . . . . 9
6. Security Considerations . . . . . . . . . . . . . . . . . . . 9 6. Security Considerations . . . . . . . . . . . . . . . . . . . 10
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10
8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 9 8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 10
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 10 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 11
9.1. Normative References . . . . . . . . . . . . . . . . . . . 10 9.1. Normative References . . . . . . . . . . . . . . . . . . . 11
9.2. Informative References . . . . . . . . . . . . . . . . . . 10 9.2. Informative References . . . . . . . . . . . . . . . . . . 11
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 10 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 11
1. Introduction 1. Introduction
Proxy Mobile IPv6 [RFC5213] enables network-based mobility for IPv6 Proxy Mobile IPv6 [RFC5213] enables network-based mobility for IPv6
hosts that do not implement any mobility protocols. The protocol is hosts that do not implement any mobility protocols. The protocol is
described in detail in [RFC5213]. In order to facilitate the described in detail in [RFC5213]. In order to facilitate the
network-based mobility, the PMIPv6 protocol defines a Mobile Access network-based mobility, the PMIPv6 protocol defines a Mobile Access
Gateway (MAG), which acts as a proxy for the Mobile IPv6 [RFC3775] Gateway (MAG), which acts as a proxy for the Mobile IPv6 [RFC3775]
signaling, and the Local Mobility Anchor (LMA) which acts similar to signaling, and the Local Mobility Anchor (LMA) which acts similar to
a Home Agent, anchoring a Mobile Node's sessions within a Proxy a Home Agent, anchoring a Mobile Node's sessions within a Proxy
skipping to change at page 4, line 22 skipping to change at page 5, line 22
one proxy binding cache entry at the LMA for a mobile node attached one proxy binding cache entry at the LMA for a mobile node attached
to the MAG. If there are no proxy binding cache entries at the LMA to the MAG. If there are no proxy binding cache entries at the LMA
for any of the mobile nodes attached to the MAG, then the heartbeat for any of the mobile nodes attached to the MAG, then the heartbeat
message SHOULD NOT be sent. Similarly, the LMA SHOULD NOT send a message SHOULD NOT be sent. Similarly, the LMA SHOULD NOT send a
Heartbeat Request message to a MAG if there is no active binding Heartbeat Request message to a MAG if there is no active binding
cache entry created by the MAG. A PMIPv6 node MUST respond to a cache entry created by the MAG. A PMIPv6 node MUST respond to a
Heartbeat Request message with a Heartbeat Response message, Heartbeat Request message with a Heartbeat Response message,
irrespective of whether there is an active binding cache entry. irrespective of whether there is an active binding cache entry.
The HEARTBEAT_INTERVAL SHOULD NOT be configured to a value less than The HEARTBEAT_INTERVAL SHOULD NOT be configured to a value less than
30 seconds. Sending heartbeat messages too often may become an 30 seconds. Deployments should be careful in setting the value for
overhead on the path between the MAG and the LMA. The the HEARTBEAT_INTERNVAL. Sending heartbeat messages too often may
HEARTBEAT_INTERVAL can be set to a much larger value on the MAG and become an overhead on the path between the MAG and the LMA. It could
the LMA, if required, to reduce the burden of sending periodic also create congestion in the network and negatively affect network
heartbeat messages. performance. The HEARTBEAT_INTERVAL can be set to a much larger
value on the MAG and the LMA, if required, to reduce the burden of
sending periodic heartbeat messages.
If the LMA or the MAG do not support the heartbeat messages, they If the LMA or the MAG do not support the heartbeat messages, they
respond with a Binding Error message with status set to '2' respond with a Binding Error message with status set to '2'
(unrecognized MH type value) as described in [RFC3775]. When the (unrecognized MH type value) as described in [RFC3775]. When the
Binding Error message with status set to '2' is received in response Binding Error message with status set to '2' is received in response
to Heartbeat Request message, the initiating MAG or the LMA MUST NOT to Heartbeat Request message, the initiating MAG or the LMA MUST NOT
use heartbeat messages with the other end again. use heartbeat messages with the other end again.
If a PMIPv6 node has detected that a peer PMIPv6 node has failed or If a PMIPv6 node has detected that a peer PMIPv6 node has failed or
restarted without retaining the PMIPv6 session state, it should mark restarted without retaining the PMIPv6 session state, it should mark
skipping to change at page 10, line 15 skipping to change at page 11, line 15
9.1. Normative References 9.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC5213] Gundavelli, S., Leung, K., Devarapalli, V., Chowdhury, K., [RFC5213] Gundavelli, S., Leung, K., Devarapalli, V., Chowdhury, K.,
and B. Patil, "Proxy Mobile IPv6", RFC 5213, August 2008. and B. Patil, "Proxy Mobile IPv6", RFC 5213, August 2008.
[I-D.ietf-netlmm-pmip6-ipv4-support] [I-D.ietf-netlmm-pmip6-ipv4-support]
Wakikawa, R. and S. Gundavelli, "IPv4 Support for Proxy Wakikawa, R. and S. Gundavelli, "IPv4 Support for Proxy
Mobile IPv6", draft-ietf-netlmm-pmip6-ipv4-support-08 Mobile IPv6", draft-ietf-netlmm-pmip6-ipv4-support-10
(work in progress), January 2009. (work in progress), March 2009.
[RFC4301] Kent, S. and K. Seo, "Security Architecture for the [RFC4301] Kent, S. and K. Seo, "Security Architecture for the
Internet Protocol", RFC 4301, December 2005. Internet Protocol", RFC 4301, December 2005.
[RFC4306] Kaufman, C., "Internet Key Exchange (IKEv2) Protocol", [RFC4306] Kaufman, C., "Internet Key Exchange (IKEv2) Protocol",
RFC 4306, December 2005. RFC 4306, December 2005.
[RFC3775] Johnson, D., Perkins, C., and J. Arkko, "Mobility Support [RFC3775] Johnson, D., Perkins, C., and J. Arkko, "Mobility Support
in IPv6", RFC 3775, June 2004. in IPv6", RFC 3775, June 2004.
 End of changes. 9 change blocks. 
29 lines changed or deleted 32 lines changed or added

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