Independent Submission H. Yokota
Request for Comments: 7109 KDDI Lab
Category: Experimental D. Kim
ISSN: 2070-1721 JEJU Technopark
B. Sarikaya
F. Xia
Huawei
February 2014
Independent Submission H. Yokota
Request for Comments: 7109 KDDI Lab
Category: Experimental D. Kim
ISSN: 2070-1721 JEJU Technopark
B. Sarikaya
F. Xia
Huawei
February 2014
Flow Bindings Initiated by Home Agents for Mobile IPv6
由移动IPv6的归属代理启动的流绑定
Abstract
摘要
There are scenarios in which the home agent needs to trigger flow binding operations towards the mobile node, such as moving a flow from one access network to another based on network resource availability. In order for the home agent to be able to initiate interactions for flow bindings with the mobile node, this document defines new signaling messages and sub-options for Mobile IPv6. Flow bindings initiated by a home agent are supported for mobile nodes enabled by both IPv4 and IPv6.
存在归属代理需要触发朝向移动节点的流绑定操作的场景，例如基于网络资源可用性将流从一个接入网络移动到另一个接入网络。为了使归属代理能够启动与移动节点的流绑定交互，本文档定义了移动IPv6的新信令消息和子选项。IPv4和IPv6同时启用的移动节点支持由归属代理启动的流绑定。
Status of This Memo
关于下段备忘
This document is not an Internet Standards Track specification; it is published for examination, experimental implementation, and evaluation.
本文件不是互联网标准跟踪规范；它是为检查、实验实施和评估而发布的。
This document defines an Experimental Protocol for the Internet community. This is a contribution to the RFC Series, independently of any other RFC stream. The RFC Editor has chosen to publish this document at its discretion and makes no statement about its value for implementation or deployment. Documents approved for publication by the RFC Editor are not a candidate for any level of Internet Standard; see Section 2 of RFC 5741.
本文档为互联网社区定义了一个实验协议。这是对RFC系列的贡献，独立于任何其他RFC流。RFC编辑器已选择自行发布此文档，并且未声明其对实现或部署的价值。RFC编辑批准发布的文件不适用于任何级别的互联网标准；见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/rfc7109.
有关本文件当前状态、任何勘误表以及如何提供反馈的信息，请访问http://www.rfc-editor.org/info/rfc7109.
Copyright Notice
版权公告
Copyright (c) 2014 IETF Trust and the persons identified as the document authors. All rights reserved.
版权所有（c）2014 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.
本文件受BCP 78和IETF信托有关IETF文件的法律规定的约束(http://trustee.ietf.org/license-info)自本文件出版之日起生效。请仔细阅读这些文件，因为它们描述了您对本文件的权利和限制。
Table of Contents
目录
1. Introduction ....................................................3
2. Terminology .....................................................3
3. Use Cases .......................................................3
3.1. QoS Provisioning ...........................................3
3.2. Traffic Offload from Congested Network .....................4
3.3. Flow Movement or Deletion in an Emergency Situation ........4
3.4. Service-Specific Data Cap ..................................4
4. Protocol Operation ..............................................4
4.1. Adding Flow Bindings .......................................5
4.2. Deleting Flow Bindings .....................................6
4.3. Modifying Flow Bindings ....................................6
4.4. Refreshing Flow Bindings ...................................6
4.5. Moving Flow Bindings .......................................7
4.6. Revoking Flow Bindings .....................................7
5. Handling of the Flow Bindings List ..............................8
6. Flow Binding Messages and Options ...............................9
6.1. Mobility Header ............................................9
6.1.1. Flow Binding Indication .............................9
6.1.2. Flow Binding Acknowledgement .......................10
6.1.3. Flow Binding Revocation Extensions .................11
6.2. New Options ...............................................12
6.2.1. Flow Binding Action Sub-Option .....................12
6.2.2. Target Care-of Address Sub-Option ..................13
7. Security Considerations ........................................13
8. Protocol Constants .............................................14
9. IANA Considerations ............................................14
10. References ....................................................16
10.1. Normative References .....................................16
10.2. Informative References ...................................17
1. Introduction ....................................................3
2. Terminology .....................................................3
3. Use Cases .......................................................3
3.1. QoS Provisioning ...........................................3
3.2. Traffic Offload from Congested Network .....................4
3.3. Flow Movement or Deletion in an Emergency Situation ........4
3.4. Service-Specific Data Cap ..................................4
4. Protocol Operation ..............................................4
4.1. Adding Flow Bindings .......................................5
4.2. Deleting Flow Bindings .....................................6
4.3. Modifying Flow Bindings ....................................6
4.4. Refreshing Flow Bindings ...................................6
4.5. Moving Flow Bindings .......................................7
4.6. Revoking Flow Bindings .....................................7
5. Handling of the Flow Bindings List ..............................8
6. Flow Binding Messages and Options ...............................9
6.1. Mobility Header ............................................9
6.1.1. Flow Binding Indication .............................9
6.1.2. Flow Binding Acknowledgement .......................10
6.1.3. Flow Binding Revocation Extensions .................11
6.2. New Options ...............................................12
6.2.1. Flow Binding Action Sub-Option .....................12
6.2.2. Target Care-of Address Sub-Option ..................13
7. Security Considerations ........................................13
8. Protocol Constants .............................................14
9. IANA Considerations ............................................14
10. References ....................................................16
10.1. Normative References .....................................16
10.2. Informative References ...................................17
[RFC6089] allows a mobile node (MN) to bind a particular flow to a care-of address (CoA) without affecting other flows using the same home address. BU/BA (Binding Update / Binding Acknowledgement) messages are extended for the mobile node to add, delete, modify, move, refresh, and revoke flow bindings in a home agent (HA). The operations are always initiated by the mobile node.
[RFC6089]允许移动节点（MN）将特定流绑定到转交地址（CoA），而不影响使用相同家庭地址的其他流。BU/BA（绑定更新/绑定确认）消息被扩展，以便移动节点在归属代理（HA）中添加、删除、修改、移动、刷新和撤销流绑定。这些操作始终由移动节点发起。
While the mobile node manipulates flow bindings by, e.g., the user interaction or the change of the attached link condition, these operations are also required for network-related reasons such as dynamic QoS control in the network, load balancing, or maintenance in mobility agent nodes. For the latter case, the mobile node is not very aware of the transport network condition away from it or of the policy and charging status controlled by the operator; thus, the network needs to request that the mobile node handle proper flow bindings.
当移动节点通过例如用户交互或所附链路条件的改变来操纵流绑定时，这些操作也出于网络相关的原因而需要，例如网络中的动态QoS控制、负载平衡或移动代理节点中的维护。对于后一种情况，移动节点并不十分清楚远离它的传输网络状况或由运营商控制的策略和收费状态；因此，网络需要请求移动节点处理适当的流绑定。
This document defines a new Mobility Header and messages in order for the home agent to request that the mobile node initiate flow bindings in a timely manner. Flow mobility is also supported for mobile nodes with an IPv4 home address and an IPv4 address of the home agent, as described in [RFC5555].
本文档定义了新的移动头和消息，以便归属代理请求移动节点及时启动流绑定。如[RFC5555]所述，对于具有IPv4归属地址和归属代理的IPv4地址的移动节点，也支持流移动。
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]中所述进行解释。
The terminology in this document is based on the definitions in [RFC6275] and [RFC6089].
本文件中的术语基于[RFC6275]和[RFC6089]中的定义。
When the user launches a video chat application and starts sending voice and video to the other end, the network may need to provide different QoS treatments to these media based on the operator's policy. In such a case, the network needs to request the user or mobile node to establish separate flows for voice and video.
当用户启动视频聊天应用程序并开始向另一端发送语音和视频时，网络可能需要根据运营商的策略为这些媒体提供不同的QoS处理。在这种情况下，网络需要请求用户或移动节点为语音和视频建立单独的流。
The 3G operator may want to move traffic flows from the 3G access network to another network (e.g., Wi-Fi network) due to instantaneous traffic increases in the 3G access network. Fine-grained traffic offload is desirable. For example, Voice over IP (VoIP) flows based on IP Multimedia Subsystems (IMS) must stay in the mobile core network while video-streaming flows provided by servers on the Internet could bypass the mobile core network via Wi-Fi access. Since the network knows more about its conditions and has access to the policy server, more timely and well-controlled traffic offloading is possible. The home agent sends an updated flow descriptor to be offloaded to the mobile node.
由于3G接入网络中的瞬时流量增加，3G运营商可能希望将流量从3G接入网络移动到另一个网络（例如，Wi-Fi网络）。细粒度流量卸载是可取的。例如，基于IP多媒体子系统（IMS）的IP语音（VoIP）流必须留在移动核心网络中，而互联网上服务器提供的视频流可以通过Wi-Fi接入绕过移动核心网络。由于网络更多地了解其状况并可以访问策略服务器，因此可以更及时、更好地控制流量卸载。归属代理发送要卸载到移动节点的更新流描述符。
In an emergency situation caused by a natural disaster, it is necessary to accept as many voice calls as possible for inquiries to confirm the safety status of family and friends, while non-critical services such as gaming would be considered lower priority. In order to save the 3G / Long Term Evolution (LTE) radio resources for emergency services, non-critical services may need to be moved to another access network or closed down. The home agent requests that the mobile node use Wi-Fi access for non-critical application flows or terminate them gracefully, e.g., by letting it notify the user of possible QoS degradation or ask him/her to finish the corresponding applications before taking any action.
在自然灾害造成的紧急情况下，有必要接受尽可能多的语音查询，以确认家人和朋友的安全状况，而游戏等非关键服务将被视为较低优先级。为了节省3G/长期演进（LTE）无线电资源用于紧急服务，可能需要将非关键服务移动到另一个接入网络或关闭。归属代理请求移动节点对非关键应用程序流使用Wi-Fi访问，或优雅地终止它们，例如，让移动节点通知用户可能的QoS降低，或要求用户在采取任何操作之前完成相应的应用程序。
The mobile operator offers a mobile broadband service with a flat rate subscription limited to 5 GB per month. Once the allotment is used up, the service is downgraded to 64 kbits/s. This limitation, however, is not applied to IMS-based services (e.g., Voice over LTE (VoLTE)), while video conversations over the Internet will be affected. The operator can indicate this to the user by sending modified flow descriptors as a proposal to adjust the communication data rate or change access for an ongoing session.
移动运营商提供移动宽带服务，固定费率订阅限制为每月5 GB。分配用完后，服务将降级到64 kbits/s。然而，这一限制不适用于基于IMS的服务（例如，LTE语音（VoLTE）），而互联网上的视频对话将受到影响。操作员可以通过发送修改后的流描述符向用户指示这一点，作为调整通信数据速率或更改正在进行的会话的访问的建议。
[RFC6089] makes use of BU/BA signaling to forward, i.e., register or discard, a flow binding in a home agent. Flow binding operations are always initiated from the mobile node. The basic principle of this specification is that the home agent prompts the mobile node to perform flow binding operations. For this purpose, a new Mobility Header and two new messages, that is, Flow Binding Indication (FBI) and Flow Binding Acknowledgement (FBA), are defined. An FBI is used
[RFC6089]利用BU/BA信令转发（即注册或丢弃）归属代理中的流绑定。流绑定操作始终从移动节点启动。本规范的基本原理是，归属代理提示移动节点执行流绑定操作。为此，定义了一个新的移动报头和两个新消息，即流绑定指示（FBI）和流绑定确认（FBA）。使用FBI
by the home agent to request flow binding operations to the mobile node, and an FBA is used for acknowledging an FBI. In order for the flow binding operation to be complete, a BU/BA exchange MUST be initiated by the mobile node after an FBI/FBA exchange.
由归属代理向移动节点请求流绑定操作，FBA用于确认FBI。为了完成流绑定操作，移动节点必须在FBI/FBA交换之后启动BU/BA交换。
It is assumed that the home agent has already created binding cache entries for the mobile node before launching flow binding operations.
假设在启动流绑定操作之前，归属代理已经为移动节点创建了绑定缓存项。
Due to access-network change on the mobile-node side, some interfaces that used to be active may not be valid at the time of the flow binding operation by the home agent, in which case, even if the HA sends the FBI to the MN, the FBA will not return. After retransmitting the FBIs for MAX_FBI_RETRIES times and not receiving the FBA, the HA determines that the target interface is not available.
由于移动节点侧的接入网络发生变化，在归属代理进行流绑定操作时，一些曾经处于活动状态的接口可能无效，在这种情况下，即使HA向MN发送FBI，FBA也不会返回。在重新传输FBI最多重试次数且未接收FBA后，HA确定目标接口不可用。
If the mobile node does not support the FBI message, it responds with a Binding Error message with status set to 2 (unrecognized Mobility Header (MH) type value) as described in [RFC6275]. When the Binding Error message with status set to 2 is received in response to an FBI message, the home agent MUST NOT use an FBI message with that mobile node again.
如果移动节点不支持FBI消息，则其响应绑定错误消息，状态设置为2（无法识别的移动头（MH）类型值），如[RFC6275]中所述。当收到状态设置为2的绑定错误消息以响应FBI消息时，归属代理不得再次将FBI消息用于该移动节点。
Adding the flow binding implies associating a particular flow with one of the care-of addresses on the mobile node. The care-of address concerned with the flow binding is present in the destination address of the packet or the alternate care-of address option. Alternatively, the care-of address may be indicated by the Target Care-of Address sub-option defined in Section 6.2.2.
添加流绑定意味着将特定流与移动节点上的一个转交地址相关联。与流绑定相关的转交地址存在于数据包的目的地址或备用转交地址选项中。或者，转交地址可由第6.2.2节中定义的目标转交地址子选项指示。
When adding a new flow binding, the home agent sends an FBI with a Flow Identification Mobility option to the mobile node. In Figure 1, which is shown as an example for this operation, the mobile node exchanges both voice and video over FID#1 (Flow Identifier #1). Based on the operator's policy, the network determines if it needs to provide separate QoS for the video flow, and the home agent sends the FBI to the mobile node. The Flow Identification Mobility option defined in [RFC6089] includes the current FID and the Traffic Selector (TS) to specify the video flow. The Flow Binding Action sub-option MUST indicate the Add operation defined in Section 6.2.1. The mobile node returns the FBA to the home agent with the same options. The BU/BA exchange follows afterwards to perform the actual flow binding as defined in [RFC6088], and the video traffic is exchanged over FID#2.
添加新的流绑定时，归属代理向移动节点发送带有流标识移动选项的FBI。在图1中，移动节点通过FID#1（流标识符#1）交换语音和视频，这是该操作的一个示例。根据运营商的策略，网络确定是否需要为视频流提供单独的QoS，并且归属代理将FBI发送到移动节点。[RFC6089]中定义的流标识移动选项包括当前FID和用于指定视频流的流量选择器（TS）。流绑定操作子选项必须指明第6.2.1节中定义的添加操作。移动节点使用相同的选项将FBA返回给归属代理。BU/BA交换随后执行[RFC6088]中定义的实际流绑定，视频流量通过FID#2进行交换。
+----+ +----+
| MN | | HA |
+----+ +----+
| FID#1(voice+video) |
|/==============================\|
|\==============================/|
| |
| FBI(add,FID#1,TS[video]) |
|<-------------------------------|
| FBA(FID#1,TS[video]) |
|------------------------------->|
| BU(FID#2,TS[video]) |
|------------------------------->|
| BA(FID#2,TS[video]) |
|<-------------------------------|
| |
| FID#1(voice) |
|<==============================>|
| FID#2(video) |
|<==============================>|
+----+ +----+
| MN | | HA |
+----+ +----+
| FID#1(voice+video) |
|/==============================\|
|\==============================/|
| |
| FBI(add,FID#1,TS[video]) |
|<-------------------------------|
| FBA(FID#1,TS[video]) |
|------------------------------->|
| BU(FID#2,TS[video]) |
|------------------------------->|
| BA(FID#2,TS[video]) |
|<-------------------------------|
| |
| FID#1(voice) |
|<==============================>|
| FID#2(video) |
|<==============================>|
Figure 1: Example Call Flow for Adding a Flow Binding
图1：添加流绑定的调用流示例
When removing a flow binding, the home agent sends an FBI with a Flow Identification Mobility option in which the Flow Binding Action sub-option indicates the Delete operation. The Flow Identification Mobility option includes a unique FID for the mobile node to locate the flow binding and remove it.
删除流绑定时，归属代理将发送一个FBI，其中流标识移动选项中的流绑定操作子选项指示删除操作。流标识移动选项包括一个唯一的FID，用于移动节点定位流绑定并将其移除。
When modifying a flow binding (e.g., changing QoS attributes of the flow as defined in [PMIP6-QOS]) is needed, the home agent sends the mobile node an FBI message with the Flow Identification Mobility option. The option includes the FID to be modified. A Traffic Selector sub-option MAY come with the Flow Identification Mobility option and contain new attributes, e.g., the in Quality of Service option.
当需要修改流绑定（例如，改变[PMIP6-QoS]中定义的流的QoS属性）时，归属代理向移动节点发送具有流标识移动选项的FBI消息。该选项包括要修改的FID。流量选择器子选项可以与流标识移动性选项一起提供，并包含新属性，例如，服务质量选项。
A flow binding is refreshed by simply including the Flow Identification Mobility option with the Refresh Action field in the FBI message. The message should be sent before the expiration of the flow binding. The message updates existing bindings with new
只需在FBI消息中包含带有刷新操作字段的流标识移动选项，即可刷新流绑定。消息应在流绑定到期之前发送。该消息将使用新绑定更新现有绑定
information. Hence, all information previously sent in the last refreshing message need to be resent; otherwise, such information will be lost.
信息因此，需要重新发送上次刷新消息中先前发送的所有信息；否则，这些信息将丢失。
The home agent can request to move a flow associated with one interface of the multi-interfaced mobile node to another by sending an FBI message to the mobile node. The Action field of the Flow Binding Action sub-option is set to Move, and the address of the target interface is also included in the Target Care-of Address sub-option. After the FBA is returned to the home agent, the flow mobility is performed by the mobile node. Figure 2 shows the movement of a flow label as FID from the interface with sCoA to that with tCoA, which is stored in the Binding Identity Mobility option.
归属代理可以通过向移动节点发送FBI消息来请求将与多接口移动节点的一个接口相关联的流移动到另一个接口。流绑定操作子选项的操作字段设置为移动，目标接口的地址也包含在目标转交地址子选项中。在FBA返回到归属代理之后，由移动节点执行流移动性。图2显示了作为FID的流标签从与sCoA的接口移动到与tCoA的接口，该接口存储在绑定标识移动选项中。
+----+ +----+
| MN | | HA |
+----+ +----+
|<=sCoA |
| |<=tCoA |
| | FBI(FID,tCoA) |
|<--------------------------------|
| | FBA(FID,tCoA) |
|-------------------------------->|
| | |
| | BU(BID[tCoA],FID) |
| |------------------------------>|
| | BA(BID[tCoA],FID) |
| |<------------------------------|
| | |
+----+ +----+
| MN | | HA |
+----+ +----+
|<=sCoA |
| |<=tCoA |
| | FBI(FID,tCoA) |
|<--------------------------------|
| | FBA(FID,tCoA) |
|-------------------------------->|
| | |
| | BU(BID[tCoA],FID) |
| |------------------------------>|
| | BA(BID[tCoA],FID) |
| |<------------------------------|
| | |
Figure 2: Example Call Flow for Moving a Flow Binding
图2：移动流绑定的调用流示例
When the home agent or the network attached to it is overloaded, the home agent can revoke a flow binding registered by the mobile node. The home agent sends the mobile node an FBI message with a Flow Identification Mobility option in which the Flow Binding Action sub-option indicates the Revoke operation. When the MN receives the FBI message with the Revoke operation, it decides whether the flow should be removed (de-registration) or moved to another interface and returns the FBA with an appropriate status code. The mobile node SHOULD take an action by sending a new BU, for example, to deregister the flow.
当归属代理或连接到它的网络过载时，归属代理可以撤销由移动节点注册的流绑定。归属代理向移动节点发送具有流标识移动选项的FBI消息，其中流绑定操作子选项指示撤销操作。当MN接收到带有撤销操作的FBI消息时，它决定是删除流（取消注册）还是移动到另一个接口，并返回带有适当状态代码的FBA。移动节点应该通过发送一个新BU来采取行动，例如，取消流的注册。
The difference between revoking and deleting flow bindings (Section 4.2) is that the target flow may be revoked by the network with the procedures defined in [RFC5846] even if the mobile node does not take any action.
撤销和删除流绑定（第4.2节）之间的区别在于，即使移动节点没有采取任何行动，网络也可以使用[RFC5846]中定义的过程撤销目标流。
The flow bindings list defined in [RFC6089] needs to be updated as follows after each protocol operation defined above is performed:
[RFC6089]中定义的流绑定列表需要在执行上述每个协议操作后按如下方式更新：
If an FBI contains a flow binding Add operation and if the corresponding FBA has a status code equal to zero, the home agent MUST add a new entry to the flow bindings list. The FID, Flow Descriptor, FID-PRI, and Action fields are taken from the Flow Identification Mobility option. The binding identifier (BID) is copied from the Binding Reference sub-option. The Active/Inactive Flag is set to Active. Note that if BID is not available, it may be replaced by Target Care-of Address.
如果FBI包含流绑定添加操作，并且相应FBA的状态代码等于零，则归属代理必须向流绑定列表添加新条目。FID、流描述符、FID-PRI和操作字段取自流标识移动选项。绑定标识符（BID）是从绑定引用子选项复制的。活动/非活动标志设置为活动。请注意，如果投标文件不可用，则可由目标公司转交地址代替。
If an FBI contains a flow binding Delete operation and if the corresponding FBA has a status code equal to zero, the home agent MUST locate the list entry corresponding to this flow and then delete the entry.
如果FBI包含流绑定删除操作，并且相应FBA的状态代码等于零，则归属代理必须找到与此流对应的列表条目，然后删除该条目。
If the home agent sends a Binding Revocation Indication message with the Flow Identification Mobility option with the action field set to Revoke and if the corresponding Binding Revocation Acknowledgement message indicates acceptance, the home agent MUST locate the list entry corresponding to this flow and then delete the entry.
如果归属代理发送绑定撤销指示消息，其中流标识移动选项的操作字段设置为撤销，并且如果相应的绑定撤销确认消息指示接受，则归属代理必须找到与此流对应的列表条目，然后删除该条目。
If an FBI contains a flow binding Modify operation and if the corresponding FBA has a status code equal to zero, the home agent MUST delete the list entry corresponding to this flow and then add a new entry, setting the values as defined in the Flow Identification Mobility option.
如果FBI包含流绑定修改操作，并且相应FBA的状态代码等于零，则归属代理必须删除与此流对应的列表条目，然后添加新条目，设置流标识移动选项中定义的值。
If an FBI contains a flow binding Refresh operation and if the corresponding FBA has a status code equal to zero, the home agent MUST locate the list entry corresponding to this flow and then set the Active/Inactive Flag to Active.
如果FBI包含流绑定刷新操作，并且相应FBA的状态代码等于零，则归属代理必须找到与此流对应的列表项，然后将Active/Inactive标志设置为Active。
If an FBI contains a flow binding Move operation and if the corresponding FBA has a status code equal to zero, the home agent MUST locate the list entry corresponding to this flow and then change the BID value to the care-of address in the Flow Identification Mobility option.
如果FBI包含流绑定移动操作，并且相应FBA的状态代码等于零，则归属代理必须找到与此流对应的列表条目，然后在流标识移动选项中将BID值更改为转交地址。
If an FBI contains a flow binding Revoke operation and if the corresponding FBA has a status code equal to zero, the home agent MUST locate the list entry corresponding to this flow and then delete the entry.
如果FBI包含流绑定撤销操作，并且相应FBA的状态代码等于零，则归属代理必须找到与此流对应的列表条目，然后删除该条目。
Flow binding operations apply equally to IPv4 packets and IPv6 packets as per Dual-Stack Mobile IPv6 [RFC5555]. In order to support the situation where there is a NAT/firewall between the mobile node and home agent, NAT detection and NAT keepalive mechanisms defined in [RFC5555] MUST be used. When the mobile node and home agent are in IPv6-only and IPv4-only networks respectively and NAT64 [RFC6146] resides in between, each node would behave as if the other node was in the same network domain. Even though this scenario is not fully described in [RFC5555], the initial mobility binding is always performed by the mobile node, and the binding cache is created in the home agent. The destination address of the FBI SHALL be the mobile node's IPv4 care-of address in the binding cache entry.
根据双栈移动IPv6[RFC5555]，流绑定操作同样适用于IPv4数据包和IPv6数据包。为了支持移动节点和归属代理之间存在NAT/防火墙的情况，必须使用[RFC5555]中定义的NAT检测和NAT保持机制。当移动节点和归属代理分别位于仅限IPv6和仅限IPv4的网络中，并且NAT64[RFC6146]位于两者之间时，每个节点的行为将与另一个节点位于同一网络域中的行为相同。尽管[RFC5555]中未完全描述此场景，但初始移动绑定始终由移动节点执行，并且绑定缓存在归属代理中创建。FBI的目标地址应为绑定缓存项中移动节点的IPv4转交地址。
The messages described below follow the Mobility Header format specified in Section 6.1 of [RFC6275].
下面描述的消息遵循[RFC6275]第6.1节规定的移动报头格式。
Flow Binding Indication messages are used by the home agent to initiate flow binding operations to the mobile node. Flow Binding Indication messages use the MH Type value (21) for Flow Binding messages and a Flow Binding Type value of 1, and the format of the Message Data field in the Mobility Header is as follows:
归属代理使用流绑定指示消息来发起到移动节点的流绑定操作。流绑定指示消息对流绑定消息使用MH类型值（21），流绑定类型值为1，移动性报头中消息数据字段的格式如下：
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Flow Binding Type = 1 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sequence # | Trigger |A| 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Flow Binding Type = 1 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sequence # | Trigger |A| Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
. .
. Mobility options .
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 3: Flow Binding Indication Mobility Header Format
图3：流绑定指示移动头格式
Sequence # A 16-bit unsigned integer used by the home agent to match a returned Flow Binding Acknowledgement with the Flow Binding Indication. It could be a random number.
序列#归属代理用于将返回的流绑定确认与流绑定指示匹配的16位无符号整数。它可能是一个随机数。
Trigger 8-bit unsigned integer indicating the event that triggered the home agent to send the Flow Binding Indication message. The following Trigger values are currently defined:
触发器8位无符号整数，指示触发归属代理发送流绑定指示消息的事件。当前定义了以下触发值：
0 Reserved
0保留
1 Unspecified
1未指明
2 Administrative Reason
2行政原因
3 Possible Out-of-Sync BCE State
3可能的不同步BCE状态
250-255 Reserved for Testing Purposes Only
250-255仅用于测试目的
All other values are unassigned.
所有其他值均未赋值。
Acknowledge (A) The Acknowledge (A) bit is set by the home agent to request that a Flow Binding Acknowledgement be returned upon receipt of the Flow Binding Indication.
确认（A）归属代理设置确认（A）位，以请求在收到流绑定指示时返回流绑定确认。
Reserved These fields are unused. They MUST be initialized to zero by the sender and MUST be ignored by the receiver.
保留这些字段未使用。发送方必须将它们初始化为零，接收方必须忽略它们。
Mobility options Variable-length field of such length that the complete Mobility Header is an integer multiple of 8 octets long. Flow Identification Mobility options are included in this field.
Mobility options可变长度字段，其长度应确保完整Mobility报头为8个八位字节长的整数倍。流量识别流动性选项包括在该字段中。
The Flow Binding Acknowledgement is used to acknowledge receipt of a Flow Binding Indication. The mobile node sends an FBA message to acknowledge the reception of an FBI to add, delete, modify, refresh, move, or revoke a flow binding. On receiving messages with Flow Identification Mobility option(s), the mobile node should copy each Flow Identification Mobility option to the Acknowledgement message. The Flow Binding Acknowledgement has the MH Type value (21) for Flow Binding messages and a Flow Binding Type value of 2. When this value is indicated in the MH Type field, the format of the Message Data field in the Mobility Header is as follows:
流绑定确认用于确认收到流绑定指示。移动节点发送FBA消息以确认接收到FBI以添加、删除、修改、刷新、移动或撤销流绑定。在接收到具有流标识移动性选项的消息时，移动节点应将每个流标识移动性选项复制到确认消息。流绑定确认具有流绑定消息的MH类型值（21）和流绑定类型值2。当在MH类型字段中指示该值时，移动报头中消息数据字段的格式如下：
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Flow Binding Type = 2 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sequence # | Status | 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Flow Binding Type = 2 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sequence # | Status | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
. .
. Mobility options .
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 4: Flow Binding Acknowledgement Mobility Header Format
图4：流绑定确认移动头格式
Sequence # The sequence number in the Flow Binding Acknowledgement is copied from the Sequence Number field in the Flow Binding Indication.
序列#流绑定确认中的序列号从流绑定指示中的序列号字段复制。
Status 8-bit unsigned integer indicating the result of processing the Flow Binding Indication message by the receiving mobile node. Values less than 128 in the Status field indicate that the Flow Binding Indication was processed successfully by the receiving node. Values greater than or equal to 128 indicate that the Flow Binding Indication was rejected by the receiving node. The following status values are currently defined:
状态8位无符号整数，指示接收移动节点处理流绑定指示消息的结果。状态字段中小于128的值表示接收节点已成功处理流绑定指示。大于或等于128的值表示接收节点拒绝了流绑定指示。当前定义了以下状态值：
0 Success
0成功
128 Binding (target CoA) Does NOT Exist
128绑定（目标CoA）不存在
129 Action NOT Authorized
129未授权的行动
All other values are unassigned.
所有其他值均未赋值。
Mobility options Variable-length field of such length that the complete Mobility Header is an integer multiple of 8 octets long. This field contains zero or more TLV-encoded mobility options. Flow Identification Mobility options are included in this field.
Mobility options可变长度字段，其长度应确保完整Mobility报头为8个八位字节长的整数倍。此字段包含零个或多个TLV编码的移动性选项。流量识别流动性选项包括在该字段中。
This specification enables Binding Revocation Indication and Binding Revocation Acknowledgement messages to carry Flow Identification Mobility options as defined in [RFC6089] with the extensions defined in this document.
本规范允许绑定撤销指示和绑定撤销确认消息携带[RFC6089]中定义的流标识移动选项以及本文档中定义的扩展。
This document defines new Flow Identification sub-options that are included in the Flow Identification Mobility option specified in [RFC6089].
本文件定义了[RFC6089]中规定的流量标识移动选项中包含的新流量标识子选项。
This section defines a new sub-option for flow binding actions, which MUST be included in the Flow Identification Mobility option when it is sent from the home agent to the mobile node via the FBI message. The format of this sub-option is shown in Figure 5.
本节为流绑定操作定义了一个新的子选项，当它通过FBI消息从归属代理发送到移动节点时，必须包含在流标识移动选项中。此子选项的格式如图5所示。
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 | Reserved | Action |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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 | Reserved | Action |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 5: Flow Binding Action Sub-Option
图5：流绑定操作子选项
Sub-opt Type 4
子选项类型4
Sub-opt Length Length of the sub-option in octets, excluding the Sub-opt Type and Sub-opt Length fields.
子选项的子选项长度（以八位字节为单位），不包括子选项类型和子选项长度字段。
Action This is a 8-bit field that describes the required processing for the option. It can be assigned one of the following new values:
操作这是一个8位字段，描述选项所需的处理。可以为其指定以下新值之一：
11 Add a flow binding
11添加流绑定
12 Delete a flow binding
12删除流绑定
13 Modify a flow binding
13修改流绑定
14 Refresh a flow binding
14刷新流绑定
15 Move a flow binding
15移动流绑定
16 Revoke a flow binding
16撤销流绑定
All other values are unassigned.
所有其他值均未赋值。
This section introduces the Target Care-of Address sub-option, which may be included in the Flow Identification Mobility option. This sub-option is used to indicate to the mobile node that a flow binding is to be moved from one interface to another.
本节介绍目标转交地址子选项，该子选项可能包含在流标识移动性选项中。此子选项用于向移动节点指示流绑定将从一个接口移动到另一个接口。
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 | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Target Care-of Address |
. .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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 | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Target Care-of Address |
. .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 6: Target Care-of Address Sub-Option
图6：目标转交地址子选项
Sub-opt Type 5
子选项类型5
Sub-opt Length Length of the sub-option in octets, excluding the Sub-opt Type and Sub-opt Length fields.
子选项的子选项长度（以八位字节为单位），不包括子选项类型和子选项长度字段。
Reserved This field is unused. It MUST be initialized to zero by the sender and MUST be ignored by the receiver.
保留此字段未使用。发送方必须将其初始化为零，接收方必须忽略它。
Target Care-of Address The address of an interface that the flow is moved to. This address could be an IPv4 or IPv6 address. This sub-option MUST be included when the action taken is "15 Move a flow binding".
目标转交地址流移动到的接口的地址。此地址可以是IPv4或IPv6地址。当所采取的行动是“15移动流绑定”时，必须包括此子选项。
Security issues for this document follow those of [RFC6088], [RFC6089], and [RFC5846]. This specification allows the home agent to manipulate only the binding of a flow(s) that is currently registered with it, which is the same principle described in [RFC5846]. No additional security issue specific to this document is identified.
本文档的安全问题遵循[RFC6088]、[RFC6089]和[RFC5846]中的安全问题。本规范允许归属代理仅操纵当前已注册的流的绑定，这与[RFC5846]中描述的原理相同。未发现与本文件相关的其他安全问题。
Maximum FBI retries (MAX_FBI_RETRIES) This variable specifies the maximum number of times the HA MAY retransmit a Flow Binding Indication message when the FBA is not returned within the time period specified by MAX_FBA_TIMEOUT. The default value for this parameter is 3.
Maximum FBI retries（MAX_FBI_retries）此变量指定在MAX_FBA_TIMEOUT指定的时间段内未返回FBA时，HA可重新传输流绑定指示消息的最大次数。此参数的默认值为3。
Maximum FBA timeout (MAX_FBA_TIMEOUT) This variable specifies the maximum time in seconds the HA MUST wait before retransmitting another FBI message. The default for this parameter is 3 seconds.
最大FBA超时（MAX_FBA_timeout）此变量指定HA在重新传输另一条FBI消息之前必须等待的最长时间（以秒为单位）。此参数的默认值为3秒。
IANA has taken the actions described below.
IANA已采取下述措施。
Action-1 This specification defines a new Mobility Header Type, "Flow Binding Message". This Mobility Header message is described in Section 6.1, and the type value for this messages is 21, which has been assigned in the "Mobility Header Types - for the MH Type field in the Mobility Header" registry.
措施1本规范定义了一种新的移动头类型“流绑定消息”。第6.1节描述了该移动头消息，该消息的类型值为21，已在“移动头类型-移动头中的MH类型”注册表中分配。
Action-2 This specification defines "Flow Binding Type". IANA has created a new sub-registry within the "Mobile IPv6 parameters" registry. Flow Binding Type is described in Sections 6.1.1 and 6.1.2, which reserve the following values:
措施2本规范定义了“流量绑定类型”。IANA在“移动IPv6参数”注册表中创建了一个新的子注册表。第6.1.1节和第6.1.2节描述了流量绑定类型，其中保留了以下值：
+-------+------------------------------+--------------+
| Value | Description | Reference |
+-------+------------------------------+--------------+
| 0 | Unassigned | |
+-------+------------------------------+--------------+
| 1 | Flow Binding Indication | [RFC7109] |
+-------+------------------------------+--------------+
| 2 | Flow Binding Acknowledgement | [RFC7109] |
+-------+------------------------------+--------------+
| 3-255 | Unassigned | |
+--------------------------------------+--------------+
+-------+------------------------------+--------------+
| Value | Description | Reference |
+-------+------------------------------+--------------+
| 0 | Unassigned | |
+-------+------------------------------+--------------+
| 1 | Flow Binding Indication | [RFC7109] |
+-------+------------------------------+--------------+
| 2 | Flow Binding Acknowledgement | [RFC7109] |
+-------+------------------------------+--------------+
| 3-255 | Unassigned | |
+--------------------------------------+--------------+
Future assignments in the "Flow Binding Type" registry are to be made through RFC Required [RFC5226].
“流绑定类型”注册表中的未来分配将通过要求的RFC[RFC5226]进行。
Action-3 This specification defines "Flow Binding Indication Triggers". IANA has created a new sub-registry within the "Mobile IPv6 parameters" registry. The trigger values are described in Section 6.1.1, which reserves the following values:
措施3本规范定义了“流量绑定指示触发器”。IANA在“移动IPv6参数”注册表中创建了一个新的子注册表。第6.1.1节中描述了触发值，该节保留了以下值：
+---------+------------------------------------+--------------+
| Value | Description | Reference |
+---------+------------------------------------+--------------+
| 0 | Reserved | [RFC7109] |
+---------+------------------------------------+--------------+
| 1 | Unspecified | [RFC7109] |
+---------+------------------------------------+--------------+
| 2 | Administrative Reason | [RFC7109] |
+---------+------------------------------------+--------------+
| 3 | Possible Out-of-Sync BCE State | [RFC7109] |
+---------+------------------------------------+--------------+
| 4-249 | Unassigned | |
+---------+------------------------------------+--------------+
| 250-255 | Reserved for Testing Purposes Only | [RFC7109] |
+----------------------------------------------+--------------+
+---------+------------------------------------+--------------+
| Value | Description | Reference |
+---------+------------------------------------+--------------+
| 0 | Reserved | [RFC7109] |
+---------+------------------------------------+--------------+
| 1 | Unspecified | [RFC7109] |
+---------+------------------------------------+--------------+
| 2 | Administrative Reason | [RFC7109] |
+---------+------------------------------------+--------------+
| 3 | Possible Out-of-Sync BCE State | [RFC7109] |
+---------+------------------------------------+--------------+
| 4-249 | Unassigned | |
+---------+------------------------------------+--------------+
| 250-255 | Reserved for Testing Purposes Only | [RFC7109] |
+----------------------------------------------+--------------+
Future assignments in the "Flow Binding Indication Triggers" registry are to be made through RFC Required [RFC5226].
“流绑定指示触发器”注册表中的未来分配将通过要求的RFC[RFC5226]进行。
Action-4 This specification defines "Flow Binding Acknowledgement Status Codes". IANA has created a new sub-registry within the "Mobile IPv6 parameters" registry. The status codes are described in Section 6.1.2, which reserves the following values:
措施4本规范定义了“流程绑定确认状态代码”。IANA在“移动IPv6参数”注册表中创建了一个新的子注册表。第6.1.2节描述了状态代码，其中保留了以下值：
+---------+-------------------------------------+--------------+
| Value | Description | Reference |
+---------+-------------------------------------+--------------+
| 0 | Success | [RFC7109] |
+---------+-------------------------------------+--------------+
| 1-127 | Unassigned | |
+---------+-------------------------------------+--------------+
| 128 | Binding (target CoA) Does NOT Exist | [RFC7109] |
+---------+-------------------------------------+--------------+
| 129 | Action NOT Authorized | [RFC7109] |
+---------+-------------------------------------+--------------+
| 130-255 | Unassigned | |
+---------+-------------------------------------+--------------+
+---------+-------------------------------------+--------------+
| Value | Description | Reference |
+---------+-------------------------------------+--------------+
| 0 | Success | [RFC7109] |
+---------+-------------------------------------+--------------+
| 1-127 | Unassigned | |
+---------+-------------------------------------+--------------+
| 128 | Binding (target CoA) Does NOT Exist | [RFC7109] |
+---------+-------------------------------------+--------------+
| 129 | Action NOT Authorized | [RFC7109] |
+---------+-------------------------------------+--------------+
| 130-255 | Unassigned | |
+---------+-------------------------------------+--------------+
Future assignments in the "Flow Binding Acknowledgement Status Codes" are to be made through RFC Required [RFC5226].
“流程绑定确认状态代码”中的未来分配将通过要求的RFC[RFC5226]进行。
Action-5 This specification defines two new Flow Identification sub-options: the "Flow Binding Action" sub-option and "Target Care-of Address" sub-option. These sub-options are described in Sections 6.2.1 and 6.2.2, and the sub-option values are 4 and 5, respectively, as assigned in the "Flow Identification Sub-options" registry.
措施5本规范定义了两个新的流标识子选项：“流绑定措施”子选项和“目标转交地址”子选项。第6.2.1节和第6.2.2节描述了这些子选项，子选项值分别为4和5，如“流量标识子选项”注册表中所分配的。
Action-6 This specification defines "Flow Binding Action Values". IANA has created a new sub-registry within the "Mobile IPv6 parameters" registry. The action values are described in Section 6.2.1, which reserves the following values:
行动-6本规范定义了“流动约束行动值”。IANA在“移动IPv6参数”注册表中创建了一个新的子注册表。第6.2.1节中描述了动作值，该节保留了以下值：
+--------+-------------------------------------+--------------+
| Value | Description | Reference |
+--------+-------------------------------------+--------------+
| 0-10 | Unassigned | |
+--------+-------------------------------------+--------------+
| 11 | Add a flow binding | [RFC7109] |
+--------+-------------------------------------+--------------+
| 12 | Delete a flow binding | [RFC7109] |
+--------+-------------------------------------+--------------+
| 13 | Modify a flow binding | [RFC7109] |
+--------+-------------------------------------+--------------+
| 14 | Refresh a flow binding | [RFC7109] |
+--------+-------------------------------------+--------------+
| 15 | Move a flow binding | [RFC7109] |
+--------+-------------------------------------+--------------+
| 16 | Revoke a flow binding | [RFC7109] |
+--------+-------------------------------------+--------------+
| 17-255 | Unassigned | |
+--------+-------------------------------------+--------------+
+--------+-------------------------------------+--------------+
| Value | Description | Reference |
+--------+-------------------------------------+--------------+
| 0-10 | Unassigned | |
+--------+-------------------------------------+--------------+
| 11 | Add a flow binding | [RFC7109] |
+--------+-------------------------------------+--------------+
| 12 | Delete a flow binding | [RFC7109] |
+--------+-------------------------------------+--------------+
| 13 | Modify a flow binding | [RFC7109] |
+--------+-------------------------------------+--------------+
| 14 | Refresh a flow binding | [RFC7109] |
+--------+-------------------------------------+--------------+
| 15 | Move a flow binding | [RFC7109] |
+--------+-------------------------------------+--------------+
| 16 | Revoke a flow binding | [RFC7109] |
+--------+-------------------------------------+--------------+
| 17-255 | Unassigned | |
+--------+-------------------------------------+--------------+
Future assignments in the "Flow Binding Action Values" registry are to be made through RFC Required [RFC5226].
“流绑定操作值”注册表中的未来分配将通过要求的RFC[RFC5226]进行。
[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月。
[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月。
[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月。
[RFC6088] Tsirtsis, G., Giarreta, G., Soliman, H., and N. Montavont, "Traffic Selectors for Flow Bindings", RFC 6088, January 2011.
[RFC6088]Tsirtsis，G.，Giarreta，G.，Soliman，H.，和N.Montavont，“流绑定的流量选择器”，RFC 6088，2011年1月。
[RFC6089] Tsirtsis, G., Soliman, H., Montavont, N., Giaretta, G., and K. Kuladinithi, "Flow Bindings in Mobile IPv6 and Network Mobility (NEMO) Basic Support", RFC 6089, January 2011.
[RFC6089]Tsirtsis，G.，Soliman，H.，Montavont，N.，Giaretta，G.，和K.Kuladinhi，“移动IPv6和网络移动（NEMO）基本支持中的流绑定”，RFC 60892011年1月。
[RFC6146] Bagnulo, M., Matthews, P., and I. van Beijnum, "Stateful NAT64: Network Address and Protocol Translation from IPv6 Clients to IPv4 Servers", RFC 6146, April 2011.
[RFC6146]Bagnulo，M.，Matthews，P.，和I.van Beijnum，“有状态NAT64：从IPv6客户端到IPv4服务器的网络地址和协议转换”，RFC 61462011年4月。
[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月。
[PMIP6-QOS] Liebsch, M., Seite, P., Yokota, H., Korhonen, J., and S. Gundavelli, "Quality of Service Option for Proxy Mobile IPv6", Work in Progress, December 2013.
[PMIP6-QOS]Liebsch，M.，Seite，P.，横田，H.，Korhonen，J.，和S.Gundavelli，“代理移动IPv6的服务质量选项”，正在进行的工作，2013年12月。
Authors' Addresses
作者地址
Hidetoshi Yokota KDDI Lab 2-1-15 Ohara Fujimino, Saitama 356-8502 Japan
横田英寿KDDI实验室2-1-15日本柴达木大原藤美浓356-8502
EMail: yokota@kddilabs.jp
EMail: yokota@kddilabs.jp
Dae-Sun Kim JEJU Technopark 217, Jungang-ro (St) Jejusi, Jeju Special Self-Governing Province 690-787 Korea
韩国济州特别自治省济州岛郑岗罗（街）217号济州大新金科技园690-787
EMail: dskim@jejutp.or.kr
EMail: dskim@jejutp.or.kr
Behcet Sarikaya Huawei USA 5340 Legacy Drive, Building 3 Plano, TX 75024 US
Behcet Sarikaya华为美国德克萨斯州Plano 3号楼5340 Legacy Drive美国75024
Phone: +1 469-277-5839
EMail: sarikaya@ieee.org
Phone: +1 469-277-5839
EMail: sarikaya@ieee.org
Frank Xia Huawei Technologies Co., Ltd. 101 Software Avenue, Yuhua District Nanjing, Jiangsu 210012 China
中国江苏省南京市雨花区软件大道101号富兰克夏华为技术有限公司210012
Phone: +86-25-56625443
EMail: xiayangsong@huawei.com
Phone: +86-25-56625443
EMail: xiayangsong@huawei.com