draft-ietf-rserpool-common-param-18.txt   rfc5354.txt 
Network Working Group R. Stewart Network Working Group R. Stewart
Internet-Draft The Resource Group Request for Comments: 5354 Q. Xie
Intended status: Experimental Q. Xie Category: Experimental The Resource Group
Expires: January 15, 2009
M. Stillman M. Stillman
Nokia Nokia
M. Tuexen M. Tuexen
Muenster Univ. of Applied Sciences Muenster Univ. of Applied Sciences
July 14, 2008 September 2008
Aggregate Server Access Protocol (ASAP) and Endpoint Handlespace
Redundancy Protocol (ENRP) Parameters
draft-ietf-rserpool-common-param-18.txt
Status of this Memo
By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-
Drafts.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at Aggregate Server Access Protocol (ASAP) and
http://www.ietf.org/ietf/1id-abstracts.txt. Endpoint Handlespace Redundancy Protocol (ENRP) Parameters
The list of Internet-Draft Shadow Directories can be accessed at Status of This Memo
http://www.ietf.org/shadow.html.
This Internet-Draft will expire on January 15, 2009. 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 Abstract
This document details the parameters of the Aggregate Server Access This document details the parameters of the Aggregate Server Access
Protocol (ASAP) and Endpoint Handlespace Redundancy Protocol (ENRP) Protocol (ASAP) and Endpoint Handlespace Redundancy Protocol (ENRP)
protocols defined within the Reliable Server Pooling (RSerPool) defined within the Reliable Server Pooling (RSerPool) architecture.
architecture.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 1. Introduction ....................................................3
1.1. Conventions . . . . . . . . . . . . . . . . . . . . . . . 4 1.1. Conventions ................................................3
2. Parameters in General . . . . . . . . . . . . . . . . . . . . 5 2. Parameters in General ...........................................3
3. ENRP-ASAP Common Parameters . . . . . . . . . . . . . . . . . 6 3. ENRP-ASAP Common Parameters .....................................3
3.1. IPv4 Address Parameter . . . . . . . . . . . . . . . . . . 8 3.1. IPv4 Address Parameter .....................................6
3.2. IPv6 Address Parameter . . . . . . . . . . . . . . . . . . 8 3.2. IPv6 Address Parameter .....................................6
3.3. DCCP Transport Parameter . . . . . . . . . . . . . . . . . 9 3.3. DCCP Transport Parameter ...................................7
3.4. SCTP Transport Parameter . . . . . . . . . . . . . . . . . 9 3.4. SCTP Transport Parameter ...................................8
3.5. TCP Transport Parameter . . . . . . . . . . . . . . . . . 10 3.5. TCP Transport Parameter ....................................9
3.6. UDP Transport Parameter . . . . . . . . . . . . . . . . . 11 3.6. UDP Transport Parameter ....................................9
3.7. UDP-Lite Transport Parameter . . . . . . . . . . . . . . . 12 3.7. UDP-Lite Transport Parameter ..............................10
3.8. Pool Member Selection Policy Parameter . . . . . . . . . . 13 3.8. Pool Member Selection Policy Parameter ....................11
3.9. Pool Handle Parameter . . . . . . . . . . . . . . . . . . 13 3.9. Pool Handle Parameter .....................................12
3.10. Pool Element Parameter . . . . . . . . . . . . . . . . . . 14 3.10. Pool Element Parameter ...................................12
3.11. Server Information Parameter . . . . . . . . . . . . . . . 15 3.11. Server Information Parameter .............................13
3.12. Operation Error Parameter . . . . . . . . . . . . . . . . 16 3.12. Operation Error Parameter ................................14
3.12.1. Unspecified Error . . . . . . . . . . . . . . . . . . 17 3.12.1. Unspecified Error .................................15
3.12.2. Unrecognized Parameter Error . . . . . . . . . . . . 18 3.12.2. Unrecognized Parameter Error ......................15
3.12.3. Unrecognized Message Error . . . . . . . . . . . . . 18 3.12.3. Unrecognized Message Error ........................15
3.12.4. Invalid Values Error . . . . . . . . . . . . . . . . 18 3.12.4. Invalid Values Error ..............................16
3.12.5. Non-unique PE Identifier Error . . . . . . . . . . . 18 3.12.5. Non-Unique PE Identifier Error ....................16
3.12.6. Inconsistent Pool Policy Error . . . . . . . . . . . 18 3.12.6. Inconsistent Pool Policy Error ....................16
3.12.7. Lack of Resources Error . . . . . . . . . . . . . . . 18 3.12.7. Lack of Resources Error ...........................16
3.12.8. Inconsistent Transport Type Error . . . . . . . . . . 18 3.12.8. Inconsistent Transport Type Error .................16
3.12.9. Inconsistent Data/Control Configuration Error . . . . 19 3.12.9. Inconsistent Data/Control Configuration Error .....16
3.12.10. Rejected due to security considerations . . . . . . . 19 3.12.10. Rejected Due to Security Considerations ..........16
3.12.11. Unknown Pool Handle Error . . . . . . . . . . . . . . 19 3.12.11. Unknown Pool Handle Error ........................17
3.13. Cookie Parameter . . . . . . . . . . . . . . . . . . . . . 19 3.13. Cookie Parameter .........................................17
3.14. PE Identifier Parameter . . . . . . . . . . . . . . . . . 19 3.14. PE Identifier Parameter ..................................17
3.15. PE Checksum Parameter . . . . . . . . . . . . . . . . . . 20 3.15. PE Checksum Parameter ....................................18
3.16. Opaque Transport Parameter . . . . . . . . . . . . . . . . 20 3.16. Opaque Transport Parameter ...............................18
4. Common Message Formats . . . . . . . . . . . . . . . . . . . . 22 4. Common Message Formats .........................................18
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 24 5. IANA Considerations ............................................20
5.1. A New Table for RSerPool Parameter Types . . . . . . . . . 24 5.1. A New Table for RSerPool Parameter Types ..................20
5.2. A New Table for RSerPool Error Causes . . . . . . . . . . 26 5.2. A New Table for RSerPool Error Causes .....................21
6. Security Considerations . . . . . . . . . . . . . . . . . . . 27 6. Security Considerations ........................................21
7. Normative References . . . . . . . . . . . . . . . . . . . . . 28 7. Normative References ...........................................21
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 29
Intellectual Property and Copyright Statements . . . . . . . . . . 30
1. Introduction 1. Introduction
Aggregate Server Access Protocol (ASAP) [I-D.ietf-rserpool-asap] in The Aggregate Server Access Protocol (ASAP) [RFC5352], in conjunction
conjunction with the Endpoint Handlespace Redundancy Protocol (ENRP) with the Endpoint Handlespace Redundancy Protocol (ENRP) [RFC5353],
[I-D.ietf-rserpool-enrp] provides a high availability data transfer provides a high-availability, data-transfer mechanism over IP
mechanism over IP networks. networks.
Both protocols work together and so share many common parameters used Both protocols work together and so share many common parameters used
in message formats. This document details the common message in message formats. This document details the common message
parameters shared between the two protocols. This document provides parameters shared between the two protocols. This document provides
parameter formats only, for procedures and message composition please parameter formats only; for procedures and message composition,
refer to the respective [I-D.ietf-rserpool-asap] and please refer to the respective [RFC5352] and [RFC5353] documents.
[I-D.ietf-rserpool-enrp] documents.
1.1. Conventions 1.1. Conventions
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in [RFC2119].
2. Parameters in General 2. Parameters in General
All parameters described below MUST be in Network Byte Order (a.k.a. All parameters described below MUST be in network byte order (aka Big
Big Endian, i.e., the most significant byte first) during Endian, i.e., the most significant byte first) during transmission.
transmission.
Please note that messages in both ENRP and ASAP are often composed of Please note that messages in both ENRP and ASAP are often composed of
multiple parameters. These parameters may also be nested. In such a multiple parameters. These parameters may also be nested. In such a
case a nested parameter will include the length of the padding case, a nested parameter will include the length of the padding
between the nested parameters but not the last padding. between the nested parameters but not the last padding.
3. ENRP-ASAP Common Parameters 3. ENRP-ASAP Common Parameters
Parameters are defined in the following Type-Length-Value (TLV) Parameters are defined in the following Type-Length-Value (TLV)
format: format:
0 1 2 3 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 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 6, line 20 skipping to change at page 4, line 4
0 1 2 3 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 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 Type | Parameter Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: : : :
: Parameter Value : : Parameter Value :
: +-------------------------------: : +-------------------------------:
: | Padding : : | Padding :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Parameter Type: 16 bits (unsigned integer) Parameter Type: 16 bits (unsigned integer)
The Type field is a 16 bit identifier of the type of parameter. The Type field is a 16-bit identifier of the type of parameter.
It takes a value of 0 to 65534. It takes a value of 0 to 65534.
The value of 65535 is reserved for IETF-defined extensions. The value of 65535 is reserved for IETF-defined extensions.
Values other than those defined in specific ENRP parameter Values, other than those defined in the specific ENRP parameter
description are reserved by IETF. (Additional types, when needed, description, are reserved by IETF. (Additional types, when
will be defined in the future through appropriate IETF/IANA needed, will be defined in the future through appropriate IETF/
procedures.) IANA procedures.)
The Parameter Types are encoded such that the highest-order two The Parameter Types are encoded such that the two bits of the
bits specify the action that must be taken if the processing highest-order specify the action that must be taken if the
endpoint does not recognize the Parameter Type. processing endpoint does not recognize the Parameter Type.
00 Stop processing this ENRP or ASAP message and discard it, do 00 Stop processing this ENRP or ASAP message and discard it; do
not process any further parameters within it. not process any further parameters within it.
01 Stop processing this ENRP or ASAP message and discard it, do 01 Stop processing this ENRP or ASAP message and discard it; do
not process any further parameters within it, and report the not process any further parameters within it, and report the
unrecognized parameter in an 'Unrecognized Parameter' error unrecognized parameter in an 'Unrecognized Parameter' error
(see Section 3.12). (see Section 3.12).
10 Skip this parameter and continue processing. 10 Skip this parameter and continue processing.
11 Skip this parameter and continue processing, but report the 11 Skip this parameter and continue processing, but report the
unrecognized parameter in an 'Unrecognized Parameter' error unrecognized parameter in an 'Unrecognized Parameter' error
(see Section 3.12). (see Section 3.12).
The values of parameter types are defined as follows: The values of parameter types are defined as follows:
+------------+------------------------------+ +-----------------+------------------------------+
| Value | Parameter Type | | Value | Parameter Type |
+------------+------------------------------+ +-----------------+------------------------------+
| 0x0 | (reserved by IETF) | | 0x0 | (Reserved by IETF) |
| | |
| 0x1 | IPv4 Address | | 0x1 | IPv4 Address |
| | |
| 0x2 | IPv6 Address | | 0x2 | IPv6 Address |
| | |
| 0x3 | DCCP Transport | | 0x3 | DCCP Transport |
| | |
| 0x4 | SCTP Transport | | 0x4 | SCTP Transport |
| | |
| 0x5 | TCP Transport | | 0x5 | TCP Transport |
| | |
| 0x6 | UDP Transport | | 0x6 | UDP Transport |
| | |
| 0x7 | UDP-Lite | | 0x7 | UDP-Lite |
| | |
| 0x8 | Pool Member Selection Policy | | 0x8 | Pool Member Selection Policy |
| | |
| 0x9 | Pool Handle | | 0x9 | Pool Handle |
| | |
| 0xa | Pool Element | | 0xa | Pool Element |
| | |
| 0xb | Server Information | | 0xb | Server Information |
| | |
| 0xc | Operation Error | | 0xc | Operation Error |
| | |
| 0xd | Cookie | | 0xd | Cookie |
| | |
| 0xe | PE Identifier | | 0xe | PE Identifier |
| | |
| 0xf | PE Checksum | | 0xf | PE Checksum |
| | |
| 0x10 | Opaque Transport | | 0x10 | Opaque Transport |
| | | | 0x11-0xfffffffe | (Available for assignment) |
| others | (reserved by IETF) |
| | |
| 0xffffffff | IETF-defined extensions | | 0xffffffff | IETF-defined extensions |
+------------+------------------------------+ +-----------------+------------------------------+
Table 1 Table 1
Parameter Length: 16 bits (unsigned integer) Parameter Length: 16 bits (unsigned integer)
The Parameter Length field contains the size of the parameter in The Parameter Length field contains the size of the parameter in
bytes, including the Parameter Type, Parameter Length, and bytes, including the Parameter Type, Parameter Length, and
Parameter Value fields. Thus, a parameter with a zero-length Parameter Value fields. Thus, a parameter with a zero-length
Parameter Value field would have a Length field of 4. Parameter Value field would have a Length field of 4.
The total length of a parameter (including Type, Parameter Length The total length of a parameter (including Type, Parameter Length
and Value fields) MUST be a multiple of 4 bytes. If the length of 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 is not a multiple of 4 bytes, the sender MUST pad
the parameter at the end (i.e., after the Parameter Value field) the parameter at the end (i.e., after the Parameter Value field)
with all zero bytes. The length of this padding is not included with all zero bytes. The length of this padding is not included
skipping to change at page 8, line 17 skipping to change at page 5, line 46
Parameter Value fields. Thus, a parameter with a zero-length Parameter Value fields. Thus, a parameter with a zero-length
Parameter Value field would have a Length field of 4. Parameter Value field would have a Length field of 4.
The total length of a parameter (including Type, Parameter Length The total length of a parameter (including Type, Parameter Length
and Value fields) MUST be a multiple of 4 bytes. If the length of 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 is not a multiple of 4 bytes, the sender MUST pad
the parameter at the end (i.e., after the Parameter Value field) the parameter at the end (i.e., after the Parameter Value field)
with all zero bytes. The length of this padding is not included with all zero bytes. The length of this padding is not included
in the Parameter Length field. A sender MUST NOT pad with more in the Parameter Length field. A sender MUST NOT pad with more
than 3 bytes. The receiver MUST ignore the padding bytes. than 3 bytes. The receiver MUST ignore the padding bytes.
Parameter Value: variable-length. Parameter Value: variable length.
The Parameter Value field contains the actual information to be The Parameter Value field contains the actual information to be
transferred in the parameter. transferred in the parameter.
Parameter Padding: variable-length. Parameter Padding: variable length.
The Parameter Padding as described above. The Parameter Padding, as described above.
3.1. IPv4 Address Parameter 3.1. IPv4 Address Parameter
This parameter defines a TLV that carries an IPv4 address. This parameter defines a TLV that carries an IPv4 address.
0 1 2 3 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 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 | | Type = 0x1 | Length = 0x8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 9, line 6 skipping to change at page 6, line 35
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 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 | | Type = 0x2 | Length = 0x14 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
| IPv6 Address | | IPv6 Address |
| | | |
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
IPv6 Address: 128 bit (unsigned integer) IPv6 Address: 128 bits (unsigned integer)
Contains an IPv6 address. It is binary encoded. Contains an IPv6 address. It is binary encoded.
3.3. DCCP Transport Parameter 3.3. DCCP Transport Parameter
This parameter defines a TLV that describes a user transport using This parameter defines a TLV that describes a user transport using
DCCP protocol. Datagram Congestion Control Protocol (DCCP).
0 1 2 3 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 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 | | Type = 0x3 | Length = variable |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| DCCP port | (reserved) | | DCCP Port | (reserved) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| DCCP service code | | DCCP Service Code |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: IPv4 or IPv6 Address : : IPv4 or IPv6 Address :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Length: 16 bits (unsigned integer) Length: 16 bits (unsigned integer)
Indicates the entire length of the parameter in number of octets, Indicates the entire length of the parameter in number of octets,
including the Type, Length, DCCP port, reserved fields, and IP including the Type, Length, DCCP port, reserved fields, and IP
address parameter. Address Parameter.
DCCP port: 16 bits (unsigned integer) DCCP Port: 16 bits (unsigned integer)
The DCCP port number signed to this DCCP user transport. The DCCP port number signed to this DCCP user transport.
DCCP service code: 32 bits (unsigned integer) DCCP Service Code: 32 bits (unsigned integer)
The DCCP service code signed to this DCCP user transport. The DCCP service code signed to this DCCP user transport.
IPv4 or IPv6 Address IPv4 or IPv6 Address
Indicates an IPv4 or IPv6 address parameter (as defined above in Indicates an IPv4 or IPv6 address parameter (as defined above in
Section 3.1 and Section 3.2) assigned to this DCCP user transport. Section 3.1 and Section 3.2) assigned to this DCCP user transport.
Unlike in an SCTP transport parameter, only one IP address Unlike in an SCTP Transport parameter, only one IP address
parameter can be present in a DCCP transport parameter. parameter can be present in a DCCP Transport parameter.
Note: A DCCP port MUST NOT be used for control information. For this Note: The DCCP Port MUST NOT be used for control information. For
reason, no Transport Use field is provided. DCCP MUST always be this reason, no Transport Use field is provided. DCCP MUST always be
treated as a "Data Only" type transport use. treated as a "Data Only" type transport use.
3.4. SCTP Transport Parameter 3.4. SCTP Transport Parameter
This parameter defines a TLV that describes a user transport using This parameter defines a TLV that describes a user transport using
SCTP protocol. Stream Control Transport Protocol (SCTP).
0 1 2 3 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 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 | | Type = 0x4 | Length = variable |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SCTP port | Transport Use | | SCTP Port | Transport Use |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: IPv4 or IPv6 Address #1 : : IPv4 or IPv6 Address #1 :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: : : :
: ... : : ... :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: IPv4 or IPv6 Address #n : : IPv4 or IPv6 Address #n :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Length: 16 bits (unsigned integer) Length: 16 bits (unsigned integer)
Indicates the entire length of the parameter in number of octets, Indicates the entire length of the parameter in number of octets,
including the Type, Length, SCTP port, reserved fields, and all IP including the Type, Length, SCTP port, reserved fields, and all IP
address parameters present. Address Parameters present.
SCTP port: 16 bits (unsigned integer) SCTP Port: 16 bits (unsigned integer)
The SCTP port number signed to this SCTP user transport. The SCTP port number signed to this SCTP user transport.
Transport use: 16 bits (unsigned integer) Transport Use: 16 bits (unsigned integer)
This field represents how the pool element intends this transport This field represents how the pool element intends this transport
address to be used. The field MUST be populated with one of the address to be used. The field MUST be populated with one of the
following values: following values:
+-------------------+--------+ +-------------------+--------+
| Type | Value | | Type | Value |
+-------------------+--------+ +-------------------+--------+
| DATA ONLY | 0x0000 | | DATA ONLY | 0x0000 |
| | |
| DATA plus CONTROL | 0x0001 | | DATA plus CONTROL | 0x0001 |
+-------------------+--------+ +-------------------+--------+
IPv4 or IPv6 Address #1 - #n IPv4 or IPv6 Address #1 - #n
Each indicates an IPv4 or IPv6 address parameter (as defined above Each indicates an IPv4 or IPv6 address parameter (as defined above
in Section 3.1 and Section 3.2) assigned to this SCTP user in Section 3.1 and Section 3.2) assigned to this SCTP user
transport. An SCTP Transport parameter may have a mixed list of transport. An SCTP Transport parameter may have a mixed list of
IPv4 and IPv6 addresses and at least one IP address parameter MUST IPv4 and IPv6 addresses and at least one IP address parameter MUST
be present in an SCTP transport parameter. be present in an SCTP Transport parameter.
3.5. TCP Transport Parameter 3.5. TCP Transport Parameter
This parameter defines a TLV that describes a user transport using This parameter defines a TLV that describes a user transport using
TCP protocol. TCP protocol.
0 1 2 3 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 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 | | Type = 0x5 | Length = variable |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| TCP port | (reserved) | | TCP Port | (reserved) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: IPv4 or IPv6 Address : : IPv4 or IPv6 Address :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Length: 16 bits (unsigned integer) Length: 16 bits (unsigned integer)
Indicates the entire length of the parameter in number of octets, Indicates the entire length of the parameter in number of octets,
including the Type, Length, TCP port, reserved fields, and IP including the Type, Length, TCP port, reserved fields, and IP
address parameter. Address Parameter.
TCP port: 16 bits (unsigned integer) TCP Port: 16 bits (unsigned integer)
The TCP port number signed to this TCP user transport. The TCP port number signed to this TCP user transport.
IPv4 or IPv6 Address IPv4 or IPv6 Address
Indicates an IPv4 or IPv6 address parameter (as defined above in Indicates an IPv4 or IPv6 address parameter (as defined above in
Section 3.1 and Section 3.2) assigned to this TCP user transport. Section 3.1 and Section 3.2) assigned to this TCP user transport.
Unlike in an SCTP transport parameter, only one IP address Unlike in an SCTP Transport parameter, only one IP Address
parameter can be present in a TCP transport parameter. parameter can be present in a TCP Transport parameter.
Note: A TCP port MUST NOT be used for control information. For this Note: The TCP Port MUST NOT be used for control information. For
reason, no Transport Use field is provided. TCP MUST always be this reason, no Transport Use field is provided. TCP MUST always be
treated as a "Data Only" type transport use. treated as a "Data Only" type transport use.
3.6. UDP Transport Parameter 3.6. UDP Transport Parameter
This parameter defines a TLV that describes a user transport using This parameter defines a TLV that describes a user transport using
UDP protocol. UDP protocol.
0 1 2 3 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 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 | | Type = 0x6 | Length = variable |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| UDP port | (reserved) | | UDP Port | (reserved) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: IPv4 or IPv6 Address : : IPv4 or IPv6 Address :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Length: 16 bits (unsigned integer) Length: 16 bits (unsigned integer)
Indicates the entire length of the parameter in number of octets, Indicates the entire length of the parameter in number of octets,
including the Type, Length, UDP port, reserved fields, and IP including the Type, Length, UDP port, reserved fields, and IP
address parameter. Address Parameter.
UDP port: 16 bits (unsigned integer) UDP Port: 16 bits (unsigned integer)
The UDP port number signed to this UDP user transport. The UDP port number signed to this UDP user transport.
IPv4 or IPv6 Address IPv4 or IPv6 Address
Indicates an IPv4 or IPv6 address parameter (as defined above in Indicates an IPv4 or IPv6 address parameter (as defined above in
Section 3.1 and Section 3.2) assigned to this UDP user transport. Section 3.1 and Section 3.2) assigned to this UDP user transport.
Unlike in an SCTP transport parameter, only one IP address Unlike in an SCTP Transport parameter, only one IP Address
parameter can be present in a UDP transport parameter. parameter can be present in a UDP Transport parameter.
Note: A UDP port MUST NOT be used for control information. For this Note: The UDP Port MUST NOT be used for control information. For
reason, no Transport Use field is provided. UDP MUST always be this reason, no Transport Use field is provided. UDP MUST always be
treated as a "Data Only" type transport use. treated as a "Data Only" type transport use.
3.7. UDP-Lite Transport Parameter 3.7. UDP-Lite Transport Parameter
This parameter defines a TLV that describes a user transport using This parameter defines a TLV that describes a user transport using
UDP-Lite protocol. UDP-Lite protocol.
0 1 2 3 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 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 | | Type = 0x7 | Length = variable |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| UDP-Lite port | (reserved) | | UDP-Lite Port | (reserved) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: IPv4 or IPv6 Address : : IPv4 or IPv6 Address :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Length: 16 bits (unsigned integer) Length: 16 bits (unsigned integer)
Indicates the entire length of the parameter in number of octets, Indicates the entire length of the parameter in number of octets,
including the Type, Length, UDP-Lite port, reserved fields, and IP including the Type, Length, UDP-Lite port, reserved fields, and IP
address parameter. Address Parameter.
UDP port: 16 bits (unsigned integer) UDP Port: 16 bits (unsigned integer)
The UDP-Lite port number signed to this UDP-Lite user transport. The UDP-Lite port number signed to this UDP-Lite user transport.
IPv4 or IPv6 Address IPv4 or IPv6 Address
Indicates an IPv4 or IPv6 address parameter (as defined above in Indicates an IPv4 or IPv6 address parameter (as defined above in
Section 3.1 and Section 3.2) assigned to this UDP-Lite user Section 3.1 and Section 3.2) assigned to this UDP-Lite user
transport. Unlike in an SCTP transport parameter, only one IP transport. Unlike in an SCTP Transport parameter, only one IP
address parameter can be present in a UDP-Lite transport address parameter can be present in a UDP-Lite transport
parameter. parameter.
Note: A UDP-Lite port MUST NOT be used for control information. For Note: The UDP-Lite Port MUST NOT be used for control information.
this reason, no Transport Use field is provided. UDP-Lite MUST For this reason, no Transport Use field is provided. UDP-Lite MUST
always be treated as a "Data Only" type transport use. always be treated as a "Data Only" type transport use.
3.8. Pool Member Selection Policy Parameter 3.8. Pool Member Selection Policy Parameter
This parameter defines a pool member selection policy. RSerPool This parameter defines a pool member selection policy. RSerPool
supports multiple pool member selection policies and also allows supports multiple pool member selection policies and also allows the
definition of new selection policies in the future. definition of new selection policies in the future.
The enforcement rules and handling procedures of all the policies are The enforcement rules and handling procedures of all the policies are
defined in [I-D.ietf-rserpool-asap]. defined in [RFC5352].
All pool member selection policies, both present and future, MUST use All pool member selection policies, both present and future, MUST use
the following general parameter format: the following general parameter format:
0 1 2 3 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 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 | | Type = 0x8 | Length = variable |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Policy Type | | Policy Type |
skipping to change at page 13, line 36 skipping to change at page 11, line 40
Length: 16 bits (unsigned integer) Length: 16 bits (unsigned integer)
Indicates the entire length of the parameter in number of octets, Indicates the entire length of the parameter in number of octets,
including the Type, Length, Policy Type, and the Policy-specific including the Type, Length, Policy Type, and the Policy-specific
Data fields. Data fields.
Note, the Length field value will NOT include any padding at the Note, the Length field value will NOT include any padding at the
end of the parameter. end of the parameter.
Policy Type: 32 bits (unsigned integer) Policy Type: 32 bits (unsigned integer)
Specifies the type of selection policy. The values are defined in Specifies the type of selection policy. The values are defined in
[I-D.ietf-rserpool-policies]. [RFC5356].
Policy-specific Data: Policy-specific Data:
The structure and fields for each presently defined policy type The structure and fields for each presently defined policy type
are described in detail in [I-D.ietf-rserpool-policies]. are described in detail in [RFC5356].
3.9. Pool Handle Parameter 3.9. Pool Handle Parameter
This parameter holds a pool handle. This parameter holds a pool handle.
0 1 2 3 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 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 | | Type = 0x9 | Length=variable |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: : : :
: Pool Handle : : Pool Handle :
: : : :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Length: 16 bits (unsigned integer) Length: 16 bits (unsigned integer)
Indicates the entire length of the parameter in number of octets, Indicates the entire length of the parameter in number of octets,
including the Type, Length, and Pool Handle string. including the Type, Length, and Pool Handle string.
Note, the value in Length field will NOT cover any padding at the Note, the value in the Length field will NOT cover any padding at
end of the parameter. the end of the parameter.
Pool Handle Pool Handle
defined as a sequence of (Length - 4) bytes. Defined as a sequence of (Length - 4) bytes.
3.10. Pool Element Parameter 3.10. Pool Element Parameter
This parameter is used in multiple ENRP messages to represent an ASAP This parameter is used in multiple ENRP messages to represent an ASAP
endpoint (i.e., a PE in a pool) and the associated information, such endpoint (i.e., a Pool Element (PE) in a pool) and the associated
as its transport address, selection policy, and other operational or information, such as its transport address, selection policy, and
status information of the PE. other operational or status information of the PE.
0 1 2 3 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 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 | | Type = 0xa | Length=variable |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| PE Identifier | | PE Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Home ENRP Server Identifier | | Home ENRP Server Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 15, line 8 skipping to change at page 13, line 8
: User Transport param : : User Transport param :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: Member Selection Policy param : : Member Selection Policy param :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: ASAP Transport param : : ASAP Transport param :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Length: 16 bits (unsigned integer) Length: 16 bits (unsigned integer)
Indicates the entire length of the parameter in number of octets, Indicates the entire length of the parameter in number of octets,
including the Type, Length, PE Identifier, Registration Life, User including the Type, Length, PE Identifier, Registration Life, User
Transport, and Member Selection Policy parameters. Transport, and Member Selection Policy parameters.
Note, the value in Length field will NOT cover any padding at the Note, the value in the Length field will NOT cover any padding at
end of this Pool Element parameter. the end of this Pool Element parameter.
PE Identifier: 32 bits (unsigned integer) PE Identifier: 32 bits (unsigned integer)
Uniquely identifies the PE in the pool. The PE picks its Uniquely identifies the PE in the pool. The PE picks its
identifier when it starts up. identifier when it starts up.
Home ENRP Server Identifier: 32 bits (unsigned integer) Home ENRP Server Identifier: 32 bits (unsigned integer)
Indicates the current home ENRP server of this PE. Set to all 0's Indicates the current Home ENRP server of this PE. Set to all 0s
if the PE's home ENRP server is undetermined. if the PE's Home ENRP server is undetermined.
Registration Life: 32 bits (signed integer) Registration Life: 32 bits (signed integer)
Indicates the life time of the registration in number of seconds. Indicates the life time of the registration in number of seconds.
A value of -1 indicates infinite life time. A value of -1 indicates infinite life time.
User Transport User Transport
This can be either an DCCP, SCTP, TCP, UDP, UDP-Lite, or Opaque 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, Transport parameter (see Section 3.3, Section 3.4, Section 3.5,
Section 3.6, Section 3.7, Section 3.16). A PE MUST have one and Section 3.6, Section 3.7, and Section 3.16). A PE MUST have one
only one User Transport. and only one User Transport.
Member Selection Policy Member Selection Policy
Contains one of the defined member selection policy parameters Contains one of the defined member selection policy parameters
(see Section 3.8). (see Section 3.8).
ASAP Transport ASAP Transport
This indicates the ASAP transport address of the PE and MUST be an This indicates the ASAP transport address of the PE and MUST be an
SCTP type transport parameter (see Section 3.4). SCTP type transport parameter (see Section 3.4).
3.11. Server Information Parameter 3.11. Server Information Parameter
skipping to change at page 16, line 6 skipping to change at page 14, line 6
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 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 | | Type = 0xb | Length=variable |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Server ID | | Server ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: Server Transport : : Server Transport :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Length: 16 bits (unsigned integer) Length: 16 bits (unsigned integer)
Indicates the entire length of the parameter in number of bytes. Indicates the entire length of the parameter in number of bytes.
Note, the value in Length field will NOT cover any padding at the Note, the value in the Length field will NOT cover any padding at
end of the parameter. the end of the parameter.
Server ID: 32 bit (unsigned integer) Server ID: 32 bits (unsigned integer)
This is the ID of the ENRP server, as defined in This is the ID of the ENRP server, as defined in [RFC5353].
[I-D.ietf-rserpool-enrp].
Server Transport: Server Transport:
This is an SCTP Transport Parameter, as defined in Section 3.4 This is an SCTP Transport Parameter, as defined in Section 3.4,
that contains the network access address(es), SCTP port number, that contains the network access address(es), SCTP port number,
etc. of the ENRP server. etc. of the ENRP server.
3.12. Operation Error Parameter 3.12. Operation Error Parameter
This parameter is used in both ENRP and ASAP for a message sender to This parameter is used in both ENRP and ASAP for a message sender to
report an error(s) to a message receiver. report an error(s) to a message receiver.
0 1 2 3 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 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 | | Type = 0xc | Length=variable |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: : : :
: one or more Error Causes : : one or more Error Causes :
: : : :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Length: 16 bits (unsigned integer) Length: 16 bits (unsigned integer)
Indicates the entire length of the parameter in number of bytes. Indicates the entire length of the parameter in number of bytes.
Note, the value in Length field will NOT cover any padding at the Note, the value in the Length field will NOT cover any padding at
end of the parameter. the end of the parameter.
Error causes are defined as variable-length parameters using the Error causes are defined as variable-length parameters using the
following format: following format:
0 1 2 3 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 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 Code | Cause Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: : : :
: Cause-specific Information : : Cause-Specific Information :
: : : :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Cause Code: 16 bits (unsigned integer) Cause Code: 16 bits (unsigned integer)
Defines the type of error condition being reported. Defines the type of error condition being reported.
+------------------+-----------------------------------------+ +------------------+-----------------------------------------+
| Cause Code Value | Cause Code | | Cause Code Value | Cause Code |
+------------------+-----------------------------------------+ +------------------+-----------------------------------------+
| 0x0 | Unspecified Error | | 0x0 | Unspecified Error |
| | |
| 0x1 | Unrecognized Parameter | | 0x1 | Unrecognized Parameter |
| | |
| 0x2 | Unrecognized Message | | 0x2 | Unrecognized Message |
| | |
| 0x3 | Invalid Values | | 0x3 | Invalid Values |
| | |
| 0x4 | Non-unique PE Identifier | | 0x4 | Non-unique PE Identifier |
| | |
| 0x5 | Inconsistent Pooling Policy | | 0x5 | Inconsistent Pooling Policy |
| | |
| 0x6 | Lack of Resources | | 0x6 | Lack of Resources |
| | |
| 0x7 | Inconsistent Transport Type | | 0x7 | Inconsistent Transport Type |
| | |
| 0x8 | Inconsistent Data/Control Configuration | | 0x8 | Inconsistent Data/Control Configuration |
| | |
| 0x9 | Unknown Pool Handle | | 0x9 | Unknown Pool Handle |
| | |
| 0xa | Rejected due to security considerations | | 0xa | Rejected due to security considerations |
| | | | 0xb -0xffff | (Available for assignment) |
| others | reserved by IETF |
+------------------+-----------------------------------------+ +------------------+-----------------------------------------+
Table 2 Table 2
Cause Length: 16 bits (unsigned integer) Cause Length: 16 bits (unsigned integer)
Set to the size of the parameter in bytes, including the Cause Set to the size of the parameter in bytes, including the Cause
Code, Cause Length, and Cause-Specific Information fields, but not Code, Cause Length, and Cause-Specific Information fields, but not
including any padding at the end of this error cause TLV. including any padding at the end of this error cause TLV.
Cause-specific Information: variable length Cause-specific Information: variable length
skipping to change at page 18, line 8 skipping to change at page 15, line 43
specific error causes. specific error causes.
3.12.1. Unspecified Error 3.12.1. Unspecified Error
This error cause is used to report an unspecified error by the This error cause is used to report an unspecified error by the
sender. There is no cause specific information. sender. There is no cause specific information.
3.12.2. Unrecognized Parameter Error 3.12.2. Unrecognized Parameter Error
This error cause is used to report an unrecognized parameter. The This error cause is used to report an unrecognized parameter. The
complete unrecognized parameter TLV is included as cause specific complete, unrecognized parameter TLV is included as cause-specific
information. If a message contains multiple unrecognized parameters, information. If a message contains multiple unrecognized parameters,
multiple error causes are used. multiple error causes are used.
3.12.3. Unrecognized Message Error 3.12.3. Unrecognized Message Error
This error cause is used to report an unrecognized message. The This error cause is used to report an unrecognized message. The
unrecognized message TLV is included as cause specific information. unrecognized message TLV is included as cause-specific information.
3.12.4. Invalid Values Error 3.12.4. Invalid Values Error
This error cause is used to report one or more invalid values found This error cause is used to report one or more invalid values found
in a received parameter. The offending TLV that contains the invalid in a received parameter. The offending TLV that contains the invalid
value(s) is included as cause specific information. value(s) is included as cause-specific information.
3.12.5. Non-unique PE Identifier Error 3.12.5. Non-Unique PE Identifier Error
This error cause is used by an ENRP server to indicate to a This error cause is used by an ENRP server to indicate to a
registering PE that the PE Identifier it chooses has already been registering PE that the PE Identifier it chooses has already been
used by another PE in the pool. There is no cause specific used by another PE in the pool. There is no cause-specific
information. information.
3.12.6. Inconsistent Pool Policy Error 3.12.6. Inconsistent Pool Policy Error
This error cause is used by an ENRP server to indicate to a 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 registering PE that the pool policy it chooses does not match the
overall policy of the pool. A Pool Member Selection Policy TLV (see overall policy of the pool. A Pool Member Selection Policy TLV (see
Section 3.8) that indicates the overall pool policy is included as Section 3.8) that indicates the overall pool policy is included as
cause specific information. cause-specific information.
3.12.7. Lack of Resources Error 3.12.7. Lack of Resources Error
This error cause is used to indicate that the sender does not have This error cause is used to indicate that the sender does not have
certain resources to perform a requested function. There is no cause certain resources to perform a requested function. There is no cause
specific information. specific information.
3.12.8. Inconsistent Transport Type Error 3.12.8. Inconsistent Transport Type Error
This error cause is used by an ENRP server to indicate to a 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 registering PE that the User Transport it chooses does not match the
overall user transport of the pool. A Transport TLV that indicates overall user transport of the pool. A Transport TLV that indicates
the overall pool user transport type is included as cause specific the overall pool user transport type is included as cause-specific
information. information.
3.12.9. Inconsistent Data/Control Configuration Error 3.12.9. Inconsistent Data/Control Configuration Error
This error cause is used by an ENRP server to indicate to a 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 registering PE that the Transport Use field in the User Transport it
sent in its registration is inconsistent to the pool's overall data/ sent in its registration is inconsistent to the pool's overall data/
control channel configuration. There is no cause specific control channel configuration. There is no cause-specific
information. information.
3.12.10. Rejected due to security considerations 3.12.10. Rejected Due to Security Considerations
This error cause is used by any endpoint to indicate a rejection of a This error cause is used by any endpoint to indicate a rejection of a
request due to a failure in security credentials or authorizations. request due to a failure in security credentials or authorizations.
3.12.11. Unknown Pool Handle Error 3.12.11. Unknown Pool Handle Error
This error cause is used by an ENRP server to indicate to a PE or PU 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 that the requested pool is unknown by the server. There is no cause-
specific information. specific information.
3.13. Cookie Parameter 3.13. Cookie Parameter
This parameter defines a TLV that carries a Cookie. This parameter defines a TLV that carries a Cookie.
0 1 2 3 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 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 | | Type = 0xd | Length=variable |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: : : :
: Cookie : : Cookie :
: : : :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Length: 16 bits (unsigned integer) Length: 16 bits (unsigned integer)
Indicates the entire length of the parameter in number of bytes, Indicates the entire length of the parameter in number of bytes,
including the Type, Length, and Cookie. including the Type, Length, and Cookie.
Cookie: variable length The Cookie is an arbitrary byte string of Cookie: variable length
(Length - 4) bytes. The Cookie is an arbitrary byte string of (Length - 4) bytes.
3.14. PE Identifier Parameter 3.14. PE Identifier Parameter
This parameter defines a TLV that carries a PE Identifier. This parameter defines a TLV that carries a PE Identifier.
0 1 2 3 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 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 | | Type = 0xe | Length=0x8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| PE Identifier | | PE Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
PE Identifier: 32 bits (unsigned integer) PE Identifier: 32 bits (unsigned integer)
Uniquely identifies the PE in the pool. The PE picks its Uniquely identifies the PE in the pool. The PE picks its
identifier when it starts up. See [I-D.ietf-rserpool-asap] for identifier when it starts up. See [RFC5352] for recommendations
recommendations on PE identifier generation. on PE identifier generation.
3.15. PE Checksum Parameter 3.15. PE Checksum Parameter
This parameter defines a TLV that carries a PE Checksum. This parameter defines a TLV that carries a PE Checksum.
0 1 2 3 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 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 | | Type = 0xf | Length=0x6 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| PE Checksum | Padding | | PE Checksum | Padding |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
PE Checksum: 16 bits (unsigned integer) PE Checksum: 16 bits (unsigned integer)
An overall checksum of all PEs in the current handlespace owned by An overall checksum of all PEs in the current handlespace owned by
an ENRP server (which is normally the sender of this TLV). The an ENRP server (which is normally the sender of this TLV). The
definition and calculation of this checksum is defined in definition and calculation of this checksum is defined in
[I-D.ietf-rserpool-enrp]. [RFC5353].
3.16. Opaque Transport Parameter 3.16. Opaque Transport Parameter
This parameter defines a TLV that carries opaque transport This parameter defines a TLV that carries opaque transport
information. information.
0 1 2 3 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 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 | | Type = 0x10 | Length=variable |
skipping to change at page 22, line 26 skipping to change at page 19, line 19
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: : : :
: Message Value : : Message Value :
: : : :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Message Type: 8 bits (unsigned integer) Message Type: 8 bits (unsigned integer)
This field identifies the type of information contained in the This field identifies the type of information contained in the
Message Value field. It takes a value from 0 to 254. The value Message Value field. It takes a value from 0 to 254. The value
of 255 is reserved for future use as an extension field. of 255 is reserved for future use as an extension field.
Message Types are encoded such that the highest-order two bits Message Types are encoded such that the two bits of the highest
specify the action that must be taken if the message receiver does order specify the action that must be taken if the message
not recognize the Message Type. receiver does not recognize the Message Type.
00 Stop processing this message and discard it. 00 Stop processing this message and discard it.
01 Stop processing this message and discard it, and report the 01 Stop processing this message and discard it, and report the
unrecognized message in an 'Unrecognized Message' error (see unrecognized message in an 'Unrecognized Message' error (see
Section 3.12.3). Section 3.12.3).
10 reserved. 10 Reserved.
11 reserved. 11 Reserved.
Message Flags: 8 bits Message Flags: 8 bits
The usage of these bits depends on the message type as given by The usage of these bits depends on the message type, as given by
the Message Type. Unless otherwise specified, they are set to the Message Type. Unless otherwise specified, they are set to
zero on transmit and are ignored on receipt. zero on transmit and ignored on receipt.
Message Length: 16 bits (unsigned integer) Message Length: 16 bits (unsigned integer)
This value represents the size of the message in bytes including This value represents the size of the message in bytes, including
the Message Type, Message Flags, Message Length, and Message Value the Message Type, Message Flags, Message Length, and Message Value
fields. Therefore, if the Message Value field is zero-length, the fields. Therefore, if the Message Value field is zero length, the
Length field will be set to 4. Length field will be set to 4.
Note, the value in Message Length field will NOT cover any padding Note, the value in the Message Length field will NOT cover any
at the end of this message. padding at the end of this message.
Message Value: variable length Message Value: variable length
The Message Value field contains the actual information to be The Message Value field contains the actual information to be
transferred in the message. The usage and format of this field is transferred in the message. The usage and format of this field is
dependent on the Message Type. dependent on the Message Type.
The total length of a message (including Type, Length and Value The total length of a message (including Type, Length, and Value
fields) MUST be a multiple of 4 bytes. If the length of the 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 message is not a multiple of 4 bytes, the sender MUST pad the
message with all zero bytes and this padding is not included in message with all zero bytes and this padding is not included in
the message length field. The sender should never pad with more the Message Length field. The sender should never pad with more
than 3 bytes. The receiver MUST ignore the padding bytes. than 3 bytes. The receiver MUST ignore the padding bytes.
5. IANA Considerations 5. IANA Considerations
[NOTE to RFC-Editor: This document (RFC 5354) is the reference for all registrations
described in this section. All registrations have been listed on the
"RFCXXXX" is to be replaced by the RFC number you assign this RSerPool Parameters page.
document.
]
This document (RFCXXX) is the reference for all registrations
described in this section. All registrations need to be listed on an
RSerPool specific page.
5.1. A New Table for RSerPool Parameter Types 5.1. A New Table for RSerPool Parameter Types
RSerPool Parameter Types have to be maintained by IANA. Thirteen RSerPool Parameter Types are maintained by IANA. Thirteen initial
initial values should be assigned by IANA as described in Table 1. values have been assigned by IANA, as described in Table 1. IANA
This requires a new table "RSerPool Parameter Types": created a new table, "RSerPool Parameter Types":
+------------+------------------------------+ +------------+------------------------------+
| Value | Parameter Type | | Value | Parameter Type |
+------------+------------------------------+ +------------+------------------------------+
| 0x0 | (reserved by IETF) | | 0x0 | (Reserved by IETF) |
| | |
| 0x1 | IPv4 Address | | 0x1 | IPv4 Address |
| | |
| 0x2 | IPv6 Address | | 0x2 | IPv6 Address |
| | |
| 0x3 | DCCP Transport | | 0x3 | DCCP Transport |
| | |
| 0x4 | SCTP Transport | | 0x4 | SCTP Transport |
| | |
| 0x5 | TCP Transport | | 0x5 | TCP Transport |
| | |
| 0x6 | UDP Transport | | 0x6 | UDP Transport |
| | |
| 0x7 | UDP-Lite | | 0x7 | UDP-Lite |
| | |
| 0x8 | Pool Member Selection Policy | | 0x8 | Pool Member Selection Policy |
| | |
| 0x9 | Pool Handle | | 0x9 | Pool Handle |
| | |
| 0xa | Pool Element | | 0xa | Pool Element |
| | |
| 0xb | Server Information | | 0xb | Server Information |
| | |
| 0xc | Operation Error | | 0xc | Operation Error |
| | |
| 0xd | Cookie | | 0xd | Cookie |
| | |
| 0xe | PE Identifier | | 0xe | PE Identifier |
| | |
| 0xf | PE Checksum | | 0xf | PE Checksum |
| | |
| 0x10 | Opaque Transport | | 0x10 | Opaque Transport |
| | |
| others | (reserved by IETF) |
| | |
| 0xffffffff | IETF-defined extensions | | 0xffffffff | IETF-defined extensions |
| others | (Reserved by IETF) |
+------------+------------------------------+ +------------+------------------------------+
For registering at IANA an RSerPool Parameter Type in this table a Requests to register an RSerPool Parameter Type in this table should
request has to be made to assign such a number. This number must be be sent to IANA. The number must be unique. The "Specification
unique. The "Specification Required" policy of [RFC5226] MUST be Required" policy of [RFC5226] MUST be applied.
applied.
5.2. A New Table for RSerPool Error Causes 5.2. A New Table for RSerPool Error Causes
RSerPool Error Causes have to be maintained by IANA. Eleven initial RSerPool Error Causes are maintained by IANA. Eleven initial values
values should be assigned by IANA as described in Table 2. This have been assigned by IANA, as described in Table 2. IANA created a
requires a new table "RSerPool Error Causes": new table, "RSerPool Error Causes":
+------------------+-----------------------------------------+ +------------------+-----------------------------------------+
| Cause Code Value | Cause Code | | Cause Code Value | Cause Code |
+------------------+-----------------------------------------+ +------------------+-----------------------------------------+
| 0x0 | Unspecified Error | | 0x0 | Unspecified Error |
| | |
| 0x1 | Unrecognized Parameter | | 0x1 | Unrecognized Parameter |
| | |
| 0x2 | Unrecognized Message | | 0x2 | Unrecognized Message |
| | |
| 0x3 | Invalid Values | | 0x3 | Invalid Values |
| | | | 0x4 | Non-Unique PE Identifier |
| 0x4 | Non-unique PE Identifier |
| | |
| 0x5 | Inconsistent Pooling Policy | | 0x5 | Inconsistent Pooling Policy |
| | |
| 0x6 | Lack of Resources | | 0x6 | Lack of Resources |
| | |
| 0x7 | Inconsistent Transport Type | | 0x7 | Inconsistent Transport Type |
| | |
| 0x8 | Inconsistent Data/Control Configuration | | 0x8 | Inconsistent Data/Control Configuration |
| | |
| 0x9 | Unknown Pool Handle | | 0x9 | Unknown Pool Handle |
| | | | 0xa | Rejected Due to Security Considerations |
| 0xa | Rejected due to security considerations | | others | (Reserved by IETF) |
| | |
| others | reserved by IETF |
+------------------+-----------------------------------------+ +------------------+-----------------------------------------+
For registering at IANA an RSerPool Error Cause in this table a Requests to register an RSerPool Error Cause in this table should be
request has to be made to assign such a number. This number must be sent to IANA. The number must be unique. The "Specification
unique. The "Specification Required" policy of [RFC5226] MUST be Required" policy of [RFC5226] MUST be applied.
applied.
6. Security Considerations 6. Security Considerations
This document contains common parameter formats only. As such it This document contains common parameter formats only. As such, it
specifies no new security constraints on either ENRP or ASAP. specifies no new security constraints on either ENRP or ASAP.
Details on ENRP and ASAP security constraints are addressed in Details on ENRP and ASAP security constraints are addressed in
[I-D.ietf-rserpool-enrp] and [I-D.ietf-rserpool-asap]. [RFC5353] and [RFC5352].
7. Normative References 7. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", BCP 26, RFC 5226, IANA Considerations Section in RFCs", BCP 26, RFC 5226,
May 2008. May 2008.
[I-D.ietf-rserpool-asap] [RFC5352] Stewart, R., Xie, Q., Stillman, M., and M. Tuexen,
Stewart, R., Xie, Q., Stillman, M., and M. Tuexen, "Aggregate Server Access Protocol (ASAP)", RFC 5352,
"Aggregate Server Access Protocol (ASAP)", September 2008.
draft-ietf-rserpool-asap-21 (work in progress), July 2008.
[I-D.ietf-rserpool-enrp] [RFC5353] Xie, Q., Stewart, R., Stillman, M., Tuexen, M., and A.
Xie, Q., Stewart, R., Stillman, M., Tuexen, M., and A.
Silverton, "Endpoint Handlespace Redundancy Protocol Silverton, "Endpoint Handlespace Redundancy Protocol
(ENRP)", draft-ietf-rserpool-enrp-21 (work in progress), (ENRP)", RFC 5353, September 2008.
July 2008.
[I-D.ietf-rserpool-policies] [RFC5356] Dreibholz, T. and M. Tuexen, "Reliable Server Pooling
Tuexen, M. and T. Dreibholz, "Reliable Server Pooling Policies", RFC 5356, September 2008.
Policies", draft-ietf-rserpool-policies-10 (work in
progress), July 2008.
Authors' Addresses Authors' Addresses
Randall R. Stewart Randall R. Stewart
The Resource Group The Resource Group
1700 Pennsylvania Ave NW 1700 Pennsylvania Ave NW
Suite 56 Suite 560
Washington, DC 20006 Washington, DC 20006
USA USA
Phone: Phone:
Email: randall.stewart@trgworld.com EMail: randall.stewart@trgworld.com
Qiaobing Xie Qiaobing Xie
The Resource Group
1700 Pennsylvania Ave NW
Suite 560
Washington, D.C., 20006
USA USA
Phone: +1 224-465-5954 Phone: +1 224-465-5954
Email: Qiaobing.Xie@gmail.org EMail: Qiaobing.Xie@gmail.com
Maureen Stillman Maureen Stillman
Nokia Nokia
127 W. State Street 1167 Peachtree Ct.
Ithaca, NY 14850 Naperville, IL 60540
USA USA
Email: maureen.stillman@nokia.com EMail: maureen.stillman@nokia.com
Michael Tuexen Michael Tuexen
Muenster Univ. of Applied Sciences Muenster Univ. of Applied Sciences
Stegerwaldstr. 39 Stegerwaldstr. 39
48565 Steinfurt 48565 Steinfurt
Germany Germany
Email: tuexen@fh-muenster.de EMail: tuexen@fh-muenster.de
Full Copyright Statement Full Copyright Statement
Copyright (C) The IETF Trust (2008). Copyright (C) The IETF Trust (2008).
This document is subject to the rights, licenses and restrictions This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors contained in BCP 78, and except as set forth therein, the authors
retain all their rights. retain all their rights.
This document and the information contained herein are provided on an This document and the information contained herein are provided on an
 End of changes. 166 change blocks. 
304 lines changed or deleted 209 lines changed or added

This html diff was produced by rfcdiff 1.35. The latest version is available from http://tools.ietf.org/tools/rfcdiff/