Network Working Group K. Leung
Request for Comments: 4332 A. Patel
Category: Informational Cisco Systems
G. Tsirtsis
Flarion Technologies
E. Klovning
Birdstep Technology ASA
December 2005
Network Working Group K. Leung
Request for Comments: 4332 A. Patel
Category: Informational Cisco Systems
G. Tsirtsis
Flarion Technologies
E. Klovning
Birdstep Technology ASA
December 2005
Cisco's Mobile IPv4 Host Configuration Extensions
Cisco的移动IPv4主机配置扩展
Status of This Memo
关于下段备忘
This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited.
本备忘录为互联网社区提供信息。它没有规定任何类型的互联网标准。本备忘录的分发不受限制。
Copyright Notice
版权公告
Copyright (C) The Internet Society (2005).
版权所有（C）互联网协会（2005年）。
IESG Note
IESG注释
This RFC is not a candidate for any level of Internet Standard. The IETF disclaims any knowledge of the fitness of this RFC for any purpose and in particular notes that the decision to publish is not based on IETF review for such things as security, congestion control, or inappropriate interaction with deployed protocols. The RFC Editor has chosen to publish this document at its discretion. Readers of this document should exercise caution in evaluating its value for implementation and deployment. See RFC 3932 for more information.
本RFC不适用于任何级别的互联网标准。IETF不承认本RFC适用于任何目的的任何知识，特别注意到，发布决定并非基于IETF对安全、拥塞控制或与已部署协议的不当交互等事项的审查。RFC编辑已自行决定发布本文件。本文档的读者在评估其实施和部署价值时应谨慎。有关更多信息，请参阅RFC 3932。
This RFC does not offer any security mechanisms to provide data origin authentication and integrity, yet these security services are vitally important in this context.
此RFC不提供任何安全机制来提供数据源身份验证和完整性，但这些安全服务在这种情况下至关重要。
Abstract
摘要
An IP device requires basic host configuration to be able to communicate. For example, it will typically require an IP address and the address of a DNS server. This information is configured statically or obtained dynamically using Dynamic Host Configuration Protocol (DHCP) or Point-to-Point Protocol/IP Control Protocol (PPP/IPCP). However, both DHCP and PPP/IPCP provide host configuration based on the access network. In Mobile IPv4, the registration process boots up a Mobile Node at an access network, also known as a foreign network. The information to configure the
IP设备需要基本的主机配置才能进行通信。例如，它通常需要IP地址和DNS服务器的地址。此信息是静态配置的，或使用动态主机配置协议（DHCP）或点对点协议/IP控制协议（PPP/IPCP）动态获取的。但是，DHCP和PPP/IPCP都提供基于接入网络的主机配置。在移动IPv4中，注册过程在接入网络（也称为外部网络）上启动移动节点。要配置的信息
host needs to be based on the home network. This document describes the Cisco vendor-specific extensions to Mobile IPv4 to provide the base host configuration in Registration Request and Reply messages.
主机需要基于家庭网络。本文档描述了Cisco供应商对移动IPv4的特定扩展，以在注册请求和回复消息中提供基本主机配置。
Table of Contents
目录
1. Introduction ....................................................2
2. Host Configuration Extensions Summary ...........................3
3. Host Configuration Extensions ...................................4
3.1. Host Configuration Request Extension .......................5
3.2. Home Network Length Prefix Extension .......................5
3.3. DNS Server Extension .......................................6
3.4. DHCP Server Extension ......................................6
3.5. DHCP Client ID Extension ...................................7
3.6. Default Gateway Extension ..................................7
3.7. DNS Suffix Extension .......................................8
3.8. Configuration URL Extension ................................8
4. Security Considerations .........................................9
5. Acknowledgements ................................................9
6. Informative References ..........................................9
1. Introduction ....................................................2
2. Host Configuration Extensions Summary ...........................3
3. Host Configuration Extensions ...................................4
3.1. Host Configuration Request Extension .......................5
3.2. Home Network Length Prefix Extension .......................5
3.3. DNS Server Extension .......................................6
3.4. DHCP Server Extension ......................................6
3.5. DHCP Client ID Extension ...................................7
3.6. Default Gateway Extension ..................................7
3.7. DNS Suffix Extension .......................................8
3.8. Configuration URL Extension ................................8
4. Security Considerations .........................................9
5. Acknowledgements ................................................9
6. Informative References ..........................................9
An IPv4 device requires some basic configuration to communicate with other nodes. Typically, it has an IP address for an interface and DNS server's IP address to resolve the peer's hostname to an IP address. DHCP [RFC2131] and PPP/IPCP [RFC1332] provide host configuration information on the access network interface, but this is inadequate in a Mobile IPv4 environment. In Mobile IPv4 [RFC3344], a Mobile Node has a virtual network interface on the home network, anchored by the Home Agent. The IP address, home subnet prefix, default gateway, and home network's DNS servers are essential in the boot up of a network interface. In some cases, these are the only pieces of information needed by the Mobile Node.
IPv4设备需要一些基本配置才能与其他节点通信。通常，它具有接口的IP地址和DNS服务器的IP地址，以将对等主机名解析为IP地址。DHCP[RFC2131]和PPP/IPCP[RFC1332]在接入网络接口上提供主机配置信息，但这在移动IPv4环境中是不够的。在移动IPv4[RFC3344]中，移动节点在家庭网络上有一个虚拟网络接口，由家庭代理锚定。IP地址、家庭子网前缀、默认网关和家庭网络的DNS服务器在网络接口的启动中至关重要。在某些情况下，移动节点只需要这些信息。
The Mobile IPv4 registration process provides the mechanism for a Mobile Node to boot up on a foreign network. Upon the successful registration, the Mobile Node can communicate with the Correspondent Node. The need to provide an efficient method to obtain the host configuration exists. If the Mobile Node is a DHCP client, it can obtain configuration parameters from the DHCP server in the home network after the initial registration.
移动IPv4注册过程为移动节点在外部网络上启动提供了机制。成功注册后，移动节点可以与对应节点通信。需要提供一种有效的方法来获取主机配置。如果移动节点是DHCP客户端，则可以在初始注册后从家庭网络中的DHCP服务器获取配置参数。
This document introduces the Cisco vendor-specific extensions (VSEs) [RFC3115] to provide the means for a Mobile Node to download some fundamental configuration associated with the home network via the
本文档介绍Cisco供应商特定扩展（VSE）[RFC3115]，为移动节点提供通过网络下载与家庭网络相关的一些基本配置的方法
Home Agent. These extensions provide information for home subnet prefix, DNS server, DHCP server, DHCP client identifier, default gateway, DNS suffix, and configuration URL.
国内代理。这些扩展提供有关主子网前缀、DNS服务器、DHCP服务器、DHCP客户端标识符、默认网关、DNS后缀和配置URL的信息。
The following Cisco vendor-specific extensions provide the host configuration for a Mobile Node. The "Host Configuration Request" extension is allowed only in the Registration Request. The rest of the extensions are appended in the Registration Reply.
以下Cisco供应商特定扩展提供了移动节点的主机配置。“主机配置请求”扩展仅允许在注册请求中使用。其余扩展将附加在注册回复中。
o Host Configuration Request
o 主机配置请求
* Request for host configuration information from the Mobile Node to the Home Agent.
* 从移动节点向归属代理请求主机配置信息。
o Home Network Prefix Length
o 家庭网络前缀长度
* The length of the subnet prefix on the home network.
* 家庭网络上子网前缀的长度。
o Default Gateway
o 默认网关
* The default gateway's IP address on the home network.
* 家庭网络上默认网关的IP地址。
o DNS Server
o DNS服务器
* The DNS server's IP address in the home network.
* DNS服务器在家庭网络中的IP地址。
o DNS Suffix
o DNS后缀
* The DNS suffix for hostname resolution in the home network.
* 家庭网络中主机名解析的DNS后缀。
o DHCP Client ID
o DHCP客户端ID
* The DHCP Client ID used to obtain the IP address. When the Mobile Node returns home and is responsible for managing its own address, this information maps to the client identifier option as defined in section 9.14 of [RFC2132] and referenced in [RFC2131].
* 用于获取IP地址的DHCP客户端ID。当移动节点返回家乡并负责管理自己的地址时，该信息映射到[RFC2132]第9.14节中定义并在[RFC2131]中引用的客户端标识符选项。
o DHCP Server
o DHCP服务器
* The DHCP server's IP address in the home network.
* 家庭网络中DHCP服务器的IP地址。
o Configuration URL
o 配置URL
* The URL for the Mobile Node to download configuration parameters from a server.
* 移动节点从服务器下载配置参数的URL。
When the Mobile Node needs to obtain its host configuration, the Host Configuration Request VSE is appended to the Registration Request. This VSE indicates to the Home Agent that either all or selected host configuration VSEs need to be appended to the Registration Reply. If the Home Agent retrieved the information from a DHCP server (in Proxy DHCP mode), then the DHCP Client ID and DHCP Server extensions are appended in the Registration Reply. These DHCP-related extensions are populated with values that had been used in the DHCP messages exchanged between the Home Agent and the DHCP server.
当移动节点需要获得其主机配置时，主机配置请求VSE被附加到注册请求。此VSE向归属代理指出，所有或选定的主机配置VSE都需要附加到注册回复中。如果归属代理从DHCP服务器（在代理DHCP模式下）检索到信息，则DHCP客户端ID和DHCP服务器扩展将附加在注册回复中。这些与DHCP相关的扩展由在归属代理和DHCP服务器之间交换的DHCP消息中使用的值填充。
The VSEs are authenticated as part of the registration message using any of the authentication mechanism defined for Mobile IP ([RFC3344], [RFC3012]).
使用为移动IP定义的任何身份验证机制（[RFC3344]、[RFC3012]），将VSE作为注册消息的一部分进行身份验证。
This message MAY contain extensions defined in Mobile IP, including vendor-specific extensions [RFC3115].
此消息可能包含移动IP中定义的扩展，包括特定于供应商的扩展[RFC3115]。
Cisco's host configuration extensions to Mobile IPv4 are based on the vendor-specific extensions defined in [RFC3115]. The format of the VSE TLV (Type-Length-Value) is as follows:
Cisco对移动IPv4的主机配置扩展基于[RFC3115]中定义的特定于供应商的扩展。VSE TLV（类型长度值）的格式如下：
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Vendor/Org-ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Vendor-NVSE-Type | Vendor-NVSE-Value ...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Vendor/Org-ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Vendor-NVSE-Type | Vendor-NVSE-Value ...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: 134
类型：134
Length:
长度：
Indicates the length (in bytes) of the data field within this extension, excluding the Type and Length fields.
指示此扩展中数据字段的长度（字节），不包括类型和长度字段。
Reserved:
保留：
Reserved for future use. To be set to 0 while sending, ignored on reception.
保留供将来使用。发送时设置为0，接收时忽略。
Vendor/Org-ID:
供应商/组织ID：
9 (Cisco Systems)
9（思科系统）
Vendor-NVSE-Type:
供应商NVSE类型：
14 (Host Configuration)
14（主机配置）
Vendor-NVSE-Value:
供应商NVSE值：
Format is shown below for each subtype. The Sub-Type field is an integer from 0 to 255.
每个子类型的格式如下所示。子类型字段是0到255之间的整数。
This format of the Host Configuration Request extension is shown below.
主机配置请求扩展的这种格式如下所示。
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-Type | Selector |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sub-Type | Selector |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Sub-Type:
子类型：
0
0
Selector:
选择器：
0 indicates all host configuration available to the Home Agent (HA) is requested by the Mobile Node.
0表示移动节点请求归属代理（HA）可用的所有主机配置。
This format of the Home Network Prefix Length extension is shown below.
家庭网络前缀长度扩展的这种格式如下所示。
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-Type | Prefix Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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-Type | Prefix Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Sub-Type:
子类型：
1
1.
Prefix Length:
前缀长度：
The number of bits in the home subnet prefix.
主子网前缀中的位数。
This format of the DNS Server extension is shown below.
DNS服务器扩展的这种格式如下所示。
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-Type | Primary DNS Server
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
. . . | Secondary DNS Server
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
. . . |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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-Type | Primary DNS Server
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
. . . | Secondary DNS Server
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
. . . |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Sub-Type:
子类型：
2
2.
Primary DNS Server:
主DNS服务器：
The IP address of the primary DNS server.
主DNS服务器的IP地址。
Secondary DNS Server:
辅助DNS服务器：
The IP address of the secondary DNS server.
辅助DNS服务器的IP地址。
This format of the DHCP Server extension is shown below.
DHCP服务器扩展的这种格式如下所示。
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-Type | DHCP Server
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
. . . |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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-Type | DHCP Server
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
. . . |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Sub-Type:
子类型：
3
3.
DHCP Server:
DHCP服务器：
The IP address of the DHCP server.
DHCP服务器的IP地址。
This format of the DHCP Client ID extension is shown below.
DHCP客户端ID扩展的这种格式如下所示。
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-Type | Client ID . . .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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-Type | Client ID . . .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Sub-Type:
子类型：
4
4.
Client ID:
客户端ID:
DHCP servers use this value to index their database of address bindings. This value is expected to be unique for all clients in an administrative domain. The size of field is between 2 and 255 octets.
DHCP服务器使用此值为其地址绑定数据库编制索引。此值对于管理域中的所有客户端都是唯一的。字段大小在2到255个八位字节之间。
This format of the Default Gateway extension is shown below.
默认网关扩展的这种格式如下所示。
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-Type | Default Gateway
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
. . . |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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-Type | Default Gateway
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
. . . |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Sub-Type:
子类型：
5
5.
Default Gateway:
默认网关：
The IP address of the default gateway for the Mobile Node on the home network.
家庭网络上移动节点的默认网关的IP地址。
This format of the DNS Suffix extension is shown below.
DNS后缀扩展的这种格式如下所示。
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-Type | DNS Suffix . . .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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-Type | DNS Suffix . . .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Sub-Type:
子类型：
6
6.
DNS Suffix:
DNS后缀：
The DNS suffix to be appended to the name of Mobile Node when completing its fully qualified domain name (FQDN). The size of field is between 1 and 246 octets.
完成其完全限定域名（FQDN）时要附加到移动节点名称的DNS后缀。字段大小介于1到246个八位字节之间。
This format of the Configuration URL extension is shown below.
配置URL扩展的这种格式如下所示。
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-Type | URL String . . .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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-Type | URL String . . .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Sub-Type:
子类型：
7
7.
URL String:
URL字符串：
The Mobile Node can retrieve configuration parameters via the URL. The URL is at most 246 bytes in length.
移动节点可以通过URL检索配置参数。URL的长度最多为246字节。
The host configuration extensions follow the same rules for Mobile IP extensions in registration messages. See the Security Considerations section in RFC 3344.
主机配置扩展遵循注册消息中移动IP扩展的相同规则。请参阅RFC 3344中的安全注意事项部分。
The Configuration URL extension may trigger the Mobile Node to download the configuration parameters from a server. The protection of the data transfer is outside the scope of this document. Possible options include encryption of data before transfer or using HTTPS.
配置URL扩展可触发移动节点从服务器下载配置参数。数据传输的保护不在本文件的范围内。可能的选项包括传输前的数据加密或使用HTTPS。
The authors would like to acknowledge Jayshree Bharatia, Kuntal Chowdhury, Avi Lior, and Lila Madour for their contributions to the work in progress titled "Mobile IPv4 Extension for Configuration Options Exchange".
作者要感谢Jayshree Bharatia、Kuntal Chowdhury、Avi Lior和Lila Madour对正在进行的题为“配置选项交换的移动IPv4扩展”的工作所做的贡献。
[RFC1332] McGregor, G., "The PPP Internet Protocol Control Protocol (IPCP)", RFC 1332, May 1992.
[RFC1332]McGregor，G.“PPP互联网协议控制协议（IPCP）”，RFC1332，1992年5月。
[RFC2131] Droms, R., "Dynamic Host Configuration Protocol", RFC 2131, March 1997.
[RFC2131]Droms，R.，“动态主机配置协议”，RFC21311997年3月。
[RFC2132] Alexander, S. and R. Droms, "DHCP Options and BOOTP Vendor Extensions", RFC 2132, March 1997.
[RFC2132]Alexander，S.和R.Droms，“DHCP选项和BOOTP供应商扩展”，RFC 21321997年3月。
[RFC3012] Perkins, C. and P. Calhoun, "Mobile IPv4 Challenge/ Response Extensions", RFC 3012, November 2000.
[RFC3012]Perkins，C.和P.Calhoun，“移动IPv4挑战/响应扩展”，RFC3012，2000年11月。
[RFC3115] Dommety, G. and K. Leung, "Mobile IP Vendor/ Organization-Specific Extensions", RFC 3115, April 2001.
[RFC3115]Dommety，G.和K.Leung，“移动IP供应商/组织特定扩展”，RFC 3115，2001年4月。
[RFC3344] Perkins, C., "IP Mobility Support for IPv4", RFC 3344, August 2002.
[RFC3344]Perkins，C.，“IPv4的IP移动支持”，RFC 3344，2002年8月。
Authors' Addresses
作者地址
Kent Leung Cisco Systems 170 W. Tasman Drive San Jose, CA 95134 US
美国加利福尼亚州圣何塞塔斯曼大道西170号肯特梁思科系统公司，邮编95134
Phone: +1 408-526-5030
EMail: kleung@cisco.com
Phone: +1 408-526-5030
EMail: kleung@cisco.com
Alpesh Patel Cisco Systems 170 W. Tasman Drive San Jose, CA 95134 US
美国加利福尼亚州圣何塞塔斯曼大道西170号阿尔佩什帕特尔思科系统公司，邮编95134
Phone: +1 408-853-9580
EMail: alpesh@cisco.com
Phone: +1 408-853-9580
EMail: alpesh@cisco.com
George Tsirtsis Flarion Technologies Bedminster One 135 Route 202/206 South Bedminster, NJ 07921 US
George Tsirtsis Flarion Technologies Bedminster One 135号公路202/206南贝德明斯特，美国新泽西州07921
Phone: +1 908-947-7059
EMail: g.tsirtsis@flarion.com
Phone: +1 908-947-7059
EMail: g.tsirtsis@flarion.com
Espen Klovning Birdstep Technology ASA Bryggegata 7 Oslo, 0250 Norway
Espen Kloving Birdstep Technology ASA Bryggegata 7奥斯陆，邮编：0250挪威
Phone: +47 95 20 26 29
EMail: espen@birdstep.com
Phone: +47 95 20 26 29
EMail: espen@birdstep.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 at www.rfc-editor.org/copyright.html, and except as set forth therein, the authors retain all their rights.
本文件受BCP 78和www.rfc-editor.org/copyright.html中包含的权利、许可和限制的约束，除其中规定外，作者保留其所有权利。
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 procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79.
IETF对可能声称与本文件所述技术的实施或使用有关的任何知识产权或其他权利的有效性或范围，或此类权利下的任何许可可能或可能不可用的程度，不采取任何立场；它也不表示它已作出任何独立努力来确定任何此类权利。有关RFC文件中权利的程序信息，请参见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编辑功能的资金目前由互联网协会提供。