Internet Engineering Task Force (IETF)                          D. Patki
Request for Comments: 8127                                 S. Gundavelli
Category: Standards Track                                          Cisco
ISSN: 2070-1721                                                   J. Lee
                                                    Sangmyung University
                                                                   Q. Fu
                                                            China Mobile
                                                                L. Bertz
                                                                  Sprint
                                                             August 2017
        
Internet Engineering Task Force (IETF)                          D. Patki
Request for Comments: 8127                                 S. Gundavelli
Category: Standards Track                                          Cisco
ISSN: 2070-1721                                                   J. Lee
                                                    Sangmyung University
                                                                   Q. Fu
                                                            China Mobile
                                                                L. Bertz
                                                                  Sprint
                                                             August 2017
        

Mobile Access Gateway Configuration Parameters Controlled by the Local Mobility Anchor

由本地移动锚控制的移动接入网关配置参数

Abstract

摘要

This specification defines a new extension, LMA-Controlled-MAG-Session-Params, to Proxy Mobile IPv6. This option can be used by the local mobility anchor (LMA) in a Proxy Mobile IPv6 domain for signaling a mobile access gateway (MAG) on enforcing specific values for various configuration parameters such as heartbeat and binding refresh parameters.

该规范定义了一个新的扩展,LMA控制的MAG会话参数,用于代理移动IPv6。该选项可由代理移动IPv6域中的本地移动锚(LMA)使用,用于向移动接入网关(MAG)发送信号,以强制执行各种配置参数(例如心跳和绑定刷新参数)的特定值。

Status of This Memo

关于下段备忘

This is an Internet Standards Track document.

这是一份互联网标准跟踪文件。

This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 7841.

本文件是互联网工程任务组(IETF)的产品。它代表了IETF社区的共识。它已经接受了公众审查,并已被互联网工程指导小组(IESG)批准出版。有关互联网标准的更多信息,请参见RFC 7841第2节。

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.

有关本文件当前状态、任何勘误表以及如何提供反馈的信息,请访问http://www.rfc-editor.org/info/rfc8127.

Copyright Notice

版权公告

Copyright (c) 2017 IETF Trust and the persons identified as the document authors. All rights reserved.

版权所有(c)2017 IETF信托基金和确定为文件作者的人员。版权所有。

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 described in the Simplified BSD License.

本文件受BCP 78和IETF信托有关IETF文件的法律规定的约束(http://trustee.ietf.org/license-info)自本文件出版之日起生效。请仔细阅读这些文件,因为它们描述了您对本文件的权利和限制。从本文件中提取的代码组件必须包括信托法律条款第4.e节中所述的简化BSD许可证文本,并提供简化BSD许可证中所述的无担保。

Table of Contents

目录

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Conventions and Terminology . . . . . . . . . . . . . . . . .   3
     2.1.  Conventions . . . . . . . . . . . . . . . . . . . . . . .   3
     2.2.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Protocol Extension  . . . . . . . . . . . . . . . . . . . . .   4
     3.1.  Format of the LCMP Sub-Options  . . . . . . . . . . . . .   5
       3.1.1.  Binding Re-registration Control Sub-Option  . . . . .   6
       3.1.2.  Heartbeat Control Sub-Option  . . . . . . . . . . . .   7
   4.  Protocol Configuration Variables  . . . . . . . . . . . . . .   8
     4.1.  Local Mobility Anchor -- Configuration Variables  . . . .   8
   5.  Protocol Considerations . . . . . . . . . . . . . . . . . . .   9
     5.1.  Local Mobility Anchor Considerations  . . . . . . . . . .  10
     5.2.  Mobile Access Gateway Considerations  . . . . . . . . . .  10
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  11
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .  11
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  12
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .  12
     8.2.  Informative References  . . . . . . . . . . . . . . . . .  12
   Acknowledgements  . . . . . . . . . . . . . . . . . . . . . . . .  13
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  14
        
   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Conventions and Terminology . . . . . . . . . . . . . . . . .   3
     2.1.  Conventions . . . . . . . . . . . . . . . . . . . . . . .   3
     2.2.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Protocol Extension  . . . . . . . . . . . . . . . . . . . . .   4
     3.1.  Format of the LCMP Sub-Options  . . . . . . . . . . . . .   5
       3.1.1.  Binding Re-registration Control Sub-Option  . . . . .   6
       3.1.2.  Heartbeat Control Sub-Option  . . . . . . . . . . . .   7
   4.  Protocol Configuration Variables  . . . . . . . . . . . . . .   8
     4.1.  Local Mobility Anchor -- Configuration Variables  . . . .   8
   5.  Protocol Considerations . . . . . . . . . . . . . . . . . . .   9
     5.1.  Local Mobility Anchor Considerations  . . . . . . . . . .  10
     5.2.  Mobile Access Gateway Considerations  . . . . . . . . . .  10
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  11
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .  11
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  12
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .  12
     8.2.  Informative References  . . . . . . . . . . . . . . . . .  12
   Acknowledgements  . . . . . . . . . . . . . . . . . . . . . . . .  13
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  14
        
1. Introduction
1. 介绍

A large Proxy Mobile IPv6 (PMIPv6) [RFC5213] deployment, such as residential deployment, can have tens of thousands of mobile access gateways (MAGs) spread across geographical locations. While it can be operationally challenging to manage such a large number of MAGs, it can also be very difficult to ensure configuration consistency across all the MAGs if they are not centrally managed. Configuring aggressive values of parameters such as re-registration timeout and heartbeat interval can potentially create considerable signaling load on the local mobility anchor (LMA). This document provides a new option to enable the LMA to control various parameters on the MAG such as the re-registration frequency [RFC5213] and heartbeat frequency [RFC5847]. With this option, the configuration of these tunable parameters enforced centrally from the LMA enables Service Providers to have better control on the behavior of the MAGs with deterministic signaling load on the LMA.

大型代理移动IPv6(PMIPv6)[RFC5213]部署(如住宅部署)可以在地理位置上分布数万个移动访问网关(MAG)。虽然管理如此大量的MAG在操作上可能具有挑战性,但如果没有集中管理,则也很难确保所有MAG之间的配置一致性。配置积极的参数值,如重新注册超时和心跳间隔,可能会在本地移动锚(LMA)上产生相当大的信令负载。本文档提供了一个新选项,使LMA能够控制MAG上的各种参数,如重新注册频率[RFC5213]和心跳频率[RFC5847]。通过该选项,这些可调参数的配置从LMA集中实施,使得服务提供商能够在LMA上具有确定性信令负载的情况下更好地控制mag的行为。

2. Conventions and Terminology
2. 公约和术语
2.1. Conventions
2.1. 习俗

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "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.

本文件中的关键词“必须”、“不得”、“必需”、“应”、“不应”、“建议”、“不建议”、“可”和“可选”在所有大写字母出现时(如图所示)应按照BCP 14[RFC2119][RFC8174]所述进行解释。

2.2. Terminology
2.2. 术语

All the terms used in this document are to be interpreted as defined in [RFC5213], [RFC5847], and [RFC7563].

本文件中使用的所有术语应按照[RFC5213]、[RFC5847]和[RFC7563]中的定义进行解释。

3. Protocol Extension
3. 协议扩展

The LMA-Controlled MAG Parameters (LCMPs) option is a mobility header option used to exchange information related to the parameters that an LMA enforces on a MAG. This option can be included only in the Proxy Binding Acknowledge (PBA) message, and there MUST NOT be more than a single instance of this mobility option in a given PBA message. This option MUST contain one or more LCMP sub-options. Each LCMP sub-option carries a specific configuration parameter. The sub-options are defined in Section 3.1. The LCMP option has an alignment requirement of 4n+2 [RFC8200].

LMA控制的MAG参数(LCMPs)选项是一个移动报头选项,用于交换与LMA对MAG强制执行的参数相关的信息。此选项只能包含在代理绑定确认(PBA)消息中,并且在给定PBA消息中,此移动选项的实例不得超过一个。此选项必须包含一个或多个LCMP子选项。每个LCMP子选项都带有一个特定的配置参数。子选项在第3.1节中定义。LCMP选项的对准要求为4n+2[RFC8200]。

    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      |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                     LCMP Sub-Option(s)                        ~
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
        
    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      |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                     LCMP Sub-Option(s)                        ~
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
        

Figure 1: LMA-Controlled MAG Parameters Option

图1:LMA控制的MAG参数选项

Type

类型

MUST be set to the value of 62, indicating that it is an LMA-Controlled-MAG-Parameters option.

必须设置为值62,表示它是LMA控制的MAG参数选项。

Length

8-bit unsigned integer indicating the length in octets of the option, excluding the Type and Length fields.

8位无符号整数,表示选项的长度(以八位字节为单位),不包括类型和长度字段。

LCMP Sub-Option(s)

LCMP子选项

LCMP sub-options are described in the sections below. The sub-options can be present in any order. Inclusion of any specific sub-option is optional, but at least one sub-option MUST be present.

LCMP子选项在以下章节中描述。子选项可以以任何顺序出现。包含任何特定子选项都是可选的,但必须至少存在一个子选项。

3.1. Format of the LCMP Sub-Options
3.1. LCMP子选项的格式

The LCMP 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 LCMP option defined in Section 3. The LCMP sub-options have an alignment requirement of 4n. The format of this sub-option is as follows.

LCMP子选项用于携带与需要在MAG上配置的各种参数相关的信息元素。这些子选项可包含在第3节中定义的LCMP选项中。LCMP子选项的对齐要求为4n。此子选项的格式如下所示。

    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         ~
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
        
    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

图2:LMA控制的MAG参数子选项

Type

类型

8-bit unsigned integer indicating the type of the LCMP sub-option. This specification defines the following types:

8位无符号整数,指示LCMP子选项的类型。本规范定义了以下类型:

0 - Reserved

0-保留

1 - Binding Re-registration Control Sub-Option

1-绑定重新注册控制子选项

2 - Heartbeat Control Sub-Option

2-心跳控制子选项

Length

8-bit unsigned integer indicating the number of octets needed to encode the Option Data, excluding the LCMP Type and LCMP Length fields of the sub-option.

8位无符号整数,指示编码选项数据所需的八位字节数,不包括子选项的LCMP类型和LCMP长度字段。

3.1.1. Binding Re-registration Control Sub-Option
3.1.1. 绑定重新注册控制子选项

The Binding Re-registration Control Sub-Option is a mobility sub-option carried in the LCMP mobility option defined in Section 3. This sub-option carries timer values related to re-registration. There MUST be no more than a single instance of this sub-option in the LCMP option. The format of this sub-option is defined below.

绑定重新注册控制子选项是第3节定义的LCMP移动性选项中包含的移动性子选项。此子选项包含与重新注册相关的计时器值。LCMP选项中此子选项的实例不得超过一个。此子选项的格式定义如下。

    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 = 1 |  LCMP Length  |  Re-registration-Start-Time   |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |  Initial-Retransmission-Time  | Maximum-Retransmission-Time   |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
        
    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 = 1 |  LCMP Length  |  Re-registration-Start-Time   |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |  Initial-Retransmission-Time  | Maximum-Retransmission-Time   |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
        

Figure 3: Binding Re-registration Control Sub-Option

图3:绑定重新注册控制子选项

LCMP Type

LCMP型

1 for the Binding Re-registration Control Sub-Option.

1用于绑定重新注册控制子选项。

LCMP Length

LCMP长度

6

6.

Re-registration-Start-Time

重新注册开始时间

16-bit unsigned integer indicating the number of time units before the expiry of the PMIPv6 binding lifetime when the registration refresh process needs to be activated. One time unit is 4 seconds.

16位无符号整数,表示需要激活注册刷新过程时PMIPv6绑定生存期到期前的时间单位数。一个时间单位是4秒。

Initial-Retransmission-Time

初始重传时间

16-bit unsigned integer indicating minimum delay in seconds before the first Proxy Binding Update (PBU) retransmission of the exponential backoff process.

16位无符号整数,表示指数退避过程的第一次代理绑定更新(PBU)重传之前的最小延迟(秒)。

Maximum-Retransmission-Time

最大重传时间

16-bit unsigned integer indicating maximum delay in seconds before the last PBU retransmission message of the exponential backoff process.

16位无符号整数,表示指数退避过程的最后一条PBU重传消息之前的最大延迟(秒)。

3.1.2. Heartbeat Control Sub-Option
3.1.2. 心跳控制子选项
    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 = 2 |  LCMP Length  |        HB-Interval            |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |    HB-Retransmission-Delay    |    HB-Max-Retransmissions     |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
        
    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 = 2 |  LCMP Length  |        HB-Interval            |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |    HB-Retransmission-Delay    |    HB-Max-Retransmissions     |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
        

Figure 4: Heartbeat Control Sub-Option

图4:心跳控制子选项

LCMP Type

LCMP型

2 for the Heartbeat Control Sub-Option.

2用于心跳控制子选项。

LCMP Length

LCMP长度

6

6.

HB-Interval

血红蛋白间期

16-bit unsigned integer indicating the heartbeat interval, i.e., time delay in seconds after a successful heartbeat exchange (heartbeat request followed by response) when the next heartbeat exchange can be triggered.

16位无符号整数,指示心跳间隔,即成功的心跳交换(心跳请求后接响应)后的时间延迟(秒),此时可以触发下一次心跳交换。

HB-Retransmission-Delay

重传延迟

16-bit unsigned integer indicating minimum time delay in seconds before a heartbeat message is retransmitted.

16位无符号整数,表示重新传输心跳消息之前的最小时间延迟(秒)。

HB-Max-Retransmissions

HB最大重传

16-bit unsigned integer indicating maximum number of heartbeat retransmissions.

16位无符号整数,表示心跳信号重新传输的最大次数。

4. Protocol Configuration Variables
4. 协议配置变量
4.1. Local Mobility Anchor -- Configuration Variables
4.1. 本地移动性锚——配置变量

This specification defines the following variables to be configured by the system management. The configured values for these protocol variables MUST survive server reboots and service restarts.

本规范定义了系统管理层要配置的以下变量。这些协议变量的配置值必须在服务器重新启动和服务重新启动后仍然有效。

EnableLCMPSubOptReregControl

启用LCMPSuboptreRegControl

This flag indicates the operational state of the Binding Re-registration Control Sub-Option support. The default value of this flag is (0), indicating that support for the Binding Re-registration Control Sub-Option is disabled.

此标志指示绑定重新注册控制子选项支持的操作状态。此标志的默认值为(0),表示已禁用对绑定重新注册控制子选项的支持。

   EnableLCMPSubOptHeartbeatControl
        
   EnableLCMPSubOptHeartbeatControl
        

This flag indicates the operational state of the Heartbeat Control Sub-Option support. The default value of this flag is (0), indicating that support for the Heartbeat Control Sub-Option is disabled.

此标志指示心跳控制子选项支持的操作状态。此标志的默认值为(0),表示已禁用对心跳控制子选项的支持。

The following variables MAY be defined at various granularities such as per binding, per cluster of bindings, per peering MAG, per cluster of peering MAGs, or any other custom grouping. Regardless of the granularity of this configuration, the LMA MUST be able to determine the value of these variables for every individual binding.

以下变量可以按不同粒度定义,例如按绑定、按绑定集群、按对等MAG、按对等MAG集群或任何其他自定义分组。无论这种配置的粒度如何,LMA都必须能够为每个单独的绑定确定这些变量的值。

LCMPReregistrationStartTime

LCMPReregistrationStartTime

This variable is used to set the minimum time interval in number of seconds before the expiry of the PMIPv6 binding lifetime when the registration refresh process SHOULD be activated. The default value of this variable is 10 units, where each unit is 4 seconds.

此变量用于设置应激活注册刷新过程时PMIPv6绑定生存期到期前的最小时间间隔(以秒为单位)。此变量的默认值为10个单位,其中每个单位为4秒。

LCMPInitialRetransmissionTime

LCM初始重传时间

This variable is used to set the minimum delay in seconds before the first PBU retransmission of the exponential backoff process. This variable is the same as INITIAL_BINDACK_TIMEOUT mentioned in Section 6.9.4 of [RFC5213]. The default value of this variable is 1 second.

此变量用于在指数退避过程的第一次PBU重传之前设置最小延迟(秒)。该变量与[RFC5213]第6.9.4节中提到的初始_BINDACK_超时相同。此变量的默认值为1秒。

LCMPMaximumRetransmissionTime

LCMPMaximumRetransmissionTime

This variable is used to set the maximum delay in seconds before the last PBU retransmission message of the exponential backoff process. This variable is the same as MAX_BINDACK_TIMEOUT mentioned in Section 6.9.4 of [RFC5213]. The default value of this variable is 32 seconds.

此变量用于设置指数退避过程的最后一条PBU重传消息之前的最大延迟(秒)。该变量与[RFC5213]第6.9.4节中提到的MAX_BINDACK_TIMEOUT相同。此变量的默认值为32秒。

LCMPHeartbeatInterval

立法会九题

This variable is used to set the time delay in seconds after a successful heartbeat exchange (heartbeat request followed by response) when the next heartbeat exchange can be triggered. The default value of this variable is 60 seconds. The time delay SHOULD NOT be 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 configured on the LMA.

此变量用于设置成功的心跳交换(心跳请求后接响应)后可触发下一次心跳交换的时间延迟(秒)。此变量的默认值为60秒。延时不应小于30秒或大于3600秒。如果在LMA上配置,该变量的值可以从[RFC5847]第5节中定义的变量HEARTBEAT_INTERVAL中导出。

   LCMPHeartbeatRetransmissionDelay
        
   LCMPHeartbeatRetransmissionDelay
        

This variable is used to set the minimum time delay in seconds before a heartbeat message is retransmitted. The value of this variable SHOULD be less than LCMPHeartbeatInterval. The default value of this variable is 5 seconds.

此变量用于设置重新传输心跳消息之前的最小时间延迟(以秒为单位)。此变量的值应小于LCMPHeartbeatInterval。此变量的默认值为5秒。

LCMPHeartbeatMaxRetransmissions

立法会三题:重发

This variable is used to set the maximum number of heartbeat retransmissions. The default value of 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 configured on the LMA.

此变量用于设置心跳重新传输的最大次数。此变量的默认值为3。如果在LMA上配置,该变量的值可以从[RFC5847]第5节中定义的缺少\u心跳\u的变量中导出。

5. Protocol Considerations
5. 议定书考虑事项

The following considerations apply to the LMA and the MAG.

以下注意事项适用于LMA和MAG。

For supporting this extension, the conceptual Binding Cache Entry data structure maintained by the LMA, described in Section 5.1 of [RFC5213], and the conceptual Binding Update List entry data structure maintained by the MAG, described in Section 6.1 of [RFC5213], need to be extended to store the information elements related to the LCMP option that are defined below.

为了支持此扩展,LMA维护的概念绑定缓存条目数据结构(如[RFC5213]第5.1节所述)和MAG维护的概念绑定更新列表条目数据结构(如[RFC5213]第6.1节所述),需要扩展以存储与下面定义的LCMP选项相关的信息元素。

o LCMPReregistrationStartTime

o LCMPReregistrationStartTime

o LCMPInitialRetransmissionTime

o LCM初始重传时间

o LCMPMaximumRetransmissionTime

o LCMPMaximumRetransmissionTime

o LCMPHeartbeatInterval

o 立法会九题

o LCMPHeartbeatRetransmissionDelay

o LCMPHeartBeat重传播放

o LCMPHeartbeatMaxRetransmissions

o 立法会三题:重发

5.1. Local Mobility Anchor Considerations
5.1. 局部机动性考虑因素

On receiving a PBU message [RFC5213] from a MAG, the LMA MUST check if the variable EnableLCMPSubOptReregControl is configured and set to (1). If yes, and if LCMPReregistrationStartTime, LCMPInitialRetransmissionTime, and LCMPMaximumRetransmissionTime are all set to NON_ZERO values, then it MUST include the Binding Re-registration Control Sub-Option in the LCMP mobility option, which is in turn included in the PBA message. If the variable EnableLCMPSubOptReregControl is configured and set to (1), and if any of LCMPReregistrationStartTime, LCMPInitialRetransmissionTime, and LCMPMaximumRetransmissionTime 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].

从MAG接收PBU消息[RFC5213]时,LMA必须检查变量EnableLCMPSubOptReregControl是否已配置并设置为(1)。如果是,并且如果LCMPReregistrationStartTime、LCMPInitialRetransmissionTime和LCMPMaximumRetransmissionTime都设置为非零值,则它必须在LCMP移动选项中包含绑定重新注册控制子选项,该选项又包含在PBA消息中。如果变量EnableLCMPSubOptReregControl配置并设置为(1),并且如果LCMPReregistrationStartTime、LCMPInitialRetransmissionTime和LCMPMaximumRetransmissionTime中的任何一个设置为零值,然后,LMA必须报告配置错误,并通过发送状态代码为“128-原因未指定”的PBA消息来拒绝绑定请求[RFC5213]。

The LMA MUST also check if variable EnableLCMPSubOptHeartbeatControl is configured and set to (1). If yes, and if LCMPHeartbeatInterval, LCMPHeartbeatRetransmissionDelay, and LCMPHeartbeatMaxRetransmissions are all set to NON_ZERO values, then it MUST include the 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].

LMA还必须检查变量EnableLCMPSubOptHeartbeatControl是否已配置并设置为(1)。如果是,并且如果LCMPHeartbeatInterval、LCMPHeartbeatRetransmissionDelay和LCMPHeartbeatMaxRetransmissions都设置为非零值,则必须在LCMP移动性选项中包含心跳控制子选项,该子选项又包含在PBA消息中。如果变量EnableLCMPSubOptHeartbeatControl设置为(1),并且如果LCMPHeartbeatInterval、LCMPHeartbeatRetransmissionDelay和LCMPHeartbeatMaxRetransmissions中的任何一个设置为零值,则LMA必须报告配置错误,并通过发送状态代码为“128-未指定原因”的PBA消息来拒绝绑定请求[RFC5213].

5.2. Mobile Access Gateway Considerations
5.2. 移动接入网关注意事项

If the PBA message [RFC5213] received from the LMA contains the LCMP mobility option and the Binding Re-registration Control Sub-Option, then the MAG MUST overwrite the timer parameters related to binding re-registration that are configured locally on the MAG with the parameters received in the Binding Re-registration Control Sub-Option. If any of the parameters in the Binding Re-registration Control Sub-Option are ZERO, then the PBA message MUST be ignored and an error message SHOULD be logged.

如果从LMA接收的PBA消息[RFC5213]包含LCMP移动选项和绑定重新注册控制子选项,则MAG必须使用绑定重新注册控制子选项中接收的参数覆盖与绑定重新注册相关的计时器参数,这些参数在MAG上本地配置。如果绑定重新注册控制子选项中的任何参数为零,则必须忽略PBA消息并记录错误消息。

Similarly, if the LCMP mobility option contains the Heartbeat Control Sub-Option, then the MAG MUST overwrite the heartbeat-related timer 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, are ZERO, then the PBA message MUST be ignored and an error message SHOULD be logged.

类似地,如果LCMP移动选项包含心跳控制子选项,则MAG必须使用心跳控制子选项中接收的参数覆盖MAG上本地配置的心跳相关计时器参数。如果心跳控制子选项中的任何参数(HB重新传输延迟除外)为零,则必须忽略PBA消息,并记录错误消息。

6. IANA Considerations
6. IANA考虑

IANA has updated the "Mobile IPv6 parameters" registry as described here.

IANA已更新了“移动IPv6参数”注册表,如下所述。

o Action 1: This specification defines a new mobility header option, "LMA-Controlled MAG Parameters". This mobility option is described in Section 3. The type value 62 has been assigned for this option in the "Mobility Options" registry, as defined in [RFC6275].

o 行动1:本规范定义了一个新的移动报头选项“LMA控制的MAG参数”。第3节介绍了该移动性选项。根据[RFC6275]中的定义,已在“移动选项”注册表中为该选项分配了类型值62。

o Action 2: This specification defines a new mobility sub-option format, the LCMP sub-option. The format of this mobility sub-option is described in Section 3.1. This sub-option can be carried in the LCMP option. The type values for this sub-option are managed by IANA, under the "LMA-Controlled MAG Parameters Sub-Option Type Values" registry. Per this document, IANA has reserved the following type values. Approval of new LCMP sub-option type values are to be made through Expert Review [RFC8126].

o 措施2:本规范定义了一种新的移动性子选项格式,即LCMP子选项。第3.1节描述了该移动性子选项的格式。此子选项可在LCMP选项中携带。此子选项的类型值由IANA在“LMA控制的MAG参数子选项类型值”注册表下管理。根据本文档,IANA保留了以下类型值。新LCMP子选项类型值的批准将通过专家评审[RFC8126]进行。

      +---+-----------------------------------------------------+
      | 0 | Reserved                                            |
      +---+-----------------------------------------------------+
      | 1 | Binding Re-registration Control Sub-Option          |
      +---+-----------------------------------------------------+
      | 2 | Heartbeat Control Sub-Option                        |
      +---+-----------------------------------------------------+
        
      +---+-----------------------------------------------------+
      | 0 | Reserved                                            |
      +---+-----------------------------------------------------+
      | 1 | Binding Re-registration Control Sub-Option          |
      +---+-----------------------------------------------------+
      | 2 | Heartbeat Control Sub-Option                        |
      +---+-----------------------------------------------------+
        
7. Security Considerations
7. 安全考虑

The LCMP option defined in this specification allows the configuration of re-registration and heartbeat frequencies. This option is defined for carrying it in Proxy Binding Update and Proxy Binding Acknowledgement messages. This option is carried like any other mobility header option as specified and does not require any special security considerations.

本规范中定义的LCMP选项允许配置重新注册和心跳频率。此选项定义为在代理绑定更新和代理绑定确认消息中携带它。此选项与指定的任何其他移动标头选项一样,不需要任何特殊的安全考虑。

8. References
8. 工具书类
8.1. Normative References
8.1. 规范性引用文件

[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997, <https://www.rfc-editor.org/info/rfc2119>.

[RFC2119]Bradner,S.,“RFC中用于表示需求水平的关键词”,BCP 14,RFC 2119,DOI 10.17487/RFC2119,1997年3月<https://www.rfc-editor.org/info/rfc2119>.

[RFC5213] Gundavelli, S., Ed., Leung, K., Devarapalli, V., Chowdhury, K., and B. Patil, "Proxy Mobile IPv6", RFC 5213, DOI 10.17487/RFC5213, August 2008, <https://www.rfc-editor.org/info/rfc5213>.

[RFC5213]Gundavelli,S.,Ed.,Leung,K.,Devarapalli,V.,Chowdhury,K.,和B.Patil,“代理移动IPv6”,RFC 5213,DOI 10.17487/RFC5213,2008年8月<https://www.rfc-editor.org/info/rfc5213>.

[RFC5847] Devarapalli, V., Ed., Koodli, R., Ed., Lim, H., Kant, N., Krishnan, S., and J. Laganier, "Heartbeat Mechanism for Proxy Mobile IPv6", RFC 5847, DOI 10.17487/RFC5847, June 2010, <https://www.rfc-editor.org/info/rfc5847>.

[RFC5847]Devarapalli,V.,Ed.,Koodli,R.,Ed.,Lim,H.,Kant,N.,Krishnan,S.,和J.Laganier,“代理移动IPv6的心跳机制”,RFC 5847,DOI 10.17487/RFC5847,2010年6月<https://www.rfc-editor.org/info/rfc5847>.

[RFC7563] Pazhyannur, R., Speicher, S., Gundavelli, S., Korhonen, J., and J. Kaippallimalil, "Extensions to the Proxy Mobile IPv6 (PMIPv6) Access Network Identifier Option", RFC 7563, DOI 10.17487/RFC7563, June 2015, <https://www.rfc-editor.org/info/rfc7563>.

[RFC7563]Pazhyannur,R.,Speicher,S.,Gundavelli,S.,Korhonen,J.,和J.Kaippallimalil,“代理移动IPv6(PMIPv6)接入网络标识符选项的扩展”,RFC 7563,DOI 10.17487/RFC7563,2015年6月<https://www.rfc-editor.org/info/rfc7563>.

[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>.

[RFC8174]Leiba,B.,“RFC 2119关键词中大写与小写的歧义”,BCP 14,RFC 8174,DOI 10.17487/RFC8174,2017年5月<https://www.rfc-editor.org/info/rfc8174>.

8.2. Informative References
8.2. 资料性引用

[RFC6275] Perkins, C., Ed., Johnson, D., and J. Arkko, "Mobility Support in IPv6", RFC 6275, DOI 10.17487/RFC6275, July 2011, <https://www.rfc-editor.org/info/rfc6275>.

[RFC6275]Perkins,C.,Ed.,Johnson,D.,和J.Arkko,“IPv6中的移动支持”,RFC 6275,DOI 10.17487/RFC6275,2011年7月<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>.

[RFC8126]Cotton,M.,Leiba,B.,和T.Narten,“在RFC中编写IANA考虑事项部分的指南”,BCP 26,RFC 8126,DOI 10.17487/RFC8126,2017年6月<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>.

[RFC8200]Deering,S.和R.Hinden,“互联网协议,第6版(IPv6)规范”,STD 86,RFC 8200,DOI 10.17487/RFC8200,2017年7月<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.

作者感谢DMM工作组对本文件的所有评论和讨论。作者还要感谢Suresh Krishnan、Ralph Droms、Mirja Kuhlewind、Alexey Melnikov和Ben Campbell的评论反馈。

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.

李钟赫的工作得到了韩国科学、信息通信技术和未来规划部的“跨部Giga韩国项目”资助。

Authors' Addresses

作者地址

Dhananjay Patki Cisco Cessna Business Park SEZ, Kadubeesanahalli Bangalore, Karnataka 560087 India

印度卡纳塔克邦班加罗尔卡杜比萨纳哈利经济特区达南杰·帕奇思科塞斯纳商业园560087

   Email: dhpatki@cisco.com
        
   Email: dhpatki@cisco.com
        

Sri Gundavelli Cisco 170 West Tasman Drive San Jose, CA 95134 United States of America

美国加利福尼亚州圣何塞市西塔斯曼大道170号,邮编95134

   Email: sgundave@cisco.com
        
   Email: sgundave@cisco.com
        

Jong-Hyouk Lee Sangmyung University 31, Sangmyeongdae-gil, Dongnam-gu Cheonan 31066 Republic of Korea

韩国东南固天安省三明大吉31号郑孝利三明大学31066

   Email: jonghyouk@smu.ac.kr
        
   Email: jonghyouk@smu.ac.kr
        

Qiao Fu China Mobile Xuanwumenxi Ave. No.32 Beijing China

乔夫中国移动北京宣武门西大街32号

   Email: fuqiao1@outlook.com
        
   Email: fuqiao1@outlook.com
        

Lyle T. Bertz Sprint Kansas United States of America

美国堪萨斯州Lyle T.Bertz Sprint

   Email: Lyle.T.Bertz@sprint.com
        
   Email: Lyle.T.Bertz@sprint.com