Internet Engineering Task Force (IETF) S. Krishnan
Request for Comments: 7077 Ericsson
Category: Standards Track S. Gundavelli
ISSN: 2070-1721 Cisco
M. Liebsch
NEC
H. Yokota
KDDI
J. Korhonen
Broadcom
November 2013
Internet Engineering Task Force (IETF) S. Krishnan
Request for Comments: 7077 Ericsson
Category: Standards Track S. Gundavelli
ISSN: 2070-1721 Cisco
M. Liebsch
NEC
H. Yokota
KDDI
J. Korhonen
Broadcom
November 2013
Update Notifications for Proxy Mobile IPv6
代理移动IPv6的更新通知
Abstract
摘要
This document specifies protocol enhancements for allowing the local mobility anchor in a Proxy Mobile IPv6 domain to asynchronously notify the mobile access gateway about changes related to a mobility session. These Update Notification messages are exchanged using a new Mobility Header message type specifically designed for this purpose.
本文档指定了协议增强功能，以允许代理移动IPv6域中的本地移动锚异步通知移动访问网关与移动会话相关的更改。这些更新通知消息使用专门为此目的设计的新移动报头消息类型进行交换。
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 5741.
本文件是互联网工程任务组（IETF）的产品。它代表了IETF社区的共识。它已经接受了公众审查，并已被互联网工程指导小组（IESG）批准出版。有关互联网标准的更多信息，请参见RFC 5741第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/rfc7077.
有关本文件当前状态、任何勘误表以及如何提供反馈的信息，请访问http://www.rfc-editor.org/info/rfc7077.
Copyright Notice
版权公告
Copyright (c) 2013 IETF Trust and the persons identified as the document authors. All rights reserved.
版权所有（c）2013 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 .....................................4
2.1. Conventions ................................................4
2.2. Terminology ................................................4
3. Notification Message - Usage Examples ...........................4
4. Message Formats .................................................5
4.1. Update Notification (UPN) ..................................5
4.2. Update Notification Acknowledgement (UPA) ..................7
5. LMA Considerations ..............................................9
5.1. Constructing the Update Notification Message ..............10
5.2. Receiving the Update Notification Acknowledgement
Message ...................................................11
6. MAG Considerations .............................................12
6.1. Receiving the Update Notification Message .................12
6.2. Constructing the Update Notification Acknowledgement
Message ...................................................15
7. Protocol Configuration Variables ...............................16
8. Security Considerations ........................................16
9. Acknowledgements ...............................................17
10. IANA Considerations ...........................................17
11. References ....................................................19
11.1. Normative References .....................................19
11.2. Informative References ...................................19
1. Introduction ....................................................3
2. Conventions and Terminology .....................................4
2.1. Conventions ................................................4
2.2. Terminology ................................................4
3. Notification Message - Usage Examples ...........................4
4. Message Formats .................................................5
4.1. Update Notification (UPN) ..................................5
4.2. Update Notification Acknowledgement (UPA) ..................7
5. LMA Considerations ..............................................9
5.1. Constructing the Update Notification Message ..............10
5.2. Receiving the Update Notification Acknowledgement
Message ...................................................11
6. MAG Considerations .............................................12
6.1. Receiving the Update Notification Message .................12
6.2. Constructing the Update Notification Acknowledgement
Message ...................................................15
7. Protocol Configuration Variables ...............................16
8. Security Considerations ........................................16
9. Acknowledgements ...............................................17
10. IANA Considerations ...........................................17
11. References ....................................................19
11.1. Normative References .....................................19
11.2. Informative References ...................................19
In some situations, there is a need for the local mobility anchor (LMA) to send asynchronous notification messages to the mobile access gateway (MAG) in the course of a mobility session. These situations include changes to mobility session parameters and policy parameters. In this context, "Asynchronous messages" is used to mean messages that are not synchronous with the Proxy Binding Update and Proxy Binding Acknowledgement messages of the base Proxy Mobile IPv6 specification [RFC5213]. The base Proxy Mobile IPv6 specification does not have a provision for sending unsolicited Update Notification messages from the local mobility anchor to the mobile access gateway.
在某些情况下，需要本地移动锚（LMA）在移动会话过程中向移动接入网关（MAG）发送异步通知消息。这些情况包括移动会话参数和策略参数的更改。在此上下文中，“异步消息”用于表示与基本代理移动IPv6规范[RFC5213]的代理绑定更新和代理绑定确认消息不同步的消息。基本代理移动IPv6规范没有规定从本地移动锚向移动接入网关发送未经请求的更新通知消息。
Proxy Mobile IPv6 [RFC5213] is a network-based mobility management protocol. It is designed to provide IP mobility management support to a mobile node without requiring the participation of the mobile node in any IP mobility-related signaling. The protocol defines two mobility management entities: the LMA and the MAG. These entities are responsible for managing IP mobility management support for a mobile node in a Proxy Mobile IPv6 domain. The setup of the mobility session is initiated by the mobile access gateway by sending a Proxy Binding Update message and acknowledged by the local mobility anchor in the Proxy Binding Acknowledgement message. Once the mobility session is set up, currently there is no mechanism for the local mobility anchor to inform the mobile access gateway about changes to the mobility session or any parameters related to the mobility session. However, there are mechanisms in the Proxy Mobile IPv6 protocol that allow a local mobility anchor to send signaling messages to the mobile access gateway asynchronously, as defined in the Proxy Mobile IPv6 Heartbeat message [RFC5847] or in the Binding Revocation message [RFC5846], but these signaling messages are designed for a very specific purpose and are not sufficient for supporting a notification framework.
代理移动IPv6[RFC5213]是一种基于网络的移动性管理协议。它被设计为向移动节点提供IP移动性管理支持，而不需要移动节点参与任何IP移动性相关信令。该协议定义了两个移动性管理实体：LMA和MAG。这些实体负责管理代理移动IPv6域中移动节点的IP移动性管理支持。移动接入网关通过发送代理绑定更新消息来启动移动会话的设置，并在代理绑定确认消息中由本地移动锚确认。一旦移动会话被建立，当前没有本地移动锚通知移动接入网关关于移动会话的改变或与移动会话相关的任何参数的机制。然而，代理移动IPv6协议中存在允许本地移动锚向移动接入网关异步发送信令消息的机制，如代理移动IPv6心跳消息[RFC5847]或绑定撤销消息[RFC5846]中所定义，但是，这些信令消息是为非常特定的目的而设计的，不足以支持通知框架。
One such scenario where such a mechanism is needed is when the local mobility anchor wants to inform the mobile access gateway that it needs to re-register the mobility session for a mobile node. It is possible to achieve a similar effect by using a short lifetime for the mobility sessions, but in several networks this results in an unacceptable, and mostly unnecessary, increase in the signaling load and overhead. A more suitable scenario would be to enable demand-based signaling from the local mobility anchor to one or more mobile access gateways. Another example is when there is a change in a QoS policy [PMIPv6-QoS], an IP flow mobility policy [PMIPv6-FLOW-MOB], or an IPv4 traffic offload policy [RFC6909] for a mobility session. In this case, the local mobility anchor wants to request that the mobile access gateway perform re-registration of the
需要这种机制的一个这样的场景是当本地移动锚想要通知移动接入网关它需要为移动节点重新注册移动会话时。通过对移动性会话使用较短的生存期可以实现类似的效果，但是在一些网络中，这导致信令负载和开销的增加是不可接受的，并且大部分是不必要的。一个更合适的场景是启用从本地移动锚到一个或多个移动接入网关的基于需求的信令。另一个示例是当移动会话的QoS策略[PMIPv6 QoS]、IP流移动策略[PMIPv6 flow MOB]或IPv4流量卸载策略[RFC6909]发生变化时。在这种情况下，本地移动性锚想要请求移动接入网关执行用户的重新注册
mobility session in order to update the policies associated with the mobility session of a mobile node.
移动会话，以更新与移动节点的移动会话相关联的策略。
This document defines a new Mobility Header message for allowing the local mobility anchor to send notification messages to the mobile access gateway and a corresponding Mobility Header message for the mobile access gateway to acknowledge the notification message. The purpose of the notification message is twofold: (1) to enable the local mobility anchor to notify the mobile access gateway about the updated session parameters and (2) to enable the local mobility anchor to request that the mobile access gateway renegotiate the session parameters.
本文档定义了一个新的移动报头消息，用于允许本地移动锚向移动接入网关发送通知消息，以及一个相应的移动报头消息，用于移动接入网关确认通知消息。通知消息的目的有两个：（1）使本地移动锚能够向移动接入网关通知更新的会话参数；（2）使本地移动锚能够请求移动接入网关重新协商会话参数。
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [RFC2119].
本文件中的关键词“必须”、“不得”、“要求”、“应”、“不应”、“应”、“不应”、“建议”、“可”和“可选”应按照RFC 2119[RFC2119]中所述进行解释。
All the mobility-related terms used in this document are to be interpreted as defined in the base Proxy Mobile IPv6 specifications [RFC5213] and [RFC5844].
本文档中使用的所有移动相关术语应按照基本代理移动IPv6规范[RFC5213]和[RFC5844]中的定义进行解释。
Use Case 1: Consider a use case where the local mobility anchor wants the mobile access gateway to re-register a specific mobility session.
用例1：考虑本地移动锚希望移动接入网关重新登记特定移动性会话的用例。
MN MAG LMA
|------>| | 1. Mobile Node Attach
| |------->| 2. Proxy Binding Update
| |<-------| 3. Proxy Binding Acknowledgement
| |========| 4. Tunnel/Route Setup
| | |
| |<-------| 5. Update Notification (FORCE-REREGISTRATION)
| |------->| 6. Update Notification Acknowledgement
| | |
| |------->| 7. Proxy Binding Update
| |<-------| 8. Proxy Binding Acknowledgement
| | |
MN MAG LMA
|------>| | 1. Mobile Node Attach
| |------->| 2. Proxy Binding Update
| |<-------| 3. Proxy Binding Acknowledgement
| |========| 4. Tunnel/Route Setup
| | |
| |<-------| 5. Update Notification (FORCE-REREGISTRATION)
| |------->| 6. Update Notification Acknowledgement
| | |
| |------->| 7. Proxy Binding Update
| |<-------| 8. Proxy Binding Acknowledgement
| | |
Figure 1: Update Notification: FORCE-REREGISTRATION
图1：更新通知：强制重新注册
Use Case 2: Consider a use case where the local mobility anchor wants to notify the mobile access gateway of the updated session parameters, for example, an updated QoS profile or an updated IPv4 offload policy.
用例2：考虑本地移动锚想要通知移动接入网关的更新的会话参数，例如更新的QoS配置文件或更新的IPv4卸载策略的使用情况。
MN MAG LMA
|------>| | 1. Mobile Node Attach
| |------->| 2. Proxy Binding Update
| |<-------| 3. Proxy Binding Acknowledgement
| |========| 4. Tunnel/Route Setup
| | |
| |<-------| 5. Update Notification
| | | (UPDATE-SESSION-PARAMETERS)
| |------->| 6. Update Notification Acknowledgement
| + | 7. MAG applies the new policy option
| | |
MN MAG LMA
|------>| | 1. Mobile Node Attach
| |------->| 2. Proxy Binding Update
| |<-------| 3. Proxy Binding Acknowledgement
| |========| 4. Tunnel/Route Setup
| | |
| |<-------| 5. Update Notification
| | | (UPDATE-SESSION-PARAMETERS)
| |------->| 6. Update Notification Acknowledgement
| + | 7. MAG applies the new policy option
| | |
Figure 2: Update Notification: UPDATE-SESSION-PARAMETERS
图2：更新通知：更新会话参数
The Update Notification is a Mobility Header message that has an MH Type value of 19. It is used by the local mobility anchor to notify the mobile access gateway that some parameters related to the mobility session have changed.
更新通知是MH Type值为19的移动报头消息。本地移动锚使用它来通知移动接入网关与移动会话相关的一些参数已经改变。
The format of the Update Notification message 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sequence # |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Notification Reason |A|D| Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
. .
. Mobility options .
. .
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sequence # |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Notification Reason |A|D| Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
. .
. Mobility options .
. .
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 3: Update Notification Message
图3：更新通知消息
Sequence Number This 16-bit unsigned integer is used by the local mobility anchor to match the received Update Notification Acknowledgement message with this Update Notification message. This Sequence Number could be a random number and can be managed under the same variable used in Proxy Mobile IPv6 signaling messages [RFC5213]. Implementations MUST ensure that there is no collision between the Sequence Numbers of all outstanding Update Notification messages at any time.
序列号本地移动锚使用此16位无符号整数将接收到的更新通知确认消息与此更新通知消息相匹配。该序列号可以是随机数，并且可以在代理移动IPv6信令消息中使用的相同变量下进行管理[RFC5213]。实现必须确保所有未完成的更新通知消息的序列号在任何时候都没有冲突。
Notification Reason This 16-bit unsigned integer indicates the Notification Reason code. This code corresponds to the reason that the local mobility anchor sent the Update Notification to the mobile access gateway. This field does not contain any structure and MUST be treated as an enumeration. The reason code can indicate a vendor-specific reason if the semantics of the Update Notification message are to be based on the attached vendor-specific options, not solely from the reason code. These attached options can be deployment specific and are not specified in this document. The following Notification Reason values are currently defined:
通知原因此16位无符号整数表示通知原因代码。该代码对应于本地移动锚向移动接入网关发送更新通知的原因。此字段不包含任何结构，必须视为枚举。如果更新通知消息的语义基于附加的特定于供应商的选项，而不仅仅是原因码，则原因码可以指示特定于供应商的原因。这些附加选项可以是特定于部署的，并且未在本文档中指定。当前定义了以下通知原因值：
(0) - Reserved This value is currently reserved and cannot be used.
(0) -保留此值当前已保留，无法使用。
(1) - FORCE-REREGISTRATION Request to re-register the session by sending a Proxy Binding Update for the mobility session.
(1) -FORCE-REREGISTRATION请求通过发送移动会话的代理绑定更新来重新注册会话。
(2) - UPDATE-SESSION-PARAMETERS Request to apply the updated session parameters obtained from the message on the mobility session.
(2) -UPDATE-SESSION-PARAMETERS请求应用从移动会话上的消息获得的更新会话参数。
(3) - VENDOR-SPECIFIC-REASON This Notification Reason is for vendor-specific use. The processing rules are to be based on the Vendor-Specific Mobility option(s) [RFC5094] present in the message.
(3) -供应商特定原因此通知原因用于供应商特定用途。处理规则基于消息中存在的供应商特定移动选项[RFC5094]。
(4) - ANI-PARAMS-REQUESTED Request to send currently known Access Network Identifier (ANI) [RFC6757] parameters for the mobility session.
(4) -ANI-PARAMS-请求发送移动会话当前已知接入网络标识符（ANI）[RFC6757]参数的请求。
(255) - Reserved This value is currently reserved and cannot be used.
（255）-保留此值当前为保留值，无法使用。
Acknowledgement Requested Flag ((A) Flag) When this flag is set to a value of (1), it is an indication that the local mobility anchor is requesting that the mobile access gateway send an Update Notification Acknowledgement message. When this flag is set to a value of (0), it is an indication that the local mobility anchor is not requesting any Update Notification Acknowledgement messages.
确认请求标志（（A）标志）当该标志设置为值（1）时，表示本地移动锚正在请求移动接入网关发送更新通知确认消息。当该标志设置为值（0）时，表示本地移动锚没有请求任何更新通知确认消息。
Retransmit Flag ((D) Flag) When this flag is set to a value of (1), it is an indication that the message is a retransmitted message and has the same Sequence Number and other message contents as in the previously sent message. The (D) flag is set for retransmitted request messages, to aid the reliable detection of duplicate requests at the receiver of the request message. It is set when originating requests that have not yet been acknowledged, as an indication of a possible duplicate due to a retransmission. This flag MUST be cleared when sending a request for the first time for a given Sequence Number; otherwise, the sender MUST set this flag.
重传标志（（D）标志）当该标志设置为（1）值时，表示该消息是重传消息，并且具有与先前发送的消息相同的序列号和其他消息内容。为重新传输的请求消息设置（D）标志，以帮助在请求消息的接收器处可靠地检测重复请求。它在发起尚未确认的请求时设置，作为由于重新传输而可能出现重复的指示。首次发送给定序列号的请求时，必须清除此标志；否则，发送方必须设置此标志。
Reserved This field is unused for now. The value MUST be initialized to 0 by the sender and MUST be ignored by the receiver.
保留此字段目前未使用。发送方必须将该值初始化为0，接收方必须忽略该值。
Mobility Options This variable-length field is of such length that the complete Mobility Header is an integer multiple of 8 octets long; the Pad1 and PadN options [RFC6275] can be used for padding. This field contains zero or more TLV-encoded mobility options. Any of the Mobility Header options, including Vendor-Specific Mobility options [RFC5094], can be included here. The receiver MUST ignore and skip any options that it does not understand. These mobility options are used by the mobile access gateway to identify the specific binding for which the Update Notification message is sent.
移动性选项该可变长度字段的长度使得完整移动性报头是8个八位字节长的整数倍；Pad1和PadN选项[RFC6275]可用于填充。此字段包含零个或多个TLV编码的移动性选项。此处可以包括任何移动标题选项，包括特定于供应商的移动选项[RFC5094]。接收方必须忽略并跳过其不理解的任何选项。移动接入网关使用这些移动选项来识别为其发送更新通知消息的特定绑定。
The Update Notification Acknowledgement is a Mobility Header message that has an MH Type value of 20. The mobile access gateway sends this message in order to acknowledge that it has received an Update Notification message with the (A) flag set and to indicate the status after processing the message.
更新通知确认是具有MH Type值20的移动报头消息。移动接入网关发送该消息以确认其已接收到设置了（A）标志的更新通知消息，并指示处理该消息后的状态。
The format of the Update Notification Acknowledgement message 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sequence # |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Status Code | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
. .
. Mobility options .
. .
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sequence # |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Status Code | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
. .
. Mobility options .
. .
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 4: Update Notification Acknowledgement Message
图4：更新通知确认消息
Sequence Number This 16-bit unsigned integer is copied from the Update Notification message and is used for matching the Update Notification Acknowledgement message with the Update Notification message.
序号此16位无符号整数从更新通知消息复制而来，用于将更新通知确认消息与更新通知消息匹配。
Status Code This 8-bit unsigned integer indicates the status code and specifies the result of the processing of the Update Notification message. Status codes between 0 and 127 signify successful processing of the Update Notification message, and codes between 128 and 255 signify that an error occurred during processing of the Update Notification message. The following status code values are currently defined:
状态代码此8位无符号整数表示状态代码，并指定更新通知消息的处理结果。介于0和127之间的状态代码表示更新通知消息处理成功，介于128和255之间的代码表示在处理更新通知消息期间出错。当前定义了以下状态代码值：
(0) - SUCCESS The mobile access gateway successfully processed the received Update Notification message.
(0) -成功移动访问网关已成功处理收到的更新通知消息。
(128) - FAILED-TO-UPDATE-SESSION-PARAMETERS The mobile access gateway was not able to apply the session parameters sent by the local mobility anchor in the Update Notification message.
（128）-更新会话参数失败移动接入网关无法在更新通知消息中应用本地移动锚发送的会话参数。
(129) - MISSING-VENDOR-SPECIFIC-OPTION The received Update Notification message does not have the required Vendor-Specific Mobility option(s) needed for handling the message.
（129）-缺少特定于供应商的选项收到的更新通知消息没有处理消息所需的特定于供应商的移动选项。
Reserved This field is unused for now. The value MUST be initialized to 0 by the sender and MUST be ignored by the receiver.
保留此字段目前未使用。发送方必须将该值初始化为0，接收方必须忽略该值。
Mobility Options This variable-length field is of such length that the complete Mobility Header is an integer multiple of 8 octets long; the Pad1 and PadN options [RFC6275] can be used for padding. This field contains zero or more TLV-encoded mobility options. Any of the Mobility Header options, including Vendor-Specific Mobility options [RFC5094], can be included here. The receiver MUST ignore and skip any options that it does not understand. These mobility options are used by the mobile access gateway to identify the specific binding for which the Update Notification Acknowledgement message is sent.
移动性选项该可变长度字段的长度使得完整移动性报头是8个八位字节长的整数倍；Pad1和PadN选项[RFC6275]可用于填充。此字段包含零个或多个TLV编码的移动性选项。此处可以包括任何移动标题选项，包括特定于供应商的移动选项[RFC5094]。接收方必须忽略并跳过其不理解的任何选项。移动接入网关使用这些移动选项来识别为其发送更新通知确认消息的特定绑定。
o The local mobility anchor sends the Update Notification message in response to a condition that is specified in the Notification Reason field. The Notification Reason field in the Update Notification message MUST be set to a specific value that identifies the reason for which the Update Notification message is being sent. The Notification Reason, based on the chosen value, may require a specific action that the mobile access gateway needs to perform (for example, requiring re-registration of a mobility session).
o 本地移动锚发送更新通知消息以响应在通知原因字段中指定的条件。更新通知消息中的通知原因字段必须设置为特定值，该值标识发送更新通知消息的原因。基于所选值的通知原因可能需要移动接入网关需要执行的特定动作（例如，需要重新注册移动会话）。
o The Update Notification message MUST include either the Mobile Node Identifier option [RFC4283] or the Mobile Node Group Identifier option [RFC6602].
o 更新通知消息必须包括移动节点标识符选项[RFC4283]或移动节点组标识符选项[RFC6602]。
* If the Mobile Node Identifier option is present, it indicates that the Update Notification message is sent for that specific mobility session.
* 如果存在移动节点标识符选项，则指示针对该特定移动会话发送更新通知消息。
* If the Mobile Node Group Identifier option is present, it indicates that the Update Notification message is sent for the set of mobility sessions identified by the Group Identifier. The Group Identifier is negotiated as part of the initial Proxy Mobile IPv6 signaling. If the Group Identifier is not negotiated in the initial Proxy Mobile IPv6 signaling, a value of (1) for the Group Identifier can always be used. The Group Identifier value of (1) identifies all the mobility sessions established between that local mobility anchor and the mobile access gateway.
* 如果存在移动节点组标识符选项，则指示针对由组标识符标识的移动会话集发送更新通知消息。组标识符作为初始代理移动IPv6信令的一部分进行协商。如果在初始代理移动IPv6信令中未协商组标识符，则始终可以使用组标识符的值（1）。组标识符值（1）标识在该本地移动锚和移动接入网关之间建立的所有移动会话。
o The Update Notification message MAY contain a modified session parameter in the form of a mobility option (e.g., an IPv4 traffic offload option or a QoS option), so the mobile access gateway can apply them on the identified mobility session.
o 更新通知消息可以包含移动选项（例如，IPv4流量卸载选项或QoS选项）形式的修改的会话参数，因此移动接入网关可以将其应用于所识别的移动会话。
The local mobility anchor, when sending the Update Notification message to the mobile access gateway, has to construct the message as specified below:
当向移动接入网关发送更新通知消息时，本地移动锚必须按照以下规定构造消息：
o For requesting an Acknowledgement message and an indication about the result of processing the message from the mobile access gateway for the Update Notification message, the (A) flag in the Update Notification message MUST be set to a value of (1); otherwise, it MUST be set to a value of (0). However, if the Notification Reason is set to a value of (1) "FORCE-REREGISTRATION" or (4) "ANI-PARAMS-REQUESTED", then it is RECOMMENDED that the (A) flag be set to a value of (0). For certain general notifications that are informational in nature, the local mobility anchor may choose not to request acknowledgement for the Update Notification message.
o 为了请求确认消息和关于针对更新通知消息处理来自移动接入网关的消息的结果的指示，更新通知消息中的（A）标志必须设置为值（1）；否则，必须将其设置为（0）值。但是，如果通知原因设置为（1）“强制重新注册”或（4）“ANI-PARAMS-REQUESTED”，则建议将（a）标志设置为（0）值。对于某些本质上是信息性的一般通知，本地移动锚可以选择不请求对更新通知消息的确认。
o The Sequence Number field of the message MUST be initialized to a random number and increased monotonically for subsequent messages. Once the Sequence Number hits the maximum value, it should be wrapped around to 0. Furthermore, if the message is a retransmission of a previously sent message, then the Sequence Number value is not changed.
o 消息的序列号字段必须初始化为随机数，并为后续消息单调递增。一旦序列号达到最大值，它应该被包装为0。此外，如果消息是先前发送的消息的重传，则序列号值不改变。
o When using IPv4 transport, the source address in the IPv4 header MUST be set to the local mobility anchor's IPv4 address (IPv4-LMAA), and the destination address in the IPv4 header MUST be set to the IPv4-Proxy-CoA (Care-of Address) of the mobile access gateway. The Mobility Header (without the IPv6 header) containing the Update Notification message is encapsulated in a UDP header with the destination port of 5436 [RFC5844]. If IPsec Encapsulating Security Payload (ESP) [RFC4303] is used to protect signaling, the packet is processed using transport mode ESP.
o 使用IPv4传输时，IPv4标头中的源地址必须设置为本地移动锚的IPv4地址（IPv4 LMAA），IPv4标头中的目标地址必须设置为移动访问网关的IPv4代理CoA（转交地址）。包含更新通知消息的移动报头（不含IPv6报头）封装在目标端口为5436[RFC5844]的UDP报头中。如果IPsec封装安全有效负载（ESP）[RFC4303]用于保护信令，则使用传输模式ESP处理数据包。
o The format of the Update Notification message sent over IPv4 and protected using ESP is shown below:
o 通过IPv4发送并使用ESP保护的更新通知消息的格式如下所示：
IPv4 header (src=IPv4-LMAA, dst=IPv4-Proxy-CoA) ESP header (in transport mode) UDP header (sport=5436, dport=5436) Mobility Header (Update Notification) (one or more Mobility Header options)
IPv4标头（src=IPv4 LMAA，dst=IPv4代理CoA）ESP标头（在传输模式下）UDP标头（sport=5436，dport=5436）移动标头（更新通知）（一个或多个移动标头选项）
o When using IPv6 transport, the source address in the IPv6 header MUST be set to the local mobility anchor's IPv6 address (LMAA). The destination address in the IPv6 header MUST be set to the Proxy-CoA of the mobile access gateway. The Mobility Header is part of the IPv6 headers.
o 使用IPv6传输时，IPv6标头中的源地址必须设置为本地移动锚的IPv6地址（LMAA）。IPv6标头中的目标地址必须设置为移动访问网关的代理CoA。移动报头是IPv6报头的一部分。
o The format of the Update Notification message sent over IPv6 and protected using ESP is shown below:
o 通过IPv6发送并使用ESP保护的更新通知消息的格式如下所示：
IPv6 header (src=LMAA, dst=Proxy-CoA) Mobility Header (Update Notification) ESP header (in transport mode) (one or more Mobility Header options)
IPv6头（src=LMAA，dst=Proxy-CoA）移动头（更新通知）ESP头（在传输模式下）（一个或多个移动头选项）
o If the local mobility anchor does not receive an Update Notification Acknowledgement message from the mobile access gateway for the Update Notification message with the (A) flag set, then the local mobility anchor MUST retransmit the message. The related considerations are as follows:
o 如果本地移动锚没有从移动接入网关接收到针对设置了（A）标志的更新通知消息的更新通知确认消息，则本地移动锚必须重新传输该消息。有关的考虑如下：
* When retransmitting an Update Notification message, the Sequence Number value and other message contents MUST be the same as in the original message. The (D) flag in the message MUST be set to a value of (1).
* 重新传输更新通知消息时，序列号值和其他消息内容必须与原始消息中的相同。消息中的（D）标志必须设置为（1）值。
* There MUST be a minimum delay of MIN_DELAY_BETWEEN_UPDATE_NOTIFICATION_REPLAY (Section 7), with a default value of 1000 milliseconds, between two retransmit messages.
* 两条重传消息之间的最小延迟必须为MIN\u delay\u，默认值为1000毫秒。
* The message MUST be retransmitted up to the number of times defined by the configuration variable MAX_UPDATE_NOTIFICATION_RETRANSMIT_COUNT (Section 7), with a default value of (1). If there is no Update Notification Acknowledgement message after the retransmission count reaches the value defined by the configuration variable MAX_UPDATE_NOTIFICATION_RETRANSMIT_COUNT, then the message MUST be discarded, and the event SHOULD be logged.
* 消息的重新传输次数必须达到配置变量MAX_UPDATE_NOTIFICATION_RETRANSMIT_COUNT（第7节）定义的次数，默认值为（1）。如果在重新传输计数达到配置变量MAX_Update_Notification_RETRANSMIT_count定义的值后没有更新通知确认消息，则必须丢弃该消息，并记录该事件。
o If the local mobility anchor receives a Binding Error message with the Status field set to 2 as described in [RFC6275], this indicates that the mobile access gateway does not support the Update Notification message, and hence the local mobility anchor MUST NOT send any further Update Notification messages to that mobile access gateway unless an administrative action is taken.
o 如[RFC6275]所述，如果本地移动锚接收到状态字段设置为2的绑定错误消息，则表示移动接入网关不支持更新通知消息，因此，除非采取管理措施，否则本地移动锚不得向该移动接入网关发送任何进一步的更新通知消息。
o When receiving an Update Notification Acknowledgement message, the local mobility anchor MUST verify the Mobility Header as described in Section 9.2 of [RFC6275]. If the packet is dropped due to failure of any of the Mobility Header test checks, the local mobility anchor MUST follow the processing rules as described in Section 9.2 of [RFC6275].
o 当接收到更新通知确认消息时，本地移动锚必须按照[RFC6275]第9.2节所述验证移动报头。如果由于任何移动性报头测试检查失败而丢弃数据包，则本地移动性锚必须遵循[RFC6275]第9.2节所述的处理规则。
o Upon receiving the Update Notification Acknowledgement message, the local mobility anchor MUST verify that the received message is protected by the security association that is being used to protect the other signaling messages between those two peers. For example, if the Proxy Binding Update and Proxy Binding Acknowledgement messages are protected using an IPsec security association [RFC4301], then the Update Notification Acknowledgement message MUST have the IPsec protection with the currently established IPsec security association that is being used for protecting the other Proxy Mobile IPv6 signaling messages.
o 在接收到更新通知确认消息时，本地移动锚必须验证所接收的消息是否受到用于保护这两个对等方之间的其他信令消息的安全关联的保护。例如，如果使用IPsec安全关联[RFC4301]保护代理绑定更新和代理绑定确认消息，然后，更新通知确认消息必须具有IPsec保护，当前已建立的IPsec安全关联用于保护其他代理移动IPv6信令消息。
o If the local mobility anchor receives an Update Notification Acknowledgement message with a failure status and a value of 128 or greater, then it SHOULD log an error.
o 如果本地移动锚接收到一个更新通知确认消息，该消息的状态为失败，值为128或更大，那么它应该记录一个错误。
o If the Sequence Number in the received Update Notification Acknowledgement message does not match any of the Update Notification messages that the local mobility anchor sent, then the message MUST be discarded, and the message should be logged.
o 如果接收到的更新通知确认消息中的序列号与本地移动锚发送的任何更新通知消息不匹配，则必须丢弃该消息，并记录该消息。
o If the local mobility anchor receives an Update Notification Acknowledgement message from the mobile access gateway for an Update Notification message that did not have the (A) flag set, the local mobility anchor MUST process the received message in the same way as a response to an Update Notification message with the (A) flag set.
o 如果本地移动锚从移动接入网关接收到针对未设置（A）标志的更新通知消息的更新通知确认消息，则本地移动锚必须以与对设置了（A）标志的更新通知消息的响应相同的方式处理所接收的消息。
o When receiving an Update Notification message, the mobile access gateway MUST verify the Mobility Header as described in Section 9.2. of [RFC6275]. If the packet is dropped due to failure of any of the Mobility Header test checks, the mobile access gateway MUST follow the processing rules as described in Section 9.2 of [RFC6275].
o 当接收到更新通知消息时，移动接入网关必须按照第9.2节所述验证移动报头。属于[RFC6275]。如果由于任何移动报头测试检查失败而丢弃数据包，则移动接入网关必须遵循[RFC6275]第9.2节所述的处理规则。
o Upon receiving the Update Notification message, the mobile access gateway MUST verify that the received packet is protected by the security association that is being used to protect the other signaling messages between those two peers. For example, if the Proxy Binding Update and Proxy Binding Acknowledgement messages are protected using an IPsec security association, then the Update Notification message MUST have the IPsec protection with the currently established IPsec security association that is being used for protecting the other Proxy Mobile IPv6 signaling messages.
o 在接收到更新通知消息时，移动接入网关必须验证所接收的分组是否受到用于保护这两个对等方之间的其他信令消息的安全关联的保护。例如，如果使用IPsec安全关联保护代理绑定更新和代理绑定确认消息，则更新通知消息必须具有IPsec保护，且当前建立的IPsec安全关联用于保护其他代理移动IPv6信令消息。
o If the received Update Notification message is a retransmission of a previously received message, as identified by the Sequence Number, then the mobile access gateway MUST NOT handle the message as a new request. The (D) flag is used as an indication of a retransmitted request, e.g., due to lost messages or the local mobility anchor not seeing the requested update actions. If the mobile access gateway has not seen the (potentially lost) initial request message, it MUST treat the received Update Notification message (with the (D) flag set) as an initial request and continue processing based on that. If the mobile access gateway detects that the request is a retransmission based on the (D) flag and the Sequence Number, then it SHOULD redo the requested update action, e.g., when the Acknowledgement Requested ((A)) flag is not set. The mobile access gateway MUST always respond to the retransmitted request if the (A) flag is set.
o 如果接收到的更新通知消息是由序列号标识的先前接收到的消息的重传，则移动接入网关不得将该消息作为新请求处理。（D）标志用作重传请求的指示，例如，由于消息丢失或本地移动锚没有看到所请求的更新动作。如果移动接入网关没有看到（可能丢失的）初始请求消息，它必须将接收到的更新通知消息（设置了（D）标志）视为初始请求，并根据该消息继续处理。如果移动接入网关检测到请求是基于（D）标志和序列号的重传，则其应重做请求的更新动作，例如，当未设置确认请求（（a））标志时。如果设置了（A）标志，则移动接入网关必须始终响应重新传输的请求。
o Upon accepting the Update Notification message, the mobile access gateway MUST process the message and perform the actions based on the Notification Reason.
o 在接受更新通知消息后，移动接入网关必须处理该消息并根据通知原因执行操作。
* If the (A) flag in the message is set to a value of (1), the mobile access gateway MUST send an Update Notification Acknowledgement message with the status code field set based on the result of processing the Update Notification message.
* 如果消息中的（A）标志设置为值（1），则移动接入网关必须发送更新通知确认消息，其中状态代码字段根据处理更新通知消息的结果设置。
* If the Notification Reason is set to a value of (1) "FORCE-REREGISTRATION", then the mobile access gateway MUST send a Proxy Binding Update message to the local mobility anchor and obtain the updated session parameters for that mobility session.
* 如果通知原因设置为值（1）“强制重新注册”，则移动接入网关必须向本地移动锚发送代理绑定更新消息，并获取该移动会话的更新会话参数。
* If the Notification Reason is set to a value of (2) "UPDATE-SESSION-PARAMETERS", then the mobile access gateway MUST apply the session parameters that are obtained from the Update Notification message in the form of mobility options.
* 如果通知原因设置为（2）“更新会话参数”，则移动接入网关必须以移动选项的形式应用从更新通知消息获得的会话参数。
However, if the mobile access gateway is unable to apply the received session parameters, then the mobile access gateway MUST apply the following considerations:
但是，如果移动接入网关无法应用接收到的会话参数，则移动接入网关必须应用以下注意事项：
+ If the received Update Notification message has the (A) flag in the message set to a value of (0), then the mobile access gateway MUST drop the received Update Notification message and log the error.
+ 如果收到的更新通知消息中的（A）标志设置为（0）值，则移动访问网关必须删除收到的更新通知消息并记录错误。
+ If the received Update Notification message has the (A) flag in the message set to a value of (1), then the mobile access gateway MUST send an Update Notification Acknowledgement message with a status code value of 128 (FAILED-TO-UPDATE-SESSION-PARAMETERS).
+ 如果接收到的更新通知消息中的（A）标志设置为（1）值，则移动接入网关必须发送状态代码值为128的更新通知确认消息（FAILED-to-Update-SESSION-PARAMETERS）。
* If the Notification Reason is set to a value of (3) "VENDOR-SPECIFIC-REASON", then the mobile access gateway MUST apply the considerations related to handling of the Vendor-Specific Mobility option [RFC5094] that is carried in the Update Notification message. However, if there is no Vendor-Specific Mobility option present in the message, the mobile access gateway MUST apply the following considerations:
* 如果通知原因设置为值（3）“特定于供应商的原因”，则移动接入网关必须应用与处理更新通知消息中携带的特定于供应商的移动选项[RFC5094]相关的注意事项。但是，如果消息中不存在特定于供应商的移动选项，则移动接入网关必须应用以下注意事项：
+ If the received Update Notification message has the (A) flag in the message set to a value of (0), then the mobile access gateway MUST drop the received Update Notification message and log the error.
+ 如果收到的更新通知消息中的（A）标志设置为（0）值，则移动访问网关必须删除收到的更新通知消息并记录错误。
+ If the received Update Notification message has the (A) flag in the message set to a value of (1), then the mobile access gateway MUST send an Update Notification Acknowledgement message with a status code value of 129 (MISSING-VENDOR-SPECIFIC-OPTION).
+ 如果接收到的更新通知消息中的（A）标志设置为值（1），则移动接入网关必须发送状态代码值为129的更新通知确认消息（MISSING-VENDOR-SPECIFIC-OPTION）。
* If the Notification Reason is set to a value of (4) "ANI-PARAMS-REQUESTED", then the mobile access gateway MUST send a Proxy Binding Update message to the local mobility anchor with the Access Network Identifier option [RFC6757]. The Access Network Identifier option MUST reflect the current access network parameters for that mobility session as known to the mobile access gateway at the time of sending the Proxy Binding Update message.
* 如果通知原因设置为值（4）“ANI-PARAMS-REQUESTED”，则移动接入网关必须使用接入网络标识符选项[RFC6757]向本地移动锚发送代理绑定更新消息。接入网络标识符选项必须反映移动接入网关在发送代理绑定更新消息时已知的该移动会话的当前接入网络参数。
* For other Notification Reason values not reserved by this document, the processing required on the mobile access gateway is out of scope for this document and will be specified for each Notification Reason defined by other documents.
* 对于本文档未保留的其他通知原因值，移动访问网关上所需的处理超出了本文档的范围，将为其他文档定义的每个通知原因指定。
The mobile access gateway, when sending the Update Notification Acknowledgement message to the local mobility anchor, has to construct the message as specified below:
移动接入网关在向本地移动锚发送更新通知确认消息时，必须按照以下规定构造消息：
o The Sequence Number MUST be the same as the Sequence Number from the received Update Notification message.
o 序列号必须与收到的更新通知消息中的序列号相同。
o The Status field of the Update Notification message MUST be set to a value that reflects the status of the processing of the Update Notification request. A value of 0 (SUCCESS) indicates that the handling of the Update Notification message was successful.
o 更新通知消息的状态字段必须设置为反映更新通知请求处理状态的值。值0（成功）表示已成功处理更新通知消息。
o The Update Notification Acknowledgement message MUST contain either the Mobile Node Identifier option or the Mobile Node Group Identifier option, copied from the Update Notification message. Furthermore, the mobile access gateway MAY include other Mobility Header options.
o 更新通知确认消息必须包含从更新通知消息复制的移动节点标识符选项或移动节点组标识符选项。此外，移动接入网关可以包括其他移动报头选项。
o The source address in the IP header of the Update Notification Acknowledgement message MUST be set to the destination IP address of the received Update Notification message.
o 更新通知确认消息的IP头中的源地址必须设置为接收到的更新通知消息的目标IP地址。
o The destination address in the IP header of the Update Notification Acknowledgement message MUST be set to the source address of the received Update Notification message.
o 更新通知确认消息的IP标头中的目标地址必须设置为接收到的更新通知消息的源地址。
o If IPsec ESP is used to protect signaling, the packet is processed using transport mode ESP.
o 如果IPsec ESP用于保护信令，则使用传输模式ESP处理数据包。
o The format of the Update Notification Acknowledgement message sent over IPv4 and protected using ESP is shown below:
o 通过IPv4发送并使用ESP保护的更新通知确认消息的格式如下所示：
IPv4 header (src=IPv4-Proxy-CoA, dst=IPv4-LMAA) ESP header (in transport mode) UDP header (sport=5436, dport=5436) Mobility Header (Update Notification Acknowledgement) (one or more Mobility Header options)
IPv4报头（src=IPv4代理CoA，dst=IPv4 LMAA）ESP报头（在传输模式下）UDP报头（sport=5436，dport=5436）移动报头（更新通知确认）（一个或多个移动报头选项）
o The format of the Update Notification Acknowledgement message sent over IPv6 and protected using ESP is shown below:
o 通过IPv6发送并使用ESP保护的更新通知确认消息的格式如下所示：
IPv6 header (src=Proxy-CoA, dst=LMAA) Mobility Header (Update Notification Acknowledgement) ESP header (in transport mode) (one or more Mobility Header options)
IPv6头（src=代理CoA，dst=LMAA）移动头（更新通知确认）ESP头（在传输模式下）（一个或多个移动头选项）
This specification defines the following configuration variables that control the Update Notification feature.
本规范定义了以下控制更新通知功能的配置变量。
The mobility entities, the local mobility anchor, and the mobile access gateway have to allow these variables to be configured by the system management. The configured values for these protocol variables have to survive server reboots and service restarts.
移动实体、本地移动锚和移动接入网关必须允许系统管理层配置这些变量。这些协议变量的配置值必须在服务器重新启动和服务重新启动后仍然有效。
MAX_UPDATE_NOTIFICATION_RETRANSMIT_COUNT
最大更新通知重传计数
This variable specifies the maximum number of times a local mobility anchor can retransmit an Update Notification message before it receives an Update Notification Acknowledgement message. The default value for this parameter is 1. The suggested range of configured values for this variable is between 0 and 5.
此变量指定本地移动锚在接收更新通知确认消息之前可以重新传输更新通知消息的最大次数。此参数的默认值为1。此变量的建议配置值范围介于0和5之间。
MIN_DELAY_BETWEEN_UPDATE_NOTIFICATION_REPLAY
更新通知与重播之间的最小延迟
This variable specifies the minimum delay in seconds before an Update Notification message is retransmitted. The default value for this parameter is 1000 milliseconds. The suggested range of configured values for this variable is between 500 and 5000 milliseconds.
此变量指定重新传输更新通知消息之前的最小延迟（秒）。此参数的默认值为1000毫秒。此变量的建议配置值范围在500到5000毫秒之间。
The Update Notification protocol described in this specification is for use between a local mobility anchor and a mobile access gateway. This specification defines two new Mobility Header messages: Update Notification messages and Update Notification Acknowledgement messages. These Mobility Header messages are to be protected using the same security mechanism that is used for protecting the Proxy Mobile IPv6 signaling messages exchanged between a given local mobility anchor and mobile access gateway.
本规范中描述的更新通知协议用于本地移动锚和移动接入网关之间。该规范定义了两个新的移动头消息：更新通知消息和更新通知确认消息。将使用用于保护在给定本地移动锚和移动接入网关之间交换的代理移动IPv6信令消息的相同安全机制来保护这些移动报头消息。
If IPsec is used, the IPsec security association that is used for protecting the Proxy Binding Update and Proxy Binding Acknowledgement also needs to be used for protecting Update Notification and Update Notification Acknowledgement messages. A Proxy Mobile IPv6 implementation and the IPsec layer are typically able to communicate with each other through an implementation-specific interface, for example, to exchange configuration and notification information.
如果使用IPsec，则用于保护代理绑定更新和代理绑定确认的IPsec安全关联也需要用于保护更新通知和更新通知确认消息。代理移动IPv6实现和IPsec层通常能够通过实现特定的接口彼此通信，例如，交换配置和通知信息。
The traffic selectors associated with the Security Policy Database (SPD) entry for protecting Proxy Binding Update and Proxy Binding Acknowledgement messages (Section 4.2 of [RFC5213]) have to be
与用于保护代理绑定更新和代理绑定确认消息的安全策略数据库（SPD）条目相关联的流量选择器（RFC5213）第4.2节）必须
extended to include the Mobility Header Type values 19 and 20, which have been allocated for Update Notification and Update Notification Acknowledgement messages, respectively. Furthermore, any time there is rekeying of the IPsec security association between the mobile access gateway and the local mobility anchor, the newly established IPsec security association will be used for protecting the Update Notification and Update Notification Acknowledgement messages.
扩展以包括移动性报头类型值19和20，其分别被分配用于更新通知和更新通知确认消息。此外，每当在移动接入网关和本地移动锚之间存在IPsec安全关联的密钥更新时，新建立的IPsec安全关联将用于保护更新通知和更新通知确认消息。
The authors would like to thank Basavaraj Patil, Rajeev Koodli, Lionel Morand, Itsuma Tanaka, Rajesh Pazhyannur, Carlos Jesus Bernardos Cano, John Kaippallimalil, Brian Haberman, and other members of the NETEXT working group for all the comments and discussions on the document.
作者要感谢Basavaraj Patil、Rajeev Koodli、Lionel Morand、Itsuma Tanaka、Rajesh Pazhyannur、Carlos Jesus Bernardos Cano、John Kaippallimalil、Brian Haberman和NETEXT工作组其他成员对该文件的所有评论和讨论。
The authors would like to thank Barry Leiba, Robert Sparks, Carlos Pignataro, Benoit Claise, Stephen Farrell, and Jari Arkko for their inputs to the document as part of the IESG review process.
作者要感谢巴里·莱巴、罗伯特·斯帕克斯、卡洛斯·皮格纳塔罗、贝诺特·克莱斯、斯蒂芬·法雷尔和贾里·阿尔科，感谢他们在IESG审查过程中为文件提供的投入。
IANA has taken the following actions.
IANA已采取以下行动。
o This specification defines a new Mobility Header Type message, Update Notification. This Mobility Header message is described in Section 4.1. The type value 19 for this message has been allocated from the "Mobility Header Types - for the MH Type field in the Mobility Header" registry at <http://www.iana.org/assignments/mobility-parameters>.
o 该规范定义了一种新的移动头类型消息，即更新通知。第4.1节描述了该移动性报头消息。此消息的类型值19已从位于的“移动头类型-移动头中的MH类型”注册表中分配<http://www.iana.org/assignments/mobility-parameters>.
o This specification defines a new Mobility Header Type message, Update Notification Acknowledgement. This Mobility Header message is described in Section 4.2. The type value 20 for this message has been allocated from the "Mobility Header Types - for the MH Type field in the Mobility Header" registry at <http://www.iana.org/assignments/mobility-parameters>.
o 该规范定义了一种新的移动头类型消息，即更新通知确认。第4.2节描述了该移动性报头消息。此消息的类型值20已从位于的“移动头类型-移动头中的MH类型”注册表中分配<http://www.iana.org/assignments/mobility-parameters>.
o This specification defines a new registry for Notification Reasons. It is called the "Update Notification Reasons Registry". This registry has been created under the "Mobile IPv6 Parameters" registry at <http://www.iana.org/assignments/mobility-parameters>. The Notification Reason is a field in the Update Notification message (Section 4.1). The number space for the Notification Reason field needs to be managed by IANA, under the "Update Notification Reason Registry". This specification reserves the following type values. The allocation policy for this field is "Specification Required" [RFC5226].
o 由于通知原因，此规范定义了一个新的注册表。它被称为“更新通知原因注册表”。此注册表已在以下位置的“移动IPv6参数”注册表下创建：<http://www.iana.org/assignments/mobility-parameters>. 通知原因是更新通知消息中的一个字段（第4.1节）。通知原因字段的数字空间需要由IANA在“更新通知原因注册表”下管理。本规范保留以下类型值。此字段的分配策略为“需要规范”[RFC5226]。
+=====+===========================+====================+
|Value| Description | Reference |
+=====+===========================+====================+
| 0 | Reserved | [RFC7077] |
+=====+================================================+
| 1 | FORCE-REREGISTRATION | [RFC7077] |
+=====+================================================+
| 2 | UPDATE-SESSION-PARAMETERS | [RFC7077] |
+=====+================================================+
| 3 | VENDOR-SPECIFIC-REASON | [RFC7077] |
+=====+================================================+
| 4 | ANI-PARAMS-REQUESTED | [RFC7077] |
+=====+================================================+
|255 | Reserved | [RFC7077] |
+=====+================================================+
+=====+===========================+====================+
|Value| Description | Reference |
+=====+===========================+====================+
| 0 | Reserved | [RFC7077] |
+=====+================================================+
| 1 | FORCE-REREGISTRATION | [RFC7077] |
+=====+================================================+
| 2 | UPDATE-SESSION-PARAMETERS | [RFC7077] |
+=====+================================================+
| 3 | VENDOR-SPECIFIC-REASON | [RFC7077] |
+=====+================================================+
| 4 | ANI-PARAMS-REQUESTED | [RFC7077] |
+=====+================================================+
|255 | Reserved | [RFC7077] |
+=====+================================================+
o This specification defines a new registry for Status. It is called the "Update Notification Acknowledgement Status Registry". This registry has been created under the "Mobile IPv6 Parameters" registry at <http://www.iana.org/assignments/mobility-parameters>. The status is a field in the Update Notification Acknowledgement message (Section 4.2). The number space for the Status field needs to be managed by IANA, under the "Update Notification Acknowledgement Status Registry". This specification reserves the following type values. The allocation policy for this field is "Specification Required". Status codes between 0 and 127 signify successful processing of the Update Notification message, and codes between 128 and 255 signify that an error occurred during processing of the Update Notification message.
o 此规范定义了状态的新注册表。它被称为“更新通知确认状态注册表”。此注册表已在以下位置的“移动IPv6参数”注册表下创建：<http://www.iana.org/assignments/mobility-parameters>. 状态是更新通知确认消息中的一个字段（第4.2节）。状态字段的数字空间需要由IANA在“更新通知确认状态注册表”下管理。本规范保留以下类型值。此字段的分配策略为“需要规格”。介于0和127之间的状态代码表示更新通知消息处理成功，介于128和255之间的代码表示在处理更新通知消息期间出错。
+=====+=====================================+=============+
|Value| Description | Reference |
+=====+=====================================+=============+
| 0 | SUCCESS | [RFC7077] |
+=====+=====================================+=============+
|128 | FAILED-TO-UPDATE-SESSION-PARAMETERS | [RFC7077] |
+=====+=====================================+=============+
|129 | MISSING-VENDOR-SPECIFIC-OPTION | [RFC7077] |
+=====+=====================================+=============+
+=====+=====================================+=============+
|Value| Description | Reference |
+=====+=====================================+=============+
| 0 | SUCCESS | [RFC7077] |
+=====+=====================================+=============+
|128 | FAILED-TO-UPDATE-SESSION-PARAMETERS | [RFC7077] |
+=====+=====================================+=============+
|129 | MISSING-VENDOR-SPECIFIC-OPTION | [RFC7077] |
+=====+=====================================+=============+
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2119]Bradner，S.，“RFC中用于表示需求水平的关键词”，BCP 14，RFC 2119，1997年3月。
[RFC4283] Patel, A., Leung, K., Khalil, M., Akhtar, H., and K. Chowdhury, "Mobile Node Identifier Option for Mobile IPv6 (MIPv6)", RFC 4283, November 2005.
[RFC4283]Patel，A.，Leung，K.，Khalil，M.，Akhtar，H.，和K.Chowdhury，“移动IPv6的移动节点标识符选项（MIPv6）”，RFC 4283，2005年11月。
[RFC5094] Devarapalli, V., Patel, A., and K. Leung, "Mobile IPv6 Vendor Specific Option", RFC 5094, December 2007.
[RFC5094]Devarapalli，V.，Patel，A.，和K.Leung，“移动IPv6供应商特定选项”，RFC 50942007年12月。
[RFC5213] Gundavelli, S., Leung, K., Devarapalli, V., Chowdhury, K., and B. Patil, "Proxy Mobile IPv6", RFC 5213, August 2008.
[RFC5213]Gundavelli，S.，Leung，K.，Devarapalli，V.，Chowdhury，K.，和B.Patil，“代理移动IPv6”，RFC 5213，2008年8月。
[RFC5844] Wakikawa, R. and S. Gundavelli, "IPv4 Support for Proxy Mobile IPv6", RFC 5844, May 2010.
[RFC5844]Wakikawa，R.和S.Gundavelli，“代理移动IPv6的IPv4支持”，RFC 5844，2010年5月。
[RFC6275] Perkins, C., Johnson, D., and J. Arkko, "Mobility Support in IPv6", RFC 6275, July 2011.
[RFC6275]Perkins，C.，Johnson，D.，和J.Arkko，“IPv6中的移动支持”，RFC 62752011年7月。
[RFC6602] Abinader, F., Gundavelli, S., Leung, K., Krishnan, S., and D. Premec, "Bulk Binding Update Support for Proxy Mobile IPv6", RFC 6602, May 2012.
[RFC6602]Abinader，F.，Gundavelli，S.，Leung，K.，Krishnan，S.，和D.Premec，“代理移动IPv6的批量绑定更新支持”，RFC 6602，2012年5月。
[PMIPv6-FLOW-MOB] Bernardos, CJ., Ed., "Proxy Mobile IPv6 Extensions to Support Flow Mobility", Work in Progress, October 2013.
[PMIPv6 FLOW MOB]Bernardos，CJ.，编辑，“支持流移动的代理移动IPv6扩展”，正在进行的工作，2013年10月。
[PMIPv6-QoS] Liebsch, M., Seite, P., Yokota, H., Korhonen, J., and S. Gundavelli, "Quality of Service Option for Proxy Mobile IPv6", Work in Progress, November 2013.
[PMIPv6 QoS]Liebsch，M.，Seite，P.，横田，H.，Korhonen，J.，和S.Gundavelli，“代理移动IPv6的服务质量选项”，正在进行的工作，2013年11月。
[RFC4301] Kent, S. and K. Seo, "Security Architecture for the Internet Protocol", RFC 4301, December 2005.
[RFC4301]Kent，S.和K.Seo，“互联网协议的安全架构”，RFC 43012005年12月。
[RFC4303] Kent, S., "IP Encapsulating Security Payload (ESP)", RFC 4303, December 2005.
[RFC4303]Kent，S.，“IP封装安全有效载荷（ESP）”，RFC 4303，2005年12月。
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA Considerations Section in RFCs", BCP 26, RFC 5226, May 2008.
[RFC5226]Narten，T.和H.Alvestrand，“在RFCs中编写IANA注意事项部分的指南”，BCP 26，RFC 5226，2008年5月。
[RFC5846] Muhanna, A., Khalil, M., Gundavelli, S., Chowdhury, K., and P. Yegani, "Binding Revocation for IPv6 Mobility", RFC 5846, June 2010.
[RFC5846]Muhanna，A.，Khalil，M.，Gundavelli，S.，Chowdhury，K.，和P.Yegani，“IPv6移动的绑定撤销”，RFC 58462010年6月。
[RFC5847] Devarapalli, V., Koodli, R., Lim, H., Kant, N., Krishnan, S., and J. Laganier, "Heartbeat Mechanism for Proxy Mobile IPv6", RFC 5847, June 2010.
[RFC5847]Devarapalli，V.，Koodli，R.，Lim，H.，Kant，N.，Krishnan，S.，和J.Laganier，“代理移动IPv6的心跳机制”，RFC 58472010年6月。
[RFC6757] Gundavelli, S., Korhonen, J., Grayson, M., Leung, K., and R. Pazhyannur, "Access Network Identifier (ANI) Option for Proxy Mobile IPv6", RFC 6757, October 2012.
[RFC6757]Gundavelli，S.，Korhonen，J.，Grayson，M.，Leung，K.，和R.Pazhyannur，“代理移动IPv6的接入网络标识符（ANI）选项”，RFC 6757，2012年10月。
[RFC6909] Gundavelli, S., Zhou, X., Korhonen, J., Feige, G., and R. Koodli, "IPv4 Traffic Offload Selector Option for Proxy Mobile IPv6", RFC 6909, April 2013.
[RFC6909]Gundavelli，S.，Zhou，X.，Korhonen，J.，Feige，G.，和R.Koodli，“代理移动IPv6的IPv4流量卸载选择器选项”，RFC 69092013年4月。
Authors' Addresses
作者地址
Suresh Krishnan Ericsson 8400 Blvd Decarie Town of Mount Royal, Quebec Canada
Suresh Krishnan Ericsson加拿大魁北克皇家山Decarie镇8400大道
Phone: +1 514 345 7900 x42871
EMail: suresh.krishnan@ericsson.com
Phone: +1 514 345 7900 x42871
EMail: suresh.krishnan@ericsson.com
Sri Gundavelli Cisco 170 West Tasman Drive San Jose, CA 95134 USA
美国加利福尼亚州圣何塞市西塔斯曼大道170号，邮编95134
EMail: sgundave@cisco.com
EMail: sgundave@cisco.com
Marco Liebsch NEC Kurfuersten-Anlage 36 D-69115 Heidelberg Germany
Marco Liebsch NEC Kurfuersten Anlage 36 D-69115德国海德堡
EMail: marco.liebsch@neclab.eu
EMail: marco.liebsch@neclab.eu
Hidetoshi Yokota KDDI
横田英寿
EMail: yokota@kddilabs.jp
EMail: yokota@kddilabs.jp
Jouni Korhonen Broadcom Porkkalankatu 24 Helsinki FIN-00180 Finland
Jouni Korhonen Broadcom Porkkalankatu 24赫尔辛基FIN-00180芬兰
EMail: jouni.nospam@gmail.com
EMail: jouni.nospam@gmail.com