draft-ietf-rserpool-common-param-10.txt   draft-ietf-rserpool-common-param-11.txt 
Network Working Group R. Stewart Network Working Group R. Stewart
Internet-Draft Cisco Systems, Inc. Internet-Draft Cisco Systems, Inc.
Expires: August 11, 2006 Q. Xie Intended status: Informational Q. Xie
Motorola, Inc. Expires: April 20, 2007 Motorola, Inc.
M. Stillman M. Stillman
Nokia Nokia
M. Tuexen M. Tuexen
Muenster Univ. of Applied Sciences Muenster Univ. of Applied Sciences
February 7, 2006 October 17, 2006
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-10.txt draft-ietf-rserpool-common-param-11.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 August 11, 2006. This Internet-Draft will expire on April 20, 2007.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2006). Copyright (C) The Internet Society (2006).
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 2, line 19 skipping to change at page 2, line 24
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 . . . . . . . . . . . . . . . . . 9 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 . . . . . . . . . . . . . . . . . 11 3.6.1. Round Robin Policy . . . . . . . . . . . . . . . . . 12
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 . . . . . . . . . . . . . 12 3.6.4. Weighted Round Robin Policy . . . . . . . . . . . . . 13
3.7. Pool Handle Parameter . . . . . . . . . . . . . . . . . . 13 3.7. Pool Handle Parameter . . . . . . . . . . . . . . . . . . 13
3.8. Pool Element Parameter . . . . . . . . . . . . . . . . . . 13 3.8. Pool Element Parameter . . . . . . . . . . . . . . . . . . 14
3.9. Server Information Parameter . . . . . . . . . . . . . . . 15 3.9. Server Information Parameter . . . . . . . . . . . . . . . 15
3.10. Operation Error Parameter . . . . . . . . . . . . . . . . 16 3.10. Operation Error Parameter . . . . . . . . . . . . . . . . 16
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 . . . . . . . . . . . . . . . . 18
3.10.5. Non-unique PE Identifier Error . . . . . . . . . . . 18 3.10.5. Non-unique PE Identifier Error . . . . . . . . . . . 18
3.10.6. Inconsistent Pool Policy Error . . . . . . . . . . . 18 3.10.6. Inconsistent Pool Policy Error . . . . . . . . . . . 18
3.10.7. Lack of Resources Error . . . . . . . . . . . . . . . 18 3.10.7. Lack of Resources Error . . . . . . . . . . . . . . . 18
3.10.8. Inconsistent Transport Type Error . . . . . . . . . . 18 3.10.8. Inconsistent Transport Type Error . . . . . . . . . . 18
3.10.9. Inconsistent Data/Control Configuration Error . . . . 18 3.10.9. Inconsistent Data/Control Configuration Error . . . . 18
3.10.10. Unknown Poor Handle Error . . . . . . . . . . . . . . 18 3.10.10. Rejected due to security considerations . . . . . . . 18
3.11. Cookie Parameter . . . . . . . . . . . . . . . . . . . . . 18 3.10.11. Unknown Poor Handle Error . . . . . . . . . . . . . . 19
3.11. Cookie Parameter . . . . . . . . . . . . . . . . . . . . . 19
3.12. PE Identifier Parameter . . . . . . . . . . . . . . . . . 19 3.12. PE Identifier Parameter . . . . . . . . . . . . . . . . . 19
3.13. PE Checksum Parameter . . . . . . . . . . . . . . . . . . 19 3.13. PE Checksum Parameter . . . . . . . . . . . . . . . . . . 20
4. Common Message Formats . . . . . . . . . . . . . . . . . . . . 21 4. Common Message Formats . . . . . . . . . . . . . . . . . . . . 21
5. Security Considerations . . . . . . . . . . . . . . . . . . . 23 5. Security Considerations . . . . . . . . . . . . . . . . . . . 23
6. Normative References . . . . . . . . . . . . . . . . . . . . . 23 6. Normative References . . . . . . . . . . . . . . . . . . . . . 24
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 24 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 25
Intellectual Property and Copyright Statements . . . . . . . . . . 25 Intellectual Property and Copyright Statements . . . . . . . . . . 26
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 Handlespace Redundancy Protocol (ENRP) [4] 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
skipping to change at page 11, line 10 skipping to change at page 11, line 10
defined in Section xxxxx in ASAP [3]. 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-specific Data.... | Policy Type | Reserved |
+-+-+-+-+-+-+-+-+------------------------------------------------ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 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 Data
fields. fields.
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.
skipping to change at page 12, line 15 skipping to change at page 12, line 26
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.
3.6.2. Least Used Policy 3.6.2. Least Used Policy
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Param Type = 0x6 | Length = 0x8 | | Param Type = 0x6 | Length = 0x8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Policy=0x2 | Load | | Policy=0x2 | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-------------------------------+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Load |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Load: 24 bits (signed integer) Reserved: 24 bits
Load: 32 bits (signed integer)
(TBD) (TBD)
3.6.3. Least Used with Degradation Policy 3.6.3. Least Used with Degradation Policy
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Param Type = 0x6 | Length = 0x8 | | Param Type = 0x6 | Length = 0x8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Policy=0x3 | Load | | Policy=0x3 | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-------------------------------+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Load |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Load: 24 bits (signed integer) Reserved: 24 bits
Load: 32 bits (signed integer)
(TBD) (TBD)
3.6.4. Weighted Round Robin Policy 3.6.4. Weighted Round Robin Policy
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Param Type = 0x6 | Length = 0x8 | | Param Type = 0x6 | Length = 0x8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Policy=0x4 | Weight | | Policy=0x4 | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-------------------------------+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Weight |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Load: 24 bits (signed integer) Reserved: 24 bits
Load: 32 bits (signed integer)
(TBD) (TBD)
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 17, line 18 skipping to change at page 17, line 21
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.
other values reserved by IETF other values reserved by IETF
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 42 skipping to change at page 18, line 48
information. information.
3.10.9. Inconsistent Data/Control Configuration Error 3.10.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. Unknown Poor Handle Error 3.10.10. Rejected due to security considerations
This error cause is used by any endpoint to indicate a rejection of a
request due to a failure in security credentials or authorizations.
3.10.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.11. 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
skipping to change at page 25, line 5 skipping to change at page 26, line 5
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
Intellectual Property Statement Full Copyright Statement
Copyright (C) The Internet Society (2006).
This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors
retain all their rights.
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING 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.
Intellectual Property
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 Rights 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; nor does it represent that it has might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79. found in BCP 78 and BCP 79.
skipping to change at page 25, line 29 skipping to change at page 26, line 45
such proprietary rights by implementers or users of this such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr. 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 that may cover technology that may be required to implement rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at this standard. Please address the information to the IETF at
ietf-ipr@ietf.org. ietf-ipr@ietf.org.
Disclaimer of Validity
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING 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.
Copyright Statement
Copyright (C) The Internet Society (2006). This document is subject
to the rights, licenses and restrictions contained in BCP 78, and
except as set forth therein, the authors retain all their rights.
Acknowledgment Acknowledgment
Funding for the RFC Editor function is currently provided by the Funding for the RFC Editor function is provided by the IETF
Internet Society. Administrative Support Activity (IASA).
 End of changes. 24 change blocks. 
44 lines changed or deleted 64 lines changed or added

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