Network Working Group R. Stewart
Request for Comments: 5354 Q. Xie
Category: Experimental The Resource Group
M. Stillman
Nokia
M. Tuexen
Muenster Univ. of Applied Sciences
September 2008
Network Working Group R. Stewart
Request for Comments: 5354 Q. Xie
Category: Experimental The Resource Group
M. Stillman
Nokia
M. Tuexen
Muenster Univ. of Applied Sciences
September 2008
Aggregate Server Access Protocol (ASAP) and Endpoint Handlespace Redundancy Protocol (ENRP) Parameters
聚合服务器访问协议（ASAP）和端点Handlespace冗余协议（ENRP）参数
Status of This Memo
关于下段备忘
This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard of any kind. Discussion and suggestions for improvement are requested. Distribution of this memo is unlimited.
这份备忘录为互联网社区定义了一个实验性协议。它没有规定任何类型的互联网标准。要求进行讨论并提出改进建议。本备忘录的分发不受限制。
Abstract
摘要
This document details the parameters of the Aggregate Server Access Protocol (ASAP) and Endpoint Handlespace Redundancy Protocol (ENRP) defined within the Reliable Server Pooling (RSerPool) architecture.
本文档详细介绍了可靠服务器池（RSerPool）体系结构中定义的聚合服务器访问协议（ASAP）和端点Handlespace冗余协议（ENRP）的参数。
Table of Contents
目录
1. Introduction ....................................................3
1.1. Conventions ................................................3
2. Parameters in General ...........................................3
3. ENRP-ASAP Common Parameters .....................................3
3.1. IPv4 Address Parameter .....................................6
3.2. IPv6 Address Parameter .....................................6
3.3. DCCP Transport Parameter ...................................7
3.4. SCTP Transport Parameter ...................................8
3.5. TCP Transport Parameter ....................................9
3.6. UDP Transport Parameter ....................................9
3.7. UDP-Lite Transport Parameter ..............................10
3.8. Pool Member Selection Policy Parameter ....................11
3.9. Pool Handle Parameter .....................................12
3.10. Pool Element Parameter ...................................12
3.11. Server Information Parameter .............................13
3.12. Operation Error Parameter ................................14
3.12.1. Unspecified Error .................................15
3.12.2. Unrecognized Parameter Error ......................15
3.12.3. Unrecognized Message Error ........................15
3.12.4. Invalid Values Error ..............................16
3.12.5. Non-Unique PE Identifier Error ....................16
3.12.6. Inconsistent Pool Policy Error ....................16
3.12.7. Lack of Resources Error ...........................16
3.12.8. Inconsistent Transport Type Error .................16
3.12.9. Inconsistent Data/Control Configuration Error .....16
3.12.10. Rejected Due to Security Considerations ..........16
3.12.11. Unknown Pool Handle Error ........................17
3.13. Cookie Parameter .........................................17
3.14. PE Identifier Parameter ..................................17
3.15. PE Checksum Parameter ....................................18
3.16. Opaque Transport Parameter ...............................18
4. Common Message Formats .........................................18
5. IANA Considerations ............................................20
5.1. A New Table for RSerPool Parameter Types ..................20
5.2. A New Table for RSerPool Error Causes .....................21
6. Security Considerations ........................................21
7. Normative References ...........................................21
1. Introduction ....................................................3
1.1. Conventions ................................................3
2. Parameters in General ...........................................3
3. ENRP-ASAP Common Parameters .....................................3
3.1. IPv4 Address Parameter .....................................6
3.2. IPv6 Address Parameter .....................................6
3.3. DCCP Transport Parameter ...................................7
3.4. SCTP Transport Parameter ...................................8
3.5. TCP Transport Parameter ....................................9
3.6. UDP Transport Parameter ....................................9
3.7. UDP-Lite Transport Parameter ..............................10
3.8. Pool Member Selection Policy Parameter ....................11
3.9. Pool Handle Parameter .....................................12
3.10. Pool Element Parameter ...................................12
3.11. Server Information Parameter .............................13
3.12. Operation Error Parameter ................................14
3.12.1. Unspecified Error .................................15
3.12.2. Unrecognized Parameter Error ......................15
3.12.3. Unrecognized Message Error ........................15
3.12.4. Invalid Values Error ..............................16
3.12.5. Non-Unique PE Identifier Error ....................16
3.12.6. Inconsistent Pool Policy Error ....................16
3.12.7. Lack of Resources Error ...........................16
3.12.8. Inconsistent Transport Type Error .................16
3.12.9. Inconsistent Data/Control Configuration Error .....16
3.12.10. Rejected Due to Security Considerations ..........16
3.12.11. Unknown Pool Handle Error ........................17
3.13. Cookie Parameter .........................................17
3.14. PE Identifier Parameter ..................................17
3.15. PE Checksum Parameter ....................................18
3.16. Opaque Transport Parameter ...............................18
4. Common Message Formats .........................................18
5. IANA Considerations ............................................20
5.1. A New Table for RSerPool Parameter Types ..................20
5.2. A New Table for RSerPool Error Causes .....................21
6. Security Considerations ........................................21
7. Normative References ...........................................21
The Aggregate Server Access Protocol (ASAP) [RFC5352], in conjunction with the Endpoint Handlespace Redundancy Protocol (ENRP) [RFC5353], provides a high-availability, data-transfer mechanism over IP networks.
聚合服务器访问协议（ASAP）[RFC5352]与端点Handlespace冗余协议（ENRP）[RFC5353]结合，提供了IP网络上的高可用性数据传输机制。
Both protocols work together and so share many common parameters used in message formats. This document details the common message parameters shared between the two protocols. This document provides parameter formats only; for procedures and message composition, please refer to the respective [RFC5352] and [RFC5353] documents.
这两个协议一起工作，因此共享消息格式中使用的许多公共参数。本文档详细介绍了两个协议之间共享的公共消息参数。本文件仅提供参数格式；有关程序和消息组成，请参考相应的[RFC5352]和[RFC5353]文档。
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119].
本文件中的关键词“必须”、“不得”、“必需”、“应”、“不应”、“应”、“不应”、“建议”、“可”和“可选”应按照[RFC2119]中所述进行解释。
All parameters described below MUST be in network byte order (aka Big Endian, i.e., the most significant byte first) during transmission.
在传输过程中，以下描述的所有参数必须以网络字节顺序排列（也称为Big-Endian，即最重要的字节优先）。
Please note that messages in both ENRP and ASAP are often composed of multiple parameters. These parameters may also be nested. In such a case, a nested parameter will include the length of the padding between the nested parameters but not the last padding.
请注意，ENRP和ASAP中的消息通常由多个参数组成。这些参数也可以嵌套。在这种情况下，嵌套参数将包括嵌套参数之间的填充长度，但不包括最后一个填充。
Parameters are defined in the following Type-Length-Value (TLV) format:
参数以以下类型长度值（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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Parameter Type | Parameter Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: :
: Parameter Value :
: +-------------------------------:
: | Padding :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Parameter Type | Parameter Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: :
: Parameter Value :
: +-------------------------------:
: | Padding :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Parameter Type: 16 bits (unsigned integer) The Type field is a 16-bit identifier of the type of parameter. It takes a value of 0 to 65534. The value of 65535 is reserved for IETF-defined extensions. Values, other than those defined in the specific ENRP parameter description, are reserved by IETF. (Additional types, when needed, will be defined in the future through appropriate IETF/ IANA procedures.) The Parameter Types are encoded such that the two bits of the highest-order specify the action that must be taken if the processing endpoint does not recognize the Parameter Type.
参数类型：16位（无符号整数）。类型字段是参数类型的16位标识符。它的值为0到65534。65535的值保留给IETF定义的扩展。IETF保留特定ENRP参数描述中定义的值以外的值。（需要时，将在将来通过适当的IETF/IANA程序定义其他类型。）对参数类型进行编码，以便最高阶的两位指定处理端点不识别参数类型时必须采取的操作。
00 Stop processing this ENRP or ASAP message and discard it; do not process any further parameters within it.
00停止处理此ENRP或ASAP消息并丢弃它；不要在其中处理任何其他参数。
01 Stop processing this ENRP or ASAP message and discard it; do not process any further parameters within it, and report the unrecognized parameter in an 'Unrecognized Parameter' error (see Section 3.12).
01停止处理此ENRP或ASAP消息并丢弃它；不要处理其中的任何其他参数，并在“unrecognized parameter”（未识别参数）错误中报告未识别的参数（参见第3.12节）。
10 Skip this parameter and continue processing.
10跳过此参数并继续处理。
11 Skip this parameter and continue processing, but report the unrecognized parameter in an 'Unrecognized Parameter' error (see Section 3.12).
11跳过此参数并继续处理，但在“unrecognized parameter”（未识别参数）错误中报告未识别的参数（参见第3.12节）。
The values of parameter types are defined as follows:
参数类型的值定义如下：
+-----------------+------------------------------+
| Value | Parameter Type |
+-----------------+------------------------------+
| 0x0 | (Reserved by IETF) |
| 0x1 | IPv4 Address |
| 0x2 | IPv6 Address |
| 0x3 | DCCP Transport |
| 0x4 | SCTP Transport |
| 0x5 | TCP Transport |
| 0x6 | UDP Transport |
| 0x7 | UDP-Lite |
| 0x8 | Pool Member Selection Policy |
| 0x9 | Pool Handle |
| 0xa | Pool Element |
| 0xb | Server Information |
| 0xc | Operation Error |
| 0xd | Cookie |
| 0xe | PE Identifier |
| 0xf | PE Checksum |
| 0x10 | Opaque Transport |
| 0x11-0xfffffffe | (Available for assignment) |
| 0xffffffff | IETF-defined extensions |
+-----------------+------------------------------+
+-----------------+------------------------------+
| Value | Parameter Type |
+-----------------+------------------------------+
| 0x0 | (Reserved by IETF) |
| 0x1 | IPv4 Address |
| 0x2 | IPv6 Address |
| 0x3 | DCCP Transport |
| 0x4 | SCTP Transport |
| 0x5 | TCP Transport |
| 0x6 | UDP Transport |
| 0x7 | UDP-Lite |
| 0x8 | Pool Member Selection Policy |
| 0x9 | Pool Handle |
| 0xa | Pool Element |
| 0xb | Server Information |
| 0xc | Operation Error |
| 0xd | Cookie |
| 0xe | PE Identifier |
| 0xf | PE Checksum |
| 0x10 | Opaque Transport |
| 0x11-0xfffffffe | (Available for assignment) |
| 0xffffffff | IETF-defined extensions |
+-----------------+------------------------------+
Table 1
表1
Parameter Length: 16 bits (unsigned integer) The Parameter Length field contains the size of the parameter in bytes, including the Parameter Type, Parameter Length, and Parameter Value fields. Thus, a parameter with a zero-length Parameter Value field would have a Length field of 4. The total length of a parameter (including Type, Parameter Length and Value fields) MUST be a multiple of 4 bytes. If the length of the parameter is not a multiple of 4 bytes, the sender MUST pad the parameter at the end (i.e., after the Parameter Value field) with all zero bytes. The length of this padding is not included in the Parameter Length field. A sender MUST NOT pad with more than 3 bytes. The receiver MUST ignore the padding bytes.
参数长度：16位（无符号整数）。参数长度字段包含以字节为单位的参数大小，包括参数类型、参数长度和参数值字段。因此，具有零长度参数值字段的参数的长度字段为4。参数的总长度（包括类型、参数长度和值字段）必须是4字节的倍数。如果参数的长度不是4字节的倍数，则发送方必须将所有零字节填入参数末尾（即参数值字段之后）。此填充的长度不包括在参数长度字段中。发送方的填充长度不得超过3个字节。接收器必须忽略填充字节。
Parameter Value: variable length. The Parameter Value field contains the actual information to be transferred in the parameter.
参数值：可变长度。参数值字段包含要在参数中传输的实际信息。
Parameter Padding: variable length. The Parameter Padding, as described above.
参数填充：可变长度。参数填充，如上所述。
This parameter defines a TLV that carries an IPv4 address.
此参数定义携带IPv4地址的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 = 0x1 | Length = 0x8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| IPv4 Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 0x1 | Length = 0x8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| IPv4 Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
IPv4 Address: 32 bits (unsigned integer) Contains an IPv4 address. It is binary encoded.
IPv4地址：32位（无符号整数）包含IPv4地址。它是二进制编码的。
This parameter defines a TLV that carries an IPv6 address.
此参数定义携带IPv6地址的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 = 0x2 | Length = 0x14 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
| IPv6 Address |
| |
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 0x2 | Length = 0x14 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
| IPv6 Address |
| |
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
IPv6 Address: 128 bits (unsigned integer) Contains an IPv6 address. It is binary encoded.
IPv6地址：128位（无符号整数）包含IPv6地址。它是二进制编码的。
This parameter defines a TLV that describes a user transport using Datagram Congestion Control Protocol (DCCP).
此参数定义一个TLV，该TLV使用数据报拥塞控制协议（DCCP）描述用户传输。
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 = 0x3 | Length = variable |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| DCCP Port | (reserved) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| DCCP Service Code |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: IPv4 or IPv6 Address :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 0x3 | Length = variable |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| DCCP Port | (reserved) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| DCCP Service Code |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: IPv4 or IPv6 Address :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Length: 16 bits (unsigned integer) Indicates the entire length of the parameter in number of octets, including the Type, Length, DCCP port, reserved fields, and IP Address Parameter.
长度：16位（无符号整数）表示参数的整个长度（以八位字节为单位），包括类型、长度、DCCP端口、保留字段和IP地址参数。
DCCP Port: 16 bits (unsigned integer) The DCCP port number signed to this DCCP user transport.
DCCP端口：16位（无符号整数）签名到此DCCP用户传输的DCCP端口号。
DCCP Service Code: 32 bits (unsigned integer) The DCCP service code signed to this DCCP user transport.
DCCP服务代码：32位（无符号整数）签名到此DCCP用户传输的DCCP服务代码。
IPv4 or IPv6 Address Indicates an IPv4 or IPv6 address parameter (as defined above in Section 3.1 and Section 3.2) assigned to this DCCP user transport. Unlike in an SCTP Transport parameter, only one IP address parameter can be present in a DCCP Transport parameter.
IPv4或IPv6地址表示分配给此DCCP用户传输的IPv4或IPv6地址参数（如上文第3.1节和第3.2节所定义）。与SCTP传输参数不同，DCCP传输参数中只能存在一个IP地址参数。
Note: The DCCP Port MUST NOT be used for control information. For this reason, no Transport Use field is provided. DCCP MUST always be treated as a "Data Only" type transport use.
注意：DCCP端口不得用于控制信息。因此，未提供“传输使用”字段。DCCP必须始终被视为“仅数据”类型的传输使用。
This parameter defines a TLV that describes a user transport using Stream Control Transport Protocol (SCTP).
此参数定义一个TLV，该TLV使用流控制传输协议（SCTP）描述用户传输。
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 = 0x4 | Length = variable |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SCTP Port | Transport Use |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: IPv4 or IPv6 Address #1 :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: :
: ... :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: IPv4 or IPv6 Address #n :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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 = 0x4 | Length = variable |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SCTP Port | Transport Use |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: IPv4 or IPv6 Address #1 :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: :
: ... :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: IPv4 or IPv6 Address #n :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Length: 16 bits (unsigned integer) Indicates the entire length of the parameter in number of octets, including the Type, Length, SCTP port, reserved fields, and all IP Address Parameters present.
长度：16位（无符号整数）表示参数的整个长度（以八位字节为单位），包括类型、长度、SCTP端口、保留字段和所有存在的IP地址参数。
SCTP Port: 16 bits (unsigned integer) The SCTP port number signed to this SCTP user transport.
SCTP端口：16位（无符号整数）签名到此SCTP用户传输的SCTP端口号。
Transport Use: 16 bits (unsigned integer) This field represents how the pool element intends this transport address to be used. The field MUST be populated with one of the following values:
传输使用：16位（无符号整数）此字段表示池元素打算如何使用此传输地址。该字段必须填充以下值之一：
+-------------------+--------+
| Type | Value |
+-------------------+--------+
| DATA ONLY | 0x0000 |
| DATA plus CONTROL | 0x0001 |
+-------------------+--------+
+-------------------+--------+
| Type | Value |
+-------------------+--------+
| DATA ONLY | 0x0000 |
| DATA plus CONTROL | 0x0001 |
+-------------------+--------+
IPv4 or IPv6 Address #1 - #n Each indicates an IPv4 or IPv6 address parameter (as defined above in Section 3.1 and Section 3.2) assigned to this SCTP user transport. An SCTP Transport parameter may have a mixed list of IPv4 and IPv6 addresses and at least one IP address parameter MUST be present in an SCTP Transport parameter.
IPv4或IPv6地址#1-#n分别表示分配给此SCTP用户传输的IPv4或IPv6地址参数（如上文第3.1节和第3.2节所定义）。SCTP传输参数可能包含IPv4和IPv6地址的混合列表，并且SCTP传输参数中必须至少存在一个IP地址参数。
This parameter defines a TLV that describes a user transport using TCP protocol.
此参数定义一个TLV，该TLV描述使用TCP协议的用户传输。
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 = 0x5 | Length = variable |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| TCP Port | (reserved) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: IPv4 or IPv6 Address :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 0x5 | Length = variable |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| TCP Port | (reserved) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: IPv4 or IPv6 Address :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Length: 16 bits (unsigned integer) Indicates the entire length of the parameter in number of octets, including the Type, Length, TCP port, reserved fields, and IP Address Parameter.
长度：16位（无符号整数）表示参数的整个长度（以八位字节为单位），包括类型、长度、TCP端口、保留字段和IP地址参数。
TCP Port: 16 bits (unsigned integer) The TCP port number signed to this TCP user transport.
TCP端口：16位（无符号整数）签名到此TCP用户传输的TCP端口号。
IPv4 or IPv6 Address Indicates an IPv4 or IPv6 address parameter (as defined above in Section 3.1 and Section 3.2) assigned to this TCP user transport. Unlike in an SCTP Transport parameter, only one IP Address parameter can be present in a TCP Transport parameter.
IPv4或IPv6地址表示分配给此TCP用户传输的IPv4或IPv6地址参数（如上文第3.1节和第3.2节所定义）。与SCTP传输参数不同，TCP传输参数中只能存在一个IP地址参数。
Note: The TCP Port MUST NOT be used for control information. For this reason, no Transport Use field is provided. TCP MUST always be treated as a "Data Only" type transport use.
注意：TCP端口不得用于控制信息。因此，未提供“传输使用”字段。TCP必须始终被视为“仅数据”类型的传输使用。
This parameter defines a TLV that describes a user transport using UDP protocol.
此参数定义一个TLV，该TLV描述使用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 = 0x6 | Length = variable |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| UDP Port | (reserved) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: IPv4 or IPv6 Address :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 0x6 | Length = variable |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| UDP Port | (reserved) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: IPv4 or IPv6 Address :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Length: 16 bits (unsigned integer) Indicates the entire length of the parameter in number of octets, including the Type, Length, UDP port, reserved fields, and IP Address Parameter.
长度：16位（无符号整数）表示参数的整个长度（以八位字节为单位），包括类型、长度、UDP端口、保留字段和IP地址参数。
UDP Port: 16 bits (unsigned integer) The UDP port number signed to this UDP user transport.
UDP端口：16位（无符号整数）签名到此UDP用户传输的UDP端口号。
IPv4 or IPv6 Address Indicates an IPv4 or IPv6 address parameter (as defined above in Section 3.1 and Section 3.2) assigned to this UDP user transport. Unlike in an SCTP Transport parameter, only one IP Address parameter can be present in a UDP Transport parameter.
IPv4或IPv6地址表示分配给此UDP用户传输的IPv4或IPv6地址参数（如上文第3.1节和第3.2节所定义）。与SCTP传输参数不同，UDP传输参数中只能存在一个IP地址参数。
Note: The UDP Port MUST NOT be used for control information. For this reason, no Transport Use field is provided. UDP MUST always be treated as a "Data Only" type transport use.
注意：UDP端口不得用于控制信息。因此，未提供“传输使用”字段。UDP必须始终被视为“仅数据”类型的传输使用。
This parameter defines a TLV that describes a user transport using UDP-Lite protocol.
此参数定义一个TLV，该TLV描述使用UDP Lite协议的用户传输。
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 = 0x7 | Length = variable |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| UDP-Lite Port | (reserved) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: IPv4 or IPv6 Address :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 0x7 | Length = variable |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| UDP-Lite Port | (reserved) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: IPv4 or IPv6 Address :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Length: 16 bits (unsigned integer) Indicates the entire length of the parameter in number of octets, including the Type, Length, UDP-Lite port, reserved fields, and IP Address Parameter.
长度：16位（无符号整数）表示参数的整个长度（以八位字节为单位），包括类型、长度、UDP Lite端口、保留字段和IP地址参数。
UDP Port: 16 bits (unsigned integer) The UDP-Lite port number signed to this UDP-Lite user transport.
UDP端口：16位（无符号整数）签名到此UDP Lite用户传输的UDP Lite端口号。
IPv4 or IPv6 Address Indicates an IPv4 or IPv6 address parameter (as defined above in Section 3.1 and Section 3.2) assigned to this UDP-Lite user transport. Unlike in an SCTP Transport parameter, only one IP address parameter can be present in a UDP-Lite transport parameter.
IPv4或IPv6地址表示分配给此UDP Lite用户传输的IPv4或IPv6地址参数（如上文第3.1节和第3.2节所定义）。与SCTP传输参数不同，UDP Lite传输参数中只能存在一个IP地址参数。
Note: The UDP-Lite Port MUST NOT be used for control information. For this reason, no Transport Use field is provided. UDP-Lite MUST always be treated as a "Data Only" type transport use.
注意：UDP Lite端口不得用于控制信息。因此，未提供“传输使用”字段。UDP Lite必须始终被视为“仅数据”类型的传输使用。
This parameter defines a pool member selection policy. RSerPool supports multiple pool member selection policies and also allows the definition of new selection policies in the future.
此参数定义池成员选择策略。RSerPool支持多个池成员选择策略，并允许将来定义新的选择策略。
The enforcement rules and handling procedures of all the policies are defined in [RFC5352].
[RFC5352]中定义了所有政策的实施规则和处理程序。
All pool member selection policies, both present and future, MUST use the following general parameter format:
当前和将来的所有池成员选择策略必须使用以下常规参数格式：
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 = 0x8 | Length = variable |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Policy Type |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Policy-specific Data |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 0x8 | Length = variable |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Policy Type |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Policy-specific Data |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Length: 16 bits (unsigned integer) Indicates the entire length of the parameter in number of octets, including the Type, Length, Policy Type, and the Policy-specific Data fields. Note, the Length field value will NOT include any padding at the end of the parameter.
长度：16位（无符号整数）表示参数的整个长度（以八位字节为单位），包括类型、长度、策略类型和特定于策略的数据字段。注意，“长度”字段值将不包括参数末尾的任何填充。
Policy Type: 32 bits (unsigned integer) Specifies the type of selection policy. The values are defined in [RFC5356].
策略类型：32位（无符号整数）指定选择策略的类型。这些值在[RFC5356]中定义。
Policy-specific Data: The structure and fields for each presently defined policy type are described in detail in [RFC5356].
特定于策略的数据：[RFC5356]中详细描述了当前定义的每种策略类型的结构和字段。
This parameter holds a pool handle.
此参数保存池句柄。
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 = 0x9 | Length=variable |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: :
: Pool Handle :
: :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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 = 0x9 | Length=variable |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: :
: Pool Handle :
: :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Length: 16 bits (unsigned integer) Indicates the entire length of the parameter in number of octets, including the Type, Length, and Pool Handle string. Note, the value in the Length field will NOT cover any padding at the end of the parameter.
长度：16位（无符号整数）表示参数的整个长度（以八位字节为单位），包括类型、长度和池句柄字符串。注意，“长度”字段中的值不会覆盖参数末尾的任何填充。
Pool Handle Defined as a sequence of (Length - 4) bytes.
池句柄定义为（长度-4）字节的序列。
This parameter is used in multiple ENRP messages to represent an ASAP endpoint (i.e., a Pool Element (PE) in a pool) and the associated information, such as its transport address, selection policy, and other operational or status information of the PE.
此参数在多个ENRP消息中用于表示ASAP端点（即池中的池元素（PE））和相关信息，例如其传输地址、选择策略以及PE的其他操作或状态信息。
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 = 0xa | Length=variable |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| PE Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Home ENRP Server Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Registration Life |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: User Transport param :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: Member Selection Policy param :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: ASAP Transport param :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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 = 0xa | Length=variable |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| PE Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Home ENRP Server Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Registration Life |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: User Transport param :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: Member Selection Policy param :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: ASAP Transport param :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Length: 16 bits (unsigned integer) Indicates the entire length of the parameter in number of octets, including the Type, Length, PE Identifier, Registration Life, User Transport, and Member Selection Policy parameters. Note, the value in the Length field will NOT cover any padding at the end of this Pool Element parameter.
长度：16位（无符号整数）表示参数的整个长度（以八位字节为单位），包括类型、长度、PE标识符、注册期限、用户传输和成员选择策略参数。注意，“长度”字段中的值不会覆盖此池元素参数末尾的任何填充。
PE Identifier: 32 bits (unsigned integer) Uniquely identifies the PE in the pool. The PE picks its identifier when it starts up.
PE标识符：32位（无符号整数）唯一标识池中的PE。PE在启动时选择其标识符。
Home ENRP Server Identifier: 32 bits (unsigned integer) Indicates the current Home ENRP server of this PE. Set to all 0s if the PE's Home ENRP server is undetermined.
家庭ENRP服务器标识符：32位（无符号整数）表示此PE的当前家庭ENRP服务器。如果PE的主ENRP服务器未确定，则设置为所有0。
Registration Life: 32 bits (signed integer) Indicates the lifetime of the registration in number of seconds. A value of -1 indicates infinite lifetime.
注册寿命：32位（有符号整数）表示注册的寿命，以秒为单位。值-1表示无限寿命。
User Transport This can be either an DCCP, SCTP, TCP, UDP, UDP-Lite, or Opaque Transport parameter (see Section 3.3, Section 3.4, Section 3.5, Section 3.6, Section 3.7, and Section 3.16). A PE MUST have one and only one User Transport.
用户传输这可以是DCCP、SCTP、TCP、UDP、UDP Lite或不透明传输参数（请参阅第3.3节、第3.4节、第3.5节、第3.6节、第3.7节和第3.16节）。PE必须有且只能有一个用户传输。
Member Selection Policy Contains one of the defined member selection policy parameters (see Section 3.8).
成员选择策略包含一个已定义的成员选择策略参数（参见第3.8节）。
ASAP Transport This indicates the ASAP transport address of the PE and MUST be an SCTP type transport parameter (see Section 3.4).
ASAP传输这表示PE的ASAP传输地址，必须是SCTP类型的传输参数（参见第3.4节）。
This parameter is used in ENRP to pass basic information of an ENRP server.
此参数在ENRP中用于传递ENRP服务器的基本信息。
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 = 0xb | Length=variable |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Server ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: Server Transport :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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 = 0xb | Length=variable |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Server ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: Server Transport :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Length: 16 bits (unsigned integer) Indicates the entire length of the parameter in number of bytes. Note, the value in the Length field will NOT cover any padding at the end of the parameter.
长度：16位（无符号整数）表示参数的整个长度（字节数）。注意，“长度”字段中的值不会覆盖参数末尾的任何填充。
Server ID: 32 bits (unsigned integer) This is the ID of the ENRP server, as defined in [RFC5353].
服务器ID:32位（无符号整数）这是ENRP服务器的ID，如[RFC5353]中所定义。
Server Transport: This is an SCTP Transport Parameter, as defined in Section 3.4, that contains the network access address(es), SCTP port number, etc. of the ENRP server.
服务器传输：这是第3.4节中定义的SCTP传输参数，包含ENRP服务器的网络访问地址、SCTP端口号等。
This parameter is used in both ENRP and ASAP for a message sender to report an error(s) to a message receiver.
此参数在ENRP和ASAP中都用于消息发送方向消息接收方报告错误。
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 = 0xc | Length=variable |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: :
: one or more Error Causes :
: :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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 = 0xc | Length=variable |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: :
: one or more Error Causes :
: :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Length: 16 bits (unsigned integer) Indicates the entire length of the parameter in number of bytes. Note, the value in the Length field will NOT cover any padding at the end of the parameter.
长度：16位（无符号整数）表示参数的整个长度（字节数）。注意，“长度”字段中的值不会覆盖参数末尾的任何填充。
Error causes are defined as variable-length parameters using the following format:
错误原因定义为使用以下格式的可变长度参数：
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Cause Code | Cause Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: :
: Cause-Specific Information :
: :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Cause Code | Cause Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: :
: Cause-Specific Information :
: :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Cause Code: 16 bits (unsigned integer) Defines the type of error condition being reported.
原因代码：16位（无符号整数）定义报告的错误条件类型。
+------------------+-----------------------------------------+
| Cause Code Value | Cause Code |
+------------------+-----------------------------------------+
| 0x0 | Unspecified Error |
| 0x1 | Unrecognized Parameter |
| 0x2 | Unrecognized Message |
| 0x3 | Invalid Values |
| 0x4 | Non-unique PE Identifier |
| 0x5 | Inconsistent Pooling Policy |
| 0x6 | Lack of Resources |
| 0x7 | Inconsistent Transport Type |
| 0x8 | Inconsistent Data/Control Configuration |
| 0x9 | Unknown Pool Handle |
| 0xa | Rejected due to security considerations |
| 0xb -0xffff | (Available for assignment) |
+------------------+-----------------------------------------+
+------------------+-----------------------------------------+
| Cause Code Value | Cause Code |
+------------------+-----------------------------------------+
| 0x0 | Unspecified Error |
| 0x1 | Unrecognized Parameter |
| 0x2 | Unrecognized Message |
| 0x3 | Invalid Values |
| 0x4 | Non-unique PE Identifier |
| 0x5 | Inconsistent Pooling Policy |
| 0x6 | Lack of Resources |
| 0x7 | Inconsistent Transport Type |
| 0x8 | Inconsistent Data/Control Configuration |
| 0x9 | Unknown Pool Handle |
| 0xa | Rejected due to security considerations |
| 0xb -0xffff | (Available for assignment) |
+------------------+-----------------------------------------+
Table 2
表2
Cause Length: 16 bits (unsigned integer) Set to the size of the parameter in bytes, including the Cause Code, Cause Length, and Cause-Specific Information fields, but not including any padding at the end of this error cause TLV.
原因长度：设置为参数大小的16位（无符号整数），以字节为单位，包括原因代码、原因长度和原因特定信息字段，但不包括此错误原因TLV末尾的任何填充。
Cause-specific Information: variable length This field carries the details of the error condition.
原因特定信息：可变长度此字段包含错误情况的详细信息。
The following subsections (Section 3.12.1 - Section 3.12.9) define specific error causes.
以下小节（第3.12.1节-第3.12.9节）定义了具体的错误原因。
This error cause is used to report an unspecified error by the sender. There is no cause specific information.
此错误原因用于报告发件人未指定的错误。没有特定原因的信息。
This error cause is used to report an unrecognized parameter. The complete, unrecognized parameter TLV is included as cause-specific information. If a message contains multiple unrecognized parameters, multiple error causes are used.
此错误原因用于报告无法识别的参数。完整的、无法识别的参数TLV包含在原因特定信息中。如果消息包含多个无法识别的参数，则会使用多个错误原因。
This error cause is used to report an unrecognized message. The unrecognized message TLV is included as cause-specific information.
此错误原因用于报告无法识别的消息。无法识别的消息TLV作为特定于原因的信息包含在内。
This error cause is used to report one or more invalid values found in a received parameter. The offending TLV that contains the invalid value(s) is included as cause-specific information.
此错误原因用于报告在收到的参数中发现的一个或多个无效值。包含无效值的违规TLV包含为原因特定信息。
This error cause is used by an ENRP server to indicate to a registering PE that the PE Identifier it chooses has already been used by another PE in the pool. There is no cause-specific information.
ENRP服务器使用此错误原因向注册PE指示其选择的PE标识符已被池中的另一个PE使用。没有特定原因的信息。
This error cause is used by an ENRP server to indicate to a registering PE that the pool policy it chooses does not match the overall policy of the pool. A Pool Member Selection Policy TLV (see Section 3.8) that indicates the overall pool policy is included as cause-specific information.
ENRP服务器使用此错误原因向注册PE指示其选择的池策略与池的总体策略不匹配。一个池成员选择策略TLV（见第3.8节），表明整个池策略作为特定于原因的信息包括在内。
This error cause is used to indicate that the sender does not have certain resources to perform a requested function. There is no cause specific information.
此错误原因用于指示发送方没有某些资源来执行请求的功能。没有特定原因的信息。
This error cause is used by an ENRP server to indicate to a registering PE that the User Transport it chooses does not match the overall user transport of the pool. A Transport TLV that indicates the overall pool user transport type is included as cause-specific information.
ENRP服务器使用此错误原因向注册PE指示其选择的用户传输与池的总体用户传输不匹配。指示整个池用户传输类型的传输TLV包含为特定于原因的信息。
This error cause is used by an ENRP server to indicate to a registering PE that the Transport Use field in the User Transport it sent in its registration is inconsistent to the pool's overall data/ control channel configuration. There is no cause-specific information.
ENRP服务器使用此错误原因向注册PE指示其在注册中发送的用户传输中的传输使用字段与池的总体数据/控制通道配置不一致。没有特定原因的信息。
This error cause is used by any endpoint to indicate a rejection of a request due to a failure in security credentials or authorizations.
任何端点都会使用此错误原因来指示由于安全凭据或授权失败而拒绝请求。
This error cause is used by an ENRP server to indicate to a PE or PU that the requested pool is unknown by the server. There is no cause-specific information.
ENRP服务器使用此错误原因向PE或PU指示服务器未知请求的池。没有特定原因的信息。
This parameter defines a TLV that carries a Cookie.
此参数定义携带Cookie的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 = 0xd | Length=variable |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: :
: Cookie :
: :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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 = 0xd | Length=variable |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: :
: Cookie :
: :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Length: 16 bits (unsigned integer) Indicates the entire length of the parameter in number of bytes, including the Type, Length, and Cookie.
长度：16位（无符号整数）以字节数表示参数的整个长度，包括类型、长度和Cookie。
Cookie: variable length The Cookie is an arbitrary byte string of (Length - 4) bytes.
Cookie：可变长度Cookie是（长度-4）字节的任意字节字符串。
This parameter defines a TLV that carries a PE Identifier.
此参数定义携带PE标识符的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 = 0xe | Length=0x8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| PE Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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 = 0xe | Length=0x8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| PE Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
PE Identifier: 32 bits (unsigned integer) Uniquely identifies the PE in the pool. The PE picks its identifier when it starts up. See [RFC5352] for recommendations on PE identifier generation.
PE标识符：32位（无符号整数）唯一标识池中的PE。PE在启动时选择其标识符。有关PE标识符生成的建议，请参阅[RFC5352]。
This parameter defines a TLV that carries a PE Checksum.
此参数定义携带PE校验和的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 = 0xf | Length=0x6 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| PE Checksum | Padding |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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 = 0xf | Length=0x6 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| PE Checksum | Padding |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
PE Checksum: 16 bits (unsigned integer) An overall checksum of all PEs in the current handlespace owned by an ENRP server (which is normally the sender of this TLV). The definition and calculation of this checksum is defined in [RFC5353].
PE校验和：16位（无符号整数）ENRP服务器（通常是此TLV的发送方）拥有的当前handlespace中所有PE的总校验和。[RFC5353]中定义了该校验和的定义和计算。
This parameter defines a TLV that carries opaque transport information.
此参数定义承载不透明传输信息的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 = 0x10 | Length=variable |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: :
: Opaque Transport Data :
: :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 0x10 | Length=variable |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: :
: Opaque Transport Data :
: :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Length: 16 bits (unsigned integer) Indicates the entire length of the parameter in number of bytes, including the Type, Length, and Opaque Transport Data.
长度：16位（无符号整数）以字节数表示参数的整个长度，包括类型、长度和不透明传输数据。
Opaque Transport Data: variable length The Opaque Transport Data is an arbitrary byte string of (Length - 4) bytes.
不透明传输数据：可变长度不透明传输数据是（长度-4）字节的任意字节字符串。
The figure below illustrates the common format for all ASAP and ENRP messages. Each message is formatted with a Message Type field, a message-specific Flag field, a Message Length field, and a Value field.
下图说明了所有ASAP和ENRP消息的通用格式。每个消息都使用消息类型字段、消息特定标志字段、消息长度字段和值字段进行格式化。
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Message Type | Msg Flags | Message Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: :
: Message 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Message Type | Msg Flags | Message Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: :
: Message Value :
: :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Message Type: 8 bits (unsigned integer) This field identifies the type of information contained in the Message Value field. It takes a value from 0 to 254. The value of 255 is reserved for future use as an extension field. Message Types are encoded such that the two bits of the highest order specify the action that must be taken if the message receiver does not recognize the Message Type.
消息类型：8位（无符号整数）此字段标识消息值字段中包含的信息类型。它的值从0到254。值255保留为将来用作扩展字段。对消息类型进行编码，以便最高顺序的两个位指定在消息接收方无法识别消息类型时必须采取的操作。
00 Stop processing this message and discard it.
00停止处理此消息并放弃它。
01 Stop processing this message and discard it, and report the unrecognized message in an 'Unrecognized Message' error (see Section 3.12.3).
01停止处理此消息并放弃它，并在“unrecognized message”（未识别消息）错误中报告未识别的消息（参见第3.12.3节）。
10 Reserved.
10保留。
11 Reserved.
11保留。
Message Flags: 8 bits The usage of these bits depends on the message type, as given by the Message Type. Unless otherwise specified, they are set to zero on transmit and ignored on receipt.
消息标志：8位这些位的使用取决于消息类型，如消息类型所示。除非另有规定，否则它们在传输时被设置为零，在接收时被忽略。
Message Length: 16 bits (unsigned integer) This value represents the size of the message in bytes, including the Message Type, Message Flags, Message Length, and Message Value fields. Therefore, if the Message Value field is zero length, the Length field will be set to 4. Note, the value in the Message Length field will NOT cover any padding at the end of this message.
消息长度：16位（无符号整数）此值表示消息的大小（字节），包括消息类型、消息标志、消息长度和消息值字段。因此，如果消息值字段的长度为零，则长度字段将设置为4。注意，“消息长度”字段中的值不会覆盖此消息末尾的任何填充。
Message Value: variable length The Message Value field contains the actual information to be transferred in the message. The usage and format of this field is dependent on the Message Type. The total length of a message (including Type, Length, and Value fields) MUST be a multiple of 4 bytes. If the length of the message is not a multiple of 4 bytes, the sender MUST pad the
消息值：可变长度消息值字段包含要在消息中传输的实际信息。此字段的用法和格式取决于消息类型。消息的总长度（包括类型、长度和值字段）必须是4字节的倍数。如果消息长度不是4字节的倍数，则发送方必须填充
message with all zero bytes and this padding is not included in the Message Length field. The sender should never pad with more than 3 bytes. The receiver MUST ignore the padding bytes.
消息长度字段中不包括所有零字节且此填充的消息。发送方的填充长度不应超过3个字节。接收器必须忽略填充字节。
This document (RFC 5354) is the reference for all registrations described in this section. All registrations have been listed on the RSerPool Parameters page.
本文件（RFC 5354）是本节所述所有注册的参考文件。所有注册都已列在RSerPool参数页面上。
RSerPool Parameter Types are maintained by IANA. Thirteen initial values have been assigned by IANA, as described in Table 1. IANA created a new table, "RSerPool Parameter Types":
RSerPool参数类型由IANA维护。IANA分配了13个初始值，如表1所示。IANA创建了一个新表“RSerPool参数类型”：
+------------+------------------------------+
| Value | Parameter Type |
+------------+------------------------------+
| 0x0 | (Reserved by IETF) |
| 0x1 | IPv4 Address |
| 0x2 | IPv6 Address |
| 0x3 | DCCP Transport |
| 0x4 | SCTP Transport |
| 0x5 | TCP Transport |
| 0x6 | UDP Transport |
| 0x7 | UDP-Lite |
| 0x8 | Pool Member Selection Policy |
| 0x9 | Pool Handle |
| 0xa | Pool Element |
| 0xb | Server Information |
| 0xc | Operation Error |
| 0xd | Cookie |
| 0xe | PE Identifier |
| 0xf | PE Checksum |
| 0x10 | Opaque Transport |
| 0xffffffff | IETF-defined extensions |
| others | (Reserved by IETF) |
+------------+------------------------------+
+------------+------------------------------+
| Value | Parameter Type |
+------------+------------------------------+
| 0x0 | (Reserved by IETF) |
| 0x1 | IPv4 Address |
| 0x2 | IPv6 Address |
| 0x3 | DCCP Transport |
| 0x4 | SCTP Transport |
| 0x5 | TCP Transport |
| 0x6 | UDP Transport |
| 0x7 | UDP-Lite |
| 0x8 | Pool Member Selection Policy |
| 0x9 | Pool Handle |
| 0xa | Pool Element |
| 0xb | Server Information |
| 0xc | Operation Error |
| 0xd | Cookie |
| 0xe | PE Identifier |
| 0xf | PE Checksum |
| 0x10 | Opaque Transport |
| 0xffffffff | IETF-defined extensions |
| others | (Reserved by IETF) |
+------------+------------------------------+
Requests to register an RSerPool Parameter Type in this table should be sent to IANA. The number must be unique. The "Specification Required" policy of [RFC5226] MUST be applied.
在此表中注册RSerPool参数类型的请求应发送给IANA。号码必须是唯一的。必须采用[RFC5226]的“要求规范”政策。
RSerPool Error Causes are maintained by IANA. Eleven initial values have been assigned by IANA, as described in Table 2. IANA created a new table, "RSerPool Error Causes":
RSerPool错误原因由IANA维护。IANA分配了11个初始值，如表2所述。IANA创建了一个新表“RSerPool错误原因”：
+------------------+-----------------------------------------+
| Cause Code Value | Cause Code |
+------------------+-----------------------------------------+
| 0x0 | Unspecified Error |
| 0x1 | Unrecognized Parameter |
| 0x2 | Unrecognized Message |
| 0x3 | Invalid Values |
| 0x4 | Non-Unique PE Identifier |
| 0x5 | Inconsistent Pooling Policy |
| 0x6 | Lack of Resources |
| 0x7 | Inconsistent Transport Type |
| 0x8 | Inconsistent Data/Control Configuration |
| 0x9 | Unknown Pool Handle |
| 0xa | Rejected Due to Security Considerations |
| others | (Reserved by IETF) |
+------------------+-----------------------------------------+
+------------------+-----------------------------------------+
| Cause Code Value | Cause Code |
+------------------+-----------------------------------------+
| 0x0 | Unspecified Error |
| 0x1 | Unrecognized Parameter |
| 0x2 | Unrecognized Message |
| 0x3 | Invalid Values |
| 0x4 | Non-Unique PE Identifier |
| 0x5 | Inconsistent Pooling Policy |
| 0x6 | Lack of Resources |
| 0x7 | Inconsistent Transport Type |
| 0x8 | Inconsistent Data/Control Configuration |
| 0x9 | Unknown Pool Handle |
| 0xa | Rejected Due to Security Considerations |
| others | (Reserved by IETF) |
+------------------+-----------------------------------------+
Requests to register an RSerPool Error Cause in this table should be sent to IANA. The number must be unique. The "Specification Required" policy of [RFC5226] MUST be applied.
在此表中注册RSerPool错误原因的请求应发送至IANA。号码必须是唯一的。必须采用[RFC5226]的“要求规范”政策。
This document contains common parameter formats only. As such, it specifies no new security constraints on either ENRP or ASAP. Details on ENRP and ASAP security constraints are addressed in [RFC5353] and [RFC5352].
本文档仅包含常用参数格式。因此，它没有在ENRP或ASAP上指定新的安全约束。有关ENRP和ASAP安全约束的详细信息，请参见[RFC5353]和[RFC5352]。
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2119]Bradner，S.，“RFC中用于表示需求水平的关键词”，BCP 14，RFC 2119，1997年3月。
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA Considerations Section in RFCs", BCP 26, RFC 5226, May 2008.
[RFC5226]Narten，T.和H.Alvestrand，“在RFCs中编写IANA注意事项部分的指南”，BCP 26，RFC 5226，2008年5月。
[RFC5352] Stewart, R., Xie, Q., Stillman, M., and M. Tuexen, "Aggregate Server Access Protocol (ASAP)", RFC 5352, September 2008.
[RFC5352]Stewart，R.，Xie，Q.，Stillman，M.，和M.Tuexen，“聚合服务器访问协议（ASAP）”，RFC 53522008年9月。
[RFC5353] Xie, Q., Stewart, R., Stillman, M., Tuexen, M., and A. Silverton, "Endpoint Handlespace Redundancy Protocol (ENRP)", RFC 5353, September 2008.
[RFC5353]Xie，Q.，Stewart，R.，Stillman，M.，Tuexen，M.，和A.Silverton，“端点Handlespace冗余协议（ENRP）”，RFC 53532008年9月。
[RFC5356] Dreibholz, T. and M. Tuexen, "Reliable Server Pooling Policies", RFC 5356, September 2008.
[RFC5356]Dreibholz，T.和M.Tuexen，“可靠的服务器池策略”，RFC 5356，2008年9月。
Authors' Addresses
作者地址
Randall R. Stewart The Resource Group 1700 Pennsylvania Ave NW Suite 560 Washington, DC 20006 USA
Randall R.Stewart资源集团美国华盛顿特区宾夕法尼亚大道西北1700号560室，邮编：20006
Phone: EMail: randall.stewart@trgworld.com
电话：电子邮件：randall。stewart@trgworld.com
Qiaobing Xie The Resource Group 1700 Pennsylvania Ave NW Suite 560 Washington, D.C., 20006 USA
美国华盛顿特区宾夕法尼亚大道西北1700号560室，邮编20006
Phone: +1 224-465-5954
EMail: Qiaobing.Xie@gmail.com
Phone: +1 224-465-5954
EMail: Qiaobing.Xie@gmail.com
Maureen Stillman Nokia 1167 Peachtree Ct. Naperville, IL 60540 USA
Maureen Stillman诺基亚1167桃树Ct。美国伊利诺伊州纳珀维尔60540
EMail: maureen.stillman@nokia.com
EMail: maureen.stillman@nokia.com
Michael Tuexen Muenster Univ. of Applied Sciences Stegerwaldstr. 39 48565 Steinfurt Germany
Michael Tuexen Muenster应用科学大学Stegerwaldstr。39 48565德国斯坦福德
EMail: tuexen@fh-muenster.de
EMail: tuexen@fh-muenster.de
Full Copyright Statement
完整版权声明
Copyright (C) The IETF Trust (2008).
版权所有（C）IETF信托基金（2008年）。
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, THE IETF TRUST 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.
本文件及其包含的信息以“原样”为基础提供，贡献者、他/她所代表或赞助的组织（如有）、互联网协会、IETF信托基金和互联网工程任务组不承担任何明示或暗示的担保，包括但不限于任何保证，即使用本文中的信息不会侵犯任何权利，或对适销性或特定用途适用性的任何默示保证。
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.