draft-ietf-rserpool-common-param-08.txt   draft-ietf-rserpool-common-param-09.txt 
Network Working Group R. Stewart Network Working Group R. Stewart
Internet-Draft Cisco Systems, Inc. Internet-Draft Cisco Systems, Inc.
Expires: August 22, 2005 Q. Xie Expires: January 19, 2006 Q. Xie
Motorola, Inc. Motorola, Inc.
M. Stillman M. Stillman
Nokia Nokia
M. Tuexen M. Tuexen
February 18, 2005 Muenster Univ. of Applied Sciences
July 18, 2005
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-08.txt draft-ietf-rserpool-common-param-09.txt
Status of this Memo Status of this Memo
This document is an Internet-Draft and is subject to all provisions By submitting this Internet-Draft, each author represents that any
of Section 3 of RFC 3667. By submitting this Internet-Draft, each applicable patent or other IPR claims of which he or she is aware
author represents that any applicable patent or other IPR claims of have been or will be disclosed, and any of which he or she becomes
which he or she is aware have been or will be disclosed, and any of aware will be disclosed, in accordance with Section 6 of BCP 79.
which he or she 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 Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as other groups may also distribute working documents as Internet-
Internet-Drafts. 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 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 22, 2005. This Internet-Draft will expire on January 19, 2006.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2005). Copyright (C) The Internet Society (2005).
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 24 skipping to change at page 2, line 23
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 . . . . . . . . . . . . . . . . . . 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 . . . . . . . . . . . . . 12 3.6.4 Weighted Round Robin Policy . . . . . . . . . . . . . 12
3.7 Pool Handle Parameter . . . . . . . . . . . . . . . . . . 12 3.7 Pool Handle Parameter . . . . . . . . . . . . . . . . . . 13
3.8 Pool Element Parameter . . . . . . . . . . . . . . . . . . 13 3.8 Pool Element Parameter . . . . . . . . . . . . . . . . . . 13
3.9 Server Information Parameter . . . . . . . . . . . . . . . 14 3.9 Server Information Parameter . . . . . . . . . . . . . . . 15
3.10 Operation Error Parameter . . . . . . . . . . . . . . . . 15 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 . . . . . . . . . . . . . . . . . 17
3.10.5 Non-unique PE Identifier Error . . . . . . . . . . . . 17 3.10.5 Non-unique PE Identifier Error . . . . . . . . . . . . 18
3.10.6 Inconsistent Pool Policy Error . . . . . . . . . . . . 17 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 Unknown Poor Handle Error . . . . . . . . . . . . . 18
3.11 Cookie Parameter . . . . . . . . . . . . . . . . . . . . . 18 3.11 Cookie Parameter . . . . . . . . . . . . . . . . . . . . . 18
3.12 PE Identifier Parameter . . . . . . . . . . . . . . . . . 19 3.12 PE Identifier Parameter . . . . . . . . . . . . . . . . . 19
3.13 PE Checksum Parameter . . . . . . . . . . . . . . . . . . 19 3.13 PE Checksum Parameter . . . . . . . . . . . . . . . . . . 19
4. Common Message Formats . . . . . . . . . . . . . . . . . . . . 20 4. Common Message Formats . . . . . . . . . . . . . . . . . . . . 21
5. Security Considerations . . . . . . . . . . . . . . . . . . . 22 5. Security Considerations . . . . . . . . . . . . . . . . . . . 23
6. Normative References . . . . . . . . . . . . . . . . . . . . . 22 6. Normative References . . . . . . . . . . . . . . . . . . . . . 23
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 22 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 23
Intellectual Property and Copyright Statements . . . . . . . . 24 Intellectual Property and Copyright Statements . . . . . . . . 25
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 18, line 23 skipping to change at page 18, line 38
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.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 sent in its registration is inconsistent to the pool's overall data/
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 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
skipping to change at page 19, line 31 skipping to change at page 19, line 49
when it starts up. See Section ???? in ASAP [3] 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=0x8 | | Type = 0xd | Length=0x6 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| PE Checksum | | PE Checksum | Padding |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
PE Checksum: 16 bits (unsigned integer)
PE Checksum: 32 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
???? in ENRP [4]. 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 22, line 20 skipping to change at page 23, line 20
[4] and ASAP [3] . [4] and ASAP [3] .
6. Normative References 6. Normative References
[1] Bradner, S., "The Internet Standards Process -- Revision 3", [1] Bradner, S., "The Internet Standards Process -- Revision 3",
BCP 9, RFC 2026, October 1996. BCP 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)", Server Access Protocol (ASAP)", draft-ietf-rserpool-asap-12
Internet-Draft draft-ietf-rserpool-asap-11, February 2005. (work in progress), July 2005.
[4] Xie, Q., Stewart, R., Stillman, M., Tuexen, M. and A. Silverton, [4] Xie, Q., Stewart, R., Stillman, M., Tuexen, M., and A.
"Endpoint Handlespace Redundancy Protocol (ENRP)", Silverton, "Endpoint Handlespace Redundancy Protocol (ENRP)",
Internet-Draft draft-ietf-rserpool-enrp-11, February 2005. draft-ietf-rserpool-enrp-12 (work in progress), July 2005.
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
skipping to change at page 23, line 14 skipping to change at page 24, line 14
Maureen Stillman Maureen Stillman
Nokia Nokia
127 W. State Street 127 W. State Street
Ithaca, NY 14850 Ithaca, NY 14850
USA USA
Phone: Phone:
Email: maureen.stillman@nokia.com Email: maureen.stillman@nokia.com
Michael Tuexen Michael Tuexen
Muenster Univ. of Applied Sciences
Stegerwaldstr. 39
48565 Steinfurt
Germany Germany
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 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
 End of changes. 

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