--- 1/draft-ietf-dmm-lma-controlled-mag-params-00.txt 2016-04-13 17:15:53.185809955 -0700 +++ 2/draft-ietf-dmm-lma-controlled-mag-params-01.txt 2016-04-13 17:15:53.213810654 -0700 @@ -1,24 +1,24 @@ DMM WG D. Patki Internet-Draft S. Gundavelli Intended status: Standards Track Cisco -Expires: June 18, 2016 J. Lee +Expires: October 15, 2016 J. Lee Sangmyung University Q. Fu China Mobile L. Bertz Sprint - December 16, 2015 + April 13, 2016 LMA Controlled MAG Session Parameters - draft-ietf-dmm-lma-controlled-mag-params-00.txt + draft-ietf-dmm-lma-controlled-mag-params-01.txt Abstract This specification defines a new extension, LMA-Controlled-MAG- 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 parameters contained in this extension. Status of this Memo @@ -28,25 +28,25 @@ Internet-Drafts are working documents of the Internet Engineering 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 and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." - This Internet-Draft will expire on June 18, 2016. + This Internet-Draft will expire on October 15, 2016. Copyright Notice - Copyright (c) 2015 IETF Trust and the persons identified as the + Copyright (c) 2016 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as @@ -106,22 +106,22 @@ 3. Protocol Extension The LMA Controlled MAG Parameters (LCMP) option is a mobility header option used to exchange information related to the parameters that a local mobility anchor enforces on a mobile access gateway. The option can be included in Proxy Binding Acknowledgement (PBA) message only, and there MUST NOT be more than a single instance of this mobility option in a mobility message. This mobility option MUST contain one or more LMA Controlled MAG Parameters sub-options. The - suboptions are defined in Section 3.1. The alignment requirement for - this option is 4n [RFC2460]. + suboptions are defined in Section 3.1. The alignment of this option + MUST be 4n [RFC2460]. 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 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Type | Length | Reserved | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | ... LCMP Sub-option(s) ... ~ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Figure 1: LMA Controlled MAG Parameters Option @@ -133,36 +133,39 @@ Length 8-bit unsigned integer indicating the length in octets of the option, excluding the Type and Length fields. Reserved MUST be set to zero when sending and ignored when received. + LCMP Sub-option(s) + + LCMP Sub-options are described in the below sections. The sub- + options are optional and can be present in any order. + 3.1. Format of the LCMP Sub-Options The LMA Controlled MAG Parameters sub-options are used for carrying information elements related to various parameters that need to be configured on the MAG. These sub-options can be included in the LMA - Controlled MAG Parameters option defined in Section 3. The format of - this sub-option is as follows. The alignment requirement for the - sub-option is 4n. The sub-options are optional and can be present in - any order. + Controlled MAG Parameters option defined in Section 3. The alignment + of the sub-option MUST be 4n. The format of this sub-option is as + follows. 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 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | LCMP Type | LCMP Length | Sub-Option Data ~ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ - Figure 2: LMA Controlled MAG Parameters Sub-Option Type 8-bit unsigned integer indicating the type of the LMA Controlled MAG Parameters sub-option. This specification defines the following types: 0 - Reserved @@ -249,39 +252,39 @@ configured by the system management. The configured values for these protocol variables MUST survive server reboots and service restarts. EnableLCMPSubOptReregControl This flag indicates the operational state of the Binding Re- registration Control sub-option support. The default value for this flag is set to (0), indicating that support for the Binding Re-registration Control sub-option is disabled. - When this flag on the mobile access gateway is set to a value of + 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 SHOULD NOT include the sub-option. + 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 This flag indicates the operational state of the Heartbeat Control sub-option support. The default value for this flag is set to (0), indicating that support for the Heartbeat Control sub-option is disabled. - When this flag on the mobile access gateway is set to a value of + 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 SHOULD NOT include the sub-option. + access gateway; otherwise, it MUST NOT include the sub-option. 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 hierarchy. @@ -312,21 +315,21 @@ successful heartbeat exchange (request followed by response) when the next heartbeat exchange can be triggered. The default value is 60 seconds. It SHOULD NOT be set to less than 30 seconds or more than 3600 seconds. The value of this variable MAY be derived from the variable HEARTBEAT_INTERVAL defined in Section 5 of [RFC5847] if defined on the local mobility anchor. LCMPHeartbeatRetransmissionDelay 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 value is 5 seconds. LCMPHeartbeatMaxRetransmissions This variable is used to set the maximum number of heartbeat retransmissions. The default value for this variable is 3. The value of this variable MAY be derived from the variable MISSING_HEARTBEATS_ALLOWED defined in Section 5 of [RFC5847] if defined on the local mobility anchor.