draft-ietf-rserpool-common-param-13.txt   draft-ietf-rserpool-common-param-14.txt 
Network Working Group R. Stewart Network Working Group R. Stewart
Internet-Draft Cisco Systems, Inc. Internet-Draft Cisco Systems, Inc.
Intended status: Experimental Q. Xie Intended status: Experimental Q. Xie
Expires: March 25, 2008 Motorola, Inc. Expires: May 20, 2008 Motorola, Inc.
M. Stillman M. Stillman
Nokia Nokia
M. Tuexen M. Tuexen
Muenster Univ. of Applied Sciences Muenster Univ. of Applied Sciences
September 22, 2007 November 17, 2007
Aggregate Server Access Protocol (ASAP) and Endpoint Handlespace Aggregate Server Access Protocol (ASAP) and Endpoint Handlespace
Redundancy Protocol (ENRP) Parameters Redundancy Protocol (ENRP) Parameters
draft-ietf-rserpool-common-param-13.txt draft-ietf-rserpool-common-param-14.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware 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 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. aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 1, line 40 skipping to change at page 1, line 40
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on March 25, 2008. This Internet-Draft will expire on May 20, 2008.
Copyright Notice Copyright Notice
Copyright (C) The IETF Trust (2007). Copyright (C) The IETF Trust (2007).
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) protocols defined within the Reliable Server Pooling (RSerPool)
architecture. architecture.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Conventions . . . . . . . . . . . . . . . . . . . . . . . 3 1.1. Conventions . . . . . . . . . . . . . . . . . . . . . . . 3
2. Parameters in General . . . . . . . . . . . . . . . . . . . . 4 2. Parameters in General . . . . . . . . . . . . . . . . . . . . 4
3. ENRP-ASAP Common Parameters . . . . . . . . . . . . . . . . . 5 3. ENRP-ASAP Common Parameters . . . . . . . . . . . . . . . . . 5
3.1. IPv4 Address Parameter . . . . . . . . . . . . . . . . . . 7 3.1. IPv4 Address Parameter . . . . . . . . . . . . . . . . . . 7
3.2. IPv6 Address Parameter . . . . . . . . . . . . . . . . . . 7 3.2. IPv6 Address Parameter . . . . . . . . . . . . . . . . . . 7
3.3. SCTP Transport Parameter . . . . . . . . . . . . . . . . . 7 3.3. DCCP Transport Parameter . . . . . . . . . . . . . . . . . 7
3.4. TCP Transport Parameter . . . . . . . . . . . . . . . . . 9 3.4. SCTP Transport Parameter . . . . . . . . . . . . . . . . . 8
3.5. UDP Transport Parameter . . . . . . . . . . . . . . . . . 9 3.5. TCP Transport Parameter . . . . . . . . . . . . . . . . . 9
3.6. Pool Member Selection Policy Parameter . . . . . . . . . . 10 3.6. UDP Transport Parameter . . . . . . . . . . . . . . . . . 10
3.7. Pool Handle Parameter . . . . . . . . . . . . . . . . . . 11 3.7. UDP-Lite Transport Parameter . . . . . . . . . . . . . . . 11
3.8. Pool Element Parameter . . . . . . . . . . . . . . . . . . 12 3.8. Pool Member Selection Policy Parameter . . . . . . . . . . 11
3.9. Server Information Parameter . . . . . . . . . . . . . . . 13 3.9. Pool Handle Parameter . . . . . . . . . . . . . . . . . . 12
3.10. Operation Error Parameter . . . . . . . . . . . . . . . . 14 3.10. Pool Element Parameter . . . . . . . . . . . . . . . . . . 13
3.10.1. Unspecified Error . . . . . . . . . . . . . . . . . . 16 3.11. Server Information Parameter . . . . . . . . . . . . . . . 14
3.10.2. Unrecognized Parameter Error . . . . . . . . . . . . 16 3.12. Operation Error Parameter . . . . . . . . . . . . . . . . 14
3.10.3. Unrecognized Message Error . . . . . . . . . . . . . 16 3.12.1. Unspecified Error . . . . . . . . . . . . . . . . . . 16
3.10.4. Invalid Values Error . . . . . . . . . . . . . . . . 16 3.12.2. Unrecognized Parameter Error . . . . . . . . . . . . 17
3.10.5. Non-unique PE Identifier Error . . . . . . . . . . . 16 3.12.3. Unrecognized Message Error . . . . . . . . . . . . . 17
3.10.6. Inconsistent Pool Policy Error . . . . . . . . . . . 16 3.12.4. Invalid Values Error . . . . . . . . . . . . . . . . 17
3.10.7. Lack of Resources Error . . . . . . . . . . . . . . . 16 3.12.5. Non-unique PE Identifier Error . . . . . . . . . . . 17
3.10.8. Inconsistent Transport Type Error . . . . . . . . . . 16 3.12.6. Inconsistent Pool Policy Error . . . . . . . . . . . 17
3.10.9. Inconsistent Data/Control Configuration Error . . . . 17 3.12.7. Lack of Resources Error . . . . . . . . . . . . . . . 17
3.10.10. Rejected due to security considerations . . . . . . . 17 3.12.8. Inconsistent Transport Type Error . . . . . . . . . . 17
3.10.11. Unknown Poor Handle Error . . . . . . . . . . . . . . 17 3.12.9. Inconsistent Data/Control Configuration Error . . . . 18
3.11. Cookie Parameter . . . . . . . . . . . . . . . . . . . . . 17 3.12.10. Rejected due to security considerations . . . . . . . 18
3.12. PE Identifier Parameter . . . . . . . . . . . . . . . . . 17 3.12.11. Unknown Poor Handle Error . . . . . . . . . . . . . . 18
3.13. PE Checksum Parameter . . . . . . . . . . . . . . . . . . 18 3.13. Cookie Parameter . . . . . . . . . . . . . . . . . . . . . 18
4. Common Message Formats . . . . . . . . . . . . . . . . . . . . 19 3.14. PE Identifier Parameter . . . . . . . . . . . . . . . . . 18
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 21 3.15. PE Checksum Parameter . . . . . . . . . . . . . . . . . . 19
5.1. A New Table for RSerPool Parameter Types . . . . . . . . . 21 4. Common Message Formats . . . . . . . . . . . . . . . . . . . . 20
5.2. A New Table for RSerPool Error Causes . . . . . . . . . . 21 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 22
6. Security Considerations . . . . . . . . . . . . . . . . . . . 23 5.1. A New Table for RSerPool Parameter Types . . . . . . . . . 22
7. Normative References . . . . . . . . . . . . . . . . . . . . . 24 5.2. A New Table for RSerPool Error Causes . . . . . . . . . . 23
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 25 6. Security Considerations . . . . . . . . . . . . . . . . . . . 25
Intellectual Property and Copyright Statements . . . . . . . . . . 26 7. Normative References . . . . . . . . . . . . . . . . . . . . . 26
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 27
Intellectual Property and Copyright Statements . . . . . . . . . . 28
1. Introduction 1. Introduction
Aggregate Server Access Protocol (ASAP) [3] in conjunction with the Aggregate Server Access Protocol (ASAP) [I-D.ietf-rserpool-asap] in
Endpoint Handlespace Redundancy Protocol (ENRP) [4] provides a high conjunction with the Endpoint Handlespace Redundancy Protocol (ENRP)
availability data transfer mechanism over IP networks. [I-D.ietf-rserpool-enrp] provides a high availability data transfer
mechanism over IP 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 please
refer to the respective ASAP [3] and ENRP [4] documents. refer to the respective [I-D.ietf-rserpool-asap] and
[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 [1]. 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 (a.k.a.
Big Endian, i.e., the most significant byte first) during Big 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
skipping to change at page 5, line 21 skipping to change at page 5, line 21
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 :
: : : :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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.
It takes a value of 0 to 65534.
The value of 65535 is reserved for IETF-defined extensions.
Values other than those defined in 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 highest-order two
bits specify the action that must be taken if the processing
endpoint does not recognize the Parameter Type.
The Type field is a 16 bit identifier of the type of parameter. It 00 Stop processing this ENRP or ASAP message and discard it, do
takes a value of 0 to 65534. not process any further parameters within it.
The value of 65535 is reserved for IETF-defined extensions. Values
other than those defined in 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 highest-order two bits
specify the action that must be taken if the processing endpoint does
not recognize the Parameter Type.
00 Stop processing this ENRP or ASAP message and discard it, do not
process any further parameters within it.
01 Stop processing this ENRP or ASAP message and discard it, do not 01 Stop processing this ENRP or ASAP message and discard it, do
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 (see unrecognized parameter in an 'Unrecognized Parameter' error
Section 3.10). (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 (see unrecognized parameter in an 'Unrecognized Parameter' error
Section 3.10). (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) +--------+------------------------------+
0x1 - IPv4 Address | 0x0 | (reserved by IETF) |
0x2 - IPv6 Address | | |
0x3 - SCTP Transport | 0x1 | IPv4 Address |
0x4 - TCP Transport | | |
0x5 - UDP Transport | 0x2 | IPv6 Address |
0x6 - Pool Member Selection Policy | | |
0x7 - Pool Handle | 0x3 | DCCP Transport |
0x8 - Pool Element | | |
0x9 - Server Information | 0x4 | SCTP Transport |
0xa - Operation Error | | |
0xb - Cookie | 0x5 | TCP Transport |
0xc - PE Identifier | | |
0xd - PE Checksum | 0x6 | UDP Transport |
| | |
others - (reserved by IETF) | 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 |
| | |
| others | (reserved by IETF) |
+--------+------------------------------+
Figure 2 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 Parameter bytes, including the Parameter Type, Parameter Length, and
Value fields. Thus, a parameter with a zero-length Parameter Value Parameter Value fields. Thus, a parameter with a zero-length
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 and Value fields) MUST be a multiple of 4 bytes. If the length of
Value fields) MUST be a multiple of 4 bytes. If the length of the the parameter is not a multiple of 4 bytes, the sender MUST pad
parameter is not a multiple of 4 bytes, the sender MUST pad the the parameter at the end (i.e., after the Parameter Value field)
parameter at the end (i.e., after the Parameter Value field) with all with all zero bytes. The length of this padding is not included
zero bytes. The length of this padding is not included in the in the Parameter Length field. A sender MUST NOT pad with more
Parameter Length field. A sender MUST NOT pad with more than 3 than 3 bytes. The receiver MUST ignore the padding bytes.
bytes. The receiver MUST ignore the padding bytes.
(Editor's note: clarify further that any padding inside in the
parameter, such as the padding in sub-param is included in the total
length)
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.
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 7, line 37 skipping to change at page 7, line 44
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 0x2 | Length = 0x14 | | Type = 0x2 | Length = 0x14 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
| IPv6 Address | | IPv6 Address |
| | | |
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
IPv6 Address: 128 bit (unsigned integer) IPv6 Address: 128 bit (unsigned integer)
Contains an IPv6 address. It is binary encoded. Contains an IPv6 address. It is binary encoded.
3.3. SCTP 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
SCTP protocol. DCCP 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 = 0x3 | Length = variable | | Type = 0x3 | Length = variable |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| DCCP 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, DCCP port, reserved fields, and IP
address parameter.
DCCP port: 16 bits (unsigned integer)
The DCCP port number signed to this DCCP user transport.
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.
Note: A 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.
3.4. SCTP Transport Parameter
This parameter defines a TLV that describes a user transport using
SCTP protocol.
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 | | 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 plus CONTROL | 0x0001 | DATA ONLY | 0x0000 |
| | |
IPv4 or IPv6 Address #1 - #n: | DATA plus CONTROL | 0x0001 |
+-------------------+--------+
Each indicates an IPv4 or IPv6 address parameter (as defined above in IPv4 or IPv6 Address #1 - #n
Section 3.1 and Section 3.2) assigned to this SCTP user transport. Each indicates an IPv4 or IPv6 address parameter (as defined above
An SCTP Transport parameter may have a mixed list of IPv4 and IPv6 in Section 3.1 and Section 3.2) assigned to this SCTP user
addresses and at least one IP address parameter MUST be present in an transport. An SCTP Transport parameter may have a mixed list of
SCTP transport parameter. IPv4 and IPv6 addresses and at least one IP address parameter MUST
be present in an SCTP transport parameter.
3.4. 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 = 0x4 | Length = variable | | Type = 0x5 | Length = variable |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| TCP port | Transport Use | | 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 address including the Type, Length, TCP port, reserved fields, and IP
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.
Transport use: 16 bits (unsigned integer) IPv4 or IPv6 Address
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:
Type | Value
------------------+----------------
DATA ONLY | 0x0000
DATA plus CONTROL | 0x0001
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, only one IP address parameter can be Unlike in an SCTP transport parameter, only one IP address
present in a TCP transport parameter. parameter can be present in a TCP transport parameter.
3.5. UDP Transport Parameter Note: A 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.
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 = 0x5 | 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 address including the Type, Length, UDP port, reserved fields, and IP
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, only one IP address parameter can be Unlike in an SCTP transport parameter, only one IP address
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: A UDP port MUST NOT be used for control information. For this
reason, no Transport Use field is provided. UDP MUST always be 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.6. Pool Member Selection Policy Parameter 3.7. UDP-Lite Transport Parameter
This parameter defines a pool member selection policy. RSERPOOL This parameter defines a TLV that describes a user transport using
UDP-Lite protocol.
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.
UDP port: 16 bits (unsigned integer)
The UDP-Lite port number signed to this UDP-Lite user transport.
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.
Note: A 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.
3.8. Pool Member Selection Policy Parameter
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
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 Section xxxxx in ASAP [3]. defined in [I-D.ietf-rserpool-asap].
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 = 0x6 | Length = variable | | Type = 0x8 | Length = variable |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Policy Type | | Policy Type |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Policy-specific Data | | Policy-specific Data |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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 Data including the Type, Length, Policy Type, and the Policy-specific
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 end of the parameter.
of the parameter.
Policy Type: 32 bits (unsigned integer) Policy Type: 32 bits (unsigned integer)
Specifies the type of selection policy. Specifies the type of selection policy.
Policy-specific Data: Policy-specific Data:
The structure and fields for each presently defined policy types
are described in detail in [I-D.ietf-rserpool-policies].
The structure and fields for each presently defined policy types are 3.9. Pool Handle Parameter
described in detail in Policies [5].
3.7. 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 = 0x7 | 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
end of the parameter.
Note, the value in Length field will NOT cover any padding at the end Pool Handle
of the parameter.
Pool Handle:
defined as a sequence of (Length - 4) bytes. defined as a sequence of (Length - 4) bytes.
3.8. 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 PE in a pool) and the associated information, such
as its transport address, selection policy, and other operational or as its transport address, selection policy, and other operational or
status information of the PE. 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 = 0x8 | Length=variable | | Type = 0xa | Length=variable |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| PE Identifier | | PE Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Home ENRP Server Identifier | | Home ENRP Server Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Registration Life | | Registration Life |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: User Transport param : : User Transport param :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: Member Selection Policy param : : Member Selection Policy param :
skipping to change at page 12, line 38 skipping to change at page 13, line 34
| Registration Life | | Registration Life |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: 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 Length field will NOT cover any padding at the end end of this Pool Element parameter.
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 identifier when it starts up.
when it starts up. See Section 3.1 in ASAP [3] for recommendations
on PE identifier generation.
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 if Indicates the current home ENRP server of this PE. Set to all 0's
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.
A value of -1 indicates infinite life time.
Indicates the life time of the registration in number of seconds. A User Transport
value of -1 indicates infinite life time. This can be either an DCCP, SCTP, TCP, UDP, or UDP-Lite type
transport parameter (see Section 3.3, Section 3.4, Section 3.5,
User Transport: Section 3.6, Section 3.7). A PE MUST have one and only one User
Transport.
This can be either an SCTP, TCP, or UDP type transport parameter (see
Section 3.3, Section 3.4, Section 3.5). A PE MUST have one and only
one User Transport.
Member Selection Policy:
Contains one of the defined member selection policy parameters (see
Section 3.6).
ASAP Transport: Member Selection Policy
Contains one of the defined member selection policy parameters
(see Section 3.8).
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.3). SCTP type transport parameter (see Section 3.4).
3.9. Server Information Parameter 3.11. Server Information Parameter
This parameter is used in ENRP to pass basic information of an ENRP This parameter is used in ENRP to pass basic information of an ENRP
server. server.
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 = 0xb | Length=variable |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Server ID | | Server ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|M| (reserved) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: 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 octets. Note, the value in Length field will NOT cover any padding at the
end of the parameter.
Note, the value in Length field will NOT cover any padding at the end
of the parameter.
Server ID: 32 bit (unsigned integer) Server ID: 32 bit (unsigned integer)
This is the ID of the ENRP server, as defined in
This is the ID of the ENRP server, as defined in Section xxxxxx in [I-D.ietf-rserpool-enrp].
ENRP [4] .
Multicast Flag (M): 1 bit
If set to '1', indicates the ENRP server is allowed to use multicast
for communications. If set to '0', multicast is not used by the
server.
Reserved: 31 bits
MUST be set to 0's by sender and ignored by the receiver.
Server Transport: 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.
This is an SCTP Transport Parameter, as defined in Section 3.3 that 3.12. Operation Error Parameter
contains the network access address(es), SCTP port number, etc. of
the ENRP server.
3.10. Operation Error Parameter
This parameter is used in both ENPR and ASAP for a message sender to This parameter is used in both ENPR 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 = 0xa | 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 octets. Note, the value in Length field will NOT cover any padding at the
end of the parameter.
Note, the value in Length field will NOT cover any padding at 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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: : : :
skipping to change at page 15, line 16 skipping to change at page 15, line 34
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 |
--------- ---------------- +------------------+-----------------------------------------+
0 Unspecified Error | 0x0 | Unspecified Error |
1 Unrecognized Parameter | | |
2 Unrecognized Message | 0x1 | Unrecognized Parameter |
3 Invalid Values | | |
4 Non-unique PE Identifier | 0x2 | Unrecognized Message |
5 Inconsistent Pooling Policy | | |
6 Lack of Resources | 0x3 | Invalid Values |
7 Inconsistent Transport Type | | |
8 Inconsistent Data/Control Configuration | 0x4 | Non-unique PE Identifier |
9 Unknown Poor Handle | | |
10 Rejected due to security considerations | 0x5 | Inconsistent Pooling Policy |
others reserved by IETF | | |
| 0x6 | Lack of Resources |
| | |
| 0x7 | Inconsistent Transport Type |
| | |
| 0x8 | Inconsistent Data/Control Configuration |
| | |
| 0x9 | Unknown Poor Handle |
| | |
| 0xa | Rejected due to security considerations |
| | |
| others | reserved by IETF |
+------------------+-----------------------------------------+
Figure 16 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, Code, Cause Length, and Cause-Specific Information fields, but not
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
This field carries the details of the error condition. This field carries the details of the error condition.
The following subsections (Section 3.10.1 - Section 3.10.9) define The following subsections (Section 3.12.1 - Section 3.12.9) define
specific error causes. specific error causes.
3.10.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.10.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
unrecognized parameter TLV is included as cause specific information. unrecognized parameter TLV is included as cause specific information.
If a message contains multiple unrecognized parameters, multiple
error causes are used.
3.10.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.10.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.10.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.10.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.6) 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.10.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.10.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.10.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.10.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.10.11. Unknown Poor Handle Error 3.12.11. Unknown Poor 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.11. 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 = 0xb | 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 Cookie: variable length The Cookie is an arbitrary byte string of
(Length - 4) bytes.
The Cookie is an arbitrary byte string of (Length - 4) bytes.
3.12. 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 = 0xc | 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
identifier when it starts up. See [I-D.ietf-rserpool-asap] for
recommendations on PE identifier generation.
Uniquely identifies the PE in the pool. The PE picks its identifier 3.15. PE Checksum Parameter
when it starts up. See Section ???? in ASAP [3] for recommendations
on PE identifier generation.
3.13. 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 = 0xd | 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 an ENRP server (which is normally the sender of this TLV). The
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 Section [I-D.ietf-rserpool-enrp].
3.11.2 in ENRP [4].
4. Common Message Formats 4. Common Message Formats
The figure below illustrates the common format for all ASAP and ENRP The figure below illustrates the common format for all ASAP and ENRP
messages. Each message is formatted with a Message Type field, a messages. Each message is formatted with a Message Type field, a
message-specific Flag field, a Message Length field, and a Value message-specific Flag field, a Message Length field, and a Value
field. field.
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 19, line 23 skipping to change at page 20, line 23
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Message Type | Msg Flags | Message Length | | Message Type | Msg Flags | Message Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: : : :
: 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 of Message Value field. It takes a value from 0 to 254. The value
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 highest-order two bits
specify the action that must be taken if the message receiver does specify the action that must be taken if the message receiver does
not recognize the Message Type. 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.10.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 the Message Type. Unless otherwise specified, they are set to
Message Type. Unless otherwise specified, they are set to zero on zero on transmit and are ignored on receipt.
transmit and are 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 the Message Type, Message Flags, Message Length, and Message Value
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 Message Length field will NOT cover any padding at at the end of this message.
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 message fields) MUST be a multiple of 4 bytes. If the length of the
is not a multiple of 4 bytes, the sender MUST pad the message with message is not a multiple of 4 bytes, the sender MUST pad the
all zero bytes and this padding is not included in the message length message with all zero bytes and this padding is not included in
field. The sender should never pad with more than 3 bytes. The the message length field. The sender should never pad with more
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: [NOTE to RFC-Editor:
"RFCXXXX" is to be replaced by the RFC number you assign this "RFCXXXX" is to be replaced by the RFC number you assign this
document. document.
] ]
This document (RFCXXX) is the reference for all registrations This document (RFCXXX) is the reference for all registrations
described in this section. All registrations need to be listed on an described in this section. All registrations need to be listed on an
RSerPool specific page. 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 have to be maintained by IANA. Thirteen
initial values should be assigned by IANA as described in Figure 2. initial values should be assigned by IANA as described in Table 1.
This requires a new table "RSerPool Parameter Types": This requires a new table "RSerPool Parameter Types":
Type Message Name Reference +--------+------------------------------+
----- ------------------------- --------- | Value | Parameter Type |
0x0 (reserved by IETF) RFCXXXX +--------+------------------------------+
0x1 IPv4 Address RFCXXXX | 0x0 | (reserved by IETF) |
0x2 IPv6 Address RFCXXXX | | |
0x3 SCTP Transport RFCXXXX | 0x1 | IPv4 Address |
0x4 TCP Transport RFCXXXX | | |
0x5 UDP Transport RFCXXXX | 0x2 | IPv6 Address |
0x6 Pool Member Selection Policy RFCXXXX | | |
0x7 Pool Handle RFCXXXX | 0x3 | DCCP Transport |
0x8 Pool Element RFCXXXX | | |
0x9 Server Information RFCXXXX | 0x4 | SCTP Transport |
0xa Operation Error RFCXXXX | | |
0xb Cookie RFCXXXX | 0x5 | TCP Transport |
0xc PE Identifier RFCXXXX | | |
0xd PE Checksum RFCXXXX | 0x6 | UDP Transport |
others (reserved by IETF) RFCXXXX | | |
| 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 |
| | |
| others | (reserved by IETF) |
+--------+------------------------------+
For registering at IANA an RSerPool Parameter Type in this table a For registering at IANA an RSerPool Parameter Type in this table a
request has to be made to assign such a number. This number must be request has to be made to assign such a number. This number must be
unique. The "Specification Required" policy of RFC2434 [2] MUST be unique. The "Specification Required" policy of [RFC2434] 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 have to be maintained by IANA. Eleven initial
values should be assigned by IANA as described in Figure 16. This values should be assigned by IANA as described in Table 2. This
requires a new table "RSerPool Error Causes": requires a new table "RSerPool Error Causes":
Cause Cause Name Reference +------------------+-----------------------------------------+
----- ------------------------- --------- | Cause Code Value | Cause Code |
0 Unspecified Error RFCXXXX +------------------+-----------------------------------------+
1 Unrecognized Parameter RFCXXXX | 0x0 | Unspecified Error |
2 Unrecognized Message RFCXXXX | | |
3 Invalid Values RFCXXXX | 0x1 | Unrecognized Parameter |
4 Non-unique PE Identifier RFCXXXX | | |
5 Inconsistent Pooling Policy RFCXXXX | 0x2 | Unrecognized Message |
6 Lack of Resources RFCXXXX | | |
7 Inconsistent Transport Type RFCXXXX | 0x3 | Invalid Values |
8 Inconsistent Data/Control Configuration RFCXXXX | | |
9 Unknown Poor Handle RFCXXXX | 0x4 | Non-unique PE Identifier |
10 Rejected due to security considerations RFCXXXX | | |
others (reserved by IETF) RFCXXXX | 0x5 | Inconsistent Pooling Policy |
| | |
| 0x6 | Lack of Resources |
| | |
| 0x7 | Inconsistent Transport Type |
| | |
| 0x8 | Inconsistent Data/Control Configuration |
| | |
| 0x9 | Unknown Poor Handle |
| | |
| 0xa | Rejected due to security considerations |
| | |
| others | reserved by IETF |
+------------------+-----------------------------------------+
For registering at IANA an RSerPool Error Cause in this table a For registering at IANA an RSerPool Error Cause in this table a
request has to be made to assign such a number. This number must be request has to be made to assign such a number. This number must be
unique. The "Specification Required" policy of RFC2434 [2] MUST be unique. The "Specification Required" policy of [RFC2434] 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 ENRP Details on ENRP and ASAP security constraints are addressed in
[4] and ASAP [3] . [I-D.ietf-rserpool-enrp] and [I-D.ietf-rserpool-asap].
7. Normative References 7. Normative References
[1] Bradner, S., "Key words for use in RFCs to Indicate Requirement [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[2] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA [RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing an
Considerations Section in RFCs", BCP 26, RFC 2434, October 1998. IANA Considerations Section in RFCs", BCP 26, RFC 2434,
October 1998.
[3] Stewart, R., "Aggregate Server Access Protocol (ASAP)", [I-D.ietf-rserpool-asap]
draft-ietf-rserpool-asap-16 (work in progress), July 2007. Stewart, R., Xie, Q., Stillman, M., and M. Tuexen,
"Aggregate Server Access Protocol (ASAP)",
draft-ietf-rserpool-asap-17 (work in progress),
September 2007.
[4] Stewart, R., "Endpoint Handlespace Redundancy Protocol (ENRP)", [I-D.ietf-rserpool-enrp]
draft-ietf-rserpool-enrp-16 (work in progress), July 2007. Xie, Q., Stewart, R., Stillman, M., Tuexen, M., and A.
Silverton, "Endpoint Handlespace Redundancy Protocol
(ENRP)", draft-ietf-rserpool-enrp-17 (work in progress),
September 2007.
[5] Tuexen, M. and T. Dreibholz, "Reliable Server Pooling Policies", [I-D.ietf-rserpool-policies]
draft-ietf-rserpool-policies-05 (work in progress), July 2007. Tuexen, M. and T. Dreibholz, "Reliable Server Pooling
Policies", draft-ietf-rserpool-policies-07 (work in
progress), November 2007.
Authors' Addresses Authors' Addresses
Randall R. Stewart Randall R. Stewart
Cisco Systems, Inc. Cisco Systems, Inc.
4875 Forest Drive 4875 Forest Drive
Suite 200 Suite 200
Columbia, SC 29206 Columbia, SC 29206
USA USA
Phone:
Email: rrs@cisco.com Email: rrs@cisco.com
Qiaobing Xie Qiaobing Xie
Motorola, Inc. Motorola, Inc.
1501 W. Shure Drive, #2309 1501 W. Shure Drive, #2309
Arlington Heights, IL 60004 Arlington Heights, IL 60004
USA USA
Phone:
Email: qxie1@email.mot.com Email: qxie1@email.mot.com
Maureen Stillman Maureen Stillman
Nokia Nokia
127 W. State Street 127 W. State Street
Ithaca, NY 14850 Ithaca, NY 14850
USA USA
Phone:
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
 End of changes. 129 change blocks. 
353 lines changed or deleted 425 lines changed or added

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