draft-ietf-netlmm-pmipv6-heartbeat-00.txt   draft-ietf-netlmm-pmipv6-heartbeat-01.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: March 18, 2009 Starent Networks Expires: April 3, 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
September 14, 2008 September 30, 2008
Heartbeat Mechanism for Proxy Mobile IPv6 Heartbeat Mechanism for Proxy Mobile IPv6
draft-ietf-netlmm-pmipv6-heartbeat-00.txt draft-ietf-netlmm-pmipv6-heartbeat-01.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 1, line 42 skipping to change at page 1, line 42
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 March 18, 2009. This Internet-Draft will expire on April 3, 2009.
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 and
take appropriate action. take appropriate action.
skipping to change at page 2, line 19 skipping to change at page 2, line 19
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Heartbeat Mechanism . . . . . . . . . . . . . . . . . . . . . 3 3. Heartbeat Mechanism . . . . . . . . . . . . . . . . . . . . . 3
3.1. Failure Detection . . . . . . . . . . . . . . . . . . . . 4 3.1. Failure Detection . . . . . . . . . . . . . . . . . . . . 4
3.2. Restart Detection . . . . . . . . . . . . . . . . . . . . 4 3.2. Restart Detection . . . . . . . . . . . . . . . . . . . . 4
3.3. Heartbeat Message . . . . . . . . . . . . . . . . . . . . 5 3.3. Heartbeat Message . . . . . . . . . . . . . . . . . . . . 5
3.4. Restart Counter Mobility Option . . . . . . . . . . . . . 6 3.4. Restart Counter Mobility Option . . . . . . . . . . . . . 6
4. Exchanging Heartbeat Messages over an IPv4 Transport 4. Exchanging Heartbeat Messages over an IPv4 Transport
Network . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Network . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
5. Security Considerations . . . . . . . . . . . . . . . . . . . 7 5. Configuration Variables . . . . . . . . . . . . . . . . . . . 7
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7 6. Security Considerations . . . . . . . . . . . . . . . . . . . 7
7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 7 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8
8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 8 8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 8
8.1. Normative References . . . . . . . . . . . . . . . . . . . 8 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 8
8.2. Informative References . . . . . . . . . . . . . . . . . . 8 9.1. Normative References . . . . . . . . . . . . . . . . . . . 8
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 8 9.2. Informative References . . . . . . . . . . . . . . . . . . 8
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 9
Intellectual Property and Copyright Statements . . . . . . . . . . 11 Intellectual Property and Copyright Statements . . . . . . . . . . 11
1. Introduction 1. Introduction
Proxy Mobile IPv6 [2] enables network-based mobility for IPv6 hosts Proxy Mobile IPv6 [2] enables network-based mobility for IPv6 hosts
that do not implement any mobility protocols. The protocol is that do not implement any mobility protocols. The protocol is
described in detail in [2]. In order to facilitate the network-based described in detail in [2]. In order to facilitate the network-based
mobility, the PMIPv6 protocol defines a Mobility Anchor Gateway mobility, the PMIPv6 protocol defines a Mobile Access Gateway (MAG),
(MAG), which acts as a proxy for the Mobile IPv6 [6] signaling, and which acts as a proxy for the Mobile IPv6 [6] signaling, and the
the Local Mobility Anchor (LMA) which acts similar to a Home Agent, Local Mobility Anchor (LMA) which acts similar to a Home Agent,
anchoring a Mobile Node's sessions within a Proxy Mobile IPv6 anchoring a Mobile Node's sessions within a Proxy Mobile IPv6
(PMIPv6) domain. The LMA and the MAG establish a bidirectional (PMIPv6) domain. The LMA and the MAG establish a bidirectional
tunnel for forwarding all data traffic belonging to the Mobile Nodes. tunnel for forwarding all data traffic belonging to the Mobile Nodes.
In a distributed environment such as a PMIPv6 domain consisting of In a distributed environment such as a PMIPv6 domain consisting of
LMA and MAGs, it is necessary for the nodes to 1) have a consistent LMA and MAGs, it is necessary for the nodes to 1) have a consistent
state about each others reachability, and 2) quickly inform peers in state about each others reachability, and 2) quickly inform peers in
the event of recovery from node failures. So, when the LMA restarts the event of recovery from node failures. So, when the LMA restarts
after a failure, the MAG should (quickly) learn about the restart so after a failure, the MAG should (quickly) learn about the restart so
that it could take appropriate actions (such as releasing any that it could take appropriate actions (such as releasing any
skipping to change at page 4, line 37 skipping to change at page 4, line 37
should respond with an ICMP Parameter Problem, Code 0, message to the should respond with an ICMP Parameter Problem, Code 0, message to the
initiator. The 'Pointer' field in the ICMP Parameter Problem message initiator. The 'Pointer' field in the ICMP Parameter Problem message
SHOULD point to the 'MH Type' field, indicating that the particular SHOULD point to the 'MH Type' field, indicating that the particular
Mobility Header message is not supported. When the ICMP Parameter Mobility Header message is not supported. When the ICMP Parameter
Problem message is received in response to Heartbeat Request message, Problem message is received in response to Heartbeat Request message,
the initiating MAG or the LMA MUST NOT use heartbeat messages with the initiating MAG or the LMA MUST NOT use heartbeat messages with
the other end again. the other end again.
3.1. Failure Detection 3.1. Failure Detection
A PMIPv6 node, (MAR or LMA) matches every received Heartbeat Response A PMIPv6 node, (MAG or LMA) matches every received Heartbeat Response
to the Heartbeat Request sent using the sequence number. Before to the Heartbeat Request sent using the sequence number. Before
sending the next Heartbeat Request, it increments a local variable sending the next Heartbeat Request, it increments a local variable
MISSING_HEARTBEAT if it has not received a Heartbeat Response for the MISSING_HEARTBEAT if it has not received a Heartbeat Response for the
previous request. When this local variable MISSING_HEARTBEAT exceeds previous request. When this local variable MISSING_HEARTBEAT exceeds
a configurable parameter MISSING_HEARTBEATS_ALLOWED, the PMIPv6 node a configurable parameter MISSING_HEARTBEATS_ALLOWED, the PMIPv6 node
concludes that the peer PMIPv6 node is not reachable. The PMIPv6 concludes that the peer PMIPv6 node is not reachable. The PMIPv6
node may then take appropriate actions which are outside the scope of node may then take appropriate actions which are outside the scope of
this document. If a Heartbeat Response message is received, the this document. If a Heartbeat Response message is received, the
MISSING_HEARTBEATS_ALLOWED counter is reset. MISSING_HEARTBEATS counter is reset.
3.2. Restart Detection 3.2. Restart Detection
The section describes a mechanism for detecting failure recovery The section describes a mechanism for detecting failure recovery
without session persistence. In case the LMA or the MAG crashes and without session persistence. In case the LMA or the MAG crashes and
re-boots and loses all state with respect to the PMIPv6 sessions, it re-boots and loses all state with respect to the PMIPv6 sessions, it
would be beneficial for the peer PMIPv6 node to discover the failure would be beneficial for the peer PMIPv6 node to discover the failure
and the loss of session state and establish the sessions again. and the loss of session state and establish the sessions again.
Each PMIPv6 node (both the MAG and LMA) MUST maintain a monotonically Each PMIPv6 node (both the MAG and LMA) MUST maintain a monotonically
skipping to change at page 7, line 21 skipping to change at page 7, line 21
In some deployments, the network between the MAG and the LMA may not In some deployments, the network between the MAG and the LMA may not
be capable of transporting IPv6 packets. In this case, the Heartbeat be capable of transporting IPv6 packets. In this case, the Heartbeat
messages are tunneled over IPv4. If the Proxy Binding Update and messages are tunneled over IPv4. If the Proxy Binding Update and
Proxy Binding Acknowledgment messages are sent using UDP Proxy Binding Acknowledgment messages are sent using UDP
encapsulation to traverse NATs, then the Heartbeat messages are also encapsulation to traverse NATs, then the Heartbeat messages are also
sent with UDP encapsulation. The UDP port used would be the same as sent with UDP encapsulation. The UDP port used would be the same as
the port used for the Proxy Binding Update and Proxy Binding the port used for the Proxy Binding Update and Proxy Binding
Acknowledgement messages. For more details on tunneling Proxy Mobile Acknowledgement messages. For more details on tunneling Proxy Mobile
IPv6 signaling messages over IPv4, see [3]. IPv6 signaling messages over IPv4, see [3].
5. Security Considerations 5. Configuration Variables
The LMA and the MAG must allow the following variables to be
configurable.
HEARTBEAT_INTERVAL
This variable is used to set the time interval in seconds between
two consecutive Heartbeat Request messages. The default value is
60 seconds. It SHOULD not be set to less than 30 seconds.
MISSING_HEARTBEATS_ALLOWED
This variable indicates the maximum number of consecutive
Heartbeat Request messages that a PMIPv6 node can miss before
concluding that the peer PMIPv6 node is not reachable. The
default value for this variable is 3.
6. Security Considerations
The heartbeat messages are just used for checking reachability The heartbeat messages are just used for checking reachability
between the MAG and the LMA. They do not carry information that is between the MAG and the LMA. They do not carry information that is
useful for eavesdroppers on the path. Therefore, confidentiality useful for eavesdroppers on the path. Therefore, confidentiality
protection is not required. Integrity protection using IPsec [4] for protection is not required. Integrity protection using IPsec [4] for
the heartbeat messages MUST be supported on the MAG and the LMA. the heartbeat messages MUST be supported on the MAG and the LMA.
If dynamic key negotiation between the MAG and the LMA is required, If dynamic key negotiation between the MAG and the LMA is required,
IKEv2 [5] should be used. IKEv2 [5] should be used.
6. IANA Considerations 7. IANA Considerations
The Heartbeat message defined in Section 3.3 must have the type value The Heartbeat message defined in Section 3.3 must have the type value
allocated from the same space as the 'MH Type' field in the Mobility allocated from the same space as the 'MH Type' field in the Mobility
Header defined in RFC 3775 [6]. Header defined in RFC 3775 [6].
The Restart Counter mobility option defined in Section 3.4 must have The Restart Counter mobility option defined in Section 3.4 must have
the type value allocated from the same space as the Mobility Options the type value allocated from the same space as the Mobility Options
defined in RFC 3775 [6]. defined in RFC 3775 [6].
7. Acknowledgments 8. Acknowledgments
A heartbeat mechanism for a network-based mobility management A heartbeat mechanism for a network-based mobility management
protocol was first described in [7]. The authors would like to thank protocol was first described in [7]. The authors would like to thank
the members of a NETLMM design team that produced that document. The the members of a NETLMM design team that produced that document. The
mechanism described in this document also derives from the path mechanism described in this document also derives from the path
management mechanism described in [8]. management mechanism described in [8].
We would like to thank Alessio Casati for first suggesting a fault We would like to thank Alessio Casati for first suggesting a fault
handling mechanism for Proxy Mobile IPv6. handling mechanism for Proxy Mobile IPv6.
8. References 9. References
8.1. Normative References 9.1. Normative References
[1] Bradner, S., "Key words for use in RFCs to Indicate Requirement [1] Bradner, S., "Key words for use in RFCs to Indicate Requirement
Levels", BCP 14, RFC 2119, March 1997. Levels", BCP 14, RFC 2119, March 1997.
[2] Gundavelli, S., Leung, K., Devarapalli, V., Chowdhury, K., and [2] Gundavelli, S., Leung, K., Devarapalli, V., Chowdhury, K., and
B. Patil, "Proxy Mobile IPv6", RFC 5213, August 2008. B. Patil, "Proxy Mobile IPv6", RFC 5213, August 2008.
[3] Wakikawa, R. and S. Gundavelli, "IPv4 Support for Proxy Mobile [3] Wakikawa, R. and S. Gundavelli, "IPv4 Support for Proxy Mobile
IPv6", draft-ietf-netlmm-pmip6-ipv4-support-04 (work in IPv6", draft-ietf-netlmm-pmip6-ipv4-support-04 (work in
progress), July 2008. progress), July 2008.
[4] Kent, S. and K. Seo, "Security Architecture for the Internet [4] Kent, S. and K. Seo, "Security Architecture for the Internet
Protocol", RFC 4301, December 2005. Protocol", RFC 4301, December 2005.
[5] Kaufman, C., "Internet Key Exchange (IKEv2) Protocol", RFC 4306, [5] Kaufman, C., "Internet Key Exchange (IKEv2) Protocol", RFC 4306,
December 2005. December 2005.
8.2. Informative References 9.2. Informative References
[6] Johnson, D., Perkins, C., and J. Arkko, "Mobility Support in [6] Johnson, D., Perkins, C., and J. Arkko, "Mobility Support in
IPv6", RFC 3775, June 2004. IPv6", RFC 3775, June 2004.
[7] Giaretta, G., "The NetLMM Protocol", [7] Giaretta, G., "The NetLMM Protocol",
draft-giaretta-netlmm-dt-protocol-02 (work in progress), draft-giaretta-netlmm-dt-protocol-02 (work in progress),
October 2006. October 2006.
[8] 3rd Generation Partnership Project, "3GPP Technical [8] 3rd Generation Partnership Project, "3GPP Technical
Specification 29.060 V7.6.0: "Technical Specification Group Core Specification 29.060 V7.6.0: "Technical Specification Group Core
 End of changes. 14 change blocks. 
22 lines changed or deleted 41 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/