draft-ietf-dmm-lma-controlled-mag-params-05.txt   rfc8127.txt 
DMM WG D. Patki Internet Engineering Task Force (IETF) D. Patki
Internet-Draft S. Gundavelli Request for Comments: 8127 S. Gundavelli
Intended status: Standards Track Cisco Category: Standards Track Cisco
Expires: December 2, 2017 J. Lee ISSN: 2070-1721 J. Lee
Sangmyung University Sangmyung University
Q. Fu Q. Fu
China Mobile China Mobile
L. Bertz L. Bertz
Sprint Sprint
May 31, 2017 August 2017
LMA Controlled MAG Session Parameters Mobile Access Gateway Configuration Parameters Controlled
draft-ietf-dmm-lma-controlled-mag-params-05.txt by the Local Mobility Anchor
Abstract Abstract
This specification defines a new extension, LMA-Controlled-MAG- This specification defines a new extension,
Session-Params to Proxy Mobile IPv6. This option can be used by the LMA-Controlled-MAG-Session-Params, to Proxy Mobile IPv6. This option
local mobility anchor in Proxy Mobile IPv6 signaling for notifying can be used by the local mobility anchor (LMA) in a Proxy Mobile IPv6
the mobile access gateway to conform to various configuration domain for signaling a mobile access gateway (MAG) on enforcing
parameters such as heartbeat parameters and binding refresh specific values for various configuration parameters such as
parameters. heartbeat and binding refresh parameters.
Status of this Memo
This Internet-Draft is submitted in full conformance with the Status of This Memo
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering This is an Internet Standards Track document.
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months This document is a product of the Internet Engineering Task Force
and may be updated, replaced, or obsoleted by other documents at any (IETF). It represents the consensus of the IETF community. It has
time. It is inappropriate to use Internet-Drafts as reference received public review and has been approved for publication by the
material or to cite them other than as "work in progress." Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 7841.
This Internet-Draft will expire on December 2, 2017. Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc8127.
Copyright Notice Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the Copyright (c) 2017 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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Conventions and Terminology . . . . . . . . . . . . . . . . . 3 2. Conventions and Terminology . . . . . . . . . . . . . . . . . 3
2.1. Conventions . . . . . . . . . . . . . . . . . . . . . . . 3 2.1. Conventions . . . . . . . . . . . . . . . . . . . . . . . 3
2.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3 2.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3
3. Protocol Extension . . . . . . . . . . . . . . . . . . . . . . 3 3. Protocol Extension . . . . . . . . . . . . . . . . . . . . . 4
3.1. Format of the LCMP Sub-Options . . . . . . . . . . . . . . 4 3.1. Format of the LCMP Sub-Options . . . . . . . . . . . . . 5
3.1.1. Binding Re-registration Control Sub-Option . . . . . . 5 3.1.1. Binding Re-registration Control Sub-Option . . . . . 6
3.1.2. Heartbeat Control Sub-Option . . . . . . . . . . . . . 6 3.1.2. Heartbeat Control Sub-Option . . . . . . . . . . . . 7
4. Protocol Configuration Variables . . . . . . . . . . . . . . . 7 4. Protocol Configuration Variables . . . . . . . . . . . . . . 8
4.1. Local Mobility Anchor - Configuration Variables . . . . . 7 4.1. Local Mobility Anchor -- Configuration Variables . . . . 8
5. Protocol Considerations . . . . . . . . . . . . . . . . . . . 8 5. Protocol Considerations . . . . . . . . . . . . . . . . . . . 9
5.1. Local Mobility Anchor Considerations . . . . . . . . . . . 9 5.1. Local Mobility Anchor Considerations . . . . . . . . . . 10
5.2. Mobile Access Gateway Considerations . . . . . . . . . . . 10 5.2. Mobile Access Gateway Considerations . . . . . . . . . . 10
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11
7. Security Considerations . . . . . . . . . . . . . . . . . . . 11 7. Security Considerations . . . . . . . . . . . . . . . . . . . 11
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 11 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 12
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 11 8.1. Normative References . . . . . . . . . . . . . . . . . . 12
9.1. Normative References . . . . . . . . . . . . . . . . . . . 11 8.2. Informative References . . . . . . . . . . . . . . . . . 12
9.2. Informative References . . . . . . . . . . . . . . . . . . 11 Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 13
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 12 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 14
1. Introduction 1. Introduction
A large Proxy Mobile IPv6 (PMIPv6) [RFC5213] deployment, such as A large Proxy Mobile IPv6 (PMIPv6) [RFC5213] deployment, such as
residential deployment, can have tens of thousands of mobile access residential deployment, can have tens of thousands of mobile access
gateways (MAG) spread across geographical locations. While it can be gateways (MAGs) spread across geographical locations. While it can
operationally challenging to manage such a large number of MAGs, it be operationally challenging to manage such a large number of MAGs,
can also be very difficult to ensure configuration consistency across it can also be very difficult to ensure configuration consistency
all the MAGs if they are not centrally managed. Configuring across all the MAGs if they are not centrally managed. Configuring
aggressive values of parameters such as re-registration timeout and aggressive values of parameters such as re-registration timeout and
heartbeat interval can potentially create considerable signaling load heartbeat interval can potentially create considerable signaling load
on the local mobility anchor (LMA). This document provides a new on the local mobility anchor (LMA). This document provides a new
option to enable the LMA to control various parameters on the MAG option to enable the LMA to control various parameters on the MAG
such as the re-registration frequency [RFC5213] and heartbeat such as the re-registration frequency [RFC5213] and heartbeat
frequency [RFC5847]. With this option, the configuration of these frequency [RFC5847]. With this option, the configuration of these
tunable parameters done centrally on the LMA enables Service tunable parameters enforced centrally from the LMA enables Service
Providers to have better control on the behavior of the MAGs with Providers to have better control on the behavior of the MAGs with
deterministic signaling load on the LMA. deterministic signaling load on the LMA.
2. Conventions and Terminology 2. Conventions and Terminology
2.1. Conventions 2.1. Conventions
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
document are to be interpreted as described in [RFC2119]. "OPTIONAL" in this document are to be interpreted as described in
BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here.
2.2. Terminology 2.2. Terminology
All the terms used in this document are to be interpreted as defined All the terms used in this document are to be interpreted as defined
in [RFC5213], [RFC5847] and [RFC7563]. in [RFC5213], [RFC5847], and [RFC7563].
3. Protocol Extension 3. Protocol Extension
The LMA Controlled MAG Parameters (LCMP) option is a mobility header The LMA-Controlled MAG Parameters (LCMPs) option is a mobility header
option used to exchange information related to the parameters that a option used to exchange information related to the parameters that an
LMA enforces on a MAG. The option can be included in Proxy Binding LMA enforces on a MAG. This option can be included only in the Proxy
Acknowledge (PBA) message only, and there MUST NOT be more than a Binding Acknowledge (PBA) message, and there MUST NOT be more than a
single instance of this mobility option in the PBA message. This single instance of this mobility option in a given PBA message. This
mobility option MUST contain one or more LCMP sub-options. The sub- option MUST contain one or more LCMP sub-options. Each LCMP sub-
options are defined in Section 3.1. The LCMP option has an alignment option carries a specific configuration parameter. The sub-options
requirement of 4n+2 [RFC2460]. are defined in Section 3.1. The LCMP option has an alignment
requirement of 4n+2 [RFC8200].
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | | Type | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| LCMP Sub-option(s) ~ | LCMP Sub-Option(s) ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 1: LMA Controlled MAG Parameters Option Figure 1: LMA-Controlled MAG Parameters Option
Type Type
MUST be set to the value of IANA-1, indicating that it is a LMA- MUST be set to the value of 62, indicating that it is an
Controlled-MAG-Parameters option. LMA-Controlled-MAG-Parameters option.
Length Length
8-bit unsigned integer indicating the length in octets of the 8-bit unsigned integer indicating the length in octets of the
option, excluding the Type and Length fields. option, excluding the Type and Length fields.
LCMP Sub-option(s) LCMP Sub-Option(s)
LCMP Sub-options are described in the below sections. The sub- LCMP sub-options are described in the sections below. The sub-
options can be present in any order. Inclusion of any specifc options can be present in any order. Inclusion of any specific
sub-option is optional, but at least one sub-option MUST be sub-option is optional, but at least one sub-option MUST be
present. present.
3.1. Format of the LCMP Sub-Options 3.1. Format of the LCMP Sub-Options
The LCMP sub-options are used for carrying information elements The LCMP sub-options are used for carrying information elements
related to various parameters that need to be configured on the MAG. related to various parameters that need to be configured on the MAG.
These sub-options can be included in the LCMP option defined in These sub-options can be included in the LCMP option defined in
Section 3. The LCMP sub-options have an alignment requirement of 4n. Section 3. The LCMP sub-options have an alignment requirement of 4n.
The format of this sub-option is as follows. The format of this sub-option is as follows.
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| LCMP Type | LCMP Length | Sub-Option Data ~ | LCMP Type | LCMP Length | Sub-Option Data ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 2: LMA Controlled MAG Parameters Sub-Option Figure 2: LMA-Controlled MAG Parameters Sub-Option
Type Type
8-bit unsigned integer indicating the type of the LCMP sub-option. 8-bit unsigned integer indicating the type of the LCMP sub-option.
This specification defines the following types: This specification defines the following types:
0 - Reserved 0 - Reserved
1 - Binding Re-registration Control Sub-Option 1 - Binding Re-registration Control Sub-Option
skipping to change at page 5, line 25 skipping to change at page 6, line 8
Length Length
8-bit unsigned integer indicating the number of octets needed to 8-bit unsigned integer indicating the number of octets needed to
encode the Option Data, excluding the LCMP Type and LCMP Length encode the Option Data, excluding the LCMP Type and LCMP Length
fields of the sub-option. fields of the sub-option.
3.1.1. Binding Re-registration Control Sub-Option 3.1.1. Binding Re-registration Control Sub-Option
The Binding Re-registration Control Sub-Option is a mobility sub- The Binding Re-registration Control Sub-Option is a mobility sub-
option carried in the LCMP mobility option defined in Section 3.1. option carried in the LCMP mobility option defined in Section 3.
This sub-option carries re-registration related timer values. There This sub-option carries timer values related to re-registration.
MUST be no more than a single instance of this sub-option in LCMP There MUST be no more than a single instance of this sub-option in
option. The format of this sub-option is defined below. the LCMP option. The format of this sub-option is defined below.
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| LCMP Type = 1 | LCMP Length | Re-registration-Start-Time | | LCMP Type = 1 | LCMP Length | Re-registration-Start-Time |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Initial-Retransmission-Time | Maximum-Retransmission-Time | | Initial-Retransmission-Time | Maximum-Retransmission-Time |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 3: Binding Re-registration Control Sub-Option Figure 3: Binding Re-registration Control Sub-Option
LCMP Type LCMP Type
1 for Binding Re-registration Control Sub-Option 1 for the Binding Re-registration Control Sub-Option.
LCMP Length LCMP Length
6 6
Re-registration-Start-Time Re-registration-Start-Time
16-bit unsigned integer indicating the number of time units before 16-bit unsigned integer indicating the number of time units before
the expiry of the PMIPv6 binding lifetime when the registration the expiry of the PMIPv6 binding lifetime when the registration
refresh process needs to be activated. One time unit is 4 refresh process needs to be activated. One time unit is 4
seconds. seconds.
Initial-Retransmission-Time Initial-Retransmission-Time
16-bit unsigned integer indicating minimum delay in seconds before 16-bit unsigned integer indicating minimum delay in seconds before
the first Proxy Binding Update (PBU) retransmission of the the first Proxy Binding Update (PBU) retransmission of the
exponential back-off process. exponential backoff process.
Maximum-Retransmission-Time Maximum-Retransmission-Time
16-bit unsigned integer indicating maximum delay in seconds before 16-bit unsigned integer indicating maximum delay in seconds before
the last PBU retransmission message of the exponential back-off the last PBU retransmission message of the exponential backoff
process. process.
3.1.2. Heartbeat Control Sub-Option 3.1.2. Heartbeat Control Sub-Option
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| LCMP Type = 2 | LCMP Length | HB-Interval | | LCMP Type = 2 | LCMP Length | HB-Interval |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| HB-Retransmission-Delay | HB-Max-Retransmissions | | HB-Retransmission-Delay | HB-Max-Retransmissions |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 4: Heartbeat Control Sub-Option Figure 4: Heartbeat Control Sub-Option
LCMP Type LCMP Type
2 for Heartbeat Control Sub-Option 2 for the Heartbeat Control Sub-Option.
LCMP Length LCMP Length
6 6
HB-Interval HB-Interval
16-bit unsigned integer indicating heartbeat interval, i.e. time 16-bit unsigned integer indicating the heartbeat interval, i.e.,
delay in seconds after a successful heartbeat exchange (heartbeat time delay in seconds after a successful heartbeat exchange
request followed by response) when the next heartbeat exchange can (heartbeat request followed by response) when the next heartbeat
be triggered. exchange can be triggered.
HB-Retransmission-Delay HB-Retransmission-Delay
16-bit unsigned integer indicating minimum time delay in seconds 16-bit unsigned integer indicating minimum time delay in seconds
before a heartbeat message is retransmitted. before a heartbeat message is retransmitted.
HB-Max-Retransmissions HB-Max-Retransmissions
16-bit unsigned integer indicating maximum number of heartbeat 16-bit unsigned integer indicating maximum number of heartbeat
retransmissions. retransmissions.
4. Protocol Configuration Variables 4. Protocol Configuration Variables
4.1. Local Mobility Anchor - Configuration Variables 4.1. Local Mobility Anchor -- Configuration Variables
This specification defines the following variables to be configured This specification defines the following variables to be configured
by the system management. The configured values for these protocol by the system management. The configured values for these protocol
variables MUST survive server reboots and service restarts. variables MUST survive server reboots and service restarts.
EnableLCMPSubOptReregControl EnableLCMPSubOptReregControl
This flag indicates the operational state of the Binding Re- This flag indicates the operational state of the Binding
registration Control sub-option support. The default value of Re-registration Control Sub-Option support. The default value of
this flag is (0), indicating that support for the Binding Re- this flag is (0), indicating that support for the Binding
registration Control sub-option is disabled. Re-registration Control Sub-Option is disabled.
EnableLCMPSubOptHeartbeatControl EnableLCMPSubOptHeartbeatControl
This flag indicates the operational state of the Heartbeat Control This flag indicates the operational state of the Heartbeat Control
sub-option support. The default value of this flag is (0), Sub-Option support. The default value of this flag is (0),
indicating that support for the Heartbeat Control sub-option is indicating that support for the Heartbeat Control Sub-Option is
disabled. disabled.
The following variables MAY be defined at various granularities such The following variables MAY be defined at various granularities such
as per binding, per cluster of bindings, per peering MAG, per cluster as per binding, per cluster of bindings, per peering MAG, per cluster
of peering MAGs or any other custom grouping. Regardless of the of peering MAGs, or any other custom grouping. Regardless of the
granularity of this configuration, the LMA MUST be able to determine granularity of this configuration, the LMA MUST be able to determine
the value of these variables for every individual binding. the value of these variables for every individual binding.
LCMPReregistrationStartTime LCMPReregistrationStartTime
This variable is used to set the minimum time interval in number This variable is used to set the minimum time interval in number
of seconds before the expiry of the PMIPv6 binding lifetime when of seconds before the expiry of the PMIPv6 binding lifetime when
the registration refresh process SHOULD be activated. The default the registration refresh process SHOULD be activated. The default
value of this variable is 10 units, where each unit is 4 seconds. value of this variable is 10 units, where each unit is 4 seconds.
LCMPInitialRetransmissionTime LCMPInitialRetransmissionTime
This variable is used to set the minimum delay in seconds before This variable is used to set the minimum delay in seconds before
the first PBU retransmission of the exponential back-off process. the first PBU retransmission of the exponential backoff process.
This variable is same as INITIAL_BINDACK_TIMEOUT mentioned in This variable is the same as INITIAL_BINDACK_TIMEOUT mentioned in
Section 6.9.4 of [RFC5213]. The default value of this variable is Section 6.9.4 of [RFC5213]. The default value of this variable is
1 second. 1 second.
LCMPMaximumRetransmissionTime LCMPMaximumRetransmissionTime
This variable is used to set the maximum delay in seconds before This variable is used to set the maximum delay in seconds before
the last PBU retransmission message of the exponential back-off the last PBU retransmission message of the exponential backoff
process. This variable is same as MAX_BINDACK_TIMEOUT mentioned process. This variable is the same as MAX_BINDACK_TIMEOUT
in Section 6.9.4 of [RFC5213]. The default value of this variable mentioned in Section 6.9.4 of [RFC5213]. The default value of
is 32 seconds. this variable is 32 seconds.
LCMPHeartbeatInterval LCMPHeartbeatInterval
This variable is used to set the time delay in seconds after a This variable is used to set the time delay in seconds after a
successful heartbeat exchange (heartbeat request followed by successful heartbeat exchange (heartbeat request followed by
response) when the next heartbeat exchange can be triggered. The response) when the next heartbeat exchange can be triggered. The
default value of this variable is 60 seconds. The time delay default value of this variable is 60 seconds. The time delay
SHOULD NOT be less than 30 seconds or more than 3600 seconds. The SHOULD NOT be less than 30 seconds or more than 3600 seconds. The
value of this variable MAY be derived from the variable value of this variable MAY be derived from the variable
HEARTBEAT_INTERVAL defined in Section 5 of [RFC5847] if configured HEARTBEAT_INTERVAL defined in Section 5 of [RFC5847] if configured
skipping to change at page 9, line 5 skipping to change at page 9, line 45
value of this variable MAY be derived from the variable value of this variable MAY be derived from the variable
MISSING_HEARTBEATS_ALLOWED defined in Section 5 of [RFC5847] if MISSING_HEARTBEATS_ALLOWED defined in Section 5 of [RFC5847] if
configured on the LMA. configured on the LMA.
5. Protocol Considerations 5. Protocol Considerations
The following considerations apply to the LMA and the MAG. The following considerations apply to the LMA and the MAG.
For supporting this extension, the conceptual Binding Cache Entry For supporting this extension, the conceptual Binding Cache Entry
data structure maintained by the LMA, described in Section 5.1 of data structure maintained by the LMA, described in Section 5.1 of
[RFC5213] and the conceptual Binding Update List entry data structure [RFC5213], and the conceptual Binding Update List entry data
maintained by the MAG, described in Section 6.1 of [RFC5213], need to structure maintained by the MAG, described in Section 6.1 of
be extended to store the LCMP option related information elements [RFC5213], need to be extended to store the information elements
defined below. related to the LCMP option that are defined below.
o LCMPReregistrationStartTime o LCMPReregistrationStartTime
o LCMPInitialRetransmissionTime o LCMPInitialRetransmissionTime
o LCMPMaximumRetransmissionTime o LCMPMaximumRetransmissionTime
o LCMPHeartbeatInterval o LCMPHeartbeatInterval
o LCMPHeartbeatRetransmissionDelay o LCMPHeartbeatRetransmissionDelay
o LCMPHeartbeatMaxRetransmissions o LCMPHeartbeatMaxRetransmissions
5.1. Local Mobility Anchor Considerations 5.1. Local Mobility Anchor Considerations
skipping to change at page 9, line 26 skipping to change at page 10, line 16
o LCMPHeartbeatInterval o LCMPHeartbeatInterval
o LCMPHeartbeatRetransmissionDelay o LCMPHeartbeatRetransmissionDelay
o LCMPHeartbeatMaxRetransmissions o LCMPHeartbeatMaxRetransmissions
5.1. Local Mobility Anchor Considerations 5.1. Local Mobility Anchor Considerations
On receiving a PBU message [RFC5213] from a MAG, the LMA MUST check On receiving a PBU message [RFC5213] from a MAG, the LMA MUST check
if the variable EnableLCMPSubOptReregControl is configured and set to if the variable EnableLCMPSubOptReregControl is configured and set to
(1). If yes, and if all of LCMPReregistrationStartTime, (1). If yes, and if LCMPReregistrationStartTime,
LCMPInitialRetransmissionTime and LCMPMaximumRetransmissionTime are LCMPInitialRetransmissionTime, and LCMPMaximumRetransmissionTime are
set to NON_ZERO values, then it MUST include Binding Re-registration all set to NON_ZERO values, then it MUST include the Binding
Control Sub-Option in the LCMP mobility option which is in turn Re-registration Control Sub-Option in the LCMP mobility option, which
included in the PBA message. If the variable is in turn included in the PBA message. If the variable
EnableLCMPSubOptReregControl is configured and set to (1) and if any EnableLCMPSubOptReregControl is configured and set to (1), and if any
of LCMPReregistrationStartTime, LCMPInitialRetransmissionTime and of LCMPReregistrationStartTime, LCMPInitialRetransmissionTime, and
LCMPMaximumRetransmissionTime is set to ZERO value, then the LMA MUST LCMPMaximumRetransmissionTime is set to ZERO value, then the LMA MUST
report a configuration error and reject the binding request by report a configuration error and reject the binding request by
sending a PBA message with status code '128-Reason Unspecified' sending a PBA message with status code '128 - Reason Unspecified'
[RFC5213]. [RFC5213].
The LMA MUST also check if variable EnableLCMPSubOptHeartbeatControl The LMA MUST also check if variable EnableLCMPSubOptHeartbeatControl
is configured and set to (1). If yes, and if all of is configured and set to (1). If yes, and if LCMPHeartbeatInterval,
LCMPHeartbeatInterval, LCMPHeartbeatRetransmissionDelay and LCMPHeartbeatRetransmissionDelay, and LCMPHeartbeatMaxRetransmissions
LCMPHeartbeatMaxRetransmissions are set to NON_ZERO values, then it are all set to NON_ZERO values, then it MUST include the Heartbeat
MUST include Heartbeat Control Sub-Option in the LCMP mobility option Control Sub-Option in the LCMP mobility option, which is in turn
which is in turn included in the PBA message. If the variable included in the PBA message. If the variable
EnableLCMPSubOptHeartbeatControl is set to (1) and if any of EnableLCMPSubOptHeartbeatControl is set to (1), and if any of
LCMPHeartbeatInterval, LCMPHeartbeatRetransmissionDelay and LCMPHeartbeatInterval, LCMPHeartbeatRetransmissionDelay, and
LCMPHeartbeatMaxRetransmissions is set to ZERO value, then the LMA LCMPHeartbeatMaxRetransmissions is set to ZERO value, then the LMA
MUST report a configuration error and reject the binding request by MUST report a configuration error and reject the binding request by
sending a PBA message with status code '128-Reason Unspecified' sending a PBA message with status code '128 - Reason Unspecified'
[RFC5213]. [RFC5213].
5.2. Mobile Access Gateway Considerations 5.2. Mobile Access Gateway Considerations
If the PBA message [RFC5213] received from the LMA contains the LCMP If the PBA message [RFC5213] received from the LMA contains the LCMP
mobility option and the Binding Re-registration Control Sub-Option, mobility option and the Binding Re-registration Control Sub-Option,
then the MAG MUST overwrite the binding re-registration related timer then the MAG MUST overwrite the timer parameters related to binding
parameters configured locally on the MAG with the parameters received re-registration that are configured locally on the MAG with the
in Binding Re-registration Control Sub-Option. If any of the parameters received in the Binding Re-registration Control Sub-
parameters in the Binding Re-registration Control Sub-Option is ZERO, Option. If any of the parameters in the Binding Re-registration
then the PBA message MUST be ignored and an error message SHOULD be Control Sub-Option are ZERO, then the PBA message MUST be ignored and
logged. an error message SHOULD be logged.
Similarly, if the LCMP mobility option contains the Heartbeat Control Similarly, if the LCMP mobility option contains the Heartbeat Control
Sub-Option, then the MAG MUST overwrite the heartbeat related timer Sub-Option, then the MAG MUST overwrite the heartbeat-related timer
parameters configured locally on the MAG with the parameters received parameters configured locally on the MAG with the parameters received
in the Heartbeat Control Sub-Option. If any of the parameters in the in the Heartbeat Control Sub-Option. If any of the parameters in the
Heartbeat Control Sub-Option except HB-Retransmission-Delay is ZERO, Heartbeat Control Sub-Option, except HB-Retransmission-Delay, are
then the PBA message MUST be ignored and error message SHOULD be ZERO, then the PBA message MUST be ignored and an error message
logged. SHOULD be logged.
6. IANA Considerations 6. IANA Considerations
This document requires the following IANA actions in the "Mobile IPv6 IANA has updated the "Mobile IPv6 parameters" registry as described
Parameters" registry. here.
o Action 1: This specification defines a new mobility header option, o Action 1: This specification defines a new mobility header option,
"LMA Controlled MAG Parameters". This mobility option is "LMA-Controlled MAG Parameters". This mobility option is
described in Section 3. The type value (IANA-1) for this option described in Section 3. The type value 62 has been assigned for
needs to be assigned from the same numbering space as allocated this option in the "Mobility Options" registry, as defined in
for the other mobility options, as defined in [RFC6275]. [RFC6275].
o Action 2: This specification defines a new mobility sub-option o Action 2: This specification defines a new mobility sub-option
format, the LCMP Parameters sub-option. The format of this format, the LCMP sub-option. The format of this mobility sub-
mobility sub-option is described in Section 3.1. This sub-option option is described in Section 3.1. This sub-option can be
can be carried in the LCMP Parameters option. The type value for carried in the LCMP option. The type values for this sub-option
this sub-option needs to be managed by IANA, under the registry are managed by IANA, under the "LMA-Controlled MAG Parameters Sub-
"LMA Controlled MAG Parameters Sub-Option Type Values". This Option Type Values" registry. Per this document, IANA has
specification reserves the following type values. Approval of new reserved the following type values. Approval of new LCMP sub-
LCMP Parameters sub-option type values are to be made through IANA option type values are to be made through Expert Review [RFC8126].
Expert Review.
+---+-----------------------------------------------------+ +---+-----------------------------------------------------+
| 0 | Reserved | | 0 | Reserved |
+---+-----------------------------------------------------+ +---+-----------------------------------------------------+
| 1 | Binding Re-registration Control Sub-Option | | 1 | Binding Re-registration Control Sub-Option |
+---+-----------------------------------------------------+ +---+-----------------------------------------------------+
| 2 | Heartbeat Control Sub-Option | | 2 | Heartbeat Control Sub-Option |
+---+-----------------------------------------------------+ +---+-----------------------------------------------------+
7. Security Considerations 7. Security Considerations
The LCMP Parameters option defined in this specification allows the The LCMP option defined in this specification allows the
configuration of re-registration and heartbeat frequencies. This configuration of re-registration and heartbeat frequencies. This
option is defined for carrying it in Proxy Binding Update and Proxy option is defined for carrying it in Proxy Binding Update and Proxy
Binding Acknowledgement messages. This option is carried like any Binding Acknowledgement messages. This option is carried like any
other mobility header option as specified in [RFC5213] and does not other mobility header option as specified and does not require any
require any special security considerations. special security considerations.
8. Acknowledgements
The authors would like to thank the DMM working group for all the
comments and discussions on this document. The authors would also
like to thank Suresh Krishnan, Ralph Droms, Mirja Kuehlewind, Alexey
Melnikov and Ben Campbell for their review feedback.
9. References 8. References
9.1. Normative References 8.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, DOI 10.17487/ Requirement Levels", BCP 14, RFC 2119,
RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<http://www.rfc-editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
[RFC5213] Gundavelli, S., Ed., Leung, K., Devarapalli, V., [RFC5213] Gundavelli, S., Ed., Leung, K., Devarapalli, V.,
Chowdhury, K., and B. Patil, "Proxy Mobile IPv6", Chowdhury, K., and B. Patil, "Proxy Mobile IPv6",
RFC 5213, DOI 10.17487/RFC5213, August 2008, RFC 5213, DOI 10.17487/RFC5213, August 2008,
<http://www.rfc-editor.org/info/rfc5213>. <https://www.rfc-editor.org/info/rfc5213>.
[RFC5847] Devarapalli, V., Ed., Koodli, R., Ed., Lim, H., Kant, N., [RFC5847] Devarapalli, V., Ed., Koodli, R., Ed., Lim, H., Kant, N.,
Krishnan, S., and J. Laganier, "Heartbeat Mechanism for Krishnan, S., and J. Laganier, "Heartbeat Mechanism for
Proxy Mobile IPv6", RFC 5847, DOI 10.17487/RFC5847, Proxy Mobile IPv6", RFC 5847, DOI 10.17487/RFC5847, June
June 2010, <http://www.rfc-editor.org/info/rfc5847>. 2010, <https://www.rfc-editor.org/info/rfc5847>.
[RFC7563] Pazhyannur, R., Speicher, S., Gundavelli, S., Korhonen, [RFC7563] Pazhyannur, R., Speicher, S., Gundavelli, S., Korhonen,
J., and J. Kaippallimalil, "Extensions to the Proxy Mobile J., and J. Kaippallimalil, "Extensions to the Proxy Mobile
IPv6 (PMIPv6) Access Network Identifier Option", RFC 7563, IPv6 (PMIPv6) Access Network Identifier Option", RFC 7563,
DOI 10.17487/RFC7563, June 2015, DOI 10.17487/RFC7563, June 2015,
<http://www.rfc-editor.org/info/rfc7563>. <https://www.rfc-editor.org/info/rfc7563>.
9.2. Informative References [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/info/rfc8174>.
[RFC2460] Deering, S. and R. Hinden, "Internet Protocol, Version 6 8.2. Informative References
(IPv6) Specification", RFC 2460, DOI 10.17487/RFC2460,
December 1998, <http://www.rfc-editor.org/info/rfc2460>.
[RFC6275] Perkins, C., Ed., Johnson, D., and J. Arkko, "Mobility [RFC6275] Perkins, C., Ed., Johnson, D., and J. Arkko, "Mobility
Support in IPv6", RFC 6275, DOI 10.17487/RFC6275, Support in IPv6", RFC 6275, DOI 10.17487/RFC6275, July
July 2011, <http://www.rfc-editor.org/info/rfc6275>. 2011, <https://www.rfc-editor.org/info/rfc6275>.
[RFC8126] Cotton, M., Leiba, B., and T. Narten, "Guidelines for
Writing an IANA Considerations Section in RFCs", BCP 26,
RFC 8126, DOI 10.17487/RFC8126, June 2017,
<https://www.rfc-editor.org/info/rfc8126>.
[RFC8200] Deering, S. and R. Hinden, "Internet Protocol, Version 6
(IPv6) Specification", STD 86, RFC 8200,
DOI 10.17487/RFC8200, July 2017,
<https://www.rfc-editor.org/info/rfc8200>.
Acknowledgements
The authors would like to thank the DMM Working Group for all the
comments and discussions on this document. The authors would also
like to thank Suresh Krishnan, Ralph Droms, Mirja Kuhlewind, Alexey
Melnikov, and Ben Campbell for their review feedback.
The work of Jong-Hyouk Lee was supported by 'The Cross-Ministry Giga
KOREA Project' grant from the Ministry of Science, ICT and Future
Planning, Korea.
Authors' Addresses Authors' Addresses
Dhananjay Patki Dhananjay Patki
Cisco Cisco
Cessna Business Park SEZ, Kadubeesanahalli Cessna Business Park SEZ, Kadubeesanahalli
Bangalore, Karnataka 560087 Bangalore, Karnataka 560087
India India
Email: dhpatki@cisco.com Email: dhpatki@cisco.com
Sri Gundavelli Sri Gundavelli
Cisco Cisco
170 West Tasman Drive 170 West Tasman Drive
San Jose, CA 95134 San Jose, CA 95134
USA United States of America
Email: sgundave@cisco.com Email: sgundave@cisco.com
Jong-Hyouk Lee Jong-Hyouk Lee
Sangmyung University Sangmyung University
31, Sangmyeongdae-gil, Dongnam-gu 31, Sangmyeongdae-gil, Dongnam-gu
Cheonan 330-720 Cheonan 31066
Republic of Korea Republic of Korea
Email: jonghyouk@smu.ac.kr Email: jonghyouk@smu.ac.kr
Qiao Fu Qiao Fu
China Mobile China Mobile
Xuanwumenxi Ave. No.32 Xuanwumenxi Ave. No.32
Beijing Beijing
P.R. China China
Email: fuqiao1@outlook.com Email: fuqiao1@outlook.com
Lyle T Bertz
Lyle T. Bertz
Sprint Sprint
Kansas Kansas
USA United States of America
Email: Lyle.T.Bertz@sprint.com Email: Lyle.T.Bertz@sprint.com
 End of changes. 60 change blocks. 
171 lines changed or deleted 184 lines changed or added

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