From mailman-admin@ietf.org Thu May 1 13:48:48 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA24945 for ; Thu, 1 May 2003 13:48:48 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h41Hsv827024 for ; Thu, 1 May 2003 13:54:57 -0400 Date: Thu, 01 May 2003 13:54:57 -0400 Message-ID: <20030501175457.17986.81271.Mailman@www1.ietf.org> Subject: ietf.org mailing list memberships reminder From: mailman-owner@www1.ietf.org To: rserpool-archive@ietf.org X-No-Archive: yes X-Ack: no Sender: mailman-admin@ietf.org Errors-To: mailman-admin@ietf.org X-BeenThere: mailman@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk This is a reminder, sent out once a month, about your ietf.org mailing list memberships. It includes your subscription info and how to use it to change it or unsubscribe from a list. You can visit the URLs to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on. In addition to the URL interfaces, you can also use email to make such changes. For more info, send a message to the '-request' address of the list (for example, rserpool-request@ietf.org) containing just the word 'help' in the message body, and an email message will be sent to you with instructions. *************************************************************************** Note Well All statements related to the activities of the IETF and addressed to the IETF are subject to all provisions of Section 10 of RFC 2026, which grants to the IETF and its participants certain licenses and rights in such statements. Such statements include verbal statements in IETF meetings, as well as written and electronic communications made at any time or place, which are addressed to * the IETF plenary session, * any IETF working group or portion thereof, * the IESG, or any member thereof on behalf of the IESG, * the IAB or any member thereof on behalf of the IAB, * any IETF mailing list, including the IETF list itself, any working group or design team list, or any other list functioning under IETF auspices, * the RFC Editor or the Internet-Drafts function Statements made outside of an IETF meeting, mailing list or other function, that are clearly not intended to be input to an IETF activity, group or function, are not subject to these provisions. *************************************************************************** If you have questions, problems, comments, etc, send them to mailman-owner@www1.ietf.org. Thanks! Passwords for rserpool-archive@lists.ietf.org: List Password // URL ---- -------- rserpool@ietf.org RVOD https://www1.ietf.org/mailman/options/rserpool/rserpool-archive%40lists.ietf.org From rserpool-admin@ietf.org Fri May 2 11:35:48 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA18153 for ; Fri, 2 May 2003 11:35:48 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h42Fg8832034; Fri, 2 May 2003 11:42:08 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h42FfT831959 for ; Fri, 2 May 2003 11:41:29 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA18064 for ; Fri, 2 May 2003 11:34: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 19BcaP-00052Q-00 for rserpool@ietf.org; Fri, 02 May 2003 11:36:34 -0400 Received: from mgw-dax2.ext.nokia.com ([63.78.179.217]) by ietf-mx with esmtp (Exim 4.12) id 19BcaK-00052K-00 for rserpool@ietf.org; Fri, 02 May 2003 11:36:28 -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 h42Fajb19437 for ; Fri, 2 May 2003 10:36:45 -0500 (CDT) Received: from daebh001.NOE.Nokia.com (unverified) by davir02nok.americas.nokia.com (Content Technologies SMTPRS 4.2.5) with ESMTP id for ; Fri, 2 May 2003 10:36:45 -0500 Received: from daebe007.NOE.Nokia.com ([172.18.242.211]) by daebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139); Fri, 2 May 2003 08:36:20 -0700 X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Date: Fri, 2 May 2003 10:36:20 -0500 Message-ID: <57A26D272F67A743952F6B4371B8F811E68108@daebe007.americas.nokia.com> Thread-Topic: Next security design team teleconference -- Tuesday, May 6 Thread-Index: AcMQwJRGS/Vsi8k2TYypvc46/+aSSQ== To: X-OriginalArrivalTime: 02 May 2003 15:36:21.0162 (UTC) FILETIME=[94BC00A0:01C310C0] Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h42FfT831960 Subject: [Rserpool] Next security design team teleconference -- Tuesday, May 6 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: 8bit The next security design team teleconference will be held on Tuesday, May 6 at 10AM EDT USA. Here is the call in number: DIAL-IN NUMBERS & PASSCODES: USA Toll Free Number: 877-940-8608 USA Toll Number: +1-712-247-6284 (for international callers) PARTICIPANT PASSCODE: 538600 We will discuss outstanding security issues. It is not too late to join the design team. We are open to everyone. Just drop me an e-mail. Thanks. -- maureen _______________________________________________ rserpool mailing list rserpool@ietf.org https://www1.ietf.org/mailman/listinfo/rserpool From mailnull@www1.ietf.org Fri May 2 11:36:19 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA18184 for ; Fri, 2 May 2003 11:36:19 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h42Fgrp32081 for rserpool-archive@odin.ietf.org; Fri, 2 May 2003 11:42:53 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h42Fg8832034; Fri, 2 May 2003 11:42:08 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h42FfT831959 for ; Fri, 2 May 2003 11:41:29 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA18064 for ; Fri, 2 May 2003 11:34: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 19BcaP-00052Q-00 for rserpool@ietf.org; Fri, 02 May 2003 11:36:34 -0400 Received: from mgw-dax2.ext.nokia.com ([63.78.179.217]) by ietf-mx with esmtp (Exim 4.12) id 19BcaK-00052K-00 for rserpool@ietf.org; Fri, 02 May 2003 11:36:28 -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 h42Fajb19437 for ; Fri, 2 May 2003 10:36:45 -0500 (CDT) Received: from daebh001.NOE.Nokia.com (unverified) by davir02nok.americas.nokia.com (Content Technologies SMTPRS 4.2.5) with ESMTP id for ; Fri, 2 May 2003 10:36:45 -0500 Received: from daebe007.NOE.Nokia.com ([172.18.242.211]) by daebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139); Fri, 2 May 2003 08:36:20 -0700 X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Date: Fri, 2 May 2003 10:36:20 -0500 Message-ID: <57A26D272F67A743952F6B4371B8F811E68108@daebe007.americas.nokia.com> Thread-Topic: Next security design team teleconference -- Tuesday, May 6 Thread-Index: AcMQwJRGS/Vsi8k2TYypvc46/+aSSQ== To: X-OriginalArrivalTime: 02 May 2003 15:36:21.0162 (UTC) FILETIME=[94BC00A0:01C310C0] Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h42FfT831960 Subject: [Rserpool] Next security design team teleconference -- Tuesday, May 6 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: 8bit The next security design team teleconference will be held on Tuesday, May 6 at 10AM EDT USA. Here is the call in number: DIAL-IN NUMBERS & PASSCODES: USA Toll Free Number: 877-940-8608 USA Toll Number: +1-712-247-6284 (for international callers) PARTICIPANT PASSCODE: 538600 We will discuss outstanding security issues. It is not too late to join the design team. We are open to everyone. Just drop me an e-mail. Thanks. -- maureen _______________________________________________ rserpool mailing list rserpool@ietf.org https://www1.ietf.org/mailman/listinfo/rserpool From rserpool-admin@ietf.org Tue May 13 15:30:25 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA26721 for ; Tue, 13 May 2003 15:30:25 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4DIuNB21683; Tue, 13 May 2003 14:56:23 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4DItFB21598 for ; Tue, 13 May 2003 14:55:15 -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 PAA26647 for ; Tue, 13 May 2003 15:28:34 -0400 (EDT) From: Maureen.Stillman@nokia.com Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19FfTr-00073Z-00 for rserpool@ietf.org; Tue, 13 May 2003 15:30:31 -0400 Received: from [63.78.179.217] (helo=mgw-dax2.ext.nokia.com) by ietf-mx with esmtp (Exim 4.12) id 19FfTq-00073Q-00 for rserpool@ietf.org; Tue, 13 May 2003 15:30:30 -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 h4DJVVb17890 for ; Tue, 13 May 2003 14:31:31 -0500 (CDT) Received: from daebh001.NOE.Nokia.com (unverified) by davir04nok.americas.nokia.com (Content Technologies SMTPRS 4.2.5) with ESMTP id for ; Tue, 13 May 2003 14:31:30 -0500 Received: from daebe007.NOE.Nokia.com ([172.18.242.211]) by daebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139); Tue, 13 May 2003 12:31:10 -0700 X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Date: Tue, 13 May 2003 14:31:10 -0500 Message-ID: <57A26D272F67A743952F6B4371B8F81101222D28@daebe007.americas.nokia.com> Thread-Topic: Minutes of the security design team -- May 6, 2003 Thread-Index: AcMZhjSoAJw+CF75QY+q5XBmSqS95Q== To: X-OriginalArrivalTime: 13 May 2003 19:31:10.0866 (UTC) FILETIME=[35657720:01C31986] Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h4DItFB21599 Subject: [Rserpool] Minutes of the security design team -- May 6, 2003 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: 8bit Attending the teleconference on May 6, 2003 were: Aron Silverton Maureen Stillman Michael Tuexen 1) Ports for ENRP and ASAP We received a response to our question about the use of two ports for ENRP -- one for secure communications via TLS and the other for insecure. Jon Peterson consulted with Eric Rescorla and they said two ports or one port -- both were acceptable. Based on this response we are interested in the two port option for reasons of implementation simplicity. Therefore, we need to make the request to IANA for the following: We need port numbers for the ENRP server and for ASAP. We need two port numbers each for SCTP, TCP: one secure, one not secure At the same time, we will request a multicast port/address for ENRP. Michael will propose what we need as this was not clear. Action item: Michael will draft an e-mail with what we need and send it to the Rserpool mailing list for review and comment. 2) Mixed response of secure and insecure items in the namespace for the client ENRP servers that have both: PE registrations using TLS and PE registrations not using TLS There were two options discussed: Option 1) PE registration entries that had used TLS would be flagged as such. The ENRP server would pass along a list to the PU with some entries marked as "secured" and others marked as not. Option 2) An ENRP server that supports security would only accept PE input that used TLS. All other registrations would be rejected. Then, when the PU requests a pool name resolution (securely), it would get only secured entries in response. The reason to support #1 is that it lets the PU decide what entries to use, trusted or not. The reason to support #2 is simplicity and support for a consistent security policy. The question concerns whether to allow for a "split" namespace in which some of the pool entries are "secured" and some are not. We did not receive a response from Eric Rescorla on this item. Due to the response on the first item, we decided for reasons of simplicity to go with option 2. This simplifies both the implementation and the protocol. No changes to the ASAP protocol are necessary. If security is required, all communication would be done using TLS on the secured ports and the PU would receive only trusted entries. If security is not required, then all communication would be done on the unsecured ports and the PU would receive untrusted entries. Comments on this proposal or on the minutes? -- maureen _______________________________________________ rserpool mailing list rserpool@ietf.org https://www1.ietf.org/mailman/listinfo/rserpool From mailnull@www1.ietf.org Tue May 13 15:30:56 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA26748 for ; Tue, 13 May 2003 15:30:56 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h4DIv6D21736 for rserpool-archive@odin.ietf.org; Tue, 13 May 2003 14:57:06 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4DIuNB21683; Tue, 13 May 2003 14:56:23 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4DItFB21598 for ; Tue, 13 May 2003 14:55:15 -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 PAA26647 for ; Tue, 13 May 2003 15:28:34 -0400 (EDT) From: Maureen.Stillman@nokia.com Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19FfTr-00073Z-00 for rserpool@ietf.org; Tue, 13 May 2003 15:30:31 -0400 Received: from [63.78.179.217] (helo=mgw-dax2.ext.nokia.com) by ietf-mx with esmtp (Exim 4.12) id 19FfTq-00073Q-00 for rserpool@ietf.org; Tue, 13 May 2003 15:30:30 -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 h4DJVVb17890 for ; Tue, 13 May 2003 14:31:31 -0500 (CDT) Received: from daebh001.NOE.Nokia.com (unverified) by davir04nok.americas.nokia.com (Content Technologies SMTPRS 4.2.5) with ESMTP id for ; Tue, 13 May 2003 14:31:30 -0500 Received: from daebe007.NOE.Nokia.com ([172.18.242.211]) by daebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139); Tue, 13 May 2003 12:31:10 -0700 X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Date: Tue, 13 May 2003 14:31:10 -0500 Message-ID: <57A26D272F67A743952F6B4371B8F81101222D28@daebe007.americas.nokia.com> Thread-Topic: Minutes of the security design team -- May 6, 2003 Thread-Index: AcMZhjSoAJw+CF75QY+q5XBmSqS95Q== To: X-OriginalArrivalTime: 13 May 2003 19:31:10.0866 (UTC) FILETIME=[35657720:01C31986] Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h4DItFB21599 Subject: [Rserpool] Minutes of the security design team -- May 6, 2003 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: 8bit Attending the teleconference on May 6, 2003 were: Aron Silverton Maureen Stillman Michael Tuexen 1) Ports for ENRP and ASAP We received a response to our question about the use of two ports for ENRP -- one for secure communications via TLS and the other for insecure. Jon Peterson consulted with Eric Rescorla and they said two ports or one port -- both were acceptable. Based on this response we are interested in the two port option for reasons of implementation simplicity. Therefore, we need to make the request to IANA for the following: We need port numbers for the ENRP server and for ASAP. We need two port numbers each for SCTP, TCP: one secure, one not secure At the same time, we will request a multicast port/address for ENRP. Michael will propose what we need as this was not clear. Action item: Michael will draft an e-mail with what we need and send it to the Rserpool mailing list for review and comment. 2) Mixed response of secure and insecure items in the namespace for the client ENRP servers that have both: PE registrations using TLS and PE registrations not using TLS There were two options discussed: Option 1) PE registration entries that had used TLS would be flagged as such. The ENRP server would pass along a list to the PU with some entries marked as "secured" and others marked as not. Option 2) An ENRP server that supports security would only accept PE input that used TLS. All other registrations would be rejected. Then, when the PU requests a pool name resolution (securely), it would get only secured entries in response. The reason to support #1 is that it lets the PU decide what entries to use, trusted or not. The reason to support #2 is simplicity and support for a consistent security policy. The question concerns whether to allow for a "split" namespace in which some of the pool entries are "secured" and some are not. We did not receive a response from Eric Rescorla on this item. Due to the response on the first item, we decided for reasons of simplicity to go with option 2. This simplifies both the implementation and the protocol. No changes to the ASAP protocol are necessary. If security is required, all communication would be done using TLS on the secured ports and the PU would receive only trusted entries. If security is not required, then all communication would be done on the unsecured ports and the PU would receive untrusted entries. Comments on this proposal or on the minutes? -- maureen _______________________________________________ rserpool mailing list rserpool@ietf.org https://www1.ietf.org/mailman/listinfo/rserpool From rserpool-admin@ietf.org Sun May 18 04:24:31 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA04784 for ; Sun, 18 May 2003 04:24:31 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4I7qeB21667; Sun, 18 May 2003 03:52:41 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4I7nJB21600 for ; Sun, 18 May 2003 03:49:19 -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 EAA04753 for ; Sun, 18 May 2003 04:20:27 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19HJQv-0002cp-00 for rserpool@ietf.org; Sun, 18 May 2003 04:22:17 -0400 Received: from mail-n.franken.de ([193.175.24.27] ident=postfix) by ietf-mx with esmtp (Exim 4.12) id 19HJQv-0002ck-00 for rserpool@ietf.org; Sun, 18 May 2003 04:22:17 -0400 Received: from lurchi.franken.de (dialin-145-254-156-105.arcor-ip.net [145.254.156.105]) by mail-n.franken.de (Postfix) with ESMTP id 8AF8A245E3 for ; Sun, 18 May 2003 10:23:29 +0200 (CEST) Date: Sun, 18 May 2003 10:22:05 +0200 Mime-Version: 1.0 (Apple Message framework v552) Content-Type: text/plain; charset=US-ASCII; format=flowed From: Michael Tuexen To: rserpool@ietf.org Content-Transfer-Encoding: 7bit Message-Id: X-Mailer: Apple Mail (2.552) Content-Transfer-Encoding: 7bit Subject: [Rserpool] IANA numbers Sender: rserpool-admin@ietf.org Errors-To: rserpool-admin@ietf.org X-BeenThere: rserpool@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Reliable Server Pooling List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Dear all, there are now two numbers assigned by IANA for RSerPool use: - SCTP PPI for ASAP: 11 - SCTP PPI for ENRP: 12 I think more IANA numbers are needed (this assumes a two port strategy for TLS): - SCTP port number for ENRP - SCTP port number for ENRP/TLS - SCTP and TCP port number for ASAP - SCTP and TCP port number for ASAP/TLS - Multicast address and a UDP port number for SERVER ANNOUNCEMENTS I'm suggesting to get one UDP, TCP and SCTP port number for ASAP and use the SCTP and TCP port number for ASAP messages except the SERVER ANNOUNCEMENTS and the UDP port number for SERVER ANNOUNCEMENTS only. Any comments? Best regards Michael _______________________________________________ rserpool mailing list rserpool@ietf.org https://www1.ietf.org/mailman/listinfo/rserpool From mailnull@www1.ietf.org Sun May 18 04:25:03 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA04803 for ; Sun, 18 May 2003 04:25:03 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h4I7rPa21699 for rserpool-archive@odin.ietf.org; Sun, 18 May 2003 03:53:25 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4I7qeB21667; Sun, 18 May 2003 03:52:41 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4I7nJB21600 for ; Sun, 18 May 2003 03:49:19 -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 EAA04753 for ; Sun, 18 May 2003 04:20:27 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19HJQv-0002cp-00 for rserpool@ietf.org; Sun, 18 May 2003 04:22:17 -0400 Received: from mail-n.franken.de ([193.175.24.27] ident=postfix) by ietf-mx with esmtp (Exim 4.12) id 19HJQv-0002ck-00 for rserpool@ietf.org; Sun, 18 May 2003 04:22:17 -0400 Received: from lurchi.franken.de (dialin-145-254-156-105.arcor-ip.net [145.254.156.105]) by mail-n.franken.de (Postfix) with ESMTP id 8AF8A245E3 for ; Sun, 18 May 2003 10:23:29 +0200 (CEST) Date: Sun, 18 May 2003 10:22:05 +0200 Mime-Version: 1.0 (Apple Message framework v552) Content-Type: text/plain; charset=US-ASCII; format=flowed From: Michael Tuexen To: rserpool@ietf.org Content-Transfer-Encoding: 7bit Message-Id: X-Mailer: Apple Mail (2.552) Content-Transfer-Encoding: 7bit Subject: [Rserpool] IANA numbers Sender: rserpool-admin@ietf.org Errors-To: rserpool-admin@ietf.org X-BeenThere: rserpool@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Reliable Server Pooling List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Dear all, there are now two numbers assigned by IANA for RSerPool use: - SCTP PPI for ASAP: 11 - SCTP PPI for ENRP: 12 I think more IANA numbers are needed (this assumes a two port strategy for TLS): - SCTP port number for ENRP - SCTP port number for ENRP/TLS - SCTP and TCP port number for ASAP - SCTP and TCP port number for ASAP/TLS - Multicast address and a UDP port number for SERVER ANNOUNCEMENTS I'm suggesting to get one UDP, TCP and SCTP port number for ASAP and use the SCTP and TCP port number for ASAP messages except the SERVER ANNOUNCEMENTS and the UDP port number for SERVER ANNOUNCEMENTS only. Any comments? Best regards Michael _______________________________________________ rserpool mailing list rserpool@ietf.org https://www1.ietf.org/mailman/listinfo/rserpool From rserpool-admin@ietf.org Mon May 19 17:39:15 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA06706 for ; Mon, 19 May 2003 17:39:15 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4JL8FB20515; Mon, 19 May 2003 17:08:15 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4J9fbB02124 for ; Mon, 19 May 2003 05:41:37 -0400 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA13874; Mon, 19 May 2003 06:12:13 -0400 (EDT) Message-Id: <200305191012.GAA13874@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: rserpool@ietf.org From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Date: Mon, 19 May 2003 06:12:13 -0400 Subject: [Rserpool] I-D ACTION:draft-ietf-rserpool-common-param-04.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 : Aggregate Server Access Protocol (ASAP) and Endpoint Name Resolution (ENRP) Parameters Author(s) : R. Stewart, Q. Xie, M. Tuexen Filename : draft-ietf-rserpool-common-param-04.txt Pages : 26 Date : 2003-5-16 This document details the parameters of the Aggregate Server Access Protocol (ASAP) and Endpoint Name Resolution Protocol (ENRP) protocols defined within the Reliable Server Pooling (RSERPOOL) architecture. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-rserpool-common-param-04.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-common-param-04.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-common-param-04.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-5-16151657.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-rserpool-common-param-04.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-rserpool-common-param-04.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2003-5-16151657.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 May 19 17:39:15 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA06719 for ; Mon, 19 May 2003 17:39:15 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4JL8FB20530; Mon, 19 May 2003 17:08:15 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4J9ffB02128 for ; Mon, 19 May 2003 05:41:41 -0400 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA13890; Mon, 19 May 2003 06:12:18 -0400 (EDT) Message-Id: <200305191012.GAA13890@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: rserpool@ietf.org From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Date: Mon, 19 May 2003 06:12:17 -0400 Subject: [Rserpool] I-D ACTION:draft-ietf-rserpool-enrp-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 : Enpoint Name Resolution Protocol (ENRP) Author(s) : Q. Xie, R. Stewart, M. Stillman Filename : draft-ietf-rserpool-enrp-06.txt Pages : 43 Date : 2003-5-16 Endpoint Name Resolution Protocol (ENRP) is designed to work in conjunction with the Aggregate Server Access Protocol (ASAP) to accomplish the functionality of the Reliable Server Pooling (Rserpool) requirements and architecture. Within the operational scope of Rserpool, ENRP defines the procedures and message formats of a distributed, fault-tolerant registry service for storing, bookkeeping, retrieving, and distributing pool operation and membership information. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-rserpool-enrp-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-enrp-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-enrp-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-5-16151706.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-rserpool-enrp-06.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-rserpool-enrp-06.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2003-5-16151706.I-D@ietf.org> --OtherAccess-- --NextPart-- _______________________________________________ rserpool mailing list rserpool@ietf.org https://www1.ietf.org/mailman/listinfo/rserpool From mailnull@www1.ietf.org Mon May 19 17:39:46 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA06759 for ; Mon, 19 May 2003 17:39:45 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h4JL8q320565 for rserpool-archive@odin.ietf.org; Mon, 19 May 2003 17:08:52 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4JL8EB20500; Mon, 19 May 2003 17:08:14 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4J9fWB02119 for ; Mon, 19 May 2003 05:41:32 -0400 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA13848; Mon, 19 May 2003 06:12:09 -0400 (EDT) Message-Id: <200305191012.GAA13848@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: rserpool@ietf.org From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Date: Mon, 19 May 2003 06:12:08 -0400 Subject: [Rserpool] I-D ACTION:draft-ietf-rserpool-asap-07.txt Sender: rserpool-admin@ietf.org Errors-To: rserpool-admin@ietf.org X-BeenThere: rserpool@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Reliable Server Pooling List-Post: List-Help: List-Subscribe: , --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Reliable Server Pooling Working Group of the IETF. Title : Aggregate Server Access Protocol (ASAP) Author(s) : R. Stewart, Q. Xie, M. Stillman, M. Tuexen Filename : draft-ietf-rserpool-asap-07.txt Pages : 41 Date : 2003-5-16 Aggregate Server Access Protocol (ASAP) in conjunction with the Endpoint Name Resolution Protocol (ENRP) [6] provides a high availability data transfer mechanism over IP networks. ASAP uses a name-based addressing model which isolates a logical communication endpoint from its IP address(es), thus effectively eliminating the binding between the communication endpoint and its physical IP address(es) which normally constitutes a single point of failure. In addition, ASAP defines each logical communication destination as a pool, providing full transparent support for server-pooling and load sharing. It also allows dynamic system scalability - members of a server pool can be added or removed at any time without interrupting the service. ASAP is designed to take full advantage of the network level redundancy provided by the Stream Transmission Control Protocol (SCTP) RFC2960 [4]. Each transport protocol to be used by Pool Elements (PE) and Pool Users (PU) MUST have an accompanying transports mapping document. Note that ASAP messages passed between PE's and ENRP servers MUST use SCTP. The high availability server pooling is gained by combining two protocols, namely ASAP and ENRP, in which ASAP provides the user interface for name to address translation, load sharing management, and fault management while ENRP defines the high availability name translation service. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-rserpool-asap-07.txt To remove yourself from the IETF Announcement list, send a message to ietf-announce-request with the word unsubscribe in the body of the message. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-rserpool-asap-07.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-rserpool-asap-07.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2003-5-16151647.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-rserpool-asap-07.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-rserpool-asap-07.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2003-5-16151647.I-D@ietf.org> --OtherAccess-- --NextPart-- _______________________________________________ rserpool mailing list rserpool@ietf.org https://www1.ietf.org/mailman/listinfo/rserpool From mailnull@www1.ietf.org Mon May 19 17:39:46 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA06765 for ; Mon, 19 May 2003 17:39:46 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h4JL8rH20593 for rserpool-archive@odin.ietf.org; Mon, 19 May 2003 17:08:53 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4JL8FB20530; Mon, 19 May 2003 17:08:15 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4J9ffB02128 for ; Mon, 19 May 2003 05:41:41 -0400 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA13890; Mon, 19 May 2003 06:12:18 -0400 (EDT) Message-Id: <200305191012.GAA13890@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: rserpool@ietf.org From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Date: Mon, 19 May 2003 06:12:17 -0400 Subject: [Rserpool] I-D ACTION:draft-ietf-rserpool-enrp-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 : Enpoint Name Resolution Protocol (ENRP) Author(s) : Q. Xie, R. Stewart, M. Stillman Filename : draft-ietf-rserpool-enrp-06.txt Pages : 43 Date : 2003-5-16 Endpoint Name Resolution Protocol (ENRP) is designed to work in conjunction with the Aggregate Server Access Protocol (ASAP) to accomplish the functionality of the Reliable Server Pooling (Rserpool) requirements and architecture. Within the operational scope of Rserpool, ENRP defines the procedures and message formats of a distributed, fault-tolerant registry service for storing, bookkeeping, retrieving, and distributing pool operation and membership information. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-rserpool-enrp-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-enrp-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-enrp-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-5-16151706.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-rserpool-enrp-06.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-rserpool-enrp-06.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2003-5-16151706.I-D@ietf.org> --OtherAccess-- --NextPart-- _______________________________________________ rserpool mailing list rserpool@ietf.org https://www1.ietf.org/mailman/listinfo/rserpool From mailnull@www1.ietf.org Mon May 19 18:27:15 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA06760 for ; Mon, 19 May 2003 17:39:46 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h4JL8qT20563 for rserpool-archive@odin.ietf.org; Mon, 19 May 2003 17:08:52 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4JL8FB20515; Mon, 19 May 2003 17:08:15 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4J9fbB02124 for ; Mon, 19 May 2003 05:41:37 -0400 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA13874; Mon, 19 May 2003 06:12:13 -0400 (EDT) Message-Id: <200305191012.GAA13874@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: rserpool@ietf.org From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Date: Mon, 19 May 2003 06:12:13 -0400 Subject: [Rserpool] I-D ACTION:draft-ietf-rserpool-common-param-04.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 : Aggregate Server Access Protocol (ASAP) and Endpoint Name Resolution (ENRP) Parameters Author(s) : R. Stewart, Q. Xie, M. Tuexen Filename : draft-ietf-rserpool-common-param-04.txt Pages : 26 Date : 2003-5-16 This document details the parameters of the Aggregate Server Access Protocol (ASAP) and Endpoint Name Resolution Protocol (ENRP) protocols defined within the Reliable Server Pooling (RSERPOOL) architecture. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-rserpool-common-param-04.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-common-param-04.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-common-param-04.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-5-16151657.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-rserpool-common-param-04.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-rserpool-common-param-04.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2003-5-16151657.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 May 19 18:27:17 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA06705 for ; Mon, 19 May 2003 17:39:14 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4JL8EB20500; Mon, 19 May 2003 17:08:14 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4J9fWB02119 for ; Mon, 19 May 2003 05:41:32 -0400 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA13848; Mon, 19 May 2003 06:12:09 -0400 (EDT) Message-Id: <200305191012.GAA13848@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: rserpool@ietf.org From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Date: Mon, 19 May 2003 06:12:08 -0400 Subject: [Rserpool] I-D ACTION:draft-ietf-rserpool-asap-07.txt Sender: rserpool-admin@ietf.org Errors-To: rserpool-admin@ietf.org X-BeenThere: rserpool@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Reliable Server Pooling List-Post: List-Help: List-Subscribe: , --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Reliable Server Pooling Working Group of the IETF. Title : Aggregate Server Access Protocol (ASAP) Author(s) : R. Stewart, Q. Xie, M. Stillman, M. Tuexen Filename : draft-ietf-rserpool-asap-07.txt Pages : 41 Date : 2003-5-16 Aggregate Server Access Protocol (ASAP) in conjunction with the Endpoint Name Resolution Protocol (ENRP) [6] provides a high availability data transfer mechanism over IP networks. ASAP uses a name-based addressing model which isolates a logical communication endpoint from its IP address(es), thus effectively eliminating the binding between the communication endpoint and its physical IP address(es) which normally constitutes a single point of failure. In addition, ASAP defines each logical communication destination as a pool, providing full transparent support for server-pooling and load sharing. It also allows dynamic system scalability - members of a server pool can be added or removed at any time without interrupting the service. ASAP is designed to take full advantage of the network level redundancy provided by the Stream Transmission Control Protocol (SCTP) RFC2960 [4]. Each transport protocol to be used by Pool Elements (PE) and Pool Users (PU) MUST have an accompanying transports mapping document. Note that ASAP messages passed between PE's and ENRP servers MUST use SCTP. The high availability server pooling is gained by combining two protocols, namely ASAP and ENRP, in which ASAP provides the user interface for name to address translation, load sharing management, and fault management while ENRP defines the high availability name translation service. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-rserpool-asap-07.txt To remove yourself from the IETF Announcement list, send a message to ietf-announce-request with the word unsubscribe in the body of the message. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-rserpool-asap-07.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-rserpool-asap-07.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2003-5-16151647.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-rserpool-asap-07.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-rserpool-asap-07.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2003-5-16151647.I-D@ietf.org> --OtherAccess-- --NextPart-- _______________________________________________ rserpool mailing list rserpool@ietf.org https://www1.ietf.org/mailman/listinfo/rserpool From mailnull@www1.ietf.org Tue May 20 13:54:02 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA22987 for ; Tue, 20 May 2003 13:54:02 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h4KHKQc20004 for rserpool-archive@odin.ietf.org; Tue, 20 May 2003 13:20:26 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4KHJPB19880; Tue, 20 May 2003 13:19:25 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4KHGVB19749 for ; Tue, 20 May 2003 13:16:31 -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 NAA22840 for ; Tue, 20 May 2003 13:49:37 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19IBDk-0007Cw-00 for rserpool@ietf.org; Tue, 20 May 2003 13:48:17 -0400 Received: from motgate5.mot.com ([144.189.100.105]) by ietf-mx with esmtp (Exim 4.12) id 19IBDk-0007Cp-00 for rserpool@ietf.org; Tue, 20 May 2003 13:48:16 -0400 Received: from il06exr01.mot.com (il06exr01.mot.com [129.188.137.131]) by motgate5.mot.com (Motorola/Motgate5) with ESMTP id h4KHnZYo023653 for ; Tue, 20 May 2003 10:49:35 -0700 (MST) Received: from il27exb01.cig.mot.com (il27exb01.cig.mot.com [136.182.15.100]) by il06exr01.mot.com (Motorola/il06exr01) with ESMTP id h4KHnX1l013703 for ; Tue, 20 May 2003 12:49:33 -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.2656.59) id KK952N92; Tue, 20 May 2003 12:49:33 -0500 Message-ID: <3ECA6B73.1B59E8C2@motorola.com> Date: Tue, 20 May 2003 12:52:51 -0500 From: Qiaobing Xie X-Mailer: Mozilla 4.8 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Rserpool list Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Subject: [Rserpool] New draft releases (ASAP-07, ENRP-06, and Common-Param-04) for your review 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, This round of revision is mainly for capturing what we talked about at the last IETF, in particular, 1) to disallow the support of multiple user transport params in a PE 2) all PEs in a pool must use the same transport type 3) no "control only" PEs allowed 4) all PEs in a pool must use the same data/control config, i.e., all of them being either "data only" or "data and control", but no mixing of the two. ... plus some corrections/fixes/enhancements of text based on comments from the mailing list. Since this update impacts all 3 drafts, you are encouraged to read and review all the three. The following are some specific change items in each draft. =============================================== Common Param draft (v03 -> v04): x cleaned up Abstract x re-arranged text in section 3 to enhance the flow for readability x removed Comm. Restrictions Param (no longer needed) x removed Control-Only option in Transport Use field, and make 0x0 (the blank/unused/unspefied value) to map to Data-only. x changed the term "Control or data" to "Data plus control", so as to make sure people won't mistake that "control only" is still allowed. x removed multiple user transport support in PE parameter def. And made clear that a PE must have one and only one user trans param. x added missing text for existing error cause defs x added new error causes: inconsistent transport type and inconsistent data/control usage. x added a generic error cause code "unspecified error", useful when one needs to report something that does not fit well to any specific cause code. =============================================== =============================================== ASAP (v06 -> v07): x made correction to show that PU can use TCP to carry ASAP messages as well. x no more support for multiple transports for a PE. x removed Data Channel Contact msg (no longer needed). x removed the Commu. Restrictions Param from name-resolution (no longer needed). x Added text on how to use transport type and transport usage fields at registration. x Added text on how to handle policy, transport usage overwrite by the ENRP server. x added the 'R' (rejection) flag to reg-response to allow more flexibility when accepting a reg with warning(s). x Due to the R flag, no longer need the optional Member Selection Policy Param in reg-response. x Added some text to explain the usefulness of ASAP keepalive. x Added text to clarify that the syntax part of the API section is for illustrative purposes only, and not meant to be enforced. x some editorial fixes and corrections (and a spelling check) =============================================== =============================================== ENRP (v05 -> v06): x added clarification on when multiple Peer-name-table-reponse msgs are used and why. x added new procedures and rules in registration handling (4.3) to enforce the consistency of transport type and transport usage for existing pools, and how to use 'R' flag to support sending back "accepted but with a warning" response. =============================================== Your comments will be appreciated. regards, -Qiaobing (on behalf of co-authors) _______________________________________________ rserpool mailing list rserpool@ietf.org https://www1.ietf.org/mailman/listinfo/rserpool From mailnull@www1.ietf.org Tue May 20 18:43:44 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA04353 for ; Tue, 20 May 2003 18:43:44 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h4KMAG109975 for rserpool-archive@odin.ietf.org; Tue, 20 May 2003 18:10:16 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4KMA8B09943; Tue, 20 May 2003 18:10:08 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4KM90B09801 for ; Tue, 20 May 2003 18:09:00 -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 SAA04205 for ; Tue, 20 May 2003 18:41:58 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19IFmh-0001RX-00 for rserpool@ietf.org; Tue, 20 May 2003 18:40:39 -0400 Received: from [144.189.100.106] (helo=motgate6.mot.com) by ietf-mx with esmtp (Exim 4.12) id 19IFmg-0001RR-00 for rserpool@ietf.org; Tue, 20 May 2003 18:40:38 -0400 Received: from il06exr02.mot.com (il06exr02.mot.com [129.188.137.132]) by motgate6.mot.com (Motorola/Motgate6) with ESMTP id h4KMfvKe029458 for ; Tue, 20 May 2003 15:41:58 -0700 (MST) Received: from il27exb01.cig.mot.com (il27exb01.cig.mot.com [136.182.15.100]) by il06exr02.mot.com (Motorola/il06exr02) with ESMTP id h4KMft2J016002 for ; Tue, 20 May 2003 17:41:56 -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.2656.59) id KK952ZMA; Tue, 20 May 2003 17:41:55 -0500 Message-ID: <3ECAA636.C0A704DC@motorola.com> Date: Tue, 20 May 2003 17:03:34 -0500 From: Qiaobing Xie X-Mailer: Mozilla 4.8 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Randall Stewart CC: Phillip Conrad , Rserpool Subject: Re: [Rserpool] Another data channel issue: failover of messagesinbasic mode? References: <5.1.0.14.2.20030401164828.0238ad38@joda.cis.temple.edu> <3E8B7B50.BF421814@motorola.com> <3E8BBFD8.7DC572AD@ieee.org> <5.1.0.14.2.20030403221208.0471b418@joda.cis.temple.edu> <3E8E1553.37B8F67@motorola.com> <3E9DA605.4010209@stewart.chicago.il.us> 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 Randall Stewart wrote: ... > > Yeah, it's quite confusing now. Let me try this: > > > > basic mode - defined as a PU <-> pool session with no control channel; > > enhanced mode - defined as a PU <-> pool session with a control channel; > > > > Note, I don't say PE here because of potential SF. Let's see if we can > > agree on this first :-) > > I would agree with the above :-) Good. With the above definitions, I will try here to re-phrase what I was trying to say earlier in this thread, that is: message failover (MF) and session failover (SF) are **orthogonal** to the two modes as defined above. I.e., one can get MF and SF in either of the modes. I don't think we have any disagreement here to the technical aspects of the protocol. It is just a matter of the accuracy of the terminology/definitions and how to precisely describe the relationship between the modes and SF/MF in the service draft. regards, -Qiaobing _______________________________________________ rserpool mailing list rserpool@ietf.org https://www1.ietf.org/mailman/listinfo/rserpool