Rserpool minutes from IETF #60

Comments anyone?

-- maureen

Rserpool report from IETF #60

Approximately 30 people attended the WG meeting held on 8/5/2004.

A policies draft was presented (draft-tuexen-rserpool-policies-00.txt).  This draft presents new policies for reliable server pooling.  The proposal was to take the pool policies currently included in the ASAP draft and separate them into a separate policies draft.  This allows the stable base ASAP protocol specification to be separated from the pool policies which are subject to further investigation and more substantial changes.  Consensus was reached in the meeting to make this change.  We will take the proposal to the mailing list.

The SASP Server Application State protocol was presented (draft-bivens-sasp-00.txt).  SASP is focused on a specific application which is load balancing among a group of servers.  The architecture of SASP was presented and it was compared to Rserpool.  This protocol has some overlap with Rserpool and many of the same goals and requirements.    The meeting participants reached consensus to work with the author of SASP on a collaborative effort as SASP brings an important application's set of requirements, namely load balancers, into the protocol development process.  An offline discussion followed the agreement.  

A brief update was presented on the following documents with minor changes since the last draft:

These documents are currently in AD review.

Rserpool comparison
draft-ietf-rserpool-comp-07.txt
Rserpool Architecture 
draft-ietf-rserpool-arch-07.txt
Security Threats
draft-ietf-rserpool-threats-03.txt

These documents are under construction:

Rserpool services
draft-ietf-rserpool-service-01.txt
ASAP
draft-ietf-rserpool-asap-09.txt
ENRP
draft-ietf-rserpool-enrp-09.txt
Rserpool applicability 
draft-ietf-rserpool-applic-02.txt

The group was encouraged to read the latest drafts and send comments to the mailing list.

The ASAP and ENRP protocols are fairly stable at this time.  Rserpool implementations are being discussed on the mailing list since IETF #59 and changes have been suggested to the protocols as a result.  These changes were made to the latest drafts.  A presentation on the current status of the implementations gave details of how to get open source and tools such as Ethereal which has been updated to dissect ENRP and ASAP packets.

We feel that the WG is moving ahead and making good progress.  

-- maureen