Network Working Group A. Patel
Request for Comments: 4064 K. Leung
Category: Standards Track Cisco Systems
May 2005
Network Working Group A. Patel
Request for Comments: 4064 K. Leung
Category: Standards Track Cisco Systems
May 2005
Experimental Message, Extensions, and Error Codes for Mobile IPv4
移动IPv4的实验性消息、扩展和错误代码
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
摘要
Mobile IPv4 message types range from 0 to 255. This document reserves a message type for use by an individual, company, or organization for experimental purposes, to evaluate enhancements to Mobile IPv4 messages before a formal standards proposal is issued.
移动IPv4消息类型的范围从0到255。本文档保留一种消息类型，供个人、公司或组织出于实验目的使用，以便在发布正式标准提案之前评估移动IPv4消息的增强功能。
Table of Contents
目录
1. Introduction ................................................. 2
2. Terminology .................................................. 3
3. Experimental Message ......................................... 3
4. Experimental Extensions ...................................... 4
4.1. Non-skippable Mobile IPv4 Experimental Extension ....... 5
4.2. Non-skippable ICMP Router Discovery Exp. Extension ..... 5
4.3. Skippable Mobile IPv4 Experimental Extension ........... 6
4.4. Skippable ICMP Router Discovery Experimental Extension . 6
5. Experimental Error Codes ..................................... 7
6. Mobility Entity Considerations ............................... 7
7. IANA Considerations .......................................... 7
7.1. New Message Type ....................................... 8
7.2. New Extension Values ................................... 8
7.3. New Error Codes ........................................ 8
8. Security Considerations ...................................... 8
9. Backward Compatibility Considerations ........................ 9
10. Acknowledgements.............................................. 9
11. References ................................................... 9
11.1. Normative References ................................... 9
11.2. Informative References ................................. 9
1. Introduction ................................................. 2
2. Terminology .................................................. 3
3. Experimental Message ......................................... 3
4. Experimental Extensions ...................................... 4
4.1. Non-skippable Mobile IPv4 Experimental Extension ....... 5
4.2. Non-skippable ICMP Router Discovery Exp. Extension ..... 5
4.3. Skippable Mobile IPv4 Experimental Extension ........... 6
4.4. Skippable ICMP Router Discovery Experimental Extension . 6
5. Experimental Error Codes ..................................... 7
6. Mobility Entity Considerations ............................... 7
7. IANA Considerations .......................................... 7
7.1. New Message Type ....................................... 8
7.2. New Extension Values ................................... 8
7.3. New Error Codes ........................................ 8
8. Security Considerations ...................................... 8
9. Backward Compatibility Considerations ........................ 9
10. Acknowledgements.............................................. 9
11. References ................................................... 9
11.1. Normative References ................................... 9
11.2. Informative References ................................. 9
Mobile IPv4 message types range from 0 to 255. This document reserves a message type for experimental purposes, to evaluate enhancements to Mobile IPv4 messages before a formal standards proposal is issued.
移动IPv4消息类型的范围从0到255。本文档保留了一种用于实验目的的消息类型，以便在发布正式标准提案之前评估移动IPv4消息的增强功能。
Without experimental message capability, one would have to select a type value from the range defined for IANA assignment, which may result in collisions.
如果没有实验性消息功能，则必须从为IANA分配定义的范围中选择一个类型值，这可能会导致冲突。
Within a message, Mobile IP defines a general extension mechanism allowing optional information to be carried by Mobile IP control messages. Extensions are not skippable if defined in the range [0- 127] and are skippable if defined in the range [128-255]. This document reserves extension types in both the skippable and non-skippable ranges for experimental use.
在消息中，移动IP定义了一种通用扩展机制，允许移动IP控制消息携带可选信息。如果在[0-127]范围内定义扩展，则扩展不可跳过；如果在[128-255]范围内定义扩展，则扩展可跳过。本文档保留可跳过和不可跳过范围内的扩展类型，以供实验使用。
Mobile IPv4 defines error codes for use by the FA [64-127] and HA [128-192]. This document reserves an error code in both of these ranges for experimental use.
移动IPv4定义了供FA[64-127]和HA[128-192]使用的错误代码。本文件在这两个范围内保留一个错误代码，供实验使用。
The definition of experimental numbers in this document is made according to the recommendation of Section 2.2 of BCP 82, RFC 3692.
本文件中的实验数定义根据BCP 82，RFC 3692第2.2节的建议进行。
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [1].
本文件中的关键词“必须”、“不得”、“必需”、“应”、“不应”、“应”、“不应”、“建议”、“可”和“可选”应按照[1]中所述进行解释。
In addition, this document frequently uses the following terms:
此外，本文件经常使用以下术语：
EXP-MSG-TYPE: A Mobile-IPv4 message number assigned for experimental use. IANA has assigned message number 255 for this.
EXP-MSG-TYPE：分配给实验使用的Mobile-IPv4消息编号。IANA已为此分配了邮件编号255。
EXP-SKIP-EXT-TYPE: A Mobile-IPv4 and ICMP router discovery Agent Advertisement extension number assigned for experimental use. IANA has assigned extension number 255 for this.
EXP-SKIP-EXT-TYPE：分配给实验使用的Mobile-IPv4和ICMP路由器发现代理播发扩展号。IANA已为此分配了分机号码255。
EXP-NONSKIP-EXT-TYPE: A Mobile-IPv4 and ICMP router discovery Agent Advertisement extension number for experimental use. IANA has assigned extension number 127 for this.
EXP-NONSKIP-EXT-TYPE：用于实验的Mobile-IPv4和ICMP路由器发现代理播发扩展号。IANA为此分配了分机号码127。
EXP-HA-ERROR-CODE: A Mobile-IPv4 error code for use by the HA in MIPv4 reply messages to indicate an error condition. IANA has assigned error code 192 for this.
EXP-HA-ERROR-CODE：HA在MIPv4回复消息中用于指示错误条件的Mobile-IPv4错误代码。IANA为此分配了错误代码192。
EXP-FA-ERROR-CODE: A Mobile-IPv4 error code for use by FA in reply messages to indicate an error condition. IANA has assigned error code 127 for this.
EXP-FA-ERROR-CODE：一个Mobile-IPv4错误代码，供FA在回复消息中用于指示错误情况。IANA为此分配了错误代码127。
Mobility Entity: Entities as defined in [2] (home agent, foreign agent, and mobile node).
移动实体：如[2]中定义的实体（归属代理、外部代理和移动节点）。
As the nature and purpose of an experimental message cannot be known in advance, the structure is defined as having an opaque payload. Entities implementing the message can interpret the message according to their implementation. Interpreting based on extensions present in the message is one suggestion.
由于无法预先知道实验消息的性质和目的，因此该结构被定义为具有不透明的有效负载。实现消息的实体可以根据其实现来解释消息。根据信息中的扩展进行口译是一个建议。
These messages may be used between the mobility entities (Home Agent, Foreign Agent, and Mobile Node). Experimental messages MUST be authenticated using any of the authentication mechanisms defined for Mobile IP ([2], [5]).
这些消息可以在移动实体（归属代理、外部代理和移动节点）之间使用。实验性消息必须使用为移动IP定义的任何身份验证机制进行身份验证（[2]，[5]）。
This message MAY contain extensions defined in Mobile IP, including vendor-specific extensions [4].
此消息可能包含移动IP中定义的扩展，包括特定于供应商的扩展[4]。
IP fields:
IP fields:translate error, please retry
Source Address: Typically the interface address from which the message is sent.
源地址：通常是发送消息的接口地址。
Destination Address: The address of the agent or the Mobile Node.
目的地地址：代理或移动节点的地址。
UDP fields:
UDP字段：
Source Port Set according to RFC 768 (variable)
根据RFC 768设置的源端口（变量）
Destination Port Set to the value 434
目标端口设置为值434
Mobile IP fields shown below follow the UDP header.
下面显示的移动IP字段位于UDP标头之后。
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 | Opaque. . .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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 | Opaque. . .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type 255 (EXP-MSG-TYPE)
255型（EXP-MSG-Type）
Opaque Zero or more octets of data, with structure defined only by the particular experiment it is used for.
不透明的零个或多个八位字节的数据，其结构仅由其用于的特定实验定义。
Once an experimental message has been tested and shown to be useful, a permanent number should be obtained through the normal IANA numbers assignment procedures.
一旦实验信息经过测试并证明有用，应通过正常IANA编号分配程序获得永久编号。
A single experimental message type is defined. This message can contain extensions based on which the message can be interpreted.
定义了单个实验消息类型。此消息可以包含可根据其解释消息的扩展。
Up-to-date values for the message types for Mobile IP control messages are specified in the most recent "Assigned Numbers" [3].
移动IP控制消息的消息类型的最新值在最新的“分配编号”[3]中指定。
This document reserves Mobile IPv4 extensions in both the skippable and non-skippable ranges for experimental purposes. The long extension format (for non-skippable extensions) and short extension format (for skippable extensions), as defined by [2], are used for Mobile IPv4 experimental extensions.
本文档保留可跳过和不可跳过范围内的移动IPv4扩展，以供实验使用。[2]定义的长扩展格式（用于不可跳过的扩展）和短扩展格式（用于可跳过的扩展）用于移动IPv4实验扩展。
Also, ICMP router discovery extension numbers in both the skippable and non-skippable ranges are reserved for experimental use.
此外，可跳过和不可跳过范围内的ICMP路由器发现扩展号保留供实验使用。
This format is applicable for non-skippable extensions and may carry information more than 256 bytes.
此格式适用于不可跳过的扩展，并且可能包含超过256字节的信息。
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 | Sub-Type | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Opaque. . .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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 | Sub-Type | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Opaque. . .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type 127 (EXP-NONSKIP-EXT-TYPE) is the type, which describes an experimental extension.
127型（EXP-NONSKIP-EXT-Type）是描述实验扩展的类型。
Sub-Type A unique number given to each member in the aggregated type.
子类型为聚合类型中的每个成员指定的唯一编号。
Length Indicates the length (in bytes) of the data field within this extension. It does NOT include the Type, Sub-Type, and Length fields.
Length表示此扩展中数据字段的长度（以字节为单位）。它不包括类型、子类型和长度字段。
Opaque Zero or more octets of data, with structure defined only by the particular experiment it is used for.
不透明的零个或多个八位字节的数据，其结构仅由其用于的特定实验定义。
As the length field is 16 bits wide, the extension data can exceed 256 bytes in length.
由于长度字段为16位宽，扩展数据的长度可以超过256字节。
This format is applicable for non-skippable extensions.
This format is applicable for non-skippable extensions.translate error, please retry
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 | Opaque . . .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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 | Opaque . . .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type 127 (EXP-NONSKIP-EXT-TYPE) is the type, which describes an ICMP router discovery experimental extension.
类型127（EXP-NONSKIP-EXT-Type）是描述ICMP路由器发现实验扩展的类型。
Length Indicates the length (in bytes) of the data field within this extension. It does NOT include the Type and Length fields.
Length表示此扩展中数据字段的长度（以字节为单位）。它不包括类型和长度字段。
Opaque Zero or more octets of data, with structure defined only by the particular experiment it is used for.
不透明的零个或多个八位字节的数据，其结构仅由其用于的特定实验定义。
A node that receives a router advertisement with this extension should ignore the extension if it does not recognize it.
接收具有此扩展的路由器播发的节点如果无法识别扩展，则应忽略该扩展。
A mobility entity that understands this extension but does not recognize it should drop (ignore) the router advertisement.
理解此扩展但不识别它的移动实体应丢弃（忽略）路由器公告。
This format is applicable for skippable extensions, which carry information less than 256 bytes.
此格式适用于可跳过的扩展，这些扩展包含的信息少于256字节。
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 | Sub-Type | Opaque. . .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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 | Sub-Type | Opaque. . .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type 255 (EXP-SKIP-EXT-TYPE) is the type, which describes an experimental extension.
类型255（EXP-SKIP-EXT-Type）是描述实验扩展的类型。
Length Indicates the length (in bytes) of the data field within this extension. It does NOT include the Type and Length fields.
Length表示此扩展中数据字段的长度（以字节为单位）。它不包括类型和长度字段。
Sub-Type A unique number given to each member in the aggregated type.
子类型为聚合类型中的每个成员指定的唯一编号。
Opaque Zero or more octets of data, with structure defined only by the particular experiment it is used for.
不透明的零个或多个八位字节的数据，其结构仅由其用于的特定实验定义。
As the length field is 8 bits wide, the extension data cannot exceed 256 bytes in length.
由于长度字段的宽度为8位，扩展数据的长度不能超过256字节。
This format is applicable for skippable ICMP router discovery extensions. This extension should be ignored if an implementation does not understand it.
此格式适用于可跳过的ICMP路由器发现扩展。如果实现不理解此扩展，则应忽略此扩展。
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 | Opaque. . .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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 | Opaque. . .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type 255 (EXP-SKIP-EXT-TYPE) is the type, which describes an experimental extension.
类型255（EXP-SKIP-EXT-Type）是描述实验扩展的类型。
Length Indicates the length (in bytes) of the data field within this extension. It does NOT include the Type and Length fields.
Length表示此扩展中数据字段的长度（以字节为单位）。它不包括类型和长度字段。
Opaque Zero or more octets of data, with structure defined only by the particular experiment it is used for.
不透明的零个或多个八位字节的数据，其结构仅由其用于的特定实验定义。
This document reserves the reply error code EXP-FA-ERROR-CODE for use by the FA. This document also reserves the reply error code EXP-HA-ERROR-CODE for use by the HA.
本文件保留回复错误代码EXP-FA-error-code供FA使用。本文件还保留回复错误代码EXP-HA-error-code供HA使用。
These experimental error codes may be used in registration reply messages.
这些实验性错误代码可用于注册回复消息中。
It is recommended that experimental error codes be used with experimental messages and extensions whenever none of the standardized error codes are applicable.
当标准化错误代码均不适用时，建议将实验错误代码与实验消息和扩展一起使用。
Mobility entities can send and receive experimental messages. Implementations that don't understand the message type SHOULD silently discard the message.
移动实体可以发送和接收实验性消息。不理解消息类型的实现应该自动放弃消息。
Experimental extensions can be carried in experimental messages and standards-defined messages. In the latter case, it is suggested that experimental extensions MUST NOT be used in deployed products and that usage be restricted to experiments only.
实验扩展可以在实验消息和标准定义的消息中进行。在后一种情况下，建议不得在已部署的产品中使用实验性扩展，并且使用仅限于实验。
This document defines a control message to be used between mobility entities, two new extension formats, and two new error codes. To ensure correct interoperation based on this specification, IANA has reserved values in the Mobile IPv4 number space, as defined in [2], for one new message type, two new extensions, and two error codes.
This document defines a control message to be used between mobility entities, two new extension formats, and two new error codes. To ensure correct interoperation based on this specification, IANA has reserved values in the Mobile IPv4 number space, as defined in [2], for one new message type, two new extensions, and two error codes.translate error, please retry
A new Mobile IPv4 control message using UDP port 434, type 255 (EXP-MSG-TYPE), has been defined by IANA. This value has been taken from the same number space as Mobile IP Registration Request (Type = 1) and Mobile IP Registration Reply (Type = 3).
IANA已经定义了使用UDP端口434、类型255（EXP-MSG-type）的新移动IPv4控制消息。此值取自与移动IP注册请求（类型=1）和移动IP注册回复（类型=3）相同的数字空间。
The following extension types are introduced by this specification:
本规范介绍了以下扩展类型：
Experimental non-skippable extension: The value 127 (EXP-NONSKIP-EXT-TYPE) has been assigned from the numbering space for non-skippable extensions, which may appear in Mobile IPv4 control messages.
实验性不可跳过扩展：值127（EXP-NONSKIP-EXT-TYPE）已从不可跳过扩展的编号空间中分配，该值可能出现在移动IPv4控制消息中。
Also, the same number, 127 (EXP-NONSKIP-EXT-TYPE), has been assigned from the numbering space for non-skippable extensions, which may appear in ICMP router discovery messages.
此外，同一编号127（EXP-NONSKIP-EXT-TYPE）已从编号空间分配给不可跳过的扩展，这可能出现在ICMP路由器发现消息中。
Experimental skippable extension: The value 255 (EXP-SKIP-EXT-TYPE) has been assigned from the numbering space for skippable extensions, which may appear in Mobile IPv4 control messages.
实验性可跳过扩展：值255（EXP-SKIP-EXT-TYPE）已从可跳过扩展的编号空间分配，该值可能出现在移动IPv4控制消息中。
Also, the same number, 255 (EXP-SKIP-EXT-TYPE), has been assigned from the numbering space for skippable extensions, which may appear in ICMP router discovery messages.
此外，相同的号码255（EXP-SKIP-EXT-TYPE）已从可跳过扩展的编号空间分配，该号码可能出现在ICMP路由器发现消息中。
The value 192 (EXP-HA-ERROR-CODE) has been defined by IANA to be used as a code field in messages generated by HA.
IANA已将值192（EXP-HA-ERROR-CODE）定义为HA生成的消息中的代码字段。
Also, the value 127 (EXP-FA-ERROR-CODE) has been defined by IANA to be used as the code field in messages generated by the FA.
此外，IANA还定义了值127（EXP-FA-ERROR-CODE），用作FA生成的消息中的代码字段。
Like all Mobile IP control messages, the experimental messages MUST be authenticated per the requirements specified in [2] or [5]. Experimental messages without a valid authenticator SHOULD be discarded.
与所有移动IP控制消息一样，实验消息必须按照[2]或[5]中规定的要求进行身份验证。应丢弃没有有效验证器的实验消息。
Mobility entities that don't understand the experimental message MUST silently discard it.
不理解实验消息的移动实体必须悄悄地丢弃它。
Mobility entities that don't understand the experimental skippable extensions MUST ignore them. Mobility entities that don't understand the non-skippable experimental extensions MUST silently discard the message containing them. This behavior is consistent with section 1.8 of [2].
不了解实验性可跳过扩展的移动性实体必须忽略它们。不理解不可跳过的实验扩展的移动实体必须默默地丢弃包含它们的消息。该行为符合[2]第1.8节的规定。
Foreign Agents and Home Agents SHOULD include an experimental error code in a reply message only if they have a general indication that the receiving entity would be able to parse it. This is indicated if the request message was of type EXP-MSG-TYPE or contained at least one experimental extension.
只有当外国代理和本国代理具有接收实体能够解析的一般指示时，它们才应该在回复消息中包含实验性错误代码。如果请求消息的类型为EXP-MSG-type或至少包含一个实验扩展名，则会指示此消息。
The authors would like to acknowledge Henrik Levkowetz for his detailed review of the document and suggestion to incorporate experimental extensions in this draft.
作者要感谢Henrik Levkowetz对文件的详细审查，并建议将实验扩展纳入本草案。
The authors would also like to acknowledge Thomas Narten for his initial review of the document and reference to [6] for general guidelines.
作者还想感谢Thomas Narten对该文件的初步审查，并参考[6]中的一般指南。
[1] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
[1] Bradner，S.，“RFC中用于表示需求水平的关键词”，BCP 14，RFC 2119，1997年3月。
[2] Perkins, C., "IP Mobility Support for IPv4", RFC 3344, August 2002.
[2] Perkins，C.，“IPv4的IP移动支持”，RFC 3344，2002年8月。
[3] Reynolds, J., "Assigned Numbers: RFC 1700 is Replaced by an On-line Database", RFC 3232, January 2002.
[3] Reynolds，J.，“分配号码：RFC 1700被在线数据库取代”，RFC 3232，2002年1月。
[4] Dommety, G. and K. Leung, "Mobile IP Vendor/Organization-Specific Extensions", RFC 3115, April 2001.
[4] Dommety，G.和K.Leung，“移动IP供应商/特定于组织的扩展”，RFC3115，2001年4月。
[5] Perkins, C. and P. Calhoun, "Mobile IPv4 Challenge/Response Extensions", RFC 3012, November 2000.
[5] Perkins，C.和P.Calhoun，“移动IPv4挑战/响应扩展”，RFC3012，2000年11月。
[6] Narten, T., "Assigning Experimental and Testing Numbers Considered Useful", BCP 82, RFC 3692, January 2004.
[6] Narten，T.，“分配被认为有用的实验和测试数字”，BCP 82，RFC 3692，2004年1月。
Authors' Addresses
Authors' Addressestranslate error, please retry
Questions and comments about this document should be directed to the Mobile IPv4 working group:
有关本文档的问题和意见，请联系移动IPv4工作组：
mip4@ietf.org
mip4@ietf.org
Questions and comments about this document may also be directed to the authors:
关于本文件的问题和意见也可向作者提出：
Alpesh Patel Cisco Systems 170 W. Tasman Drive, San Jose, CA 95134 USA
美国加利福尼亚州圣何塞塔斯曼大道西170号阿尔佩什·帕特尔思科系统公司，邮编95134
Phone: +1 408-853-9580
EMail: alpesh@cisco.com
Phone: +1 408-853-9580
EMail: alpesh@cisco.com
Kent Leung Cisco Systems 170 W. Tasman Drive, San Jose, CA 95134 USA
Kent Leung Cisco Systems美国加利福尼亚州圣何塞塔斯曼大道西170号，邮编95134
Phone: +1 408-526-5030
EMail: kleung@cisco.com
Phone: +1 408-526-5030
EMail: kleung@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 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编辑功能的资金目前由互联网协会提供。