draft-ietf-rserpool-common-param-12.txt   draft-ietf-rserpool-common-param-13.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: January 10, 2008 Motorola, Inc. Expires: March 25, 2008 Motorola, Inc.
M. Stillman M. Stillman
Nokia Nokia
M. Tuexen M. Tuexen
Muenster Univ. of Applied Sciences Muenster Univ. of Applied Sciences
July 9, 2007 September 22, 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-12.txt draft-ietf-rserpool-common-param-13.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 January 10, 2008. This Internet-Draft will expire on March 25, 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)
skipping to change at page 3, line 7 skipping to change at page 3, line 7
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 21 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 21
5.1. A New Table for RSerPool Parameter Types . . . . . . . . . 21 5.1. A New Table for RSerPool Parameter Types . . . . . . . . . 21
5.2. A New Table for RSerPool Error Causes . . . . . . . . . . 21 5.2. A New Table for RSerPool Error Causes . . . . . . . . . . 21
6. Security Considerations . . . . . . . . . . . . . . . . . . . 23 6. Security Considerations . . . . . . . . . . . . . . . . . . . 23
7. Normative References . . . . . . . . . . . . . . . . . . . . . 24 7. Normative References . . . . . . . . . . . . . . . . . . . . . 24
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 25 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 25
Intellectual Property and Copyright Statements . . . . . . . . . . 26 Intellectual Property and Copyright Statements . . . . . . . . . . 26
1. Introduction 1. Introduction
Aggregate Server Access Protocol (ASAP) [4] in conjunction with the Aggregate Server Access Protocol (ASAP) [3] in conjunction with the
Endpoint Handlespace Redundancy Protocol (ENRP) [5] provides a high Endpoint Handlespace Redundancy Protocol (ENRP) [4] provides a high
availability data transfer mechanism over IP networks. 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 [4] and ENRP [5] documents. refer to the respective ASAP [3] and ENRP [4] documents.
1.1. Conventions 1.1. Conventions
The keywords MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD, The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
SHOULD NOT, RECOMMENDED, NOT RECOMMENDED, MAY, and OPTIONAL, when "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
they appear in this document, are to be interpreted as described in document are to be interpreted as described in RFC2119 [1].
RFC2119 [2].
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 10, line 43 skipping to change at page 10, line 43
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.6. 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
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 [4]. defined in Section xxxxx in ASAP [3].
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 = 0x6 | Length = variable |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Policy Type | | Policy Type |
skipping to change at page 11, line 31 skipping to change at page 11, line 31
Note, the Length field value will NOT include any padding at the end Note, the Length field value will NOT include any padding at the 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 The structure and fields for each presently defined policy types are
described in detail in Policies [6]. described in detail in Policies [5].
3.7. Pool Handle Parameter 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 = 0x7 | Length=variable |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 12, line 49 skipping to change at page 12, line 49
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 end Note, the value in Length field will NOT cover any padding at the 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 identifier Uniquely identifies the PE in the pool. The PE picks its identifier
when it starts up. See Section ???? in [ASAP] for recommendations on when it starts up. See Section 3.1 in ASAP [3] for recommendations
PE identifier generation. 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 if
the PE's home ENRP server is undetermined. 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 Indicates the life time of the registration in number of seconds. A
value of -1 indicates infinite life time. value of -1 indicates infinite life time.
skipping to change at page 14, line 8 skipping to change at page 14, line 8
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.
Note, the value in Length field will NOT cover any padding at the end Note, the value in Length field will NOT cover any padding at the end
of the parameter. 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 Section xxxxxx in This is the ID of the ENRP server, as defined in Section xxxxxx in
ENRP [5] . ENRP [4] .
Multicast Flag (M): 1 bit Multicast Flag (M): 1 bit
If set to '1', indicates the ENRP server is allowed to use multicast 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 for communications. If set to '0', multicast is not used by the
server. server.
Reserved: 31 bits Reserved: 31 bits
MUST be set to 0's by sender and ignored by the receiver. MUST be set to 0's by sender and ignored by the receiver.
skipping to change at page 15, line 32 skipping to change at page 15, line 32
0 Unspecified Error 0 Unspecified Error
1 Unrecognized Parameter 1 Unrecognized Parameter
2 Unrecognized Message 2 Unrecognized Message
3 Invalid Values 3 Invalid Values
4 Non-unique PE Identifier 4 Non-unique PE Identifier
5 Inconsistent Pooling Policy 5 Inconsistent Pooling Policy
6 Lack of Resources 6 Lack of Resources
7 Inconsistent Transport Type 7 Inconsistent Transport Type
8 Inconsistent Data/Control Configuration 8 Inconsistent Data/Control Configuration
9 Unknown Poor Handle 9 Unknown Poor Handle
10 Rejected due to security considerations. 10 Rejected due to security considerations
other values reserved by IETF others reserved by IETF
Figure 16 Figure 16
Cause Length: 16 bits (unsigned integer) Cause Length: 16 bits (unsigned integer)
Set to the size of the parameter in bytes, including the Cause Code, Set to the size of the parameter in bytes, including the Cause 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
skipping to change at page 18, line 16 skipping to change at page 18, line 16
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 = 0xc | 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 Uniquely identifies the PE in the pool. The PE picks its identifier
when it starts up. See Section ???? in ASAP [4] for recommendations when it starts up. See Section ???? in ASAP [3] for recommendations
on PE identifier generation. on PE identifier generation.
3.13. PE Checksum Parameter 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 = 0xd | 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 An overall checksum of all PEs in the current handlespace owned by 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 Section definition and calculation of this checksum is defined in Section
3.11.2 in ENRP [5]. 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 21, line 44 skipping to change at page 21, line 44
0x8 Pool Element RFCXXXX 0x8 Pool Element RFCXXXX
0x9 Server Information RFCXXXX 0x9 Server Information RFCXXXX
0xa Operation Error RFCXXXX 0xa Operation Error RFCXXXX
0xb Cookie RFCXXXX 0xb Cookie RFCXXXX
0xc PE Identifier RFCXXXX 0xc PE Identifier RFCXXXX
0xd PE Checksum RFCXXXX 0xd PE Checksum RFCXXXX
others (reserved by IETF) RFCXXXX others (reserved by IETF) RFCXXXX
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 [3] MUST be unique. The "Specification Required" policy of RFC2434 [2] 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 Figure 16. This
requires a new table "RSerPool Error Causes": requires a new table "RSerPool Error Causes":
Cause Cause Name Reference Cause Cause Name Reference
----- ------------------------- --------- ----- ------------------------- ---------
skipping to change at page 22, line 22 skipping to change at page 22, line 22
5 Inconsistent Pooling Policy RFCXXXX 5 Inconsistent Pooling Policy RFCXXXX
6 Lack of Resources RFCXXXX 6 Lack of Resources RFCXXXX
7 Inconsistent Transport Type RFCXXXX 7 Inconsistent Transport Type RFCXXXX
8 Inconsistent Data/Control Configuration RFCXXXX 8 Inconsistent Data/Control Configuration RFCXXXX
9 Unknown Poor Handle RFCXXXX 9 Unknown Poor Handle RFCXXXX
10 Rejected due to security considerations RFCXXXX 10 Rejected due to security considerations RFCXXXX
others (reserved by IETF) RFCXXXX others (reserved by IETF) RFCXXXX
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 [3] MUST be unique. The "Specification Required" policy of RFC2434 [2] 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 ENRP
[5] and ASAP [4] . [4] and ASAP [3] .
7. Normative References 7. Normative References
[1] Bradner, S., "The Internet Standards Process -- Revision 3", [1] Bradner, S., "Key words for use in RFCs to Indicate Requirement
BCP 9, RFC 2026, October 1996.
[2] Bradner, S., "Key words for use in RFCs to Indicate Requirement
Levels", BCP 14, RFC 2119, March 1997. Levels", BCP 14, RFC 2119, March 1997.
[3] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA [2] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA
Considerations Section in RFCs", BCP 26, RFC 2434, October 1998. Considerations Section in RFCs", BCP 26, RFC 2434, October 1998.
[4] Stewart, R., Xie, Q., Stillman, M., and M. Tuexen, "Aggregate [3] Stewart, R., "Aggregate Server Access Protocol (ASAP)",
Server Access Protocol (ASAP)", draft-ietf-rserpool-asap-12 draft-ietf-rserpool-asap-16 (work in progress), July 2007.
(work in progress), July 2005.
[5] Xie, Q., Stewart, R., Stillman, M., Tuexen, M., and A. [4] Stewart, R., "Endpoint Handlespace Redundancy Protocol (ENRP)",
Silverton, "Endpoint Handlespace Redundancy Protocol (ENRP)", draft-ietf-rserpool-enrp-16 (work in progress), July 2007.
draft-ietf-rserpool-enrp-12 (work in progress), July 2005.
[6] Tuexen, M. and T. Dreibholz, "Reliable Server Pooling Policies", [5] Tuexen, M. and T. Dreibholz, "Reliable Server Pooling Policies",
draft-ietf-rserpool-policies-04 (work in progress), March 2007. draft-ietf-rserpool-policies-05 (work in progress), July 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
 End of changes. 22 change blocks. 
36 lines changed or deleted 30 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/