Internet Engineering Task Force (IETF) G. Tsirtsis
Request for Comments: 6089 Qualcomm
Updates: 5648 H. Soliman
Category: Standards Track Elevate Technologies
ISSN: 2070-1721 N. Montavont
IT/TB
G. Giaretta
Qualcomm
K. Kuladinithi
University of Bremen
January 2011
Internet Engineering Task Force (IETF) G. Tsirtsis
Request for Comments: 6089 Qualcomm
Updates: 5648 H. Soliman
Category: Standards Track Elevate Technologies
ISSN: 2070-1721 N. Montavont
IT/TB
G. Giaretta
Qualcomm
K. Kuladinithi
University of Bremen
January 2011
Flow Bindings in Mobile IPv6 and Network Mobility (NEMO) Basic Support
移动IPv6和网络移动（NEMO）基本支持中的流绑定
Abstract
摘要
This document introduces extensions to Mobile IPv6 that allow nodes to bind one or more flows to a care-of address. These extensions allow multihomed nodes to instruct home agents and other Mobile IPv6 entities to direct inbound flows to specific addresses.
本文档介绍了移动IPv6的扩展，允许节点将一个或多个流绑定到转交地址。这些扩展允许多宿节点指示归属代理和其他移动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/rfc6089.
有关本文件当前状态、任何勘误表以及如何提供反馈的信息，请访问http://www.rfc-editor.org/info/rfc6089.
Copyright Notice
版权公告
Copyright (c) 2011 IETF Trust and the persons identified as the document authors. All rights reserved.
版权所有（c）2011 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
本文件受BCP 78和IETF信托有关IETF文件的法律规定的约束(http://trustee.ietf.org/license-info)自本文件出版之日起生效。请仔细阅读这些文件，因为它们描述了您对本文件的权利和限制。从该文档中提取的代码组件必须
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.
包括信托法律条款第4.e节中所述的简化BSD许可证文本，且不提供简化BSD许可证中所述的担保。
Table of Contents
目录
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Requirements Notation . . . . . . . . . . . . . . . . . . . . 4
3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4
4. Mobile IPv6 Extensions . . . . . . . . . . . . . . . . . . . . 5
4.1. Definition Update for Binding Identifier Mobility
Option . . . . . . . . . . . . . . . . . . . . . . . . . . 5
4.2. Flow Identification Mobility Option . . . . . . . . . . . 5
4.2.1. Flow Identification Sub-Options Definition . . . . . . 7
4.2.2. Flow Summary Mobility Option . . . . . . . . . . . . . 11
4.3. Flow Bindings Entries List and Its Relationship to
Binding Cache . . . . . . . . . . . . . . . . . . . . . . 12
5. Protocol Operations . . . . . . . . . . . . . . . . . . . . . 14
5.1. General . . . . . . . . . . . . . . . . . . . . . . . . . 14
5.1.1. Preferred Care-of Address . . . . . . . . . . . . . . 15
5.2. Mobile Node Considerations . . . . . . . . . . . . . . . . 15
5.2.1. Sending BU with BID Options . . . . . . . . . . . . . 15
5.2.2. Sending BU with Flow Identification Mobility
Options . . . . . . . . . . . . . . . . . . . . . . . 16
5.2.3. Sending BU with a Flow Summary Option . . . . . . . . 17
5.2.4. Removing Flow Bindings . . . . . . . . . . . . . . . . 18
5.2.5. Returning Home . . . . . . . . . . . . . . . . . . . . 18
5.2.6. Receiving Binding Acknowledgements . . . . . . . . . . 19
5.2.7. Return Routability Procedure . . . . . . . . . . . . . 19
5.3. HA, MAP, and CN Considerations . . . . . . . . . . . . . . 19
5.3.1. Handling Binding Identifier Mobility Options . . . . . 20
5.3.2. Handling Flow Identification Mobility Options . . . . 20
5.3.3. Handling Flow Summary Mobility Option . . . . . . . . 23
5.3.4. Flow Binding Removals . . . . . . . . . . . . . . . . 23
5.3.5. Sending Binding Acknowledgements . . . . . . . . . . . 24
5.3.6. Packet Processing . . . . . . . . . . . . . . . . . . 24
6. MTU Considerations . . . . . . . . . . . . . . . . . . . . . . 25
7. Security considerations . . . . . . . . . . . . . . . . . . . 26
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 27
9. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 28
10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 29
11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 29
11.1. Normative References . . . . . . . . . . . . . . . . . . . 29
11.2. Informative References . . . . . . . . . . . . . . . . . . 29
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Requirements Notation . . . . . . . . . . . . . . . . . . . . 4
3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4
4. Mobile IPv6 Extensions . . . . . . . . . . . . . . . . . . . . 5
4.1. Definition Update for Binding Identifier Mobility
Option . . . . . . . . . . . . . . . . . . . . . . . . . . 5
4.2. Flow Identification Mobility Option . . . . . . . . . . . 5
4.2.1. Flow Identification Sub-Options Definition . . . . . . 7
4.2.2. Flow Summary Mobility Option . . . . . . . . . . . . . 11
4.3. Flow Bindings Entries List and Its Relationship to
Binding Cache . . . . . . . . . . . . . . . . . . . . . . 12
5. Protocol Operations . . . . . . . . . . . . . . . . . . . . . 14
5.1. General . . . . . . . . . . . . . . . . . . . . . . . . . 14
5.1.1. Preferred Care-of Address . . . . . . . . . . . . . . 15
5.2. Mobile Node Considerations . . . . . . . . . . . . . . . . 15
5.2.1. Sending BU with BID Options . . . . . . . . . . . . . 15
5.2.2. Sending BU with Flow Identification Mobility
Options . . . . . . . . . . . . . . . . . . . . . . . 16
5.2.3. Sending BU with a Flow Summary Option . . . . . . . . 17
5.2.4. Removing Flow Bindings . . . . . . . . . . . . . . . . 18
5.2.5. Returning Home . . . . . . . . . . . . . . . . . . . . 18
5.2.6. Receiving Binding Acknowledgements . . . . . . . . . . 19
5.2.7. Return Routability Procedure . . . . . . . . . . . . . 19
5.3. HA, MAP, and CN Considerations . . . . . . . . . . . . . . 19
5.3.1. Handling Binding Identifier Mobility Options . . . . . 20
5.3.2. Handling Flow Identification Mobility Options . . . . 20
5.3.3. Handling Flow Summary Mobility Option . . . . . . . . 23
5.3.4. Flow Binding Removals . . . . . . . . . . . . . . . . 23
5.3.5. Sending Binding Acknowledgements . . . . . . . . . . . 24
5.3.6. Packet Processing . . . . . . . . . . . . . . . . . . 24
6. MTU Considerations . . . . . . . . . . . . . . . . . . . . . . 25
7. Security considerations . . . . . . . . . . . . . . . . . . . 26
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 27
9. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 28
10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 29
11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 29
11.1. Normative References . . . . . . . . . . . . . . . . . . . 29
11.2. Informative References . . . . . . . . . . . . . . . . . . 29
Mobile IPv6 [RFC3775], Dual-Stack MIPv6 (DSMIPv6) [RFC5555], and Network Mobility (NEMO) Basic Support [RFC3963] allow a mobile node / mobile router to manage its mobility using the binding update message, which binds one care-of address to one home address and associated mobile networks. The binding update message can be sent to the home agent. In Mobile IPv6, the binding update can also be sent to a correspondent node or to a mobility anchor point (see [RFC5380]). The semantics of the binding update are limited to care-of address changes. That is, [RFC3775], [RFC5555], and [RFC3963] do not allow a mobile node / mobile router to bind more than one address to the home address. In [RFC5648], Mobile IPv6 and NEMO Basic Support are extended to allow the binding of more than one care-of address to a home address. This specification further extends Mobile IPv6, DSMIPv6, and NEMO Basic Support to allow them to specify policies associated with each binding. A policy can contain a request for special treatment of a particular IPv4 or IPv6 flow, which is viewed as a group of packets matching a traffic selector. Hence, this specification allows a mobile node / mobile router to bind a particular flow to a care-of address without affecting other flows using the same home address. In addition, this specification allows to bind a particular flow to a particular care-of address directly with correspondent node and mobility agents (i.e., home agents [RFC3775] and mobility anchor points [RFC5380]).
移动IPv6[RFC3775]、双栈MIPv6（DSMPv6）[RFC5555]和网络移动性（NEMO）基本支持[RFC3963]允许移动节点/移动路由器使用绑定更新消息管理其移动性，该消息将一个转交地址绑定到一个家庭地址和相关移动网络。绑定更新消息可以发送到归属代理。在移动IPv6中，绑定更新还可以发送到对应节点或移动锚点（请参见[RFC5380]）。绑定更新的语义仅限于处理地址更改。也就是说，[RFC3775]、[RFC5555]和[RFC3963]不允许移动节点/移动路由器将多个地址绑定到家庭地址。[RFC5648]扩展了移动IPv6和NEMO基本支持，允许将多个转交地址绑定到家庭地址。该规范进一步扩展了移动IPv6、DSMIV6和NEMO基本支持，以允许它们指定与每个绑定关联的策略。策略可以包含对特定IPv4或IPv6流进行特殊处理的请求，该请求被视为与流量选择器匹配的一组数据包。因此，该规范允许移动节点/移动路由器将特定流绑定到转交地址，而不影响使用相同归属地址的其他流。此外，该规范允许直接使用对应节点和移动代理（即，归属代理[RFC3775]和移动锚定点[RFC5380]）将特定流绑定到特定转交地址。
In this document, a flow is defined as a set of IP packets matching a traffic selector. A traffic selector can identify the source and destination IP addresses, transport protocol number, the source and destination port numbers and other fields in IP and higher-layer headers. This specification does not define traffic selectors, which are going to be defined in other specifications. This specification, however, does define the traffic selector sub-option format to be used for any specific traffic selector.
在本文档中，流定义为一组与流量选择器匹配的IP数据包。流量选择器可以识别源和目标IP地址、传输协议号、源和目标端口号以及IP和更高层报头中的其他字段。本规范未定义流量选择器，其他规范将对其进行定义。但是，本规范确实定义了用于任何特定流量选择器的流量选择器子选项格式。
Using the flow identifier option introduced in this specification, a mobile node / mobile router can bind one or more flows to a care-of address while maintaining the reception of other flows on another care-of address. The mobile node / mobile router assembles the flow binding requests based on local policies, link characteristics, and the types of applications running at the time. Such policies are outside the scope of this document.
使用本规范中引入的流标识符选项，移动节点/移动路由器可以将一个或多个流绑定到转交地址，同时保持在另一转交地址上接收其他流。移动节点/移动路由器根据本地策略、链路特征和当时运行的应用程序类型组合流绑定请求。此类政策不在本文件范围内。
It should be noted that the flow identification mobility option can be associated with any binding update, whether it is sent to a mobility agent or a correspondent node.
应当注意，流标识移动选项可以与任何绑定更新相关联，无论它是发送到移动代理还是对应节点。
Note that per-packet load balancing may have negative impacts on TCP congestion avoidance mechanisms as it is desirable to maintain order between packets belonging to the same TCP connection. This behavior is specified in [RFC2702]. Other negative impacts are also foreseen for other types of real-time connections due to the potential variations in round-trip time between packets. Moreover, per-packet load-balancing will negatively affect traffic with anti-replay protection mechanisms. Hence, per-packet load balancing is not envisioned in this specification.
请注意，每个数据包负载平衡可能会对TCP拥塞避免机制产生负面影响，因为需要保持属于同一TCP连接的数据包之间的顺序。[RFC2702]中规定了此行为。由于数据包之间往返时间的潜在变化，其他类型的实时连接也会受到其他负面影响。此外，每个数据包的负载平衡将通过反重放保护机制对流量产生负面影响。因此，本规范中未设想每个数据包的负载平衡。
In the rest of the document, the term "mobile node" is used to designate either a mobile node as defined in [RFC3775] and [RFC5648], or a mobile router as defined in [RFC3963] unless stated otherwise.
在本文件的其余部分中，术语“移动节点”用于指定[RFC3775]和[RFC5648]中定义的移动节点，或[RFC3963]中定义的移动路由器，除非另有说明。
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 [RFC2119].
本文件中的关键词“必须”、“不得”、“必需”、“应”、“不应”、“应”、“不应”、“建议”、“可”和“可选”应按照[RFC2119]中所述进行解释。
Terms used in this document are defined in [RFC3753] and [RFC4885]. The following terms are also used in this document:
本文件中使用的术语在[RFC3753]和[RFC4885]中定义。本文件中还使用了以下术语：
Flow: A flow is a sequence of packets for which the mobile node (MN) desires special handling either by the home agent (HA), the corresponding node (CN) or the mobility anchor point (MAP).
流：流是移动节点（MN）希望由归属代理（HA）、相应节点（CN）或移动锚定点（MAP）对其进行特殊处理的分组序列。
Traffic Selector: One or more parameters that can be matched against fields in the packet's headers for the purpose of classifying a packet. Examples of such parameters include the source and destination IP addresses, transport protocol number, the source and destination port numbers, and other fields in IP and higher-layer headers.
流量选择器：一个或多个参数，可与数据包头中的字段相匹配，用于对数据包进行分类。此类参数的示例包括源和目标IP地址、传输协议号、源和目标端口号以及IP和更高层头中的其他字段。
Flow binding: It consists of a traffic selector, and one or more binding identifiers (BIDs). IP packets from one or more flows that match the traffic selector associated with the flow binding are forwarded to the BIDs associated with the same flow binding.
流绑定：它由一个流量选择器和一个或多个绑定标识符（BIDs）组成。来自与流绑定关联的流量选择器匹配的一个或多个流的IP数据包被转发到与相同流绑定关联的BID。
Flow Identifier: A flow identifier uniquely identifies a flow binding associated with a mobile node. It is generated by a mobile node and is cached in the table of flow binding entries maintained by the MN, HA, CN, or MAP.
流标识符：流标识符唯一标识与移动节点关联的流绑定。它由移动节点生成，并缓存在由MN、HA、CN或MAP维护的流绑定条目表中。
This section introduces extensions to Mobile IPv6 that are necessary for supporting the flow binding mechanism described in this document.
本节介绍支持本文档中描述的流绑定机制所必需的移动IPv6扩展。
This specification updates the definition of the Binding Identifier Mobility option defined in [RFC5648], as follows:
本规范更新了[RFC5648]中定义的绑定标识符移动选项的定义，如下所示：
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 = 35 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Binding ID (BID) | Status |H| BID-PRI |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-------------------------------+
+ +
: IPv4 or IPv6 Care-of Address (CoA) :
+ +
+---------------------------------------------------------------+
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 = 35 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Binding ID (BID) | Status |H| BID-PRI |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-------------------------------+
+ +
: IPv4 or IPv6 Care-of Address (CoA) :
+ +
+---------------------------------------------------------------+
Figure 1: The Binding Identifier Mobility Option
图1：绑定标识符移动选项
BID-PRI
BID-PRI
This is a 7-bit unsigned integer placing each BID to a relative priority (PRI) with other registered BIDs. Value '0' is reserved and MUST NOT be used. A lower number in this field indicates a higher priority, while BIDs with the same BID-PRI value have equal priority meaning that, the BID used is an implementation issue. This is consistent with current practice in packet classifiers.
这是一个7位无符号整数，将每个出价与其他注册出价置于相对优先级（PRI）。值“0”是保留的，不能使用。此字段中的数字越小表示优先级越高，而具有相同BID-PRI值的投标具有相同的优先级，这意味着所使用的投标是一个实施问题。这与包分类器的当前实践是一致的。
The flow identification mobility option is a new mobility option [RFC3775], and it is included in the binding update and acknowledgement messages. This option contains information that allows the receiver of a binding update to install policies on a traffic flow and route it to a given care-of address. Multiple options may exist within the same binding update message. The alignment requirement for this option is 2n.
流标识移动选项是一个新的移动选项[RFC3775]，它包含在绑定更新和确认消息中。此选项包含允许绑定更新的接收方在流量上安装策略并将其路由到给定转交地址的信息。同一绑定更新消息中可能存在多个选项。该选项的对齐要求为2n。
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Option Type | Option Len | FID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| FID-PRI | Reserved | Status |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sub-options (optional) ...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Option Type | Option Len | FID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| FID-PRI | Reserved | Status |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sub-options (optional) ...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 2: The Flow Identification Mobility Option
图2：流标识移动性选项
Option Type
选项类型
45
45
Option Len
选择透镜
Length of the option in octets as per [RFC3775].
根据[RFC3775]以八位字节为单位的选项长度。
FID
氢火焰离子化检测器
The Flow Identifier field is a 16-bit unsigned integer that includes the unique identifier for the flow binding. This field is used to refer to an existing flow binding or to create a new flow binding. The value of this field is set by the mobile node. FID = 0 is reserved and MUST NOT be used.
流标识符字段是一个16位无符号整数，其中包括流绑定的唯一标识符。此字段用于引用现有流绑定或创建新的流绑定。此字段的值由移动节点设置。FID=0是保留的，不得使用。
FID-PRI
FID-PRI
This is a 16-bit unsigned integer priority field to indicate the priority of a particular option. This field is needed in cases where two different flow descriptions in two different options overlap. The priority field decides which policy should be executed in those cases. A lower number in this field indicates a higher priority. Value '0' is reserved and MUST NOT be used. FID-PRI MUST be unique to each of the flows pertaining to a given MN. In other words, two FIDs MUST NOT be associated with the same FID-PRI value.
这是一个16位无符号整数优先级字段，用于指示特定选项的优先级。如果两个不同选项中的两个不同流描述重叠，则需要此字段。优先级字段决定在这些情况下应执行的策略。此字段中的数字越小，表示优先级越高。值“0”是保留的，不能使用。FID-PRI对于与给定MN相关的每个流都必须是唯一的。换句话说，两个FID不得与同一FID-PRI值关联。
Status
地位
This 8-bit unsigned integer field indicates the success or failure of the flow binding operation for the particular flow in the option. This field is not relevant to the binding update message as a whole or to other flow identification options. This field is only relevant when included in the Binding Acknowledgement message and must be ignored in the
此8位无符号整数字段表示选项中特定流的流绑定操作的成功或失败。此字段与整个绑定更新消息或其他流标识选项无关。此字段仅在包含在绑定确认消息中时才相关，并且必须在
binding update message. The following values are reserved for the Status field within the flow identification mobility option:
绑定更新消息。以下值保留用于流标识移动选项内的状态字段：
0 Flow binding successful
0流绑定成功
128 Administratively prohibited
128行政禁止
129 Flow binding rejected, reason unspecified
129流绑定被拒绝，原因不明
130 Flow identification mobility option malformed
130流标识移动选项格式不正确
131 BID not found
131未找到投标书
132 FID not found
132未找到FID
133 Traffic selector format not supported
133不支持流量选择器格式
Sub-options (optional)
子选项（可选）
Zero or more sub-options, defined in Section 4.2.1.
第4.2.1节中定义的零个或多个子选项。
Flow identification sub-options are encoded within the remaining space of the flow identification mobility option, using a sub-option type-length-value (TLV) format as follows:
流标识子选项在流标识移动选项的剩余空间内编码，使用子选项类型长度值（TLV）格式，如下所示：
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sub-Opt Type |Sub-Opt 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sub-Opt Type |Sub-Opt Length | Sub-Option Data...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 3: Flow Identification Sub-Option Format
图3：流标识子选项格式
Sub-Opt Type
子选项类型
8-bit unsigned integer indicating the sub-option Type. When processing a flow identification mobility option containing an option for which the sub-option Type value is not recognized by the receiver, the receiver MUST silently ignore and skip over the sub-option, correctly handling any remaining sub-options in the same option.
指示子选项类型的8位无符号整数。当处理包含接收者无法识别子选项类型值的选项的流标识移动选项时，接收者必须默默忽略并跳过子选项，正确处理同一选项中的任何剩余子选项。
Sub-Opt Len
次选择透镜
8-bit unsigned integer, representing the length in octets of the flow identification sub-option. This field indicates the length of the sub-option not including the Sub-Opt Type and Sub-Opt Length fields. Note that Sub-Opt Type '0' (Section 4.2.1.1) is a special case that does not take a Sub-Opt Length field.
8位无符号整数，表示流标识子选项的长度（以八位字节为单位）。此字段表示子选项的长度，不包括子选项类型和子选项长度字段。请注意，子选项类型“0”（第4.2.1.1节）是一种特殊情况，不采用子选项长度字段。
Sub-Option Data
子选项数据
A variable length field that contains data specific to the sub-option.
包含子选项特定数据的可变长度字段。
The following subsections specify the sub-option Types that are currently defined for use in the flow identification option. Implementations MUST silently ignore any sub-options that they do not understand.
以下小节指定了当前定义用于流标识选项的子选项类型。实现必须悄悄地忽略它们不理解的任何子选项。
These sub-options may have alignment requirements. Following the convention in [RFC3775], regarding mobility options, these sub-options are aligned in a packet so that multi-octet values within the sub-option Data field of each sub-option fall on natural boundaries (i.e., fields of width n octets are placed at an integer multiple of n octets from the start of the header, for n = 1, 2, 4, or 8).
这些子选项可能有对齐要求。按照[RFC3775]中关于移动性选项的约定，这些子选项在一个数据包中对齐，以便每个子选项的子选项数据字段中的多个八位组值落在自然边界上（即，宽度为n个八位组的字段从报头开始以n个八位组的整数倍放置，对于n=1、2、4或8）。
The Pad1 sub-option does not have any alignment requirements. Its format is as follows:
Pad1子选项没有任何对齐要求。其格式如下：
0
0 1 2 3 4 5 6 7
+-+-+-+-+-+-+-+-+
| Sub-Opt Type |
+-+-+-+-+-+-+-+-+
0
0 1 2 3 4 5 6 7
+-+-+-+-+-+-+-+-+
| Sub-Opt Type |
+-+-+-+-+-+-+-+-+
Sub-Opt Type
子选项类型
0
0
NOTE: The format of the Pad1 sub-option is a special case -- it has neither sub-option Length nor sub-option Data fields.
注意：Pad1子选项的格式是一种特殊情况——它既没有子选项长度，也没有子选项数据字段。
The Pad1 sub-option is used to insert one octet of padding in the flow identification option. If more than one octet of padding is required, the PadN sub-option, described next, should be used rather than multiple Pad1 sub-options.
Pad1子选项用于在流标识选项中插入一个八位字节的填充。如果需要多个八位字节的填充，则应使用下面描述的PadN子选项，而不是多个Pad1子选项。
The PadN sub-option does not have any alignment requirements. Its format is as follows:
PadN子选项没有任何对齐要求。其格式如下：
0 1
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+- - - - - - - - -
| Sub-Opt Type | Sub-Opt Len | Option Data
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+- - - - - - - - -
0 1
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+- - - - - - - - -
| Sub-Opt Type | Sub-Opt Len | Option Data
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+- - - - - - - - -
Sub-Opt Type
子选项类型
1
1.
Sub-Opt Len
次选择透镜
Set to the length of the sub-option.
设置为子选项的长度。
Sub-Opt Data
子选项数据
0 or more bytes set to 0 by the sender and ignored by the receiver.
0个或多个字节由发送方设置为0，但被接收方忽略。
The PadN sub-option is used to insert two or more octets of padding in the flow identification mobility option. For N octets of padding, the sub-option Length field contains the value N, and the sub-option Data field consists of N-2 zero-valued octets. PadN sub-option Data MUST be ignored by the receiver.
PadN子选项用于在流标识移动性选项中插入两个或多个八位字节的填充。对于N个八位字节的填充，子选项长度字段包含值N，子选项数据字段由N-2个零值八位字节组成。接收器必须忽略PadN子选项数据。
This section introduces the binding reference sub-option, included in the flow identification mobility option. A node MUST NOT include more than one binding reference sub-options in a given flow binding identification option. The binding reference sub-option includes one or more BIDs defined in Multiple Care-of Addresses (MCoA) [RFC5648]. This sub-option associates the flow described in a flow identification mobility option with one or more registered BIDs.
本节介绍绑定参考子选项，包括在流标识移动性选项中。在给定的流绑定标识选项中，节点不得包含多个绑定引用子选项。绑定引用子选项包括在多个转交地址（MCoA）[RFC5648]中定义的一个或多个出价。此子选项将流标识移动选项中描述的流与一个或多个注册投标相关联。
When binding a flow using this sub-option, the binding identifier mobility option, defined in [RFC5648], MUST be included in either the same or an earlier binding update (BU). The binding reference sub-option is shown below. The alignment requirement for this sub-option is 2n.
使用此子选项绑定流时，[RFC5648]中定义的绑定标识符移动选项必须包含在相同或早期绑定更新（BU）中。绑定引用子选项如下所示。该子选项的对齐要求为2n。
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Sub-Opt Type | Sub-Opt Len | BID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| BID ........
+-+-+-+-+-+-+-+-+-+-
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Sub-Opt Type | Sub-Opt Len | BID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| BID ........
+-+-+-+-+-+-+-+-+-+-
Figure 4: The Binding Reference Sub-Option
图4：绑定引用子选项
Sub-Opt Type
子选项类型
2
2.
Sub-Opt Len
次选择透镜
Variable
变量
BID
投标
A 16-bit unsigned integer indicating the BID that the mobile node wants to associate with the flow identification option. One or more BID fields can be included in this sub-option. Since each BID is 2 bytes long, the value of the Sub-opt Len field indicates the number of BIDs present. Number of BIDs = Sub-Opt Len/2.
16位无符号整数，指示移动节点希望与流标识选项关联的出价。此子选项中可以包含一个或多个投标字段。由于每个BID的长度为2字节，因此Sub-opt Len字段的值表示存在的BID数。投标数量=子选项长度/2。
The traffic selector sub-option includes the parameters used to match packets for a specific flow binding. A node MUST NOT include more than one traffic selector sub-option in a given flow binding identification option.
流量选择器子选项包括用于匹配特定流绑定的数据包的参数。在给定的流绑定标识选项中，节点不得包含多个流量选择器子选项。
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Sub-Opt Type | Sub-Opt Len | TS Format | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Traffic Selector ...
+-+-+-+-+-+-+-+-+-+-+-+
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Sub-Opt Type | Sub-Opt Len | TS Format | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Traffic Selector ...
+-+-+-+-+-+-+-+-+-+-+-+
Figure 5: The Traffic Selector Sub-Option
图5：交通选择器子选项
Sub-Opt Type
子选项类型
3
3.
Sub-Opt Len
次选择透镜
Variable
变量
TS Format
TS格式
An 8-bit unsigned integer indicating the Traffic Selector Format. Value "0" is reserved and MUST NOT be used.
表示流量选择器格式的8位无符号整数。值“0”是保留的，不能使用。
Reserved
含蓄的
An 8-bit reserved field. It MUST be set to zero by the sender and ignored by the receiver.
8位保留字段。发送方必须将其设置为零，接收方必须忽略它。
Traffic Selector
交通选择器
A variable-length field, the format and content of which is out of scope for this specification. The traffic selector defined in [RFC6088] is mandatory to implement.
可变长度字段，其格式和内容超出本规范的范围。必须使用[RFC6088]中定义的流量选择器。
The flow summary mobility option is a new mobility option [RFC3775], which includes one or more flow identifiers (FIDs) for the purpose of refreshing their state. The alignment requirement for this option is 2n.
流摘要移动选项是一个新的移动选项[RFC3775]，它包括一个或多个流标识符（FID），用于刷新其状态。该选项的对齐要求为2n。
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Option Type | Option Len | FID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| FID ........
+-+-+-+-+-+-+-+-+-+-
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Option Type | Option Len | FID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| FID ........
+-+-+-+-+-+-+-+-+-+-
Figure 6: The Flow Summary Mobility Option
图6：流程摘要移动选项
Option Type
选项类型
44
44
Option Length
选项长度
Length of the option in octets as per [RFC3775].
根据[RFC3775]以八位字节为单位的选项长度。
FID
氢火焰离子化检测器
A 16-bit unsigned integer indicating a registered FID. One or more FID fields can be included in this option. Number of FIDs = Option Len/2.
表示已注册FID的16位无符号整数。此选项中可以包含一个或多个FID字段。FID数量=选项Len/2。
The conceptual Mobile IPv6 binding cache was defined in [RFC3775] to identify the mobile IP state maintained by the mobile node, mobility agent, and correspondent node. The binding cache includes, among others, the mobile node's home address, the registered care-of address, and the lifetime of the binding. The binding cache has been extended by [RFC5648] to include more than one care-of addresses and to associate each of them with a binding identifier (BID).
[RFC3775]中定义了概念上的移动IPv6绑定缓存，以标识由移动节点、移动代理和对应节点维护的移动IP状态。除其他外，绑定高速缓存包括移动节点的家庭地址、注册的转交地址和绑定的生存期。绑定缓存已由[RFC5648]扩展，以包括多个转交地址，并将每个地址与绑定标识符（BID）关联。
This specification does not modify the Mobile IPv6 binding cache any further.
此规范不会进一步修改移动IPv6绑定缓存。
Flow bindings can be thought of as a conceptual list of entries that is separate from the binding cache. The flow bindings list contains an entry for each of the registered flow bindings. Flow binding entries point to an entry in the binding cache by means of the BID. Each flow binding entry includes the following parameters:
流绑定可以看作是一个概念性的条目列表，与绑定缓存分离。流绑定列表包含每个已注册流绑定的条目。流绑定条目通过BID指向绑定缓存中的条目。每个流绑定条目包括以下参数：
o FID (Flow Identifier): For a given mobile node, identified by its primary home address, the FID MUST uniquely identify an entry, i.e., a unique flow binding. Each mobile node can only have a single entry identified by a given FID at any one time. A given FID number space is used for all the addresses associated to a given MN by the HA (e.g., via [RFC3963]). Different mobile nodes use the same FID number space.
o FID（流标识符）：对于给定的移动节点，由其主家庭地址标识，FID必须唯一标识一个条目，即唯一的流绑定。每个移动节点在任何时候都只能有一个由给定FID标识的条目。给定的FID编号空间用于HA（例如，通过[RFC3963]）与给定MN关联的所有地址。不同的移动节点使用相同的FID编号空间。
o A Traffic Selector: Included in a traffic selector sub-option.
o 交通选择器：包含在交通选择器子选项中。
o BID(s): The list of BIDs associated with the entry as defined by the binding reference sub-option included in the FID option that created it.
o 投标：与条目相关的投标列表，由创建该条目的FID选项中包含的约束参考子选项定义。
o Active/Inactive flag: This flag indicates whether the entry is active or inactive.
o 活动/非活动标志：此标志指示条目是活动的还是非活动的。
o FID-PRI: This field indicates the priority of the flow binding and is used to break the tie between overlapping flow bindings.
o FID-PRI：此字段指示流绑定的优先级，用于断开重叠流绑定之间的连接。
The flow bindings list is associated with a given mobile node, and the correspondent binding cache. An entry in the flow bindings list, however, is identified by the FID and the list is ordered according to the FID-PRI field as defined in the FID option that created each entry.
流绑定列表与给定的移动节点以及相应的绑定缓存相关联。但是，流绑定列表中的条目由FID标识，并且该列表根据创建每个条目的FID选项中定义的FID-PRI字段排序。
A valid BID is required to make the entry 'Active'. If all of the BIDs pointed to by a given entry are deregistered [RFC5648], the flow binding entry becomes 'Inactive', in other words it does not affect data traffic. Note that an entry becomes 'Inactive' only if all of the BIDs are deregistered. If only some of the BIDs are still valid, the invalid BIDs are simply ignored.
需要有效的投标才能使条目“有效”。如果取消注册给定条目指向的所有出价[RFC5648]，则流绑定条目将变为“非活动”，换句话说，它不会影响数据流量。请注意，只有在取消所有投标时，条目才会变为“非活动”。如果只有部分投标仍然有效，则将忽略无效投标。
Also, note that the state described in this section is maintained by the mobile node as well as in mobility agents and correspondent nodes. As such, the mobile node is fully aware of which BIDs are valid at any time and which flow binding entries are active/inactive. Section 5 defines how these flow binding entries are manipulated by the mobile node in detail.
另外，请注意，本节中描述的状态由移动节点以及移动代理和对应节点维护。因此，移动节点在任何时候都完全知道哪些出价是有效的，哪些流绑定条目是活动的/非活动的。第5节详细定义了移动节点如何操作这些流绑定条目。
As an example, the following represents an ordered flow binding entry table for a mobile node that has registered multiple care-of addresses and flow bindings.
例如，以下内容表示已注册多个转交地址和流绑定的移动节点的有序流绑定条目表。
FID-PRI FID Traffic Selector BIDs A/I
------- --- ---------------- ---- -------
10 4 TCP 2 Active
30 2 srcAddr=IPy 4 Inactive
40 5 UDP 1,3 Active
FID-PRI FID Traffic Selector BIDs A/I
------- --- ---------------- ---- -------
10 4 TCP 2 Active
30 2 srcAddr=IPy 4 Inactive
40 5 UDP 1,3 Active
Ordered Flow Binding Entries
有序流绑定条目
According to the above list of flow binding entries, all TCP traffic will match the first entry, and will be forwarded to BID2, corresponding to a given care-of address (IP3), as shown below.
根据上面的流绑定条目列表，所有TCP流量将与第一个条目匹配，并将转发给BID2，对应于给定的转交地址（IP3），如下所示。
The second entry is marked as 'Inactive' since the BID 4 does not exist in the ordered list of BID entries below. Inactive entries do not affect traffic, i.e., packets are not matched against them.
第二个条目标记为“未激活”，因为投标4不存在于以下投标条目的有序列表中。非活动条目不会影响流量，即，数据包不会与它们匹配。
Any UDP traffic that does not match any of the earlier entries will match the third rule, at which point it will be replicated and forwarded to BIDs 1 and 3, corresponding to care-of addresses IP1 and IP2 shown below.
任何与任何早期条目不匹配的UDP通信都将与第三条规则匹配，此时它将被复制并转发到BIDs 1和3，对应于下面显示的转交地址IP1和IP2。
Finally, any remaining packets that do not match any of the entries above will be simply forwarded to the care-of address indicated by the highest order BID in the table below. In the example, such packets will be forwarded to BID1 corresponding to care-of address IP1.
最后，与上述任何条目不匹配的任何剩余数据包将被简单地转发到下表中最高顺序出价指示的转交地址。在该示例中，此类分组将被转发到对应于转交地址IP1的BID1。
BID-PRI BID CoA
--------- --- ---
20 1 IP1
30 3 IP2
30 2 IP3
BID-PRI BID CoA
--------- --- ---
20 1 IP1
30 3 IP2
30 2 IP3
Ordered BID Entries
有序投标条目
Mobility agent and corresponding node implementations should take care to avoid flow binding rules affecting the fundamental operation of Mobile IPv6 and its extensions. In particular, flow binding rules MUST NOT apply to Mobile IPv6 signaling generated by mobility agents and corresponding nodes communicating with a given mobile node, since that could adversely affect the operation of the protocol. Other, non-MIPv6 traffic generated by these entities SHOULD be matched against the mobile node's flow binding rules as normal.
移动代理和相应的节点实现应注意避免流绑定规则影响移动IPv6及其扩展的基本操作。特别地，流绑定规则不得应用于由移动代理和与给定移动节点通信的对应节点生成的移动IPv6信令，因为这可能对协议的操作产生不利影响。其他由这些实体生成的非MIPv6流量应与移动节点的流绑定规则进行正常匹配。
This specification introduces a flow bindings list of entries and an ordered list of flow binding identifiers, allowing mobile nodes to associate flow binding policies with the registered care-of addresses.
该规范引入了条目的流绑定列表和流绑定标识符的有序列表，允许移动节点将流绑定策略与注册的转交地址相关联。
The flow identification mobility option defines how the mobile node can control a set of flow binding entries maintained in a mobility agent, or correspondent node.
流标识移动选项定义移动节点如何控制在移动代理或对应节点中维护的一组流绑定条目。
This specification allows mobile nodes to direct flows to a particular care-of address. The granularity of what constitutes a flow depends on the traffic selector used.
此规范允许移动节点将流定向到特定的转交地址。构成流的内容的粒度取决于所使用的流量选择器。
The remainder of this section discusses how mobile nodes can use the options and sub-options defined in this document when sending binding updates to the correspondent node, home agent, or mobility anchor point. In addition, refresh, deletion, and modification of flow binding entries are all discussed below.
本节的其余部分将讨论移动节点在向对应节点、归属代理或移动定位点发送绑定更新时如何使用本文档中定义的选项和子选项。此外，下面将讨论流绑定条目的刷新、删除和修改。
Any node that supports this specification MUST maintain an ordered list of care-of addresses for each mobile node for which it maintains a list of flow bindings. The ordered list of care-of addresses is built based on the BID-PRI field of the binding identifier mobility option (see Section 4.1).
支持此规范的任何节点都必须为其维护流绑定列表的每个移动节点维护一个有序的转交地址列表。转交地址的有序列表基于绑定标识符移动选项的BID-PRI字段构建（见第4.1节）。
The ordered list of BIDs is used to determine how to forward a packet to a given mobile node when the packet does not match any of the flow binding entries defined in Section 4.3. A packet that does not match any of the flow binding entries SHOULD be forwarded to the care-of address identified by the BID with the highest priority, i.e., lowest BID-PRI value.
当数据包与第4.3节中定义的任何流绑定条目不匹配时，有序的投标列表用于确定如何将数据包转发给给定的移动节点。不匹配任何流绑定条目的数据包应转发到具有最高优先级（即最低BID-PRI值）的BID标识的转交地址。
This specification allows the mobile node to maintain several bindings with its mobility agent and correspondent nodes, and it allows it to direct packets to different care-of addresses according to flow bindings.
该规范允许移动节点与其移动代理和对应节点保持多个绑定，并允许移动节点根据流绑定将数据包定向到不同的转交地址。
The mobility agent and correspondent node list of flow bindings is manipulated by the mobile node, via flow identification and flow summary mobility options included in binding update messages. Each flow binding update can add, modify, refresh, or delete a given binding. More than one flow identification mobility option MAY be included in the same binding update, but each of them MUST include a different FID. In other words, two flow identification options in the same message cannot be about the same flow binding.
移动节点通过绑定更新消息中包含的流标识和流摘要移动选项来操纵流绑定的移动代理和对应节点列表。每个流绑定更新都可以添加、修改、刷新或删除给定绑定。同一绑定更新中可能包含多个流标识移动性选项，但每个选项必须包含不同的FID。换句话说，同一消息中的两个流标识选项不能是关于同一个流绑定的。
All flow binding state MUST be refreshed in every binding update the mobile node sends. Any previously registered flow binding that is not included in a given binding update will be deleted. So, any flow bindings that are not added or modified by a flow identification mobility option, but have previously registered and need to be maintained, MUST be included in a flow summary mobility option.
必须在移动节点发送的每个绑定更新中刷新所有流绑定状态。任何以前注册的未包含在给定绑定更新中的流绑定都将被删除。因此，任何未通过流标识移动选项添加或修改的流绑定，但之前已注册并需要维护的流绑定，都必须包含在流摘要移动选项中。
This specification (see Section 4.1) updates the definition of the binding identifier mobility option, originally defined in [RFC5648]. According to this specification, the BID option includes a BID-PRI field assigning each registered care-of address a priority, and thus places them in an ordered list, as also described in Section 4.3.
本规范（见第4.1节）更新了最初在[RFC5648]中定义的绑定标识符移动选项的定义。根据本规范，BID选项包括一个BID-PRI字段，该字段为每个注册的转交地址分配优先级，并因此将其置于有序列表中，如第4.3节所述。
To ensure backwards compatibility with [RFC5648], for the purpose of this specification, the field BID-PRI MUST NOT be set to zero.
为确保与[RFC5648]向后兼容，就本规范而言，BID-PRI字段不得设置为零。
Receiver implementation of this specification will take a BID-PRI field of value zero as an indication that this is a BID option of the format defined in [RFC5648].
本规范的接收器实现将采用值为零的BID-PRI字段作为指示，表明这是[RFC5648]中定义格式的BID选项。
Mobile nodes supporting this specification MUST use the BID option format defined in Section 4.1. Mobile nodes MUST also register all care-of addresses using the updated BID option format, either in the same BU as any flow identification mobility options using them or in earlier BUs.
支持本规范的移动节点必须使用第4.1节中定义的投标选项格式。移动节点还必须使用更新的BID选项格式注册所有转交地址，或者在与使用它们的任何流标识移动选项相同的BU中，或者在更早的总线中。
When adding a new flow binding, a mobile node sends the flow identification mobility option in the binding update, with the FID field set to a value that is not already present in the list of flow binding entries maintained by the receiver. The care-of address(es) associated with each flow identification mobility option in the binding update must be logically registered by this binding update, or must have already been registered by the receiver of the binding update in an earlier binding update, as defined in Section 5.2.1.
当添加新的流绑定时，移动节点在绑定更新中发送流标识移动选项，FID字段设置为接收方维护的流绑定条目列表中尚未存在的值。与绑定更新中的每个流标识移动选项相关联的转交地址必须通过该绑定更新进行逻辑注册，或者必须已经由绑定更新的接收方在早期绑定更新中进行了注册，如第5.2.1节所定义。
The flow identification mobility option MUST include a unique flow identifier in the FID field. The FID need only be unique for the receiver of the binding update and for the same sender, i.e., the same FID can be used across different receivers of the binding update, for the same sender. The FID-PRI field is set to the desired unique priority of the FID, defining the order of the flow binding to be added in the list of flow binding entries, as defined in Section 4.3. The Status field is set to zero in all binding update messages.
流量标识移动选项必须在FID字段中包含唯一的流量标识符。FID只需对绑定更新的接收者和同一发送者是唯一的，即，同一FID可用于同一发送者的绑定更新的不同接收者。FID-PRI字段设置为FID所需的唯一优先级，定义了要添加到流绑定条目列表中的流绑定顺序，如第4.3节所定义。在所有绑定更新消息中，状态字段都设置为零。
Since this flow identification mobility option is requesting the addition of a new flow binding in the list of flow bindings maintained by the receiver, the mobile node MUST include exactly one traffic selector sub-option (see Section 4.2.1.4) describing the flow associated with the new flow binding. The TS Format field of the traffic selector sub-option MUST be set to the non-zero value of the format used by the mobile node.
由于此流标识移动选项请求在接收方维护的流绑定列表中添加新的流绑定，因此移动节点必须仅包括一个描述与新流绑定相关联的流的流量选择器子选项（参见第4.2.1.4节）。流量选择器子选项的TS格式字段必须设置为移动节点使用的格式的非零值。
The mobile node MUST also include exactly one BID reference sub-option (see Section 4.2.1.3) to associate the flow binding with a given set of BIDs and corresponding CoAs.
移动节点还必须包括一个投标参考子选项（见第4.2.1.3节），以将流绑定与给定的一组投标和相应的COA相关联。
Flow binding modification is essentially a process where parameters associated with an existing flow binding in the list of flow binding entries are replaced by parameters included in the flow identification mobility option, and the same FID is maintained. With this procedure, the mobile node can change the priority, the BID(s), and/or the traffic selector associated with a flow binding.
流绑定修改本质上是一个过程，其中流绑定条目列表中与现有流绑定相关的参数被流标识移动性选项中包含的参数替换，并保持相同的FID。通过该过程，移动节点可以改变与流绑定相关联的优先级、出价和/或流量选择器。
To modify an existing flow binding, the mobile node MUST send a binding update with a flow identification option, with the FID field set to one of the FID values already in the list of flow binding entries. The FID-PRI field MUST be set to the priority value for the flow binding entry. The Status field is set to zero since this option is in a binding update.
要修改现有的流绑定，移动节点必须发送带有流标识选项的绑定更新，并将FID字段设置为流绑定条目列表中已有的FID值之一。FID-PRI字段必须设置为流绑定条目的优先级值。由于此选项位于绑定更新中，因此状态字段设置为零。
The mobile node MAY include exactly one traffic selector sub-option (see Section 4.2.1.4) describing the updated flow to be associated with the flow binding. The mobile node MAY, however, omit the traffic selector sub-option if it wants the traffic selector currently associated with the flow binding entry identified by the FID field to be maintained.
移动节点可以仅包括一个业务选择器子选项（参见第4.2.1.4节），描述与流绑定关联的更新流。然而，如果移动节点希望保持当前与FID字段标识的流绑定条目相关联的业务选择器，则可以省略业务选择器子选项。
The mobile node MAY include exactly one binding reference sub-option (see Section 4.2.1.3) to associate the existing flow binding with a new set of CoAs. The mobile node MAY omit the binding reference sub-option if it wants the BIDs currently associated with the flow binding entry identified by the FID field to be maintained.
移动节点可以仅包括一个绑定参考子选项（参见第4.2.1.3节），以将现有流绑定与一组新的CoA相关联。如果移动节点希望保持当前与FID字段标识的流绑定条目相关联的出价，则可以省略绑定引用子选项。
Note that it is also possible for the mobile node to effectively modify the effect of a flow binding entry without actually changing the entry itself. This can be done by changing the CoA associated with a given BID, which is a process defined in detail in [RFC5648].
注意，移动节点也可以有效地修改流绑定条目的效果，而不实际更改条目本身。这可以通过更改与给定投标相关的CoA来实现，该过程在[RFC5648]中有详细定义。
When the mobile node sends a binding update, it MUST refresh all flow bindings it wants to maintain even if it does not want to change any of their parameters.
当移动节点发送绑定更新时，它必须刷新它想要维护的所有流绑定，即使它不想更改它们的任何参数。
To refresh an existing flow binding, the mobile node MUST send a binding update with a flow summary option. The flow summary option MUST include one or more FID fields, as indicated in Section 4.2.2. Each FID field included MUST be set to one of the FID values already in the list of flow binding entries. Each flow summary mobility option can identify up to 127 FIDs, so more than one such option can
要刷新现有流绑定，移动节点必须发送带有流摘要选项的绑定更新。流量汇总选项必须包括一个或多个FID字段，如第4.2.2节所示。包含的每个FID字段必须设置为流绑定条目列表中已有的FID值之一。每个流量汇总移动选项最多可识别127个FID，因此可以识别多个此类选项
be included in a binding update message as required. A given FID SHOULD NOT be included more than once in all of the flow summary mobility options included in a given binding update message.
根据需要包含在绑定更新消息中。给定的FID不应在给定绑定更新消息中包含的所有流摘要移动选项中包含多次。
Any flow bindings (active or inactive) that are not identified in a binding update will be removed from the list of flow binding entries.
绑定更新中未标识的任何流绑定（活动或非活动）将从流绑定条目列表中删除。
Note that any inactive flow bindings, i.e., flow bindings without associated BIDs that are marked as 'Inactive' in the list of flow binding entries (see Section 4.3), MUST also be refreshed, or modified, to be maintained. If they are not included in a BU message, they will be removed.
请注意，任何非活动流绑定，即在流绑定条目列表（参见第4.3节）中标记为“非活动”的没有关联投标的流绑定，也必须刷新或修改以进行维护。如果未包含在BU消息中，则会将其删除。
Removal of flow binding entries is performed implicitly by omission of a given FID from a binding update.
通过从绑定更新中省略给定的FID隐式地删除流绑定条目。
To remove a flow binding, the MN simply sends a binding update message that includes flow identification and flow summary mobility options for all the FIDs that need to be refreshed, modified, or added, and simply omits any FIDs that need to be removed.
要删除流绑定，MN只需发送一条绑定更新消息，该消息包括需要刷新、修改或添加的所有FID的流标识和流摘要移动选项，并且只需忽略任何需要删除的FID。
Note that a mobile node can also render a flow binding inactive by removing the BIDs associated with it, without removing the flow binding itself. The procedure for removing a BID is defined in detail in [RFC5648].
请注意，移动节点还可以通过删除与流绑定关联的出价而不删除流绑定本身，从而使流绑定处于非活动状态。[RFC5648]中详细规定了删除投标文件的程序。
When all the BIDs associated with a flow binding are removed, the flow binding MUST be marked as 'Inactive' in the list of flow binding entries, as shown in Section 4.3. In other words, the state associated with the flow binding MUST be maintained, but it no longer affects the mobile node's traffic. The MN can return an inactive flow binding to the active state by using the flow binding modification process, described in Section 5.2.2.2, to associate it again with one or more valid BIDs.
当删除与流绑定相关的所有投标时，流绑定必须在流绑定条目列表中标记为“非活动”，如第4.3节所示。换句话说，必须保持与流绑定关联的状态，但它不再影响移动节点的流量。MN可以使用第5.2.2.2节中描述的流绑定修改过程将非活动流绑定返回到活动状态，以将其再次与一个或多个有效投标关联。
This specification is compatible with the home registration procedures defined in [RFC3775] and [RFC5648]. More specifically, if the mobile node performs a deregistration in the [RFC3775] style, all of its bindings, including flow bindings are deleted. If the mobile node, however, performs a home registration in the [RFC5648] style, then the home link is associated with a specific BID and so, as far as this specification is concerned, it is treated as any other link associated with a given BID.
本规范与[RFC3775]和[RFC5648]中定义的家庭注册程序兼容。更具体地说，如果移动节点以[RFC3775]样式执行注销，则其所有绑定（包括流绑定）都将被删除。然而，如果移动节点以[RFC5648]样式执行归属注册，则归属链路与特定出价相关联，因此，就本规范而言，它被视为与给定出价相关联的任何其他链路。
According to [RFC3775], all nodes are required to silently ignore mobility options not understood while processing binding updates. As such, a mobile node receiving a Binding Acknowledgement message in response to the transmission of a binding update message MUST determine if the Binding Acknowledgement message contains a copy of every flow identification mobility options included in the binding update. A Binding Acknowledgement without flow identification option(s), in response to a binding update with flow identification mobility option, would indicate the inability (or unwillingness) on behalf of the source node to support the extensions presented in this document.
根据[RFC3775]，在处理绑定更新时，所有节点都需要静默地忽略未理解的移动选项。因此，响应于绑定更新消息的传输而接收绑定确认消息的移动节点必须确定绑定确认消息是否包含绑定更新中包括的每个流标识移动选项的副本。不带流标识选项的绑定确认，响应带有流标识移动选项的绑定更新，将表示源节点无法（或不愿意）支持本文档中提供的扩展。
If a received Binding Acknowledgement contains a copy of each flow identification mobility option that was sent within the binding update, the Status field of each flow identification option indicates the status of the flow binding on the distant node.
如果接收到的绑定确认包含绑定更新中发送的每个流标识移动选项的副本，则每个流标识选项的状态字段指示远程节点上的流绑定状态。
A mobile node may perform route optimization with correspondent nodes, as defined in [RFC3775]. Route optimization allows a mobile node to bind a care-of address to a home address in order to allow the correspondent node to direct the traffic to the current location of the mobile node. Before sending a binding update to correspondent node, the Return Routability Procedure needs to be performed between the mobile node and the correspondent node. This procedure is not affected by the extensions defined in this document.
如[RFC3775]中所定义，移动节点可与对应节点执行路由优化。路由优化允许移动节点将转交地址绑定到家庭地址，以便允许对应节点将通信量定向到移动节点的当前位置。在向对应节点发送绑定更新之前，需要在移动节点和对应节点之间执行返回路由程序。本程序不受本文档中定义的扩展的影响。
This specification allows the mobility agents (home agents and mobility anchor points), and correspondent nodes to maintain several flow bindings for a given home address and to direct packets to different care-of addresses according to flow bindings. This section details the home agent operations necessary to implement this specification. These operations are identical for MAPs and CNs, unless otherwise stated.
该规范允许移动代理（归属代理和移动锚定点）和对应节点为给定的归属地址维护多个流绑定，并根据流绑定将数据包定向到不同的转交地址。本节详细介绍了实施本规范所需的归属代理操作。除非另有说明，这些操作对于MAPs和CNs是相同的。
Note that route optimization is only defined for mobile nodes (MIPv6 [RFC3775]) and not mobile routers (NEMOv6 [RFC3963]). Thus, these sections only apply to correspondent nodes with respect to mobile nodes and not mobile routers.
注意，路由优化仅针对移动节点（MIPv6[RFC3775]）而非移动路由器（NEMOv6[RFC3963]）定义。因此，这些部分仅适用于移动节点的对应节点，而不适用于移动路由器。
This specification (see Section 4.1) updates the definition of the binding identifier mobility option, originally defined in [RFC5648]. According to this specification, the BID option includes a BID-PRI field assigning each registered care-of address a priority, and thus places them in an ordered list (see Section 4.3).
本规范（见第4.1节）更新了最初在[RFC5648]中定义的绑定标识符移动选项的定义。根据本规范，BID选项包括一个BID-PRI字段，为每个注册的转交地址分配一个优先级，从而将其置于有序列表中（见第4.3节）。
Home agents receiving BUs including BID options and flow identification options MUST logically process BID options first. This is because BID reference sub-options included in the flow identification mobility options might refer to BIDs defined in BID options included in the same message.
接收总线（包括投标选项和流标识选项）的家庭代理必须首先在逻辑上处理投标选项。这是因为流标识移动选项中包含的投标参考子选项可能引用同一消息中包含的投标选项中定义的投标。
The BID option is processed as defined in [RFC5648], but then the BID to care-of address mapping is placed in an ordered list according to the BID-PRI field of the BID option.
按照[RFC5648]中的定义处理BID选项，然后根据BID选项的BID-PRI字段将BID-to care地址映射放置在有序列表中。
Binding identifier registrations and deregistrations indirectly affect the MN's flow binding entries. The home agent MUST update the flow binding entries table accordingly as BIDs are added or removed (as per [RFC5648]). For example, as discussed in Section 4.3, if all of the BIDs associated with a given flow binding entry are removed (i.e., become invalid) the entry MUST be marked as 'Inactive'. While if any of the invalid BIDs associated with an inactive flow binding entry are registered (i.e., become valid), the entry MUST be marked as 'Active'.
绑定标识符注册和注销会间接影响MN的流绑定条目。在添加或删除标书时（根据[RFC5648]），主代理必须相应地更新流绑定条目表。例如，如第4.3节所述，如果与给定流绑定条目相关的所有投标被删除（即无效），则该条目必须标记为“非活动”。如果注册了与非活动流绑定条目相关联的任何无效投标（即生效），则该条目必须标记为“活动”。
When the home agent receives a binding update that includes at least one flow identification mobility option, it first performs the operation described in section 10.3.1 of RFC 3775, followed by the operations defined in Section 5.3.1 of this document.
当归属代理收到包含至少一个流标识移动选项的绑定更新时，它首先执行RFC 3775第10.3.1节中描述的操作，然后执行本文件第5.3.1节中定义的操作。
Home agents that do not support this specification will ignore the flow identification mobility options and all their sub-options, having no effect on the operation of the rest of the protocol.
不支持此规范的归属代理将忽略流标识移动选项及其所有子选项，对协议其余部分的操作没有影响。
If the binding update is accepted, and the home agent is willing to support flow bindings for this MN, the home agent checks the flow identification mobility options.
如果绑定更新被接受，并且归属代理愿意支持此MN的流绑定，则归属代理将检查流标识移动选项。
If more than one flow identification mobility option in the same BU has the same value in the FID field, all the flow identification mobility options MUST be rejected.
如果同一BU中的多个流量标识移动选项在FID字段中具有相同的值，则必须拒绝所有流量标识移动选项。
If all FID fields have different values the flow identification mobility options can be processed further and in any order, as defined by the following subsections.
如果所有FID字段具有不同的值，则可以按照以下小节的定义，以任何顺序进一步处理流量标识移动选项。
If the FID field of the flow identification mobility option is not already present in the list of flow binding entries for this mobile node, then this is a request for a new entry.
如果流标识移动选项的FID字段尚未出现在此移动节点的流绑定条目列表中，则这是对新条目的请求。
If the flow identification mobility option does not include a traffic selector sub-option, the home agent MUST reject this request by copying the flow identification mobility option in the Binding Acknowledgement (BA) and setting the Status field to the value defined in Figure 2 for "Flow identification option malformed".
如果流标识移动性选项不包括流量选择器子选项，则归属代理必须通过复制绑定确认（BA）中的流标识移动性选项并将状态字段设置为图2中为“流标识选项格式错误”定义的值来拒绝此请求。
If the flow identification option does include a traffic selector sub-option, but the format indicated in the TS Format field is not supported, the home agent MUST reject this request by copying the flow identification mobility option in the BA, and setting the Status field to the value defined in Figure 2 for "Traffic Selector format not supported".
如果流标识选项确实包含流量选择器子选项，但不支持TS格式字段中指示的格式，则归属代理必须通过复制BA中的流标识移动选项，并将状态字段设置为图2中定义的值来拒绝此请求“不支持流量选择器格式”。
Then, the home agent MUST check the binding reference sub-option.
然后，归属代理必须检查绑定引用子选项。
If the binding reference sub-option is not included, the home agent MUST reject this request by copying the flow identification mobility option in the BA and setting the Status field to the value defined for "Flow identification mobility option malformed" in Section 4.2.
如果未包括绑定参考子选项，则归属代理必须通过复制BA中的流标识移动选项并将状态字段设置为第4.2节中为“流标识移动选项格式错误”定义的值来拒绝该请求。
If the binding reference sub-option is present and includes one or more BIDs that are not present in the binding cache of the mobile node, the home agent MUST reject this request by copying the flow identification option in the BA and setting the Status field to the value defined for "BID not found" in Section 4.2.
如果绑定引用子选项存在，并且包括移动节点的绑定缓存中不存在的一个或多个出价，则归属代理必须通过复制BA中的流标识选项并将状态字段设置为第4.2节中为“未找到出价”定义的值来拒绝该请求。
If the binding reference sub-option is present and includes one or more BIDs, and the BIDs exist in the mobile node's binding cache, the home agent SHOULD add a new entry in the mobile node's list of flow binding entries, as defined below.
如果存在绑定引用子选项并且包含一个或多个出价，并且出价存在于移动节点的绑定缓存中，则归属代理应在移动节点的流绑定条目列表中添加一个新条目，如下所述。
When the home agent decides to add an entry in the mobile node's list of flow binding entries, as discussed above, it MUST do it according to the following rules: the entry MUST be placed according to the order indicated by the FID-PRI field of the flow identification mobility option and it MUST include:
如上文所述，当归属代理决定在移动节点的流绑定条目列表中添加条目时，它必须按照以下规则进行：条目必须按照流标识移动选项的FID-PRI字段指示的顺序放置，并且必须包括：
the FID as a key to the entry,
FID作为入口的钥匙，
the traffic selector included in the corresponding sub-option,
包含在相应子选项中的交通选择器，
the BIDs indicated in the binding reference sub-option, and
约束性参考子选项中所示的标书，以及
the entry MUST be marked as 'Active', as shown in Section 4.3.
条目必须标记为“活动”，如第4.3节所示。
If the FID field of the flow identification mobility option is already present in the list of flow binding entries for this mobile node, then this is a request to update the existing entry.
如果流标识移动选项的FID字段已经存在于该移动节点的流绑定条目列表中，则这是更新现有条目的请求。
The flow binding modification is essentially a process where parameters associated with an existing flow binding entry are replaced by the parameters included in a flow identification mobility option with the same FID as the existing entry.
流量绑定修改实质上是一个过程，其中与现有流量绑定条目相关的参数被包含在与现有条目具有相同FID的流量标识移动性选项中的参数替换。
The home agent MUST change the priority of the entry according to the FID-PRI field of the flow identification mobility option.
归属代理必须根据流标识移动选项的FID-PRI字段更改条目的优先级。
Since this flow identification mobility option is designed to update an existing entry, it may or may not include a traffic selector sub-option. Specifically:
由于此流量标识移动选项旨在更新现有入口，因此它可能包括也可能不包括流量选择器子选项。明确地：
if a traffic selector sub-option is not included in the flow identification mobility option, then the traffic selector already associated with entry MUST be maintained;
如果流量识别移动选项中不包括交通选择器子选项，则必须维护已与入口关联的交通选择器；
otherwise, the traffic selector in the entry MUST be replaced by the traffic selector in the sub-option.
否则，条目中的交通选择器必须替换为子选项中的交通选择器。
Since this flow identification mobility option is designed to update an existing entry, it may or may not include a binding reference sub-option. Specifically:
由于此流标识移动性选项旨在更新现有条目，因此它可能包括也可能不包括绑定参考子选项。明确地：
if a binding reference sub-option is not included in the flow identification mobility option, then the BIDs already associated with entry MUST be maintained;
如果流标识移动性选项中未包含具有约束力的参考子选项，则必须保留已经与进入相关联的投标；
otherwise, the BIDs in the entry MUST be replaced by the BIDs in the sub-option.
否则，条目中的投标必须替换为子选项中的投标。
When the home agent receives a binding update that includes flow summary mobility options, it first performs the operation described so far in Section 5.3.
当归属代理收到包含流摘要移动选项的绑定更新时，它首先执行第5.3节中描述的操作。
If the value of any of the FID fields included in a flow summary mobility option is not present in the list of flow binding entries for this mobile node, the home agent MUST reject this flow binding refresh by including a flow identification mobility option in the BA for each FID that is not found, and by setting the FID field to the value of the FID that is not found and the Status field to the value defined for "FID not found" in Section 4.2.
如果包含在流摘要移动选项中的任何FID字段的值不存在于该移动节点的流绑定条目列表中，则归属代理必须通过在BA中包含未找到的每个FID的流标识移动选项来拒绝该流绑定刷新，通过将FID字段设置为未找到的FID值，将状态字段设置为第4.2节中为“未找到FID”定义的值。
If the value of the FID field is present in the mobile nodes list of flow binding entries the, home agent SHOULD refresh the flow binding entry identified by the FID without changing any of the other parameters associated with it.
如果FID字段的值出现在流绑定条目的移动节点列表中，则归属代理应刷新FID标识的流绑定条目，而不更改与之相关的任何其他参数。
If a given FID is included more than once in the same or different flow summary mobility options in the same binding update message, the duplicates can be simply ignored.
如果给定的FID多次包含在同一绑定更新消息中相同或不同的流摘要移动选项中，则可以忽略重复项。
Note that, an [RFC3775] deregistration binding update (with a zero lifetime) would result in deleting all bindings, including all flow bindings regardless of the presence of flow summary mobility options. A binding update (with a zero lifetime) would result in deleting all bindings, including all flow bindings regardless of the presence of flow summary mobility options. A specific binding deregistration, however, as defined in [RFC5648] (with lifetime of zero and one or more binding identifier mobility options identifying specific BIDs) does not remove all the bindings for the MN, and thus it SHOULD include flow summary mobility options to maintain the flow bindings that need to be preserved.
请注意，[RFC3775]注销绑定更新（使用零生存期）将导致删除所有绑定，包括所有流绑定，而不管是否存在流摘要移动选项。绑定更新（使用零生存期）将导致删除所有绑定，包括所有流绑定，而不管是否存在流摘要移动选项。但是，如[RFC5648]中所定义的特定绑定取消注册（生命周期为零，一个或多个绑定标识符移动选项标识特定出价）不会删除MN的所有绑定，因此它应该包括流摘要移动选项，以维护需要保留的流绑定。
Removal of flow bindings is performed implicitly by omission of a given FID from a binding update.
流绑定的删除是通过在绑定更新中省略给定的FID隐式执行的。
When a valid binding update is received, any registered FIDs that are not explicitly referred to in a flow identification mobility option or in a flow summary mobility option, in the same binding update, MUST be removed from the list of flow binding entries for the mobile node.
当接收到有效的绑定更新时，必须从移动节点的流绑定条目列表中删除流标识移动选项或流摘要移动选项中未明确提及的任何注册FID。
Upon the reception of a binding update, the home agent is required to send back a Binding Acknowledgement. The status code in the Binding Acknowledgement must be set as recommended in [RFC3775]. This status code does not give information on the success or failure of flow bindings.
在接收到绑定更新后，归属代理需要发回绑定确认。必须按照[RFC3775]中的建议设置绑定确认中的状态代码。此状态代码不提供流绑定成功或失败的信息。
In order to inform the mobile node about the status of the flow binding(s) requested by a mobile node, flow identification options SHOULD be included in the Binding Acknowledgement message. Specifically, the home agent SHOULD copy each flow identification mobility option received in the binding update and set its status code to an appropriate value. Note that the home agent does not need to respond specifically regarding FIDs included in a flow summary mobility option but only to those in flow identification mobility options. If an operation requested in a flow identification option by a mobile node is performed successfully by the home agent, the Status field on the copied flow identification mobility option in the BA, SHOULD be set to the value defined for "Flow binding successful" in Section 4.2; otherwise, it SHOULD be set to one of the rejection codes also defined in Section 4.2. Section 5.3.2 identifies a number of cases where specific error codes should be used.
为了向移动节点通知移动节点请求的流绑定的状态，绑定确认消息中应包括流标识选项。具体而言，归属代理应复制在绑定更新中接收的每个流标识移动选项，并将其状态代码设置为适当的值。注意，归属代理不需要具体地响应包括在流摘要移动性选项中的fid，而只需要响应流标识移动性选项中的fid。如果移动节点在流标识选项中请求的操作由归属代理成功执行，则BA中复制的流标识移动选项上的状态字段应设置为第4.2节中为“流绑定成功”定义的值；否则，应将其设置为第4.2节中定义的拒收代码之一。第5.3.2节确定了一些应使用特定错误代码的情况。
Home agents that support this specification MAY refuse to maintain flow bindings by setting the Status field of any flow identification mobility options to the value defined for "Administratively prohibited" in Section 4.2, or by just ignoring all the flow binding options.
支持本规范的家庭代理可以通过将任何流标识移动选项的状态字段设置为第4.2节中为“管理禁止”定义的值，或通过忽略所有流绑定选项，来拒绝维护流绑定。
Note that BID options and their Status field are handled as defined in [RFC5648]. The BID-PRI field in a BID option included in the Binding Acknowledgement is copied from the BID-PRI field of the corresponding BID option in the binding request.
请注意，投标选项及其状态字段按照[RFC5648]中的定义进行处理。约束性确认中包含的投标选项中的BID-PRI字段从约束性请求中相应投标选项的BID-PRI字段复制而来。
This section defines packet processing rules according to this specification. This specification does not change any of the packet interception rules defined in [RFC3775] and [RFC5555]. These rules apply to HAs, MAPs, and CNs as part of the routing process for any packet with a destination address set to a valid home address of the mobile node. For nodes other than CNs, this also applies to packets with a destination address set to an address under any of the registered prefixes. These rules apply equally to IPv6 packets as well as to IPv4 packets as per [RFC5555].
本节根据本规范定义数据包处理规则。本规范不改变[RFC3775]和[RFC5555]中定义的任何数据包拦截规则。这些规则适用于HAs、MAPs和CNs，作为目的地地址设置为移动节点有效家庭地址的任何数据包的路由过程的一部分。对于CNs以外的节点，这也适用于目标地址设置为任何已注册前缀下的地址的数据包。根据[RFC5555]，这些规则同样适用于IPv6数据包以及IPv4数据包。
Before a packet is forwarded to the mobile node, it MUST be matched against the ordered list of flow bindings stored in the list of flow binding entries for this mobile node (see Section 4.3). A match is attempted with the traffic selector included in the first line (highest order) of the table. The first entry that creates a match defines how the packet is routed. When a packet matches the traffic selector of a given entry, a copy of the packet is forwarded to each of the care-of addresses associated with the BIDs indicated in the same line of the table.
在将数据包转发到移动节点之前，它必须与存储在该移动节点的流绑定条目列表中的流绑定有序列表相匹配（参见第4.3节）。尝试使用表的第一行（最高顺序）中包含的流量选择器进行匹配。创建匹配项的第一个条目定义如何路由数据包。当数据包与给定条目的流量选择器匹配时，数据包的副本被转发到与表的同一行中指示的投标相关联的每个转交地址。
If any of the BIDs indicated does not correspond to a valid care-of address, e.g., the BID was deregistered then, that BID has no effect on the traffic. In other words, packets matching the flow binding are forwarded to the remaining BIDs, pointing to registered care-of addresses. If none of the BIDs pointed to in a flow binding entry is valid, then the entry is considered to be inactive (as defined in Section 4.3) and is skipped. In other words, packets should not be matched against that entry.
如果所示的任何投标不符合有效的转交地址，例如，该投标当时已注销，则该投标对交通没有影响。换句话说，匹配流绑定的数据包被转发到剩余的出价，指向已注册的转交地址。如果流绑定条目中所指的所有投标均无效，则该条目被视为无效（如第4.3节所定义），并被跳过。换句话说，数据包不应与该条目匹配。
If a packet does not match any of the active flow binding entries for the given MN, the packet SHOULD be forwarded to the highest order care-of address, i.e., the one associated with the BID with the lowest BID-PRI.
如果分组与给定MN的任何活动流绑定条目不匹配，则分组应转发到最高顺序的转交地址，即与具有最低BID-PRI的BID相关联的地址。
If a packet is fragmented, only the first fragment contains all IP and transport layer headers, while subsequent fragments only contain an IP header without transport layer headers. For this reason, it is possible that subsequent fragments do not match the same traffic selector as the initial fragment of such a packet. Unless specific measures are taken, the likely outcome is that the initial fragment is routed as the MN intended while subsequent fragments are routed differently, and probably based on the default flow binding. HAs, MAPs, and CNs SHOULD take care to forward all fragments of a given packet the same way, and in accordance to the flow binding matching the first fragment of said packet. This should be possible given the fact that fragment headers include enough information to identify a fragment as part of a specific packet, but the details of how this is ensured are implementation specific and are not defined in this specification.
如果数据包是分段的，则只有第一个片段包含所有IP和传输层头，而后续片段仅包含不包含传输层头的IP头。出于这个原因，后续片段可能与此类数据包的初始片段不匹配相同的流量选择器。除非采取具体措施，否则可能的结果是初始片段按照MN的预期路由，而后续片段的路由则不同，并且可能基于默认的流绑定。HAs、MAPs和CNs应注意以相同的方式转发给定数据包的所有片段，并根据与所述数据包的第一个片段匹配的流绑定。这应该是可能的，因为片段头包含足够的信息来识别作为特定数据包一部分的片段，但是如何确保这一点的细节是特定于实现的，并且没有在本规范中定义。
The options and sub-options defined in this specification add to those defined in [RFC3775] and other related specifications, all of which potentially add to the size of binding update messages. Implementations SHOULD take care to minimize fragmentation by forming binding updates that are shorter than what the path MTU allows whenever possible.
本规范中定义的选项和子选项添加到[RFC3775]和其他相关规范中定义的选项和子选项，所有这些都可能增加绑定更新消息的大小。实现应尽可能通过形成比MTU允许的路径更短的绑定更新来尽量减少碎片。
This specification offers a number of mechanisms for reducing the size of binding updates. The operations defined in this specification that require the most verbose options are those registering new BIDs, Section 4.1, and identifying new flows, Section 4.2.1.4. Implementations are encouraged to keep binding updates to sizes below that of the path's MTU by making full use of the BID reference sub-option, Section 4.2.1.3, and flow summary option, Section 4.2.2, which allows them to refer to already registered care-of addresses and flow bindings, while registering new ones in subsequent binding update messages.
该规范提供了许多减少绑定更新大小的机制。本规范中定义的需要最详细选项的操作是注册新投标（第4.1节）和识别新流程（第4.2.1.4节）。通过充分利用第4.2.1.3节“投标参考”子选项和第4.2.2节“流量汇总”选项，鼓励实施将绑定更新保持在路径MTU的大小以下，这允许它们参考已注册的转交地址和流量绑定，在随后的绑定更新消息中注册新的绑定更新消息时。
This document introduces a new option that adds more granularity to the binding update and acknowledgement messages defined in [RFC3775], [RFC5555], and [RFC3963], so it inherits the security considerations discussed in these documents. The new option allows the mobile node to associate some flows to one interface and other flows to another interface. Since the flow identification mobility option is part of the mobility header, it uses the same security as the binding update, whether it is sent to a mobility agent or to a correspondent node.
本文档引入了一个新选项，该选项为[RFC3775]、[RFC5555]和[RFC3963]中定义的绑定更新和确认消息添加了更多粒度，因此它继承了这些文档中讨论的安全注意事项。新选项允许移动节点将一些流关联到一个接口，将其他流关联到另一个接口。由于流标识移动选项是移动报头的一部分，因此它使用与绑定更新相同的安全性，无论是发送到移动代理还是发送到对应节点。
This specification does not open up new fundamental lines of attack on communications between the MN and its correspondent nodes. However, it allows attacks of a finer granularity than those on the binding update. For instance, the attacker can divert or replicate flows of special interest to the attacker to an address of the attacker's choosing, if the attacker is able to impersonate the MN or modify a binding update sent by the MN. Hence, it becomes doubly critical that authentication and integrity services are applied to binding updates.
该规范不会对MN及其对应节点之间的通信打开新的基本攻击线。但是，它允许比绑定更新更细粒度的攻击。例如，如果攻击者能够模拟MN或修改MN发送的绑定更新，则攻击者可以将攻击者特别感兴趣的流转移或复制到攻击者选择的地址。因此，将身份验证和完整性服务应用于绑定更新变得更加重要。
Finally, when the optional anti-replay feature of Encapsulating Security Payload (ESP) [RFC4303] is employed and packets to/from different CoAs are sent on the same security association (SA), some packets could be discarded at the receiver due to the windowing mechanism used by this feature. Therefore, a sender SHOULD put traffic to/from different CoAs, but with the same HoA in the selector values, on different SAs to support Multiple Care-of Addresses appropriately. To permit this, the IPsec implementation SHOULD establish and maintain multiple SAs between a given sender and receiver, with the same selectors. Distribution of traffic among these parallel SAs to support Multiple Care-of Addresses is locally determined by the sender and is not negotiated by the Internet Key Exchange version 2 (IKEv2) protocol [RFC5996]. The receiver will process the packets from the different SAs without prejudice.
最后，当采用封装安全有效载荷（ESP）[RFC4303]的可选反重放功能，并且在同一安全关联（SA）上发送来自不同CoA的数据包时，由于该功能使用的窗口机制，一些数据包可能在接收器处被丢弃。因此，发送方应在不同的SA上设置不同CoA之间的通信量，但选择器值中的HoA相同，以适当地支持多个转交地址。为了实现这一点，IPsec实现应该使用相同的选择器在给定的发送方和接收方之间建立和维护多个SA。这些并行SA之间支持多个转交地址的流量分布由发送方在本地确定，而不是由Internet密钥交换版本2（IKEv2）协议[RFC5996]协商。接收器将处理来自不同SA的数据包，而不会产生任何影响。
This specification requires the following IANA assignments on existing namespaces as well as the creation of some new namespaces.
该规范要求对现有名称空间进行以下IANA分配，以及创建一些新的名称空间。
New Mobility Options [RFC3775]: This registry is available from http://www.iana.org under "Mobile IPv6 parameters". The following type numbers have been assigned for:
新移动选项[RFC3775]：此注册表可从http://www.iana.org 在“移动IPv6参数”下。以下类型编号已分配给：
44 Flow Identification Mobility Option, defined in Section 4.2
44第4.2节中定义的流量识别移动选项
45 Flow Summary Mobility Option, defined in Section 4.2.2
45第4.2.2节中定义的流量汇总流动选项
A new "Flow Identification Mobility Option Status Codes" namespace has been created. The following 'Status' codes are defined in this specification, in Section 4.2:
创建了一个新的“流标识移动选项状态代码”命名空间。本规范第4.2节定义了以下“状态”代码：
0 Flow binding successful
0流绑定成功
1-127 Unassigned. Available for success codes to be allocated via Standards Action or IESG Approval as per [RFC5226].
1-127未分配。根据[RFC5226]，可通过标准行动或IESG批准分配成功代码。
128 Administratively prohibited
128行政禁止
129 Flow binding rejected, reason unspecified
129流绑定被拒绝，原因不明
130 Flow identification mobility option malformed
130流标识移动选项格式不正确
131 BID not found
131未找到投标书
132 FID not found
132未找到FID
133 Traffic selector format not supported
133不支持流量选择器格式
134-250 Unassigned. Available for reject codes to be allocated via Standards Action or IESG Approval as per [RFC5226].
134-250未分配。可用于根据[RFC5226]通过标准行动或IESG批准分配的拒收代码。
251-255 Reserved for experimental use. This small number of status codes should be sufficient for experiments with currently unforeseen error conditions.
251-255保留供实验使用。这少量的状态代码应足以用于当前无法预见的错误条件下的实验。
A new "Flow Identification Sub-Options" namespace for the flow identification mobility option has been created. The sub-option space is defined in Figure 3. The following sub-option Type values are defined in this specification:
为流标识移动选项创建了一个新的“流标识子选项”命名空间。子选项空间如图3所示。本规范中定义了以下子选项类型值：
0 Pad
0垫
1 PadN
1 PadN
2 BID Reference
2投标参考
3 Traffic Selector
3交通选择器
4-250 Unassigned. Available for allocation based on Standards Action or IESG Approval as per [RFC5226].
4-250未分配。可根据[RFC5226]的标准行动或IESG批准进行分配。
251-255 Reserved for experimental use. This small number of sub-option Types should be sufficient for experiments with additional parameters associated with a flow.
251-255保留供实验使用。这一小部分子选项类型应足以进行与流量相关的附加参数实验。
A new "Traffic Selector Format" namespace for the traffic selector sub-option has been created. The traffic selector format space is defined by the TS Format field in Figure 5. The following values are defined in this specification:
已为Traffic Selector子选项创建新的“Traffic Selector Format”命名空间。交通选择器格式空间由图5中的TS format字段定义。本规范中定义了以下值：
0 Reserved
0保留
1-250 Unassigned. Available for allocation based on Standards Action or IESG Approval as per [RFC5226].
1-250未分配。可根据[RFC5226]的标准行动或IESG批准进行分配。
251-255 Reserved for experimental use. This small number of traffic selector format types should be sufficient for experiments with different ways of representing a traffic selector.
251-255保留供实验使用。这少量的流量选择器格式类型应足以用于以不同方式表示流量选择器的实验。
Similar to the procedures specified for Mobile IPv6 [RFC3775] number spaces, future allocations from the new number spaces requires Standards Action or IESG Approval as per [RFC5226].
与为移动IPv6[RFC3775]号码空间指定的程序类似，新号码空间的未来分配需要按照[RFC5226]的标准行动或IESG批准。
We would like to explicitly acknowledge the following person who coauthored one of the documents used as source material for this document.
我们要明确确认以下人员，他们共同编写了一份用作本文件源材料的文件。
Nikolaus A. Fikouras, niko@comnets.uni-bremen.de
尼古拉斯·菲库拉斯，niko@comnets.uni-不来梅
We would also like to acknowledge the following people in alphabetical order for their contributions to this specification: C. Castelluccia, D. Craig, K. ElMalki, K. Georgios, C. Goerg, C. Kaas-Petersen, J. Laganier, T. Noel, V. Park, F.-N. Pavlidou, P. Stupar. Also, Gabor Fekete for the analysis that led to the inclusion of the BID reference sub-option, and Henrik Levkowetz for suggesting support for other ways of describing flows.
我们还要按照字母顺序感谢以下人士对本规范的贡献：C.Castelluccia、D.Craig、K.ElMalki、K.Georgios、C.Goerg、C.Kaas Petersen、J.Laganier、T.Noel、V.Park、F.-N.Pavlidou、P.Stupar。此外，Gabor Fekete对导致包含投标参考子选项的分析表示感谢，Henrik Levkowetz对描述流量的其他方式表示支持。
[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月。
[RFC3775] Johnson, D., Perkins, C., and J. Arkko, "Mobility Support in IPv6", RFC 3775, June 2004.
[RFC3775]Johnson，D.，Perkins，C.，和J.Arkko，“IPv6中的移动支持”，RFC 37752004年6月。
[RFC3963] Devarapalli, V., Wakikawa, R., Petrescu, A., and P. Thubert, "Network Mobility (NEMO) Basic Support Protocol", RFC 3963, January 2005.
[RFC3963]Devarapalli，V.，Wakikawa，R.，Petrescu，A.，和P.Thubert，“网络移动（NEMO）基本支持协议”，RFC 3963，2005年1月。
[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月。
[RFC5555] Soliman, H., "Mobile IPv6 Support for Dual Stack Hosts and Routers", RFC 5555, June 2009.
[RFC5555]Soliman，H.，“双栈主机和路由器的移动IPv6支持”，RFC 55552009年6月。
[RFC5648] Wakikawa, R., Devarapalli, V., Tsirtsis, G., Ernst, T., and K. Nagami, "Multiple Care-of Addresses Registration", RFC 5648, October 2009.
[RFC5648]Wakikawa，R.，Devarapalli，V.，Tsirtsis，G.，Ernst，T.，和K.Nagami，“多重托管地址注册”，RFC 5648，2009年10月。
[RFC6088] Tsirtsis, G., Giaretta, G., Soliman, H., and N. Montavont, "Traffic Selectors for Flow Bindings", RFC 6088, January 2011.
[RFC6088]Tsirtsis，G.，Giaretta，G.，Soliman，H.，和N.Montavont，“流绑定的流量选择器”，RFC 6088，2011年1月。
[RFC2702] Awduche, D., Malcolm, J., Agogbua, J., O'Dell, M., and J. McManus, "Requirements for Traffic Engineering Over MPLS", RFC 2702, September 1999.
[RFC2702]Awduche，D.，Malcolm，J.，Agogbua，J.，O'Dell，M.，和J.McManus，“MPLS上的流量工程要求”，RFC 2702，1999年9月。
[RFC3753] Manner, J. and M. Kojo, "Mobility Related Terminology", RFC 3753, June 2004.
[RFC3753]Way，J.和M.Kojo，“机动性相关术语”，RFC 3753，2004年6月。
[RFC4303] Kent, S., "IP Encapsulating Security Payload (ESP)", RFC 4303, December 2005.
[RFC4303]Kent，S.，“IP封装安全有效载荷（ESP）”，RFC 4303，2005年12月。
[RFC4885] Ernst, T. and H-Y. Lach, "Network Mobility Support Terminology", RFC 4885, July 2007.
[RFC4885]Ernst，T.和H-Y.Lach，“网络移动性支持术语”，RFC 48852007年7月。
[RFC5380] Soliman, H., Castelluccia, C., ElMalki, K., and L. Bellier, "Hierarchical Mobile IPv6 (HMIPv6) Mobility Management", RFC 5380, October 2008.
[RFC5380]Soliman，H.，Castelluccia，C.，ElMalki，K.，和L.Bellier，“分层移动IPv6（HMIPv6）移动性管理”，RFC 53802008年10月。
[RFC5996] Kaufman, C., Hoffman, P., Nir, Y., and P. Eronen, "Internet Key Exchange Protocol Version 2 (IKEv2)", RFC 5996, September 2010.
[RFC5996]Kaufman，C.，Hoffman，P.，Nir，Y.，和P.Eronen，“互联网密钥交换协议版本2（IKEv2）”，RFC 59962010年9月。
Authors' Addresses
作者地址
George Tsirtsis Qualcomm
George Tsirtsis高通公司
EMail: tsirtsis@qualcomm.com
EMail: tsirtsis@qualcomm.com
Hesham Soliman Elevate Technologies
Hesham Soliman提升技术公司
EMail: hesham@elevatemobile.com
EMail: hesham@elevatemobile.com
Nicolas Montavont Institut Telecom / Telecom Bretagne 2, rue de la chataigneraie Cesson Sevigne 35576 France
Nicolas Montavont Institut Telecom/Telecom Bretagne 2，法国塞森塞维涅Chataignae街35576号
Phone: (+33) 2 99 12 70 23
EMail: nicolas.montavont@telecom-bretagne.eu
URI: http://www.rennes.enst-bretagne.fr/~nmontavo//
Phone: (+33) 2 99 12 70 23
EMail: nicolas.montavont@telecom-bretagne.eu
URI: http://www.rennes.enst-bretagne.fr/~nmontavo//
Gerardo Giaretta Qualcomm
Gerardo Giaretta高通公司
EMail: gerardog@qualcomm.com
EMail: gerardog@qualcomm.com
Koojana Kuladinithi University of Bremen ComNets-ikom Otto-Hahn-Allee NW 1 Bremen, Bremen 28359 Germany
KojaaKuldaythi不来梅大学CiNETIKM Otto Hahan-AlLee NW 1不来梅，不来梅28359德国
Phone: +49-421-218-8264
Fax: +49-421-218-3601
EMail: koo@comnets.uni-bremen.de
URI: http://www.comnets.uni-bremen.de/~koo/
Phone: +49-421-218-8264
Fax: +49-421-218-3601
EMail: koo@comnets.uni-bremen.de
URI: http://www.comnets.uni-bremen.de/~koo/