From mailman-admin@ietf.org Sun Feb 1 09:17:36 2004 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA14442 for ; Sun, 1 Feb 2004 09:17:36 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AnIPN-0001sb-UL for rserpool-archive@lists.ietf.org; Sun, 01 Feb 2004 09:17:09 -0500 Date: Sun, 01 Feb 2004 09:17:09 -0500 Message-ID: <20040201141709.1364.11412.Mailman@www1.ietf.org> Subject: ietf.org mailing list memberships reminder From: mailman-owner@www1.ietf.org To: rserpool-archive@ietf.org X-No-Archive: yes X-Ack: no Sender: mailman-admin@ietf.org Errors-To: mailman-admin@ietf.org X-BeenThere: mailman@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk This is a reminder, sent out once a month, about your ietf.org mailing list memberships. It includes your subscription info and how to use it to change it or unsubscribe from a list. You can visit the URLs to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on. In addition to the URL interfaces, you can also use email to make such changes. For more info, send a message to the '-request' address of the list (for example, rserpool-request@ietf.org) containing just the word 'help' in the message body, and an email message will be sent to you with instructions. *************************************************************************** Note Well All statements related to the activities of the IETF and addressed to the IETF are subject to all provisions of Section 10 of RFC 2026, which grants to the IETF and its participants certain licenses and rights in such statements. Such statements include verbal statements in IETF meetings, as well as written and electronic communications made at any time or place, which are addressed to * the IETF plenary session, * any IETF working group or portion thereof, * the IESG, or any member thereof on behalf of the IESG, * the IAB or any member thereof on behalf of the IAB, * any IETF mailing list, including the IETF list itself, any working group or design team list, or any other list functioning under IETF auspices, * the RFC Editor or the Internet-Drafts function Statements made outside of an IETF meeting, mailing list or other function, that are clearly not intended to be input to an IETF activity, group or function, are not subject to these provisions. *************************************************************************** If you have questions, problems, comments, etc, send them to mailman-owner@www1.ietf.org. Thanks! Passwords for rserpool-archive@lists.ietf.org: List Password // URL ---- -------- rserpool@ietf.org RVOD https://www1.ietf.org/mailman/options/rserpool/rserpool-archive%40lists.ietf.org From exim@www1.ietf.org Sun Feb 15 17:39:29 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA27918 for ; Sun, 15 Feb 2004 17:39:29 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AsUuk-0004aB-Bt for rserpool-archive@odin.ietf.org; Sun, 15 Feb 2004 17:39:02 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i1FMd2Ho017599 for rserpool-archive@odin.ietf.org; Sun, 15 Feb 2004 17:39:02 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AsUuj-0004Zb-NM; Sun, 15 Feb 2004 17:39:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AsUuh-0004ZB-Ni for rserpool@optimus.ietf.org; Sun, 15 Feb 2004 17:38:59 -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 RAA27911 for ; Sun, 15 Feb 2004 17:38:56 -0500 (EST) From: Maureen.Stillman@nokia.com Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AsUuf-0001Me-00 for rserpool@ietf.org; Sun, 15 Feb 2004 17:38:57 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AsUtj-0001Ie-00 for rserpool@ietf.org; Sun, 15 Feb 2004 17:38:00 -0500 Received: from mgw-x1.nokia.com ([131.228.20.21]) by ietf-mx with esmtp (Exim 4.12) id 1AsUtM-0001E7-00 for rserpool@ietf.org; Sun, 15 Feb 2004 17:37:36 -0500 Received: from esvir01nok.ntc.nokia.com (esvir01nokt.ntc.nokia.com [172.21.143.33]) by mgw-x1.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id i1FMbZ326218 for ; Mon, 16 Feb 2004 00:37:35 +0200 (EET) Received: from daebh001.NOE.Nokia.com (unverified) by esvir01nok.ntc.nokia.com (Content Technologies SMTPRS 4.2.5) with ESMTP id for ; Mon, 16 Feb 2004 00:37:35 +0200 Received: from daebe007.NOE.Nokia.com ([10.241.35.107]) by daebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6747); Sun, 15 Feb 2004 14:37:34 -0800 X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Date: Sun, 15 Feb 2004 16:37:34 -0600 Message-ID: <57A26D272F67A743952F6B4371B8F811021D00BA@daebe007.americas.nokia.com> Thread-Topic: Topics for Rserpool meeting at IETF #59 Thread-Index: AcP0FEvJsmKpX/ZORzCfTfUhDmSYnA== To: X-OriginalArrivalTime: 15 Feb 2004 22:37:34.0258 (UTC) FILETIME=[4E0E2920:01C3F414] X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.3 required=5.0 tests=AWL,NO_REAL_NAME autolearn=no version=2.60 Content-Transfer-Encoding: quoted-printable Subject: [Rserpool] Topics for Rserpool meeting at IETF #59 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 Any agenda topics for the Korea meeting? We are tentatively scheduled = for Wednesday afternoon. Thanks. -- maureen _______________________________________________ rserpool mailing list rserpool@ietf.org https://www1.ietf.org/mailman/listinfo/rserpool From rserpool-admin@ietf.org Sun Feb 15 18:24:30 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA27916 for ; Sun, 15 Feb 2004 17:39:29 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AsUuj-0004Zb-NM; Sun, 15 Feb 2004 17:39:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AsUuh-0004ZB-Ni for rserpool@optimus.ietf.org; Sun, 15 Feb 2004 17:38:59 -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 RAA27911 for ; Sun, 15 Feb 2004 17:38:56 -0500 (EST) From: Maureen.Stillman@nokia.com Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AsUuf-0001Me-00 for rserpool@ietf.org; Sun, 15 Feb 2004 17:38:57 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AsUtj-0001Ie-00 for rserpool@ietf.org; Sun, 15 Feb 2004 17:38:00 -0500 Received: from mgw-x1.nokia.com ([131.228.20.21]) by ietf-mx with esmtp (Exim 4.12) id 1AsUtM-0001E7-00 for rserpool@ietf.org; Sun, 15 Feb 2004 17:37:36 -0500 Received: from esvir01nok.ntc.nokia.com (esvir01nokt.ntc.nokia.com [172.21.143.33]) by mgw-x1.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id i1FMbZ326218 for ; Mon, 16 Feb 2004 00:37:35 +0200 (EET) Received: from daebh001.NOE.Nokia.com (unverified) by esvir01nok.ntc.nokia.com (Content Technologies SMTPRS 4.2.5) with ESMTP id for ; Mon, 16 Feb 2004 00:37:35 +0200 Received: from daebe007.NOE.Nokia.com ([10.241.35.107]) by daebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6747); Sun, 15 Feb 2004 14:37:34 -0800 X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Date: Sun, 15 Feb 2004 16:37:34 -0600 Message-ID: <57A26D272F67A743952F6B4371B8F811021D00BA@daebe007.americas.nokia.com> Thread-Topic: Topics for Rserpool meeting at IETF #59 Thread-Index: AcP0FEvJsmKpX/ZORzCfTfUhDmSYnA== To: X-OriginalArrivalTime: 15 Feb 2004 22:37:34.0258 (UTC) FILETIME=[4E0E2920:01C3F414] X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.3 required=5.0 tests=AWL,NO_REAL_NAME autolearn=no version=2.60 Content-Transfer-Encoding: quoted-printable Subject: [Rserpool] Topics for Rserpool meeting at IETF #59 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 Any agenda topics for the Korea meeting? We are tentatively scheduled = for Wednesday afternoon. Thanks. -- maureen _______________________________________________ rserpool mailing list rserpool@ietf.org https://www1.ietf.org/mailman/listinfo/rserpool From rserpool-admin@ietf.org Mon Feb 16 15:38:31 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA19508 for ; Mon, 16 Feb 2004 15:38:30 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AspVB-0001Yx-K0; Mon, 16 Feb 2004 15:38:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AspUy-0001X3-AM for rserpool@optimus.ietf.org; Mon, 16 Feb 2004 15:37:48 -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 PAA19365 for ; Mon, 16 Feb 2004 15:37:46 -0500 (EST) From: Maureen.Stillman@nokia.com Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AspUw-000291-00 for rserpool@ietf.org; Mon, 16 Feb 2004 15:37:46 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AspU1-00023u-00 for rserpool@ietf.org; Mon, 16 Feb 2004 15:36:50 -0500 Received: from mgw-x1.nokia.com ([131.228.20.21]) by ietf-mx with esmtp (Exim 4.12) id 1AspTV-0001yi-00 for rserpool@ietf.org; Mon, 16 Feb 2004 15:36:17 -0500 Received: from esvir01nok.ntc.nokia.com (esvir01nokt.ntc.nokia.com [172.21.143.33]) by mgw-x1.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id i1GKaG313183 for ; Mon, 16 Feb 2004 22:36:16 +0200 (EET) Received: from daebh002.NOE.Nokia.com (unverified) by esvir01nok.ntc.nokia.com (Content Technologies SMTPRS 4.2.5) with ESMTP id for ; Mon, 16 Feb 2004 22:36:15 +0200 Received: from daebe007.NOE.Nokia.com ([10.241.35.107]) by daebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6747); Mon, 16 Feb 2004 14:36:06 -0600 X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Date: Mon, 16 Feb 2004 14:36:06 -0600 Message-ID: <57A26D272F67A743952F6B4371B8F811021D00C1@daebe007.americas.nokia.com> Thread-Topic: Tentative agenda for IETF #59 Thread-Index: AcP0zIBadyQKu7nURL6j4SFDaJnlLw== To: X-OriginalArrivalTime: 16 Feb 2004 20:36:06.0606 (UTC) FILETIME=[80B076E0:01C3F4CC] X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.3 required=5.0 tests=AWL,NO_REAL_NAME autolearn=no version=2.60 Content-Transfer-Encoding: quoted-printable Subject: [Rserpool] Tentative agenda for IETF #59 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 Here is a tentative agenda for IETF #59. Please send me any additional = agenda items. Thanks. -- maureen Reliable Server Pooling WG (rserpool) =3D=3D=3D=3D=3D=3D=3D=3D=3D=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 AGENDA: Opening Remarks Lyndon Ong, Maureen Stillman Rserpool services, 20 min. http://www.ietf.org/internet-drafts/draft-ietf-rserpool-service-00.txt Michael Tuexen Rserpool architecture, 20 min. http://www.ietf.org/internet-drafts/draft-ietf-rserpool-arch-07.txt Michael Tuexen Security http://www.ietf.org/internet-drafts/draft-ietf-rserpool-threats-02.txt Maureen Stillman, 20 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 Mon Feb 16 16:29:40 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA19517 for ; Mon, 16 Feb 2004 15:38:31 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AspVC-0001Za-LK for rserpool-archive@odin.ietf.org; Mon, 16 Feb 2004 15:38:03 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i1GKc2rR006019 for rserpool-archive@odin.ietf.org; Mon, 16 Feb 2004 15:38:02 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AspVB-0001Yx-K0; Mon, 16 Feb 2004 15:38:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AspUy-0001X3-AM for rserpool@optimus.ietf.org; Mon, 16 Feb 2004 15:37:48 -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 PAA19365 for ; Mon, 16 Feb 2004 15:37:46 -0500 (EST) From: Maureen.Stillman@nokia.com Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AspUw-000291-00 for rserpool@ietf.org; Mon, 16 Feb 2004 15:37:46 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AspU1-00023u-00 for rserpool@ietf.org; Mon, 16 Feb 2004 15:36:50 -0500 Received: from mgw-x1.nokia.com ([131.228.20.21]) by ietf-mx with esmtp (Exim 4.12) id 1AspTV-0001yi-00 for rserpool@ietf.org; Mon, 16 Feb 2004 15:36:17 -0500 Received: from esvir01nok.ntc.nokia.com (esvir01nokt.ntc.nokia.com [172.21.143.33]) by mgw-x1.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id i1GKaG313183 for ; Mon, 16 Feb 2004 22:36:16 +0200 (EET) Received: from daebh002.NOE.Nokia.com (unverified) by esvir01nok.ntc.nokia.com (Content Technologies SMTPRS 4.2.5) with ESMTP id for ; Mon, 16 Feb 2004 22:36:15 +0200 Received: from daebe007.NOE.Nokia.com ([10.241.35.107]) by daebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6747); Mon, 16 Feb 2004 14:36:06 -0600 X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Date: Mon, 16 Feb 2004 14:36:06 -0600 Message-ID: <57A26D272F67A743952F6B4371B8F811021D00C1@daebe007.americas.nokia.com> Thread-Topic: Tentative agenda for IETF #59 Thread-Index: AcP0zIBadyQKu7nURL6j4SFDaJnlLw== To: X-OriginalArrivalTime: 16 Feb 2004 20:36:06.0606 (UTC) FILETIME=[80B076E0:01C3F4CC] X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.3 required=5.0 tests=AWL,NO_REAL_NAME autolearn=no version=2.60 Content-Transfer-Encoding: quoted-printable Subject: [Rserpool] Tentative agenda for IETF #59 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 Here is a tentative agenda for IETF #59. Please send me any additional = agenda items. Thanks. -- maureen Reliable Server Pooling WG (rserpool) =3D=3D=3D=3D=3D=3D=3D=3D=3D=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 AGENDA: Opening Remarks Lyndon Ong, Maureen Stillman Rserpool services, 20 min. http://www.ietf.org/internet-drafts/draft-ietf-rserpool-service-00.txt Michael Tuexen Rserpool architecture, 20 min. http://www.ietf.org/internet-drafts/draft-ietf-rserpool-arch-07.txt Michael Tuexen Security http://www.ietf.org/internet-drafts/draft-ietf-rserpool-threats-02.txt Maureen Stillman, 20 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 Tue Feb 17 02:59:30 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA15429 for ; Tue, 17 Feb 2004 02:59:30 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1At08D-0002Jf-3P; Tue, 17 Feb 2004 02:59:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1At087-0002JL-Ac for rserpool@optimus.ietf.org; Tue, 17 Feb 2004 02:58:55 -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 CAA15423 for ; Tue, 17 Feb 2004 02:58:52 -0500 (EST) From: john.loughney@nokia.com Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1At083-00071E-00 for rserpool@ietf.org; Tue, 17 Feb 2004 02:58:51 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1At073-0006xn-00 for rserpool@ietf.org; Tue, 17 Feb 2004 02:57:49 -0500 Received: from mgw-x4.nokia.com ([131.228.20.27]) by ietf-mx with esmtp (Exim 4.12) id 1At066-0006vL-00 for rserpool@ietf.org; Tue, 17 Feb 2004 02:56:50 -0500 Received: from esvir04nok.ntc.nokia.com (esvir04nokt.ntc.nokia.com [172.21.143.36]) by mgw-x4.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id i1H7uov25634 for ; Tue, 17 Feb 2004 09:56:51 +0200 (EET) Received: from esebh004.NOE.Nokia.com (unverified) by esvir04nok.ntc.nokia.com (Content Technologies SMTPRS 4.2.5) with ESMTP id for ; Tue, 17 Feb 2004 09:56:50 +0200 Received: from esebh005.NOE.Nokia.com ([172.21.138.86]) by esebh004.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6747); Tue, 17 Feb 2004 09:56:51 +0200 Received: from esebe023.NOE.Nokia.com ([172.21.138.115]) by esebh005.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6747); Tue, 17 Feb 2004 09:56:50 +0200 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: Tue, 17 Feb 2004 09:56:34 +0200 Message-ID: Thread-Topic: AD review of draft-ietf-rserpool-comp-07 Thread-Index: AcO+tVAiee/RI0RJRjaNMogG3gpJoA2dQvXQ To: X-OriginalArrivalTime: 17 Feb 2004 07:56:50.0499 (UTC) FILETIME=[998BF130:01C3F52B] X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.3 required=5.0 tests=AWL,NO_REAL_NAME autolearn=no version=2.60 Content-Transfer-Encoding: quoted-printable Subject: [Rserpool] FW: AD review of draft-ietf-rserpool-comp-07 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 all, Jon Peterson sent these comments on draft-ietf-rserpool-comp-07. As I=20 was updating the document, I ran into some problems & I think some = discussions are needed. > This document does a nice amount of due diligence in evaluating = existing > solutions for the rserpool problem space. While I'm sure there are = others > that could have been included, this provides a pretty comprehensive = look at > the sorts of protocols out there that should be considered. >=20 > The section on DNS will probably attract the most attention from the = IESG. I > think there are two issues with that section as it stands: first, it = does > not discuss DDDS (RFC3401 passim); second, it does not discuss EPP > (draft-ietf-provreg-epp-09). Some sort of comparison with the = qualities of > those protocols is warranted, since they provide some qualities that, = say, > SRV does not. The potential use of URNs for pool handles should also = be > discussed along with DDDS. >=20 > In general, as well, the comparison to DNS seems a little questionable = in so > far as it assumes that there must be one protocol that performs the = function > of name resolution, keepalives, and NS provisioning. In fact, as I = commented > on the rserpool architecture document, those are separable functions = with > radically different properties and associated message exchanges, and = very > credible motivation is required to establish that a single protocol = should > be tooled to perform those functions. I think there are arguments to = made > against the use of the DNS for RSERPOOL, but I don't think it's fair = to say > that 'doesn't provide keepalives' is one of them. >=20 > In the SLP section (beginning of 2.3.3) in particular, the distinction > between a service-oriented and communication-oriented solution is a = little > obscure to me. But overall I think the analysis here is sound. Same = for the > analyis of L4/L7 switching. The main points raised are: 1) Discussion of RFC3401, etc. http://www.ietf.org/rfc/rfc3401.txt?number=3D3401 My general feeling is that DDDS will suffer similar problems as DNS, = in=20 terms of the lack of dynamicity in DDS. 2) Discussion of draft-ietf-provreg-epp-09 is more difficult. =20 http://www.ietf.org/internet-drafts/draft-ietf-provreg-epp-09 EPP looks at some levels like it could provide some solutions, but = just in different ways than what has originally been thought of. I would = need some other folks to review EPP and DDS, to see what other folks = think. 3) Support for URNs. We have some discussions on namespace issues & identifiers for RserPool. If we don't want to support URNs, we need good reasons why we think that URNS are not a good idea for Rserool. 4) Text about SLP & l4/l7 I can probably fix. thanks, John _______________________________________________ rserpool mailing list rserpool@ietf.org https://www1.ietf.org/mailman/listinfo/rserpool From exim@www1.ietf.org Tue Feb 17 03:44:46 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA15431 for ; Tue, 17 Feb 2004 02:59:30 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1At08E-0002K5-Q6 for rserpool-archive@odin.ietf.org; Tue, 17 Feb 2004 02:59:02 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i1H7x2Mt008923 for rserpool-archive@odin.ietf.org; Tue, 17 Feb 2004 02:59:02 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1At08D-0002Jf-3P; Tue, 17 Feb 2004 02:59:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1At087-0002JL-Ac for rserpool@optimus.ietf.org; Tue, 17 Feb 2004 02:58:55 -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 CAA15423 for ; Tue, 17 Feb 2004 02:58:52 -0500 (EST) From: john.loughney@nokia.com Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1At083-00071E-00 for rserpool@ietf.org; Tue, 17 Feb 2004 02:58:51 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1At073-0006xn-00 for rserpool@ietf.org; Tue, 17 Feb 2004 02:57:49 -0500 Received: from mgw-x4.nokia.com ([131.228.20.27]) by ietf-mx with esmtp (Exim 4.12) id 1At066-0006vL-00 for rserpool@ietf.org; Tue, 17 Feb 2004 02:56:50 -0500 Received: from esvir04nok.ntc.nokia.com (esvir04nokt.ntc.nokia.com [172.21.143.36]) by mgw-x4.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id i1H7uov25634 for ; Tue, 17 Feb 2004 09:56:51 +0200 (EET) Received: from esebh004.NOE.Nokia.com (unverified) by esvir04nok.ntc.nokia.com (Content Technologies SMTPRS 4.2.5) with ESMTP id for ; Tue, 17 Feb 2004 09:56:50 +0200 Received: from esebh005.NOE.Nokia.com ([172.21.138.86]) by esebh004.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6747); Tue, 17 Feb 2004 09:56:51 +0200 Received: from esebe023.NOE.Nokia.com ([172.21.138.115]) by esebh005.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6747); Tue, 17 Feb 2004 09:56:50 +0200 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: Tue, 17 Feb 2004 09:56:34 +0200 Message-ID: Thread-Topic: AD review of draft-ietf-rserpool-comp-07 Thread-Index: AcO+tVAiee/RI0RJRjaNMogG3gpJoA2dQvXQ To: X-OriginalArrivalTime: 17 Feb 2004 07:56:50.0499 (UTC) FILETIME=[998BF130:01C3F52B] X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.3 required=5.0 tests=AWL,NO_REAL_NAME autolearn=no version=2.60 Content-Transfer-Encoding: quoted-printable Subject: [Rserpool] FW: AD review of draft-ietf-rserpool-comp-07 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 all, Jon Peterson sent these comments on draft-ietf-rserpool-comp-07. As I=20 was updating the document, I ran into some problems & I think some = discussions are needed. > This document does a nice amount of due diligence in evaluating = existing > solutions for the rserpool problem space. While I'm sure there are = others > that could have been included, this provides a pretty comprehensive = look at > the sorts of protocols out there that should be considered. >=20 > The section on DNS will probably attract the most attention from the = IESG. I > think there are two issues with that section as it stands: first, it = does > not discuss DDDS (RFC3401 passim); second, it does not discuss EPP > (draft-ietf-provreg-epp-09). Some sort of comparison with the = qualities of > those protocols is warranted, since they provide some qualities that, = say, > SRV does not. The potential use of URNs for pool handles should also = be > discussed along with DDDS. >=20 > In general, as well, the comparison to DNS seems a little questionable = in so > far as it assumes that there must be one protocol that performs the = function > of name resolution, keepalives, and NS provisioning. In fact, as I = commented > on the rserpool architecture document, those are separable functions = with > radically different properties and associated message exchanges, and = very > credible motivation is required to establish that a single protocol = should > be tooled to perform those functions. I think there are arguments to = made > against the use of the DNS for RSERPOOL, but I don't think it's fair = to say > that 'doesn't provide keepalives' is one of them. >=20 > In the SLP section (beginning of 2.3.3) in particular, the distinction > between a service-oriented and communication-oriented solution is a = little > obscure to me. But overall I think the analysis here is sound. Same = for the > analyis of L4/L7 switching. The main points raised are: 1) Discussion of RFC3401, etc. http://www.ietf.org/rfc/rfc3401.txt?number=3D3401 My general feeling is that DDDS will suffer similar problems as DNS, = in=20 terms of the lack of dynamicity in DDS. 2) Discussion of draft-ietf-provreg-epp-09 is more difficult. =20 http://www.ietf.org/internet-drafts/draft-ietf-provreg-epp-09 EPP looks at some levels like it could provide some solutions, but = just in different ways than what has originally been thought of. I would = need some other folks to review EPP and DDS, to see what other folks = think. 3) Support for URNs. We have some discussions on namespace issues & identifiers for RserPool. If we don't want to support URNs, we need good reasons why we think that URNS are not a good idea for Rserool. 4) Text about SLP & l4/l7 I can probably fix. thanks, John _______________________________________________ rserpool mailing list rserpool@ietf.org https://www1.ietf.org/mailman/listinfo/rserpool From rserpool-admin@ietf.org Tue Feb 17 11:41:29 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA15221 for ; Tue, 17 Feb 2004 11:41:29 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1At8HM-00020i-P6; Tue, 17 Feb 2004 11:41:00 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1At8Gy-0001zu-TK for rserpool@optimus.ietf.org; Tue, 17 Feb 2004 11:40:36 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA15125 for ; Tue, 17 Feb 2004 11:40:34 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1At8Gx-0003NG-00 for rserpool@ietf.org; Tue, 17 Feb 2004 11:40:36 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1At8Fe-0003Ey-00 for rserpool@ietf.org; Tue, 17 Feb 2004 11:39:15 -0500 Received: from motgate8.mot.com ([129.188.136.8]) by ietf-mx with esmtp (Exim 4.12) id 1At8FH-0003Bg-00 for rserpool@ietf.org; Tue, 17 Feb 2004 11:38:52 -0500 Received: from az33exr03.mot.com (az33exr03.mot.com [10.64.251.233]) by motgate8.mot.com (Motorola/Motgate3) with ESMTP id i1HGcoAH013581 for ; Tue, 17 Feb 2004 09:38:51 -0700 (MST) Received: from il02exm11.corp.mot.com (il02exm11.corp.mot.com [10.0.111.22]) by az33exr03.mot.com (Motorola/az33exr03) with ESMTP id i1HGZEcQ014648 for ; Tue, 17 Feb 2004 10:35:25 -0600 Received: by il02exm11 with Internet Mail Service (5.5.2657.2) id <18YS95BS>; Tue, 17 Feb 2004 10:35:20 -0600 Message-ID: <6F8DFFA2C996D711945800065BFC9E4A0389878A@il02exm11> From: Silverton Aron-C1710C To: "'john.loughney@nokia.com'" , rserpool@ietf.org Subject: RE: [Rserpool] FW: AD review of draft-ietf-rserpool-comp-07 Date: Tue, 17 Feb 2004 10:35:11 -0600 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.2) Content-Type: text/plain X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 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: , john.loughney@nokia.com <> wrote: > Hi all, > >snip > > The main points raised are: > > 1) Discussion of RFC3401, etc. > http://www.ietf.org/rfc/rfc3401.txt?number=3401 > > My general feeling is that DDDS will suffer similar problems as > DNS, in terms of the lack of dynamicity in DDS. > > 2) Discussion of draft-ietf-provreg-epp-09 is more difficult. > > http://www.ietf.org/internet-drafts/draft-ietf-provreg-epp-09 > > EPP looks at some levels like it could provide some solutions, but > just in different ways than what has originally been thought of. > I would need some other folks to review EPP and DDS, to see what > other folks think. > > 3) Support for URNs. We have some discussions on namespace issues & > identifiers for RserPool. If we don't want to support URNs, we > need good reasons why we think that URNS are not a good idea for > Rserool. > > 4) Text about SLP & l4/l7 I can probably fix. John, according to Jon P's email, the L4/L7 stuff is ". . . I think the analysis here is sound. Same for the analysis of L4/L7 switching." So I wouldn't waste too many cycles on that unless you feel that there is something that needs to be changed. As for the other portions, I'm not familiar with them so I will have to read the drafts. I think that some of the comments that Qiaobing made in the past regarding loosely-coupled approaches of trying to integrate many protocols versus a tightly-coupled protocol (RSERPOOL) will hold here as well. All the more so if we stress that RSERPOOL is intended for system with some degree of real-time performance constraints. > > thanks, > John Aron > > _______________________________________________ > 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 Feb 17 12:29:49 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA15223 for ; Tue, 17 Feb 2004 11:41:29 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1At8HN-00021V-RR for rserpool-archive@odin.ietf.org; Tue, 17 Feb 2004 11:41:02 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i1HGf1TT007769 for rserpool-archive@odin.ietf.org; Tue, 17 Feb 2004 11:41:01 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1At8HM-00020i-P6; Tue, 17 Feb 2004 11:41:00 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1At8Gy-0001zu-TK for rserpool@optimus.ietf.org; Tue, 17 Feb 2004 11:40:36 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA15125 for ; Tue, 17 Feb 2004 11:40:34 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1At8Gx-0003NG-00 for rserpool@ietf.org; Tue, 17 Feb 2004 11:40:36 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1At8Fe-0003Ey-00 for rserpool@ietf.org; Tue, 17 Feb 2004 11:39:15 -0500 Received: from motgate8.mot.com ([129.188.136.8]) by ietf-mx with esmtp (Exim 4.12) id 1At8FH-0003Bg-00 for rserpool@ietf.org; Tue, 17 Feb 2004 11:38:52 -0500 Received: from az33exr03.mot.com (az33exr03.mot.com [10.64.251.233]) by motgate8.mot.com (Motorola/Motgate3) with ESMTP id i1HGcoAH013581 for ; Tue, 17 Feb 2004 09:38:51 -0700 (MST) Received: from il02exm11.corp.mot.com (il02exm11.corp.mot.com [10.0.111.22]) by az33exr03.mot.com (Motorola/az33exr03) with ESMTP id i1HGZEcQ014648 for ; Tue, 17 Feb 2004 10:35:25 -0600 Received: by il02exm11 with Internet Mail Service (5.5.2657.2) id <18YS95BS>; Tue, 17 Feb 2004 10:35:20 -0600 Message-ID: <6F8DFFA2C996D711945800065BFC9E4A0389878A@il02exm11> From: Silverton Aron-C1710C To: "'john.loughney@nokia.com'" , rserpool@ietf.org Subject: RE: [Rserpool] FW: AD review of draft-ietf-rserpool-comp-07 Date: Tue, 17 Feb 2004 10:35:11 -0600 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.2) Content-Type: text/plain X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 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: , john.loughney@nokia.com <> wrote: > Hi all, > >snip > > The main points raised are: > > 1) Discussion of RFC3401, etc. > http://www.ietf.org/rfc/rfc3401.txt?number=3401 > > My general feeling is that DDDS will suffer similar problems as > DNS, in terms of the lack of dynamicity in DDS. > > 2) Discussion of draft-ietf-provreg-epp-09 is more difficult. > > http://www.ietf.org/internet-drafts/draft-ietf-provreg-epp-09 > > EPP looks at some levels like it could provide some solutions, but > just in different ways than what has originally been thought of. > I would need some other folks to review EPP and DDS, to see what > other folks think. > > 3) Support for URNs. We have some discussions on namespace issues & > identifiers for RserPool. If we don't want to support URNs, we > need good reasons why we think that URNS are not a good idea for > Rserool. > > 4) Text about SLP & l4/l7 I can probably fix. John, according to Jon P's email, the L4/L7 stuff is ". . . I think the analysis here is sound. Same for the analysis of L4/L7 switching." So I wouldn't waste too many cycles on that unless you feel that there is something that needs to be changed. As for the other portions, I'm not familiar with them so I will have to read the drafts. I think that some of the comments that Qiaobing made in the past regarding loosely-coupled approaches of trying to integrate many protocols versus a tightly-coupled protocol (RSERPOOL) will hold here as well. All the more so if we stress that RSERPOOL is intended for system with some degree of real-time performance constraints. > > thanks, > John Aron > > _______________________________________________ > 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 Feb 17 15:27:29 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA02822 for ; Tue, 17 Feb 2004 15:27:29 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AtBo5-0003HQ-1O for rserpool-archive@odin.ietf.org; Tue, 17 Feb 2004 15:27:01 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i1HKR0YK012585 for rserpool-archive@odin.ietf.org; Tue, 17 Feb 2004 15:27:00 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AtBo4-0003Gs-IG; Tue, 17 Feb 2004 15:27:00 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AtBnW-0003Ej-3a for rserpool@optimus.ietf.org; Tue, 17 Feb 2004 15:26:26 -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 PAA02771 for ; Tue, 17 Feb 2004 15:26:23 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AtBnT-0001VJ-00 for rserpool@ietf.org; Tue, 17 Feb 2004 15:26:23 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AtBmc-0001PX-00 for rserpool@ietf.org; Tue, 17 Feb 2004 15:25:30 -0500 Received: from smtp02.uc3m.es ([163.117.136.122]) by ietf-mx with esmtp (Exim 4.12) id 1AtBll-0001Gc-00 for rserpool@ietf.org; Tue, 17 Feb 2004 15:24:37 -0500 Received: from smtp02.uc3m.es (localhost [127.0.0.1]) by localhost.uc3m.es (Postfix) with ESMTP id C70117F64; Tue, 17 Feb 2004 21:24:06 +0100 (CET) Received: from requiem.it.uc3m.es (requiem.it.uc3m.es [163.117.139.166]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by smtp02.uc3m.es (Postfix) with ESMTP id B36E47F47; Tue, 17 Feb 2004 21:24:06 +0100 (CET) Subject: RE: [Rserpool] FW: AD review of draft-ietf-rserpool-comp-07 From: Manuel =?ISO-8859-1?Q?Urue=F1a?= To: Silverton Aron-C1710C Cc: rserpool@ietf.org In-Reply-To: <6F8DFFA2C996D711945800065BFC9E4A0389878A@il02exm11> References: <6F8DFFA2C996D711945800065BFC9E4A0389878A@il02exm11> Content-Type: text/plain Organization: Universidad Carlos III de Madrid Message-Id: <1077049264.3614.37.camel@requiem.it.uc3m.es> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.4-8mdk Date: Tue, 17 Feb 2004 21:21:06 +0100 Content-Transfer-Encoding: 7bit X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 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 > ... > > As for the other portions, I'm not familiar with them so I will have to > read the drafts. I think that some of the comments that Qiaobing made > in the past regarding loosely-coupled approaches of trying to integrate > many protocols versus a tightly-coupled protocol (RSERPOOL) will hold > here as well. All the more so if we stress that RSERPOOL is intended > for system with some degree of real-time performance constraints. > > Aron What do you mean by systems with "real-time" performance constraints? If it means to quickly obtain the best server from a pool maybe the mandatory usage of SCTP is not an optimal solution. Let's imagine an user that wants to access a web-service served by a pool of servers. That means that first it has to establish a SCTP connection to the ENRP server (4-way handshake), get server info, and finally open a TCP connection (3-way handshake) to the selected web server for the HTTP transaction. It makes more or less 4,5 RTTs. It seems that querying ENRP servers via UDP will lead to better server-selection latency for "real-time" services (2'5 RTTS for TCP connections). Regards, --Manuel -- Manuel Uruen~a - Universidad Carlos III de Madrid GPG FP: 68A1 164B EE28 52C9 87CB EBF9 616E 52B5 451A B6B2 _______________________________________________ rserpool mailing list rserpool@ietf.org https://www1.ietf.org/mailman/listinfo/rserpool From rserpool-admin@ietf.org Tue Feb 17 16:14:51 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA02820 for ; Tue, 17 Feb 2004 15:27:29 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AtBo4-0003Gs-IG; Tue, 17 Feb 2004 15:27:00 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AtBnW-0003Ej-3a for rserpool@optimus.ietf.org; Tue, 17 Feb 2004 15:26:26 -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 PAA02771 for ; Tue, 17 Feb 2004 15:26:23 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AtBnT-0001VJ-00 for rserpool@ietf.org; Tue, 17 Feb 2004 15:26:23 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AtBmc-0001PX-00 for rserpool@ietf.org; Tue, 17 Feb 2004 15:25:30 -0500 Received: from smtp02.uc3m.es ([163.117.136.122]) by ietf-mx with esmtp (Exim 4.12) id 1AtBll-0001Gc-00 for rserpool@ietf.org; Tue, 17 Feb 2004 15:24:37 -0500 Received: from smtp02.uc3m.es (localhost [127.0.0.1]) by localhost.uc3m.es (Postfix) with ESMTP id C70117F64; Tue, 17 Feb 2004 21:24:06 +0100 (CET) Received: from requiem.it.uc3m.es (requiem.it.uc3m.es [163.117.139.166]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by smtp02.uc3m.es (Postfix) with ESMTP id B36E47F47; Tue, 17 Feb 2004 21:24:06 +0100 (CET) Subject: RE: [Rserpool] FW: AD review of draft-ietf-rserpool-comp-07 From: Manuel =?ISO-8859-1?Q?Urue=F1a?= To: Silverton Aron-C1710C Cc: rserpool@ietf.org In-Reply-To: <6F8DFFA2C996D711945800065BFC9E4A0389878A@il02exm11> References: <6F8DFFA2C996D711945800065BFC9E4A0389878A@il02exm11> Content-Type: text/plain Organization: Universidad Carlos III de Madrid Message-Id: <1077049264.3614.37.camel@requiem.it.uc3m.es> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.4-8mdk Date: Tue, 17 Feb 2004 21:21:06 +0100 Content-Transfer-Encoding: 7bit X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 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 > ... > > As for the other portions, I'm not familiar with them so I will have to > read the drafts. I think that some of the comments that Qiaobing made > in the past regarding loosely-coupled approaches of trying to integrate > many protocols versus a tightly-coupled protocol (RSERPOOL) will hold > here as well. All the more so if we stress that RSERPOOL is intended > for system with some degree of real-time performance constraints. > > Aron What do you mean by systems with "real-time" performance constraints? If it means to quickly obtain the best server from a pool maybe the mandatory usage of SCTP is not an optimal solution. Let's imagine an user that wants to access a web-service served by a pool of servers. That means that first it has to establish a SCTP connection to the ENRP server (4-way handshake), get server info, and finally open a TCP connection (3-way handshake) to the selected web server for the HTTP transaction. It makes more or less 4,5 RTTs. It seems that querying ENRP servers via UDP will lead to better server-selection latency for "real-time" services (2'5 RTTS for TCP connections). Regards, --Manuel -- Manuel Uruen~a - Universidad Carlos III de Madrid GPG FP: 68A1 164B EE28 52C9 87CB EBF9 616E 52B5 451A B6B2 _______________________________________________ rserpool mailing list rserpool@ietf.org https://www1.ietf.org/mailman/listinfo/rserpool From rserpool-admin@ietf.org Wed Feb 18 04:38:32 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA03821 for ; Wed, 18 Feb 2004 04:38:32 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AtO9a-0006P3-KW; Wed, 18 Feb 2004 04:38:02 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AtO9K-0006Mr-VO for rserpool@optimus.ietf.org; Wed, 18 Feb 2004 04:37:47 -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 EAA03807 for ; Wed, 18 Feb 2004 04:37:44 -0500 (EST) From: john.loughney@nokia.com Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AtO9I-0001Zr-00 for rserpool@ietf.org; Wed, 18 Feb 2004 04:37:44 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AtO8N-0001XM-00 for rserpool@ietf.org; Wed, 18 Feb 2004 04:36:48 -0500 Received: from mgw-x2.nokia.com ([131.228.20.22]) by ietf-mx with esmtp (Exim 4.12) id 1AtO7R-0001UL-00 for rserpool@ietf.org; Wed, 18 Feb 2004 04:35:49 -0500 Received: from esdks003.ntc.nokia.com (esdks003.ntc.nokia.com [172.21.138.158]) by mgw-x2.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id i1I9ZnT15467; Wed, 18 Feb 2004 11:35:49 +0200 (EET) X-Scanned: Wed, 18 Feb 2004 11:35:40 +0200 Nokia Message Protector V1.3.13 2004020314 - RELEASE Received: (from root@localhost) by esdks003.ntc.nokia.com (8.12.9/8.12.9) id i1I9Ze0R004952; Wed, 18 Feb 2004 11:35:40 +0200 Received: from mgw-int1.ntc.nokia.com (172.21.143.96) by esdks003.ntc.nokia.com 00Jb64Dc; Wed, 18 Feb 2004 11:35:39 EET Received: from esebh003.NOE.Nokia.com (esebh003.ntc.nokia.com [172.21.138.82]) by mgw-int1.ntc.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id i1I9Zb729835; Wed, 18 Feb 2004 11:35:37 +0200 (EET) Received: from esebe023.NOE.Nokia.com ([172.21.138.115]) by esebh003.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6747); Wed, 18 Feb 2004 11:35:33 +0200 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 Subject: RE: [Rserpool] FW: AD review of draft-ietf-rserpool-comp-07 Date: Wed, 18 Feb 2004 11:35:31 +0200 Message-ID: Thread-Topic: [Rserpool] FW: AD review of draft-ietf-rserpool-comp-07 Thread-Index: AcP1dBqHde9s4xfYTU+Rv/7OXouGDgAjk+2g To: , X-OriginalArrivalTime: 18 Feb 2004 09:35:33.0321 (UTC) FILETIME=[8E3C9B90:01C3F602] X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.3 required=5.0 tests=AWL,NO_REAL_NAME autolearn=no version=2.60 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 Aron, > > 4) Text about SLP & l4/l7 I can probably fix. >=20 > John, according to Jon P's email, the L4/L7 stuff is ". . . I=20 > think the analysis here is sound. Same for the analysis of=20 > L4/L7 switching." So I wouldn't waste too many cycles on=20 > that unless you feel that there is something that needs to be changed. Agreed. I think I can just try to clarify the text. =20 > As for the other portions, I'm not familiar with them so I=20 > will have to read the drafts. I think that some of the=20 > comments that Qiaobing made in the past regarding=20 > loosely-coupled approaches of trying to integrate many=20 > protocols versus a tightly-coupled protocol (RSERPOOL) will=20 > hold here as well. All the more so if we stress that=20 > RSERPOOL is intended for system with some degree of real-time=20 > performance constraints. I think we need to check the documents Jon pointed out & craft text to cover the issue. John _______________________________________________ rserpool mailing list rserpool@ietf.org https://www1.ietf.org/mailman/listinfo/rserpool From exim@www1.ietf.org Wed Feb 18 04:38:33 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA03827 for ; Wed, 18 Feb 2004 04:38:33 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AtO9c-0006Pw-TK for rserpool-archive@odin.ietf.org; Wed, 18 Feb 2004 04:38:05 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i1I9c4RZ024646 for rserpool-archive@odin.ietf.org; Wed, 18 Feb 2004 04:38:04 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AtO9a-0006P3-KW; Wed, 18 Feb 2004 04:38:02 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AtO9K-0006Mr-VO for rserpool@optimus.ietf.org; Wed, 18 Feb 2004 04:37:47 -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 EAA03807 for ; Wed, 18 Feb 2004 04:37:44 -0500 (EST) From: john.loughney@nokia.com Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AtO9I-0001Zr-00 for rserpool@ietf.org; Wed, 18 Feb 2004 04:37:44 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AtO8N-0001XM-00 for rserpool@ietf.org; Wed, 18 Feb 2004 04:36:48 -0500 Received: from mgw-x2.nokia.com ([131.228.20.22]) by ietf-mx with esmtp (Exim 4.12) id 1AtO7R-0001UL-00 for rserpool@ietf.org; Wed, 18 Feb 2004 04:35:49 -0500 Received: from esdks003.ntc.nokia.com (esdks003.ntc.nokia.com [172.21.138.158]) by mgw-x2.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id i1I9ZnT15467; Wed, 18 Feb 2004 11:35:49 +0200 (EET) X-Scanned: Wed, 18 Feb 2004 11:35:40 +0200 Nokia Message Protector V1.3.13 2004020314 - RELEASE Received: (from root@localhost) by esdks003.ntc.nokia.com (8.12.9/8.12.9) id i1I9Ze0R004952; Wed, 18 Feb 2004 11:35:40 +0200 Received: from mgw-int1.ntc.nokia.com (172.21.143.96) by esdks003.ntc.nokia.com 00Jb64Dc; Wed, 18 Feb 2004 11:35:39 EET Received: from esebh003.NOE.Nokia.com (esebh003.ntc.nokia.com [172.21.138.82]) by mgw-int1.ntc.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id i1I9Zb729835; Wed, 18 Feb 2004 11:35:37 +0200 (EET) Received: from esebe023.NOE.Nokia.com ([172.21.138.115]) by esebh003.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6747); Wed, 18 Feb 2004 11:35:33 +0200 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 Subject: RE: [Rserpool] FW: AD review of draft-ietf-rserpool-comp-07 Date: Wed, 18 Feb 2004 11:35:31 +0200 Message-ID: Thread-Topic: [Rserpool] FW: AD review of draft-ietf-rserpool-comp-07 Thread-Index: AcP1dBqHde9s4xfYTU+Rv/7OXouGDgAjk+2g To: , X-OriginalArrivalTime: 18 Feb 2004 09:35:33.0321 (UTC) FILETIME=[8E3C9B90:01C3F602] X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.3 required=5.0 tests=AWL,NO_REAL_NAME autolearn=no version=2.60 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 Aron, > > 4) Text about SLP & l4/l7 I can probably fix. >=20 > John, according to Jon P's email, the L4/L7 stuff is ". . . I=20 > think the analysis here is sound. Same for the analysis of=20 > L4/L7 switching." So I wouldn't waste too many cycles on=20 > that unless you feel that there is something that needs to be changed. Agreed. I think I can just try to clarify the text. =20 > As for the other portions, I'm not familiar with them so I=20 > will have to read the drafts. I think that some of the=20 > comments that Qiaobing made in the past regarding=20 > loosely-coupled approaches of trying to integrate many=20 > protocols versus a tightly-coupled protocol (RSERPOOL) will=20 > hold here as well. All the more so if we stress that=20 > RSERPOOL is intended for system with some degree of real-time=20 > performance constraints. I think we need to check the documents Jon pointed out & craft text to cover the issue. John _______________________________________________ rserpool mailing list rserpool@ietf.org https://www1.ietf.org/mailman/listinfo/rserpool