draft-ietf-rserpool-common-param-04.txt   draft-ietf-rserpool-common-param-05.txt 
Network Working Group R. Stewart Network Working Group R. Stewart
Internet-Draft Cisco Systems, Inc. Internet-Draft Cisco Systems, Inc.
Expires: November 12, 2003 Q. Xie Expires: April 22, 2004 Q. Xie
Motorola, Inc. Motorola, Inc.
M. Stillman M. Stillman
Nokia Nokia
M. Tuexen M. Tuexen
Siemens AG October 23, 2003
May 14, 2003
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-04.txt draft-ietf-rserpool-common-param-05.txt
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026. all provisions of Section 10 of RFC2026.
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 other
groups may also distribute working documents as Internet-Drafts. groups may also distribute working documents as Internet-Drafts.
skipping to change at page 1, line 37 skipping to change at page 1, line 36
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 http://
www.ietf.org/ietf/1id-abstracts.txt. 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 November 12, 2003. This Internet-Draft will expire on April 22, 2004.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2003). All Rights Reserved. Copyright (C) The Internet Society (2003). 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)
skipping to change at page 2, line 36 skipping to change at page 2, line 36
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 . . . . . . . . . . . . . . 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.11 Cookie Parameter . . . . . . . . . . . . . . . . . . . . . 18 3.11 Cookie Parameter . . . . . . . . . . . . . . . . . . . . . 18
3.12 PE Identifier Parameter . . . . . . . . . . . . . . . . . 19 3.12 PE Identifier Parameter . . . . . . . . . . . . . . . . . 19
4. Common Message Formats . . . . . . . . . . . . . . . . . . 20 3.13 PE Checksum Parameter . . . . . . . . . . . . . . . . . . 19
5. Security Considerations . . . . . . . . . . . . . . . . . 22 4. Common Message Formats . . . . . . . . . . . . . . . . . . 21
Normative References . . . . . . . . . . . . . . . . . . . 23 5. Security Considerations . . . . . . . . . . . . . . . . . 23
Authors' Addresses . . . . . . . . . . . . . . . . . . . . 23 Normative References . . . . . . . . . . . . . . . . . . . 24
Intellectual Property and Copyright Statements . . . . . . 25 Authors' Addresses . . . . . . . . . . . . . . . . . . . . 24
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 Name Resolution Protocol (ENRP) [5] 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
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 keywords MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD,
SHOULD NOT, RECOMMENDED, NOT RECOMMENDED, MAY, and OPTIONAL, when SHOULD NOT, RECOMMENDED, NOT RECOMMENDED, MAY, and OPTIONAL, when
they appear in this document, are to be interpreted as described in they appear in this document, are to be interpreted as described in
RFC2119 [2]. RFC2119 [2].
2. Parameters in General 2. Parameters in General
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-specific Data.... | Policy Type | Policy-specific Data....
skipping to change at page 11, line 42 skipping to change at page 11, line 42
0x2 Least Used 0x2 Least Used
0x3 Least Used with Degradation (a.k.a. dog pile) 0x3 Least Used with Degradation (a.k.a. dog pile)
0x4 Weighted Round Robin 0x4 Weighted Round Robin
others (reserved by IETF) others (reserved by IETF)
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 the following subsections. The enforcement described in detail in the following subsections. The enforcement
rules and handling procedures of these policies are defined in rules and handling procedures of these policies are defined in
Section xxxxx in ASAP [4]. Section xxxxx in ASAP [3].
3.6.1 Round Robin Policy 3.6.1 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=0x1 | (reserved) | | Policy=0x1 | (reserved) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-------------------------------+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-------------------------------+
skipping to change at page 15, line 32 skipping to change at page 15, line 32
: Server Transport : : Server Transport :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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 (unsiged 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 18, line 17 skipping to change at page 18, line 17
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 PE Identifier it chooses has already been registering PE that the PE Identifier it chooses has already been
used by another PE in the pool. There is no cause specific used by another PE in the pool. There is no cause specific
information. information.
3.10.6 Inconsistent Pool Policy Error 3.10.6 Inconsistent Pool Policy 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 Pool Policy it chooses does not match the registering PE that the Pool Policy it chooses does not match the
overall policy of the pool. A Pool Member Selection Policy TLV (see overall policy of the pool. A Pool Member Selection Policy TLV (see
Section Section 3.6) that indicates the overall pool policy is Section 3.6) that indicates the overall pool policy is included as
included as cause specific information. cause specific information.
3.10.7 Lack of Resources Error 3.10.7 Lack of Resources Error
This error cause is used to indicate that the sender does not have This error cause is used to indicate that the sender does not have
certain resources to perform a requested function. There is no cause certain resources to perform a requested function. There is no cause
specific information. specific information.
3.10.8 Inconsistent Transport Type Error 3.10.8 Inconsistent Transport Type 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
skipping to change at page 19, line 39 skipping to change at page 19, line 39
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] for recommendations on when it starts up. See Section ???? in ASAP [3] for recommendations
PE identifier generation. on PE identifier generation.
3.13 PE Checksum Parameter
This parameter defines a TLV that carries a PE Checksum.
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 0xd | Length=0x8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| PE Checksum |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
PE Checksum: 32 bits (unsigned integer)
An overall checksum of all PEs in the current namespace owned by an
ENRP server (which is normally the sender of this TLV). The
definition and calculation of this checksum is defined in Section
???? 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 20, line 36 skipping to change at page 21, line 36
255 is reserved for future use as an extension field. 255 is reserved for future use as an extension field.
Message Types are encoded such that the highest-order two bits Message Types are encoded such that the highest-order two bits
specify the action that must be taken if the message receiver does specify the action that must be taken if the message receiver does
not recognize the Message Type. not recognize the Message Type.
00 Stop processing this message and discard it. 00 Stop processing this message and discard it.
01 Stop processing this message and discard it, and report the 01 Stop processing this message and discard it, and report the
unrecognized message in an 'Unrecognized Message' error (see unrecognized message in an 'Unrecognized Message' error (see
Section Section 3.10.3). Section 3.10.3).
10 reserved. 10 reserved.
11 reserved. 11 reserved.
Message Flags: 8 bits Message Flags: 8 bits
The usage of these bits depends on the message type as given by the The usage of these bits depends on the message type as given by the
Message Type. Unless otherwise specified, they are set to zero on Message Type. Unless otherwise specified, they are set to zero on
transmit and are ignored on receipt. transmit and are ignored on receipt.
skipping to change at page 22, line 9 skipping to change at page 23, line 9
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. Details
on ENRP and ASAP security constraints are addressed in ENRP [5] and on ENRP and ASAP security constraints are addressed in ENRP [4] and
ASAP [4] . ASAP [3] .
Normative References 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., Morneault, K., Sharp, C., Schwarzbauer, [3] Stewart, R., Xie, Q., Stillman, M. and M. Tuexen, "Aggregate
H., Taylor, T., Rytina, I., Kalla, M., Zhang, L. and V. Paxson, Server Access Protocol (ASAP)", draft-ietf-rserpool-asap-08
"Stream Control Transmission Protocol", RFC 2960, October 2000. (work in progress), October 2003.
[4] Stewart, R., Xie, Q. and M. Stillman, "Aggregate Server Access
Protocol (ASAP)", draft-ietf-rserpool-common-param-01 (work in
progress), May 2002.
[5] 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-04 (work in Protocol (ENRP)", draft-ietf-rserpool-enrp-07 (work in
progress), May 2002. progress), October 2003.
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 24, line 4 skipping to change at page 24, line 41
EMail: rrs@cisco.com EMail: rrs@cisco.com
Qiaobing Xie Qiaobing Xie
Motorola, Inc. Motorola, Inc.
1501 W. Shure Drive, #2309 1501 W. Shure Drive, #2309
Arlington Heights, IL 60004 Arlington Heights, IL 60004
USA USA
Phone: +1-847-632-3028 Phone: +1-847-632-3028
EMail: qxie1@email.mot.com EMail: qxie1@email.mot.com
Maureen Stillman Maureen Stillman
Nokia Nokia
127 W. State Street 127 W. State Street
Ithaca, NY 14850 Ithaca, NY 14850
USA USA
Phone: +1-607-273-0724 Phone: +1-607-273-0724
EMail: maureen.stillman@nokia.com EMail: maureen.stillman@nokia.com
Michael Tuexen Michael Tuexen
Siemens AG
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 or other rights that might be claimed to
 End of changes. 

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