From rserpool-admin@ietf.org  Mon Dec 22 12:39:27 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA26543
	for <rserpool-archive@lists.ietf.org>; Mon, 22 Dec 2003 12:39:27 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AYU1D-0002No-QL; Mon, 22 Dec 2003 12:38:59 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AYU0q-0002NT-3k
	for rserpool@optimus.ietf.org; Mon, 22 Dec 2003 12:38:36 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA26490
	for <rserpool@ietf.org>; Mon, 22 Dec 2003 12:38:32 -0500 (EST)
From: Maureen.Stillman@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AYU0o-0003QE-00
	for rserpool@ietf.org; Mon, 22 Dec 2003 12:38:34 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AYU0n-0003Q7-00
	for rserpool@ietf.org; Mon, 22 Dec 2003 12:38:33 -0500
Received: from mgw-x1.nokia.com ([131.228.20.21])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AYU0m-0003Q4-00
	for rserpool@ietf.org; Mon, 22 Dec 2003 12:38:32 -0500
Received: from esvir05nok.ntc.nokia.com (esvir05nokt.ntc.nokia.com [172.21.143.37])
	by mgw-x1.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id hBMHcV009174
	for <rserpool@ietf.org>; Mon, 22 Dec 2003 19:38:31 +0200 (EET)
Received: from daebh001.NOE.Nokia.com (unverified) by esvir05nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T66abdadad5ac158f2566c@esvir05nok.ntc.nokia.com> for <rserpool@ietf.org>;
 Mon, 22 Dec 2003 19:38:31 +0200
Received: from daebe007.NOE.Nokia.com ([10.241.35.107]) by daebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6747);
	 Mon, 22 Dec 2003 09:38:29 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 22 Dec 2003 11:38:29 -0600
Message-ID: <57A26D272F67A743952F6B4371B8F8110249691F@daebe007.americas.nokia.com>
Thread-Topic: Rserpool minutes for IETF #58
Thread-Index: AcPGbkSBju7VPnbxQa2SMNh2jEEtkQCQ/AcA
To: <rserpool@ietf.org>
X-OriginalArrivalTime: 22 Dec 2003 17:38:29.0885 (UTC) FILETIME=[69A7E2D0:01C3C8B2]
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.7 required=5.0 tests=AWL,BIZ_TLD,NO_REAL_NAME 
	autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Subject: [Rserpool] FW: Rserpool minutes for IETF #58
Sender: rserpool-admin@ietf.org
Errors-To: rserpool-admin@ietf.org
X-BeenThere: rserpool@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=unsubscribe>
List-Id: Reliable Server Pooling <rserpool.ietf.org>
List-Post: <mailto:rserpool@ietf.org>
List-Help: <mailto:rserpool-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable

Here are the minutes.  Send any comments, however, they are already in =
the proceedings.  Sorry I didn't get from the group comments before the =
deadline.

Happy holidays.

-- maureen

-----Original Message-----
From: Stillman Maureen (NES/Ithaca)=20
Sent: Friday, December 19, 2003 3:26 PM
To: 'proceedings@ietf.org'
Cc: jon.peterson@neustar.biz; 'mankin@psg.com'; 'lyong@ciena.com'
Subject: Rserpool minutes for IETF #58


Reliable Server Pooling WG (rserpool)
=20
Monday, November 10, 2003
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D
=20
 CHAIRs:
 Lyndon Ong <lyong@ciena.com>
 Maureen Stillman <Maureen.Stillman@nokia.com>


http://www.ietf.org/internet-drafts/draft-conrad-rserpool-service-02.txt

The Rserpool services draft is still under construction.     Two modes =
are defined: basic and enhanced.  Basic just performs server selection, =
that is, it uses a pool handle to get an IP address and ports of =
servers.  Then the application must take care of all failure detection =
etc.  Enhanced mode uses TCP+shim or SCTP. Data is transported through =
RSERPOOL service.  The next draft needs to be reviewed as there have =
been a number of changes since the -02 draft.

There have been a number of requests for a socket layer defined to make =
Rserpool more easily accessible to implementers.  A high availability =
socket layer would be a useful addition.  Some volunteers for a draft =
were identified.
=20
http://www.ietf.org/internet-drafts/draft-rserpool-tcpmapping-00.txt
There have been no changes to the TCP Mapping document.  The references =
in it need to be updated.  This document is considered stable at this =
point.

http://www.ietf.org/internet-drafts/draft-ietf-rserpool-arch-07.txt

Rserpool architecture document has been submitted to the IESG for =
review.  It was updated to point to the security threat document in the =
security considerations section.  Comments received during last call =
were incorporated into the document before it was sent to the IESG for =
review.

http://www.ietf.org/internet-drafts/draft-ietf-rserpool-common-param-04.t=
xt
http://www.ietf.org/internet-drafts/draft-ietf-rserpool-asap-07.txt
http://www.ietf.org/internet-drafts/draft-ietf-rserpool-enrp-06.txt

ENRP and ASAP issues and updates were addressed.  Security =
considerations section was added to both ASAP and ENRP based on the work =
of the security design team over the last year.  The decision to use TLS =
as the security mechanism for Rserpool was documented.  A namespace =
consistency audit was added to ENRP.  It was pointed out that the =
databases will not be 100% consistent with each other.  A checksum is =
used to determine if the databases are in synch.  If the checksums do =
not match, then a resynch is required.  The use of multicast is still an =
open issue due to security concerns.  Everyone should read the drafts =
carefully and send any comments.

http://www.ietf.org/internet-drafts/draft-ietf-rserpool-threats-02.txt

The security design team has completed its work after meeting for over a =
year.  The threat document has been submitted to the IESG for review and =
comment.  Several comments were incorporated during last call.  =
Information regarding security of the ENRP namespace needs to be added =
to the ENRP document security considerations section.  One outstanding =
issue is the TLS cipher suite. A MUST implement cipher suite needs to be =
implemented.  This was brought up on the list.  We agreed on AES as MUST =
implement at the meeting. The security design team declares victory and =
has meet all of its objectives.
=20

http://www.ietf.org/internet-drafts/draft-rserpool-applic-01.txt

Applicability Statement draft is waiting on a new revision of the =
rserpool services document.  These documents need to be in =
synchronization.  The draft will be updated to reflect the changes in =
services.


http://www.ietf.org/internet-drafts/draft-xie-rserpool-redundancy-model-0=
0.txt

Rserpool redundancy model support is not sufficient to support some =
commonly deployed high availability systems.
This draft defines an extension to the load sharing policy to support an =
advanced N+M or N-way redundancy model.  There was a request to =
incorporate this draft into ASAP/ENRP.  There is potential IPR on this =
draft.  Motorola will clarify the IPR issue.  Decision will be made =
after Motorola provides more information on its IPR claim.


_______________________________________________
rserpool mailing list
rserpool@ietf.org
https://www1.ietf.org/mailman/listinfo/rserpool


From exim@www1.ietf.org  Mon Dec 22 12:39:28 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA26559
	for <rserpool-archive@odin.ietf.org>; Mon, 22 Dec 2003 12:39:28 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AYU1E-0002OA-MY
	for rserpool-archive@odin.ietf.org; Mon, 22 Dec 2003 12:39:01 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hBMHd0QO009179
	for rserpool-archive@odin.ietf.org; Mon, 22 Dec 2003 12:39:00 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AYU1D-0002No-QL; Mon, 22 Dec 2003 12:38:59 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AYU0q-0002NT-3k
	for rserpool@optimus.ietf.org; Mon, 22 Dec 2003 12:38:36 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA26490
	for <rserpool@ietf.org>; Mon, 22 Dec 2003 12:38:32 -0500 (EST)
From: Maureen.Stillman@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AYU0o-0003QE-00
	for rserpool@ietf.org; Mon, 22 Dec 2003 12:38:34 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AYU0n-0003Q7-00
	for rserpool@ietf.org; Mon, 22 Dec 2003 12:38:33 -0500
Received: from mgw-x1.nokia.com ([131.228.20.21])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AYU0m-0003Q4-00
	for rserpool@ietf.org; Mon, 22 Dec 2003 12:38:32 -0500
Received: from esvir05nok.ntc.nokia.com (esvir05nokt.ntc.nokia.com [172.21.143.37])
	by mgw-x1.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id hBMHcV009174
	for <rserpool@ietf.org>; Mon, 22 Dec 2003 19:38:31 +0200 (EET)
Received: from daebh001.NOE.Nokia.com (unverified) by esvir05nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T66abdadad5ac158f2566c@esvir05nok.ntc.nokia.com> for <rserpool@ietf.org>;
 Mon, 22 Dec 2003 19:38:31 +0200
Received: from daebe007.NOE.Nokia.com ([10.241.35.107]) by daebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6747);
	 Mon, 22 Dec 2003 09:38:29 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 22 Dec 2003 11:38:29 -0600
Message-ID: <57A26D272F67A743952F6B4371B8F8110249691F@daebe007.americas.nokia.com>
Thread-Topic: Rserpool minutes for IETF #58
Thread-Index: AcPGbkSBju7VPnbxQa2SMNh2jEEtkQCQ/AcA
To: <rserpool@ietf.org>
X-OriginalArrivalTime: 22 Dec 2003 17:38:29.0885 (UTC) FILETIME=[69A7E2D0:01C3C8B2]
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.7 required=5.0 tests=AWL,BIZ_TLD,NO_REAL_NAME 
	autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Subject: [Rserpool] FW: Rserpool minutes for IETF #58
Sender: rserpool-admin@ietf.org
Errors-To: rserpool-admin@ietf.org
X-BeenThere: rserpool@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=unsubscribe>
List-Id: Reliable Server Pooling <rserpool.ietf.org>
List-Post: <mailto:rserpool@ietf.org>
List-Help: <mailto:rserpool-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable

Here are the minutes.  Send any comments, however, they are already in =
the proceedings.  Sorry I didn't get from the group comments before the =
deadline.

Happy holidays.

-- maureen

-----Original Message-----
From: Stillman Maureen (NES/Ithaca)=20
Sent: Friday, December 19, 2003 3:26 PM
To: 'proceedings@ietf.org'
Cc: jon.peterson@neustar.biz; 'mankin@psg.com'; 'lyong@ciena.com'
Subject: Rserpool minutes for IETF #58


Reliable Server Pooling WG (rserpool)
=20
Monday, November 10, 2003
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D
=20
 CHAIRs:
 Lyndon Ong <lyong@ciena.com>
 Maureen Stillman <Maureen.Stillman@nokia.com>


http://www.ietf.org/internet-drafts/draft-conrad-rserpool-service-02.txt

The Rserpool services draft is still under construction.     Two modes =
are defined: basic and enhanced.  Basic just performs server selection, =
that is, it uses a pool handle to get an IP address and ports of =
servers.  Then the application must take care of all failure detection =
etc.  Enhanced mode uses TCP+shim or SCTP. Data is transported through =
RSERPOOL service.  The next draft needs to be reviewed as there have =
been a number of changes since the -02 draft.

There have been a number of requests for a socket layer defined to make =
Rserpool more easily accessible to implementers.  A high availability =
socket layer would be a useful addition.  Some volunteers for a draft =
were identified.
=20
http://www.ietf.org/internet-drafts/draft-rserpool-tcpmapping-00.txt
There have been no changes to the TCP Mapping document.  The references =
in it need to be updated.  This document is considered stable at this =
point.

http://www.ietf.org/internet-drafts/draft-ietf-rserpool-arch-07.txt

Rserpool architecture document has been submitted to the IESG for =
review.  It was updated to point to the security threat document in the =
security considerations section.  Comments received during last call =
were incorporated into the document before it was sent to the IESG for =
review.

http://www.ietf.org/internet-drafts/draft-ietf-rserpool-common-param-04.t=
xt
http://www.ietf.org/internet-drafts/draft-ietf-rserpool-asap-07.txt
http://www.ietf.org/internet-drafts/draft-ietf-rserpool-enrp-06.txt

ENRP and ASAP issues and updates were addressed.  Security =
considerations section was added to both ASAP and ENRP based on the work =
of the security design team over the last year.  The decision to use TLS =
as the security mechanism for Rserpool was documented.  A namespace =
consistency audit was added to ENRP.  It was pointed out that the =
databases will not be 100% consistent with each other.  A checksum is =
used to determine if the databases are in synch.  If the checksums do =
not match, then a resynch is required.  The use of multicast is still an =
open issue due to security concerns.  Everyone should read the drafts =
carefully and send any comments.

http://www.ietf.org/internet-drafts/draft-ietf-rserpool-threats-02.txt

The security design team has completed its work after meeting for over a =
year.  The threat document has been submitted to the IESG for review and =
comment.  Several comments were incorporated during last call.  =
Information regarding security of the ENRP namespace needs to be added =
to the ENRP document security considerations section.  One outstanding =
issue is the TLS cipher suite. A MUST implement cipher suite needs to be =
implemented.  This was brought up on the list.  We agreed on AES as MUST =
implement at the meeting. The security design team declares victory and =
has meet all of its objectives.
=20

http://www.ietf.org/internet-drafts/draft-rserpool-applic-01.txt

Applicability Statement draft is waiting on a new revision of the =
rserpool services document.  These documents need to be in =
synchronization.  The draft will be updated to reflect the changes in =
services.


http://www.ietf.org/internet-drafts/draft-xie-rserpool-redundancy-model-0=
0.txt

Rserpool redundancy model support is not sufficient to support some =
commonly deployed high availability systems.
This draft defines an extension to the load sharing policy to support an =
advanced N+M or N-way redundancy model.  There was a request to =
incorporate this draft into ASAP/ENRP.  There is potential IPR on this =
draft.  Motorola will clarify the IPR issue.  Decision will be made =
after Motorola provides more information on its IPR claim.


_______________________________________________
rserpool mailing list
rserpool@ietf.org
https://www1.ietf.org/mailman/listinfo/rserpool



