draft-ietf-dmm-lma-controlled-mag-params-03.txt   draft-ietf-dmm-lma-controlled-mag-params-04.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: August 9, 2017 J. Lee Expires: September 12, 2017 J. Lee
Sangmyung University Sangmyung University
Q. Fu Q. Fu
China Mobile China Mobile
L. Bertz L. Bertz
Sprint Sprint
February 5, 2017 March 11, 2017
LMA Controlled MAG Session Parameters LMA Controlled MAG Session Parameters
draft-ietf-dmm-lma-controlled-mag-params-03.txt draft-ietf-dmm-lma-controlled-mag-params-04.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
local mobility anchor (LMA) in Proxy Mobile IPv6 (PMIPv6) signaling local mobility anchor in Proxy Mobile IPv6 signaling for notifying
for notifying the mobile access gateway (MAG) to conform to various the mobile access gateway to conform to various parameters contained
parameters contained in this extension. 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 August 9, 2017. This Internet-Draft will expire on September 12, 2017.
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
skipping to change at page 2, line 36 skipping to change at page 2, line 36
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9
7. Security Considerations . . . . . . . . . . . . . . . . . . . 10 7. Security Considerations . . . . . . . . . . . . . . . . . . . 10
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 10 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 10
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 10 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 10
9.1. Normative References . . . . . . . . . . . . . . . . . . 10 9.1. Normative References . . . . . . . . . . . . . . . . . . 10
9.2. Informative References . . . . . . . . . . . . . . . . . 11 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 Proxy Mobile IPv6 (PMIPv6) deployment, such as residential
tens of thousands of MAGs spread across geographical locations. deployment, can have tens of thousands of mobile access gateways
While it can be operationally challenging to manage such a large (MAG) spread across geographical locations. While it can be
number of MAGs, it can also be very difficult to ensure configuration operationally challenging to manage such a large number of MAGs, it
consistency across all the MAGs if they are not centrally managed. can also be very difficult to ensure configuration consistency across
Configuring aggressive values of parameters such as re-registration all the MAGs if they are not centrally managed. Configuring
timeout and heartbeat interval can potentially create considerable aggressive values of parameters such as re-registration timeout and
signaling load on the LMA. This document provides a new option to heartbeat interval can potentially create considerable signaling load
enable the LMA to control various parameters on the MAG such as the on the local mobility anchor (LMA). This document provides a new
re-registration frequency [RFC5213] and heartbeat frequency option to enable the LMA to control various parameters on the MAG
[RFC5847]. With this option, the configuration of these tunable such as the re-registration frequency [RFC5213] and heartbeat
parameters done centrally on the LMA enables Service Providers to frequency [RFC5847]. With this option, the configuration of these
have better control on the behavior of the MAGs with deterministic tunable parameters done centrally on the LMA enables Service
singaling load on the LMA. Providers to have better control on the behavior of the MAGs with
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", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in [RFC2119].
2.2. Terminology 2.2. Terminology
skipping to change at page 3, line 25 skipping to change at page 3, line 25
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
LMA enforces on a MAG. The option can be included in Proxy Binding LMA enforces on a MAG. The option can be included in Proxy Binding
Acknowledge (PBA) message only, and there MUST NOT be more than a Acknowledge (PBA) message only, 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 the PBA message. This
mobility option MUST contain one or more LCMP sub-options. The mobility option MUST contain one or more LCMP sub-options. The sub-
suboptions are defined in Section 3.1. The alignment of this option options 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 12 skipping to change at page 4, line 12
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.
Reserved Reserved
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 can be present in any order. Inclusion of any specifc
sub-option is optional, but at least one sub-option MUST be
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 alignment of the sub-option MUST be 4n. The format Section 3. The alignment of the sub-option MUST be 4n. The format
of this sub-option is as follows. of this sub-option is as follows.
0 1 2 3 0 1 2 3
skipping to change at page 4, line 37 skipping to change at page 4, line 39
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 Refresh Control Sub-Option 1 - Binding Re-registration 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
skipping to change at page 5, line 25 skipping to change at page 5, line 25
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 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 Refresh Control Sub-Option 1 for 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
skipping to change at page 12, line 16 skipping to change at page 12, line 16
31, Sangmyeongdae-gil, Dongnam-gu 31, Sangmyeongdae-gil, Dongnam-gu
Cheonan 330-720 Cheonan 330-720
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
China P.R. China
Email: fuqiao1@outlook.com Email: fuqiao1@outlook.com
Lyle T Bertz Lyle T Bertz
Sprint Sprint
Kansas Kansas
USA USA
Email: Lyle.T.Bertz@sprint.com Email: Lyle.T.Bertz@sprint.com
 End of changes. 11 change blocks. 
27 lines changed or deleted 30 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/