draft-ietf-rserpool-common-param-16.txt   draft-ietf-rserpool-common-param-17.txt 
Network Working Group R. Stewart Network Working Group R. Stewart
Internet-Draft Cisco Systems, Inc. Internet-Draft Q. Xie
Intended status: Experimental Q. Xie Intended status: Experimental
Expires: September 28, 2008 Motorola, Inc. Expires: November 30, 2008 M. Stillman
M. Stillman
Nokia Nokia
M. Tuexen M. Tuexen
Muenster Univ. of Applied Sciences Muenster Univ. of Applied Sciences
March 27, 2008 May 29, 2008
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-16.txt draft-ietf-rserpool-common-param-17.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 39
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 September 28, 2008. This Internet-Draft will expire on November 30, 2008.
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
skipping to change at page 6, line 17 skipping to change at page 6, line 17
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Parameter Type | Parameter Length | | Parameter Type | Parameter Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: : : :
: Parameter Value : : Parameter Value :
: : : +-------------------------------:
: | 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 specific ENRP parameter
description are reserved by IETF. (Additional types, when needed, description are reserved by IETF. (Additional types, when needed,
will be defined in the future through appropriate IETF/IANA will be defined in the future through appropriate IETF/IANA
procedures.) procedures.)
skipping to change at page 7, line 5 skipping to change at page 7, line 5
(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 |
| | | | | |
skipping to change at page 7, line 43 skipping to change at page 7, line 43
| | | | | |
| 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) | | others | (reserved by IETF) |
+--------+------------------------------+ | | |
| 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 15 skipping to change at page 8, line 21
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.
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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| IPv4 Address | | IPv4 Address |
skipping to change at page 13, line 35 skipping to change at page 13, line 35
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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. Specifies the type of selection policy. The values are defined in
[I-D.ietf-rserpool-policies].
Policy-specific Data: Policy-specific Data:
The structure and fields for each presently defined policy types 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 [I-D.ietf-rserpool-policies].
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 |
skipping to change at page 16, line 20 skipping to change at page 16, line 20
This is the ID of the ENRP server, as defined in This is the ID of the ENRP server, as defined in
[I-D.ietf-rserpool-enrp]. [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 ENPR 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 :
: : : :
skipping to change at page 18, line 8 skipping to change at page 18, line 8
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
unrecognized parameter TLV is included as cause specific information. complete unrecognized parameter TLV is included as cause specific
If a message contains multiple unrecognized parameters, multiple information. If a message contains multiple unrecognized parameters,
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
skipping to change at page 25, line 5 skipping to change at page 25, line 5
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 Table 1. 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":
+--------+------------------------------+ +------------+------------------------------+
| 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 |
| | | | | |
skipping to change at page 25, line 43 skipping to change at page 25, line 43
| | | | | |
| 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) | | others | (reserved by IETF) |
+--------+------------------------------+ | | |
| 0xffffffff | IETF-defined extensions |
+------------+------------------------------+
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] MUST be unique. The "Specification 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 have to be maintained by IANA. Eleven initial
values should be assigned by IANA as described in Table 2. 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 Code Value | Cause Code | | Cause Code Value | Cause Code |
skipping to change at page 26, line 41 skipping to change at page 26, line 41
| | | | | |
| 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 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] MUST be unique. The "Specification 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]. [I-D.ietf-rserpool-enrp] and [I-D.ietf-rserpool-asap].
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.
[RFC2434] 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 2434, IANA Considerations Section in RFCs", BCP 26, RFC 5226,
October 1998. May 2008.
[I-D.ietf-rserpool-asap] [I-D.ietf-rserpool-asap]
Stewart, R., Xie, Q., Stillman, M., and M. Tuexen, Stewart, R., Xie, Q., Stillman, M., and M. Tuexen,
"Aggregate Server Access Protocol (ASAP)", "Aggregate Server Access Protocol (ASAP)",
draft-ietf-rserpool-asap-18 (work in progress), draft-ietf-rserpool-asap-19 (work in progress),
November 2007. March 2008.
[I-D.ietf-rserpool-enrp] [I-D.ietf-rserpool-enrp]
Xie, Q., Stewart, R., Stillman, M., Tuexen, M., and A. Kim, D., Stewart, R., Stillman, M., Tuexen, M., and A.
Silverton, "Endpoint Handlespace Redundancy Protocol Silverton, "Endpoint Handlespace Redundancy Protocol
(ENRP)", draft-ietf-rserpool-enrp-18 (work in progress), (ENRP)", draft-ietf-rserpool-enrp-19 (work in progress),
November 2007. March 2008.
[I-D.ietf-rserpool-policies] [I-D.ietf-rserpool-policies]
Tuexen, M. and T. Dreibholz, "Reliable Server Pooling Tuexen, M. and T. Dreibholz, "Reliable Server Pooling
Policies", draft-ietf-rserpool-policies-08 (work in Policies", draft-ietf-rserpool-policies-08 (work in
progress), March 2008. progress), March 2008.
Authors' Addresses Authors' Addresses
Randall R. Stewart Randall R. Stewart
Cisco Systems, Inc.
4875 Forest Drive 4875 Forest Drive
Suite 200 Suite 200
Columbia, SC 29206 Columbia, SC 29206
USA USA
Email: rrs@cisco.com Phone:
Email: randall@lakerest.net
Qiaobing Xie Qiaobing Xie
Motorola, Inc.
1501 W. Shure Drive, #2309
Arlington Heights, IL 60004
USA USA
Email: qxie1@email.mot.com Phone: +1 224-465-5954
Email: Qiaobing.Xie@gmail.org
Maureen Stillman Maureen Stillman
Nokia Nokia
127 W. State Street 127 W. State Street
Ithaca, NY 14850 Ithaca, NY 14850
USA USA
Email: maureen.stillman@nokia.com Email: maureen.stillman@nokia.com
Michael Tuexen Michael Tuexen
 End of changes. 27 change blocks. 
37 lines changed or deleted 42 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/