draft-ietf-netlmm-pmipv6-heartbeat-03.txt   draft-ietf-netlmm-pmipv6-heartbeat-04.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: July 24, 2009 Starent Networks Expires: August 20, 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
January 20, 2009 February 16, 2009
Heartbeat Mechanism for Proxy Mobile IPv6 Heartbeat Mechanism for Proxy Mobile IPv6
draft-ietf-netlmm-pmipv6-heartbeat-03.txt draft-ietf-netlmm-pmipv6-heartbeat-04.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. provisions of BCP 78 and 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
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
skipping to change at page 1, line 40 skipping to change at page 1, line 40
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 July 24, 2009. This Internet-Draft will expire on August 20, 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 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 2, line 21 skipping to change at page 2, line 21
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.
Table of Contents Table of Contents
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 . . . . . . . . . . . . . . . . . . . . . 5 3.2. Restart Detection . . . . . . . . . . . . . . . . . . . . 5
3.3. Heartbeat Message . . . . . . . . . . . . . . . . . . . . . 5 3.3. Heartbeat Message . . . . . . . . . . . . . . . . . . . . 5
3.4. Restart Counter Mobility Option . . . . . . . . . . . . . . 6 3.4. Restart Counter Mobility Option . . . . . . . . . . . . . 7
4. Exchanging Heartbeat Messages over an IPv4 Transport 4. Exchanging Heartbeat Messages over an IPv4 Transport
Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Network . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
5. Configuration Variables . . . . . . . . . . . . . . . . . . . . 7 5. Configuration Variables . . . . . . . . . . . . . . . . . . . 8
6. Security Considerations . . . . . . . . . . . . . . . . . . . . 8 6. Security Considerations . . . . . . . . . . . . . . . . . . . 8
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 8 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9
8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 8 8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 9
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 8 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 9
9.1. Normative References . . . . . . . . . . . . . . . . . . . 8 9.1. Normative References . . . . . . . . . . . . . . . . . . . 9
9.2. Informative References . . . . . . . . . . . . . . . . . . 9 9.2. Informative References . . . . . . . . . . . . . . . . . . 10
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 9 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 10
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 5, line 41 skipping to change at page 5, line 41
by the receiving PMIPv6 node. by the receiving PMIPv6 node.
If a PMIPv6 node restarts and looses PMIPv6 session state, it SHOULD If a PMIPv6 node restarts and looses PMIPv6 session state, it SHOULD
send an unsolicited Heartbeat Response message with an incremented send an unsolicited Heartbeat Response message with an incremented
Restart Counter to all the PMIPv6 nodes that had previously Restart Counter to all the PMIPv6 nodes that had previously
established PMIPv6 sessions. Note that this is possible only when established PMIPv6 sessions. Note that this is possible only when
the PMIPv6 node stores information about the peers in non-volatile the PMIPv6 node stores information about the peers in non-volatile
memory. The unsolicited Heartbeat Response message allows the peer memory. The unsolicited Heartbeat Response message allows the peer
PMIPv6 nodes to quickly discover the restart. The sequence number PMIPv6 nodes to quickly discover the restart. The sequence number
field in the unsolicited Heartbeat Response is ignored and no field in the unsolicited Heartbeat Response is ignored and no
response to necessary; the nodes will synchronize during the next response is necessary; the nodes will synchronize during the next
Request and Response exchange. Request and Response exchange.
3.3. Heartbeat Message 3.3. Heartbeat Message
The following illustrates the message format for the Heartbeat The Heartbeat Message is based on the Mobility Header defined in
Mobility Header message. The 'MH Type' field in the Mobility Header Section 6.1 of [RFC3775]. The 'MH type' field in the Mobility Header
indicates that it is a Heartbeat message. indicates that it is a Heartbeat Message. This document does not
make any other changes to the Mobility Header message. Please refer
to [RFC3775] for a description of the fields in the Mobility Header
Message.
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Payload Proto | Header Len | MH Type | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Checksum | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| |
. .
. Message Data .
. .
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The Heartbeat Message follows the 'Checksum' field in the above
message. The following illustrates the message format for the
Heartbeat Mobility Header message.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reserved |U|R| | Reserved |U|R|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sequence Number | | Sequence Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
. .
. Mobility options .
. .
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Reserved Reserved
Set to 0 and ignored by the receiver. Set to 0 and ignored by the receiver.
'U'
Set to 1 in Unsolicited Heartbeat Response. Otherwise set to 0.
'R' 'R'
A 1-bit flag that indicates whether the message is a request or a A 1-bit flag that indicates whether the message is a request or a
response. When the 'R' flag is set to 0, it indicates that the response. When the 'R' flag is set to 0, it indicates that the
Heartbeat message is a request. When the 'R' flag is set to 1, it Heartbeat message is a request. When the 'R' flag is set to 1, it
indicates that the Heartbeat message is a response. indicates that the Heartbeat message is a response.
'U'
Set to 1 in Unsolicited Heartbeat Response. Otherwise set to 0.
Sequence Number Sequence Number
A 32-bit sequence number used for matching the request to the A 32-bit sequence number used for matching the request to the
reply. reply.
Mobility Options
Variable-length field of such length that the complete Mobility
Header is an integer multiple of 8 octets long. This field
contains zero or more TLV-encoded mobility options. The receiver
MUST ignore and skip any options which it does not understand. At
the time of writing this document, the Restart Counter Mobility
Option, described in Section 3.4, is the only valid option in this
message.
3.4. Restart Counter Mobility Option 3.4. Restart Counter Mobility Option
The following shows the message format for a new mobility option for The following shows the message format for a new mobility option for
carrying the Restart Counter Value in the Heartbeat message. The carrying the Restart Counter Value in the Heartbeat message. The
Restart Counter Mobility Option is only valid in a Heartbeat Response Restart Counter Mobility Option is only valid in a Heartbeat Response
message. It has an alignment requirement of 4n+2. message. It has an alignment requirement of 4n+2.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 8, line 12 skipping to change at page 8, line 43
concluding that the peer PMIPv6 node is not reachable. The concluding that the peer PMIPv6 node is not reachable. The
default value for this variable is 3. default value for this variable is 3.
6. Security Considerations 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 protection is not required. Integrity protection using IPsec
[RFC4301] for the heartbeat messages MUST be supported on the MAG and [RFC4301] for the heartbeat messages MUST be supported on the MAG and
the LMA. the LMA. RFC 4887 [RFC4887] describes how to protect Mobile IPv6
Binding Update and Acknowledgment signaling with IPsec. The
Heartbeat message defined in this specification is merely another
subtype of the same Mobility Header protocol that is already being
protected by IPsec. Therefore, protecting this additional message is
possible using the mechanisms and security policy models from these
RFCs. The security policy database entries should use the new MH
Type, the Heartbeat Message, for the MH Type selector. See RFC 4887
for more details.
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 [RFC4306] should be used. IKEv2 [RFC4306] should be used.
7. 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' name space in the
Header defined in RFC 3775 [RFC3775]. Mobility Header defined in RFC 3775 [RFC3775].
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 name space as the Mobility
defined in RFC 3775 [RFC3775]. Options defined in RFC 3775 [RFC3775].
8. 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 [I-D.giaretta-netlmm-dt-protocol]. protocol was first described in [I-D.giaretta-netlmm-dt-protocol].
The authors would like to thank the members of a NETLMM design team The authors would like to thank the members of a NETLMM design team
that produced that document. The mechanism described in this that produced that document. The mechanism described in this
document also derives from the path management mechanism described in document also derives from the path management mechanism described in
[GTP]. [GTP].
skipping to change at page 9, line 14 skipping to change at page 10, line 8
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-08
(work in progress), January 2009. (work in progress), January 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.
9.2. Informative References [RFC4887] Thubert, P., Wakikawa, R., and V. Devarapalli, "Network
Mobility Home Network Models", RFC 4887, July 2007.
[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.
9.2. Informative References
[I-D.giaretta-netlmm-dt-protocol] [I-D.giaretta-netlmm-dt-protocol]
Giaretta, G., "The NetLMM Protocol", 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.
[GTP] 3rd Generation Partnership Project, "3GPP Technical [GTP] 3rd Generation Partnership Project, "3GPP Technical
Specification 29.060 V7.6.0: "Technical Specification Specification 29.060 V7.6.0: "Technical Specification
Group Core Network and Terminals; General Packet Radio Group Core Network and Terminals; General Packet Radio
Service (GPRS); GPRS Tunnelling Protocol (GTP) across the Service (GPRS); GPRS Tunnelling Protocol (GTP) across the
Gn and Gp interface (Release 7)"", July 2007. Gn and Gp interface (Release 7)"", July 2007.
 End of changes. 17 change blocks. 
33 lines changed or deleted 79 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/