Network Working Group V. Devarapalli
Request for Comments: 3963 Nokia
Category: Standards Track R. Wakikawa
Keio University
A. Petrescu
Motorola
P. Thubert
Cisco Systems
January 2005
Network Working Group V. Devarapalli
Request for Comments: 3963 Nokia
Category: Standards Track R. Wakikawa
Keio University
A. Petrescu
Motorola
P. Thubert
Cisco Systems
January 2005
Network Mobility (NEMO) Basic Support Protocol
网络移动（NEMO）基本支持协议
Status of This Memo
关于下段备忘
This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited.
本文件规定了互联网社区的互联网标准跟踪协议，并要求进行讨论和提出改进建议。有关本协议的标准化状态和状态，请参考当前版本的“互联网官方协议标准”（STD 1）。本备忘录的分发不受限制。
Copyright Notice
版权公告
Copyright (C) The Internet Society (2005).
版权所有（C）互联网协会（2005年）。
Abstract
摘要
This document describes the Network Mobility (NEMO) Basic Support protocol that enables Mobile Networks to attach to different points in the Internet. The protocol is an extension of Mobile IPv6 and allows session continuity for every node in the Mobile Network as the network moves. It also allows every node in the Mobile Network to be reachable while moving around. The Mobile Router, which connects the network to the Internet, runs the NEMO Basic Support protocol with its Home Agent. The protocol is designed so that network mobility is transparent to the nodes inside the Mobile Network.
本文档描述了网络移动性（NEMO）基本支持协议，该协议使移动网络能够连接到Internet上的不同点。该协议是移动IPv6的扩展，允许移动网络中的每个节点在网络移动时保持会话连续性。它还允许移动网络中的每个节点在移动时都可以访问。将网络连接到Internet的移动路由器通过其家庭代理运行NEMO基本支持协议。该协议的设计使得网络移动性对移动网络中的节点是透明的。
Table of Contents
目录
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology. . . . . . . . . . . . . . . . . . . . . . . . . 4
3. Overview of the NEMO Protocol. . . . . . . . . . . . . . . . 4
4. Message Formats. . . . . . . . . . . . . . . . . . . . . . . 7
4.1. Binding Update. . . . . . . . . . . . . . . . . . . . . 7
4.2. Binding Acknowledgement . . . . . . . . . . . . . . . . 7
4.3. Mobile Network Prefix Option. . . . . . . . . . . . . . 8
5. Mobile Router Operation. . . . . . . . . . . . . . . . . . . 9
5.1. Data Structures . . . . . . . . . . . . . . . . . . . . 10
5.2. Sending Binding Updates . . . . . . . . . . . . . . . . 10
5.3. Receiving Binding Acknowledgements. . . . . . . . . . . 11
5.4. Error Processing . . . . . . . . . . . . . . . . . . . 12
5.4.1. Implicit Mode. . . . . . . . . . . . . . . . . . 12
5.4.2. Explicit Mode. . . . . . . . . . . . . . . . . . 12
5.5. Establishment of Bi-directional Tunnel . . . . . . . . 13
5.6. Neighbor Discovery for Mobile Router . . . . . . . . . 13
5.7. Multicast Groups for Mobile Router . . . . . . . . . . 14
5.8. Returning Home . . . . . . . . . . . . . . . . . . . . 14
6. Home Agent Operation . . . . . . . . . . . . . . . . . . . . 15
6.1. Data Structures . . . . . . . . . . . . . . . . . . . . 15
6.1.1. Binding Cache. . . . . . . . . . . . . . . . . . 15
6.1.2. Prefix Table . . . . . . . . . . . . . . . . . . 15
6.2. Mobile Network Prefix Registration . . . . . . . . . . 16
6.3. Advertising Mobile Network Reachability . . . . . . . . 17
6.4. Establishment of Bi-directional Tunnel . . . . . . . . 18
6.5. Forwarding Packets . . . . . . . . . . . . . . . . . . 18
6.6. Sending Binding Acknowledgements . . . . . . . . . . . 19
6.7. Mobile Network Prefix De-Registration . . . . . . . . . 19
7. Modifications to Dynamic Home Agent Address Discovery. . . . 20
7.1. Modified Dynamic Home Agent Discovery Request . . . . . 20
7.2. Modified Dynamic Home Agent Discovery Address Request . 20
7.3. Modified Home Agent Information Option . . . . . . . . 21
8. Support for Dynamic Routing Protocols. . . . . . . . . . . . 22
9. Security Considerations. . . . . . . . . . . . . . . . . . . 23
10. IANA Considerations. . . . . . . . . . . . . . . . . . . . . 24
11. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 25
12. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 25
13. References . . . . . . . . . . . . . . . . . . . . . . . . . 25
Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
A. Examples of NEMO Basic Support Operation. . . . . . . . . 27
B. Running Link State Routing Protocol with NEMO Basic
Support . . . . . . . . . . . . . . . . . . . . . . . . . 30
B.1. Tunnel Interface Considerations. . . . . . . . . . . 30
B.2. OSPF Area Considerations . . . . . . . . . . . . . . 30
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 32
Full Copyright Statement . . . . . . . . . . . . . . . . . . . . 33
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology. . . . . . . . . . . . . . . . . . . . . . . . . 4
3. Overview of the NEMO Protocol. . . . . . . . . . . . . . . . 4
4. Message Formats. . . . . . . . . . . . . . . . . . . . . . . 7
4.1. Binding Update. . . . . . . . . . . . . . . . . . . . . 7
4.2. Binding Acknowledgement . . . . . . . . . . . . . . . . 7
4.3. Mobile Network Prefix Option. . . . . . . . . . . . . . 8
5. Mobile Router Operation. . . . . . . . . . . . . . . . . . . 9
5.1. Data Structures . . . . . . . . . . . . . . . . . . . . 10
5.2. Sending Binding Updates . . . . . . . . . . . . . . . . 10
5.3. Receiving Binding Acknowledgements. . . . . . . . . . . 11
5.4. Error Processing . . . . . . . . . . . . . . . . . . . 12
5.4.1. Implicit Mode. . . . . . . . . . . . . . . . . . 12
5.4.2. Explicit Mode. . . . . . . . . . . . . . . . . . 12
5.5. Establishment of Bi-directional Tunnel . . . . . . . . 13
5.6. Neighbor Discovery for Mobile Router . . . . . . . . . 13
5.7. Multicast Groups for Mobile Router . . . . . . . . . . 14
5.8. Returning Home . . . . . . . . . . . . . . . . . . . . 14
6. Home Agent Operation . . . . . . . . . . . . . . . . . . . . 15
6.1. Data Structures . . . . . . . . . . . . . . . . . . . . 15
6.1.1. Binding Cache. . . . . . . . . . . . . . . . . . 15
6.1.2. Prefix Table . . . . . . . . . . . . . . . . . . 15
6.2. Mobile Network Prefix Registration . . . . . . . . . . 16
6.3. Advertising Mobile Network Reachability . . . . . . . . 17
6.4. Establishment of Bi-directional Tunnel . . . . . . . . 18
6.5. Forwarding Packets . . . . . . . . . . . . . . . . . . 18
6.6. Sending Binding Acknowledgements . . . . . . . . . . . 19
6.7. Mobile Network Prefix De-Registration . . . . . . . . . 19
7. Modifications to Dynamic Home Agent Address Discovery. . . . 20
7.1. Modified Dynamic Home Agent Discovery Request . . . . . 20
7.2. Modified Dynamic Home Agent Discovery Address Request . 20
7.3. Modified Home Agent Information Option . . . . . . . . 21
8. Support for Dynamic Routing Protocols. . . . . . . . . . . . 22
9. Security Considerations. . . . . . . . . . . . . . . . . . . 23
10. IANA Considerations. . . . . . . . . . . . . . . . . . . . . 24
11. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 25
12. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 25
13. References . . . . . . . . . . . . . . . . . . . . . . . . . 25
Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
A. Examples of NEMO Basic Support Operation. . . . . . . . . 27
B. Running Link State Routing Protocol with NEMO Basic
Support . . . . . . . . . . . . . . . . . . . . . . . . . 30
B.1. Tunnel Interface Considerations. . . . . . . . . . . 30
B.2. OSPF Area Considerations . . . . . . . . . . . . . . 30
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 32
Full Copyright Statement . . . . . . . . . . . . . . . . . . . . 33
This document describes protocol extensions to Mobile IPv6 (MIPv6) [1] to enable support for network mobility. The extensions are backward compatible with Mobile IPv6. In particular, a NEMO-compliant Home Agent can operate as a Mobile IPv6 Home Agent. The solution described here satisfies the goals and requirements identified in [11] for network mobility.
本文档描述了移动IPv6（MIPv6）[1]的协议扩展，以支持网络移动性。这些扩展与移动IPv6向后兼容。特别是，符合NEMO的归属代理可以作为移动IPv6归属代理运行。此处描述的解决方案满足[11]中确定的网络移动性目标和要求。
The NEMO Basic Support ensures session continuity for all the nodes in the Mobile Network, even as the Mobile Router changes its point of attachment to the Internet. It also provides connectivity and reachability for all nodes in the Mobile Network as it moves. The solution supports both mobile nodes and hosts that do not support mobility in the Mobile Network.
NEMO基本支持确保移动网络中所有节点的会话连续性，即使移动路由器更改其与互联网的连接点。当移动网络移动时，它还为移动网络中的所有节点提供连通性和可达性。该解决方案支持在移动网络中不支持移动的移动节点和主机。
Within the context of this document, the definition of a Mobile Router extends that of a Mobile IPv6 [1] Mobile Node, by adding routing capability routing between its point of attachment (Care-of Address) and a subnet that moves with the Mobile Router.
在本文档的上下文中，移动路由器的定义扩展了移动IPv6[1]移动节点的定义，通过在其连接点（转交地址）和随移动路由器移动的子网之间添加路由能力路由。
The solution described in this document proposes a bi-directional tunnel between the Mobile Router and its Home Agent. This tunnel is set up when the Mobile Router sends a successful Binding Update to its Home Agent, informing the Home Agent of its current point of attachment.
本文档中描述的解决方案提出了移动路由器与其归属代理之间的双向隧道。当移动路由器向其归属代理发送成功的绑定更新，通知归属代理其当前连接点时，将设置此隧道。
All traffic between the nodes in the Mobile Network and Correspondent Nodes passes through the Home Agent. This document does not describe route optimization of this traffic.
移动网络中的节点和对应节点之间的所有流量都通过归属代理。本文件不描述该交通的路线优化。
The terminology document [10] describes Nested Mobility as a scenario where a Mobile Router allows another Mobile Router to attach to its Mobile Network. There could be arbitrary levels of nested mobility. The operation of each Mobile Router remains the same whether the Mobile Router attaches to another Mobile Router or to a fixed Access Router on the Internet. The solution described here does not place any restriction on the number of levels for nested mobility. But note that this might introduce significant overhead on the data packets as each level of nesting introduces another IPv6 header encapsulation.
术语文档[10]将嵌套移动描述为移动路由器允许另一个移动路由器连接到其移动网络的场景。可以有任意级别的嵌套移动。无论移动路由器连接到另一个移动路由器还是互联网上的固定接入路由器，每个移动路由器的操作都保持不变。这里描述的解决方案对嵌套移动性的级别数没有任何限制。但请注意，这可能会给数据包带来很大的开销，因为每一层嵌套都会引入另一个IPv6报头封装。
This document does not discuss multihoming for Mobile Routers.
本文档不讨论移动路由器的多主。
The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14, RFC 2119 [7].
本文件中的关键词“必须”、“不得”、“要求”、“应”、“不得”、“应”、“不应”、“建议”、“可”和“可选”应按照BCP 14、RFC 2119[7]中的描述进行解释。
Network Mobility - related terminology is defined in [9] and [10]. This document in addition defines the following terms.
[9]和[10]中定义了与网络移动性相关的术语。本文件还定义了以下术语。
Mobile Network Prefix
移动网络前缀
An IPv6 prefix delegated to a Mobile Router and advertised in the Mobile Network. More than one Mobile Network Prefix could be advertised in a Mobile Network.
委派给移动路由器并在移动网络中播发的IPv6前缀。在一个移动网络中可以广告多个移动网络前缀。
Prefix Table
前缀表
A list of Mobile Network Prefixes indexed by the Home Address of a Mobile Router. The Home Agent manages and uses Prefix Table to determine which Mobile Network Prefixes belong to a particular Mobile Router.
由移动路由器的家庭地址索引的移动网络前缀列表。归属代理管理并使用前缀表来确定哪些移动网络前缀属于特定的移动路由器。
A Mobile Network is a network segment or subnet that can move and attach to arbitrary points in the routing infrastructure. A Mobile Network can only be accessed via specific gateways called Mobile Routers that manage its movement. Mobile Networks have at least one Mobile Router serving them. A Mobile Router does not distribute the Mobile Network routes to the infrastructure at its point of attachment (i.e., in the visited network). Instead, it maintains a bi-directional tunnel to a Home Agent that advertises an aggregation of Mobile Networks to the infrastructure. The Mobile Router is also the default gateway for the Mobile Network.
移动网络是可以移动并连接到路由基础设施中任意点的网段或子网。移动网络只能通过管理其移动的称为移动路由器的特定网关访问。移动网络至少有一个移动路由器为其服务。移动路由器不会在其连接点（即，在访问的网络中）将移动网络路由分发到基础设施。相反，它维护一个到归属代理的双向隧道，该代理向基础设施宣传移动网络的聚合。移动路由器也是移动网络的默认网关。
A Mobile Network can also comprise of multiple and nested subnets. A router without mobility support may be permanently attached to a Mobile Network for local distribution. Also, Mobile Routers may be attached to Mobile Networks owned by different Mobile Routers and may form a graph. In particular, with Basic NEMO Support, each Mobile Router is attached to another Mobile Network by a single interface. If loops are avoided, the graph is a tree.
移动网络还可以由多个子网和嵌套子网组成。没有移动性支持的路由器可以永久地连接到移动网络以进行本地分发。此外，移动路由器可以连接到不同移动路由器所拥有的移动网络，并且可以形成图。特别是，在基本NEMO支持下，每个移动路由器通过一个接口连接到另一个移动网络。如果避免循环，则图形是一棵树。
A Mobile Router has a unique Home Address through which it is reachable when it is registered with its Home Agent. The Home Address is configured from a prefix aggregated and advertised by its Home Agent. The prefix could be either the prefix advertised on the home link or the prefix delegated to the Mobile Router. The Mobile
移动路由器有一个唯一的家庭地址，当它向其家庭代理注册时，可以通过该地址访问它。家庭地址由其家庭代理聚合和公布的前缀配置。前缀可以是在归属链路上公布的前缀，也可以是委托给移动路由器的前缀。手机
Router can have more than one Home Address if there are multiple prefixes in the home link. The Mobile Router also advertises one or more prefixes in the Mobile Network attached to it. The actual mechanism for assigning these prefixes to a given Mobile Router is outside the scope of this specification.
如果主链路中有多个前缀，路由器可以有多个主地址。移动路由器还在连接到它的移动网络中播发一个或多个前缀。将这些前缀分配给给定移动路由器的实际机制不在本规范的范围内。
When the Mobile Router moves away from the home link and attaches to a new access router, it acquires a Care-of Address from the visited link. The Mobile Router can at any time act either as a Mobile Host or as a Mobile Router. It acts as a Mobile Host as defined in [1] for sessions it originates and provides connectivity to the Mobile Network. As soon as the Mobile Router acquires a Care-of Address, it immediately sends a Binding Update to its Home Agent as described in [1]. When the Home Agent receives this Binding Update, it creates a cache entry binding the Mobile Router's Home Address to its Care-of Address at the current point of attachment.
当移动路由器离开主链路并连接到新的接入路由器时，它从访问的链路获取转交地址。移动路由器可以在任何时候充当移动主机或移动路由器。它充当[1]中定义的移动主机，用于发起会话，并提供与移动网络的连接。一旦移动路由器获得转交地址，它立即向其归属代理发送绑定更新，如[1]所述。当归属代理收到此绑定更新时，它将创建一个缓存条目，将移动路由器的归属地址绑定到当前连接点的转交地址。
If the Mobile Router seeks to act as a Mobile Router and provide connectivity to nodes in the Mobile Network, it indicates this to the Home Agent by setting a flag (R) in the Binding Update. It MAY also include information about the Mobile Network Prefix in the Binding Update by using one of the modes described in section 5.2, so that the Home Agent can forward packets meant for nodes in the Mobile Network to the Mobile Router. A new Mobility Header Option for carrying prefix information is described in section 4.3. If the Mobile Network has more than one IPv6 prefix and wants the Home Agent to setup forwarding for all of these prefixes, it includes multiple prefix information options in a single Binding Update. The Home Agent sets up forwarding for each of these prefixes to the Mobile Router's Care-of Address. In some scenarios the Home Agent would already know which prefixes belong to a Mobile Router by an alternate mechanism such as static configuration. In these scenarios, the Mobile Router does not include any prefix information in the Binding Update. The Home Agent sets up forwarding for all prefixes owned by the Mobile Router when it receives a Binding Update from the Mobile Router with the Mobile Router Flag (R) set.
如果移动路由器寻求充当移动路由器并向移动网络中的节点提供连接，则它通过在绑定更新中设置标志（R）来向归属代理指示这一点。它还可以通过使用第5.2节中描述的模式之一在绑定更新中包括关于移动网络前缀的信息，以便归属代理可以将用于移动网络中的节点的分组转发给移动路由器。第4.3节描述了一种新的用于承载前缀信息的移动报头选项。如果移动网络具有多个IPv6前缀，并且希望归属代理为所有这些前缀设置转发，则它在单个绑定更新中包含多个前缀信息选项。归属代理为每个前缀设置到移动路由器转交地址的转发。在某些情况下，归属代理可能已经通过诸如静态配置之类的替代机制知道哪些前缀属于移动路由器。在这些场景中，移动路由器在绑定更新中不包含任何前缀信息。当Home Agent从移动路由器接收到设置了移动路由器标志（R）的绑定更新时，它为移动路由器拥有的所有前缀设置转发。
The Home Agent acknowledges the Binding Update by sending a Binding Acknowledgement to the Mobile Router. A positive acknowledgement with the Mobile Router Flag (R) set means that the Home Agent has set up forwarding for the Mobile Network. Once the binding process finishes, a bi-directional tunnel is established between the Home Agent and the Mobile Router. The tunnel end points are the Mobile Router's Care-of Address and the Home Agent's address. If a packet with a source address belonging to the Mobile Network Prefix is received from the Mobile Network, the Mobile Router reverse-tunnels the packet to the Home Agent through this tunnel. This reverse-tunneling is done by using IP-in-IP encapsulation [3]. The Home
归属代理通过向移动路由器发送绑定确认来确认绑定更新。设置了移动路由器标志（R）的肯定确认意味着归属代理已经为移动网络设置了转发。一旦绑定过程完成，就会在归属代理和移动路由器之间建立一个双向隧道。隧道端点是移动路由器的转交地址和归属代理的地址。如果从移动网络接收到具有属于移动网络前缀的源地址的分组，则移动路由器通过该隧道将该分组反向隧道到归属代理。这种反向隧道是通过在IP封装中使用IP来完成的[3]。家
Agent decapsulates this packet and forwards it to the Correspondent Node. For traffic originated by itself, the Mobile Router can use either reverse tunneling or route optimization, as specified in [1].
代理解除此数据包的封装并将其转发到对应节点。对于自身发起的流量，移动路由器可以使用反向隧道或路由优化，如[1]中所述。
When a Correspondent Node sends a data packet to a node in the Mobile Network, the packet is routed to the Home Agent that currently has the binding for the Mobile Router. The Mobile Router's network prefix would be aggregated at the Home Agent, which would advertise the resulting aggregation. Alternatively, the Home Agent may receive the data packets destined to the Mobile Network by advertising routes to the Mobile Network Prefix. The actual mechanism by which these routes are advertised is outside the scope of this document. When the Home Agent receives a data packet meant for a node in the Mobile Network, it tunnels the packet to the Mobile Router's current Care-of Address. The Mobile Router decapsulates the packet and forwards it onto the interface where the Mobile Network is connected. Before decapsulating the tunneled packet, the Mobile Router has to check whether the Source address on the outer IPv6 header is the Home Agent's address. This check is not necessary if the packet is protected by IPsec in tunnel mode. The Mobile Router also has to make sure that the destination address on the inner IPv6 header belongs to a prefix used in the Mobile Network before forwarding the packet to the Mobile Network. If it does not, the Mobile Router should drop the packet.
当移动代理将数据包当前路由到移动代理中的归属节点时，移动代理将数据包发送到该归属节点。移动路由器的网络前缀将在归属代理处聚合，归属代理将公布生成的聚合。或者，归属代理可以通过向移动网络前缀发送路由广告来接收目的地为移动网络的数据分组。公布这些路线的实际机制不在本文件范围内。当归属代理接收到用于移动网络中的节点的数据分组时，它通过隧道将该分组传送到移动路由器的当前转交地址。移动路由器解除数据包的封装，并将其转发到移动网络连接的接口上。在解除隧道数据包的封装之前，移动路由器必须检查外部IPv6报头上的源地址是否是归属代理的地址。如果数据包在隧道模式下受IPsec保护，则无需进行此检查。在将数据包转发到移动网络之前，移动路由器还必须确保内部IPv6报头上的目标地址属于移动网络中使用的前缀。如果没有，移动路由器应该丢弃数据包。
The Mobile Network could include nodes that do not support mobility and nodes that do. A node in the Mobile Network can also be a fixed or a Mobile Router. The protocol described here ensures complete transparency of network mobility to the nodes in the Mobile Network. Mobile Nodes that attach to the Mobile Network treat it as a normal IPv6 access network and run the Mobile IPv6 protocol.
移动网络可以包括不支持移动的节点和支持移动的节点。移动网络中的节点也可以是固定或移动路由器。这里描述的协议确保了网络移动性对移动网络中的节点的完全透明。连接到移动网络的移动节点将其视为正常的IPv6接入网络，并运行移动IPv6协议。
The Mobile Router and the Home Agent can run a routing protocol through the bi-directional tunnel. In this case, the Mobile Router need not include prefix information in the Binding Update. Instead, the Home Agent uses the routing protocol updates to set up forwarding for the Mobile Network. When the routing protocol is running, the bi-directional tunnel must be treated as a tunnel interface. The tunnel interface is included in the list of interfaces on which routing protocol is active. The Mobile Router should be configured not to send any routing protocol messages on its egress interface when it is away from the home link and connected to a visited link.
移动路由器和归属代理可以通过双向隧道运行路由协议。在这种情况下，移动路由器不需要在绑定更新中包括前缀信息。相反，归属代理使用路由协议更新为移动网络设置转发。当路由协议运行时，必须将双向隧道视为隧道接口。隧道接口包括在路由协议处于活动状态的接口列表中。当移动路由器远离主链路并连接到访问链路时，应将其配置为不在其出口接口上发送任何路由协议消息。
Finally, the Home Agent may be configured with static routes to the Mobile Network Prefix via the Mobile Router's Home Address. In this case, the routes are set independently of the binding flows and the returning home of a Mobile Router. The benefit is that such movement does not induce additional signalling in the form of routing updates
最后，归属代理可以通过移动路由器的归属地址配置到移动网络前缀的静态路由。在这种情况下，路由的设置独立于绑定流和移动路由器的回家。这样做的好处是，这种移动不会以路由更新的形式引发额外的信令
in the home network. The drawback is that the routes are present even if the related Mobile Routers are not reachable (at home or bound) at a given point of time.
在家庭网络中。缺点是即使相关的移动路由器在给定的时间点不可到达（在家中或绑定），路由仍然存在。
A new flag (R) is included in the Binding Update to indicate to the Home Agent whether the Binding Update is coming from a Mobile Router and not from a mobile node. The rest of the Binding Update format remains the same as defined in [1].
绑定更新中包括新标志（R），以向归属代理指示绑定更新是否来自移动路由器而不是来自移动节点。绑定更新格式的其余部分与[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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sequence # |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|A|H|L|K|M|R| Reserved | Lifetime |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sequence # |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|A|H|L|K|M|R| Reserved | Lifetime |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Mobile Router Flag (R)
移动路由器标志（R）
The Mobile Router Flag is set to indicate to the Home Agent that the Binding Update is from a Mobile Router. If the flag is set to 0, the Home Agent assumes that the Mobile Router is behaving as a Mobile Node, and it MUST NOT forward packets destined for the Mobile Network to the Mobile Router.
移动路由器标志设置为向归属代理指示绑定更新来自移动路由器。如果标志设置为0，则归属代理假定移动路由器作为移动节点运行，并且它不得将目的地为移动网络的数据包转发给移动路由器。
Mobility Options
移动选项
A variable length field that can include zero or more mobility options. This document defines a new mobility option in addition to what is defined in [1].
可包含零个或多个移动选项的可变长度字段。除了[1]中的定义外，本文件还定义了一个新的移动选项。
For descriptions of the other fields in the message, see [1].
有关消息中其他字段的说明，请参见[1]。
A new flag (R) is included in the Binding Acknowledgement to indicate that the Home Agent that processed the corresponding Binding Update supports Mobile Routers. The flag is set only if the corresponding Binding Update had the Mobile Router Flag (R) set to 1. The rest of the Binding Acknowledgement format remains the same, as defined in [1].
绑定确认中包括新标志（R），以指示处理相应绑定更新的归属代理支持移动路由器。仅当相应的绑定更新将移动路由器标志（R）设置为1时，才会设置该标志。其余的绑定确认格式保持不变，如[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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Status |K|R| Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sequence # | Lifetime |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Status |K|R| Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sequence # | Lifetime |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Mobile Router Flag (R)
移动路由器标志（R）
The Mobile Router Flag is set to indicate that the Home Agent that processed the Binding Update supports Mobile Routers. It is set to 1 only if the corresponding Binding Update had the Mobile Router Flag set to 1.
移动路由器标志设置为指示处理绑定更新的归属代理支持移动路由器。仅当相应的绑定更新将移动路由器标志设置为1时，才会将其设置为1。
For descriptions of the other fields in the message, see [1].
有关消息中其他字段的说明，请参见[1]。
This document also introduces the following new Binding Acknowledgement status values. The values shown below are decimal values.
本文档还介绍了以下新的绑定确认状态值。下面显示的值是十进制值。
140 Mobile Router Operation not permitted
140不允许移动路由器操作
141 Invalid Prefix
141无效前缀
142 Not Authorized for Prefix
142未授权使用前缀
143 Forwarding Setup failed (prefixes missing)
143转发设置失败（缺少前缀）
Status values less than 128 indicate that the Binding Update was processed successfully by the receiving nodes. Values greater than 128 indicate that the Binding Update was rejected by the Home Agent.
小于128的状态值表示接收节点已成功处理绑定更新。大于128的值表示绑定更新被归属代理拒绝。
The Mobile Network Prefix Option is included in the Binding Update to indicate the prefix information for the Mobile Network to the Home Agent. There could be multiple Mobile Network Prefix Options if the Mobile Router has more than one IPv6 prefix in the Mobile Network and wants the Home Agent to forward packets for each of these prefixes to the Mobile Router's current location.
绑定更新中包括移动网络前缀选项，以向归属代理指示移动网络的前缀信息。如果移动路由器在移动网络中有多个IPv6前缀，并且希望归属代理将每个前缀的数据包转发到移动路由器的当前位置，则可能有多个移动网络前缀选项。
The Mobile Network Prefix Option has an alignment requirement of 8n+4. Its format is as follows.
移动网络前缀选项的对齐要求为8n+4。其格式如下。
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | Reserved | Prefix Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
+ +
| |
+ Mobile Network Prefix +
| |
+ +
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | Reserved | Prefix Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
+ +
| |
+ Mobile Network Prefix +
| |
+ +
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type
类型
6
6.
Length
长
Eight-bit unsigned integer indicating the length in octets of the option, excluding the type and length fields. Set to 18.
八位无符号整数，表示选项的长度（以八位字节为单位），不包括类型和长度字段。设置为18。
Reserved
含蓄的
This field is unused for now. The value MUST be initialized to 0 by the sender and MUST be ignored by the receiver.
此字段目前未使用。发送方必须将该值初始化为0，接收方必须忽略该值。
Prefix Length
前缀长度
Eight-bit unsigned integer indicating the prefix length of the IPv6 prefix contained in the option.
八位无符号整数，指示选项中包含的IPv6前缀的前缀长度。
Mobile Network Prefix
移动网络前缀
A sixteen-byte field containing the Mobile Network Prefix
包含移动网络前缀的16字节字段
Mobile Router operation is derived largely from the combined behaviors of a host, of a router [5], and of a Mobile Node [1].
移动路由器操作主要源自主机、路由器[5]和移动节点[1]的组合行为。
A Mobile Node can act in two ways: (1) as a Mobile Host, in which case the Home Agent doesn't maintain any prefix information related to the Mobile Host's Home Address but does maintain a binding cache entry related to the Mobile Host's Home Address, and (2) as a Mobile Router, in which case, in addition to maintaining the binding cache entry corresponding to the Mobile Router Home Address, the Home Agent
移动节点可以以两种方式工作：（1）作为移动主机，在这种情况下，归属代理不维护与移动主机的归属地址相关的任何前缀信息，而是维护与移动主机的归属地址相关的绑定缓存项，以及（2）作为移动路由器，在这种情况下，除了维护与移动路由器主地址对应的绑定缓存条目外，主代理
maintains forwarding information related to prefixes assigned to the Mobile Network. The distinction between the two modes is represented by the value of the Mobile Router Flag (R).
维护与分配给移动网络的前缀相关的转发信息。两种模式之间的区别由移动路由器标志（R）的值表示。
A Mobile Router MUST implement all requirements for IPv6 Mobile Nodes as described in section 8.5 of [1].
移动路由器必须实现[1]第8.5节所述的IPv6移动节点的所有要求。
Like a Mobile Host, a Mobile Router also maintains a Binding Update List, described in section 11.1 of the Mobile IPv6 specification [1]. The Binding Update list is a conceptual data structure that records information sent in the Binding Updates. There is one entry per each destination to which the Mobile Router is currently sending Binding Updates.
与移动主机一样，移动路由器也维护绑定更新列表，如移动IPv6规范[1]第11.1节所述。绑定更新列表是一个概念数据结构，它记录绑定更新中发送的信息。移动路由器当前向其发送绑定更新的每个目的地都有一个条目。
This document introduces a new Prefix Information field in the Binding Update list structure. This field is used to store any prefix information that the Mobile Router includes in the Binding Update. If the Mobile Router sets the Mobile Router Flag (R) in the Binding Update but does not include any prefix information in it this field is set to null. The Mobile Router does not include prefix information in the Binding Update in the implicit mode or when it, runs a dynamic routing protocol with its Home Agent.
本文档在绑定更新列表结构中引入了一个新的前缀信息字段。此字段用于存储移动路由器在绑定更新中包含的任何前缀信息。如果移动路由器在绑定更新中设置移动路由器标志（R），但其中不包含任何前缀信息，则此字段设置为null。移动路由器在隐式模式下的绑定更新中不包含前缀信息，或者当它使用其归属代理运行动态路由协议时不包含前缀信息。
As does a Mobile Host, a Mobile Router stores the information regarding status of flags of the Binding Update in the corresponding Binding Update List entry. This document introduces a new Mobile Router Flag (R) for this entry. The status of this flag is stored in the Binding Update list whenever a Binding Update is sent.
与移动主机一样，移动路由器在相应的绑定更新列表条目中存储关于绑定更新的标志状态的信息。本文档为此条目引入了一个新的移动路由器标志（R）。每当发送绑定更新时，此标志的状态都存储在绑定更新列表中。
A Mobile Router also maintains a Home Agent list populated according to the same procedure as a Mobile Host.
移动路由器还维护根据与移动主机相同的过程填充的归属代理列表。
A Mobile Router sends Binding Updates to its Home Agent, as described in [1]. If the Mobile Router is not running a routing protocol as described in section 8, it uses one of the following modes to tell the Home Agent to determine which prefixes belong to the Mobile Router. In both modes, the Mobile Router sets the Mobile Router Flag (R).
移动路由器向其归属代理发送绑定更新，如[1]所述。如果移动代理使用以下8节中描述的移动路由器前缀来确定它不属于哪个路由器。在这两种模式中，移动路由器都设置移动路由器标志（R）。
Implicit:
隐性的：
In this mode, the Mobile Router does not include a Mobile Network Prefix Option in the Binding Update. The Home Agent can use any mechanism (not defined in this document) to
在此模式下，移动路由器在绑定更新中不包括移动网络前缀选项。归属代理可以使用任何机制（本文档中未定义）来
determine the Mobile Network Prefix(es) owned by the Mobile Router and to set up forwarding for the Mobile Network. One example would be manual configuration at the Home Agent mapping the Mobile Router's Home Address to the information required for setting up forwarding for the Mobile Network.
确定移动路由器拥有的移动网络前缀，并为移动网络设置转发。一个例子是在归属代理处手动配置，将移动路由器的归属地址映射到为移动网络设置转发所需的信息。
Explicit:
明确的：
In this mode, the Mobile Router includes one or more Mobile Network Prefix Options in the Binding Update. These options contain information about the Mobile Network Prefix(es) configured on the Mobile Network.
在此模式下，移动路由器在绑定更新中包括一个或多个移动网络前缀选项。这些选项包含有关在移动网络上配置的移动网络前缀的信息。
A Mobile Router MUST implement at least one mode and MAY implement both. In the latter case, local configuration on the Mobile Router decides which mode to use. This is out of scope for this document.
移动路由器必须实现至少一种模式，并且可以同时实现两种模式。在后一种情况下，移动路由器上的本地配置决定使用哪种模式。这超出了本文档的范围。
If the Mobile Router Flag is set, the Home Registration Flag (H) MUST be set.
如果设置了移动路由器标志，则必须设置归属注册标志（H）。
If the Mobile Router has a valid binding cache entry at the Home Agent, subsequent Binding Updates for the same Home Address should have the same value as the value in the binding cache for the Mobile Router Flag (R). In explicit mode, the Mobile Router MUST include prefix information in all Binding Updates, including those sent to refresh existing binding cache entries, if it wants forwarding enabled for the corresponding Mobile Network Prefixes.
如果移动路由器在归属代理中具有有效的绑定缓存项，则相同归属地址的后续绑定更新应具有与移动路由器标志（R）的绑定缓存中的值相同的值。在显式模式下，如果移动路由器希望为相应的移动网络前缀启用转发，则必须在所有绑定更新（包括发送用于刷新现有绑定缓存项的更新）中包含前缀信息。
The Mobile Router receives Binding Acknowledgements from the Home Agent corresponding to the Binding Updates it sent. If the Binding Acknowledgement status is set to 0 (Binding Update accepted) and the Mobile Router Flag (R) is set to 1, the Mobile Router assumes that the Home Agent has successfully processed the Binding Update and has set up forwarding for the Mobile Network. The Mobile Router can then start using the bi-directional tunnel to reverse-tunnel traffic from the Mobile Network. If the Mobile Router Flag (R) is not set, then the Mobile Router concludes that its current Home Agent does not support Mobile Routers and it performs Dynamic Home Agent Address Discovery again to discover Home Agents that do. The Mobile Router MUST also de-register with the Home Agent that did not support it before attempting registration with another.
移动路由器从归属代理接收与其发送的绑定更新对应的绑定确认。如果绑定确认状态设置为0（已接受绑定更新）且移动路由器标志（R）设置为1，则移动路由器假定归属代理已成功处理绑定更新并已为移动网络设置转发。然后，移动路由器可以开始使用双向隧道来反转来自移动网络的隧道流量。如果未设置移动路由器标志（R），则移动路由器认为其当前归属代理不支持移动路由器，并再次执行动态归属代理地址发现，以发现支持移动路由器的归属代理。移动路由器还必须先向不支持它的归属代理注销，然后再尝试向其他代理注册。
If the Binding Acknowledgement status is set to a value between 128 and 139, the Mobile Router takes necessary actions as described in the Mobile IPv6 specification [1]. For the Binding Acknowledgement status values defined in this document, the following sections explain the Mobile Router's behavior.
如果绑定确认状态设置为128到139之间的值，则移动路由器将采取移动IPv6规范[1]中所述的必要操作。对于本文档中定义的绑定确认状态值，以下部分将解释移动路由器的行为。
In Implicit mode, the Mobile Router interprets only error statuses 140 (Mobile Router Operation not permitted) and 143 (Forwarding Setup failed). The Mobile Router MUST treat Binding Acknowledgements with statuses '141' and '142' as fatal errors, since they should not be sent by the Home Agent in implicit mode.
在隐式模式中，移动路由器仅解释错误状态140（不允许移动路由器操作）和143（转发设置失败）。移动路由器必须将状态为“141”和“142”的绑定确认视为致命错误，因为它们不应由归属代理以隐式模式发送。
If the Binding Acknowledgement from the Home Agent has the status 140, the Mobile Router SHOULD send a Binding Update to another Home Agent on the same home link. If no Home Agent replies positively, the Mobile Router MUST refrain from sending Binding Updates with the Mobile Router Flag set to any Home Agent on the home link, and it must log the information.
如果来自归属代理的绑定确认具有状态140，则移动路由器应向同一归属链路上的另一归属代理发送绑定更新。如果没有归属代理作出肯定的答复，则移动路由器必须避免发送绑定更新，并将移动路由器标志设置为归属链路上的任何归属代理，并且必须记录信息。
If the Binding Acknowledgement has the status 143, the Mobile Router SHOULD send a Binding Update to another Home Agent on the same home link. If no Home Agent replies positively, the Mobile Router SHOULD refrain from sending this Binding Update to any Home Agent on the home link, and MAY send Binding Updates in Explicit mode to a Home Agent on the same home link.
如果绑定确认具有状态143，则移动路由器应向同一归属链路上的另一归属代理发送绑定更新。如果没有归属代理作出肯定的答复，则移动路由器应避免向归属链路上的任何归属代理发送此绑定更新，并且可以以显式模式向同一归属链路上的归属代理发送绑定更新。
If the Mobile Router sent a Binding Update to the Home Agent in explicit mode, then the Mobile Router interprets only error statuses 140 (Mobile Router Operation not permitted), 141 (Invalid Prefix), and 142 (Not Authorized for Prefix). The Mobile Router MUST treat Binding Acknowledgements with status '143' as a fatal error, since it should not be sent by the Home Agent in explicit mode.
如果移动路由器以显式模式向归属代理发送绑定更新，则移动路由器仅解释错误状态140（不允许移动路由器操作）、141（无效前缀）和142（未授权前缀）。移动路由器必须将状态为“143”的绑定确认视为致命错误，因为它不应由归属代理以显式模式发送。
If the Binding Acknowledgement from the Home Agent has the status 140, the Mobile Router SHOULD send a Binding Update to another Home Agent on the same home link. If no Home Agent replies positively, then the Mobile Router MUST refrain from sending Binding Updates with the Mobile Router Flag set to any Home Agent on the home link, and it must log the information.
如果来自归属代理的绑定确认具有状态140，则移动路由器应向同一归属链路上的另一归属代理发送绑定更新。如果没有归属代理作出肯定的答复，则移动路由器必须避免向归属链路上的任何归属代理发送设置了移动路由器标志的绑定更新，并且必须记录信息。
If the Binding Acknowledgement has the status 141 or 142, the Mobile Router SHOULD send a Binding Update to another Home Agent on the same
如果绑定确认具有状态141或142，则移动路由器应向同一路径上的另一归属代理发送绑定更新
home link. If no Home Agent replies positively, then the Mobile Router SHOULD refrain from sending Binding Updates to any Home Agent on the home link. The Mobile Router MUST also stop advertising the prefix in the Mobile Network and try to obtain new IPv6 prefix information for the Mobile Network. It would do this by the same means that it initially got assigned the current Mobile Network Prefix. Alternatively, the Mobile Router MAY send Binding Updates in Implicit mode to a Home Agent on the same home link.
主页链接。如果没有归属代理作出肯定的答复，则移动路由器应避免向归属链路上的任何归属代理发送绑定更新。移动路由器还必须停止在移动网络中宣传前缀，并尝试获取移动网络的新IPv6前缀信息。它将通过与最初分配当前移动网络前缀相同的方式来实现这一点。或者，移动路由器可以隐式模式向同一归属链路上的归属代理发送绑定更新。
If by the end of this Error Processing procedure, as described in sections 5.4.1 and 5.4.2, the Mobile Router has tried every available mode and still has not received a positive Binding Acknowledgement, the Mobile Router MUST stop sending Binding Updates with the Mobile Router Flag set for this Home Address and it must log the information.
如第5.4.1节和第5.4.2节所述，如果在该错误处理过程结束时，移动路由器已尝试了所有可用模式，但仍未收到肯定的绑定确认，则移动路由器必须停止发送绑定更新，并使用为此家庭地址设置的移动路由器标志记录信息。
In all cases above, the Mobile Router MUST conclude that the Home Agent did not create a binding cache entry for the Mobile Router's Home Address.
在上述所有情况下，移动路由器必须断定归属代理没有为移动路由器的归属地址创建绑定缓存条目。
When a successful Binding Acknowledgement is received, the Mobile Router sets up its endpoint of the bi-directional tunnel.
当接收到成功的绑定确认时，移动路由器设置其双向隧道的端点。
The bi-directional tunnel between the Mobile Router and the Home Agent allows packets to flow in both directions, while the Mobile Router is connected to a visited link. The bi-directional tunnel is created by merging two unidirectional tunnels, as described in RFC 2473 [3]. The tunnel from the Mobile Router to the Home Agent has the Care-of address of the Mobile Router as the tunnel entry point and the Home Agent's address as the tunnel exit point. The tunnel from the Home Agent to the Mobile Router has the Home Agent's address and the Mobile Router's Care-of Address as the tunnel entry point and exit point, respectively. All IPv6 traffic to and from the Mobile Network is sent through this bi-directional tunnel.
移动路由器和归属代理之间的双向隧道允许数据包在两个方向上流动，同时移动路由器连接到访问的链路。如RFC 2473[3]所述，通过合并两个单向隧道创建双向隧道。从移动路由器到归属代理的隧道将移动路由器的转交地址作为隧道入口点，将归属代理的地址作为隧道出口点。从归属代理到移动路由器的隧道将归属代理的地址和移动路由器的转交地址分别作为隧道入口点和出口点。所有进出移动网络的IPv6流量都通过此双向隧道发送。
A Mobile Router uses the Tunnel Hop Limit normally assigned to routers (not to hosts). Please refer to [3] for more details.
移动路由器使用通常分配给路由器（而不是主机）的隧道跳数限制。有关更多详细信息，请参阅[3]。
When the Mobile Router is at home, it MAY be configured to send Router Advertisements and to reply to Router Solicitations on the interface attached to the home link. The value of the Router Lifetime field SHOULD be set to 0 to prevent other nodes from configuring the Mobile Router as the default router.
当移动路由器在家中时，它可以被配置为发送路由器广告并在连接到家庭链路的接口上回复路由器请求。路由器生存期字段的值应设置为0，以防止其他节点将移动路由器配置为默认路由器。
A Mobile Router SHOULD NOT send unsolicited Router Advertisements and SHOULD NOT reply to Router Solicitations on any egress interface when that interface is attached to a visited link. However, the Mobile Router SHOULD reply with Neighbor Advertisements to Neighbor Solicitations received on the egress interface, for addresses valid on the visited link.
移动路由器不应发送未经请求的路由器广告，并且当任何出口接口连接到访问的链路时，不应回复该接口上的路由器请求。然而，对于在访问的链路上有效的地址，移动路由器应该用邻居广告回复在出口接口上接收到的邻居请求。
A router typically ignores Router Advertisements sent by other routers on a link. However, a Mobile Router MUST NOT ignore Router Advertisements received on the egress interface. The received Router Advertisements MAY be used for address configuration, default router selection, or movement detection.
路由器通常忽略链路上其他路由器发送的路由器广告。然而，移动路由器不得忽略在出口接口上接收的路由器广告。接收到的路由器广告可用于地址配置、默认路由器选择或移动检测。
When at home, the Mobile Router joins the multicast group All Routers Address with scopes 1 interface-local (on the home-advertising interface), and 2 link-local, on any of its egress interfaces. When in a visited network, the Mobile Router MUST NOT join the above multicast groups on the corresponding interface.
在家中时，移动路由器加入多播组所有路由器地址，作用域1为本地接口（在家庭广告接口上），2为本地链路（在其任何出口接口上）。在访问网络中时，移动路由器不得在相应接口上加入上述多播组。
When the Mobile Router detects that it has returned to its home link, it MUST de-register with its Home Agent. The Mobile Router MUST implement and follow the returning-home procedures defined for a mobile node in [1]. In addition, the Mobile Router MAY start behaving as a router on its egress interface, especially as follows:
当移动路由器检测到它已返回其主链路时，它必须向其主代理注销。移动路由器必须实施并遵循[1]中为移动节点定义的回家程序。此外，移动路由器可开始在其出口接口上作为路由器运行，尤其如下所示：
- The Mobile Router MAY send Router Advertisements on its egress interfaces, but the router lifetime SHOULD be set to 0 so that hosts on the home link do not pick the Mobile Router as the default router.
- 移动路由器可以在其出口接口上发送路由器广告，但路由器生存期应设置为0，以便家庭链路上的主机不会选择移动路由器作为默认路由器。
- The Mobile Router MAY join the All Routers Address multicast group on the home link.
- 移动路由器可以加入归属链路上的所有路由器地址多播组。
- The Mobile Router MAY send routing protocol messages on its egress interface if it is configured to run a dynamic routing protocol.
- 如果移动路由器被配置为运行动态路由协议，则移动路由器可以在其出口接口上发送路由协议消息。
When the Mobile Router sends a de-registration Binding Update in Explicit mode, it SHOULD NOT include any Mobile Network Prefix options in the Binding Update. When the Home Agent removes a binding cache entry, it deletes all associated Mobile Network Prefix routes.
当移动路由器以显式模式发送取消注册绑定更新时，绑定更新中不应包含任何移动网络前缀选项。当归属代理删除绑定缓存项时，它将删除所有关联的移动网络前缀路由。
For a Mobile Router to operate correctly, the Home Agent MUST satisfy all the requirements listed in section 8.4 of [1]. The Home Agent MUST implement both modes described in section 5.2 of this document.
为了使移动路由器正常运行，归属代理必须满足[1]第8.4节中列出的所有要求。归属代理必须实施本文件第5.2节所述的两种模式。
The Home Agent maintains Binding Cache Entries for each Mobile Router currently registered with the Home Agent. The Binding Cache is a conceptual data structure described in detail in [1].
归属代理维护当前向归属代理注册的每个移动路由器的绑定缓存项。绑定缓存是[1]中详细描述的概念数据结构。
The Home Agent might need to store the Mobile Network Prefixes associated with a Mobile Router in the corresponding Binding Cache Entry. This is required if the Binding Update that created the Binding Cache Entry contained explicit prefix information. This information can be used later to clean up routes installed in explicit mode, when the Binding Cache Entry is removed, and to maintain the routing table, for instance, should the routes be removed manually.
归属代理可能需要将与移动路由器相关联的移动网络前缀存储在相应的绑定缓存条目中。如果创建绑定缓存项的绑定更新包含显式前缀信息，则需要执行此操作。当删除绑定缓存项时，此信息可用于稍后清理以显式模式安装的路由，并用于维护路由表（例如，如果手动删除路由）。
The Home Agent also stores the status of the Mobile Router Flag (R) in the Binding Cache entry.
归属代理还将移动路由器标志（R）的状态存储在绑定缓存条目中。
The Home Agent SHOULD be able to prevent a Mobile Router from claiming Mobile Network Prefixes belonging to another Mobile Router. The Home Agent can prevent such attacks if it maintains a Prefix Table and verifies the prefix information provided by the Mobile Router against Prefix Table entries. The Prefix Table SHOULD be used by the Home Agent when it processes a Binding Update in explicit mode. It is not required when a dynamic routing protocol is run between the Mobile Router and the Home Agent.
归属代理应该能够防止移动路由器声明属于另一个移动路由器的移动网络前缀。如果归属代理维护前缀表并根据前缀表条目验证移动路由器提供的前缀信息，则归属代理可以防止此类攻击。当主代理以显式模式处理绑定更新时，应该使用前缀表。当在移动路由器和归属代理之间运行动态路由协议时，不需要它。
Each entry in the Prefix Table contains the following fields:
前缀表中的每个条目都包含以下字段：
- The Home Address of the Mobile Router. This field is used as the key for searching the pre-configured Prefix Table.
- 移动路由器的家庭地址。此字段用作搜索预配置前缀表的键。
- The Mobile Network Prefix of the Mobile Router associated with the Home Address.
- 与家庭地址关联的移动路由器的移动网络前缀。
The Home Agent processes the Binding Update as described in section 10.3.1 of the Mobile IPv6 specification [1]. This section describes the processing of the Binding Update if the Mobile Router (R) Flag is set. The Home Agent performs the following check.
归属代理按照移动IPv6规范[1]第10.3.1节所述处理绑定更新。本节描述在设置移动路由器（R）标志时绑定更新的处理。归属代理执行以下检查。
- The Home Registration (H) Flag MUST be set. If it is not, the Home Agent MUST reject the Binding Update and send a Binding Acknowledgement with status set to 140. Note: The basic support does not allow sending a Binding Update for a Mobile Network Prefix to correspondent nodes (for route optimization).
- 必须设置家庭注册（H）标志。如果不是，则归属代理必须拒绝绑定更新并发送状态设置为140的绑定确认。注意：基本支持不允许向对应节点发送移动网络前缀的绑定更新（用于路由优化）。
- Mobile IPv6 specification [1] requires that the Home Address in the Binding Update be configured from a prefix advertised on the home link. Otherwise the Binding Update is rejected with status value 132 [1]. This specification relaxes this requirement so that the Home Agent rejects the Binding Update only if the Home Address does not belong to the prefix that the Home Agent is configured to serve.
- 移动IPv6规范[1]要求绑定更新中的家庭地址根据家庭链路上公布的前缀进行配置。否则，将以状态值132[1]拒绝绑定更新。本规范放宽了这一要求，以便仅当归属地址不属于归属代理配置为服务的前缀时，归属代理才拒绝绑定更新。
If the Home Agent has a valid binding cache entry for the Mobile Router, and if the Binding Update has the Mobile Router Flag (R) set to a value different from that in the existing binding cache entry, then the Home Agent MUST reject the Binding Update and send a Binding Acknowledgement with status set to 139 (Registration type change disallowed). However, if the Binding Update is a de-registration Binding Update, the Home Agent ignores the value of the Mobile Router Flag (R).
如果归属代理具有移动路由器的有效绑定缓存项，并且如果绑定更新将移动路由器标志（R）设置为与现有绑定缓存项不同的值，则归属代理必须拒绝绑定更新并发送状态设置为139的绑定确认（不允许注册类型更改）. 但是，如果绑定更新是取消注册绑定更新，则归属代理将忽略移动路由器标志（R）的值。
If the Lifetime specified in the Binding Update is 0 or the specified Care-of address matches the Home Address in the Binding Update, then this is a request to delete the cached binding for the home address and specified Mobile Network Prefixes. The Binding Update is processed as described in section 6.7.
如果绑定更新中指定的生存期为0，或者指定的转交地址与绑定更新中的家庭地址匹配，则这是删除家庭地址和指定移动网络前缀的缓存绑定的请求。绑定更新的处理如第6.7节所述。
If the Home Agent does not reject the Binding Update as invalid, and if a dynamic routing protocol is not run between the Home Agent and the Mobile Router as described in section 8, then the Home Agent retrieves the Mobile Network Prefix information as described below.
如果归属代理未将绑定更新视为无效而拒绝，并且如果未如第8节所述在归属代理和移动路由器之间运行动态路由协议，则归属代理检索移动网络前缀信息，如下所述。
- If a Mobile Network Prefix Option is present in the Binding Update, the prefix information for the Mobile Network Prefix is retrieved from the Mobile Network Prefix field and the Prefix Length field of the option. If the Binding Update contains more than one option, the Home Agent MUST set up forwarding for all the Mobile Network Prefixes. If the Home Agent fails to set up forwarding to all the prefixes listed in the Binding Update, then
- 如果绑定更新中存在移动网络前缀选项，则从该选项的移动网络前缀字段和前缀长度字段检索移动网络前缀的前缀信息。如果绑定更新包含多个选项，则归属代理必须为所有移动网络前缀设置转发。如果归属代理无法设置转发到绑定更新中列出的所有前缀，则
it MUST NOT forward traffic to any of the prefixes. Furthermore, it MUST reject the Binding Update and send a Binding Acknowledgement with status set to 141 (Invalid Prefix).
它不能将流量转发到任何前缀。此外，它必须拒绝绑定更新并发送状态设置为141（无效前缀）的绑定确认。
If the Home Agent verifies the prefix information with the Prefix Table and the check fails, the Home Agent MUST discard the Binding Update and send a Binding Acknowledgement with status set to 142 (Not Authorized for Prefix).
如果归属代理使用前缀表验证前缀信息，并且检查失败，则归属代理必须放弃绑定更新并发送状态设置为142（未授权前缀）的绑定确认。
- If there is no option in the Binding Update carrying prefix information, the Home Agent uses manual pre-configured information to determine the prefixes assigned to the Mobile Router and to set up forwarding for the Mobile Network. If there is no information that the Home Agent can use, it MUST reject the Binding Update and send a Binding Acknowledgement with status set to 143 (Forwarding Setup failed).
- 如果绑定更新中没有包含前缀信息的选项，则归属代理使用手动预配置信息来确定分配给移动路由器的前缀，并为移动网络设置转发。如果没有归属代理可以使用的信息，它必须拒绝绑定更新并发送状态设置为143的绑定确认（转发设置失败）。
If the Home Agent has a valid binding cache entry for the Mobile Router, it should compare the list of prefixes in the Binding Update against the prefixes stored in the binding cache entry. If the binding cache entry contains prefixes that do not appear in the Binding Update, the Home Agent MUST disable forwarding for these Mobile Network Prefixes.
如果归属代理具有移动路由器的有效绑定缓存项，则应将绑定更新中的前缀列表与绑定缓存项中存储的前缀进行比较。如果绑定缓存项包含绑定更新中未出现的前缀，则归属代理必须禁用这些移动网络前缀的转发。
If all checks are passed, the Home Agent creates a binding cache entry for Mobile Router's Home Address or updates the entry if it already exists. Otherwise, the Home Agent MUST NOT register the binding of the Mobile Router's Home Address.
如果所有检查都通过，则归属代理将为移动路由器的归属地址创建一个绑定缓存条目，或者更新该条目（如果该条目已经存在）。否则，归属代理不得注册移动路由器的归属地址的绑定。
The Home Agent defends the Mobile Router's Home Address through Proxy Neighbor Discovery by multicasting a Neighbor Advertisement message onto the home link on behalf of the Mobile Router. All fields in the Proxy Neighbor Advertisement message should be set the same way they would be by the Mobile Router if it sent this Neighbor Advertisement while at home, as described in [6]. There is an exception: If the Mobile Router (R) Flag has been set in the Binding Update, the Router (R) bit in the Advertisement MUST be set.
归属代理通过代理邻居发现来保护移动路由器的归属地址，方法是代表移动路由器将邻居广告消息多播到归属链路上。在移动路由器中，它们将以相同的方式发送，而在邻居路由器中，它们将以相同的方式发送[6]。有一个例外：如果在绑定更新中设置了移动路由器（R）标志，则必须设置播发中的路由器（R）位。
The Home Agent also creates a bi-directional tunnel to the Mobile Router for the requested Mobile Network Prefix or updates an existing bi-directional tunnel as described in section 6.4.
归属代理还为请求的移动网络前缀创建到移动路由器的双向隧道，或更新第6.4节中描述的现有双向隧道。
To receive packets meant for the Mobile Network, the Home Agent advertises reachability to the Mobile Network. If the Home Link is configured with an aggregated prefix and the Mobile Network Prefix is aggregated under that prefix, then the routing changes related to the
为了接收针对移动网络的分组，归属代理播发对移动网络的可达性。如果家庭链路配置了聚合前缀，并且移动网络前缀聚合在该前缀下，则路由将更改为与该前缀相关的路由
Mobile Network may be restricted to the Home Link. If the Home Agent is the only default router on the Home Link, routes to the Mobile Network Prefix are aggregated naturally under the Home Agent, which does not have to do anything special.
移动网络可能仅限于家庭链路。如果归属代理是归属链路上唯一的默认路由器，那么到移动网络前缀的路由自然地聚合在归属代理下，而不必做任何特殊的事情。
If the Home Agent receives routing updates through a dynamic routing protocol from the Mobile Router, it can be configured to propagate those routes on the relevant interfaces.
如果归属代理通过动态路由协议从移动路由器接收路由更新，则可以将其配置为在相关接口上传播这些路由。
The implementation of the bi-directional tunnels and the mechanism for attaching them to the IP stack are outside the scope of this specification. However, all implementations MUST be capable of the following operations:
双向隧道的实现以及将其连接到IP堆栈的机制不在本规范的范围内。但是，所有实现必须能够执行以下操作：
- The Home Agent can tunnel packets meant for the Mobile Network prefix to the Mobile Router's current location, the Care-of Address.
- 归属代理可以将用于移动网络前缀的数据包隧道到移动路由器的当前位置，即转交地址。
- The Home Agent can accept packets tunneled by the Mobile Router with the source address of the outer IPv6 header set to the Mobile Router's Care-of Address.
- 归属代理可以接受移动路由器通过隧道传输的数据包，并将外部IPv6报头的源地址设置为移动路由器的转交地址。
When the Home Agent receives a data packet destined for the Mobile Network, it MUST forward the packet to the Mobile Router through the bi-directional tunnel. The Home Agent uses either the routing table, the Binding Cache, or a combination to route packets to the Mobile Network. This is implementation specific. Two examples are shown below.
当归属代理接收到目的地为移动网络的数据分组时，它必须通过双向隧道将该分组转发给移动路由器。归属代理使用路由表、绑定缓存或组合将数据包路由到移动网络。这是特定于实现的。下面是两个例子。
1. The Home Agent maintains a route to the Mobile Network Prefix with the next hop set to the Mobile Router's Home Address. When the Home Agent tries to forward the packet to the next hop, it finds a binding cache entry for the home address. Then the Home Agent extracts the Mobile Router's Care-of address and tunnels the packet to the Care-of address.
1. 归属代理维护到移动网络前缀的路由，并将下一跳设置为移动路由器的归属地址。当归属代理尝试将数据包转发到下一个跃点时，它会找到归属地址的绑定缓存项。然后，归属代理提取移动路由器的转交地址，并通过隧道将数据包传输到转交地址。
2. The Home Agent maintains a route to the Mobile Network Prefix with the outgoing interface set to the bi-directional tunnel interface between the Home Agent and the Mobile Router. For this purpose, the Home Agent MUST treat this tunnel as a tunnel interface. When the packets are forwarded through the tunnel interface, they are encapsulated automatically, with the source address and
2. 归属代理维护到移动网络前缀的路由，将传出接口设置为归属代理和移动路由器之间的双向隧道接口。为此，归属代理必须将此隧道视为隧道接口。当数据包通过隧道接口转发时，它们会自动封装，并带有源地址和地址
destination address in the outer IPv6 header set to the Home Agent's address and the Mobile Router's Care-of address, respectively.
外部IPv6报头中的目标地址分别设置为归属代理的地址和移动路由器的转交地址。
A Home Agent serving a Mobile Router sends Binding Acknowledgements with the same rules it uses for sending Binding Acknowledgements to Mobile Hosts [1], with the following enhancements.
为移动路由器提供服务的归属代理发送绑定确认时使用的规则与向移动主机发送绑定确认时使用的规则相同[1]，具有以下增强功能。
The Home Agent sets the status code in the Binding Acknowledgement to 0 (Binding Update accepted) to indicate to the Mobile Router that it successfully processed the Binding Update. It also sets the Mobile Router Flag (R) to indicate to the Mobile Router that it has set up forwarding for the Mobile Network.
归属代理将绑定确认中的状态代码设置为0（已接受绑定更新），以向移动路由器指示它已成功处理绑定更新。它还设置移动路由器标志（R），以向移动路由器指示它已为移动网络设置转发。
If the Home Agent is not configured to support Mobile Routers, it sets the status code in the Binding Acknowledgement to 140 (Mobile Router Operation not permitted).
如果归属代理未配置为支持移动路由器，则它将绑定确认中的状态代码设置为140（不允许移动路由器操作）。
If one or more prefixes received in the Binding Update are invalid and the Home Agent cannot set up forwarding for the prefixes, the Home Agent sets the status code in the Binding Acknowledgement to 141 (Invalid Prefix) to indicate this to the Mobile Router.
如果在绑定更新中接收到的一个或多个前缀无效，并且归属代理无法为前缀设置转发，则归属代理将绑定确认中的状态代码设置为141（无效前缀），以向移动路由器指示这一点。
If the Mobile Router is not authorized to use this Home Address to forward packets for one or more prefixes present in the Binding Update, the Home Agent sets the status code in the Binding Acknowledgement to 142 (Not Authorized for Prefix) to indicate this.
如果未授权移动路由器使用该归属地址转发绑定更新中存在的一个或多个前缀的分组，则归属代理将绑定确认中的状态代码设置为142（未授权前缀）以指示这一点。
The Home Agent sets the status code to 143 (Forwarding Setup failed) if it is unable to determine the information needed to set up forwarding for the Mobile Network. This is used in the Implicit mode, in which the Mobile Router does not include any prefix information in the Binding Update.
如果归属代理无法确定为移动网络设置转发所需的信息，则将状态代码设置为143（转发设置失败）。这在隐式模式下使用，在这种模式下，移动路由器在绑定更新中不包含任何前缀信息。
When the Home Agent successfully processes the de-registration BU, it deletes the Binding Cache Entry for the Mobile Router's Home Address and stops proxying the Home Address. This is described in detail in the Mobile IPv6 specification [1].
当归属代理成功处理注销BU时，它将删除移动路由器归属地址的绑定缓存条目，并停止代理归属地址。移动IPv6规范[1]对此进行了详细描述。
In addition, the Home Agent removes the bi-directional tunnel and stops forwarding packets to the Mobile Network. The Home Agent should keep all necessary information to clean up whichever routes it installed, whether they come from an implicit or explicit source.
此外，归属代理移除双向隧道并停止向移动网络转发数据包。归属代理应保留所有必要信息，以清理其安装的任何路由，无论它们来自隐式或显式源。
In Explicit mode, the Home Agent MUST ignore any Mobile Network Prefix Options present in the de-registration Binding Update.
在显式模式下，归属代理必须忽略取消注册绑定更新中存在的任何移动网络前缀选项。
This document extends the Dynamic Home Agent Address Discovery (DHAAD) defined in [1] so that Mobile Routers only attempt registration with Home Agents that support them.
本文档扩展了[1]中定义的动态归属代理地址发现（DHAAD），以便移动路由器仅尝试向支持它们的归属代理注册。
A new flag (R) (Support for Mobile Routers) is introduced in the DHAAD Request message, defined in [1]. The Mobile Router sets this flag to indicate that it wants to discover Home Agents supporting Mobile Routers.
[1]中定义的DHAAD请求消息中引入了一个新标志（R）（支持移动路由器）。移动路由器设置此标志表示它希望发现支持移动路由器的家庭代理。
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Code | Checksum |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Identifier |R| Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Code | Checksum |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Identifier |R| Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Mobile Router Support Flag (R)
移动路由器支持标志（R）
A one-bit flag that when set indicates that the Mobile Router wants to discover Home Agents supporting Mobile Routers.
设置时表示移动路由器希望发现支持移动路由器的家庭代理的一位标志。
For a description of the other fields in the message, see [1].
有关消息中其他字段的说明，请参见[1]。
A new flag (R) (Support for Mobile Routers) is introduced in the DHAAD Reply message, defined in [1]. If a Home Agent receives a Dynamic Home Agent Discovery request message with the Mobile Router Support Flag set, it MUST reply with a list of Home Agents supporting Mobile Routers. The Mobile Router Support Flag MUST be set if there is at least one Home Agent supporting Mobile Routers. If none of the Home Agents support Mobile Routers, the Home Agent MAY reply with a list of Home Agents that only support Mobile IPv6 Mobile Nodes. In this case, the Mobile Router Support Flag MUST be set to 0.
[1]中定义的DHAAD回复消息中引入了一个新标志（R）（支持移动路由器）。如果归属代理接收到设置了移动路由器支持标志的动态归属代理发现请求消息，则必须使用支持移动路由器的归属代理列表进行回复。如果至少有一个归属代理支持移动路由器，则必须设置移动路由器支持标志。如果没有一个归属代理支持移动路由器，则归属代理可以使用仅支持移动IPv6移动节点的归属代理列表进行回复。在这种情况下，移动路由器支持标志必须设置为0。
The modified message format is as follows.
修改后的消息格式如下所示。
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Code | Checksum |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Identifier |R| Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
+ +
+ +
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Code | Checksum |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Identifier |R| Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
+ +
+ +
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Mobile Router Support Flag (R)
移动路由器支持标志（R）
A one-bit flag that when set indicates that the Home Agents listed in this message support Mobile Routers.
设置时表示此消息中列出的归属代理支持移动路由器的一位标志。
For a description of the other fields in the message, see [1].
有关消息中其他字段的说明，请参见[1]。
A new flag (R) (Support for Mobile Routers) is introduced in the Home Agent Information Option defined in [1]. If a Home Agent supports Mobile Routers, it SHOULD set the flag.
[1]中定义的归属代理信息选项中引入了一个新标志（R）（支持移动路由器）。如果归属代理支持移动路由器，则应设置该标志。
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length |R| Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Home Agent Preference | Home Agent Lifetime |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length |R| Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Home Agent Preference | Home Agent Lifetime |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Mobile Router Support Flag (R)
移动路由器支持标志（R）
A one-bit flag that when set indicates that the Home Agent supports Mobile Routers.
一个一位标志，设置时表示归属代理支持移动路由器。
For a description of the other fields in the message, see [1].
有关消息中其他字段的说明，请参见[1]。
In the solution described so far, forwarding to the Mobile Network at the Home Agent is set up when the Home Agent receives a Binding Update from the Mobile Router. An alternative to this is for the Home Agent and the Mobile Router to run an intra-domain routing protocol such as RIPng [12] and OSPF [13] through the bi-directional tunnel. The Mobile Router can continue running the same routing protocol that it ran when attached to the home link.
在迄今为止描述的解决方案中，当归属代理从移动路由器接收到绑定更新时，在归属代理处建立到移动网络的转发。另一种选择是，归属代理和移动路由器通过双向隧道运行域内路由协议，如RIPng[12]和OSPF[13]。移动路由器可以继续运行连接到主链路时运行的相同路由协议。
Support for running a intra-domain routing protocol is optional and is governed by the configuration on the Mobile Router and the Home Agent.
对运行域内路由协议的支持是可选的，由移动路由器和归属代理上的配置控制。
This feature is very useful when the Mobile Network is large with multiple subnets containing different IPv6 prefixes. Routing changes in the Mobile Network are quickly propagated to the Home Agent. Routing changes in the home link are quickly propagated to the Mobile Router.
当移动网络较大且多个子网包含不同IPv6前缀时，此功能非常有用。移动网络中的路由更改会快速传播到归属代理。主链路中的路由更改会快速传播到移动路由器。
When the Mobile Router is attached to the home link, it runs a routing protocol by sending routing updates through its egress interface. When the Mobile Router moves and attaches to a visited network, it should stop sending routing updates on the interface by which it attaches to the visited link. This reduces the chances that prefixes specific to the Mobile Network will be leaked to the visited network if routing protocol authentication is not enabled in the visited network and in the Mobile Network. It is expected that normal deployment practices will include proper authentication mechanisms to prevent unauthorized route announcements on both the home and visited networks. The Mobile Router then starts sending routing protocol messages through the bi-directional tunnel toward the Home Agent. Most routing protocols use link-local addresses as source addresses for the routing information messages. The Mobile Router is allowed to use link-local addresses for the inner IPv6 header of an encapsulated packet. But these MUST NOT be forwarded to another link by either the Mobile Router or the Home Agent.
当移动路由器连接到家庭链路时，它通过其出口接口发送路由更新来运行路由协议。当移动路由器移动并连接到访问的网络时，它应该停止在连接到访问的链路的接口上发送路由更新。这降低了如果在访问的网络和移动网络中未启用路由协议认证，则特定于移动网络的前缀泄漏到访问的网络的可能性。预计正常的部署实践将包括适当的身份验证机制，以防止在家庭网络和到访网络上发布未经授权的路由公告。然后，移动路由器开始通过双向隧道向归属代理发送路由协议消息。大多数路由协议使用链路本地地址作为路由信息消息的源地址。允许移动路由器为封装数据包的内部IPv6报头使用链路本地地址。但是，移动路由器或归属代理都不能将这些数据转发到另一个链路。
When the Home Agent receives the inner packet, it processes the encapsulated routing protocol messages and updates its routing table accordingly. As part of normal routing protocol operation, the next hop information in these routing entries is filled with the Mobile Router's link-local address, with the outgoing interface set to the bi-directional tunnel.
当归属代理接收到内部分组时，它处理封装的路由协议消息并相应地更新其路由表。作为正常路由协议操作的一部分，这些路由条目中的下一跳信息由移动路由器的链路本地地址填充，输出接口设置为双向隧道。
Similarly, the Home Agent sends routing updates through the bi-directional tunnel to the Mobile Router. The Mobile Router processes these routing protocol messages and updates its routing table. For
类似地，归属代理通过双向隧道向移动路由器发送路由更新。移动路由器处理这些路由协议消息并更新其路由表。对于
all routes advertised by the Home Agent, the Mobile Router sets the outgoing interface to the bi-directional tunnel to the Home Agent.
在归属代理播发的所有路由中，移动路由器将传出接口设置为指向归属代理的双向隧道。
When the Mobile Router and the Home Agent exchange routes through a dynamic routing protocol, the Mobile Router SHOULD NOT include Mobile Network Prefixes in the Binding Update to the Home Agent. Depending on its configuration, the Home Agent might not add routes based on the prefix information in the Binding Updates and might use only the routing protocol updates. Moreover, including prefix information in both the Binding Updates and the routing protocol updates is redundant.
当移动路由器和归属代理通过动态路由协议交换路由时，移动路由器不应在对归属代理的绑定更新中包含移动网络前缀。根据其配置，归属代理可能不会根据绑定更新中的前缀信息添加路由，而可能仅使用路由协议更新。此外，在绑定更新和路由协议更新中包括前缀信息是冗余的。
As the routing protocol messages from the Home Agent to the Mobile Router could potentially contain information about the internal routing structure of the home network, these messages require authentication and confidentiality protection. Appropriate authentication and confidentiality protection mechanisms, defined in [14], MUST be used. For protecting routing protocol messages by using IPsec ESP [4], the bi-directional tunnel between the Mobile Router and the Home Agent should be treated as the outgoing interface, with the Home Agent and Mobile Router's addresses as source and destination addresses for the inner encapsulated messages.
由于从归属代理到移动路由器的路由协议消息可能包含有关归属网络的内部路由结构的信息，因此这些消息需要身份验证和保密保护。必须使用[14]中定义的适当身份验证和保密保护机制。为了使用IPsec ESP[4]保护路由协议消息，移动路由器和归属代理之间的双向隧道应视为传出接口，归属代理和移动路由器的地址应作为内部封装消息的源地址和目标地址。
If a link state routing protocol such as OSPFv3 is run by the Mobile Router and the Home Agent, the recommendations in Appendix B should be followed.
如果移动路由器和归属代理运行诸如OSPFv3之类的链路状态路由协议，则应遵循附录B中的建议。
All signaling messages between the Mobile Router and the Home Agent MUST be authenticated by IPsec [8]. The use of IPsec to protect Mobile IPv6 signaling messages is described in detail in the HA-MN IPsec specification [2]. The signaling messages described in this document extend Mobile IPv6 messages and do not require any changes to what is described in [2].
移动路由器和归属代理之间的所有信令消息必须通过IPsec验证[8]。HA-MN IPsec规范[2]详细描述了使用IPsec保护移动IPv6信令消息。本文档中描述的信令消息扩展了移动IPv6消息，不需要对[2]中描述的内容进行任何更改。
The Mobile Router has to perform ingress filtering on packets received from the Mobile Network to ensure that nodes in the Mobile Network do not use the bi-directional tunnel to launch IP spoofing attacks. In particular, the Mobile Router SHOULD check that the IP source addresses in the packets received belong to the Mobile Network Prefix and are not the same as one of the addresses used by the Mobile Router. If the Mobile Router receives an IP-in-IP tunneled packet from a node in the Mobile Network and it has to forward the decapsulated packet, it SHOULD perform the above mentioned checks on the source address of the inner packet.
移动路由器必须对从移动网络接收的数据包执行入口过滤，以确保移动网络中的节点不会使用双向隧道发起IP欺骗攻击。特别地，移动路由器应检查接收的分组中的IP源地址是否属于移动网络前缀，并且与移动路由器使用的地址之一不同。如果移动路由器从移动网络中的节点接收到IP-in-IP隧道数据包，并且它必须转发解除封装的数据包，那么它应该对内部数据包的源地址执行上述检查。
The Home Agent has to verify that packets received through the bi-directional tunnel belong to the Mobile Network. This check is necessary to prevent nodes from using the Home Agent to launch attacks that would have otherwise been prevented by ingress filtering. The source address of the outer IPv6 header MUST be set to the Mobile Router's current Care-of Address. The source address of the inner IPv6 header MUST be topologically correct with respect to the IPv6 prefixes used in the Mobile Network.
归属代理必须验证通过双向隧道接收的数据包是否属于移动网络。此检查对于防止节点使用Home Agent发起攻击是必要的，否则入侵过滤将阻止这些攻击。外部IPv6标头的源地址必须设置为移动路由器的当前转交地址。相对于移动网络中使用的IPv6前缀，内部IPv6标头的源地址必须在拓扑上正确。
If the Mobile Router sends a Binding Update with a one or more Mobile Network Prefix options, the Home Agent MUST be able to verify that the Mobile Router is authorized for the prefixes before setting up forwarding for the prefixes.
如果移动路由器发送带有一个或多个移动网络前缀选项的绑定更新，则在设置前缀转发之前，归属代理必须能够验证移动路由器已获得前缀的授权。
When the Mobile Router runs a dynamic routing protocol as described in section 8, it injects routing update messages into the Home Link. As the routing protocol message could contain information about the internal routing structure of the home network, these messages require confidentiality protection. The Mobile Router SHOULD use confidentiality protection through IPsec ESP as described in [14]. If the bi-directional tunnel between the Mobile Router and the Home Agent is protected by ESP, in tunnel mode for all IP traffic, then no additional confidentiality protection specific to the routing protocol is required.
当移动路由器运行第8节所述的动态路由协议时，它会将路由更新消息注入主链路。由于路由协议消息可能包含有关家庭网络内部路由结构的信息，因此这些消息需要保密保护。移动路由器应通过IPsec ESP使用保密保护，如[14]所述。如果移动路由器和归属代理之间的双向隧道由ESP以隧道模式为所有IP流量提供保护，则不需要特定于路由协议的额外保密保护。
Home Agents and Mobile Routers may use IPsec ESP to protect payload packets tunneled between themselves. This is useful to protect communications against attackers on the path of the tunnel.
家庭代理和移动路由器可以使用IPsec ESP来保护它们之间的有效负载数据包。这有助于保护通信免受隧道路径上的攻击者的攻击。
Please refer to the Mobile IPv6 specification [1] for security considerations when the Mobile Router operates as a Mobile Host.
请参考移动IPv6规范[1]，了解移动路由器作为移动主机运行时的安全注意事项。
This document defines a new Mobility Header Option, the Mobile Network Prefix Option as described in section 4.3. The type value for this option MUST be assigned from the same space used by the mobility options defined in [1].
本文件定义了一个新的移动报头选项，即第4.3节所述的移动网络前缀选项。此选项的类型值必须从[1]中定义的移动选项使用的相同空间分配。
This document also defines the following new Binding Acknowledgement status values. These status values are defined in section 4.2 and MUST be assigned from the same space used for Binding Acknowledgement status values in [1].
本文档还定义了以下新的绑定确认状态值。这些状态值在第4.2节中定义，必须从[1]中用于绑定确认状态值的相同空间分配。
- Mobile Router Operation not permitted - Invalid Prefix - Not Authorized for Prefix - Forwarding Setup failed (prefixes missing)
- 不允许移动路由器操作-前缀无效-未授权使用前缀-转发设置失败（缺少前缀）
We would like to acknowledge Ludovic Bellier, Claude Castelluccia, Thierry Ernst [15], Miguel Catalina-Gallego, Christophe Janneteau, T.J. Kniveton, Hong-Yon Lach, Jari T. Malinen, Koshiro Mitsuya, Alexis Olivereau, Charles E. Perkins, and Keisuke Uehara for their work on earlier proposals for Network Mobility. This document has inherited a lot of ideas from these proposals.
我们要感谢Ludovic Bellier、Claude Castelluccia、Thierry Ernst[15]、Miguel Catalina Gallego、Christophe Janneteau、T.J.Kniveton、Hong Yon Lach、Jari T.Malinen、Koshiro Mitsuya、Alexis Olivereau、Charles E.Perkins和Keisuke Uehara在早期网络移动性提案方面所做的工作。这份文件继承了这些建议的许多想法。
We thank all members of the NEMO Working Group, and of the preceding MONET BoF, for fruitful discussions on the mailing list and at IETF meetings.
我们感谢NEMO工作组和之前莫奈BoF的所有成员就邮件列表和IETF会议进行了富有成效的讨论。
Kent Leung, Marco Molteni, and Patrick Wetterwald are acknowledged for their work on Network Mobility for IPv4 and IPv6.
梁建东、马尔科·莫尔特尼和帕特里克·韦特瓦尔德因其在IPv4和IPv6网络移动性方面的工作而备受赞誉。
Tim Leinmueller is acknowledged for many insightful remarks and for section 7.
Tim Leinmueller因其许多有见地的评论和第7节而受到认可。
Jari Arkko, James Kempf, Chan-Wah Ng, and Erik Nordmark are acknowledged for their thorough review and comments.
Jari Arkko、James Kempf、Chan Wah Ng和Erik Nordmark对他们的全面审查和评论表示感谢。
Souhwan Jung, Fan Zhao, S. Felix Wu, HyunGon Kim, and SungWon Sohn are acknowledged for identifying threats related to tunneling between the Mobile Network and the Home Agent.
郑素焕、范昭、S.Felix Wu、金玄和孙成元因识别移动网络和Home Agent之间的隧道相关威胁而被公认。
[1] Johnson, D., Perkins, C., and J. Arkko, "Mobility Support in IPv6", RFC 3775, June 2004.
[1] Johnson，D.，Perkins，C.，和J.Arkko，“IPv6中的移动支持”，RFC 37752004年6月。
[2] Arkko, J., Devarapalli, V., and F. Dupont, "Using IPsec to Protect Mobile IPv6 Signaling between Mobile Nodes and Home Agents", RFC 3776, June 2004.
[2] Arkko，J.，Devarapalli，V.，和F.Dupont，“使用IPsec保护移动节点和家庭代理之间的移动IPv6信令”，RFC 37762004年6月。
[3] Conta, A. and S. Deering, "Generic Packet Tunneling in IPv6 Specification", RFC 2473, December 1998.
[3] Conta，A.和S.Deering，“IPv6规范中的通用数据包隧道”，RFC 2473，1998年12月。
[4] Kent, S. and R. Atkinson, "IP Encapsulating Security Payload (ESP)", RFC 2406, November 1998.
[4] Kent，S.和R.Atkinson，“IP封装安全有效载荷（ESP）”，RFC 2406，1998年11月。
[5] Deering, S. and R. Hinden, "Internet Protocol, Version 6 (IPv6) Specification", RFC 2460, December 1998.
[5] Deering，S.和R.Hinden，“互联网协议，第6版（IPv6）规范”，RFC 2460，1998年12月。
[6] Narten, T., Nordmark, E., and W. Simpson, "Neighbor Discovery for IP Version 6 (IPv6)", RFC 2461, December 1998.
[6] Narten，T.，Nordmark，E.，和W.Simpson，“IP版本6（IPv6）的邻居发现”，RFC24611998年12月。
[7] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
[7] Bradner，S.，“RFC中用于表示需求水平的关键词”，BCP 14，RFC 2119，1997年3月。
[8] Kent, S. and R. Atkinson, "Security Architecture for the Internet Protocol", RFC 2401, November 1998.
[8] Kent，S.和R.Atkinson，“互联网协议的安全架构”，RFC 2401，1998年11月。
[9] Manner, J. and M. Kojo, Eds., "Mobility Related Terminology", RFC 3753, June 2004.
[9] Way，J.和M.Kojo编辑，“机动性相关术语”，RFC 3753，2004年6月。
[10] Ernst, T., and H.-Y. Lach, "Network Mobility Support Terminology", Work in Progress, October 2004.
[10] Ernst，T.和H.-Y.Lach，“网络移动支持术语”，进展中的工作，2004年10月。
[11] Ernst, T., "Network Mobility Support Goals and Requirements", Work in Progress, October 2004.
[11] Ernst，T.，“网络移动性支持目标和要求”，进展中的工作，2004年10月。
[12] Malkin, G. and R. Minnear, "RIPng for IPv6", RFC 2080, January 1997.
[12] Malkin，G.和R.Minnear，“IPv6的RIPng”，RFC 2080，1997年1月。
[13] Coltun, R., Ferguson, D., and J. Moy, "OSPF for IPv6", RFC 2740, December 1999.
[13] Coltun，R.，Ferguson，D.，和J.Moy，“IPv6的OSPF”，RFC 27401999年12月。
[14] Gupta, M. and N. Melam, "Authentication/Confidentiality for OSPFv3", Work in Progress, December 2004.
[14] Gupta，M.和N.Melam，“OSPFv3的认证/保密”，正在进行的工作，2004年12月。
[15] Ernst, T., "Network Mobility Support in IPv6", PhD Thesis, University Joseph Fourier, Grenoble, France. October 2001.
[15] Ernst，T.，“IPv6中的网络移动性支持”，法国格勒诺布尔约瑟夫·傅立叶大学博士论文。2001年10月。
[16] Moy, J., "Extending OSPF to Support Demand Circuits", RFC 1793, April 1995.
[16] Moy，J.，“扩展OSPF以支持需求电路”，RFC 1793，1995年4月。
[17] Thubert, P., et al., "NEMO Home Network models", Work in Progress, October 2004.
[17] Thubert，P.等人，“NEMO家庭网络模型”，正在进行的工作，2004年10月。
This section tries to illustrate the NEMO protocol by using a Mobile Router and a Mobile Node belonging to different administrative domains. The Mobile Router's Mobile Network consists of a Local Fixed Node (LFN) and a Local Fixed Router (LFR) [10]. The LFR has an access link to which other Mobile Nodes or Mobile Routers could attach.
本节试图通过使用属于不同管理域的移动路由器和移动节点来说明NEMO协议。移动路由器的移动网络由本地固定节点（LFN）和本地固定路由器（LFR）[10]组成。LFR有一个接入链路，其他移动节点或移动路由器可以连接到该链路。
Figure 1 depicts the scenario where both the Mobile Router and the Mobile Node are at home.
图1描述了移动路由器和移动节点都在家中的场景。
+----+ +-------+
| MN | | HA_MN |
+--+-+ 1:: +---+---+
2+-------------+3
|
|
+-------+2 2:: +-------------------+ 3:: 2+-------+
| CN_MN |------| Internet |------| CN_MR |
+-------+ +-------------------+ +-------+
4:: |
|
2+-------------+3
+--+-+ +---+---+
| MR | | HA_MR |
+--+-+ +-------+
5:: |1
----------
2| |3
+--+-+ +--+-+
| LFN| | LFR|
+--+-+ +--+-+
6:: |1
----------
+----+ +-------+
| MN | | HA_MN |
+--+-+ 1:: +---+---+
2+-------------+3
|
|
+-------+2 2:: +-------------------+ 3:: 2+-------+
| CN_MN |------| Internet |------| CN_MR |
+-------+ +-------------------+ +-------+
4:: |
|
2+-------------+3
+--+-+ +---+---+
| MR | | HA_MR |
+--+-+ +-------+
5:: |1
----------
2| |3
+--+-+ +--+-+
| LFN| | LFR|
+--+-+ +--+-+
6:: |1
----------
Figure 1. Mobile Router and Mobile Node at home.
图1。家庭中的移动路由器和移动节点。
The Mobile Router then moves away from the home link and attaches to a visited link. This is shown in Figure 2. The Mobile Router sends a Binding Update to HA_MR when it attaches to a visited link and configures a Care-of Address. HA_MR creates a binding cache entry for the Mobile Router's Home Address and also sets up forwarding for the prefixes on the Mobile Network.
然后，移动路由器离开主链路并连接到访问的链路。这如图2所示。当移动路由器连接到访问的链路并配置转交地址时，它向HA_MR发送绑定更新。HA_MR为移动路由器的家庭地址创建绑定缓存条目，并为移动网络上的前缀设置转发。
+----+ +-------+
| MN | | HA_MN |
+--+-+ 1:: +---+---+
2+-------------+3
|
|
+-------+2 2:: +-------------------+ 3:: 2+-------+
| CN_MN |------| Internet |------| CN_MR |
+-------+ ++------------------+ +-------+
| 7:: 4:: | 4::2->7::2
| |
2+ +3
+--+-+ +---+---+
| MR | | HA_MR | 4::2->7::2
+--+-+ +-------+ 5::/prefixlen -> forward
5:: |1 to MR
---------- 6::/prefixlen -> forward
2| |3 to MR
+--+-+ +--+-+
| LFN| | LFR|
+--+-+ +--+-+
6:: |1
----------
+----+ +-------+
| MN | | HA_MN |
+--+-+ 1:: +---+---+
2+-------------+3
|
|
+-------+2 2:: +-------------------+ 3:: 2+-------+
| CN_MN |------| Internet |------| CN_MR |
+-------+ ++------------------+ +-------+
| 7:: 4:: | 4::2->7::2
| |
2+ +3
+--+-+ +---+---+
| MR | | HA_MR | 4::2->7::2
+--+-+ +-------+ 5::/prefixlen -> forward
5:: |1 to MR
---------- 6::/prefixlen -> forward
2| |3 to MR
+--+-+ +--+-+
| LFN| | LFR|
+--+-+ +--+-+
6:: |1
----------
Figure 2. Mobile Router on a visited link.
图2。访问链路上的移动路由器。
Figure 3 shows the Mobile Node moving away from its home link and attaching to the Mobile Router. The Mobile Node configures a Care-of Address from the prefix advertised on the Mobile Network and sends a Binding Update to its Home Agent (HA_MN) and to its Correspondent Node (CN_MN). Both HA_MN and CN_MN create binding cache entries for the Mobile Node's Home Address.
图3显示移动节点离开其主链路并连接到移动路由器。移动节点根据移动网络上公布的前缀配置转交地址，并向其归属代理（HA_MN）和对应节点（CN_MN）发送绑定更新。HA_MN和CN_MN都为移动节点的主地址创建绑定缓存项。
+-------+
| HA_MN | 1::2->6::2
1:: +---+---+
---------|3
|
|
+-------+2 2:: +-------------------+ 3:: 2+-------+
| CN_MN |------| Internet |------| CN_MR |
+-------+ ++------------------+ +-------+
1::2->6::2 | 7:: 4:: | 4::2->7::2
| |
2+ +3
+--+-+ +---+---+
| MR | | HA_MR | 4::2->7::2
+--+-+ +-------+ 5::/prefixlen -> forward
5:: |1 to MR
---------- 6::/prefixlen -> forward
2| |3 to MR
+--+-+ +--+-+
| LFN| | LFR|
+--+-+ +--+-+
6:: |1
--------+-
|2
+--+-+
| MN |
+----+
+-------+
| HA_MN | 1::2->6::2
1:: +---+---+
---------|3
|
|
+-------+2 2:: +-------------------+ 3:: 2+-------+
| CN_MN |------| Internet |------| CN_MR |
+-------+ ++------------------+ +-------+
1::2->6::2 | 7:: 4:: | 4::2->7::2
| |
2+ +3
+--+-+ +---+---+
| MR | | HA_MR | 4::2->7::2
+--+-+ +-------+ 5::/prefixlen -> forward
5:: |1 to MR
---------- 6::/prefixlen -> forward
2| |3 to MR
+--+-+ +--+-+
| LFN| | LFR|
+--+-+ +--+-+
6:: |1
--------+-
|2
+--+-+
| MN |
+----+
Figure 3. Mobile Node attached to Mobile Router on a visited link
图3。在访问的链路上连接到移动路由器的移动节点
The bi-directional tunnel between the Mobile Router and the Home Agent is used as a virtual interface over which routing protocol messages are exchanged. When a link state routing protocol is run, the following recommendations should be followed.
移动路由器和归属代理之间的双向隧道用作交换路由协议消息的虚拟接口。运行链路状态路由协议时，应遵循以下建议。
If the tunnel interface goes up and down every time the Mobile Router moves to a new visited network with a high level of mobility and a sufficient number of Mobile Routers, the amount of interface state changes will adversely affect the Home Agent's performance. This also introduces a high level of instability in the home network. To avoid this, the following should be considered when the bi-directional tunnel is implemented:
如果每次移动路由器移动到具有高移动性和足够数量的移动路由器的新访问网络时，隧道接口上下波动，那么接口状态的变化量将对归属代理的性能产生不利影响。这也给家庭网络带来了高度的不稳定性。为避免这种情况，在实施双向隧道时，应考虑以下事项：
- A tunnel interface is consistently assigned to each Mobile Router, as long as it has a valid binding cache at the Home Agent.
- 隧道接口始终分配给每个移动路由器，只要它在归属代理中具有有效的绑定缓存。
- Every time the Mobile Router moves and updates the binding cache entry, the bi-directional tunnel should not be torn down and set up again. The tunnel end points should be updated dynamically with the Mobile Router's current Care-of Address.
- 每次移动路由器移动并更新绑定缓存条目时，不应拆除并重新设置双向隧道。隧道端点应使用移动路由器的当前转交地址动态更新。
- With a large number of interfaces, Hello packet processing may become a burden. Therefore, the tunnel interface should be treated as On-Demand circuits for OSPF [16].
- 有了大量的接口，Hello数据包处理可能会成为一个负担。因此，隧道接口应视为OSPF的按需电路[16]。
The following should be considered when the Home Network is configured for running OSPF:
当家庭网络配置为运行OSPF时，应考虑以下事项：
- The entire Home domain SHOULD NOT be configured as a single area if a Home Agent supports Mobile Routers. At least the home network should be configured as a separate area.
- 如果归属代理支持移动路由器，则不应将整个归属域配置为单个区域。至少家庭网络应配置为单独的区域。
- The bi-directional tunnel interfaces to the Mobile Routers should never be included in the same area as the backbone links.
- 移动路由器的双向隧道接口不应与主干链路包含在同一区域内。
For a more detailed discussion on configuring a home network for NEMO Basic Support, please see [17].
有关为NEMO基本支持配置家庭网络的更详细讨论，请参阅[17]。
One disadvantage of running OSPFv3 with NEMO Basic Support is the possibility that the Mobile Networks will be told of the topology of the entire home network, including all the fixed and Mobile Routers. The only thing the Mobile Routers might really need is a default route through the Home Agent.
在NEMO基本支持下运行OSPFv3的一个缺点是，移动网络可能会被告知整个家庭网络的拓扑结构，包括所有固定和移动路由器。移动路由器可能真正需要的唯一东西是通过Home Agent的默认路由。
To reduce the amount of routing protocol messages received by a Mobile Router, one can configure each bi-directional tunnel to a Mobile Router as a separate area. But this requires that the Home Agent support a large number of OSPF areas if it supports a large number of Mobile Routers, and it might not be possible with most router implementations.
为了减少移动路由器接收的路由协议消息的数量，可以将移动路由器的每个双向隧道配置为一个单独的区域。但是，如果Home Agent支持大量移动路由器，则需要它支持大量OSPF区域，而这在大多数路由器实现中可能是不可能的。
Another option is to configure multiple areas on the Home Link and group a number of Mobile Routers into each area. This reduces the number of areas that a Home Agent needs to support but also reduces the amount of routing protocol traffic that a Mobile Router receives.
另一个选项是在主链路上配置多个区域，并将多个移动路由器分组到每个区域中。这减少了归属代理需要支持的区域数量，但也减少了移动路由器接收的路由协议流量。
Authors' Addresses
作者地址
Vijay Devarapalli Nokia Research Center 313 Fairchild Drive Mountain View, CA 94043 USA
Vijay Devarapalli诺基亚研究中心313 Fairchild Drive Mountain View，加利福尼亚州94043
EMail: vijay.devarapalli@nokia.com
EMail: vijay.devarapalli@nokia.com
Ryuji Wakikawa Keio University and WIDE 5322 Endo Fujisawa Kanagawa 252-8520 Japan
日本庆应庆应大学和广域5322藤泽神奈川252-8520
EMail: ryuji@sfc.wide.ad.jp
EMail: ryuji@sfc.wide.ad.jp
Alexandru Petrescu Motorola Labs Parc les Algorithmes Saint Aubin Gif-sur-Yvette 91193 France
Alexandru Petrescu Motorola Labs Parc les Algorithmes Saint Aubin Gif sur Yvette 91193法国
EMail: Alexandru.Petrescu@motorola.com
EMail: Alexandru.Petrescu@motorola.com
Pascal Thubert Cisco Systems Technology Center Village d'Entreprises Green Side 400, Avenue Roumanille Biot - Sophia Antipolis 06410 France
帕斯卡·苏伯特·思科系统技术中心法国索菲亚·安提波利斯市鲁马尼尔大道400号绿边企业村（邮编：06410）
EMail: pthubert@cisco.com
EMail: pthubert@cisco.com
Full Copyright Statement
完整版权声明
Copyright (C) The Internet Society (2005).
版权所有（C）互联网协会（2005年）。
This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights.
本文件受BCP 78中包含的权利、许可和限制的约束，除其中规定外，作者保留其所有权利。
This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
本文件及其包含的信息是按“原样”提供的，贡献者、他/她所代表或赞助的组织（如有）、互联网协会和互联网工程任务组不承担任何明示或暗示的担保，包括但不限于任何保证，即使用本文中的信息不会侵犯任何权利，或对适销性或特定用途适用性的任何默示保证。
Intellectual Property
知识产权
The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. Information on the IETF's procedures with respect to rights in IETF Documents can be found in BCP 78 and BCP 79.
IETF对可能声称与本文件所述技术的实施或使用有关的任何知识产权或其他权利的有效性或范围，或此类权利下的任何许可可能或可能不可用的程度，不采取任何立场；它也不表示它已作出任何独立努力来确定任何此类权利。有关IETF文件中权利的IETF程序信息，请参见BCP 78和BCP 79。
Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr.
向IETF秘书处披露的知识产权副本和任何许可证保证，或本规范实施者或用户试图获得使用此类专有权利的一般许可证或许可的结果，可从IETF在线知识产权存储库获取，网址为http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf-ipr@ietf.org.
IETF邀请任何相关方提请其注意任何版权、专利或专利申请，或其他可能涵盖实施本标准所需技术的专有权利。请将信息发送至IETF的IETF-ipr@ietf.org.
Acknowledgement
确认
Funding for the RFC Editor function is currently provided by the Internet Society.
RFC编辑功能的资金目前由互联网协会提供。