From rserpool-admin@ietf.org Mon Oct 6 16:04:25 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA20117 for ; Mon, 6 Oct 2003 16:04:25 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A6baL-0006zZ-8Z; Mon, 06 Oct 2003 16:04:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A6bZc-0006rt-4B for rserpool@optimus.ietf.org; Mon, 06 Oct 2003 16:03:16 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA20008 for ; Mon, 6 Oct 2003 16:03:06 -0400 (EDT) From: Maureen.Stillman@nokia.com Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A6bWv-0002r0-01 for rserpool@ietf.org; Mon, 06 Oct 2003 16:00:29 -0400 Received: from mgw-x1.nokia.com ([131.228.20.21]) by ietf-mx with esmtp (Exim 4.12) id 1A6bLj-0002ko-00 for rserpool@ietf.org; Mon, 06 Oct 2003 15:48:55 -0400 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.6) with ESMTP id h96Jms625009 for ; Mon, 6 Oct 2003 22:48:54 +0300 (EET DST) Received: from daebh001.NOE.Nokia.com (unverified) by esvir05nok.ntc.nokia.com (Content Technologies SMTPRS 4.2.5) with ESMTP id ; Mon, 6 Oct 2003 22:48:54 +0300 Received: from daebe007.NOE.Nokia.com ([172.18.242.211]) by daebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139); Mon, 6 Oct 2003 12:48:52 -0700 X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: RE: [Rserpool] 58th IETF meeting Date: Mon, 6 Oct 2003 14:48:51 -0500 Message-ID: <57A26D272F67A743952F6B4371B8F8110249676A@daebe007.americas.nokia.com> Thread-Topic: [Rserpool] 58th IETF meeting Thread-Index: AcOHY9GB2Bth8OpDR0qhHDG4kDPAaQE3snuw To: , X-OriginalArrivalTime: 06 Oct 2003 19:48:52.0257 (UTC) FILETIME=[DE586110:01C38C42] Content-Transfer-Encoding: quoted-printable 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: , List-Id: Reliable Server Pooling List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable We have a slot on the draft agenda on Monday afternoon, November 10 for = 2 hours 15:30 to 17:30. Subject to change, of course, until the agenda = is finalized. -- maureen -----Original Message----- From: ext Silverton Aron-C1710C [mailto:Aron.J.Silverton@motorola.com] Sent: Tuesday, September 30, 2003 11:00 AM To: 'rserpool@ietf.org' Subject: [Rserpool] 58th IETF meeting Maureen and Lyndon, Any idea when we will meet in Minneapolis? The earlier in the week = would be best for me personally. Regards, Aron Aron J. Silverton Senior Staff Research Engineer Motorola Labs, Networks and Infrastructure Research Motorola, Inc. Telephone: 847-576-8747 =20 Fax: 847-576-3240 mailto:Aron.J.Silverton@motorola.com _______________________________________________ rserpool mailing list rserpool@ietf.org https://www1.ietf.org/mailman/listinfo/rserpool _______________________________________________ rserpool mailing list rserpool@ietf.org https://www1.ietf.org/mailman/listinfo/rserpool From exim@www1.ietf.org Mon Oct 6 16:04:25 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA20128 for ; Mon, 6 Oct 2003 16:04:25 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A6baO-000700-A3 for rserpool-archive@odin.ietf.org; Mon, 06 Oct 2003 16:04:04 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h96K44qm026892 for rserpool-archive@odin.ietf.org; Mon, 6 Oct 2003 16:04:04 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A6baL-0006zZ-8Z; Mon, 06 Oct 2003 16:04:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A6bZc-0006rt-4B for rserpool@optimus.ietf.org; Mon, 06 Oct 2003 16:03:16 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA20008 for ; Mon, 6 Oct 2003 16:03:06 -0400 (EDT) From: Maureen.Stillman@nokia.com Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A6bWv-0002r0-01 for rserpool@ietf.org; Mon, 06 Oct 2003 16:00:29 -0400 Received: from mgw-x1.nokia.com ([131.228.20.21]) by ietf-mx with esmtp (Exim 4.12) id 1A6bLj-0002ko-00 for rserpool@ietf.org; Mon, 06 Oct 2003 15:48:55 -0400 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.6) with ESMTP id h96Jms625009 for ; Mon, 6 Oct 2003 22:48:54 +0300 (EET DST) Received: from daebh001.NOE.Nokia.com (unverified) by esvir05nok.ntc.nokia.com (Content Technologies SMTPRS 4.2.5) with ESMTP id ; Mon, 6 Oct 2003 22:48:54 +0300 Received: from daebe007.NOE.Nokia.com ([172.18.242.211]) by daebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139); Mon, 6 Oct 2003 12:48:52 -0700 X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: RE: [Rserpool] 58th IETF meeting Date: Mon, 6 Oct 2003 14:48:51 -0500 Message-ID: <57A26D272F67A743952F6B4371B8F8110249676A@daebe007.americas.nokia.com> Thread-Topic: [Rserpool] 58th IETF meeting Thread-Index: AcOHY9GB2Bth8OpDR0qhHDG4kDPAaQE3snuw To: , X-OriginalArrivalTime: 06 Oct 2003 19:48:52.0257 (UTC) FILETIME=[DE586110:01C38C42] Content-Transfer-Encoding: quoted-printable 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: , List-Id: Reliable Server Pooling List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable We have a slot on the draft agenda on Monday afternoon, November 10 for = 2 hours 15:30 to 17:30. Subject to change, of course, until the agenda = is finalized. -- maureen -----Original Message----- From: ext Silverton Aron-C1710C [mailto:Aron.J.Silverton@motorola.com] Sent: Tuesday, September 30, 2003 11:00 AM To: 'rserpool@ietf.org' Subject: [Rserpool] 58th IETF meeting Maureen and Lyndon, Any idea when we will meet in Minneapolis? The earlier in the week = would be best for me personally. Regards, Aron Aron J. Silverton Senior Staff Research Engineer Motorola Labs, Networks and Infrastructure Research Motorola, Inc. Telephone: 847-576-8747 =20 Fax: 847-576-3240 mailto:Aron.J.Silverton@motorola.com _______________________________________________ rserpool mailing list rserpool@ietf.org https://www1.ietf.org/mailman/listinfo/rserpool _______________________________________________ rserpool mailing list rserpool@ietf.org https://www1.ietf.org/mailman/listinfo/rserpool From rserpool-admin@ietf.org Tue Oct 7 05:58:21 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA25251 for ; Tue, 7 Oct 2003 05:58:21 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A6obQ-0000A4-N6; Tue, 07 Oct 2003 05:58:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A6oad-000083-Io for rserpool@optimus.ietf.org; Tue, 07 Oct 2003 05:57:11 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA25186 for ; Tue, 7 Oct 2003 05:57:01 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A6oaZ-0003PE-00 for rserpool@ietf.org; Tue, 07 Oct 2003 05:57:07 -0400 Received: from ns.exp-math.uni-essen.de ([132.252.150.1] helo=pilz.exp-math.uni-essen.de) by ietf-mx with esmtp (Exim 4.12) id 1A6oaY-0003PB-00 for rserpool@ietf.org; Tue, 07 Oct 2003 05:57:07 -0400 Received: from kappes.exp-math.uni-essen.de (kappes.exp-math.uni-essen.de [132.252.150.151]) by pilz.exp-math.uni-essen.de (8.12.8-20030924/8.12.8) with ESMTP id h979v7WO027794 for ; Tue, 7 Oct 2003 11:57:07 +0200 From: Thomas Dreibholz Organization: University of Essen, Institute for Experimental Mathematics To: Date: Tue, 7 Oct 2003 11:56:53 +0200 User-Agent: KMail/1.5 MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: quoted-printable Content-Description: clearsigned data Content-Disposition: inline Message-Id: <200310071157.04064.dreibh@exp-math.uni-essen.de> Content-Transfer-Encoding: quoted-printable Subject: [Rserpool] Download ENRP Namespace Data from Mentor Peer 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: , List-Id: Reliable Server Pooling List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable =2D----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all, when an ENRP server requests a namespace copy from a mentor peer by multipl= e=20 PEER_NAME_TABLE_REQUEST / PEER_NAME_TABLE_RESPONSE cycles during startup, t= he=20 mentor peer must also transmit PEER_NAME_UPDATES to the requesting name=20 server. Otherwise, namespace inconsistency can be caused. Example without PEER_NAME_UPDATE: 1. PEER_NAME_TABLE_RESPONSE with information about PE1. 2. PE1 updates its policy parameters or deregisters. 3. PEER_NAME_TABLE_REQUEST -> PEER_NAME_TABLE_RESPONSE with remaining parts= of=20 the namespace. =3D> The requesting nameserver still has PE1's old data. Example with PEER_NAME_UPDATE: 1. PEER_NAME_TABLE_RESPONSE with information about PE1. 2a. PE1 updates its policy parameters or deregisters. 2b. PEER_NAME_UPDATE for PE1. The new name server can update the PE1 entry or remove it. 3. PEER_NAME_TABLE_REQUEST -> PEER_NAME_TABLE_RESPONSE with remaining parts= of=20 the namespace. Therefore, section 4.2.3 of the ENRP draft should be extended by requiring = the=20 mentor peer to send PEER_NAME_UPDATEs and the new nameserver to handle thes= e=20 messages. Best regards =2D --=20 =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=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=3D=3D=3D=3D=3D Dipl.-Inform. Thomas Dreibholz University of Essen, Room ES210 Inst. for Experimental Mathematics Ellernstra=DFe 29 Computer Networking Technology Group D-45326 Essen/Germany =2D ----------------------------------------------------------------------- E-Mail: dreibh@exp-math.uni-essen.de Homepage: http://www.exp-math.uni-essen.de/~dreibh =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=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=3D=3D=3D=3D=3D =2D----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE/go3u32BbsHYPLWURAknPAJ42XRQpaXrSFW3LrqF8adIwmLk2bgCfWXe5 k4Itbpl91bsu4lDM+SmdZV8=3D =3DWWTk =2D----END PGP SIGNATURE----- _______________________________________________ rserpool mailing list rserpool@ietf.org https://www1.ietf.org/mailman/listinfo/rserpool From exim@www1.ietf.org Tue Oct 7 05:58:21 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA25254 for ; Tue, 7 Oct 2003 05:58:21 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A6obR-0000AQ-DX for rserpool-archive@odin.ietf.org; Tue, 07 Oct 2003 05:58:01 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h979w1QA000638 for rserpool-archive@odin.ietf.org; Tue, 7 Oct 2003 05:58:01 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A6obQ-0000A4-N6; Tue, 07 Oct 2003 05:58:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A6oad-000083-Io for rserpool@optimus.ietf.org; Tue, 07 Oct 2003 05:57:11 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA25186 for ; Tue, 7 Oct 2003 05:57:01 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A6oaZ-0003PE-00 for rserpool@ietf.org; Tue, 07 Oct 2003 05:57:07 -0400 Received: from ns.exp-math.uni-essen.de ([132.252.150.1] helo=pilz.exp-math.uni-essen.de) by ietf-mx with esmtp (Exim 4.12) id 1A6oaY-0003PB-00 for rserpool@ietf.org; Tue, 07 Oct 2003 05:57:07 -0400 Received: from kappes.exp-math.uni-essen.de (kappes.exp-math.uni-essen.de [132.252.150.151]) by pilz.exp-math.uni-essen.de (8.12.8-20030924/8.12.8) with ESMTP id h979v7WO027794 for ; Tue, 7 Oct 2003 11:57:07 +0200 From: Thomas Dreibholz Organization: University of Essen, Institute for Experimental Mathematics To: Date: Tue, 7 Oct 2003 11:56:53 +0200 User-Agent: KMail/1.5 MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: quoted-printable Content-Description: clearsigned data Content-Disposition: inline Message-Id: <200310071157.04064.dreibh@exp-math.uni-essen.de> Content-Transfer-Encoding: quoted-printable Subject: [Rserpool] Download ENRP Namespace Data from Mentor Peer 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: , List-Id: Reliable Server Pooling List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable =2D----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all, when an ENRP server requests a namespace copy from a mentor peer by multipl= e=20 PEER_NAME_TABLE_REQUEST / PEER_NAME_TABLE_RESPONSE cycles during startup, t= he=20 mentor peer must also transmit PEER_NAME_UPDATES to the requesting name=20 server. Otherwise, namespace inconsistency can be caused. Example without PEER_NAME_UPDATE: 1. PEER_NAME_TABLE_RESPONSE with information about PE1. 2. PE1 updates its policy parameters or deregisters. 3. PEER_NAME_TABLE_REQUEST -> PEER_NAME_TABLE_RESPONSE with remaining parts= of=20 the namespace. =3D> The requesting nameserver still has PE1's old data. Example with PEER_NAME_UPDATE: 1. PEER_NAME_TABLE_RESPONSE with information about PE1. 2a. PE1 updates its policy parameters or deregisters. 2b. PEER_NAME_UPDATE for PE1. The new name server can update the PE1 entry or remove it. 3. PEER_NAME_TABLE_REQUEST -> PEER_NAME_TABLE_RESPONSE with remaining parts= of=20 the namespace. Therefore, section 4.2.3 of the ENRP draft should be extended by requiring = the=20 mentor peer to send PEER_NAME_UPDATEs and the new nameserver to handle thes= e=20 messages. Best regards =2D --=20 =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=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=3D=3D=3D=3D=3D Dipl.-Inform. Thomas Dreibholz University of Essen, Room ES210 Inst. for Experimental Mathematics Ellernstra=DFe 29 Computer Networking Technology Group D-45326 Essen/Germany =2D ----------------------------------------------------------------------- E-Mail: dreibh@exp-math.uni-essen.de Homepage: http://www.exp-math.uni-essen.de/~dreibh =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=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=3D=3D=3D=3D=3D =2D----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE/go3u32BbsHYPLWURAknPAJ42XRQpaXrSFW3LrqF8adIwmLk2bgCfWXe5 k4Itbpl91bsu4lDM+SmdZV8=3D =3DWWTk =2D----END PGP SIGNATURE----- _______________________________________________ rserpool mailing list rserpool@ietf.org https://www1.ietf.org/mailman/listinfo/rserpool From rserpool-admin@ietf.org Tue Oct 7 17:24:22 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA23054 for ; Tue, 7 Oct 2003 17:24:21 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A6zJJ-0000Kn-AJ; Tue, 07 Oct 2003 17:24:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A6zIS-0000Jw-C5 for rserpool@optimus.ietf.org; Tue, 07 Oct 2003 17:23:08 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA22995 for ; Tue, 7 Oct 2003 17:22:58 -0400 (EDT) From: Maureen.Stillman@nokia.com Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A6zIP-00041q-00 for rserpool@ietf.org; Tue, 07 Oct 2003 17:23:06 -0400 Received: from mgw-x1.nokia.com ([131.228.20.21]) by ietf-mx with esmtp (Exim 4.12) id 1A6zIP-00041n-00 for rserpool@ietf.org; Tue, 07 Oct 2003 17:23:05 -0400 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.6) with ESMTP id h97LN5609092 for ; Wed, 8 Oct 2003 00:23:05 +0300 (EET DST) Received: from daebh002.NOE.Nokia.com (unverified) by esvir05nok.ntc.nokia.com (Content Technologies SMTPRS 4.2.5) with ESMTP id for ; Wed, 8 Oct 2003 00:23:03 +0300 Received: from daebe007.NOE.Nokia.com ([172.18.242.211]) by daebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139); Tue, 7 Oct 2003 16:22:36 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Date: Tue, 7 Oct 2003 16:22:36 -0500 Message-ID: <57A26D272F67A743952F6B4371B8F8110249677D@daebe007.americas.nokia.com> Thread-Topic: Rserpool Agena for IETF #58 Thread-Index: AcONGSDrG/XiEwpEREawPHliy+uIHQ== To: X-OriginalArrivalTime: 07 Oct 2003 21:22:36.0838 (UTC) FILETIME=[21451460:01C38D19] Content-Transfer-Encoding: quoted-printable Subject: [Rserpool] Rserpool Agena 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: , List-Id: Reliable Server Pooling List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Rserpool Agena for IETF #58; Monday November 10, 2003 We need to work on the draft agenda for our 2 hour slot. Please send = any topics to me and I'll work up a draft agenda for the mailing list. Thanks. -- maureen _______________________________________________ rserpool mailing list rserpool@ietf.org https://www1.ietf.org/mailman/listinfo/rserpool From exim@www1.ietf.org Tue Oct 7 17:24:22 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA23057 for ; Tue, 7 Oct 2003 17:24:22 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A6zJJ-0000LQ-VJ for rserpool-archive@odin.ietf.org; Tue, 07 Oct 2003 17:24:02 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h97LO19I001309 for rserpool-archive@odin.ietf.org; Tue, 7 Oct 2003 17:24:01 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A6zJJ-0000Kn-AJ; Tue, 07 Oct 2003 17:24:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A6zIS-0000Jw-C5 for rserpool@optimus.ietf.org; Tue, 07 Oct 2003 17:23:08 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA22995 for ; Tue, 7 Oct 2003 17:22:58 -0400 (EDT) From: Maureen.Stillman@nokia.com Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A6zIP-00041q-00 for rserpool@ietf.org; Tue, 07 Oct 2003 17:23:06 -0400 Received: from mgw-x1.nokia.com ([131.228.20.21]) by ietf-mx with esmtp (Exim 4.12) id 1A6zIP-00041n-00 for rserpool@ietf.org; Tue, 07 Oct 2003 17:23:05 -0400 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.6) with ESMTP id h97LN5609092 for ; Wed, 8 Oct 2003 00:23:05 +0300 (EET DST) Received: from daebh002.NOE.Nokia.com (unverified) by esvir05nok.ntc.nokia.com (Content Technologies SMTPRS 4.2.5) with ESMTP id for ; Wed, 8 Oct 2003 00:23:03 +0300 Received: from daebe007.NOE.Nokia.com ([172.18.242.211]) by daebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139); Tue, 7 Oct 2003 16:22:36 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Date: Tue, 7 Oct 2003 16:22:36 -0500 Message-ID: <57A26D272F67A743952F6B4371B8F8110249677D@daebe007.americas.nokia.com> Thread-Topic: Rserpool Agena for IETF #58 Thread-Index: AcONGSDrG/XiEwpEREawPHliy+uIHQ== To: X-OriginalArrivalTime: 07 Oct 2003 21:22:36.0838 (UTC) FILETIME=[21451460:01C38D19] Content-Transfer-Encoding: quoted-printable Subject: [Rserpool] Rserpool Agena 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: , List-Id: Reliable Server Pooling List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Rserpool Agena for IETF #58; Monday November 10, 2003 We need to work on the draft agenda for our 2 hour slot. Please send = any topics to me and I'll work up a draft agenda for the mailing list. Thanks. -- maureen _______________________________________________ rserpool mailing list rserpool@ietf.org https://www1.ietf.org/mailman/listinfo/rserpool From rserpool-admin@ietf.org Tue Oct 7 19:28:22 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA27574 for ; Tue, 7 Oct 2003 19:28:22 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A71FI-0005h2-Jk; Tue, 07 Oct 2003 19:28:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A71EQ-0005cd-0h for rserpool@optimus.ietf.org; Tue, 07 Oct 2003 19:27:06 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA27539 for ; Tue, 7 Oct 2003 19:26:55 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A71EO-0005Cd-00 for rserpool@ietf.org; Tue, 07 Oct 2003 19:27:04 -0400 Received: from motgate7.mot.com ([129.188.136.7]) by ietf-mx with esmtp (Exim 4.12) id 1A71EN-0005Ca-00 for rserpool@ietf.org; Tue, 07 Oct 2003 19:27:03 -0400 Received: from il06exr04.mot.com (il06exr04.mot.com [129.188.137.134]) by motgate7.mot.com (Motorola/Motgate7) with ESMTP id h97NQe3Q029863; Tue, 7 Oct 2003 16:26:40 -0700 (MST) Received: from motorola.com (d1421-0a1070d5.cig.mot.com [10.16.112.213]) by il06exr04.mot.com (Motorola/il06exr04) with ESMTP id h97NQjhA032385; Tue, 7 Oct 2003 18:26:45 -0500 Message-ID: <3F83420A.49422671@motorola.com> Date: Tue, 07 Oct 2003 17:45:30 -0500 From: Qiaobing Xie X-Mailer: Mozilla 4.8 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Thomas Dreibholz CC: rserpool@ietf.org Subject: Re: [Rserpool] Download ENRP Namespace Data from Mentor Peer References: <200310071157.04064.dreibh@exp-math.uni-essen.de> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by motgate7.mot.com id h97NQe3Q029863 Content-Transfer-Encoding: quoted-printable 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: , List-Id: Reliable Server Pooling List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Hi, Thomas, The issue you discuss here is simply a race condition between ASAP and ENRP. Since ASAP and ENRP are two separately protocols, there will be a lot of race conditions that could occur in operation. And we realize this situation from very beginning. Our strategy has been to allow the discrepancies to occur and to rely on the auditing and re-sync procedures to bring the name servers back to consistency. The reasoning is simply - it would be too expensive to address the race conditions one by one and it wouldn't make much sense either if we only address one race condition without fixing the others... So my view is to stay with the overall design strategy and let the auditing and re-sync procedures to take care of the inconsistency. regards, -Qiaobing Thomas Dreibholz wrote: >=20 > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 >=20 > Hi all, >=20 > when an ENRP server requests a namespace copy from a mentor peer by mul= tiple > PEER_NAME_TABLE_REQUEST / PEER_NAME_TABLE_RESPONSE cycles during startu= p, the > mentor peer must also transmit PEER_NAME_UPDATES to the requesting name > server. Otherwise, namespace inconsistency can be caused. >=20 > Example without PEER_NAME_UPDATE: > 1. PEER_NAME_TABLE_RESPONSE with information about PE1. > 2. PE1 updates its policy parameters or deregisters. > 3. PEER_NAME_TABLE_REQUEST -> PEER_NAME_TABLE_RESPONSE with remaining p= arts of > the namespace. > =3D> The requesting nameserver still has PE1's old data. >=20 > Example with PEER_NAME_UPDATE: > 1. PEER_NAME_TABLE_RESPONSE with information about PE1. > 2a. PE1 updates its policy parameters or deregisters. > 2b. PEER_NAME_UPDATE for PE1. > The new name server can update the PE1 entry or remove it. > 3. PEER_NAME_TABLE_REQUEST -> PEER_NAME_TABLE_RESPONSE with remaining p= arts of > the namespace. >=20 > Therefore, section 4.2.3 of the ENRP draft should be extended by requir= ing the > mentor peer to send PEER_NAME_UPDATEs and the new nameserver to handle = these > messages. >=20 > Best regards > - -- > =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=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=3D=3D=3D=3D=3D > Dipl.-Inform. Thomas Dreibholz >=20 > University of Essen, Room ES210 > Inst. for Experimental Mathematics Ellernstra=DFe 29 > Computer Networking Technology Group D-45326 Essen/Germany > - ---------------------------------------------------------------------= -- > E-Mail: dreibh@exp-math.uni-essen.de > Homepage: http://www.exp-math.uni-essen.de/~dreibh > =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=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=3D=3D=3D=3D=3D > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.2.2 (GNU/Linux) >=20 > iD8DBQE/go3u32BbsHYPLWURAknPAJ42XRQpaXrSFW3LrqF8adIwmLk2bgCfWXe5 > k4Itbpl91bsu4lDM+SmdZV8=3D > =3DWWTk > -----END PGP SIGNATURE----- >=20 > _______________________________________________ > rserpool mailing list > rserpool@ietf.org > https://www1.ietf.org/mailman/listinfo/rserpool _______________________________________________ rserpool mailing list rserpool@ietf.org https://www1.ietf.org/mailman/listinfo/rserpool From exim@www1.ietf.org Tue Oct 7 19:28:22 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA27578 for ; Tue, 7 Oct 2003 19:28:22 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A71FK-0005hX-1e for rserpool-archive@odin.ietf.org; Tue, 07 Oct 2003 19:28:02 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h97NS2cZ021914 for rserpool-archive@odin.ietf.org; Tue, 7 Oct 2003 19:28:02 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A71FI-0005h2-Jk; Tue, 07 Oct 2003 19:28:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A71EQ-0005cd-0h for rserpool@optimus.ietf.org; Tue, 07 Oct 2003 19:27:06 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA27539 for ; Tue, 7 Oct 2003 19:26:55 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A71EO-0005Cd-00 for rserpool@ietf.org; Tue, 07 Oct 2003 19:27:04 -0400 Received: from motgate7.mot.com ([129.188.136.7]) by ietf-mx with esmtp (Exim 4.12) id 1A71EN-0005Ca-00 for rserpool@ietf.org; Tue, 07 Oct 2003 19:27:03 -0400 Received: from il06exr04.mot.com (il06exr04.mot.com [129.188.137.134]) by motgate7.mot.com (Motorola/Motgate7) with ESMTP id h97NQe3Q029863; Tue, 7 Oct 2003 16:26:40 -0700 (MST) Received: from motorola.com (d1421-0a1070d5.cig.mot.com [10.16.112.213]) by il06exr04.mot.com (Motorola/il06exr04) with ESMTP id h97NQjhA032385; Tue, 7 Oct 2003 18:26:45 -0500 Message-ID: <3F83420A.49422671@motorola.com> Date: Tue, 07 Oct 2003 17:45:30 -0500 From: Qiaobing Xie X-Mailer: Mozilla 4.8 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Thomas Dreibholz CC: rserpool@ietf.org Subject: Re: [Rserpool] Download ENRP Namespace Data from Mentor Peer References: <200310071157.04064.dreibh@exp-math.uni-essen.de> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by motgate7.mot.com id h97NQe3Q029863 Content-Transfer-Encoding: quoted-printable 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: , List-Id: Reliable Server Pooling List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Hi, Thomas, The issue you discuss here is simply a race condition between ASAP and ENRP. Since ASAP and ENRP are two separately protocols, there will be a lot of race conditions that could occur in operation. And we realize this situation from very beginning. Our strategy has been to allow the discrepancies to occur and to rely on the auditing and re-sync procedures to bring the name servers back to consistency. The reasoning is simply - it would be too expensive to address the race conditions one by one and it wouldn't make much sense either if we only address one race condition without fixing the others... So my view is to stay with the overall design strategy and let the auditing and re-sync procedures to take care of the inconsistency. regards, -Qiaobing Thomas Dreibholz wrote: >=20 > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 >=20 > Hi all, >=20 > when an ENRP server requests a namespace copy from a mentor peer by mul= tiple > PEER_NAME_TABLE_REQUEST / PEER_NAME_TABLE_RESPONSE cycles during startu= p, the > mentor peer must also transmit PEER_NAME_UPDATES to the requesting name > server. Otherwise, namespace inconsistency can be caused. >=20 > Example without PEER_NAME_UPDATE: > 1. PEER_NAME_TABLE_RESPONSE with information about PE1. > 2. PE1 updates its policy parameters or deregisters. > 3. PEER_NAME_TABLE_REQUEST -> PEER_NAME_TABLE_RESPONSE with remaining p= arts of > the namespace. > =3D> The requesting nameserver still has PE1's old data. >=20 > Example with PEER_NAME_UPDATE: > 1. PEER_NAME_TABLE_RESPONSE with information about PE1. > 2a. PE1 updates its policy parameters or deregisters. > 2b. PEER_NAME_UPDATE for PE1. > The new name server can update the PE1 entry or remove it. > 3. PEER_NAME_TABLE_REQUEST -> PEER_NAME_TABLE_RESPONSE with remaining p= arts of > the namespace. >=20 > Therefore, section 4.2.3 of the ENRP draft should be extended by requir= ing the > mentor peer to send PEER_NAME_UPDATEs and the new nameserver to handle = these > messages. >=20 > Best regards > - -- > =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=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=3D=3D=3D=3D=3D > Dipl.-Inform. Thomas Dreibholz >=20 > University of Essen, Room ES210 > Inst. for Experimental Mathematics Ellernstra=DFe 29 > Computer Networking Technology Group D-45326 Essen/Germany > - ---------------------------------------------------------------------= -- > E-Mail: dreibh@exp-math.uni-essen.de > Homepage: http://www.exp-math.uni-essen.de/~dreibh > =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=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=3D=3D=3D=3D=3D > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.2.2 (GNU/Linux) >=20 > iD8DBQE/go3u32BbsHYPLWURAknPAJ42XRQpaXrSFW3LrqF8adIwmLk2bgCfWXe5 > k4Itbpl91bsu4lDM+SmdZV8=3D > =3DWWTk > -----END PGP SIGNATURE----- >=20 > _______________________________________________ > rserpool mailing list > rserpool@ietf.org > https://www1.ietf.org/mailman/listinfo/rserpool _______________________________________________ rserpool mailing list rserpool@ietf.org https://www1.ietf.org/mailman/listinfo/rserpool From rserpool-admin@ietf.org Tue Oct 7 19:41:21 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA27923 for ; Tue, 7 Oct 2003 19:41:21 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A71Rt-0006X9-D1; Tue, 07 Oct 2003 19:41:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A71Qw-0006Vj-1S for rserpool@optimus.ietf.org; Tue, 07 Oct 2003 19:40:02 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA27883 for ; Tue, 7 Oct 2003 19:39:51 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A71Qu-0005Ji-00 for rserpool@ietf.org; Tue, 07 Oct 2003 19:40:00 -0400 Received: from ftpbox.mot.com ([129.188.136.101]) by ietf-mx with esmtp (Exim 4.12) id 1A71Qt-0005Je-00 for rserpool@ietf.org; Tue, 07 Oct 2003 19:39:59 -0400 Received: from il06exr06.mot.com (il06exr06.mot.com [129.188.137.136]) by ftpbox.mot.com (Motorola/Ftpbox) with ESMTP id h97Ne0Vx020130 for ; Tue, 7 Oct 2003 16:40:00 -0700 (MST) Received: from il02exb02.corp.mot.com (il02exb02.corp.mot.com [10.0.100.67]) by il06exr06.mot.com (Motorola/il06exr06) with ESMTP id h97NdwCi016339 for ; Tue, 7 Oct 2003 18:39:58 -0500 Received: by il02exb02.corp.mot.com with Internet Mail Service (5.5.2657.2) id ; Tue, 7 Oct 2003 18:39:17 -0500 Message-ID: <6F8DFFA2C996D711945800065BFC9E4A0110C08E@il02exm11.corp.mot.com> From: Silverton Aron-C1710C To: Xie Qiaobing-QXIE1 , Thomas Dreibholz Cc: rserpool@ietf.org Subject: RE: [Rserpool] Download ENRP Namespace Data from Mentor Peer Date: Tue, 7 Oct 2003 18:40:31 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.2) Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Transfer-Encoding: quoted-printable 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: , List-Id: Reliable Server Pooling List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Hi Thomas and Qiaobing, As Qiaobing pointed out there are many possible race conditions that = can occur depending on who the home ENRP server for the PE is and who the = mentor peer server for the new ENRP server is. That being the case, the PEER_NAME_UPDATE would seem to make more sense if the PE that changes = its information or deregisters is homed to the ENRP server acting as the = mentor. In any event, everything will get straightened out eventually, but I = could go so far as suggesting that: Upon receiving the final PEER_NAME_TABLE_RESPONSE from the mentor peer, = the new ENRP server SHOULD initiate the audit and synchronization = procedures to account for any race conditions that may be existed during the initial = name space transfer. This is probably more along the lines of a best practice or an implementation note, and perhaps it doesn't belong in the protocol = draft. Aron Xie Qiaobing-QXIE1 wrote: > Hi, Thomas, >=20 > The issue you discuss here is simply a race condition between > ASAP and ENRP. Since ASAP and ENRP are two separately protocols, > there will be a lot of race conditions that could occur in > operation. And we realize this situation from very beginning. Our > strategy has been to allow the discrepancies to occur and to rely > on the auditing and re-sync procedures to bring the name servers > back to consistency. The reasoning is simply - it would be too > expensive to address the race conditions one by one and it > wouldn't make much sense either if we only address one race > condition without fixing the others... So my view is to stay with > the overall design strategy and let the auditing and re-sync > procedures to take care of the inconsistency. =20 >=20 > regards, > -Qiaobing >=20 > Thomas Dreibholz wrote: >>=20 >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >>=20 >> Hi all, >>=20 >> when an ENRP server requests a namespace copy from a mentor peer >> by multiple PEER_NAME_TABLE_REQUEST / PEER_NAME_TABLE_RESPONSE >> cycles during startup, the mentor peer must also transmit >> PEER_NAME_UPDATES to the requesting name server. Otherwise, >> namespace inconsistency can be caused.=20 >>=20 >> Example without PEER_NAME_UPDATE: >> 1. PEER_NAME_TABLE_RESPONSE with information about PE1. >> 2. PE1 updates its policy parameters or deregisters. >> 3. PEER_NAME_TABLE_REQUEST -> PEER_NAME_TABLE_RESPONSE with >> remaining parts of the namespace. =3D> The requesting nameserver >> still has PE1's old data.=20 >>=20 >> Example with PEER_NAME_UPDATE: >> 1. PEER_NAME_TABLE_RESPONSE with information about PE1. >> 2a. PE1 updates its policy parameters or deregisters. 2b. >> PEER_NAME_UPDATE for PE1. The new name server can update the PE1 >> entry or remove it.=20 >> 3. PEER_NAME_TABLE_REQUEST -> PEER_NAME_TABLE_RESPONSE with >> remaining parts of the namespace.=20 >>=20 >> Therefore, section 4.2.3 of the ENRP draft should be extended by >> requiring the mentor peer to send PEER_NAME_UPDATEs and the new >> nameserver to handle these messages. >>=20 >> Best regards >> - -- >> = =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=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=3D=3D=3D=3D >> =3D Dipl.-Inform. Thomas Dreibholz >>=20 >> University of Essen, Room ES210 >> Inst. for Experimental Mathematics Ellernstra=DFe 29 >> Computer Networking Technology Group D-45326 >> Essen/Germany=20 >> - >> = ----------------------------------------------------------------------- >> E-Mail: dreibh@exp-math.uni-essen.de Homepage: =20 >> http://www.exp-math.uni-essen.de/~dreibh >> = =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=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=3D=3D=3D=3D >> =3D =20 >> -----BEGIN PGP SIGNATURE----- >> Version: GnuPG v1.2.2 (GNU/Linux) >>=20 >> iD8DBQE/go3u32BbsHYPLWURAknPAJ42XRQpaXrSFW3LrqF8adIwmLk2bgCfWXe5 >> k4Itbpl91bsu4lDM+SmdZV8=3D =3DWWTk >> -----END PGP SIGNATURE----- >>=20 >> _______________________________________________ >> rserpool mailing list >> rserpool@ietf.org https://www1.ietf.org/mailman/listinfo/rserpool >=20 >=20 > _______________________________________________ > rserpool mailing list > rserpool@ietf.org https://www1.ietf.org/mailman/listinfo/rserpool _______________________________________________ rserpool mailing list rserpool@ietf.org https://www1.ietf.org/mailman/listinfo/rserpool From exim@www1.ietf.org Tue Oct 7 19:41:22 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA27938 for ; Tue, 7 Oct 2003 19:41:22 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A71Rt-0006XZ-Qe for rserpool-archive@odin.ietf.org; Tue, 07 Oct 2003 19:41:02 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h97Nf1f5025125 for rserpool-archive@odin.ietf.org; Tue, 7 Oct 2003 19:41:01 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A71Rt-0006X9-D1; Tue, 07 Oct 2003 19:41:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A71Qw-0006Vj-1S for rserpool@optimus.ietf.org; Tue, 07 Oct 2003 19:40:02 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA27883 for ; Tue, 7 Oct 2003 19:39:51 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A71Qu-0005Ji-00 for rserpool@ietf.org; Tue, 07 Oct 2003 19:40:00 -0400 Received: from ftpbox.mot.com ([129.188.136.101]) by ietf-mx with esmtp (Exim 4.12) id 1A71Qt-0005Je-00 for rserpool@ietf.org; Tue, 07 Oct 2003 19:39:59 -0400 Received: from il06exr06.mot.com (il06exr06.mot.com [129.188.137.136]) by ftpbox.mot.com (Motorola/Ftpbox) with ESMTP id h97Ne0Vx020130 for ; Tue, 7 Oct 2003 16:40:00 -0700 (MST) Received: from il02exb02.corp.mot.com (il02exb02.corp.mot.com [10.0.100.67]) by il06exr06.mot.com (Motorola/il06exr06) with ESMTP id h97NdwCi016339 for ; Tue, 7 Oct 2003 18:39:58 -0500 Received: by il02exb02.corp.mot.com with Internet Mail Service (5.5.2657.2) id ; Tue, 7 Oct 2003 18:39:17 -0500 Message-ID: <6F8DFFA2C996D711945800065BFC9E4A0110C08E@il02exm11.corp.mot.com> From: Silverton Aron-C1710C To: Xie Qiaobing-QXIE1 , Thomas Dreibholz Cc: rserpool@ietf.org Subject: RE: [Rserpool] Download ENRP Namespace Data from Mentor Peer Date: Tue, 7 Oct 2003 18:40:31 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.2) Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Transfer-Encoding: quoted-printable 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: , List-Id: Reliable Server Pooling List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Hi Thomas and Qiaobing, As Qiaobing pointed out there are many possible race conditions that = can occur depending on who the home ENRP server for the PE is and who the = mentor peer server for the new ENRP server is. That being the case, the PEER_NAME_UPDATE would seem to make more sense if the PE that changes = its information or deregisters is homed to the ENRP server acting as the = mentor. In any event, everything will get straightened out eventually, but I = could go so far as suggesting that: Upon receiving the final PEER_NAME_TABLE_RESPONSE from the mentor peer, = the new ENRP server SHOULD initiate the audit and synchronization = procedures to account for any race conditions that may be existed during the initial = name space transfer. This is probably more along the lines of a best practice or an implementation note, and perhaps it doesn't belong in the protocol = draft. Aron Xie Qiaobing-QXIE1 wrote: > Hi, Thomas, >=20 > The issue you discuss here is simply a race condition between > ASAP and ENRP. Since ASAP and ENRP are two separately protocols, > there will be a lot of race conditions that could occur in > operation. And we realize this situation from very beginning. Our > strategy has been to allow the discrepancies to occur and to rely > on the auditing and re-sync procedures to bring the name servers > back to consistency. The reasoning is simply - it would be too > expensive to address the race conditions one by one and it > wouldn't make much sense either if we only address one race > condition without fixing the others... So my view is to stay with > the overall design strategy and let the auditing and re-sync > procedures to take care of the inconsistency. =20 >=20 > regards, > -Qiaobing >=20 > Thomas Dreibholz wrote: >>=20 >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >>=20 >> Hi all, >>=20 >> when an ENRP server requests a namespace copy from a mentor peer >> by multiple PEER_NAME_TABLE_REQUEST / PEER_NAME_TABLE_RESPONSE >> cycles during startup, the mentor peer must also transmit >> PEER_NAME_UPDATES to the requesting name server. Otherwise, >> namespace inconsistency can be caused.=20 >>=20 >> Example without PEER_NAME_UPDATE: >> 1. PEER_NAME_TABLE_RESPONSE with information about PE1. >> 2. PE1 updates its policy parameters or deregisters. >> 3. PEER_NAME_TABLE_REQUEST -> PEER_NAME_TABLE_RESPONSE with >> remaining parts of the namespace. =3D> The requesting nameserver >> still has PE1's old data.=20 >>=20 >> Example with PEER_NAME_UPDATE: >> 1. PEER_NAME_TABLE_RESPONSE with information about PE1. >> 2a. PE1 updates its policy parameters or deregisters. 2b. >> PEER_NAME_UPDATE for PE1. The new name server can update the PE1 >> entry or remove it.=20 >> 3. PEER_NAME_TABLE_REQUEST -> PEER_NAME_TABLE_RESPONSE with >> remaining parts of the namespace.=20 >>=20 >> Therefore, section 4.2.3 of the ENRP draft should be extended by >> requiring the mentor peer to send PEER_NAME_UPDATEs and the new >> nameserver to handle these messages. >>=20 >> Best regards >> - -- >> = =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=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=3D=3D=3D=3D >> =3D Dipl.-Inform. Thomas Dreibholz >>=20 >> University of Essen, Room ES210 >> Inst. for Experimental Mathematics Ellernstra=DFe 29 >> Computer Networking Technology Group D-45326 >> Essen/Germany=20 >> - >> = ----------------------------------------------------------------------- >> E-Mail: dreibh@exp-math.uni-essen.de Homepage: =20 >> http://www.exp-math.uni-essen.de/~dreibh >> = =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=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=3D=3D=3D=3D >> =3D =20 >> -----BEGIN PGP SIGNATURE----- >> Version: GnuPG v1.2.2 (GNU/Linux) >>=20 >> iD8DBQE/go3u32BbsHYPLWURAknPAJ42XRQpaXrSFW3LrqF8adIwmLk2bgCfWXe5 >> k4Itbpl91bsu4lDM+SmdZV8=3D =3DWWTk >> -----END PGP SIGNATURE----- >>=20 >> _______________________________________________ >> rserpool mailing list >> rserpool@ietf.org https://www1.ietf.org/mailman/listinfo/rserpool >=20 >=20 > _______________________________________________ > rserpool mailing list > rserpool@ietf.org https://www1.ietf.org/mailman/listinfo/rserpool _______________________________________________ rserpool mailing list rserpool@ietf.org https://www1.ietf.org/mailman/listinfo/rserpool From rserpool-admin@ietf.org Wed Oct 8 17:07:22 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA09377 for ; Wed, 8 Oct 2003 17:07:22 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A7LWP-00029W-Hk; Wed, 08 Oct 2003 17:07:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A6tRN-0006NS-9c for rserpool@optimus.ietf.org; Tue, 07 Oct 2003 11:07:57 -0400 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA05906; Tue, 7 Oct 2003 11:07:46 -0400 (EDT) Message-Id: <200310071507.LAA05906@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: rserpool@ietf.org From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Date: Tue, 07 Oct 2003 11:07:45 -0400 Subject: [Rserpool] I-D ACTION:draft-ietf-rserpool-threats-02.txt 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: , List-Id: Reliable Server Pooling List-Post: List-Help: List-Subscribe: , --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Reliable Server Pooling Working Group of the IETF. Title : Threats Introduced by Rserpool and Requirements for Security in response to Threats Author(s) : M. Stillman, et. al. Filename : draft-ietf-rserpool-threats-02.txt Pages : 10 Date : 2003-10-7 Rserpool is an architecture and protocols for the management and access to server pools supporting highly reliable applications and for client access mechanisms to a server pool. This Internet draft describes security threats to the Rserpool architecture and presents requirements for security to thwart these threats. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-rserpool-threats-02.txt To remove yourself from the IETF Announcement list, send a message to ietf-announce-request with the word unsubscribe in the body of the message. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-rserpool-threats-02.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-rserpool-threats-02.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2003-10-7111050.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-rserpool-threats-02.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-rserpool-threats-02.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2003-10-7111050.I-D@ietf.org> --OtherAccess-- --NextPart-- _______________________________________________ rserpool mailing list rserpool@ietf.org https://www1.ietf.org/mailman/listinfo/rserpool From exim@www1.ietf.org Wed Oct 8 17:07:22 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA09379 for ; Wed, 8 Oct 2003 17:07:22 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A7LWQ-0002AK-B4 for rserpool-archive@odin.ietf.org; Wed, 08 Oct 2003 17:07:02 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h98L72Jr008299 for rserpool-archive@odin.ietf.org; Wed, 8 Oct 2003 17:07:02 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A7LWP-00029W-Hk; Wed, 08 Oct 2003 17:07:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A6tRN-0006NS-9c for rserpool@optimus.ietf.org; Tue, 07 Oct 2003 11:07:57 -0400 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA05906; Tue, 7 Oct 2003 11:07:46 -0400 (EDT) Message-Id: <200310071507.LAA05906@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: rserpool@ietf.org From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Date: Tue, 07 Oct 2003 11:07:45 -0400 Subject: [Rserpool] I-D ACTION:draft-ietf-rserpool-threats-02.txt 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: , List-Id: Reliable Server Pooling List-Post: List-Help: List-Subscribe: , --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Reliable Server Pooling Working Group of the IETF. Title : Threats Introduced by Rserpool and Requirements for Security in response to Threats Author(s) : M. Stillman, et. al. Filename : draft-ietf-rserpool-threats-02.txt Pages : 10 Date : 2003-10-7 Rserpool is an architecture and protocols for the management and access to server pools supporting highly reliable applications and for client access mechanisms to a server pool. This Internet draft describes security threats to the Rserpool architecture and presents requirements for security to thwart these threats. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-rserpool-threats-02.txt To remove yourself from the IETF Announcement list, send a message to ietf-announce-request with the word unsubscribe in the body of the message. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-rserpool-threats-02.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-rserpool-threats-02.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2003-10-7111050.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-rserpool-threats-02.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-rserpool-threats-02.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2003-10-7111050.I-D@ietf.org> --OtherAccess-- --NextPart-- _______________________________________________ rserpool mailing list rserpool@ietf.org https://www1.ietf.org/mailman/listinfo/rserpool From rserpool-admin@ietf.org Sun Oct 12 15:28:23 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA26643 for ; Sun, 12 Oct 2003 15:28:23 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A8lsm-0000N5-LT; Sun, 12 Oct 2003 15:28:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A8lsF-0000MX-GJ for rserpool@optimus.ietf.org; Sun, 12 Oct 2003 15:27:27 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA26639 for ; Sun, 12 Oct 2003 15:27:18 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A8lsE-0002G6-00 for rserpool@ietf.org; Sun, 12 Oct 2003 15:27:26 -0400 Received: from mail-n.franken.de ([193.175.24.27] ident=postfix) by ietf-mx with esmtp (Exim 4.12) id 1A8lsD-0002G3-00 for rserpool@ietf.org; Sun, 12 Oct 2003 15:27:25 -0400 Received: from [10.0.1.2] (p5089F6D1.dip.t-dialin.net [80.137.246.209]) by mail-n.franken.de (Postfix) with ESMTP id 6EB8B245D6; Sun, 12 Oct 2003 21:27:23 +0200 (CEST) In-Reply-To: <57A26D272F67A743952F6B4371B8F81101222F34@daebe007.americas.nokia.com> References: <57A26D272F67A743952F6B4371B8F81101222F34@daebe007.americas.nokia.com> Mime-Version: 1.0 (Apple Message framework v604) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <19AD51A6-FCEA-11D7-8376-000A9591232C@lurchi.franken.de> Content-Transfer-Encoding: 7bit Cc: From: Michael Tuexen Subject: Re: [Rserpool] Comments on architecture document -- last call Date: Sun, 12 Oct 2003 21:27:21 +0200 To: Maureen.Stillman@nokia.com X-Mailer: Apple Mail (2.604) Content-Transfer-Encoding: 7bit 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: , List-Id: Reliable Server Pooling List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Hi Maureen, see my comments below. Best regards Michael On Aug 19, 2003, at 22:38, Maureen.Stillman@nokia.com wrote: > I read this carefully. Here are my comments. > Thank you very much. > Non-nits: > > 2.2.1 Endpoint Name Resolution Protocol > > The name servers use a protocol called Endpoint Name Resolution > Protocol (ENRP) for communication with each other to make sure that > all have the same information about the server pools. > > I'm concerned that this will spark a lengthy debate about > synchronization of ENRP databases. We can't guarantee instantaneous > updates of the database and a perfectly synchronized name space. How > about something like: > > The name servers use a protocol called Endpoint Name Resolution > Protocol (ENRP) for communication with each other to exchange > information and updates > about the server pools. Accepted. > > 2.2.2 Aggregate Server Access Protocol > > > ASAP in conjunction with ENRP provides a fault tolerant data > transfer > mechanism over IP networks. > > I'm concerned that this will be interpreted as a general feature with > some sort of guarantee. It is only offered by use of specific > services described in services document. In other words, this will > imply that it offers transparent fail-over in all cases which is not > true. Even with that, there is no guarantee of uninterrupted service. > It is best effort. I would delete this sentence or talk about > services and different possibilities. These are discussed in the > services document. The sentence has been deleted. > > In addition, ASAP defines each logical communication destination as > a > server pool, providing full transparent support for server-pooling > and load sharing. I doubt that this sentence is from me, I also do not understand it... I replaced it with: In addition, ASAP provides some mechanisms to support loadsharing between PEs within the same pool and to support the upper layer in case of a failover between PEs becomes necessary. > > I don't understand this statement. What is a logical communication > destination? > Phil knows this, I guess. > ASAP is also used by a server to join or leave a server pool. It > registers or deregisters itself by communicating with a name server, > which will normally the home NS. > > see changes below: > > ASAP is also used by a PE to join or leave a server pool. It > registers or deregisters itself by communicating with a name server, > which will normally be the home NS. Is a server a PE before joining a server pool? That is why I used server instead of PE. Howeverm, I changed it as you want it. > > ASAP allows dynamic system > scalability, allowing the pool membership to change at any time > without interruption of the service. > > Same concern as above. This is only offered by use of specific > services described in services document. Even with that, there is no > guarantee of uninterrupted service. It is best effort. You are right. I changed it to ASAP allows dynamic system scalability, allowing the pool membership to change at any time. > > Nits: > > 1.1 Overview > > This document defines an architecture, for providinge a highly > available reliable server function in support of some service. The > way this is achieved is by forming a pool of servers, each of which > is capable of supporting the desired service, and providing a name > service that > > see changes below, misspelled words: > > This document defines an architecture, for *providing* a highly > available reliable server function in support of a service or set > of services. > This is achieved by forming a pool of servers, each of which > is capable of supporting the desired service(s), and providing a > name > service that... Accepted. > > 2.1 RSerPool Functional Components > > Each server pool will be identifiable by a unique name which is > simply a byte string, called the pool handle. > > see changes below: > > Each server pool is identified by a unique name which is > simply a byte string, called the pool handle. Accepted. > > o A protocol field of the IP header specifying the transport layer > protocol or protocols. > > see changes below: > > o A protocol field specifying the transport layer > protocol or protocols. Accepted, but also deleted 'or protocols', since the transport protocol is now unique within a pool. > > Please note that the RSerPool architecture supports both IPv4 and > IPv6 addressing. A PE can also support multiple transport layers. > > see changes below: > > Note that the RSerPool architecture supports both IPv4 and > IPv6 addressing. A PE can also support multiple transport protocols. Accepted, but also deleted the last sentence. > > 2.2.1 > > ENRP employs a client-server > model with which an name server will respond to the name translation > service requests from endpoint clients running on the same host or > running on different hosts. > > see changes below: > > ENRP employs a client-server > model in which a name server will respond to the name translation > service requests from endpoint clients. > Accepted. > 2.2.3 PU <-> NS Communication > > The PU <-> NS communication is used for doing name queries. > > see changes below: > > The PU <-> NS communication is used for performing name queries. Accepted. > > 2.2.4 PE <-> NS Communication > > The PE <-> NS communication is used for registration and > deregistration of the PE in one ore more pools and for the > > misspelled word: > > The PE <-> NS communication is used for registration and > deregistration of the PE in one *or* more pools and for the > Accepted. > > o Multiplexed data and control channel. Both channels are > transported over one transport connection. This can either be an > SCTP association, with data and control channel are seperated by > the PPID, or an TCP connection, with data and control channel > being handled by a TCP mapping layer. > > misspelled word: > > o Multiplexed data and control channel. Both channels are > transported over one transport connection. This can either be an > SCTP association, with data and control channel are *separated* > by > the PPID, or an TCP connection, with data and control channel > being handled by a TCP mapping layer. > Accepted. > > When a name server boots up a UDP multicast message may be sent out > for initial detection of other name servers in the operational > scope. > The other name servers send an answer using a unicast UDP message. > > Aren't we addressing multicast at a later time? If so, delete this > paragraph. We do not address this later in this doc. > Otherwise, some nits: > > When a name server initializes a UDP multicast message may be > transmitted > for initial detection of other name servers in the operational > scope. > The other name servers send a response using a unicast UDP message. > Accepted. > 2.3.1 > > communication may not be know by the peer. > > Providing information to which PE the OU should failover can also be > very important. Consider the scenario given in the following figure. > > misspelled words: > > communication may not be *known* by the peer. > > Providing information to which PE the *PU* should failover can also > be > very important. Consider the scenario *presented* in the following > figure. > Accepted. > Figure 4 > > Two PE accessing the same PE > > Should be: > > Two PUs accessing the same PE > Accepted. > 2.3.2 Cookies > > Cookies may be sent from the PE to the PU if the PE wants to do > this. > The PU only stores the last received cookie. In case of a fail over > it sends this last received cookie to the new PE. > > some changes: > > Cookies may optionally be sent from the PE to the PU. > The PU only stores the last received cookie. In case of fail over > the PU sends this last received cookie to the new PE. > Accepted. > [Editors note] This section has not been updated. The examples will > be updated after the architecture has been finalized. > > Please delete this. > Accepted. > 3.1 > > After figure 8: > > > 1. the Signaling Gateway (SG) receives an incoming signaling > message > to be forwarded to the GWC. SG(X)'s ASAP layer would send an > ASAP > request to its "local" NS to request the list of pool elements > (PE's) of GWC (using (a)). The key used for this query is the > pool handle of the GWC. The ASAP layer queues the data to be > sent > in local buffers until the NS responds. > > Don't use the word "key" for this as it sounds like some security key. > Use bit string or some other phrase. > I just deleted the sentence 'The key used for this query is the pool handle of the GWC.' > some change: > > The bit string used for this query is the > pool handle of the GWC. The ASAP layer queues the data to be > sent to the GWC > in local buffers until the NS responds. I accepted the change to the second sentence. > > > OK, I think that is it for now. > > -- maureen > > > _______________________________________________ > rserpool mailing list > rserpool@ietf.org > https://www1.ietf.org/mailman/listinfo/rserpool > _______________________________________________ rserpool mailing list rserpool@ietf.org https://www1.ietf.org/mailman/listinfo/rserpool From rserpool-admin@ietf.org Sun Oct 12 16:15:23 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA27413 for ; Sun, 12 Oct 2003 16:15:23 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A8mcH-00029q-Oq; Sun, 12 Oct 2003 16:15:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A8mc0-00029Y-0O for rserpool@optimus.ietf.org; Sun, 12 Oct 2003 16:14:44 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA27403 for ; Sun, 12 Oct 2003 16:14:34 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A8mby-0002X3-00 for rserpool@ietf.org; Sun, 12 Oct 2003 16:14:42 -0400 Received: from mail-n.franken.de ([193.175.24.27] ident=postfix) by ietf-mx with esmtp (Exim 4.12) id 1A8mbx-0002X0-00 for rserpool@ietf.org; Sun, 12 Oct 2003 16:14:41 -0400 Received: from [10.0.1.2] (p5089F6D1.dip.t-dialin.net [80.137.246.209]) by mail-n.franken.de (Postfix) with ESMTP id 0CF2C245E3; Sun, 12 Oct 2003 22:14:41 +0200 (CEST) In-Reply-To: <57A26D272F67A743952F6B4371B8F81101222F27@daebe007.americas.nokia.com> References: <57A26D272F67A743952F6B4371B8F81101222F27@daebe007.americas.nokia.com> Mime-Version: 1.0 (Apple Message framework v604) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit Cc: From: Michael Tuexen Subject: Re: [Rserpool] Comments on the Rserpool architecture internet draft -- last call Date: Sun, 12 Oct 2003 22:14:35 +0200 To: Maureen.Stillman@nokia.com X-Mailer: Apple Mail (2.604) Content-Transfer-Encoding: 7bit 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: , List-Id: Reliable Server Pooling List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Maureen, I've included the section in the document as requested. Best regards Michael On Aug 18, 2003, at 22:49, Maureen.Stillman@nokia.com wrote: > There is no security considerations section in the architecture draft. > I should have caught this earlier -- my bad! > > Here is a suggestion: > > The Rserpool protocol must allow us to secure the Rserpool > infrastructure. There are security and privacy issues that relate to > the namespace, pool element registration and user queries of the > namespace. In [1] a complete threat analysis of Rserpool components > is presented. > > [1] Threats Introduced by Rserpool and Requirements for Security in > response to Threats, draft-ietf-rserpool-threats-00.txt, work in > progress. > > This is how it is handled in the OPES architecture document > http://www.ietf.org/internet-drafts/draft-ietf-opes-architecture > -04.txt. > > I have some nits, but I'll send them tomorrow. > > Of course, other suggestions are welcome. > > -- maureen > > > > > _______________________________________________ > rserpool mailing list > rserpool@ietf.org > https://www1.ietf.org/mailman/listinfo/rserpool > _______________________________________________ rserpool mailing list rserpool@ietf.org https://www1.ietf.org/mailman/listinfo/rserpool From exim@www1.ietf.org Sun Oct 12 16:15:23 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA27415 for ; Sun, 12 Oct 2003 16:15:23 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A8mcI-0002AN-BD for rserpool-archive@odin.ietf.org; Sun, 12 Oct 2003 16:15:02 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9CKF2eJ008312 for rserpool-archive@odin.ietf.org; Sun, 12 Oct 2003 16:15:02 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A8mcH-00029q-Oq; Sun, 12 Oct 2003 16:15:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A8mc0-00029Y-0O for rserpool@optimus.ietf.org; Sun, 12 Oct 2003 16:14:44 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA27403 for ; Sun, 12 Oct 2003 16:14:34 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A8mby-0002X3-00 for rserpool@ietf.org; Sun, 12 Oct 2003 16:14:42 -0400 Received: from mail-n.franken.de ([193.175.24.27] ident=postfix) by ietf-mx with esmtp (Exim 4.12) id 1A8mbx-0002X0-00 for rserpool@ietf.org; Sun, 12 Oct 2003 16:14:41 -0400 Received: from [10.0.1.2] (p5089F6D1.dip.t-dialin.net [80.137.246.209]) by mail-n.franken.de (Postfix) with ESMTP id 0CF2C245E3; Sun, 12 Oct 2003 22:14:41 +0200 (CEST) In-Reply-To: <57A26D272F67A743952F6B4371B8F81101222F27@daebe007.americas.nokia.com> References: <57A26D272F67A743952F6B4371B8F81101222F27@daebe007.americas.nokia.com> Mime-Version: 1.0 (Apple Message framework v604) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit Cc: From: Michael Tuexen Subject: Re: [Rserpool] Comments on the Rserpool architecture internet draft -- last call Date: Sun, 12 Oct 2003 22:14:35 +0200 To: Maureen.Stillman@nokia.com X-Mailer: Apple Mail (2.604) Content-Transfer-Encoding: 7bit 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: , List-Id: Reliable Server Pooling List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Maureen, I've included the section in the document as requested. Best regards Michael On Aug 18, 2003, at 22:49, Maureen.Stillman@nokia.com wrote: > There is no security considerations section in the architecture draft. > I should have caught this earlier -- my bad! > > Here is a suggestion: > > The Rserpool protocol must allow us to secure the Rserpool > infrastructure. There are security and privacy issues that relate to > the namespace, pool element registration and user queries of the > namespace. In [1] a complete threat analysis of Rserpool components > is presented. > > [1] Threats Introduced by Rserpool and Requirements for Security in > response to Threats, draft-ietf-rserpool-threats-00.txt, work in > progress. > > This is how it is handled in the OPES architecture document > http://www.ietf.org/internet-drafts/draft-ietf-opes-architecture > -04.txt. > > I have some nits, but I'll send them tomorrow. > > Of course, other suggestions are welcome. > > -- maureen > > > > > _______________________________________________ > rserpool mailing list > rserpool@ietf.org > https://www1.ietf.org/mailman/listinfo/rserpool > _______________________________________________ rserpool mailing list rserpool@ietf.org https://www1.ietf.org/mailman/listinfo/rserpool From exim@www1.ietf.org Sun Oct 12 16:16:25 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA26645 for ; Sun, 12 Oct 2003 15:28:23 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A8lso-0000NG-7t for rserpool-archive@odin.ietf.org; Sun, 12 Oct 2003 15:28:02 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9CJS2bl001438 for rserpool-archive@odin.ietf.org; Sun, 12 Oct 2003 15:28:02 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A8lsm-0000N5-LT; Sun, 12 Oct 2003 15:28:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A8lsF-0000MX-GJ for rserpool@optimus.ietf.org; Sun, 12 Oct 2003 15:27:27 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA26639 for ; Sun, 12 Oct 2003 15:27:18 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A8lsE-0002G6-00 for rserpool@ietf.org; Sun, 12 Oct 2003 15:27:26 -0400 Received: from mail-n.franken.de ([193.175.24.27] ident=postfix) by ietf-mx with esmtp (Exim 4.12) id 1A8lsD-0002G3-00 for rserpool@ietf.org; Sun, 12 Oct 2003 15:27:25 -0400 Received: from [10.0.1.2] (p5089F6D1.dip.t-dialin.net [80.137.246.209]) by mail-n.franken.de (Postfix) with ESMTP id 6EB8B245D6; Sun, 12 Oct 2003 21:27:23 +0200 (CEST) In-Reply-To: <57A26D272F67A743952F6B4371B8F81101222F34@daebe007.americas.nokia.com> References: <57A26D272F67A743952F6B4371B8F81101222F34@daebe007.americas.nokia.com> Mime-Version: 1.0 (Apple Message framework v604) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <19AD51A6-FCEA-11D7-8376-000A9591232C@lurchi.franken.de> Content-Transfer-Encoding: 7bit Cc: From: Michael Tuexen Subject: Re: [Rserpool] Comments on architecture document -- last call Date: Sun, 12 Oct 2003 21:27:21 +0200 To: Maureen.Stillman@nokia.com X-Mailer: Apple Mail (2.604) Content-Transfer-Encoding: 7bit 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: , List-Id: Reliable Server Pooling List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Hi Maureen, see my comments below. Best regards Michael On Aug 19, 2003, at 22:38, Maureen.Stillman@nokia.com wrote: > I read this carefully. Here are my comments. > Thank you very much. > Non-nits: > > 2.2.1 Endpoint Name Resolution Protocol > > The name servers use a protocol called Endpoint Name Resolution > Protocol (ENRP) for communication with each other to make sure that > all have the same information about the server pools. > > I'm concerned that this will spark a lengthy debate about > synchronization of ENRP databases. We can't guarantee instantaneous > updates of the database and a perfectly synchronized name space. How > about something like: > > The name servers use a protocol called Endpoint Name Resolution > Protocol (ENRP) for communication with each other to exchange > information and updates > about the server pools. Accepted. > > 2.2.2 Aggregate Server Access Protocol > > > ASAP in conjunction with ENRP provides a fault tolerant data > transfer > mechanism over IP networks. > > I'm concerned that this will be interpreted as a general feature with > some sort of guarantee. It is only offered by use of specific > services described in services document. In other words, this will > imply that it offers transparent fail-over in all cases which is not > true. Even with that, there is no guarantee of uninterrupted service. > It is best effort. I would delete this sentence or talk about > services and different possibilities. These are discussed in the > services document. The sentence has been deleted. > > In addition, ASAP defines each logical communication destination as > a > server pool, providing full transparent support for server-pooling > and load sharing. I doubt that this sentence is from me, I also do not understand it... I replaced it with: In addition, ASAP provides some mechanisms to support loadsharing between PEs within the same pool and to support the upper layer in case of a failover between PEs becomes necessary. > > I don't understand this statement. What is a logical communication > destination? > Phil knows this, I guess. > ASAP is also used by a server to join or leave a server pool. It > registers or deregisters itself by communicating with a name server, > which will normally the home NS. > > see changes below: > > ASAP is also used by a PE to join or leave a server pool. It > registers or deregisters itself by communicating with a name server, > which will normally be the home NS. Is a server a PE before joining a server pool? That is why I used server instead of PE. Howeverm, I changed it as you want it. > > ASAP allows dynamic system > scalability, allowing the pool membership to change at any time > without interruption of the service. > > Same concern as above. This is only offered by use of specific > services described in services document. Even with that, there is no > guarantee of uninterrupted service. It is best effort. You are right. I changed it to ASAP allows dynamic system scalability, allowing the pool membership to change at any time. > > Nits: > > 1.1 Overview > > This document defines an architecture, for providinge a highly > available reliable server function in support of some service. The > way this is achieved is by forming a pool of servers, each of which > is capable of supporting the desired service, and providing a name > service that > > see changes below, misspelled words: > > This document defines an architecture, for *providing* a highly > available reliable server function in support of a service or set > of services. > This is achieved by forming a pool of servers, each of which > is capable of supporting the desired service(s), and providing a > name > service that... Accepted. > > 2.1 RSerPool Functional Components > > Each server pool will be identifiable by a unique name which is > simply a byte string, called the pool handle. > > see changes below: > > Each server pool is identified by a unique name which is > simply a byte string, called the pool handle. Accepted. > > o A protocol field of the IP header specifying the transport layer > protocol or protocols. > > see changes below: > > o A protocol field specifying the transport layer > protocol or protocols. Accepted, but also deleted 'or protocols', since the transport protocol is now unique within a pool. > > Please note that the RSerPool architecture supports both IPv4 and > IPv6 addressing. A PE can also support multiple transport layers. > > see changes below: > > Note that the RSerPool architecture supports both IPv4 and > IPv6 addressing. A PE can also support multiple transport protocols. Accepted, but also deleted the last sentence. > > 2.2.1 > > ENRP employs a client-server > model with which an name server will respond to the name translation > service requests from endpoint clients running on the same host or > running on different hosts. > > see changes below: > > ENRP employs a client-server > model in which a name server will respond to the name translation > service requests from endpoint clients. > Accepted. > 2.2.3 PU <-> NS Communication > > The PU <-> NS communication is used for doing name queries. > > see changes below: > > The PU <-> NS communication is used for performing name queries. Accepted. > > 2.2.4 PE <-> NS Communication > > The PE <-> NS communication is used for registration and > deregistration of the PE in one ore more pools and for the > > misspelled word: > > The PE <-> NS communication is used for registration and > deregistration of the PE in one *or* more pools and for the > Accepted. > > o Multiplexed data and control channel. Both channels are > transported over one transport connection. This can either be an > SCTP association, with data and control channel are seperated by > the PPID, or an TCP connection, with data and control channel > being handled by a TCP mapping layer. > > misspelled word: > > o Multiplexed data and control channel. Both channels are > transported over one transport connection. This can either be an > SCTP association, with data and control channel are *separated* > by > the PPID, or an TCP connection, with data and control channel > being handled by a TCP mapping layer. > Accepted. > > When a name server boots up a UDP multicast message may be sent out > for initial detection of other name servers in the operational > scope. > The other name servers send an answer using a unicast UDP message. > > Aren't we addressing multicast at a later time? If so, delete this > paragraph. We do not address this later in this doc. > Otherwise, some nits: > > When a name server initializes a UDP multicast message may be > transmitted > for initial detection of other name servers in the operational > scope. > The other name servers send a response using a unicast UDP message. > Accepted. > 2.3.1 > > communication may not be know by the peer. > > Providing information to which PE the OU should failover can also be > very important. Consider the scenario given in the following figure. > > misspelled words: > > communication may not be *known* by the peer. > > Providing information to which PE the *PU* should failover can also > be > very important. Consider the scenario *presented* in the following > figure. > Accepted. > Figure 4 > > Two PE accessing the same PE > > Should be: > > Two PUs accessing the same PE > Accepted. > 2.3.2 Cookies > > Cookies may be sent from the PE to the PU if the PE wants to do > this. > The PU only stores the last received cookie. In case of a fail over > it sends this last received cookie to the new PE. > > some changes: > > Cookies may optionally be sent from the PE to the PU. > The PU only stores the last received cookie. In case of fail over > the PU sends this last received cookie to the new PE. > Accepted. > [Editors note] This section has not been updated. The examples will > be updated after the architecture has been finalized. > > Please delete this. > Accepted. > 3.1 > > After figure 8: > > > 1. the Signaling Gateway (SG) receives an incoming signaling > message > to be forwarded to the GWC. SG(X)'s ASAP layer would send an > ASAP > request to its "local" NS to request the list of pool elements > (PE's) of GWC (using (a)). The key used for this query is the > pool handle of the GWC. The ASAP layer queues the data to be > sent > in local buffers until the NS responds. > > Don't use the word "key" for this as it sounds like some security key. > Use bit string or some other phrase. > I just deleted the sentence 'The key used for this query is the pool handle of the GWC.' > some change: > > The bit string used for this query is the > pool handle of the GWC. The ASAP layer queues the data to be > sent to the GWC > in local buffers until the NS responds. I accepted the change to the second sentence. > > > OK, I think that is it for now. > > -- maureen > > > _______________________________________________ > rserpool mailing list > rserpool@ietf.org > https://www1.ietf.org/mailman/listinfo/rserpool > _______________________________________________ rserpool mailing list rserpool@ietf.org https://www1.ietf.org/mailman/listinfo/rserpool From rserpool-admin@ietf.org Sun Oct 12 17:03:21 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA29304 for ; Sun, 12 Oct 2003 17:03:21 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A8nMi-0004BU-Ku; Sun, 12 Oct 2003 17:03:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A8nLy-0004Ao-Hj for rserpool@optimus.ietf.org; Sun, 12 Oct 2003 17:02:14 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA29247 for ; Sun, 12 Oct 2003 17:02:04 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A8nLw-00037Z-00 for rserpool@ietf.org; Sun, 12 Oct 2003 17:02:12 -0400 Received: from mail-n.franken.de ([193.175.24.27] ident=postfix) by ietf-mx with esmtp (Exim 4.12) id 1A8nLv-00037V-00 for rserpool@ietf.org; Sun, 12 Oct 2003 17:02:11 -0400 Received: from [10.0.1.2] (p5089F6D1.dip.t-dialin.net [80.137.246.209]) by mail-n.franken.de (Postfix) with ESMTP id DC3A3245CF for ; Sun, 12 Oct 2003 23:02:10 +0200 (CEST) Mime-Version: 1.0 (Apple Message framework v604) Content-Transfer-Encoding: 7bit Message-Id: <576EBE80-FCF7-11D7-8376-000A9591232C@lurchi.franken.de> Content-Type: text/plain; charset=US-ASCII; format=flowed To: rserpool@ietf.org From: Michael Tuexen Date: Sun, 12 Oct 2003 23:02:08 +0200 X-Mailer: Apple Mail (2.604) Content-Transfer-Encoding: 7bit Subject: [Rserpool] New version of draft-ietf-rserpool-arch-07.txt 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: , List-Id: Reliable Server Pooling List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Dear all, I have just submitted a new version of the architecture document. It is also available at http://www.sctp.de/internet-drafts.html The changes include - removal of Maureen and Lyndon from the list of authors to reduce the number of authors. - inclusion of the comments during the WG last call (mainly from Maureen). - floating around some figures to no have them split on two pages. - inclusion of the security considerations referring to the threats ID. What I missed: include Maureen and Lyndon in the Acknowledgment section. I will add this for the next version. I'm sorry for this. Best regards Michael _______________________________________________ rserpool mailing list rserpool@ietf.org https://www1.ietf.org/mailman/listinfo/rserpool From exim@www1.ietf.org Sun Oct 12 17:51:24 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA29307 for ; Sun, 12 Oct 2003 17:03:21 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A8nMj-0004C8-4w for rserpool-archive@odin.ietf.org; Sun, 12 Oct 2003 17:03:01 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9CL31nF016104 for rserpool-archive@odin.ietf.org; Sun, 12 Oct 2003 17:03:01 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A8nMi-0004BU-Ku; Sun, 12 Oct 2003 17:03:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A8nLy-0004Ao-Hj for rserpool@optimus.ietf.org; Sun, 12 Oct 2003 17:02:14 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA29247 for ; Sun, 12 Oct 2003 17:02:04 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A8nLw-00037Z-00 for rserpool@ietf.org; Sun, 12 Oct 2003 17:02:12 -0400 Received: from mail-n.franken.de ([193.175.24.27] ident=postfix) by ietf-mx with esmtp (Exim 4.12) id 1A8nLv-00037V-00 for rserpool@ietf.org; Sun, 12 Oct 2003 17:02:11 -0400 Received: from [10.0.1.2] (p5089F6D1.dip.t-dialin.net [80.137.246.209]) by mail-n.franken.de (Postfix) with ESMTP id DC3A3245CF for ; Sun, 12 Oct 2003 23:02:10 +0200 (CEST) Mime-Version: 1.0 (Apple Message framework v604) Content-Transfer-Encoding: 7bit Message-Id: <576EBE80-FCF7-11D7-8376-000A9591232C@lurchi.franken.de> Content-Type: text/plain; charset=US-ASCII; format=flowed To: rserpool@ietf.org From: Michael Tuexen Date: Sun, 12 Oct 2003 23:02:08 +0200 X-Mailer: Apple Mail (2.604) Content-Transfer-Encoding: 7bit Subject: [Rserpool] New version of draft-ietf-rserpool-arch-07.txt 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: , List-Id: Reliable Server Pooling List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Dear all, I have just submitted a new version of the architecture document. It is also available at http://www.sctp.de/internet-drafts.html The changes include - removal of Maureen and Lyndon from the list of authors to reduce the number of authors. - inclusion of the comments during the WG last call (mainly from Maureen). - floating around some figures to no have them split on two pages. - inclusion of the security considerations referring to the threats ID. What I missed: include Maureen and Lyndon in the Acknowledgment section. I will add this for the next version. I'm sorry for this. Best regards Michael _______________________________________________ rserpool mailing list rserpool@ietf.org https://www1.ietf.org/mailman/listinfo/rserpool From exim@www1.ietf.org Mon Oct 13 16:06:24 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA24688 for ; Mon, 13 Oct 2003 16:06:24 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A98x9-0006Fu-67 for rserpool-archive@odin.ietf.org; Mon, 13 Oct 2003 16:06:03 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9DK637c024045 for rserpool-archive@odin.ietf.org; Mon, 13 Oct 2003 16:06:03 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A98x6-0006FC-5r; Mon, 13 Oct 2003 16:06:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A98oh-00053j-P4 for rserpool@optimus.ietf.org; Mon, 13 Oct 2003 15:57:19 -0400 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA24135; Mon, 13 Oct 2003 15:57:10 -0400 (EDT) Message-Id: <200310131957.PAA24135@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: rserpool@ietf.org From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Date: Mon, 13 Oct 2003 15:57:10 -0400 Subject: [Rserpool] I-D ACTION:draft-ietf-rserpool-arch-07.txt 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: , List-Id: Reliable Server Pooling List-Post: List-Help: List-Subscribe: , --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Reliable Server Pooling Working Group of the IETF. Title : Architecture for Reliable Server Pooling Author(s) : M. Tuexen, Q. Xie, et. al. Filename : draft-ietf-rserpool-arch-07.txt Pages : 22 Date : 2003-10-13 This document describes an architecture and protocols for the management and operation of server pools supporting highly reliable applications, and for client access mechanisms to a server pool. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-rserpool-arch-07.txt To remove yourself from the IETF Announcement list, send a message to ietf-announce-request with the word unsubscribe in the body of the message. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-rserpool-arch-07.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-rserpool-arch-07.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2003-10-13145837.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-rserpool-arch-07.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-rserpool-arch-07.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2003-10-13145837.I-D@ietf.org> --OtherAccess-- --NextPart-- _______________________________________________ rserpool mailing list rserpool@ietf.org https://www1.ietf.org/mailman/listinfo/rserpool From rserpool-admin@ietf.org Mon Oct 13 16:51:34 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA24687 for ; Mon, 13 Oct 2003 16:06:24 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A98x6-0006FC-5r; Mon, 13 Oct 2003 16:06:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A98oh-00053j-P4 for rserpool@optimus.ietf.org; Mon, 13 Oct 2003 15:57:19 -0400 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA24135; Mon, 13 Oct 2003 15:57:10 -0400 (EDT) Message-Id: <200310131957.PAA24135@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: rserpool@ietf.org From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Date: Mon, 13 Oct 2003 15:57:10 -0400 Subject: [Rserpool] I-D ACTION:draft-ietf-rserpool-arch-07.txt 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: , List-Id: Reliable Server Pooling List-Post: List-Help: List-Subscribe: , --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Reliable Server Pooling Working Group of the IETF. Title : Architecture for Reliable Server Pooling Author(s) : M. Tuexen, Q. Xie, et. al. Filename : draft-ietf-rserpool-arch-07.txt Pages : 22 Date : 2003-10-13 This document describes an architecture and protocols for the management and operation of server pools supporting highly reliable applications, and for client access mechanisms to a server pool. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-rserpool-arch-07.txt To remove yourself from the IETF Announcement list, send a message to ietf-announce-request with the word unsubscribe in the body of the message. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-rserpool-arch-07.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-rserpool-arch-07.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2003-10-13145837.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-rserpool-arch-07.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-rserpool-arch-07.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2003-10-13145837.I-D@ietf.org> --OtherAccess-- --NextPart-- _______________________________________________ rserpool mailing list rserpool@ietf.org https://www1.ietf.org/mailman/listinfo/rserpool From rserpool-admin@ietf.org Wed Oct 22 04:37:21 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA29001 for ; Wed, 22 Oct 2003 04:37:21 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACEUH-00047j-4a; Wed, 22 Oct 2003 04:37:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AADpr-0005Ho-Da for rserpool@optimus.ietf.org; Thu, 16 Oct 2003 15:30:59 -0400 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA19138; Thu, 16 Oct 2003 15:30:49 -0400 (EDT) Message-Id: <200310161930.PAA19138@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: rserpool@ietf.org From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Date: Thu, 16 Oct 2003 15:30:49 -0400 Subject: [Rserpool] I-D ACTION:draft-ietf-rserpool-applic-01.txt 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: , List-Id: Reliable Server Pooling List-Post: List-Help: List-Subscribe: , --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Reliable Server Pooling Working Group of the IETF. Title : Reliable Server pool applicability Statement Author(s) : L. Coene, et. al. Filename : draft-ietf-rserpool-applic-01.txt Pages : 15 Date : 2003-10-16 This document describes the applicability of the reliable server pool architecture and protocols to applications which want to have High avialebility services. This is accomplished by using redundant servers and failover between servers of the same pool in case of server failure. Processing load in a pool may de distributed/shared between the members of the pool according to a certain policy. Also some guidance is given on the choice of underlying transport protocol (and corresponding transport protocol mapping) for transporting application data and Rserpool specific control data. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-rserpool-applic-01.txt To remove yourself from the IETF Announcement list, send a message to ietf-announce-request with the word unsubscribe in the body of the message. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-rserpool-applic-01.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-rserpool-applic-01.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2003-10-16143806.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-rserpool-applic-01.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-rserpool-applic-01.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2003-10-16143806.I-D@ietf.org> --OtherAccess-- --NextPart-- _______________________________________________ rserpool mailing list rserpool@ietf.org https://www1.ietf.org/mailman/listinfo/rserpool From rserpool-admin@ietf.org Wed Oct 22 04:37:27 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA29046 for ; Wed, 22 Oct 2003 04:37:26 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACEUH-00048A-O7; Wed, 22 Oct 2003 04:37:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AAaO8-0006MP-6C for rserpool@optimus.ietf.org; Fri, 17 Oct 2003 15:35:52 -0400 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA18480; Fri, 17 Oct 2003 15:35:42 -0400 (EDT) Message-Id: <200310171935.PAA18480@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: rserpool@ietf.org From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Date: Fri, 17 Oct 2003 15:35:42 -0400 Subject: [Rserpool] I-D ACTION:draft-ietf-rserpool-comp-07.txt 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: , List-Id: Reliable Server Pooling List-Post: List-Help: List-Subscribe: , --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Reliable Server Pooling Working Group of the IETF. Title : Comparison of Protocols for Reliable Server Pooling Author(s) : J. Loughney, et. al. Filename : draft-ietf-rserpool-comp-07.txt Pages : 22 Date : 2003-10-17 This document compares protocols that may be applicable for the Reliable Server Pooling problem space. This document discusses the usage and applicability of these protocols for the Reliable Server Pooling architecture. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-rserpool-comp-07.txt To remove yourself from the IETF Announcement list, send a message to ietf-announce-request with the word unsubscribe in the body of the message. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-rserpool-comp-07.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-rserpool-comp-07.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2003-10-17124128.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-rserpool-comp-07.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-rserpool-comp-07.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2003-10-17124128.I-D@ietf.org> --OtherAccess-- --NextPart-- _______________________________________________ rserpool mailing list rserpool@ietf.org https://www1.ietf.org/mailman/listinfo/rserpool From exim@www1.ietf.org Wed Oct 22 05:23:21 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA29003 for ; Wed, 22 Oct 2003 04:37:21 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACEUI-00048r-AI for rserpool-archive@odin.ietf.org; Wed, 22 Oct 2003 04:37:02 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9M8b2uW015898 for rserpool-archive@odin.ietf.org; Wed, 22 Oct 2003 04:37:02 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACEUH-00048A-O7; Wed, 22 Oct 2003 04:37:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AAaO8-0006MP-6C for rserpool@optimus.ietf.org; Fri, 17 Oct 2003 15:35:52 -0400 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA18480; Fri, 17 Oct 2003 15:35:42 -0400 (EDT) Message-Id: <200310171935.PAA18480@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: rserpool@ietf.org From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Date: Fri, 17 Oct 2003 15:35:42 -0400 Subject: [Rserpool] I-D ACTION:draft-ietf-rserpool-comp-07.txt 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: , List-Id: Reliable Server Pooling List-Post: List-Help: List-Subscribe: , --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Reliable Server Pooling Working Group of the IETF. Title : Comparison of Protocols for Reliable Server Pooling Author(s) : J. Loughney, et. al. Filename : draft-ietf-rserpool-comp-07.txt Pages : 22 Date : 2003-10-17 This document compares protocols that may be applicable for the Reliable Server Pooling problem space. This document discusses the usage and applicability of these protocols for the Reliable Server Pooling architecture. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-rserpool-comp-07.txt To remove yourself from the IETF Announcement list, send a message to ietf-announce-request with the word unsubscribe in the body of the message. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-rserpool-comp-07.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-rserpool-comp-07.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2003-10-17124128.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-rserpool-comp-07.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-rserpool-comp-07.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2003-10-17124128.I-D@ietf.org> --OtherAccess-- --NextPart-- _______________________________________________ rserpool mailing list rserpool@ietf.org https://www1.ietf.org/mailman/listinfo/rserpool From exim@www1.ietf.org Wed Oct 22 05:23:21 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA29004 for ; Wed, 22 Oct 2003 04:37:21 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACEUI-00048x-BH for rserpool-archive@odin.ietf.org; Wed, 22 Oct 2003 04:37:02 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9M8b2Yk015905 for rserpool-archive@odin.ietf.org; Wed, 22 Oct 2003 04:37:02 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACEUH-00047j-4a; Wed, 22 Oct 2003 04:37:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AADpr-0005Ho-Da for rserpool@optimus.ietf.org; Thu, 16 Oct 2003 15:30:59 -0400 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA19138; Thu, 16 Oct 2003 15:30:49 -0400 (EDT) Message-Id: <200310161930.PAA19138@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: rserpool@ietf.org From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Date: Thu, 16 Oct 2003 15:30:49 -0400 Subject: [Rserpool] I-D ACTION:draft-ietf-rserpool-applic-01.txt 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: , List-Id: Reliable Server Pooling List-Post: List-Help: List-Subscribe: , --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Reliable Server Pooling Working Group of the IETF. Title : Reliable Server pool applicability Statement Author(s) : L. Coene, et. al. Filename : draft-ietf-rserpool-applic-01.txt Pages : 15 Date : 2003-10-16 This document describes the applicability of the reliable server pool architecture and protocols to applications which want to have High avialebility services. This is accomplished by using redundant servers and failover between servers of the same pool in case of server failure. Processing load in a pool may de distributed/shared between the members of the pool according to a certain policy. Also some guidance is given on the choice of underlying transport protocol (and corresponding transport protocol mapping) for transporting application data and Rserpool specific control data. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-rserpool-applic-01.txt To remove yourself from the IETF Announcement list, send a message to ietf-announce-request with the word unsubscribe in the body of the message. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-rserpool-applic-01.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-rserpool-applic-01.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2003-10-16143806.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-rserpool-applic-01.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-rserpool-applic-01.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2003-10-16143806.I-D@ietf.org> --OtherAccess-- --NextPart-- _______________________________________________ rserpool mailing list rserpool@ietf.org https://www1.ietf.org/mailman/listinfo/rserpool From rserpool-admin@ietf.org Thu Oct 23 11:24:22 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA28937 for ; Thu, 23 Oct 2003 11:24:21 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AChJh-0005yS-9o; Thu, 23 Oct 2003 11:24:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AChJB-0005sL-FJ for rserpool@optimus.ietf.org; Thu, 23 Oct 2003 11:23:29 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA28900 for ; Thu, 23 Oct 2003 11:23:19 -0400 (EDT) From: Maureen.Stillman@nokia.com Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AChJA-0002Ic-00 for rserpool@ietf.org; Thu, 23 Oct 2003 11:23:28 -0400 Received: from mgw-x1.nokia.com ([131.228.20.21]) by ietf-mx with esmtp (Exim 4.12) id 1AChJ9-0002IZ-00 for rserpool@ietf.org; Thu, 23 Oct 2003 11:23:28 -0400 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 h9NFNRI07061 for ; Thu, 23 Oct 2003 18:23:27 +0300 (EET DST) Received: from daebh002.NOE.Nokia.com (unverified) by esvir05nok.ntc.nokia.com (Content Technologies SMTPRS 4.2.5) with ESMTP id for ; Thu, 23 Oct 2003 18:23:26 +0300 Received: from daebe007.NOE.Nokia.com ([172.18.242.211]) by daebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6747); Thu, 23 Oct 2003 10:23:25 -0500 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: Thu, 23 Oct 2003 10:23:25 -0500 Message-ID: <57A26D272F67A743952F6B4371B8F811021CFF7F@daebe007.americas.nokia.com> Thread-Topic: Draft Agenda for Reliable Server Pooling, IETF #58 Thread-Index: AcOZeZnWZ3TRtzN5QkSCLrCO97xDaQ== To: X-OriginalArrivalTime: 23 Oct 2003 15:23:25.0100 (UTC) FILETIME=[9A0AD6C0:01C39979] Content-Transfer-Encoding: quoted-printable Subject: [Rserpool] Draft Agenda for Reliable Server Pooling, 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: , List-Id: Reliable Server Pooling List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Please send comments on this draft agenda. Thanks. -- maureen Reliable Server Pooling WG (rserpool) 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 CHAIRs: Lyndon Ong =20 Maureen Stillman Draft AGENDA: Opening Remarks Lyndon Ong, Maureen Stillman Rserpool services, 10 min. http://www.ietf.org/internet-drafts/draft-conrad-rserpool-service-02.txt Phil Conrad, 10 min. TCP mapping http://www.ietf.org/internet-drafts/draft-rserpool-tcpmapping-00.txt Peter Lei, 10 min. Rserpool architecture http://www.ietf.org/internet-drafts/draft-ietf-rserpool-arch-07.txt Michael Tuexen, 10 min. ENRP and ASAP issues and updates 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 Randy Stewart, Qiaobing Xie, 20 min. Security http://www.ietf.org/internet-drafts/draft-ietf-rserpool-threats-02.txt Maureen Stillman, 10 min. Applicability Statement http://www.ietf.org/internet-drafts/draft-rserpool-applic-01.txt Lode Coene, 10 min. http://www.ietf.org/internet-drafts/draft-rserpool-comparison-07.txt Update on implementations of Rserpool Aron Silverton, 10 min. Redundancy model http://www.ietf.org/internet-drafts/draft-xie-rserpool-redundancy-model-0= 0.txt Qiaobing Xie, 10 min. Closing Remarks Lyndon Ong, Maureen Stillman _______________________________________________ rserpool mailing list rserpool@ietf.org https://www1.ietf.org/mailman/listinfo/rserpool From exim@www1.ietf.org Thu Oct 23 12:13:33 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA28938 for ; Thu, 23 Oct 2003 11:24:22 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AChJh-0005yq-S0 for rserpool-archive@odin.ietf.org; Thu, 23 Oct 2003 11:24:01 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9NFO1QO022982 for rserpool-archive@odin.ietf.org; Thu, 23 Oct 2003 11:24:01 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AChJh-0005yS-9o; Thu, 23 Oct 2003 11:24:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AChJB-0005sL-FJ for rserpool@optimus.ietf.org; Thu, 23 Oct 2003 11:23:29 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA28900 for ; Thu, 23 Oct 2003 11:23:19 -0400 (EDT) From: Maureen.Stillman@nokia.com Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AChJA-0002Ic-00 for rserpool@ietf.org; Thu, 23 Oct 2003 11:23:28 -0400 Received: from mgw-x1.nokia.com ([131.228.20.21]) by ietf-mx with esmtp (Exim 4.12) id 1AChJ9-0002IZ-00 for rserpool@ietf.org; Thu, 23 Oct 2003 11:23:28 -0400 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 h9NFNRI07061 for ; Thu, 23 Oct 2003 18:23:27 +0300 (EET DST) Received: from daebh002.NOE.Nokia.com (unverified) by esvir05nok.ntc.nokia.com (Content Technologies SMTPRS 4.2.5) with ESMTP id for ; Thu, 23 Oct 2003 18:23:26 +0300 Received: from daebe007.NOE.Nokia.com ([172.18.242.211]) by daebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6747); Thu, 23 Oct 2003 10:23:25 -0500 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: Thu, 23 Oct 2003 10:23:25 -0500 Message-ID: <57A26D272F67A743952F6B4371B8F811021CFF7F@daebe007.americas.nokia.com> Thread-Topic: Draft Agenda for Reliable Server Pooling, IETF #58 Thread-Index: AcOZeZnWZ3TRtzN5QkSCLrCO97xDaQ== To: X-OriginalArrivalTime: 23 Oct 2003 15:23:25.0100 (UTC) FILETIME=[9A0AD6C0:01C39979] Content-Transfer-Encoding: quoted-printable Subject: [Rserpool] Draft Agenda for Reliable Server Pooling, 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: , List-Id: Reliable Server Pooling List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Please send comments on this draft agenda. Thanks. -- maureen Reliable Server Pooling WG (rserpool) 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 CHAIRs: Lyndon Ong =20 Maureen Stillman Draft AGENDA: Opening Remarks Lyndon Ong, Maureen Stillman Rserpool services, 10 min. http://www.ietf.org/internet-drafts/draft-conrad-rserpool-service-02.txt Phil Conrad, 10 min. TCP mapping http://www.ietf.org/internet-drafts/draft-rserpool-tcpmapping-00.txt Peter Lei, 10 min. Rserpool architecture http://www.ietf.org/internet-drafts/draft-ietf-rserpool-arch-07.txt Michael Tuexen, 10 min. ENRP and ASAP issues and updates 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 Randy Stewart, Qiaobing Xie, 20 min. Security http://www.ietf.org/internet-drafts/draft-ietf-rserpool-threats-02.txt Maureen Stillman, 10 min. Applicability Statement http://www.ietf.org/internet-drafts/draft-rserpool-applic-01.txt Lode Coene, 10 min. http://www.ietf.org/internet-drafts/draft-rserpool-comparison-07.txt Update on implementations of Rserpool Aron Silverton, 10 min. Redundancy model http://www.ietf.org/internet-drafts/draft-xie-rserpool-redundancy-model-0= 0.txt Qiaobing Xie, 10 min. Closing Remarks Lyndon Ong, Maureen Stillman _______________________________________________ rserpool mailing list rserpool@ietf.org https://www1.ietf.org/mailman/listinfo/rserpool From rserpool-admin@ietf.org Fri Oct 24 01:51:22 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA04277 for ; Fri, 24 Oct 2003 01:51:21 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACuqi-0004Gy-MB; Fri, 24 Oct 2003 01:51:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACupx-0004B4-VF for rserpool@optimus.ietf.org; Fri, 24 Oct 2003 01:50:13 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA04225 for ; Fri, 24 Oct 2003 01:50:03 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ACupu-0005lM-00 for rserpool@ietf.org; Fri, 24 Oct 2003 01:50:10 -0400 Received: from kairos.dsa.uqam.ca ([132.208.43.57]) by ietf-mx with esmtp (Exim 4.12) id 1ACupu-0005lC-00 for rserpool@ietf.org; Fri, 24 Oct 2003 01:50:10 -0400 Received: from mobilebill (Kairos.dsa.uqam.ca [132.208.43.57]) by Kairos.dsa.uqam.ca (8.11.4/8.11.4) with ESMTP id h9O5Rw111005; Fri, 24 Oct 2003 01:27:58 -0400 From: "bill" To: , Subject: RE: [Rserpool] Draft Agenda for Reliable Server Pooling, IETF #58 Date: Thu, 23 Oct 2003 22:49:08 -0700 Message-ID: <028101c399f2$8b27c2c0$70d912c0@mobilebill> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.3416 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 In-Reply-To: <57A26D272F67A743952F6B4371B8F811021CFF7F@daebe007.americas.nokia.com> Content-Transfer-Encoding: 7bit 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: , List-Id: Reliable Server Pooling List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Maureen/Lyndon, Ok - I have one comment on your agenda - it seems to be pretty full. Presentations that I have seen tend to have 10 minute Q/A sessions - much less time to actually present anything. For as important as this work is - would there be any way of asking for an additional agenda slot and giving a little more time to the presenters (I'd hate to be last on the agenda) On the other hand you seem to have only scheduled 90 minutes for a 120 minute slot - so maybe you can work out there Bill -----Original Message----- From: rserpool-admin@ietf.org [mailto:rserpool-admin@ietf.org] On Behalf Of Maureen.Stillman@nokia.com Sent: Thursday, October 23, 2003 8:23 AM To: rserpool@ietf.org Subject: [Rserpool] Draft Agenda for Reliable Server Pooling, IETF #58 Please send comments on this draft agenda. Thanks. -- maureen Reliable Server Pooling WG (rserpool) Monday, November 10, 2003 ================================= CHAIRs: Lyndon Ong Maureen Stillman Draft AGENDA: Opening Remarks Lyndon Ong, Maureen Stillman Rserpool services, 10 min. http://www.ietf.org/internet-drafts/draft-conrad-rserpool-service-02.txt Phil Conrad, 10 min. TCP mapping http://www.ietf.org/internet-drafts/draft-rserpool-tcpmapping-00.txt Peter Lei, 10 min. Rserpool architecture http://www.ietf.org/internet-drafts/draft-ietf-rserpool-arch-07.txt Michael Tuexen, 10 min. ENRP and ASAP issues and updates http://www.ietf.org/internet-drafts/draft-ietf-rserpool-common-param-04. txt http://www.ietf.org/internet-drafts/draft-ietf-rserpool-asap-07.txt http://www.ietf.org/internet-drafts/draft-ietf-rserpool-enrp-06.txt Randy Stewart, Qiaobing Xie, 20 min. Security http://www.ietf.org/internet-drafts/draft-ietf-rserpool-threats-02.txt Maureen Stillman, 10 min. Applicability Statement http://www.ietf.org/internet-drafts/draft-rserpool-applic-01.txt Lode Coene, 10 min. http://www.ietf.org/internet-drafts/draft-rserpool-comparison-07.txt Update on implementations of Rserpool Aron Silverton, 10 min. Redundancy model http://www.ietf.org/internet-drafts/draft-xie-rserpool-redundancy-model- 00.txt Qiaobing Xie, 10 min. Closing Remarks Lyndon Ong, Maureen Stillman _______________________________________________ rserpool mailing list rserpool@ietf.org https://www1.ietf.org/mailman/listinfo/rserpool _______________________________________________ rserpool mailing list rserpool@ietf.org https://www1.ietf.org/mailman/listinfo/rserpool From exim@www1.ietf.org Fri Oct 24 02:38:42 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA04279 for ; Fri, 24 Oct 2003 01:51:22 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACuqk-0004HJ-0J for rserpool-archive@odin.ietf.org; Fri, 24 Oct 2003 01:51:02 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9O5p1oE016441 for rserpool-archive@odin.ietf.org; Fri, 24 Oct 2003 01:51:01 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACuqi-0004Gy-MB; Fri, 24 Oct 2003 01:51:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACupx-0004B4-VF for rserpool@optimus.ietf.org; Fri, 24 Oct 2003 01:50:13 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA04225 for ; Fri, 24 Oct 2003 01:50:03 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ACupu-0005lM-00 for rserpool@ietf.org; Fri, 24 Oct 2003 01:50:10 -0400 Received: from kairos.dsa.uqam.ca ([132.208.43.57]) by ietf-mx with esmtp (Exim 4.12) id 1ACupu-0005lC-00 for rserpool@ietf.org; Fri, 24 Oct 2003 01:50:10 -0400 Received: from mobilebill (Kairos.dsa.uqam.ca [132.208.43.57]) by Kairos.dsa.uqam.ca (8.11.4/8.11.4) with ESMTP id h9O5Rw111005; Fri, 24 Oct 2003 01:27:58 -0400 From: "bill" To: , Subject: RE: [Rserpool] Draft Agenda for Reliable Server Pooling, IETF #58 Date: Thu, 23 Oct 2003 22:49:08 -0700 Message-ID: <028101c399f2$8b27c2c0$70d912c0@mobilebill> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.3416 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 In-Reply-To: <57A26D272F67A743952F6B4371B8F811021CFF7F@daebe007.americas.nokia.com> Content-Transfer-Encoding: 7bit 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: , List-Id: Reliable Server Pooling List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Maureen/Lyndon, Ok - I have one comment on your agenda - it seems to be pretty full. Presentations that I have seen tend to have 10 minute Q/A sessions - much less time to actually present anything. For as important as this work is - would there be any way of asking for an additional agenda slot and giving a little more time to the presenters (I'd hate to be last on the agenda) On the other hand you seem to have only scheduled 90 minutes for a 120 minute slot - so maybe you can work out there Bill -----Original Message----- From: rserpool-admin@ietf.org [mailto:rserpool-admin@ietf.org] On Behalf Of Maureen.Stillman@nokia.com Sent: Thursday, October 23, 2003 8:23 AM To: rserpool@ietf.org Subject: [Rserpool] Draft Agenda for Reliable Server Pooling, IETF #58 Please send comments on this draft agenda. Thanks. -- maureen Reliable Server Pooling WG (rserpool) Monday, November 10, 2003 ================================= CHAIRs: Lyndon Ong Maureen Stillman Draft AGENDA: Opening Remarks Lyndon Ong, Maureen Stillman Rserpool services, 10 min. http://www.ietf.org/internet-drafts/draft-conrad-rserpool-service-02.txt Phil Conrad, 10 min. TCP mapping http://www.ietf.org/internet-drafts/draft-rserpool-tcpmapping-00.txt Peter Lei, 10 min. Rserpool architecture http://www.ietf.org/internet-drafts/draft-ietf-rserpool-arch-07.txt Michael Tuexen, 10 min. ENRP and ASAP issues and updates http://www.ietf.org/internet-drafts/draft-ietf-rserpool-common-param-04. txt http://www.ietf.org/internet-drafts/draft-ietf-rserpool-asap-07.txt http://www.ietf.org/internet-drafts/draft-ietf-rserpool-enrp-06.txt Randy Stewart, Qiaobing Xie, 20 min. Security http://www.ietf.org/internet-drafts/draft-ietf-rserpool-threats-02.txt Maureen Stillman, 10 min. Applicability Statement http://www.ietf.org/internet-drafts/draft-rserpool-applic-01.txt Lode Coene, 10 min. http://www.ietf.org/internet-drafts/draft-rserpool-comparison-07.txt Update on implementations of Rserpool Aron Silverton, 10 min. Redundancy model http://www.ietf.org/internet-drafts/draft-xie-rserpool-redundancy-model- 00.txt Qiaobing Xie, 10 min. Closing Remarks Lyndon Ong, Maureen Stillman _______________________________________________ rserpool mailing list rserpool@ietf.org https://www1.ietf.org/mailman/listinfo/rserpool _______________________________________________ rserpool mailing list rserpool@ietf.org https://www1.ietf.org/mailman/listinfo/rserpool From rserpool-admin@ietf.org Thu Oct 30 15:09:20 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA08636 for ; Thu, 30 Oct 2003 15:09:19 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AFJ6K-0006AB-NW; Thu, 30 Oct 2003 15:09:00 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AFJ5N-0005wQ-5E for rserpool@optimus.ietf.org; Thu, 30 Oct 2003 15:08:01 -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 PAA08450 for ; Thu, 30 Oct 2003 15:07:49 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AFJ5K-0001KR-00 for rserpool@ietf.org; Thu, 30 Oct 2003 15:07:58 -0500 Received: from ftpbox.mot.com ([129.188.136.101]) by ietf-mx with esmtp (Exim 4.12) id 1AFJ5I-0001KO-00 for rserpool@ietf.org; Thu, 30 Oct 2003 15:07:57 -0500 Received: from az33exr03.mot.com (pobox3.mot.com [10.64.251.242]) by ftpbox.mot.com (Motorola/Ftpbox) with ESMTP id h9UK7r9x029536 for ; Thu, 30 Oct 2003 13:07:53 -0700 (MST) Received: from il02exb02.corp.mot.com (il02exb02.corp.mot.com [10.0.100.67]) by az33exr03.mot.com (Motorola/az33exr03) with ESMTP id h9UK7p2M004348 for ; Thu, 30 Oct 2003 14:07:53 -0600 Received: by il02exb02.corp.mot.com with Internet Mail Service (5.5.2657.2) id ; Thu, 30 Oct 2003 14:07:50 -0600 Message-ID: <6F8DFFA2C996D711945800065BFC9E4A01F88E3B@il02exm11.corp.mot.com> From: Silverton Aron-C1710C To: "'rserpool@ietf.org'" Cc: Xie Qiaobing-QXIE1 , =?iso-8859-1?Q?=27Michael_T=FCxen=27?= , "'Thomas Dreibholz'" , "'conrad@acm.org'" Date: Thu, 30 Oct 2003 14:07:48 -0600 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.2) Content-Type: text/plain; charset="iso-8859-1" Subject: [Rserpool] RSERPOOL Implementation status updates 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: , List-Id: Reliable Server Pooling List-Post: List-Help: List-Subscribe: , Hello all, I will be updating the Implementation Status Report for the IETF meeting next month. I invite all of you to provide me with updates to the existing status report from earlier this year. Those slides are available at http://www.ietf.org/proceedings/03mar/slides/rserpool-4/index.html. Please provide any additional information not included in the existing template as you see fit. If you can provide details on your intended use and any modeling or simulation that you might have done, I would like to include that information as well. I understand if your day-job-provider puts limits on the amount of information that you can share. Regards, Aron Aron J. Silverton Senior Staff Research Engineer Motorola Labs, Networks and Infrastructure Research Motorola, Inc. Telephone: 847-576-8747 Fax: 847-576-3240 mailto:Aron.J.Silverton@motorola.com _______________________________________________ rserpool mailing list rserpool@ietf.org https://www1.ietf.org/mailman/listinfo/rserpool From exim@www1.ietf.org Thu Oct 30 15:09:21 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA08653 for ; Thu, 30 Oct 2003 15:09:21 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AFJ6L-0006An-AX for rserpool-archive@odin.ietf.org; Thu, 30 Oct 2003 15:09:02 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9UK91u9023710 for rserpool-archive@odin.ietf.org; Thu, 30 Oct 2003 15:09:01 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AFJ6K-0006AB-NW; Thu, 30 Oct 2003 15:09:00 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AFJ5N-0005wQ-5E for rserpool@optimus.ietf.org; Thu, 30 Oct 2003 15:08:01 -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 PAA08450 for ; Thu, 30 Oct 2003 15:07:49 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AFJ5K-0001KR-00 for rserpool@ietf.org; Thu, 30 Oct 2003 15:07:58 -0500 Received: from ftpbox.mot.com ([129.188.136.101]) by ietf-mx with esmtp (Exim 4.12) id 1AFJ5I-0001KO-00 for rserpool@ietf.org; Thu, 30 Oct 2003 15:07:57 -0500 Received: from az33exr03.mot.com (pobox3.mot.com [10.64.251.242]) by ftpbox.mot.com (Motorola/Ftpbox) with ESMTP id h9UK7r9x029536 for ; Thu, 30 Oct 2003 13:07:53 -0700 (MST) Received: from il02exb02.corp.mot.com (il02exb02.corp.mot.com [10.0.100.67]) by az33exr03.mot.com (Motorola/az33exr03) with ESMTP id h9UK7p2M004348 for ; Thu, 30 Oct 2003 14:07:53 -0600 Received: by il02exb02.corp.mot.com with Internet Mail Service (5.5.2657.2) id ; Thu, 30 Oct 2003 14:07:50 -0600 Message-ID: <6F8DFFA2C996D711945800065BFC9E4A01F88E3B@il02exm11.corp.mot.com> From: Silverton Aron-C1710C To: "'rserpool@ietf.org'" Cc: Xie Qiaobing-QXIE1 , =?iso-8859-1?Q?=27Michael_T=FCxen=27?= , "'Thomas Dreibholz'" , "'conrad@acm.org'" Date: Thu, 30 Oct 2003 14:07:48 -0600 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.2) Content-Type: text/plain; charset="iso-8859-1" Subject: [Rserpool] RSERPOOL Implementation status updates 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: , List-Id: Reliable Server Pooling List-Post: List-Help: List-Subscribe: , Hello all, I will be updating the Implementation Status Report for the IETF meeting next month. I invite all of you to provide me with updates to the existing status report from earlier this year. Those slides are available at http://www.ietf.org/proceedings/03mar/slides/rserpool-4/index.html. Please provide any additional information not included in the existing template as you see fit. If you can provide details on your intended use and any modeling or simulation that you might have done, I would like to include that information as well. I understand if your day-job-provider puts limits on the amount of information that you can share. Regards, Aron Aron J. Silverton Senior Staff Research Engineer Motorola Labs, Networks and Infrastructure Research Motorola, Inc. Telephone: 847-576-8747 Fax: 847-576-3240 mailto:Aron.J.Silverton@motorola.com _______________________________________________ rserpool mailing list rserpool@ietf.org https://www1.ietf.org/mailman/listinfo/rserpool