draft-ietf-rserpool-common-param-05.txt   draft-ietf-rserpool-common-param-06.txt 
Network Working Group R. Stewart Network Working Group R. Stewart
Internet-Draft Cisco Systems, Inc. Internet-Draft Cisco Systems, Inc.
Expires: April 22, 2004 Q. Xie Expires: December 8, 2004 Q. Xie
Motorola, Inc. Motorola, Inc.
M. Stillman M. Stillman
Nokia Nokia
M. Tuexen M. Tuexen
October 23, 2003 June 9, 2004
Aggregate Server Access Protocol (ASAP) and Endpoint Name Resolution Aggregate Server Access Protocol (ASAP) and Endpoint Name Resolution
Protocol (ENRP) Parameters Protocol (ENRP) Parameters
draft-ietf-rserpool-common-param-05.txt draft-ietf-rserpool-common-param-06.txt
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with By submitting this Internet-Draft, I certify that any applicable
all provisions of Section 10 of RFC2026. patent or other IPR claims of which I am aware have been disclosed,
and any of which I become aware will be disclosed, in accordance with
RFC 3668.
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 other Task Force (IETF), its areas, and its working groups. Note that
groups may also distribute working documents as Internet-Drafts. other groups may also distribute working documents as
Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
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 http:// The list of current Internet-Drafts can be accessed at
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 April 22, 2004. This Internet-Draft will expire on December 8, 2004.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2003). All Rights Reserved. Copyright (C) The Internet Society (2004). All Rights Reserved.
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 Name Resolution Protocol (ENRP) Protocol (ASAP) and Endpoint Name Resolution 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 . . . . . . . . . . . . . . . . . . 6 3.1 IPv4 Address Parameter . . . . . . . . . . . . . . . . . . 6
3.2 IPv6 Address Parameter . . . . . . . . . . . . . . . . . . 7 3.2 IPv6 Address Parameter . . . . . . . . . . . . . . . . . . 7
3.3 SCTP Transport Parameter . . . . . . . . . . . . . . . . . 7 3.3 SCTP Transport Parameter . . . . . . . . . . . . . . . . . 7
3.4 TCP Transport Parameter . . . . . . . . . . . . . . . . . 8 3.4 TCP Transport Parameter . . . . . . . . . . . . . . . . . 9
3.5 UDP Transport Parameter . . . . . . . . . . . . . . . . . 9 3.5 UDP Transport Parameter . . . . . . . . . . . . . . . . . 9
3.6 Pool Member Selection Policy Parameter . . . . . . . . . . 10 3.6 Pool Member Selection Policy Parameter . . . . . . . . . . 10
3.6.1 Round Robin Policy . . . . . . . . . . . . . . . . . . . . 12 3.6.1 Round Robin Policy . . . . . . . . . . . . . . . . . . 11
3.6.2 Least Used Policy . . . . . . . . . . . . . . . . . . . . 12 3.6.2 Least Used Policy . . . . . . . . . . . . . . . . . . 12
3.6.3 Least Used with Degradation Policy . . . . . . . . . . . . 12 3.6.3 Least Used with Degradation Policy . . . . . . . . . . 12
3.6.4 Weighted Round Robin Policy . . . . . . . . . . . . . . . 13 3.6.4 Weighted Round Robin Policy . . . . . . . . . . . . . 12
3.7 Pool Handle Parameter . . . . . . . . . . . . . . . . . . 13 3.7 Pool Handle Parameter . . . . . . . . . . . . . . . . . . 12
3.8 Pool Element Parameter . . . . . . . . . . . . . . . . . . 13 3.8 Pool Element Parameter . . . . . . . . . . . . . . . . . . 13
3.9 Server Information Parameter . . . . . . . . . . . . . . . 15 3.9 Server Information Parameter . . . . . . . . . . . . . . . 14
3.10 Operation Error Parameter . . . . . . . . . . . . . . . . 16 3.10 Operation Error Parameter . . . . . . . . . . . . . . . 15
3.10.1 Unspecified Error . . . . . . . . . . . . . . . . . . . . 17 3.10.1 Unspecified Error . . . . . . . . . . . . . . . . . 17
3.10.2 Unrecognized Parameter Error . . . . . . . . . . . . . . . 17 3.10.2 Unrecognized Parameter Error . . . . . . . . . . . . 17
3.10.3 Unrecognized Message Error . . . . . . . . . . . . . . . . 17 3.10.3 Unrecognized Message Error . . . . . . . . . . . . . 17
3.10.4 Invalid Values Error . . . . . . . . . . . . . . . . . . . 17 3.10.4 Invalid Values Error . . . . . . . . . . . . . . . . 17
3.10.5 Non-unique PE Identifier Error . . . . . . . . . . . . . . 18 3.10.5 Non-unique PE Identifier Error . . . . . . . . . . . 17
3.10.6 Inconsistent Pool Policy Error . . . . . . . . . . . . . . 18 3.10.6 Inconsistent Pool Policy Error . . . . . . . . . . . 17
3.10.7 Lack of Resources Error . . . . . . . . . . . . . . . . . 18 3.10.7 Lack of Resources Error . . . . . . . . . . . . . . 17
3.10.8 Inconsistent Transport Type Error . . . . . . . . . . . . 18 3.10.8 Inconsistent Transport Type Error . . . . . . . . . 17
3.10.9 Inconsistent Data/Control Configuration Error . . . . . . 18 3.10.9 Inconsistent Data/Control Configuration Error . . . 18
3.11 Cookie Parameter . . . . . . . . . . . . . . . . . . . . . 18 3.11 Cookie Parameter . . . . . . . . . . . . . . . . . . . . 18
3.12 PE Identifier Parameter . . . . . . . . . . . . . . . . . 19 3.12 PE Identifier Parameter . . . . . . . . . . . . . . . . 18
3.13 PE Checksum Parameter . . . . . . . . . . . . . . . . . . 19 3.13 PE Checksum Parameter . . . . . . . . . . . . . . . . . 19
4. Common Message Formats . . . . . . . . . . . . . . . . . . 21 4. Common Message Formats . . . . . . . . . . . . . . . . . . . 20
5. Security Considerations . . . . . . . . . . . . . . . . . 23 5. Security Considerations . . . . . . . . . . . . . . . . . . 22
Normative References . . . . . . . . . . . . . . . . . . . 24 6. Normative References . . . . . . . . . . . . . . . . . . . . 22
Authors' Addresses . . . . . . . . . . . . . . . . . . . . 24 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . 22
Intellectual Property and Copyright Statements . . . . . . 26 Intellectual Property and Copyright Statements . . . . . . . 24
1. Introduction 1. Introduction
Aggregate Server Access Protocol (ASAP) [3] in conjunction with the Aggregate Server Access Protocol (ASAP) [3] in conjunction with the
Endpoint Name Resolution Protocol (ENRP) [4] provides a high Endpoint Name Resolution 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
skipping to change at page 6, line 20 skipping to change at page 6, line 20
0x3 - SCTP Transport 0x3 - SCTP Transport
0x4 - TCP Transport 0x4 - TCP Transport
0x5 - UDP Transport 0x5 - UDP Transport
0x6 - Pool Member Selection Policy 0x6 - Pool Member Selection Policy
0x7 - Pool Handle 0x7 - Pool Handle
0x8 - Pool Element 0x8 - Pool Element
0x9 - Server Information 0x9 - Server Information
0xa - Operation Error 0xa - Operation Error
0xb - Cookie 0xb - Cookie
0xc - PE Identifier 0xc - PE Identifier
0xd - PE Checksum
others - (reserved by IETF) others - (reserved by IETF)
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 Parameter
Value fields. Thus, a parameter with a zero-length Parameter Value Value fields. Thus, a parameter with a zero-length Parameter Value
field would have a Length field of 4. field would have a Length field of 4.
skipping to change at page 8, line 44 skipping to change at page 8, line 44
following values: following values:
Type | Value Type | Value
------------------+---------------- ------------------+----------------
DATA ONLY | 0x0000 DATA ONLY | 0x0000
DATA plus CONTROL | 0x0001 DATA plus CONTROL | 0x0001
IPv4 or IPv6 Address #1 - #n: IPv4 or IPv6 Address #1 - #n:
Each indicates an IPv4 or IPv6 address parameter (as defined above in Each indicates an IPv4 or IPv6 address parameter (as defined above in
Section 3.1 and Section 3.2) assigned to this SCTP user transport. An Section 3.1 and Section 3.2) assigned to this SCTP user transport.
SCTP Transport parameter may have a mixed list of IPv4 and IPv6 An SCTP Transport parameter may have a mixed list of IPv4 and IPv6
addresses and at least one IP address parameter MUST be present in an addresses and at least one IP address parameter MUST be present in an
SCTP transport parameter. SCTP transport parameter.
3.4 TCP Transport Parameter 3.4 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 = 0x4 | Length = variable |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| TCP port | Transport Use | | TCP port | Transport Use |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 23, line 8 skipping to change at page 22, line 8
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 message
is not a multiple of 4 bytes, the sender MUST pad the message with is not a multiple of 4 bytes, the sender MUST pad the message with
all zero bytes and this padding is not included in the message length all zero bytes and this padding is not included in the message length
field. The sender should never pad with more than 3 bytes. The field. The sender should never pad with more than 3 bytes. The
receiver MUST ignore the padding bytes. receiver MUST ignore the padding bytes.
5. Security Considerations 5. 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. Details specifies no new security constraints on either ENRP or ASAP.
on ENRP and ASAP security constraints are addressed in ENRP [4] and Details on ENRP and ASAP security constraints are addressed in ENRP
ASAP [3] . [4] and ASAP [3] .
Normative References 6 Normative References
[1] Bradner, S., "The Internet Standards Process -- Revision 3", BCP [1] Bradner, S., "The Internet Standards Process -- Revision 3", BCP
9, RFC 2026, October 1996. 9, RFC 2026, October 1996.
[2] Bradner, S., "Key words for use in RFCs to Indicate Requirement [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] Stewart, R., Xie, Q., Stillman, M. and M. Tuexen, "Aggregate [3] Stewart, R., Xie, Q., Stillman, M. and M. Tuexen, "Aggregate
Server Access Protocol (ASAP)", draft-ietf-rserpool-asap-08 Server Access Protocol (ASAP)", draft-ietf-rserpool-asap-09
(work in progress), October 2003. (work in progress), June 2004.
[4] Xie, Q., Stewart, R. and M. Stillman, "Endpoint Name Resolution [4] Xie, Q., Stewart, R. and M. Stillman, "Endpoint Name Resolution
Protocol (ENRP)", draft-ietf-rserpool-enrp-07 (work in Protocol (ENRP)", draft-ietf-rserpool-enrp-08 (work in
progress), October 2003. progress), June 2004.
Authors' Addresses Authors' Addresses
Randall R. Stewart Randall R. Stewart
Cisco Systems, Inc. Cisco Systems, Inc.
8725 West Higgins Road 8725 West Higgins Road
Suite 300 Suite 300
Chicago, IL 60631 Chicago, IL 60631
USA USA
skipping to change at page 26, line 8 skipping to change at page 24, line 8
Michael Tuexen Michael Tuexen
Germany Germany
Phone: Phone:
EMail: tuexen@fh-muenster.de EMail: tuexen@fh-muenster.de
Intellectual Property Statement Intellectual Property Statement
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
intellectual property or other rights that might be claimed to Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights this document or the extent to which any license under such rights
might or might not be available; neither does it represent that it might or might not be available; nor does it represent that it has
has made any effort to identify any such rights. Information on the made any independent effort to identify any such rights. Information
IETF's procedures with respect to rights in standards-track and on the procedures with respect to rights in RFC documents can be
standards-related documentation can be found in BCP-11. Copies of found in BCP 78 and BCP 79.
claims of rights made available for publication and any assurances of
licenses to be made available, or the result of an attempt made to Copies of IPR disclosures made to the IETF Secretariat and any
obtain a general license or permission for the use of such assurances of licenses to be made available, or the result of an
proprietary rights by implementors or users of this specification can attempt made to obtain a general license or permission for the use of
be obtained from the IETF Secretariat. such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights which may cover technology that may be required to practice rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF Executive this standard. Please address the information to the IETF at
Director. ietf-ipr@ietf.org.
Full Copyright Statement
Copyright (C) The Internet Society (2003). All Rights Reserved. Disclaimer of Validity
This document and translations of it may be copied and furnished to This document and the information contained herein are provided on an
others, and derivative works that comment on or otherwise explain it "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
or assist in its implementation may be prepared, copied, published OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
and distributed, in whole or in part, without restriction of any ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
kind, provided that the above copyright notice and this paragraph are INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
included on all such copies and derivative works. However, this INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
document itself may not be modified in any way, such as by removing WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process must be
followed, or as required to translate it into languages other than
English.
The limited permissions granted above are perpetual and will not be Copyright Statement
revoked by the Internet Society or its successors or assignees.
This document and the information contained herein is provided on an Copyright (C) The Internet Society (2004). This document is subject
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING to the rights, licenses and restrictions contained in BCP 78, and
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING except as set forth therein, the authors retain all their rights.
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Acknowledgement Acknowledgment
Funding for the RFC Editor function is currently provided by the Funding for the RFC Editor function is currently provided by the
Internet Society. Internet Society.
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/