draft-ietf-rserpool-common-param-11.txt   draft-ietf-rserpool-common-param-12.txt 
Network Working Group R. Stewart Network Working Group R. Stewart
Internet-Draft Cisco Systems, Inc. Internet-Draft Cisco Systems, Inc.
Intended status: Informational Q. Xie Intended status: Experimental Q. Xie
Expires: April 20, 2007 Motorola, Inc. Expires: January 10, 2008 Motorola, Inc.
M. Stillman M. Stillman
Nokia Nokia
M. Tuexen M. Tuexen
Muenster Univ. of Applied Sciences Muenster Univ. of Applied Sciences
October 17, 2006 July 9, 2007
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-11.txt draft-ietf-rserpool-common-param-12.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 April 20, 2007. This Internet-Draft will expire on January 10, 2008.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2006). Copyright (C) The IETF Trust (2007).
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
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 . . . . . . . . . . . . . . . . . . 7
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 . . . . . . . . . . . . . . . . . 12 3.7. Pool Handle Parameter . . . . . . . . . . . . . . . . . . 11
3.6.2. Least Used Policy . . . . . . . . . . . . . . . . . . 12 3.8. Pool Element Parameter . . . . . . . . . . . . . . . . . . 12
3.6.3. Least Used with Degradation Policy . . . . . . . . . 12 3.9. Server Information Parameter . . . . . . . . . . . . . . . 13
3.6.4. Weighted Round Robin Policy . . . . . . . . . . . . . 13 3.10. Operation Error Parameter . . . . . . . . . . . . . . . . 14
3.7. Pool Handle Parameter . . . . . . . . . . . . . . . . . . 13 3.10.1. Unspecified Error . . . . . . . . . . . . . . . . . . 16
3.8. Pool Element Parameter . . . . . . . . . . . . . . . . . . 14 3.10.2. Unrecognized Parameter Error . . . . . . . . . . . . 16
3.9. Server Information Parameter . . . . . . . . . . . . . . . 15 3.10.3. Unrecognized Message Error . . . . . . . . . . . . . 16
3.10. Operation Error Parameter . . . . . . . . . . . . . . . . 16 3.10.4. Invalid Values Error . . . . . . . . . . . . . . . . 16
3.10.1. Unspecified Error . . . . . . . . . . . . . . . . . . 17 3.10.5. Non-unique PE Identifier Error . . . . . . . . . . . 16
3.10.2. Unrecognized Parameter Error . . . . . . . . . . . . 17 3.10.6. Inconsistent Pool Policy Error . . . . . . . . . . . 16
3.10.3. Unrecognized Message Error . . . . . . . . . . . . . 17 3.10.7. Lack of Resources Error . . . . . . . . . . . . . . . 16
3.10.4. Invalid Values Error . . . . . . . . . . . . . . . . 18 3.10.8. Inconsistent Transport Type Error . . . . . . . . . . 16
3.10.5. Non-unique PE Identifier Error . . . . . . . . . . . 18 3.10.9. Inconsistent Data/Control Configuration Error . . . . 17
3.10.6. Inconsistent Pool Policy Error . . . . . . . . . . . 18 3.10.10. Rejected due to security considerations . . . . . . . 17
3.10.7. Lack of Resources Error . . . . . . . . . . . . . . . 18 3.10.11. Unknown Poor Handle Error . . . . . . . . . . . . . . 17
3.10.8. Inconsistent Transport Type Error . . . . . . . . . . 18 3.11. Cookie Parameter . . . . . . . . . . . . . . . . . . . . . 17
3.10.9. Inconsistent Data/Control Configuration Error . . . . 18 3.12. PE Identifier Parameter . . . . . . . . . . . . . . . . . 17
3.10.10. Rejected due to security considerations . . . . . . . 18 3.13. PE Checksum Parameter . . . . . . . . . . . . . . . . . . 18
3.10.11. Unknown Poor Handle Error . . . . . . . . . . . . . . 19 4. Common Message Formats . . . . . . . . . . . . . . . . . . . . 19
3.11. Cookie Parameter . . . . . . . . . . . . . . . . . . . . . 19 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 21
3.12. PE Identifier Parameter . . . . . . . . . . . . . . . . . 19 5.1. A New Table for RSerPool Parameter Types . . . . . . . . . 21
3.13. PE Checksum Parameter . . . . . . . . . . . . . . . . . . 20 5.2. A New Table for RSerPool Error Causes . . . . . . . . . . 21
4. Common Message Formats . . . . . . . . . . . . . . . . . . . . 21 6. Security Considerations . . . . . . . . . . . . . . . . . . . 23
5. Security Considerations . . . . . . . . . . . . . . . . . . . 23 7. Normative References . . . . . . . . . . . . . . . . . . . . . 24
6. Normative References . . . . . . . . . . . . . . . . . . . . . 24
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 25 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 25
Intellectual Property and Copyright Statements . . . . . . . . . . 26 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) [4] in conjunction with the
Endpoint Handlespace Redundancy Protocol (ENRP) [4] provides a high Endpoint Handlespace Redundancy Protocol (ENRP) [5] 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 [3] and ENRP [4] documents. refer to the respective ASAP [4] and ENRP [5] 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 6, line 24 skipping to change at page 6, line 24
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 0xd - PE Checksum
others - (reserved by IETF) others - (reserved by IETF)
Figure 2
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.
The total length of a parameter (including Type, Parameter Length and The total length of a parameter (including Type, Parameter Length and
Value fields) MUST be a multiple of 4 bytes. If the length of the 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
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 [3]. defined in Section xxxxx in ASAP [4].
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 | Reserved | | Policy Type |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Policy-specific Data | | 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.
Policy Type: 8 bits (unsigned integer) Policy Type: 32 bits (unsigned integer)
Specifies the type of selection policy. Specifies the type of selection policy.
Currently defined policy types are:
Value Policy
----- ---------
0x0 (reserved by IETF)
0x1 Round Robin
0x2 Least Used
0x3 Least Used with Degradation (a.k.a. dog pile)
0x4 Weighted Round Robin
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 Policies [6].
rules and handling procedures of these policies are defined in
Section xxxxx in ASAP [3].
3.6.1. Round Robin Policy
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Param Type = 0x6 | Length = 0x8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Policy=0x1 | (reserved) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-------------------------------+
Reserved: 24 bits
MUST be set to 0's by sender and ignored by the receiver.
3.6.2. Least Used Policy
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Param Type = 0x6 | Length = 0x8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Policy=0x2 | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Load |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Reserved: 24 bits
Load: 32 bits (signed integer)
(TBD)
3.6.3. Least Used with Degradation Policy
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Param Type = 0x6 | Length = 0x8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Policy=0x3 | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Load |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Reserved: 24 bits
Load: 32 bits (signed integer)
(TBD)
3.6.4. Weighted Round Robin Policy
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Param Type = 0x6 | Length = 0x8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Policy=0x4 | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Weight |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Reserved: 24 bits
Load: 32 bits (signed integer)
(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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 0x7 | Length=variable | | Type = 0x7 | Length=variable |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 15, line 49 skipping to change at page 14, line 8
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 (unsigned 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 [4] . ENRP [5] .
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.
Server Transport: Server Transport:
skipping to change at page 17, line 24 skipping to change at page 15, line 35
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. 10 Rejected due to security considerations.
other values reserved by IETF other values reserved by IETF
Figure 16
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
This field carries the details of the error condition. This field carries the details of the error condition.
skipping to change at page 19, line 49 skipping to change at page 18, line 16
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 [3] for recommendations when it starts up. See Section ???? in ASAP [4] 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=0x6 | | Type = 0xd | Length=0x6 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| PE Checksum | Padding | | PE Checksum | Padding |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
PE Checksum: 16 bits (unsigned integer) PE Checksum: 16 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
3.11.2 in ENRP [4]. 3.11.2 in ENRP [5].
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 23, line 5 skipping to change at page 21, line 5
transferred in the message. The usage and format of this field is transferred in the message. The usage and format of this field is
dependent on the Message Type. dependent on the Message Type.
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. IANA Considerations
[NOTE to RFC-Editor:
"RFCXXXX" is to be replaced by the RFC number you assign this
document.
]
This document (RFCXXX) is the reference for all registrations
described in this section. All registrations need to be listed on an
RSerPool specific page.
5.1. A New Table for RSerPool Parameter Types
RSerPool Parameter Types have to be maintained by IANA. Thirteen
initial values should be assigned by IANA as described in Figure 2.
This requires a new table "RSerPool Parameter Types":
Type Message Name Reference
----- ------------------------- ---------
0x0 (reserved by IETF) RFCXXXX
0x1 IPv4 Address RFCXXXX
0x2 IPv6 Address RFCXXXX
0x3 SCTP Transport RFCXXXX
0x4 TCP Transport RFCXXXX
0x5 UDP Transport RFCXXXX
0x6 Pool Member Selection Policy RFCXXXX
0x7 Pool Handle RFCXXXX
0x8 Pool Element RFCXXXX
0x9 Server Information RFCXXXX
0xa Operation Error RFCXXXX
0xb Cookie RFCXXXX
0xc PE Identifier RFCXXXX
0xd PE Checksum RFCXXXX
others (reserved by IETF) RFCXXXX
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
unique. The "Specification Required" policy of RFC2434 [3] MUST be
applied.
5.2. A New Table for RSerPool Error Causes
RSerPool Error Causes have to be maintained by IANA. Eleven initial
values should be assigned by IANA as described in Figure 16. This
requires a new table "RSerPool Error Causes":
Cause Cause Name Reference
----- ------------------------- ---------
0 Unspecified Error RFCXXXX
1 Unrecognized Parameter RFCXXXX
2 Unrecognized Message RFCXXXX
3 Invalid Values RFCXXXX
4 Non-unique PE Identifier RFCXXXX
5 Inconsistent Pooling Policy RFCXXXX
6 Lack of Resources RFCXXXX
7 Inconsistent Transport Type RFCXXXX
8 Inconsistent Data/Control Configuration RFCXXXX
9 Unknown Poor Handle RFCXXXX
10 Rejected due to security considerations RFCXXXX
others (reserved by IETF) RFCXXXX
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
unique. The "Specification Required" policy of RFC2434 [3] MUST be
applied.
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 ENRP Details on ENRP and ASAP security constraints are addressed in ENRP
[4] and ASAP [3] . [5] and ASAP [4] .
6. Normative References 7. 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] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA
Considerations Section in RFCs", BCP 26, RFC 2434, October 1998.
[4] Stewart, R., Xie, Q., Stillman, M., and M. Tuexen, "Aggregate
Server Access Protocol (ASAP)", draft-ietf-rserpool-asap-12 Server Access Protocol (ASAP)", draft-ietf-rserpool-asap-12
(work in progress), July 2005. (work in progress), July 2005.
[4] Xie, Q., Stewart, R., Stillman, M., Tuexen, M., and A. [5] Xie, Q., Stewart, R., Stillman, M., Tuexen, M., and A.
Silverton, "Endpoint Handlespace Redundancy Protocol (ENRP)", Silverton, "Endpoint Handlespace Redundancy Protocol (ENRP)",
draft-ietf-rserpool-enrp-12 (work in progress), July 2005. draft-ietf-rserpool-enrp-12 (work in progress), July 2005.
[6] Tuexen, M. and T. Dreibholz, "Reliable Server Pooling Policies",
draft-ietf-rserpool-policies-04 (work in progress), March 2007.
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
Phone: Phone:
skipping to change at page 26, line 7 skipping to change at page 26, line 7
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
Full Copyright Statement Full Copyright Statement
Copyright (C) The Internet Society (2006). Copyright (C) The IETF Trust (2007).
This document is subject to the rights, licenses and restrictions This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors contained in BCP 78, and except as set forth therein, the authors
retain all their rights. retain all their rights.
This document and the information contained herein are provided on an This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Intellectual Property 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
 End of changes. 28 change blocks. 
132 lines changed or deleted 130 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/