From sip-admin@ietf.org Tue Jul 1 09:26:08 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 JAA24743 for ; Tue, 1 Jul 2003 09:26:08 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19XL8e-0003Kl-Nz for rserpool-archive@lists.ietf.org; Tue, 01 Jul 2003 09:25:40 -0400 Date: Tue, 01 Jul 2003 09:25:40 -0400 Message-ID: <20030701132540.18162.5425.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: sip-admin@ietf.org Errors-To: sip-admin@ietf.org X-BeenThere: sip@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. 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 rserpool-admin@ietf.org Tue Jul 1 15:29:37 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 PAA13541 for ; Tue, 1 Jul 2003 15:29:37 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19XQn5-0003T7-2z; Tue, 01 Jul 2003 15:27:47 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19XQlC-0003Q5-7V for rserpool@optimus.ietf.org; Tue, 01 Jul 2003 15:25:50 -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 NAA07961 for ; Tue, 1 Jul 2003 13:44:27 -0400 (EDT) From: Maureen.Stillman@nokia.com Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19XPB7-0006aV-00 for rserpool@ietf.org; Tue, 01 Jul 2003 13:44:29 -0400 Received: from mgw-x4.nokia.com ([131.228.20.27]) by ietf-mx with esmtp (Exim 4.12) id 19XPB6-0006aS-00 for rserpool@ietf.org; Tue, 01 Jul 2003 13:44:28 -0400 Received: from esvir03nok.nokia.com (esvir03nokt.ntc.nokia.com [172.21.143.35]) by mgw-x4.nokia.com (Switch-2.2.6/Switch-2.2.6) with ESMTP id h61HiR923278 for ; Tue, 1 Jul 2003 20:44:27 +0300 (EET DST) Received: from esebh004.NOE.Nokia.com (unverified) by esvir03nok.nokia.com (Content Technologies SMTPRS 4.2.5) with ESMTP id for ; Tue, 1 Jul 2003 20:44:21 +0300 Received: from daebh002.NOE.Nokia.com ([172.18.242.232]) by esebh004.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139); Tue, 1 Jul 2003 20:44:18 +0300 Received: from daebe007.NOE.Nokia.com ([172.18.242.211]) by daebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139); Tue, 1 Jul 2003 12:44:15 -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, 1 Jul 2003 12:44:14 -0500 Message-ID: <57A26D272F67A743952F6B4371B8F811E68186@daebe007.americas.nokia.com> Thread-Topic: Draft Agenda for IETF #57 Thread-Index: AcM/+GNLfCHGmKZhTruS3ZDmmA6uwQ== To: X-OriginalArrivalTime: 01 Jul 2003 17:44:15.0383 (UTC) FILETIME=[63B63270:01C33FF8] Content-Transfer-Encoding: quoted-printable Subject: [Rserpool] Draft Agenda for IETF #57 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 draft agenda for IETF #57. Please send comments. Reliable Server Pooling WG (rserpool) Monday, July 14, 2003 9AM to 11:30 =3D=3D=3D=3D=3D=3D=3D=3D=3D=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 comparison document, 10 min. http://www.ietf.org/internet-drafts/draft-ietf-rserpool-comp-06.txt John Loughney Rserpool architecture document, 15 min. http://www.ietf.org/internet-drafts/draft-ietf-rserpool-arch-05.txt=20 Michael Tuexen Rserpool services, 10 min. http://www.ietf.org/internet-drafts/draft-conrad-rserpool-service-02.txt Peter Lei TCP mapping, 10 min. http://www.ietf.org/internet-drafts/draft-conrad-rserpool-tcpmapping-00.t= xt Peter Lei 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-06.txt http://www.ietf.org/internet-drafts/draft-ietf-rserpool-enrp-07.txt Michael Tuexen, 20 min. Security http://www.ietf.org/internet-drafts/draft-ietf-rserpool-threats-00.txt Maureen Stillman, 10 min. Applicability Statement http://www.ietf.org/internet-drafts/draft-coene-rserpool-applic-01.txt Lode Coene, 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 Tue Jul 1 15:30:07 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 PAA13584 for ; Tue, 1 Jul 2003 15:30:07 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19XQoO-0003VN-Qw for rserpool-archive@odin.ietf.org; Tue, 01 Jul 2003 15:29:29 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h61JSwoE013443 for rserpool-archive@odin.ietf.org; Tue, 1 Jul 2003 15:28:58 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19XQn5-0003T7-2z; Tue, 01 Jul 2003 15:27:47 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19XQlC-0003Q5-7V for rserpool@optimus.ietf.org; Tue, 01 Jul 2003 15:25:50 -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 NAA07961 for ; Tue, 1 Jul 2003 13:44:27 -0400 (EDT) From: Maureen.Stillman@nokia.com Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19XPB7-0006aV-00 for rserpool@ietf.org; Tue, 01 Jul 2003 13:44:29 -0400 Received: from mgw-x4.nokia.com ([131.228.20.27]) by ietf-mx with esmtp (Exim 4.12) id 19XPB6-0006aS-00 for rserpool@ietf.org; Tue, 01 Jul 2003 13:44:28 -0400 Received: from esvir03nok.nokia.com (esvir03nokt.ntc.nokia.com [172.21.143.35]) by mgw-x4.nokia.com (Switch-2.2.6/Switch-2.2.6) with ESMTP id h61HiR923278 for ; Tue, 1 Jul 2003 20:44:27 +0300 (EET DST) Received: from esebh004.NOE.Nokia.com (unverified) by esvir03nok.nokia.com (Content Technologies SMTPRS 4.2.5) with ESMTP id for ; Tue, 1 Jul 2003 20:44:21 +0300 Received: from daebh002.NOE.Nokia.com ([172.18.242.232]) by esebh004.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139); Tue, 1 Jul 2003 20:44:18 +0300 Received: from daebe007.NOE.Nokia.com ([172.18.242.211]) by daebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139); Tue, 1 Jul 2003 12:44:15 -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, 1 Jul 2003 12:44:14 -0500 Message-ID: <57A26D272F67A743952F6B4371B8F811E68186@daebe007.americas.nokia.com> Thread-Topic: Draft Agenda for IETF #57 Thread-Index: AcM/+GNLfCHGmKZhTruS3ZDmmA6uwQ== To: X-OriginalArrivalTime: 01 Jul 2003 17:44:15.0383 (UTC) FILETIME=[63B63270:01C33FF8] Content-Transfer-Encoding: quoted-printable Subject: [Rserpool] Draft Agenda for IETF #57 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 draft agenda for IETF #57. Please send comments. Reliable Server Pooling WG (rserpool) Monday, July 14, 2003 9AM to 11:30 =3D=3D=3D=3D=3D=3D=3D=3D=3D=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 comparison document, 10 min. http://www.ietf.org/internet-drafts/draft-ietf-rserpool-comp-06.txt John Loughney Rserpool architecture document, 15 min. http://www.ietf.org/internet-drafts/draft-ietf-rserpool-arch-05.txt=20 Michael Tuexen Rserpool services, 10 min. http://www.ietf.org/internet-drafts/draft-conrad-rserpool-service-02.txt Peter Lei TCP mapping, 10 min. http://www.ietf.org/internet-drafts/draft-conrad-rserpool-tcpmapping-00.t= xt Peter Lei 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-06.txt http://www.ietf.org/internet-drafts/draft-ietf-rserpool-enrp-07.txt Michael Tuexen, 20 min. Security http://www.ietf.org/internet-drafts/draft-ietf-rserpool-threats-00.txt Maureen Stillman, 10 min. Applicability Statement http://www.ietf.org/internet-drafts/draft-coene-rserpool-applic-01.txt Lode Coene, 10 min. Closing Remarks Lyndon Ong, Maureen Stillman _______________________________________________ rserpool mailing list rserpool@ietf.org https://www1.ietf.org/mailman/listinfo/rserpool From mailman-admin@ietf.org Thu Jul 3 18:48:44 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 SAA16717 for ; Thu, 3 Jul 2003 18:48:44 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19YCiK-00042E-F0 for rserpool-archive@lists.ietf.org; Thu, 03 Jul 2003 18:38:04 -0400 Date: Thu, 03 Jul 2003 18:38:04 -0400 Message-ID: <20030703223804.4508.40368.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 There was an error in the last monthly reminder, in that the NOTE WELL statement (below) was not included. Therefore, the reminder is being sent out again. 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 rserpool-admin@ietf.org Mon Jul 7 17:04:28 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 RAA15435 for ; Mon, 7 Jul 2003 17:04:28 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19Zd9V-0005by-Hr; Mon, 07 Jul 2003 17: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 19XoIC-0002td-LH for rserpool@optimus.ietf.org; Wed, 02 Jul 2003 16:33:28 -0400 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA13029; Wed, 2 Jul 2003 16:33:23 -0400 (EDT) Message-Id: <200307022033.QAA13029@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: Wed, 02 Jul 2003 16:33:23 -0400 Subject: [Rserpool] I-D ACTION:draft-ietf-rserpool-comp-06.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-06.txt Pages : 22 Date : 2003-7-2 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-06.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-06.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-06.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-7-2161805.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-rserpool-comp-06.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-rserpool-comp-06.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2003-7-2161805.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 Jul 7 17:50:07 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 RAA15436 for ; Mon, 7 Jul 2003 17:04:28 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19Zd9V-0005bn-Bc; Mon, 07 Jul 2003 17: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 19XfIA-0002us-FF for rserpool@optimus.ietf.org; Wed, 02 Jul 2003 06:56:50 -0400 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA03040; Wed, 2 Jul 2003 06:56:47 -0400 (EDT) Message-Id: <200307021056.GAA03040@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: Wed, 02 Jul 2003 06:56:46 -0400 Subject: [Rserpool] I-D ACTION:draft-ietf-rserpool-arch-06.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-06.txt Pages : 22 Date : 2003-7-1 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-06.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-06.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-06.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-7-1134859.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-rserpool-arch-06.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-rserpool-arch-06.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2003-7-1134859.I-D@ietf.org> --OtherAccess-- --NextPart-- _______________________________________________ rserpool mailing list rserpool@ietf.org https://www1.ietf.org/mailman/listinfo/rserpool From exim@www1.ietf.org Mon Jul 7 17:50:08 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 RAA15438 for ; Mon, 7 Jul 2003 17:04:28 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19Zd9V-0005cK-LP for rserpool-archive@odin.ietf.org; Mon, 07 Jul 2003 17:04:01 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h67L41dx021577 for rserpool-archive@odin.ietf.org; Mon, 7 Jul 2003 17:04:01 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19Zd9V-0005bn-Bc; Mon, 07 Jul 2003 17: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 19XfIA-0002us-FF for rserpool@optimus.ietf.org; Wed, 02 Jul 2003 06:56:50 -0400 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA03040; Wed, 2 Jul 2003 06:56:47 -0400 (EDT) Message-Id: <200307021056.GAA03040@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: Wed, 02 Jul 2003 06:56:46 -0400 Subject: [Rserpool] I-D ACTION:draft-ietf-rserpool-arch-06.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-06.txt Pages : 22 Date : 2003-7-1 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-06.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-06.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-06.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-7-1134859.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-rserpool-arch-06.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-rserpool-arch-06.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2003-7-1134859.I-D@ietf.org> --OtherAccess-- --NextPart-- _______________________________________________ rserpool mailing list rserpool@ietf.org https://www1.ietf.org/mailman/listinfo/rserpool From exim@www1.ietf.org Mon Jul 7 17:50:08 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 RAA15437 for ; Mon, 7 Jul 2003 17:04:28 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19Zd9V-0005cH-LE for rserpool-archive@odin.ietf.org; Mon, 07 Jul 2003 17:04:01 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h67L41v5021581 for rserpool-archive@odin.ietf.org; Mon, 7 Jul 2003 17:04:01 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19Zd9V-0005by-Hr; Mon, 07 Jul 2003 17: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 19XoIC-0002td-LH for rserpool@optimus.ietf.org; Wed, 02 Jul 2003 16:33:28 -0400 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA13029; Wed, 2 Jul 2003 16:33:23 -0400 (EDT) Message-Id: <200307022033.QAA13029@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: Wed, 02 Jul 2003 16:33:23 -0400 Subject: [Rserpool] I-D ACTION:draft-ietf-rserpool-comp-06.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-06.txt Pages : 22 Date : 2003-7-2 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-06.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-06.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-06.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-7-2161805.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-rserpool-comp-06.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-rserpool-comp-06.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2003-7-2161805.I-D@ietf.org> --OtherAccess-- --NextPart-- _______________________________________________ rserpool mailing list rserpool@ietf.org https://www1.ietf.org/mailman/listinfo/rserpool From rserpool-admin@ietf.org Tue Jul 8 13:42:30 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 NAA01583 for ; Tue, 8 Jul 2003 13:42:30 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ZwTZ-0008Hm-Ko; Tue, 08 Jul 2003 13:42:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ZwSg-0008GD-8S for rserpool@optimus.ietf.org; Tue, 08 Jul 2003 13:41: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 NAA01542 for ; Tue, 8 Jul 2003 13:41:03 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19ZwSe-0003oV-00 for rserpool@ietf.org; Tue, 08 Jul 2003 13:41:04 -0400 Received: from motgate5.mot.com ([144.189.100.105]) by ietf-mx with esmtp (Exim 4.12) id 19ZwSd-0003oS-00 for rserpool@ietf.org; Tue, 08 Jul 2003 13:41:03 -0400 Received: from il06exr01.mot.com (il06exr01.mot.com [129.188.137.131]) by motgate5.mot.com (Motorola/Motgate5) with ESMTP id h68Hf1UY009730 for ; Tue, 8 Jul 2003 10:41:02 -0700 (MST) Received: from il02exm02.corp.mot.com (il02exm02.corp.mot.com [10.0.100.55]) by il06exr01.mot.com (Motorola/il06exr01) with ESMTP id h68GeY7q022732 for ; Tue, 8 Jul 2003 11:40:34 -0500 Received: by il02exm02.corp.mot.com with Internet Mail Service (5.5.2657.2) id ; Tue, 8 Jul 2003 12:41:01 -0500 Message-ID: <4D87884B6A6D4E438A8592BCC9C85DCA0A2C36FE@il02exm06.corp.mot.com> From: Silverton Aron-C1710C To: "'rserpool@ietf.org'" Cc: Xie Qiaobing-QXIE1 Date: Tue, 8 Jul 2003 12:40:58 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.2) Content-Type: text/plain Subject: [Rserpool] DHCP option for RSerPool 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've been thinking about a DHCP option that could be used to provide ENRP server addresses to a client which may be a PE or PU. This could be very useful in some deployments of RSerPool. Sub-options could also be created, if necessary, to provide other RSerPool related information to a client on boot. Please let me know your thoughts on this. If others think that it is a good idea, then I'll get started on and I-D for the option per BCP 43/RFC 2939. Aron Aron J. Silverton Senior Staff Research Engineer Motorola Labs, Networks and Infrastructure Research Motorola, Inc. _______________________________________________ rserpool mailing list rserpool@ietf.org https://www1.ietf.org/mailman/listinfo/rserpool From exim@www1.ietf.org Tue Jul 8 13:42:31 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 NAA01586 for ; Tue, 8 Jul 2003 13:42:31 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ZwTb-0008IS-5z for rserpool-archive@odin.ietf.org; Tue, 08 Jul 2003 13:42:03 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h68Hg3vX031878 for rserpool-archive@odin.ietf.org; Tue, 8 Jul 2003 13:42:03 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ZwTZ-0008Hm-Ko; Tue, 08 Jul 2003 13:42:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ZwSg-0008GD-8S for rserpool@optimus.ietf.org; Tue, 08 Jul 2003 13:41: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 NAA01542 for ; Tue, 8 Jul 2003 13:41:03 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19ZwSe-0003oV-00 for rserpool@ietf.org; Tue, 08 Jul 2003 13:41:04 -0400 Received: from motgate5.mot.com ([144.189.100.105]) by ietf-mx with esmtp (Exim 4.12) id 19ZwSd-0003oS-00 for rserpool@ietf.org; Tue, 08 Jul 2003 13:41:03 -0400 Received: from il06exr01.mot.com (il06exr01.mot.com [129.188.137.131]) by motgate5.mot.com (Motorola/Motgate5) with ESMTP id h68Hf1UY009730 for ; Tue, 8 Jul 2003 10:41:02 -0700 (MST) Received: from il02exm02.corp.mot.com (il02exm02.corp.mot.com [10.0.100.55]) by il06exr01.mot.com (Motorola/il06exr01) with ESMTP id h68GeY7q022732 for ; Tue, 8 Jul 2003 11:40:34 -0500 Received: by il02exm02.corp.mot.com with Internet Mail Service (5.5.2657.2) id ; Tue, 8 Jul 2003 12:41:01 -0500 Message-ID: <4D87884B6A6D4E438A8592BCC9C85DCA0A2C36FE@il02exm06.corp.mot.com> From: Silverton Aron-C1710C To: "'rserpool@ietf.org'" Cc: Xie Qiaobing-QXIE1 Date: Tue, 8 Jul 2003 12:40:58 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.2) Content-Type: text/plain Subject: [Rserpool] DHCP option for RSerPool 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've been thinking about a DHCP option that could be used to provide ENRP server addresses to a client which may be a PE or PU. This could be very useful in some deployments of RSerPool. Sub-options could also be created, if necessary, to provide other RSerPool related information to a client on boot. Please let me know your thoughts on this. If others think that it is a good idea, then I'll get started on and I-D for the option per BCP 43/RFC 2939. Aron Aron J. Silverton Senior Staff Research Engineer Motorola Labs, Networks and Infrastructure Research Motorola, Inc. _______________________________________________ rserpool mailing list rserpool@ietf.org https://www1.ietf.org/mailman/listinfo/rserpool From rserpool-admin@ietf.org Tue Jul 8 16:01:30 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 QAA07813 for ; Tue, 8 Jul 2003 16:01:30 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19Zye5-0001ah-JM; Tue, 08 Jul 2003 16:01:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19Zydx-0001a0-Vr for rserpool@optimus.ietf.org; Tue, 08 Jul 2003 16:00:53 -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 QAA07791 for ; Tue, 8 Jul 2003 16:00:51 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Zydw-0005eg-00 for rserpool@ietf.org; Tue, 08 Jul 2003 16:00:52 -0400 Received: from motgate5.mot.com ([144.189.100.105]) by ietf-mx with esmtp (Exim 4.12) id 19Zydu-0005ec-00 for rserpool@ietf.org; Tue, 08 Jul 2003 16:00:51 -0400 Received: from az33exr01.mot.com (az33exr01.mot.com [10.64.251.231]) by motgate5.mot.com (Motorola/Motgate5) with ESMTP id h68K0mUY004923 for ; Tue, 8 Jul 2003 13:00:48 -0700 (MST) Received: from il27exb01.cig.mot.com (il27exb01.cig.mot.com [136.182.15.100]) by az33exr01.mot.com (Motorola/az33exr01) with ESMTP id h68K0kR2023891 for ; Tue, 8 Jul 2003 15:00:46 -0500 Received: from motorola.com (d1421-0a1070d5.cig.mot.com [10.16.112.213]) by il27exb01.cig.mot.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2657.2) id N9T7F0M2; Tue, 8 Jul 2003 15:00:45 -0500 Message-ID: <3F0B2394.25FBBB53@motorola.com> Date: Tue, 08 Jul 2003 15:03:32 -0500 From: Qiaobing Xie X-Mailer: Mozilla 4.8 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Silverton Aron-C1710C CC: rserpool@ietf.org Subject: Re: [Rserpool] DHCP option for RSerPool References: <4D87884B6A6D4E438A8592BCC9C85DCA0A2C36FE@il02exm06.corp.mot.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit 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, Aron, I think this is a good idea. One thing comes to my mind is that we may need to take into consideration of the dynamic scalability of the ENRP server cloud, i.e., ENRP servers will likely be more dynamic than the DNS servers, for example. I am not an expert on DHCP and have little idea on how currently the DHCP deals with any changes of the DNS server. Another interesting issue is how to map the "host" concept of current DHCP to a PU or PE. regards, -Qiaobing Silverton Aron-C1710C wrote: > > Hello all, > > I've been thinking about a DHCP option that could be used to provide ENRP > server addresses to a client which may be a PE or PU. This could be very > useful in some deployments of RSerPool. Sub-options could also be created, > if necessary, to provide other RSerPool related information to a client on > boot. > > Please let me know your thoughts on this. If others think that it is a good > idea, then I'll get started on and I-D for the option per BCP 43/RFC 2939. > > Aron > > Aron J. Silverton > Senior Staff Research Engineer > Motorola Labs, Networks and Infrastructure Research > Motorola, Inc. > > _______________________________________________ > 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 Jul 8 16:01:31 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 QAA07828 for ; Tue, 8 Jul 2003 16:01:31 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19Zye7-0001bD-AT for rserpool-archive@odin.ietf.org; Tue, 08 Jul 2003 16:01:04 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h68K13pp006133 for rserpool-archive@odin.ietf.org; Tue, 8 Jul 2003 16:01:03 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19Zye5-0001ah-JM; Tue, 08 Jul 2003 16:01:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19Zydx-0001a0-Vr for rserpool@optimus.ietf.org; Tue, 08 Jul 2003 16:00:53 -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 QAA07791 for ; Tue, 8 Jul 2003 16:00:51 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Zydw-0005eg-00 for rserpool@ietf.org; Tue, 08 Jul 2003 16:00:52 -0400 Received: from motgate5.mot.com ([144.189.100.105]) by ietf-mx with esmtp (Exim 4.12) id 19Zydu-0005ec-00 for rserpool@ietf.org; Tue, 08 Jul 2003 16:00:51 -0400 Received: from az33exr01.mot.com (az33exr01.mot.com [10.64.251.231]) by motgate5.mot.com (Motorola/Motgate5) with ESMTP id h68K0mUY004923 for ; Tue, 8 Jul 2003 13:00:48 -0700 (MST) Received: from il27exb01.cig.mot.com (il27exb01.cig.mot.com [136.182.15.100]) by az33exr01.mot.com (Motorola/az33exr01) with ESMTP id h68K0kR2023891 for ; Tue, 8 Jul 2003 15:00:46 -0500 Received: from motorola.com (d1421-0a1070d5.cig.mot.com [10.16.112.213]) by il27exb01.cig.mot.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2657.2) id N9T7F0M2; Tue, 8 Jul 2003 15:00:45 -0500 Message-ID: <3F0B2394.25FBBB53@motorola.com> Date: Tue, 08 Jul 2003 15:03:32 -0500 From: Qiaobing Xie X-Mailer: Mozilla 4.8 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Silverton Aron-C1710C CC: rserpool@ietf.org Subject: Re: [Rserpool] DHCP option for RSerPool References: <4D87884B6A6D4E438A8592BCC9C85DCA0A2C36FE@il02exm06.corp.mot.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit 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, Aron, I think this is a good idea. One thing comes to my mind is that we may need to take into consideration of the dynamic scalability of the ENRP server cloud, i.e., ENRP servers will likely be more dynamic than the DNS servers, for example. I am not an expert on DHCP and have little idea on how currently the DHCP deals with any changes of the DNS server. Another interesting issue is how to map the "host" concept of current DHCP to a PU or PE. regards, -Qiaobing Silverton Aron-C1710C wrote: > > Hello all, > > I've been thinking about a DHCP option that could be used to provide ENRP > server addresses to a client which may be a PE or PU. This could be very > useful in some deployments of RSerPool. Sub-options could also be created, > if necessary, to provide other RSerPool related information to a client on > boot. > > Please let me know your thoughts on this. If others think that it is a good > idea, then I'll get started on and I-D for the option per BCP 43/RFC 2939. > > Aron > > Aron J. Silverton > Senior Staff Research Engineer > Motorola Labs, Networks and Infrastructure Research > Motorola, Inc. > > _______________________________________________ > 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 Jul 8 16:14:28 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 QAA08697 for ; Tue, 8 Jul 2003 16:14:28 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19Zyqf-0002ws-0o; Tue, 08 Jul 2003 16:14:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19Zyq1-0002vd-1B for rserpool@optimus.ietf.org; Tue, 08 Jul 2003 16:13:21 -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 QAA08633 for ; Tue, 8 Jul 2003 16:13:18 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Zypz-0005y5-00 for rserpool@ietf.org; Tue, 08 Jul 2003 16:13:19 -0400 Received: from motgate.mot.com ([129.188.136.100]) by ietf-mx with esmtp (Exim 4.12) id 19Zypy-0005y0-00 for rserpool@ietf.org; Tue, 08 Jul 2003 16:13:18 -0400 Received: from az33exr01.mot.com (az33exr01.mot.com [10.64.251.231]) by motgate.mot.com (Motorola/Motgate) with ESMTP id h68KDHKf016458 for ; Tue, 8 Jul 2003 13:13:17 -0700 (MST) Received: from il02exm02.corp.mot.com (il02exm02.corp.mot.com [10.0.100.55]) by az33exr01.mot.com (Motorola/az33exr01) with ESMTP id h68KDER2011267 for ; Tue, 8 Jul 2003 15:13:15 -0500 Received: by il02exm02.corp.mot.com with Internet Mail Service (5.5.2657.2) id ; Tue, 8 Jul 2003 15:13:14 -0500 Message-ID: <4D87884B6A6D4E438A8592BCC9C85DCA0A33E61E@il02exm06.corp.mot.com> From: Silverton Aron-C1710C To: Xie Qiaobing-QXIE1 Cc: "'rserpool@ietf.org'" Subject: RE: [Rserpool] DHCP option for RSerPool Date: Tue, 8 Jul 2003 15:13:13 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.2) Content-Type: text/plain 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: , Hi Qiaobing, With DHCP, the host is given a list of DNS servers typically at boot. If those servers should actually change or go away, the client does not get a dynamic update reflecting those changes. The client can get an update, if, for example, the DHCP server is administratively updated to reflect the change in DNS servers and the client lease expires. The lease expiration will cause a renewal attempt which would get fresh data. Generally not a good way of handling dynamic systems. For RSerPool, I see this as a way to bootstrap a client in a domain where things are already administratively configured. For example, a mobile node could cross a boundary requiring an IP change which is facilitated by a DHCP transaction. Along with that address, it would receive one or more ENRP server addresses, NTP servers, DNS servers, etc. Normal RSerPool methods would then be used to update the client as the ENRP cloud changes. It's a start and one possible way to tell a client about an ENRP server, but it won't solve all of the possible cases. It is definitely not a good method for handling very dynamic ENRP server clouds. Regards, Aron Qiaobing Xie wrote: > Hi, Aron, > > I think this is a good idea. One thing comes to my mind is that we > may need to take into consideration of the dynamic scalability of the > ENRP server cloud, i.e., ENRP servers will likely be more dynamic > than the DNS servers, for example. I am not an expert on DHCP and > have little idea on how currently the DHCP deals with any changes of > the DNS server. Another interesting issue is how to map the "host" > concept of current DHCP to a PU or PE. > > regards, > -Qiaobing > > Silverton Aron-C1710C wrote: >> >> Hello all, >> >> I've been thinking about a DHCP option that could be used to provide >> ENRP server addresses to a client which may be a PE or PU. This >> could be very useful in some deployments of RSerPool. Sub-options >> could also be created, if necessary, to provide other RSerPool >> related information to a client on boot. >> >> Please let me know your thoughts on this. If others think that it is >> a good idea, then I'll get started on and I-D for the option per BCP >> 43/RFC 2939. >> >> Aron >> >> Aron J. Silverton >> Senior Staff Research Engineer >> Motorola Labs, Networks and Infrastructure Research Motorola, Inc. >> >> _______________________________________________ >> 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 Jul 8 17:00:49 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 QAA08698 for ; Tue, 8 Jul 2003 16:14:28 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19Zyqf-0002xJ-9Q for rserpool-archive@odin.ietf.org; Tue, 08 Jul 2003 16:14:01 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h68KE19q011354 for rserpool-archive@odin.ietf.org; Tue, 8 Jul 2003 16:14:01 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19Zyqf-0002ws-0o; Tue, 08 Jul 2003 16:14:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19Zyq1-0002vd-1B for rserpool@optimus.ietf.org; Tue, 08 Jul 2003 16:13:21 -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 QAA08633 for ; Tue, 8 Jul 2003 16:13:18 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Zypz-0005y5-00 for rserpool@ietf.org; Tue, 08 Jul 2003 16:13:19 -0400 Received: from motgate.mot.com ([129.188.136.100]) by ietf-mx with esmtp (Exim 4.12) id 19Zypy-0005y0-00 for rserpool@ietf.org; Tue, 08 Jul 2003 16:13:18 -0400 Received: from az33exr01.mot.com (az33exr01.mot.com [10.64.251.231]) by motgate.mot.com (Motorola/Motgate) with ESMTP id h68KDHKf016458 for ; Tue, 8 Jul 2003 13:13:17 -0700 (MST) Received: from il02exm02.corp.mot.com (il02exm02.corp.mot.com [10.0.100.55]) by az33exr01.mot.com (Motorola/az33exr01) with ESMTP id h68KDER2011267 for ; Tue, 8 Jul 2003 15:13:15 -0500 Received: by il02exm02.corp.mot.com with Internet Mail Service (5.5.2657.2) id ; Tue, 8 Jul 2003 15:13:14 -0500 Message-ID: <4D87884B6A6D4E438A8592BCC9C85DCA0A33E61E@il02exm06.corp.mot.com> From: Silverton Aron-C1710C To: Xie Qiaobing-QXIE1 Cc: "'rserpool@ietf.org'" Subject: RE: [Rserpool] DHCP option for RSerPool Date: Tue, 8 Jul 2003 15:13:13 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.2) Content-Type: text/plain 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: , Hi Qiaobing, With DHCP, the host is given a list of DNS servers typically at boot. If those servers should actually change or go away, the client does not get a dynamic update reflecting those changes. The client can get an update, if, for example, the DHCP server is administratively updated to reflect the change in DNS servers and the client lease expires. The lease expiration will cause a renewal attempt which would get fresh data. Generally not a good way of handling dynamic systems. For RSerPool, I see this as a way to bootstrap a client in a domain where things are already administratively configured. For example, a mobile node could cross a boundary requiring an IP change which is facilitated by a DHCP transaction. Along with that address, it would receive one or more ENRP server addresses, NTP servers, DNS servers, etc. Normal RSerPool methods would then be used to update the client as the ENRP cloud changes. It's a start and one possible way to tell a client about an ENRP server, but it won't solve all of the possible cases. It is definitely not a good method for handling very dynamic ENRP server clouds. Regards, Aron Qiaobing Xie wrote: > Hi, Aron, > > I think this is a good idea. One thing comes to my mind is that we > may need to take into consideration of the dynamic scalability of the > ENRP server cloud, i.e., ENRP servers will likely be more dynamic > than the DNS servers, for example. I am not an expert on DHCP and > have little idea on how currently the DHCP deals with any changes of > the DNS server. Another interesting issue is how to map the "host" > concept of current DHCP to a PU or PE. > > regards, > -Qiaobing > > Silverton Aron-C1710C wrote: >> >> Hello all, >> >> I've been thinking about a DHCP option that could be used to provide >> ENRP server addresses to a client which may be a PE or PU. This >> could be very useful in some deployments of RSerPool. Sub-options >> could also be created, if necessary, to provide other RSerPool >> related information to a client on boot. >> >> Please let me know your thoughts on this. If others think that it is >> a good idea, then I'll get started on and I-D for the option per BCP >> 43/RFC 2939. >> >> Aron >> >> Aron J. Silverton >> Senior Staff Research Engineer >> Motorola Labs, Networks and Infrastructure Research Motorola, Inc. >> >> _______________________________________________ >> 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 Wed Jul 9 14:48:31 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 OAA13937 for ; Wed, 9 Jul 2003 14:48:31 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aJz2-0002Z8-Et for rserpool-archive@odin.ietf.org; Wed, 09 Jul 2003 14:48:04 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h69Im48T009858 for rserpool-archive@odin.ietf.org; Wed, 9 Jul 2003 14:48:04 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aJyy-0002Y7-9p; Wed, 09 Jul 2003 14:48:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aJyg-0002XV-4B for rserpool@optimus.ietf.org; Wed, 09 Jul 2003 14:47:42 -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 OAA13830 for ; Wed, 9 Jul 2003 14:47:38 -0400 (EDT) From: Maureen.Stillman@nokia.com Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19aJyd-0001lP-00 for rserpool@ietf.org; Wed, 09 Jul 2003 14:47:39 -0400 Received: from [63.78.179.217] (helo=mgw-dax2.ext.nokia.com) by ietf-mx with esmtp (Exim 4.12) id 19aJyc-0001lM-00 for rserpool@ietf.org; Wed, 09 Jul 2003 14:47:38 -0400 Received: from davir02nok.americas.nokia.com (davir02nok.americas.nokia.com [172.18.242.85]) by mgw-dax2.ext.nokia.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id h69IlZG04082 for ; Wed, 9 Jul 2003 13:47:35 -0500 (CDT) Received: from daebh002.NOE.Nokia.com (unverified) by davir02nok.americas.nokia.com (Content Technologies SMTPRS 4.2.5) with ESMTP id for ; Wed, 9 Jul 2003 13:47:31 -0500 Received: from daebe007.NOE.Nokia.com ([172.18.242.211]) by daebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139); Wed, 9 Jul 2003 13:47:16 -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: Wed, 9 Jul 2003 13:47:15 -0500 Message-ID: <57A26D272F67A743952F6B4371B8F81101222E54@daebe007.americas.nokia.com> Thread-Topic: Agenda for Rserpool IETF #57 now on the website Thread-Index: AcNGSoP98zrmObm1TiWR/fM9MUhdqw== To: X-OriginalArrivalTime: 09 Jul 2003 18:47:16.0212 (UTC) FILETIME=[8490EB40:01C3464A] Content-Transfer-Encoding: quoted-printable Subject: [Rserpool] Agenda for Rserpool IETF #57 now on the website 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 Reliable Server Pooling WG (rserpool) Monday, July 14 at 09-1130 =3D=3D=3D=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 comparison document, 10 min. http://www.ietf.org/internet-drafts/draft-ietf-rserpool-comp-06.txt John Loughney Rserpool architecture document, 15 min. http://www.ietf.org/internet-drafts/draft-ietf-rserpool-arch-06.txt Michael Tuexen Rserpool services, 10 min. http://www.ietf.org/internet-drafts/draft-conrad-rserpool-service-03.txt Peter Lei TCP mapping, 10 min. http://www.ietf.org/internet-drafts/draft-ietf-rserpool-tcpmapping-00.txt= Peter Lei 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 Michael Tuexen, 20 min. Security http://www.ietf.org/internet-drafts/draft-ietf-rserpool-threats-00.txt Maureen Stillman, 10 min. Applicability Statement http://www.ietf.org/internet-drafts/draft-ietf-rserpool-applic-00.txt Lode Coene, 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 Wed Jul 9 15:05:29 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 PAA15324 for ; Wed, 9 Jul 2003 15:05:29 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aKFS-0004O8-BD; Wed, 09 Jul 2003 15:05:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aKEu-0004N1-Nh for rserpool@optimus.ietf.org; Wed, 09 Jul 2003 15:04:28 -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 PAA15201 for ; Wed, 9 Jul 2003 15:04:24 -0400 (EDT) From: Maureen.Stillman@nokia.com Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19aKEr-00025X-00 for rserpool@ietf.org; Wed, 09 Jul 2003 15:04:25 -0400 Received: from [63.78.179.217] (helo=mgw-dax2.ext.nokia.com) by ietf-mx with esmtp (Exim 4.12) id 19aKEq-00025U-00 for rserpool@ietf.org; Wed, 09 Jul 2003 15:04:24 -0400 Received: from davir02nok.americas.nokia.com (davir02nok.americas.nokia.com [172.18.242.85]) by mgw-dax2.ext.nokia.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id h69J4NG08040 for ; Wed, 9 Jul 2003 14:04:23 -0500 (CDT) Received: from daebh002.NOE.Nokia.com (unverified) by davir02nok.americas.nokia.com (Content Technologies SMTPRS 4.2.5) with ESMTP id ; Wed, 9 Jul 2003 14:04:23 -0500 Received: from daebe007.NOE.Nokia.com ([172.18.242.211]) by daebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139); Wed, 9 Jul 2003 14:04:22 -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 Subject: RE: [Rserpool] draft-ietf-rserpool-arch-06.txt Date: Wed, 9 Jul 2003 14:04:22 -0500 Message-ID: <57A26D272F67A743952F6B4371B8F81101222E56@daebe007.americas.nokia.com> Thread-Topic: [Rserpool] draft-ietf-rserpool-arch-06.txt Thread-Index: AcM+XGdmlIffb/mMRAujyHCzlCTCPQH7/raA To: , Cc: X-OriginalArrivalTime: 09 Jul 2003 19:04:22.0803 (UTC) FILETIME=[E8764630:01C3464C] 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 Most likely time is shortly after the Rserpool WG meeting in Vienna. = Minutes of IETF #57 meeting will be posted to the list.=20 Thanks.=20 -- maureen -----Original Message----- From: ext Melinda Shore [mailto:mshore@cisco.com] Sent: Sunday, June 29, 2003 12:34 PM To: Michael Tuexen Cc: rserpool@ietf.org Subject: Re: [Rserpool] draft-ietf-rserpool-arch-06.txt=20 When is this expected to go into WG last call? Thanks, Melinda _______________________________________________ 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 Wed Jul 9 15:05:29 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 PAA15327 for ; Wed, 9 Jul 2003 15:05:29 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aKFS-0004Oe-ES for rserpool-archive@odin.ietf.org; Wed, 09 Jul 2003 15:05:02 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h69J52hh016879 for rserpool-archive@odin.ietf.org; Wed, 9 Jul 2003 15:05:02 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aKFS-0004O8-BD; Wed, 09 Jul 2003 15:05:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aKEu-0004N1-Nh for rserpool@optimus.ietf.org; Wed, 09 Jul 2003 15:04:28 -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 PAA15201 for ; Wed, 9 Jul 2003 15:04:24 -0400 (EDT) From: Maureen.Stillman@nokia.com Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19aKEr-00025X-00 for rserpool@ietf.org; Wed, 09 Jul 2003 15:04:25 -0400 Received: from [63.78.179.217] (helo=mgw-dax2.ext.nokia.com) by ietf-mx with esmtp (Exim 4.12) id 19aKEq-00025U-00 for rserpool@ietf.org; Wed, 09 Jul 2003 15:04:24 -0400 Received: from davir02nok.americas.nokia.com (davir02nok.americas.nokia.com [172.18.242.85]) by mgw-dax2.ext.nokia.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id h69J4NG08040 for ; Wed, 9 Jul 2003 14:04:23 -0500 (CDT) Received: from daebh002.NOE.Nokia.com (unverified) by davir02nok.americas.nokia.com (Content Technologies SMTPRS 4.2.5) with ESMTP id ; Wed, 9 Jul 2003 14:04:23 -0500 Received: from daebe007.NOE.Nokia.com ([172.18.242.211]) by daebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139); Wed, 9 Jul 2003 14:04:22 -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 Subject: RE: [Rserpool] draft-ietf-rserpool-arch-06.txt Date: Wed, 9 Jul 2003 14:04:22 -0500 Message-ID: <57A26D272F67A743952F6B4371B8F81101222E56@daebe007.americas.nokia.com> Thread-Topic: [Rserpool] draft-ietf-rserpool-arch-06.txt Thread-Index: AcM+XGdmlIffb/mMRAujyHCzlCTCPQH7/raA To: , Cc: X-OriginalArrivalTime: 09 Jul 2003 19:04:22.0803 (UTC) FILETIME=[E8764630:01C3464C] 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 Most likely time is shortly after the Rserpool WG meeting in Vienna. = Minutes of IETF #57 meeting will be posted to the list.=20 Thanks.=20 -- maureen -----Original Message----- From: ext Melinda Shore [mailto:mshore@cisco.com] Sent: Sunday, June 29, 2003 12:34 PM To: Michael Tuexen Cc: rserpool@ietf.org Subject: Re: [Rserpool] draft-ietf-rserpool-arch-06.txt=20 When is this expected to go into WG last call? Thanks, Melinda _______________________________________________ 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 Jul 9 15:35:58 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 OAA13934 for ; Wed, 9 Jul 2003 14:48:31 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aJyy-0002Y7-9p; Wed, 09 Jul 2003 14:48:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aJyg-0002XV-4B for rserpool@optimus.ietf.org; Wed, 09 Jul 2003 14:47:42 -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 OAA13830 for ; Wed, 9 Jul 2003 14:47:38 -0400 (EDT) From: Maureen.Stillman@nokia.com Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19aJyd-0001lP-00 for rserpool@ietf.org; Wed, 09 Jul 2003 14:47:39 -0400 Received: from [63.78.179.217] (helo=mgw-dax2.ext.nokia.com) by ietf-mx with esmtp (Exim 4.12) id 19aJyc-0001lM-00 for rserpool@ietf.org; Wed, 09 Jul 2003 14:47:38 -0400 Received: from davir02nok.americas.nokia.com (davir02nok.americas.nokia.com [172.18.242.85]) by mgw-dax2.ext.nokia.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id h69IlZG04082 for ; Wed, 9 Jul 2003 13:47:35 -0500 (CDT) Received: from daebh002.NOE.Nokia.com (unverified) by davir02nok.americas.nokia.com (Content Technologies SMTPRS 4.2.5) with ESMTP id for ; Wed, 9 Jul 2003 13:47:31 -0500 Received: from daebe007.NOE.Nokia.com ([172.18.242.211]) by daebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139); Wed, 9 Jul 2003 13:47:16 -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: Wed, 9 Jul 2003 13:47:15 -0500 Message-ID: <57A26D272F67A743952F6B4371B8F81101222E54@daebe007.americas.nokia.com> Thread-Topic: Agenda for Rserpool IETF #57 now on the website Thread-Index: AcNGSoP98zrmObm1TiWR/fM9MUhdqw== To: X-OriginalArrivalTime: 09 Jul 2003 18:47:16.0212 (UTC) FILETIME=[8490EB40:01C3464A] Content-Transfer-Encoding: quoted-printable Subject: [Rserpool] Agenda for Rserpool IETF #57 now on the website 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 Reliable Server Pooling WG (rserpool) Monday, July 14 at 09-1130 =3D=3D=3D=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 comparison document, 10 min. http://www.ietf.org/internet-drafts/draft-ietf-rserpool-comp-06.txt John Loughney Rserpool architecture document, 15 min. http://www.ietf.org/internet-drafts/draft-ietf-rserpool-arch-06.txt Michael Tuexen Rserpool services, 10 min. http://www.ietf.org/internet-drafts/draft-conrad-rserpool-service-03.txt Peter Lei TCP mapping, 10 min. http://www.ietf.org/internet-drafts/draft-ietf-rserpool-tcpmapping-00.txt= Peter Lei 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 Michael Tuexen, 20 min. Security http://www.ietf.org/internet-drafts/draft-ietf-rserpool-threats-00.txt Maureen Stillman, 10 min. Applicability Statement http://www.ietf.org/internet-drafts/draft-ietf-rserpool-applic-00.txt Lode Coene, 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 Thu Jul 17 09:36: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 JAA06017 for ; Thu, 17 Jul 2003 09:36:27 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19d8vQ-0001ae-V2; Thu, 17 Jul 2003 09:36:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19d8v7-0001a3-Ot for rserpool@optimus.ietf.org; Thu, 17 Jul 2003 09:35:41 -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 JAA06005 for ; Thu, 17 Jul 2003 09:35:37 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19d8v5-0006VX-00 for rserpool@ietf.org; Thu, 17 Jul 2003 09:35:40 -0400 Received: from thoth.sbs.de ([192.35.17.2]) by ietf-mx with esmtp (Exim 4.12) id 19d8uv-0006VT-00 for rserpool@ietf.org; Thu, 17 Jul 2003 09:35:29 -0400 Received: from mail3.siemens.de (mail3.siemens.de [139.25.208.14]) by thoth.sbs.de (8.11.7/8.11.7) with ESMTP id h6HDZNb14212 for ; Thu, 17 Jul 2003 15:35:23 +0200 (MEST) Received: from moody.mchh.siemens.de (moody.mchh.siemens.de [139.21.205.85]) by mail3.siemens.de (8.11.7/8.11.7) with ESMTP id h6HDZLl14130 for ; Thu, 17 Jul 2003 15:35:21 +0200 (MEST) Received: from mchh274e.demchh201e.icn.siemens.de (mchh274e.mchh.siemens.de [139.21.200.84]) by moody.mchh.siemens.de (8.9.3/8.9.1) with ESMTP id PAA19927 for ; Thu, 17 Jul 2003 15:35:21 +0200 (MET DST) Received: by mchh274e.mchh.siemens.de with Internet Mail Service (5.5.2656.59) id ; Thu, 17 Jul 2003 15:34:46 +0200 Message-ID: <47D438A0510BD611B9470002A58EDAE70126C38F@mchh2a6e.mchh.siemens.de> From: Chen Youye To: "'rserpool@ietf.org'" Date: Thu, 17 Jul 2003 15:34:43 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2656.59) Content-Type: text/plain Subject: [Rserpool] questions on load balancing 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, A freshman on RserPool has some questions: 1.Why do we need to include the "Registration Life" in the message "REGISTRATION" when PE registers itself to Home NS? The timer to count life time only runs at PE. I cannot find any corresponding timer or other actions to work with the PE's life time at NS. Whether this information is not necessary to Home NS? 2. What is the reason that PE must register itself again to Home NS according to the Registration Life time? Force PE to update its loading information? 3. As described in RFC draft, PE shall actively update its loading information to Home NS when it desires. How does the PU get this updated loading information? Only through NAME-RESOLUTION? Is there any possible to ask Home NS to actively inform the registered PUs so that to reach a more dynamic load balancing? 4. There are items named "Pool Element parameter" in the message "NAME_RESOLUTION_RESPONSE". Whether the "Pool Element parameter" is directly copied from the PE "REGISTRATION" message, which means Home NS cannot do any modification on that? Thank you ver much. Best regards, Youye Chen _______________________________________________ rserpool mailing list rserpool@ietf.org https://www1.ietf.org/mailman/listinfo/rserpool From exim@www1.ietf.org Thu Jul 17 09:36:28 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 JAA06021 for ; Thu, 17 Jul 2003 09:36:27 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19d8vR-0001bD-ML for rserpool-archive@odin.ietf.org; Thu, 17 Jul 2003 09:36:01 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6HDa16F006132 for rserpool-archive@odin.ietf.org; Thu, 17 Jul 2003 09:36:01 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19d8vQ-0001ae-V2; Thu, 17 Jul 2003 09:36:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19d8v7-0001a3-Ot for rserpool@optimus.ietf.org; Thu, 17 Jul 2003 09:35:41 -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 JAA06005 for ; Thu, 17 Jul 2003 09:35:37 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19d8v5-0006VX-00 for rserpool@ietf.org; Thu, 17 Jul 2003 09:35:40 -0400 Received: from thoth.sbs.de ([192.35.17.2]) by ietf-mx with esmtp (Exim 4.12) id 19d8uv-0006VT-00 for rserpool@ietf.org; Thu, 17 Jul 2003 09:35:29 -0400 Received: from mail3.siemens.de (mail3.siemens.de [139.25.208.14]) by thoth.sbs.de (8.11.7/8.11.7) with ESMTP id h6HDZNb14212 for ; Thu, 17 Jul 2003 15:35:23 +0200 (MEST) Received: from moody.mchh.siemens.de (moody.mchh.siemens.de [139.21.205.85]) by mail3.siemens.de (8.11.7/8.11.7) with ESMTP id h6HDZLl14130 for ; Thu, 17 Jul 2003 15:35:21 +0200 (MEST) Received: from mchh274e.demchh201e.icn.siemens.de (mchh274e.mchh.siemens.de [139.21.200.84]) by moody.mchh.siemens.de (8.9.3/8.9.1) with ESMTP id PAA19927 for ; Thu, 17 Jul 2003 15:35:21 +0200 (MET DST) Received: by mchh274e.mchh.siemens.de with Internet Mail Service (5.5.2656.59) id ; Thu, 17 Jul 2003 15:34:46 +0200 Message-ID: <47D438A0510BD611B9470002A58EDAE70126C38F@mchh2a6e.mchh.siemens.de> From: Chen Youye To: "'rserpool@ietf.org'" Date: Thu, 17 Jul 2003 15:34:43 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2656.59) Content-Type: text/plain Subject: [Rserpool] questions on load balancing 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, A freshman on RserPool has some questions: 1.Why do we need to include the "Registration Life" in the message "REGISTRATION" when PE registers itself to Home NS? The timer to count life time only runs at PE. I cannot find any corresponding timer or other actions to work with the PE's life time at NS. Whether this information is not necessary to Home NS? 2. What is the reason that PE must register itself again to Home NS according to the Registration Life time? Force PE to update its loading information? 3. As described in RFC draft, PE shall actively update its loading information to Home NS when it desires. How does the PU get this updated loading information? Only through NAME-RESOLUTION? Is there any possible to ask Home NS to actively inform the registered PUs so that to reach a more dynamic load balancing? 4. There are items named "Pool Element parameter" in the message "NAME_RESOLUTION_RESPONSE". Whether the "Pool Element parameter" is directly copied from the PE "REGISTRATION" message, which means Home NS cannot do any modification on that? Thank you ver much. Best regards, Youye Chen _______________________________________________ rserpool mailing list rserpool@ietf.org https://www1.ietf.org/mailman/listinfo/rserpool From rserpool-admin@ietf.org Thu Jul 17 09:58:26 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 JAA06710 for ; Thu, 17 Jul 2003 09:58: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 19d9Gi-0002a5-Eu; Thu, 17 Jul 2003 09: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 19d9Gc-0002Zr-Ty for rserpool@optimus.ietf.org; Thu, 17 Jul 2003 09:57:55 -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 JAA06689 for ; Thu, 17 Jul 2003 09:57:50 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19d9Ga-0006bl-00 for rserpool@ietf.org; Thu, 17 Jul 2003 09:57:52 -0400 Received: from mail-n.franken.de ([193.175.24.27] ident=postfix) by ietf-mx with esmtp (Exim 4.12) id 19d9GQ-0006bL-00 for rserpool@ietf.org; Thu, 17 Jul 2003 09:57:42 -0400 Received: from lurchi.franken.de (powerbook.ietf57.telekom.at [81.160.140.223]) by mail-n.franken.de (Postfix) with ESMTP id 4527E2464E; Thu, 17 Jul 2003 15:55:35 +0200 (CEST) Date: Thu, 17 Jul 2003 15:54:03 +0200 Subject: Re: [Rserpool] questions on load balancing Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v552) Cc: "'rserpool@ietf.org'" To: Chen Youye From: Michael Tuexen In-Reply-To: <47D438A0510BD611B9470002A58EDAE70126C38F@mchh2a6e.mchh.siemens.de> Message-Id: <2047955B-B85E-11D7-9136-0030654C1AB6@lurchi.franken.de> Content-Transfer-Encoding: 7bit X-Mailer: Apple Mail (2.552) 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 Youye, see my comments below. Best regards Michael On Thursday, Jul 17, 2003, at 15:34 Europe/Berlin, Chen Youye wrote: > Hello,all, > > A freshman on RserPool has some questions: > > 1.Why do we need to include the "Registration Life" in the message > "REGISTRATION" when PE registers itself to Home NS? The timer to count > life time only runs at PE. I cannot find any corresponding timer or > other actions to work with the PE's life time at NS. Whether this > information is not necessary to Home NS? > The NS will delete the entry after the some time. That is what the lifetime is for. The description of this procedure seems to me missing... > 2. What is the reason that PE must register itself again to Home NS > according to the Registration Life time? Force PE to update its > loading information? > We want to make sure that there is 'up-to-date' information in the namespace. > 3. As described in RFC draft, PE shall actively update its loading > information to Home NS when it desires. How does the PU get this > updated loading information? Only through NAME-RESOLUTION? Is there > any possible to ask Home NS to actively inform the registered PUs so > that to reach a more dynamic load balancing? Only through a name resolution. > > 4. There are items named "Pool Element parameter" in the message > "NAME_RESOLUTION_RESPONSE". Whether the "Pool Element parameter" is > directly copied from the PE "REGISTRATION" message, which means Home > NS cannot do any modification on that? > Why should that entry be modified? The PE says that it is using this transport address and the NS gives this information to PUs. > Thank you ver much. > > Best regards, > Youye Chen > > _______________________________________________ > 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 Thu Jul 17 09:58: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 JAA06725 for ; Thu, 17 Jul 2003 09:58:27 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19d9Gi-0002aO-I8 for rserpool-archive@odin.ietf.org; Thu, 17 Jul 2003 09:58:01 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6HDw0Qg009931 for rserpool-archive@odin.ietf.org; Thu, 17 Jul 2003 09:58:00 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19d9Gi-0002a5-Eu; Thu, 17 Jul 2003 09: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 19d9Gc-0002Zr-Ty for rserpool@optimus.ietf.org; Thu, 17 Jul 2003 09:57:55 -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 JAA06689 for ; Thu, 17 Jul 2003 09:57:50 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19d9Ga-0006bl-00 for rserpool@ietf.org; Thu, 17 Jul 2003 09:57:52 -0400 Received: from mail-n.franken.de ([193.175.24.27] ident=postfix) by ietf-mx with esmtp (Exim 4.12) id 19d9GQ-0006bL-00 for rserpool@ietf.org; Thu, 17 Jul 2003 09:57:42 -0400 Received: from lurchi.franken.de (powerbook.ietf57.telekom.at [81.160.140.223]) by mail-n.franken.de (Postfix) with ESMTP id 4527E2464E; Thu, 17 Jul 2003 15:55:35 +0200 (CEST) Date: Thu, 17 Jul 2003 15:54:03 +0200 Subject: Re: [Rserpool] questions on load balancing Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v552) Cc: "'rserpool@ietf.org'" To: Chen Youye From: Michael Tuexen In-Reply-To: <47D438A0510BD611B9470002A58EDAE70126C38F@mchh2a6e.mchh.siemens.de> Message-Id: <2047955B-B85E-11D7-9136-0030654C1AB6@lurchi.franken.de> Content-Transfer-Encoding: 7bit X-Mailer: Apple Mail (2.552) 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 Youye, see my comments below. Best regards Michael On Thursday, Jul 17, 2003, at 15:34 Europe/Berlin, Chen Youye wrote: > Hello,all, > > A freshman on RserPool has some questions: > > 1.Why do we need to include the "Registration Life" in the message > "REGISTRATION" when PE registers itself to Home NS? The timer to count > life time only runs at PE. I cannot find any corresponding timer or > other actions to work with the PE's life time at NS. Whether this > information is not necessary to Home NS? > The NS will delete the entry after the some time. That is what the lifetime is for. The description of this procedure seems to me missing... > 2. What is the reason that PE must register itself again to Home NS > according to the Registration Life time? Force PE to update its > loading information? > We want to make sure that there is 'up-to-date' information in the namespace. > 3. As described in RFC draft, PE shall actively update its loading > information to Home NS when it desires. How does the PU get this > updated loading information? Only through NAME-RESOLUTION? Is there > any possible to ask Home NS to actively inform the registered PUs so > that to reach a more dynamic load balancing? Only through a name resolution. > > 4. There are items named "Pool Element parameter" in the message > "NAME_RESOLUTION_RESPONSE". Whether the "Pool Element parameter" is > directly copied from the PE "REGISTRATION" message, which means Home > NS cannot do any modification on that? > Why should that entry be modified? The PE says that it is using this transport address and the NS gives this information to PUs. > Thank you ver much. > > Best regards, > Youye Chen > > _______________________________________________ > 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 Jul 17 11:42: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 LAA11915 for ; Thu, 17 Jul 2003 11:42:27 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19dAtM-00016y-Qe; Thu, 17 Jul 2003 11:42:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19dAsl-00016b-1n for rserpool@optimus.ietf.org; Thu, 17 Jul 2003 11:41:23 -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 LAA11887 for ; Thu, 17 Jul 2003 11:41:18 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19dAsj-0007Ip-00 for rserpool@ietf.org; Thu, 17 Jul 2003 11:41:21 -0400 Received: from david.siemens.de ([192.35.17.14]) by ietf-mx with esmtp (Exim 4.12) id 19dAsY-0007Il-00 for rserpool@ietf.org; Thu, 17 Jul 2003 11:41:10 -0400 Received: from mail3.siemens.de (mail3.siemens.de [139.25.208.14]) by david.siemens.de (8.11.7/8.11.7) with ESMTP id h6HFf2Q00336 for ; Thu, 17 Jul 2003 17:41:02 +0200 (MEST) Received: from moody.mchh.siemens.de (moody.mchh.siemens.de [139.21.205.85]) by mail3.siemens.de (8.11.7/8.11.7) with ESMTP id h6HFf2l13874 for ; Thu, 17 Jul 2003 17:41:02 +0200 (MEST) Received: from mchh253e.mchh.siemens.de (mchh253e.mchh.siemens.de [139.21.200.63]) by moody.mchh.siemens.de (8.9.3/8.9.1) with ESMTP id RAA10699 for ; Thu, 17 Jul 2003 17:41:01 +0200 (MET DST) Received: by mchh253e.mchh.siemens.de with Internet Mail Service (5.5.2653.19) id <3945KPGG>; Thu, 17 Jul 2003 17:40:26 +0200 Message-ID: <47D438A0510BD611B9470002A58EDAE70126C391@mchh2a6e.mchh.siemens.de> From: Chen Youye Cc: "''rserpool@ietf.org' '" Subject: RE: [Rserpool] questions on load balancing Date: Thu, 17 Jul 2003 17:40:22 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain 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, Michael, Thank you for your reply! From your description, only PE can modify the Policy value according to the loading situation, and PU knows the loading change only through name resolution. So, what is the difference between the two Pool Policies, Least Used and Least Used with Degradation? We assume local cache implemented at PU side. Since the degradation of Policy value only can be done at PE side, PU cannot get this information except of performing name resolution when the timer for local cache expires. However, with Least Used policy, PU also can know that with name resolution when the timer expires. What is the difference? Best regards, Youye Chen -----Original Message----- From: Michael Tuexen To: Chen Youye Cc: 'rserpool@ietf.org' Sent: 7/17/03 3:54 PM Subject: Re: [Rserpool] questions on load balancing Hi Youye, see my comments below. Best regards Michael On Thursday, Jul 17, 2003, at 15:34 Europe/Berlin, Chen Youye wrote: > Hello,all, > > A freshman on RserPool has some questions: > > 1.Why do we need to include the "Registration Life" in the message > "REGISTRATION" when PE registers itself to Home NS? The timer to count > life time only runs at PE. I cannot find any corresponding timer or > other actions to work with the PE's life time at NS. Whether this > information is not necessary to Home NS? > The NS will delete the entry after the some time. That is what the lifetime is for. The description of this procedure seems to me missing... > 2. What is the reason that PE must register itself again to Home NS > according to the Registration Life time? Force PE to update its > loading information? > We want to make sure that there is 'up-to-date' information in the namespace. > 3. As described in RFC draft, PE shall actively update its loading > information to Home NS when it desires. How does the PU get this > updated loading information? Only through NAME-RESOLUTION? Is there > any possible to ask Home NS to actively inform the registered PUs so > that to reach a more dynamic load balancing? Only through a name resolution. > > 4. There are items named "Pool Element parameter" in the message > "NAME_RESOLUTION_RESPONSE". Whether the "Pool Element parameter" is > directly copied from the PE "REGISTRATION" message, which means Home > NS cannot do any modification on that? > Why should that entry be modified? The PE says that it is using this transport address and the NS gives this information to PUs. > Thank you ver much. > > Best regards, > Youye Chen > > _______________________________________________ > 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 Thu Jul 17 12:32:15 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 LAA11917 for ; Thu, 17 Jul 2003 11:42:27 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19dAtN-00017H-4H for rserpool-archive@odin.ietf.org; Thu, 17 Jul 2003 11:42:01 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6HFg1bd004290 for rserpool-archive@odin.ietf.org; Thu, 17 Jul 2003 11:42:01 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19dAtM-00016y-Qe; Thu, 17 Jul 2003 11:42:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19dAsl-00016b-1n for rserpool@optimus.ietf.org; Thu, 17 Jul 2003 11:41:23 -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 LAA11887 for ; Thu, 17 Jul 2003 11:41:18 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19dAsj-0007Ip-00 for rserpool@ietf.org; Thu, 17 Jul 2003 11:41:21 -0400 Received: from david.siemens.de ([192.35.17.14]) by ietf-mx with esmtp (Exim 4.12) id 19dAsY-0007Il-00 for rserpool@ietf.org; Thu, 17 Jul 2003 11:41:10 -0400 Received: from mail3.siemens.de (mail3.siemens.de [139.25.208.14]) by david.siemens.de (8.11.7/8.11.7) with ESMTP id h6HFf2Q00336 for ; Thu, 17 Jul 2003 17:41:02 +0200 (MEST) Received: from moody.mchh.siemens.de (moody.mchh.siemens.de [139.21.205.85]) by mail3.siemens.de (8.11.7/8.11.7) with ESMTP id h6HFf2l13874 for ; Thu, 17 Jul 2003 17:41:02 +0200 (MEST) Received: from mchh253e.mchh.siemens.de (mchh253e.mchh.siemens.de [139.21.200.63]) by moody.mchh.siemens.de (8.9.3/8.9.1) with ESMTP id RAA10699 for ; Thu, 17 Jul 2003 17:41:01 +0200 (MET DST) Received: by mchh253e.mchh.siemens.de with Internet Mail Service (5.5.2653.19) id <3945KPGG>; Thu, 17 Jul 2003 17:40:26 +0200 Message-ID: <47D438A0510BD611B9470002A58EDAE70126C391@mchh2a6e.mchh.siemens.de> From: Chen Youye Cc: "''rserpool@ietf.org' '" Subject: RE: [Rserpool] questions on load balancing Date: Thu, 17 Jul 2003 17:40:22 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain 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, Michael, Thank you for your reply! From your description, only PE can modify the Policy value according to the loading situation, and PU knows the loading change only through name resolution. So, what is the difference between the two Pool Policies, Least Used and Least Used with Degradation? We assume local cache implemented at PU side. Since the degradation of Policy value only can be done at PE side, PU cannot get this information except of performing name resolution when the timer for local cache expires. However, with Least Used policy, PU also can know that with name resolution when the timer expires. What is the difference? Best regards, Youye Chen -----Original Message----- From: Michael Tuexen To: Chen Youye Cc: 'rserpool@ietf.org' Sent: 7/17/03 3:54 PM Subject: Re: [Rserpool] questions on load balancing Hi Youye, see my comments below. Best regards Michael On Thursday, Jul 17, 2003, at 15:34 Europe/Berlin, Chen Youye wrote: > Hello,all, > > A freshman on RserPool has some questions: > > 1.Why do we need to include the "Registration Life" in the message > "REGISTRATION" when PE registers itself to Home NS? The timer to count > life time only runs at PE. I cannot find any corresponding timer or > other actions to work with the PE's life time at NS. Whether this > information is not necessary to Home NS? > The NS will delete the entry after the some time. That is what the lifetime is for. The description of this procedure seems to me missing... > 2. What is the reason that PE must register itself again to Home NS > according to the Registration Life time? Force PE to update its > loading information? > We want to make sure that there is 'up-to-date' information in the namespace. > 3. As described in RFC draft, PE shall actively update its loading > information to Home NS when it desires. How does the PU get this > updated loading information? Only through NAME-RESOLUTION? Is there > any possible to ask Home NS to actively inform the registered PUs so > that to reach a more dynamic load balancing? Only through a name resolution. > > 4. There are items named "Pool Element parameter" in the message > "NAME_RESOLUTION_RESPONSE". Whether the "Pool Element parameter" is > directly copied from the PE "REGISTRATION" message, which means Home > NS cannot do any modification on that? > Why should that entry be modified? The PE says that it is using this transport address and the NS gives this information to PUs. > Thank you ver much. > > Best regards, > Youye Chen > > _______________________________________________ > 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 Jul 23 11:07:26 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 LAA16291 for ; Wed, 23 Jul 2003 11:07: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 19fLCm-0006FL-5v; Wed, 23 Jul 2003 11:07:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19fLCf-0006EO-4W for rserpool@optimus.ietf.org; Wed, 23 Jul 2003 11:06:53 -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 LAA16269 for ; Wed, 23 Jul 2003 11:06:48 -0400 (EDT) From: Maureen.Stillman@nokia.com Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19fLCc-0005KS-00 for rserpool@ietf.org; Wed, 23 Jul 2003 11:06:50 -0400 Received: from [63.78.179.217] (helo=mgw-dax2.ext.nokia.com) by ietf-mx with esmtp (Exim 4.12) id 19fLCR-0005K7-00 for rserpool@ietf.org; Wed, 23 Jul 2003 11:06:39 -0400 Received: from davir04nok.americas.nokia.com (davir04nok.americas.nokia.com [172.18.242.87]) by mgw-dax2.ext.nokia.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id h6NF6RG15213 for ; Wed, 23 Jul 2003 10:06:27 -0500 (CDT) Received: from daebh002.NOE.Nokia.com (unverified) by davir04nok.americas.nokia.com (Content Technologies SMTPRS 4.2.5) with ESMTP id for ; Wed, 23 Jul 2003 10:06:50 -0500 Received: from daebe007.NOE.Nokia.com ([172.18.242.211]) by daebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139); Wed, 23 Jul 2003 10:06:22 -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: Wed, 23 Jul 2003 10:06:21 -0500 Message-ID: <57A26D272F67A743952F6B4371B8F811021CFE4C@daebe007.americas.nokia.com> Thread-Topic: Two security issues from IETF #57 Thread-Index: AcNRK/mzlTTfkUJiR3mPshTjyDnSrg== To: X-OriginalArrivalTime: 23 Jul 2003 15:06:22.0369 (UTC) FILETIME=[FA717910:01C3512B] Content-Transfer-Encoding: quoted-printable Subject: [Rserpool] Two security issues from IETF #57 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 The security discussion at IETF #57 raised two issues that we agreed = would be brought to the list for comment. Issue #1 TLS or IPsec mandatory to implement? The security design team consensus was that the network designer could = either use TLS or IPsec as mandatory to implement for ENRP-PE and = ENRP-ENRP communication. The PU-ENRP was previously decided to be = mandatory to implement TLS for reasons of interoperability. Direction = from the ADs and consensus in the meeting was that one security = mechanism should be made mandatory to implement for all. It was agreed = to select TLS as mandatory to implement by those attending the meeting. = Do the people on the list agree? Issue #2 Security of ENRP server registrations and ENRP to ENRP communications Other clarifications included the restriction of pool elements within a = particular pool to provide the same level of security, for simplicity. = In addition, an ENRP server will either have all registrations and thus = namespace entries secured or none, also for reasons of simplicity. A = mixed security rating for the elements stored in the ENRP database would = complicate the client as well as the ENRP server. The client would = have to implement a security policy which would review the entries = returned by ENRP and select them based on a security policy. It is also = unclear what the impact of a mixed database is on security as a whole. = It was agreed to restrict the ENRP database to secure registrations only = and secure communications between ENRP servers OR insecure registrations = only by those attending the meeting. Do the people on the list agree? Comments? -- maureen _______________________________________________ rserpool mailing list rserpool@ietf.org https://www1.ietf.org/mailman/listinfo/rserpool From exim@www1.ietf.org Wed Jul 23 11:07: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 LAA16293 for ; Wed, 23 Jul 2003 11:07: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 19fLCm-0006Fx-Mi for rserpool-archive@odin.ietf.org; Wed, 23 Jul 2003 11:07:00 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6NF705p024045 for rserpool-archive@odin.ietf.org; Wed, 23 Jul 2003 11:07:00 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19fLCm-0006FL-5v; Wed, 23 Jul 2003 11:07:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19fLCf-0006EO-4W for rserpool@optimus.ietf.org; Wed, 23 Jul 2003 11:06:53 -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 LAA16269 for ; Wed, 23 Jul 2003 11:06:48 -0400 (EDT) From: Maureen.Stillman@nokia.com Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19fLCc-0005KS-00 for rserpool@ietf.org; Wed, 23 Jul 2003 11:06:50 -0400 Received: from [63.78.179.217] (helo=mgw-dax2.ext.nokia.com) by ietf-mx with esmtp (Exim 4.12) id 19fLCR-0005K7-00 for rserpool@ietf.org; Wed, 23 Jul 2003 11:06:39 -0400 Received: from davir04nok.americas.nokia.com (davir04nok.americas.nokia.com [172.18.242.87]) by mgw-dax2.ext.nokia.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id h6NF6RG15213 for ; Wed, 23 Jul 2003 10:06:27 -0500 (CDT) Received: from daebh002.NOE.Nokia.com (unverified) by davir04nok.americas.nokia.com (Content Technologies SMTPRS 4.2.5) with ESMTP id for ; Wed, 23 Jul 2003 10:06:50 -0500 Received: from daebe007.NOE.Nokia.com ([172.18.242.211]) by daebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139); Wed, 23 Jul 2003 10:06:22 -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: Wed, 23 Jul 2003 10:06:21 -0500 Message-ID: <57A26D272F67A743952F6B4371B8F811021CFE4C@daebe007.americas.nokia.com> Thread-Topic: Two security issues from IETF #57 Thread-Index: AcNRK/mzlTTfkUJiR3mPshTjyDnSrg== To: X-OriginalArrivalTime: 23 Jul 2003 15:06:22.0369 (UTC) FILETIME=[FA717910:01C3512B] Content-Transfer-Encoding: quoted-printable Subject: [Rserpool] Two security issues from IETF #57 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 The security discussion at IETF #57 raised two issues that we agreed = would be brought to the list for comment. Issue #1 TLS or IPsec mandatory to implement? The security design team consensus was that the network designer could = either use TLS or IPsec as mandatory to implement for ENRP-PE and = ENRP-ENRP communication. The PU-ENRP was previously decided to be = mandatory to implement TLS for reasons of interoperability. Direction = from the ADs and consensus in the meeting was that one security = mechanism should be made mandatory to implement for all. It was agreed = to select TLS as mandatory to implement by those attending the meeting. = Do the people on the list agree? Issue #2 Security of ENRP server registrations and ENRP to ENRP communications Other clarifications included the restriction of pool elements within a = particular pool to provide the same level of security, for simplicity. = In addition, an ENRP server will either have all registrations and thus = namespace entries secured or none, also for reasons of simplicity. A = mixed security rating for the elements stored in the ENRP database would = complicate the client as well as the ENRP server. The client would = have to implement a security policy which would review the entries = returned by ENRP and select them based on a security policy. It is also = unclear what the impact of a mixed database is on security as a whole. = It was agreed to restrict the ENRP database to secure registrations only = and secure communications between ENRP servers OR insecure registrations = only by those attending the meeting. Do the people on the list agree? Comments? -- maureen _______________________________________________ rserpool mailing list rserpool@ietf.org https://www1.ietf.org/mailman/listinfo/rserpool From rserpool-admin@ietf.org Wed Jul 23 11:28:29 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 LAA16872 for ; Wed, 23 Jul 2003 11:28:29 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19fLX7-0007D9-L5; Wed, 23 Jul 2003 11:28:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19fLWG-00077P-5v for rserpool@optimus.ietf.org; Wed, 23 Jul 2003 11:27: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 LAA16826 for ; Wed, 23 Jul 2003 11:27:05 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19fLWF-0005Rz-00 for rserpool@ietf.org; Wed, 23 Jul 2003 11:27:07 -0400 Received: from motgate3.mot.com ([144.189.100.103]) by ietf-mx with esmtp (Exim 4.12) id 19fLW4-0005Ri-00 for rserpool@ietf.org; Wed, 23 Jul 2003 11:26:56 -0400 Received: from az33exr02.mot.com (az33exr02.mot.com [10.64.251.232]) by motgate3.mot.com (Motorola/Motgate3) with ESMTP id h6NFQHB0018298 for ; Wed, 23 Jul 2003 08:26:17 -0700 (MST) Received: from il02exm02.corp.mot.com (il02exm02.corp.mot.com [10.0.100.55]) by az33exr02.mot.com (Motorola/az33exr02) with ESMTP id h6NFQGew011779 for ; Wed, 23 Jul 2003 10:26:16 -0500 Received: by il02exm02.corp.mot.com with Internet Mail Service (5.5.2657.2) id ; Wed, 23 Jul 2003 10:26:15 -0500 Message-ID: <4D87884B6A6D4E438A8592BCC9C85DCA0A91A6F1@il02exm06.corp.mot.com> From: Silverton Aron-C1710C To: "'Maureen.Stillman@nokia.com'" , "'rserpool@ietf.org'" Subject: RE: [Rserpool] Two security issues from IETF #57 Date: Wed, 23 Jul 2003 10:26:13 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.2) Content-Type: text/plain 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: , Hi Maureen, Comments inline. Maureen.Stillman@nokia.com wrote: > The security discussion at IETF #57 raised two issues that we agreed > would be brought to the list for comment. > > Issue #1 > TLS or IPsec mandatory to implement? > > The security design team consensus was that the network designer > could either use TLS or IPsec as mandatory to implement for ENRP-PE > and ENRP-ENRP communication. The PU-ENRP was previously decided to > be mandatory to implement TLS for reasons of interoperability. > Direction from the ADs and consensus in the meeting was that one > security mechanism should be made mandatory to implement for all. It > was agreed to select TLS as mandatory to implement by those attending > the meeting. Do the people on the list agree? Agree. > > Issue #2 > Security of ENRP server registrations and ENRP to ENRP communications > It was agreed to > restrict the ENRP database to secure registrations only and secure > communications between ENRP servers OR insecure registrations only by > those attending the meeting. Do the people on the list agree? I'm not sure that I understand what was agreed upon. Are we talking about two modes of operation: (1) Secure registrations only and secure ENRP-ENRP traffic, and (2) Insecure registrations only and insecure ENRP-ENRP traffic? My feeling is that ENRP-ENRP should be secured in any case, but this may not be practical. This will have an affect on the use of multicast between ENRP servers and I believe that we should discuss this during the next security design team meeting. (I have previously sent an email regarding this to the design team members.) My thought would be to disallow use of multicast in ENRPv1, but leave a section in the draft explaining how it could be used properly with secure multicast. Perhaps by ENRPv2, there will be a secure IGMP or something similar. Developing our own custom secure multicast option should not be an option in my opinion. In all likelihood, an operator with a closed system (not traversing the Internet) will probably choose to do whatever they want in terms of ENRP-ENRP security and multicast. > > Comments? > > -- maureen > Regards, Aron _______________________________________________ rserpool mailing list rserpool@ietf.org https://www1.ietf.org/mailman/listinfo/rserpool From exim@www1.ietf.org Wed Jul 23 11:28:29 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 LAA16874 for ; Wed, 23 Jul 2003 11:28:29 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19fLX7-0007DV-OG for rserpool-archive@odin.ietf.org; Wed, 23 Jul 2003 11:28:01 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6NFS1Ds027730 for rserpool-archive@odin.ietf.org; Wed, 23 Jul 2003 11:28:01 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19fLX7-0007D9-L5; Wed, 23 Jul 2003 11:28:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19fLWG-00077P-5v for rserpool@optimus.ietf.org; Wed, 23 Jul 2003 11:27: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 LAA16826 for ; Wed, 23 Jul 2003 11:27:05 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19fLWF-0005Rz-00 for rserpool@ietf.org; Wed, 23 Jul 2003 11:27:07 -0400 Received: from motgate3.mot.com ([144.189.100.103]) by ietf-mx with esmtp (Exim 4.12) id 19fLW4-0005Ri-00 for rserpool@ietf.org; Wed, 23 Jul 2003 11:26:56 -0400 Received: from az33exr02.mot.com (az33exr02.mot.com [10.64.251.232]) by motgate3.mot.com (Motorola/Motgate3) with ESMTP id h6NFQHB0018298 for ; Wed, 23 Jul 2003 08:26:17 -0700 (MST) Received: from il02exm02.corp.mot.com (il02exm02.corp.mot.com [10.0.100.55]) by az33exr02.mot.com (Motorola/az33exr02) with ESMTP id h6NFQGew011779 for ; Wed, 23 Jul 2003 10:26:16 -0500 Received: by il02exm02.corp.mot.com with Internet Mail Service (5.5.2657.2) id ; Wed, 23 Jul 2003 10:26:15 -0500 Message-ID: <4D87884B6A6D4E438A8592BCC9C85DCA0A91A6F1@il02exm06.corp.mot.com> From: Silverton Aron-C1710C To: "'Maureen.Stillman@nokia.com'" , "'rserpool@ietf.org'" Subject: RE: [Rserpool] Two security issues from IETF #57 Date: Wed, 23 Jul 2003 10:26:13 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.2) Content-Type: text/plain 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: , Hi Maureen, Comments inline. Maureen.Stillman@nokia.com wrote: > The security discussion at IETF #57 raised two issues that we agreed > would be brought to the list for comment. > > Issue #1 > TLS or IPsec mandatory to implement? > > The security design team consensus was that the network designer > could either use TLS or IPsec as mandatory to implement for ENRP-PE > and ENRP-ENRP communication. The PU-ENRP was previously decided to > be mandatory to implement TLS for reasons of interoperability. > Direction from the ADs and consensus in the meeting was that one > security mechanism should be made mandatory to implement for all. It > was agreed to select TLS as mandatory to implement by those attending > the meeting. Do the people on the list agree? Agree. > > Issue #2 > Security of ENRP server registrations and ENRP to ENRP communications > It was agreed to > restrict the ENRP database to secure registrations only and secure > communications between ENRP servers OR insecure registrations only by > those attending the meeting. Do the people on the list agree? I'm not sure that I understand what was agreed upon. Are we talking about two modes of operation: (1) Secure registrations only and secure ENRP-ENRP traffic, and (2) Insecure registrations only and insecure ENRP-ENRP traffic? My feeling is that ENRP-ENRP should be secured in any case, but this may not be practical. This will have an affect on the use of multicast between ENRP servers and I believe that we should discuss this during the next security design team meeting. (I have previously sent an email regarding this to the design team members.) My thought would be to disallow use of multicast in ENRPv1, but leave a section in the draft explaining how it could be used properly with secure multicast. Perhaps by ENRPv2, there will be a secure IGMP or something similar. Developing our own custom secure multicast option should not be an option in my opinion. In all likelihood, an operator with a closed system (not traversing the Internet) will probably choose to do whatever they want in terms of ENRP-ENRP security and multicast. > > Comments? > > -- maureen > Regards, Aron _______________________________________________ rserpool mailing list rserpool@ietf.org https://www1.ietf.org/mailman/listinfo/rserpool