draft-ietf-dmm-lma-controlled-mag-params-02.txt   draft-ietf-dmm-lma-controlled-mag-params-03.txt 
DMM WG D. Patki DMM WG D. Patki
Internet-Draft S. Gundavelli Internet-Draft S. Gundavelli
Intended status: Standards Track Cisco Intended status: Standards Track Cisco
Expires: January 2, 2017 J. Lee Expires: August 9, 2017 J. Lee
Sangmyung University Sangmyung University
Q. Fu Q. Fu
China Mobile China Mobile
L. Bertz L. Bertz
Sprint Sprint
July 1, 2016 February 5, 2017
LMA Controlled MAG Session Parameters LMA Controlled MAG Session Parameters
draft-ietf-dmm-lma-controlled-mag-params-02.txt draft-ietf-dmm-lma-controlled-mag-params-03.txt
Abstract Abstract
This specification defines a new extension, LMA-Controlled-MAG- This specification defines a new extension, LMA-Controlled-MAG-
Session-Params to Proxy Mobile IPv6. This option can be used by the Session-Params to Proxy Mobile IPv6. This option can be used by the
LMA in PMIPv6 signaling for notifying the MAG to conform to various local mobility anchor (LMA) in Proxy Mobile IPv6 (PMIPv6) signaling
for notifying the mobile access gateway (MAG) to conform to various
parameters contained in this extension. parameters contained in this extension.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted 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). 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 January 2, 2017. This Internet-Draft will expire on August 9, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2016 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
skipping to change at page 2, line 19 skipping to change at page 2, line 20
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
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 . . . . . . . . . . . . . . . . . . . . . 3
3.1. Format of the LCMP Sub-Options . . . . . . . . . . . . . 4 3.1. Format of the LCMP Sub-Options . . . . . . . . . . . . . 4
3.1.1. Binding Re-registration Control Sub-Option . . . . . 5 3.1.1. Binding Re-registration Control Sub-Option . . . . . 5
3.1.2. Heartbeat Control Sub-Option . . . . . . . . . . . . 5 3.1.2. Heartbeat Control Sub-Option . . . . . . . . . . . . 6
4. Protocol Configuration Variables . . . . . . . . . . . . . . 6 4. Protocol Configuration Variables . . . . . . . . . . . . . . 6
4.1. Local Mobility Anchor - Configuration Variables . . . . . 6 4.1. Local Mobility Anchor - Configuration Variables . . . . . 6
5. Protocol Considerations . . . . . . . . . . . . . . . . . . . 8 5. Protocol Considerations . . . . . . . . . . . . . . . . . . . 8
5.1. Local Mobility Anchor Considerations . . . . . . . . . . 9 5.1. Local Mobility Anchor Considerations . . . . . . . . . . 8
5.2. Mobile Access Gateway Considerations . . . . . . . . . . 9 5.2. Mobile Access Gateway Considerations . . . . . . . . . . 9
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9
7. Security Considerations . . . . . . . . . . . . . . . . . . . 10 7. Security Considerations . . . . . . . . . . . . . . . . . . . 10
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 10 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 10
8.1. Normative References . . . . . . . . . . . . . . . . . . 10 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 10
8.2. Informative References . . . . . . . . . . . . . . . . . 11 9.1. Normative References . . . . . . . . . . . . . . . . . . 10
9.2. Informative References . . . . . . . . . . . . . . . . . 11
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 11 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 11
1. Introduction 1. Introduction
A large PMIPv6 deployment, such as residential deployment, can have A large PMIPv6 deployment, such as residential deployment, can have
tens of thousands of MAGs spread across geographical locations. tens of thousands of MAGs spread across geographical locations.
While it can be operationally challenging to manage such a large While it can be operationally challenging to manage such a large
number of MAGs, it can also be very difficult to ensure configuration number of MAGs, it can also be very difficult to ensure configuration
consistency across all the MAGs if they are not centrally managed. consistency across all the MAGs if they are not centrally managed.
Configuring aggressive values of parameters such as re-registration Configuring aggressive values of parameters such as re-registration
skipping to change at page 3, line 22 skipping to change at page 3, line 22
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 (LCMP) 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 a
local mobility anchor enforces on a mobile access gateway. The LMA enforces on a MAG. The option can be included in Proxy Binding
option can be included in Proxy Binding Acknowledgement (PBA) message Acknowledge (PBA) message only, and there MUST NOT be more than a
only, and there MUST NOT be more than a single instance of this single instance of this mobility option in the PBA message. This
mobility option in a mobility message. This mobility option MUST mobility option MUST contain one or more LCMP sub-options. The
contain one or more LMA Controlled MAG Parameters sub-options. The
suboptions are defined in Section 3.1. The alignment of this option suboptions are defined in Section 3.1. The alignment of this option
MUST be 4n [RFC2460]. MUST be 4n [RFC2460].
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 | Reserved | | Type | Length | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... LCMP Sub-option(s) ... ~ | ... LCMP Sub-option(s) ... ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 4, line 16 skipping to change at page 4, line 16
MUST be set to zero when sending and ignored when received. MUST be set to zero when sending and ignored when received.
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 below sections. The sub-
options are optional and can be present in any order. options are optional and can be present in any order.
3.1. Format of the LCMP Sub-Options 3.1. Format of the LCMP Sub-Options
The LMA Controlled MAG Parameters sub-options are used for carrying The LCMP sub-options are used for carrying information elements
information elements related to various parameters that need to be related to various parameters that need to be configured on the MAG.
configured on the MAG. These sub-options can be included in the LMA These sub-options can be included in the LCMP option defined in
Controlled MAG Parameters option defined in Section 3. The alignment Section 3. The alignment of the sub-option MUST be 4n. The format
of the sub-option MUST be 4n. The format of this sub-option is as of this sub-option is as follows.
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 LMA Controlled 8-bit unsigned integer indicating the type of the LCMP sub-option.
MAG Parameters sub-option. This specification defines the This specification defines the following types:
following types:
0 - Reserved 0 - Reserved
1 - Binding Refresh Control Sub-Option 1 - Binding Refresh Control Sub-Option
2 - Heartbeat Control Sub-Option 2 - Heartbeat Control Sub-Option
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 LMA Controlled MAG Parameters mobility option option carried in the LCMP mobility option defined in Section 3.1.
defined in Section 3.1. This sub-option carries re-registration This sub-option carries re-registration related timer values. There
related timer values. There MUST be no more than a single instance MUST be no more than a single instance of this sub-option in LCMP
of this sub-option in LMA Controlled MAG Parameters option. The option. The format of this sub-option is defined below.
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
1 for Binding Refresh Control Sub-Option
LCMP Length
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 PBU retransmission of the exponential back-off process. the first Proxy Binding Update (PBU) retransmission of the
exponential back-off 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 back-off
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
skipping to change at page 6, line 14 skipping to change at page 6, line 17
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
2 for Heartbeat Control Sub-Option
LCMP Length
6
HB-Interval HB-Interval
16-bit unsigned integer indicating heartbeat interval, i.e. time 16-bit unsigned integer indicating heartbeat interval, i.e. time
delay in seconds after a successful heartbeat exchange (request delay in seconds after a successful heartbeat exchange (heartbeat
followed by response) when the next heartbeat exchange can be request followed by response) when the next heartbeat exchange can
triggered. 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
The local mobility anchor MUST allow the following variables to be The LMA MUST allow the following variables to be configured by the
configured by the system management. The configured values for these system management. The configured values for these protocol
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 Re-
registration Control sub-option support. The default value for registration Control sub-option support. The default value for
this flag is set to (0), indicating that support for the Binding this flag is set to (0), indicating that support for the Binding
Re-registration Control sub-option is disabled. Re-registration Control sub-option is disabled.
When this flag on the local mobility anchor is set to a value of
(1), the local mobility anchor SHOULD include this sub-option in
the Proxy Binding Acknowledge messages that it sends to the mobile
access gateway; otherwise, it MUST NOT include the sub-option.
There can be situations where the local mobility anchor is unable
to obtain the Binding Re-registration Control information and may
not be able to construct this sub-option.
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 for this flag is set to sub-option support. The default value for this flag is set to
(0), indicating that support for the Heartbeat Control sub-option (0), indicating that support for the Heartbeat Control sub-option
is disabled. is disabled.
When this flag on the local mobility anchor is set to a value of The following variables MAY be defined at various granularities such
(1), the local mobility anchor SHOULD include this sub-option in as per binding, per peering MAG, per cluster of MAGs or any other
the Proxy Binding Acknowledge messages that it sends to the mobile custom grouping. Regardless of the granularity of this
access gateway; otherwise, it MUST NOT include the sub-option. configuration, the LMA MUST be able to determine the value of these
There can be situations where the local mobility anchor is unable
to obtain the Heartbeat Control information and may not be able to
construct this sub-option.
The following variables MAY be defined at various granularity such as
per binding, per peering MAG, per cluster of MAGs or any other custom
grouping. Regardless of the granularity of this configuration, the
local mobility anchor should be able to determine the value of these
variables on an individual binding basis by way of configuration variables on an individual binding basis by way of configuration
hierarchy. hierarchy.
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 is 10 units, where each unit is 4 seconds. value is 10 units, where each unit is 4 seconds.
skipping to change at page 8, line 4 skipping to change at page 7, line 45
Section 6.9.4 of [RFC5213]. The default value is 1 second. Section 6.9.4 of [RFC5213]. The default value is 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 back-off
process. This variable is same as MAX_BINDACK_TIMEOUT mentioned process. This variable is same as MAX_BINDACK_TIMEOUT mentioned
in Section 6.9.4 of [RFC5213]. The default value is 32 seconds. in Section 6.9.4 of [RFC5213]. The default value 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 (request followed by response) when successful heartbeat exchange (heartbeat request followed by
the next heartbeat exchange can be triggered. The default value response) when the next heartbeat exchange can be triggered. The
is 60 seconds. It SHOULD NOT be set to less than 30 seconds or default value is 60 seconds. It SHOULD NOT be set to less than 30
more than 3600 seconds. The value of this variable MAY be derived seconds or more than 3600 seconds. The value of this variable MAY
from the variable HEARTBEAT_INTERVAL defined in Section 5 of be derived from the variable HEARTBEAT_INTERVAL defined in
[RFC5847] if defined on the local mobility anchor. Section 5 of [RFC5847] if configured on the LMA.
LCMPHeartbeatRetransmissionDelay LCMPHeartbeatRetransmissionDelay
This variable is used to set the minimum time delay in seconds This variable is used to set the minimum time delay in seconds
before a heartbeat message is retransmitted. The value of this before a heartbeat message is retransmitted. The value of this
variable SHOULD be less than LCMP_HEARTBEAT_INTERVAL. The default variable SHOULD be less than LCMPHeartbeatInterval. The default
value is 5 seconds. value is 5 seconds.
LCMPHeartbeatMaxRetransmissions LCMPHeartbeatMaxRetransmissions
This variable is used to set the maximum number of heartbeat This variable is used to set the maximum number of heartbeat
retransmissions. The default value for this variable is 3. The retransmissions. The default value for this variable is 3. The
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
defined on the local mobility anchor. configured on the LMA.
5. Protocol Considerations 5. Protocol Considerations
The following considerations apply to the local mobility anchor and The following considerations apply to the LMA and the MAG.
the mobile access gateway.
The conceptual Binding Cache Entry data structure maintained by the The conceptual Binding Cache Entry data structure maintained by the
local mobility anchor, described in Section 5.1 of [RFC5213] and the LMA, described in Section 5.1 of [RFC5213] and the conceptual Binding
conceptual Binding Update List entry data structure maintained by the Update List entry data structure maintained by the MAG, described in
mobile access gateway, described in Section 6.1 of [RFC5213], MUST be Section 6.1 of [RFC5213], MUST be extended to store the LCMP option
extended to store the LMA Controlled MAG Parameters option related related information elements associated with the current session.
information elements associated with the current session.
Specifically the following parameters MUST be defined: Specifically the following parameters MUST be defined:
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
o On receiving a Proxy Binding Update message [RFC5213] from a On receiving a PBU message [RFC5213] from a MAG, the LMA MUST check
mobile access gateway, the local mobility anchor should check if if the variable EnableLCMPSubOptReregControl is configured and set to
EnableLCMPSubOptReregControl is set to (1). If yes, and if all of (1). If yes, and if all of LCMPReregistrationStartTime,
LCMPReregistrationStartTime, LCMPInitialRetransmissionTime and LCMPInitialRetransmissionTime and LCMPMaximumRetransmissionTime are
LCMPMaximumRetransmissionTime are set to NON_ZERO values, then in set to NON_ZERO values, then it MUST include Binding Re-registration
SHOULD include Binding Re-registration Control Sub-Option in the Control Sub-Option in the LCMP mobility option which is in turn
LMA Controlled MAG Parameters mobility option which is in turn included in the PBA message. If the variable
included in the Proxy Binding Acknowledge message. EnableLCMPSubOptReregControl is configured and set to (1) and if any
of LCMPReregistrationStartTime, LCMPInitialRetransmissionTime and
o If EnableLCMPSubOptReregControl is set to (1) and if any of LCMPMaximumRetransmissionTime is set to ZERO value, then the LMA MUST
LCMPReregistrationStartTime, LCMPInitialRetransmissionTime and report a configuration error and reject the binding request by
LCMPMaximumRetransmissionTime is set to ZERO value, then the local sending a PBA message with status code '128-Reason Unspecified'
mobility anchor should report a configuration error. [RFC5213].
o The local mobility anchor should also check if
EnableLCMPSubOptHeartbeatControl is set to (1). If yes, and if
all of LCMPHeartbeatInterval, LCMPHeartbeatRetransmissionDelay and
LCMPHeartbeatMaxRetransmissions are set to NON_ZERO values, then
in SHOULD include Heartbeat Control Sub-Option in the LMA
Controlled MAG Parameters mobility option which is in turn
included in the Proxy Binding Acknowledge message.
o If EnableLCMPSubOptHeartbeatControl is set to (1) and if any of The LMA MUST also check if variable EnableLCMPSubOptHeartbeatControl
LCMPHeartbeatInterval, LCMPHeartbeatRetransmissionDelay and is configured and set to (1). If yes, and if all of
LCMPHeartbeatMaxRetransmissions is set to ZERO value, then the LCMPHeartbeatInterval, LCMPHeartbeatRetransmissionDelay and
local mobility anchor should report a configuration error. LCMPHeartbeatMaxRetransmissions are set to NON_ZERO values, then it
MUST include Heartbeat Control Sub-Option in the LCMP mobility option
which is in turn included in the PBA message. If the variable
EnableLCMPSubOptHeartbeatControl is set to (1) and if any of
LCMPHeartbeatInterval, LCMPHeartbeatRetransmissionDelay and
LCMPHeartbeatMaxRetransmissions is set to ZERO value, then the LMA
MUST report a configuration error and reject the binding request by
sending a PBA message with status code '128-Reason Unspecified'
[RFC5213].
5.2. Mobile Access Gateway Considerations 5.2. Mobile Access Gateway Considerations
o On Receiving Proxy Binding Acknowledge message [RFC5213] from the If the PBA message [RFC5213] received from the LMA contains the LCMP
local mobility anchor with LMA Controlled MAG Parameters mobility mobility option and the Binding Re-registration Control Sub-Option,
option, the mobile access gateway MUST overwrite the binding re- then the MAG MUST overwrite the binding re-registration related timer
registration related timer parameters with the parameters received parameters configured locally on the MAG with the parameters received
in Binding Re-registration Control Sub-Option, if present in the in Binding Re-registration Control Sub-Option. If any of the
LMA Controlled MAG Parameters mobility option. Similarly, the parameters in the Binding Re-registration Control Sub-Option is ZERO,
mobile access gateway MUST overwrite the heartbeat related timer then the PBA message MUST be ignored and an error message SHOULD be
parameters with the parameters received in Heartbeat Control Sub- logged.
Option, if present in the LMA Controlled MAG Parameters mobility
option.
o If any of the parameters in the Binding Re-registration Control
Sub-Option is ZERO, then the sub-option MUST be ignored and an
error message SHOULD be logged.
o If any of the parameters in the Heartbeat Control Sub-Option Similarly, if the LCMP mobility option contains the Heartbeat Control
except HB-Retransmission-Delay is ZERO, then the sub-option MUST Sub-Option, then the MAG MUST overwrite the heartbeat related timer
be ignored and error message SHOULD be logged. parameters configured locally on the MAG with the parameters received
in the Heartbeat Control Sub-Option. If any of the parameters in the
Heartbeat Control Sub-Option except HB-Retransmission-Delay is ZERO,
then the PBA message MUST be ignored and error message SHOULD be
logged.
6. IANA Considerations 6. IANA Considerations
This document requires the following IANA actions. This document requires the following IANA actions in the "Mobile IPv6
Parameters" registry.
o Action 1: This specification defines a new mobility header option, o Action 1: This specification defines a new mobility header option,
the 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 (IANA-1) for this option
needs to be assigned from the same numbering space as allocated needs to be assigned from the same numbering space as allocated
for the other mobility options, as defined in [RFC6275]. for the other mobility options, as defined in [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 LMA Controlled MAG Parameters sub-option. The format format, the LCMP Parameters sub-option. The format of this
of this mobility sub-option is described in Section 3.1. This mobility sub-option is described in Section 3.1. This sub-option
sub-option can be carried in the LMA Controlled MAG Parameters can be carried in the LCMP Parameters option. The type value for
option. The type value for this sub-option needs to be managed by this sub-option needs to be managed by IANA, under the registry
IANA, under the registry "LMA Controlled MAG Parameters Sub-Option "LMA Controlled MAG Parameters Sub-Option Type Values". This
Type Values". This specification reserves the following type specification reserves the following type values. Approval of new
values. Approval of new LMA Controlled MAG Parameters sub-option LCMP Parameters sub-option type values are to be made through IANA
type values are to be made through IANA Expert Review. 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 LMA Controlled MAG Parameters option defined in this The LCMP Parameters option defined in this specification is for use
specification is for use in Proxy Binding Acknowledgement message. in PBA message. This option is carried like any other mobility
This option is carried like any other mobility header option as header option as specified in [RFC6275] and does not require any
specified in [RFC6275] and does not require any special security special security considerations.
considerations.
8. References 8. Acknowledgements
8.1. Normative References 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 and Ralph Droms for their review
feedback.
9. 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, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<http://www.rfc-editor.org/info/rfc2119>. <http://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>. <http://www.rfc-editor.org/info/rfc5213>.
skipping to change at page 11, line 21 skipping to change at page 11, line 21
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, June Proxy Mobile IPv6", RFC 5847, DOI 10.17487/RFC5847, June
2010, <http://www.rfc-editor.org/info/rfc5847>. 2010, <http://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>. <http://www.rfc-editor.org/info/rfc7563>.
8.2. Informative References 9.2. Informative References
[RFC2460] Deering, S. and R. Hinden, "Internet Protocol, Version 6 [RFC2460] Deering, S. and R. Hinden, "Internet Protocol, Version 6
(IPv6) Specification", RFC 2460, DOI 10.17487/RFC2460, (IPv6) Specification", RFC 2460, DOI 10.17487/RFC2460,
December 1998, <http://www.rfc-editor.org/info/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, July Support in IPv6", RFC 6275, DOI 10.17487/RFC6275, July
2011, <http://www.rfc-editor.org/info/rfc6275>. 2011, <http://www.rfc-editor.org/info/rfc6275>.
Authors' Addresses Authors' Addresses
 End of changes. 40 change blocks. 
134 lines changed or deleted 137 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/