From mailman-admin@ietf.org  Sat Mar  1 11:43: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 LAA11217
	for <rserpool-archive@lists.ietf.org>; Sat, 1 Mar 2003 11:43:56 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h21Gr1p21874
	for <rserpool-archive@lists.ietf.org>; Sat, 1 Mar 2003 11:53:01 -0500
Date: Sat, 01 Mar 2003 11:53:01 -0500
Message-ID: <20030301165301.26394.36232.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  Mon Mar  3 09:25:21 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 JAA26664
	for <rserpool-archive@lists.ietf.org>; Mon, 3 Mar 2003 09:25:21 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h23EZFp20861;
	Mon, 3 Mar 2003 09:35:15 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h23EYSp20809
	for <rserpool@optimus.ietf.org>; Mon, 3 Mar 2003 09:34:28 -0500
Received: from mgw-dax2.ext.nokia.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA26643
	for <rserpool@ietf.org>; Mon, 3 Mar 2003 09:23:54 -0500 (EST)
From: Maureen.Stillman@nokia.com
Received: from davir02nok.americas.nokia.com (davir02nok.americas.nokia.com [172.18.242.85])
	by mgw-dax2.ext.nokia.com (Switch-2.2.1/Switch-2.2.0) with ESMTP id h23EQ8O29016
	for <rserpool@ietf.org>; Mon, 3 Mar 2003 08:26:08 -0600 (CST)
Received: from daebh002.NOE.Nokia.com (unverified) by davir02nok.americas.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T60bf656b7aac12f255154@davir02nok.americas.nokia.com> for <rserpool@ietf.org>;
 Mon, 3 Mar 2003 08:25:55 -0600
Received: from daebe007.NOE.Nokia.com ([172.18.242.211]) by daebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Mon, 3 Mar 2003 08:25:55 -0600
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: Mon, 3 Mar 2003 08:25:54 -0600
Message-ID: <57A26D272F67A743952F6B4371B8F811E6808F@daebe007.americas.nokia.com>
Thread-Topic: Rserpool Conference call details for Tuesday, March 4 at 10AM EST USA
Thread-Index: AcLhkMw0Cq1j8O+KSZqmfJs/PQdMYA==
To: <rserpool@ietf.org>
X-OriginalArrivalTime: 03 Mar 2003 14:25:55.0191 (UTC) FILETIME=[CD130070:01C2E190]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h23EYSp20810
Subject: [Rserpool] Rserpool Conference call details for Tuesday, March 4 at 10AM EST USA
Sender: rserpool-admin@ietf.org
Errors-To: rserpool-admin@ietf.org
X-BeenThere: rserpool@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=unsubscribe>
List-Id: Reliable Server Pooling <rserpool.ietf.org>
List-Post: <mailto:rserpool@ietf.org>
List-Help: <mailto:rserpool-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit

The next security design team conference call will be Tuesday, March 4 at 10AM EST USA

Conference call details for Tuesday, March 4 at 10AM EST USA

USA Toll Free Number: 888-658-3075
International Toll Number: +1-484-630-0183

  PASSCODE: 59029

We will discuss the configuration of the data and control channel.  Once this is defined, then we can discuss securing the control channel.  It is not too late to join the design team.  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  Mon Mar  3 09:25:53 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 JAA26688
	for <rserpool-archive@odin.ietf.org>; Mon, 3 Mar 2003 09:25:53 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h23EZrc20885
	for rserpool-archive@odin.ietf.org; Mon, 3 Mar 2003 09:35:53 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h23EZFp20861;
	Mon, 3 Mar 2003 09:35:15 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h23EYSp20809
	for <rserpool@optimus.ietf.org>; Mon, 3 Mar 2003 09:34:28 -0500
Received: from mgw-dax2.ext.nokia.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA26643
	for <rserpool@ietf.org>; Mon, 3 Mar 2003 09:23:54 -0500 (EST)
From: Maureen.Stillman@nokia.com
Received: from davir02nok.americas.nokia.com (davir02nok.americas.nokia.com [172.18.242.85])
	by mgw-dax2.ext.nokia.com (Switch-2.2.1/Switch-2.2.0) with ESMTP id h23EQ8O29016
	for <rserpool@ietf.org>; Mon, 3 Mar 2003 08:26:08 -0600 (CST)
Received: from daebh002.NOE.Nokia.com (unverified) by davir02nok.americas.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T60bf656b7aac12f255154@davir02nok.americas.nokia.com> for <rserpool@ietf.org>;
 Mon, 3 Mar 2003 08:25:55 -0600
Received: from daebe007.NOE.Nokia.com ([172.18.242.211]) by daebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Mon, 3 Mar 2003 08:25:55 -0600
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: Mon, 3 Mar 2003 08:25:54 -0600
Message-ID: <57A26D272F67A743952F6B4371B8F811E6808F@daebe007.americas.nokia.com>
Thread-Topic: Rserpool Conference call details for Tuesday, March 4 at 10AM EST USA
Thread-Index: AcLhkMw0Cq1j8O+KSZqmfJs/PQdMYA==
To: <rserpool@ietf.org>
X-OriginalArrivalTime: 03 Mar 2003 14:25:55.0191 (UTC) FILETIME=[CD130070:01C2E190]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h23EYSp20810
Subject: [Rserpool] Rserpool Conference call details for Tuesday, March 4 at 10AM EST USA
Sender: rserpool-admin@ietf.org
Errors-To: rserpool-admin@ietf.org
X-BeenThere: rserpool@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=unsubscribe>
List-Id: Reliable Server Pooling <rserpool.ietf.org>
List-Post: <mailto:rserpool@ietf.org>
List-Help: <mailto:rserpool-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit

The next security design team conference call will be Tuesday, March 4 at 10AM EST USA

Conference call details for Tuesday, March 4 at 10AM EST USA

USA Toll Free Number: 888-658-3075
International Toll Number: +1-484-630-0183

  PASSCODE: 59029

We will discuss the configuration of the data and control channel.  Once this is defined, then we can discuss securing the control channel.  It is not too late to join the design team.  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  Wed Mar  5 14:29:58 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 OAA23722
	for <rserpool-archive@lists.ietf.org>; Wed, 5 Mar 2003 14:29:58 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h25JeRO12639;
	Wed, 5 Mar 2003 14:40:27 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h25JOXO10142
	for <rserpool@optimus.ietf.org>; Wed, 5 Mar 2003 14:24:33 -0500
Received: from mgw-dax2.ext.nokia.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA22518
	for <rserpool@ietf.org>; Wed, 5 Mar 2003 14:13:23 -0500 (EST)
From: Maureen.Stillman@nokia.com
Received: from davir04nok.americas.nokia.com (davir04nok.americas.nokia.com [172.18.242.87])
	by mgw-dax2.ext.nokia.com (Switch-2.2.5/Switch-2.2.0) with ESMTP id h25JFP812971
	for <rserpool@ietf.org>; Wed, 5 Mar 2003 13:15:25 -0600 (CST)
Received: from daebh002.NOE.Nokia.com (unverified) by davir04nok.americas.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T60cabb30b1ac12f25703c@davir04nok.americas.nokia.com> for <rserpool@ietf.org>;
 Wed, 5 Mar 2003 13:15:25 -0600
Received: from daebe007.NOE.Nokia.com ([172.18.242.211]) by daebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Wed, 5 Mar 2003 13:15:25 -0600
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: Wed, 5 Mar 2003 13:15:25 -0600
Message-ID: <57A26D272F67A743952F6B4371B8F811E68099@daebe007.americas.nokia.com>
Thread-Topic: Draft agenda for IETF #56
Thread-Index: AcLjS5HP6LtwDhstQViKGmQPJD55zg==
To: <rserpool@ietf.org>
X-OriginalArrivalTime: 05 Mar 2003 19:15:25.0662 (UTC) FILETIME=[938207E0:01C2E34B]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h25JOXO10143
Subject: [Rserpool] Draft agenda for IETF #56
Sender: rserpool-admin@ietf.org
Errors-To: rserpool-admin@ietf.org
X-BeenThere: rserpool@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=unsubscribe>
List-Id: Reliable Server Pooling <rserpool.ietf.org>
List-Post: <mailto:rserpool@ietf.org>
List-Help: <mailto:rserpool-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit

Comments?  I will be sending this to the agenda poster by the end of this week.

-- maureen


IETF #56
Reliable Server Pooling WG (rserpool)

Monday, March 17, 2003
=================================

CHAIRs:
Lyndon Ong <lyong@ciena.com> 
Maureen Stillman <Maureen.Stillman@nokia.com>

Draft AGENDA:

Opening Remarks
Lyndon Ong, Maureen Stillman

Rserpool services, 20 min.
 http://www.ietf.org/internet-drafts/draft-conrad-rserpool-service-03.txt
Peter Lei

TCP mapping, 20 min.
 http://www.ietf.org/internet-drafts/draft-conrad-rserpool-tcpmapping-01.txt
Peter Lei

 ASAP -- issue with the control and data channel
 http://www.ietf.org/internet-drafts/draft-ietf-rserpool-common-param-03.txt
 http://www.ietf.org/internet-drafts/draft-ietf-rserpool-asap-06.txt
Randy Stewart, 20 min.

 ENRP and ASAP issues and updates
 http://www.ietf.org/internet-drafts/draft-ietf-rserpool-enrp-04.txt
Qiaobing Xie, 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.

Rserpool implementations
Aron Silverton, 5 minutes

Closing Remarks
Lyndon Ong, Maureen Stillman
_______________________________________________
rserpool mailing list
rserpool@ietf.org
https://www1.ietf.org/mailman/listinfo/rserpool


From mailnull@www1.ietf.org  Wed Mar  5 14:30:28 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 OAA23805
	for <rserpool-archive@odin.ietf.org>; Wed, 5 Mar 2003 14:30:28 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h25Jf7G12780
	for rserpool-archive@odin.ietf.org; Wed, 5 Mar 2003 14:41:07 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h25JeRO12639;
	Wed, 5 Mar 2003 14:40:27 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h25JOXO10142
	for <rserpool@optimus.ietf.org>; Wed, 5 Mar 2003 14:24:33 -0500
Received: from mgw-dax2.ext.nokia.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA22518
	for <rserpool@ietf.org>; Wed, 5 Mar 2003 14:13:23 -0500 (EST)
From: Maureen.Stillman@nokia.com
Received: from davir04nok.americas.nokia.com (davir04nok.americas.nokia.com [172.18.242.87])
	by mgw-dax2.ext.nokia.com (Switch-2.2.5/Switch-2.2.0) with ESMTP id h25JFP812971
	for <rserpool@ietf.org>; Wed, 5 Mar 2003 13:15:25 -0600 (CST)
Received: from daebh002.NOE.Nokia.com (unverified) by davir04nok.americas.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T60cabb30b1ac12f25703c@davir04nok.americas.nokia.com> for <rserpool@ietf.org>;
 Wed, 5 Mar 2003 13:15:25 -0600
Received: from daebe007.NOE.Nokia.com ([172.18.242.211]) by daebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Wed, 5 Mar 2003 13:15:25 -0600
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: Wed, 5 Mar 2003 13:15:25 -0600
Message-ID: <57A26D272F67A743952F6B4371B8F811E68099@daebe007.americas.nokia.com>
Thread-Topic: Draft agenda for IETF #56
Thread-Index: AcLjS5HP6LtwDhstQViKGmQPJD55zg==
To: <rserpool@ietf.org>
X-OriginalArrivalTime: 05 Mar 2003 19:15:25.0662 (UTC) FILETIME=[938207E0:01C2E34B]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h25JOXO10143
Subject: [Rserpool] Draft agenda for IETF #56
Sender: rserpool-admin@ietf.org
Errors-To: rserpool-admin@ietf.org
X-BeenThere: rserpool@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=unsubscribe>
List-Id: Reliable Server Pooling <rserpool.ietf.org>
List-Post: <mailto:rserpool@ietf.org>
List-Help: <mailto:rserpool-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit

Comments?  I will be sending this to the agenda poster by the end of this week.

-- maureen


IETF #56
Reliable Server Pooling WG (rserpool)

Monday, March 17, 2003
=================================

CHAIRs:
Lyndon Ong <lyong@ciena.com> 
Maureen Stillman <Maureen.Stillman@nokia.com>

Draft AGENDA:

Opening Remarks
Lyndon Ong, Maureen Stillman

Rserpool services, 20 min.
 http://www.ietf.org/internet-drafts/draft-conrad-rserpool-service-03.txt
Peter Lei

TCP mapping, 20 min.
 http://www.ietf.org/internet-drafts/draft-conrad-rserpool-tcpmapping-01.txt
Peter Lei

 ASAP -- issue with the control and data channel
 http://www.ietf.org/internet-drafts/draft-ietf-rserpool-common-param-03.txt
 http://www.ietf.org/internet-drafts/draft-ietf-rserpool-asap-06.txt
Randy Stewart, 20 min.

 ENRP and ASAP issues and updates
 http://www.ietf.org/internet-drafts/draft-ietf-rserpool-enrp-04.txt
Qiaobing Xie, 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.

Rserpool implementations
Aron Silverton, 5 minutes

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 Mar  6 13:46:12 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 NAA05794
	for <rserpool-archive@lists.ietf.org>; Thu, 6 Mar 2003 13:46:12 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h26IvEO02877;
	Thu, 6 Mar 2003 13:57:14 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h26IucO02839
	for <rserpool@optimus.ietf.org>; Thu, 6 Mar 2003 13:56:38 -0500
Received: from motgate2.mot.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA05676
	for <rserpool@ietf.org>; Thu, 6 Mar 2003 13:44:59 -0500 (EST)
Received: from pobox.mot.com (pobox.mot.com [129.188.137.100])
	by motgate2.mot.com (Motorola/Motgate2) with ESMTP id h26IluI5006959
	for <rserpool@ietf.org>; Thu, 6 Mar 2003 11:47:56 -0700 (MST)
Received: [from az33exr03.mot.com (az33exr03.mot.com [10.64.251.233]) by pobox.mot.com (MOT-pobox 2.0) with ESMTP id LAA13692 for <rserpool@ietf.org>; Thu, 6 Mar 2003 11:47:03 -0700 (MST)]
Received: from pobox.cstl.labs.mot.com (pobox.cstl.labs.mot.com [173.23.1.1])
	by az33exr03.mot.com (Motorola/az33exr03) with ESMTP id h26IhqD27926
	for <rserpool@ietf.org>; Thu, 6 Mar 2003 12:43:52 -0600
Received: from labs.mot.com ([173.23.93.76]) by
          pobox.cstl.labs.mot.com (Netscape Messaging Server 4.15) with
          ESMTP id HBCC1300.HUL for <rserpool@ietf.org>; Thu, 6 Mar 2003
          12:43:51 -0600 
Message-ID: <3E6796E6.8070700@labs.mot.com>
Date: Thu, 06 Mar 2003 12:43:50 -0600
From: "Aron Silverton"<ajs@labs.mot.com>
Reply-To: ajs@labs.mot.com, ajs@labs.mot.com
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20020918
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: <rserpool@ietf.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Rserpool] RSerPool implementations
Sender: rserpool-admin@ietf.org
Errors-To: rserpool-admin@ietf.org
X-BeenThere: rserpool@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=unsubscribe>
List-Id: Reliable Server Pooling <rserpool.ietf.org>
List-Post: <mailto:rserpool@ietf.org>
List-Help: <mailto:rserpool-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Hello all,

If you are working on an implementation of RSerPool or plan on working
on an implementation, can you please provide me a few bits of
information including:

-Who you are
-Status
-Goal
-Timeline
-Anything else you would like to add

I'll be making some remarks about the various implementation efforts at
the IETF 56 meeting in San Francisco.

Please provide your information to me by 3/12.

Thank you,

Aron


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


From mailnull@www1.ietf.org  Thu Mar  6 13:46:43 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 NAA05826
	for <rserpool-archive@odin.ietf.org>; Thu, 6 Mar 2003 13:46:43 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h26Ivqk02950
	for rserpool-archive@odin.ietf.org; Thu, 6 Mar 2003 13:57:52 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h26IvEO02877;
	Thu, 6 Mar 2003 13:57:14 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h26IucO02839
	for <rserpool@optimus.ietf.org>; Thu, 6 Mar 2003 13:56:38 -0500
Received: from motgate2.mot.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA05676
	for <rserpool@ietf.org>; Thu, 6 Mar 2003 13:44:59 -0500 (EST)
Received: from pobox.mot.com (pobox.mot.com [129.188.137.100])
	by motgate2.mot.com (Motorola/Motgate2) with ESMTP id h26IluI5006959
	for <rserpool@ietf.org>; Thu, 6 Mar 2003 11:47:56 -0700 (MST)
Received: [from az33exr03.mot.com (az33exr03.mot.com [10.64.251.233]) by pobox.mot.com (MOT-pobox 2.0) with ESMTP id LAA13692 for <rserpool@ietf.org>; Thu, 6 Mar 2003 11:47:03 -0700 (MST)]
Received: from pobox.cstl.labs.mot.com (pobox.cstl.labs.mot.com [173.23.1.1])
	by az33exr03.mot.com (Motorola/az33exr03) with ESMTP id h26IhqD27926
	for <rserpool@ietf.org>; Thu, 6 Mar 2003 12:43:52 -0600
Received: from labs.mot.com ([173.23.93.76]) by
          pobox.cstl.labs.mot.com (Netscape Messaging Server 4.15) with
          ESMTP id HBCC1300.HUL for <rserpool@ietf.org>; Thu, 6 Mar 2003
          12:43:51 -0600 
Message-ID: <3E6796E6.8070700@labs.mot.com>
Date: Thu, 06 Mar 2003 12:43:50 -0600
From: "Aron Silverton"<ajs@labs.mot.com>
Reply-To: ajs@labs.mot.com, ajs@labs.mot.com
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20020918
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: <rserpool@ietf.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Rserpool] RSerPool implementations
Sender: rserpool-admin@ietf.org
Errors-To: rserpool-admin@ietf.org
X-BeenThere: rserpool@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=unsubscribe>
List-Id: Reliable Server Pooling <rserpool.ietf.org>
List-Post: <mailto:rserpool@ietf.org>
List-Help: <mailto:rserpool-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Hello all,

If you are working on an implementation of RSerPool or plan on working
on an implementation, can you please provide me a few bits of
information including:

-Who you are
-Status
-Goal
-Timeline
-Anything else you would like to add

I'll be making some remarks about the various implementation efforts at
the IETF 56 meeting in San Francisco.

Please provide your information to me by 3/12.

Thank you,

Aron


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



From rserpool-admin@ietf.org  Thu Mar  6 15:46:34 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 PAA11833
	for <rserpool-archive@lists.ietf.org>; Thu, 6 Mar 2003 15:46:34 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h26KvTO13045;
	Thu, 6 Mar 2003 15:57:29 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h26KpQO12811
	for <rserpool@optimus.ietf.org>; Thu, 6 Mar 2003 15:51:26 -0500
Received: from odin.system.xy (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA11694
	for <rserpool@ietf.org>; Thu, 6 Mar 2003 15:39:43 -0500 (EST)
Received: from odin (localhost [127.0.0.1])
	by odin.system.xy (8.12.2/8.12.2/SuSE Linux 0.6) with ESMTP id h26KOIG5003454;
	Thu, 6 Mar 2003 21:24:19 +0100
Content-Type: text/plain;
  charset="iso-8859-1"
From: Thomas Dreibholz <dreibh@irmgard.exp-math.uni-essen.de>
Organization: University of Essen, Institute for Experimental Mathematics
To: ajs@labs.mot.com, ajs@labs.mot.com, <rserpool@ietf.org>
Subject: Re: [Rserpool] RSerPool implementations
Date: Thu, 6 Mar 2003 21:24:15 +0100
X-Mailer: KMail [version 1.4]
References: <3E6796E6.8070700@labs.mot.com>
In-Reply-To: <3E6796E6.8070700@labs.mot.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Message-Id: <200303062124.18525.dreibh@irmgard.exp-math.uni-essen.de>
X-Virus-Scanned: by amavis-milter (http://amavis.org/)
Content-Transfer-Encoding: 8bit
Sender: rserpool-admin@ietf.org
Errors-To: rserpool-admin@ietf.org
X-BeenThere: rserpool@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=unsubscribe>
List-Id: Reliable Server Pooling <rserpool.ietf.org>
List-Post: <mailto:rserpool@ietf.org>
List-Help: <mailto:rserpool-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Donnerstag, 6. März 2003 19:43, Aron Silverton wrote:
> Hello all,
>
> If you are working on an implementation of RSerPool or plan on working
> on an implementation, can you please provide me a few bits of
> information including:
>
> -Who you are

Thomas Dreibholz, Institute for Experimental Mathematics at the University of 
Essen, Germany


> -Status

- - ASAP implemented (except control channel)
- - nameserver (currently without ENRP)
- - example application (echo service)
- - Currently, we support Linux, FreeBSD and DarwinOS
- - Uses sctplib userland implementation of the University of Essen


> -Goal

Complete, open source, prototype implementation of the RSerPool architecture: 
the rsplib prototype.


> -Timeline

- - Soon: ASAP control channel
- - Soon: Support for kernel SCTP under FreeBSD
- - About summer 2003: Implementation of ENRP


> -Anything else you would like to add

For more information about our implementation, see 
http://tdrwww.exp-math.uni-essen.de/dreibholz/rserpool/ and 
http://www.sctp.de/rserpool.html. An introduction to design and 
implementation of our rsplib prototype is given in our paper at 
http://tdrwww.exp-math.uni-essen.de/dreibholz/rserpool/#Research. It has been 
presented by me at the Linux Conference Australia 2003.


> I'll be making some remarks about the various implementation efforts at
> the IETF 56 meeting in San Francisco.

Please send me a copy of your remarks. I am very interested who else is 
implementing RSerPool.


Best regards
- -- 
=======================================================================
 Dipl.-Inform. Thomas Dreibholz
 Molbachweg 7
 D-51674 Wiehl-Forst    Mail: dreibh@exp-math.uni-essen.de
 Germany                WWW:  http://www.exp-math.uni-essen.de/~dreibh
=======================================================================
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE+Z65x32BbsHYPLWURAmcRAJ0Vy8eT+sBKIiUdfxuSj+by3kfmcgCggQ3f
aoFUZeVcv3ZNb8HoVDe/Ut8=
=FWgK
-----END PGP SIGNATURE-----

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


From mailnull@www1.ietf.org  Thu Mar  6 15:47:05 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 PAA11896
	for <rserpool-archive@odin.ietf.org>; Thu, 6 Mar 2003 15:47:05 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h26KwFr13103
	for rserpool-archive@odin.ietf.org; Thu, 6 Mar 2003 15:58:15 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h26KvTO13045;
	Thu, 6 Mar 2003 15:57:29 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h26KpQO12811
	for <rserpool@optimus.ietf.org>; Thu, 6 Mar 2003 15:51:26 -0500
Received: from odin.system.xy (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA11694
	for <rserpool@ietf.org>; Thu, 6 Mar 2003 15:39:43 -0500 (EST)
Received: from odin (localhost [127.0.0.1])
	by odin.system.xy (8.12.2/8.12.2/SuSE Linux 0.6) with ESMTP id h26KOIG5003454;
	Thu, 6 Mar 2003 21:24:19 +0100
Content-Type: text/plain;
  charset="iso-8859-1"
From: Thomas Dreibholz <dreibh@irmgard.exp-math.uni-essen.de>
Organization: University of Essen, Institute for Experimental Mathematics
To: ajs@labs.mot.com, ajs@labs.mot.com, <rserpool@ietf.org>
Subject: Re: [Rserpool] RSerPool implementations
Date: Thu, 6 Mar 2003 21:24:15 +0100
X-Mailer: KMail [version 1.4]
References: <3E6796E6.8070700@labs.mot.com>
In-Reply-To: <3E6796E6.8070700@labs.mot.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Message-Id: <200303062124.18525.dreibh@irmgard.exp-math.uni-essen.de>
X-Virus-Scanned: by amavis-milter (http://amavis.org/)
Content-Transfer-Encoding: 8bit
Sender: rserpool-admin@ietf.org
Errors-To: rserpool-admin@ietf.org
X-BeenThere: rserpool@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=unsubscribe>
List-Id: Reliable Server Pooling <rserpool.ietf.org>
List-Post: <mailto:rserpool@ietf.org>
List-Help: <mailto:rserpool-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Donnerstag, 6. März 2003 19:43, Aron Silverton wrote:
> Hello all,
>
> If you are working on an implementation of RSerPool or plan on working
> on an implementation, can you please provide me a few bits of
> information including:
>
> -Who you are

Thomas Dreibholz, Institute for Experimental Mathematics at the University of 
Essen, Germany


> -Status

- - ASAP implemented (except control channel)
- - nameserver (currently without ENRP)
- - example application (echo service)
- - Currently, we support Linux, FreeBSD and DarwinOS
- - Uses sctplib userland implementation of the University of Essen


> -Goal

Complete, open source, prototype implementation of the RSerPool architecture: 
the rsplib prototype.


> -Timeline

- - Soon: ASAP control channel
- - Soon: Support for kernel SCTP under FreeBSD
- - About summer 2003: Implementation of ENRP


> -Anything else you would like to add

For more information about our implementation, see 
http://tdrwww.exp-math.uni-essen.de/dreibholz/rserpool/ and 
http://www.sctp.de/rserpool.html. An introduction to design and 
implementation of our rsplib prototype is given in our paper at 
http://tdrwww.exp-math.uni-essen.de/dreibholz/rserpool/#Research. It has been 
presented by me at the Linux Conference Australia 2003.


> I'll be making some remarks about the various implementation efforts at
> the IETF 56 meeting in San Francisco.

Please send me a copy of your remarks. I am very interested who else is 
implementing RSerPool.


Best regards
- -- 
=======================================================================
 Dipl.-Inform. Thomas Dreibholz
 Molbachweg 7
 D-51674 Wiehl-Forst    Mail: dreibh@exp-math.uni-essen.de
 Germany                WWW:  http://www.exp-math.uni-essen.de/~dreibh
=======================================================================
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE+Z65x32BbsHYPLWURAmcRAJ0Vy8eT+sBKIiUdfxuSj+by3kfmcgCggQ3f
aoFUZeVcv3ZNb8HoVDe/Ut8=
=FWgK
-----END PGP SIGNATURE-----

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



From rserpool-admin@ietf.org  Thu Mar  6 17:11:24 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 RAA15411
	for <rserpool-archive@lists.ietf.org>; Thu, 6 Mar 2003 17:11:24 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h26MMSO21424;
	Thu, 6 Mar 2003 17:22:28 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h26MLnO21377
	for <rserpool@optimus.ietf.org>; Thu, 6 Mar 2003 17:21:49 -0500
Received: from ftpbox.mot.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA15374
	for <rserpool@ietf.org>; Thu, 6 Mar 2003 17:10:06 -0500 (EST)
Received: from pobox3.mot.com (pobox3.mot.com [10.64.251.242])
	by ftpbox.mot.com (Motorola/Ftpbox) with ESMTP id h26MC96N026057
	for <rserpool@ietf.org>; Thu, 6 Mar 2003 15:12:10 -0700 (MST)
Received: [from az33exr03.mot.com (az33exr03.mot.com [10.64.251.233]) by pobox3.mot.com (MOT-pobox3 2.0) with ESMTP id PAA23501 for <rserpool@ietf.org>; Thu, 6 Mar 2003 15:10:16 -0700 (MST)]
Received: from pobox.cstl.labs.mot.com (pobox.cstl.labs.mot.com [173.23.1.1])
	by az33exr03.mot.com (Motorola/az33exr03) with ESMTP id h26MC7D13124
	for <rserpool@ietf.org>; Thu, 6 Mar 2003 16:12:08 -0600
Received: from labs.mot.com ([173.23.93.76]) by
          pobox.cstl.labs.mot.com (Netscape Messaging Server 4.15) with
          ESMTP id HBCLO600.1XZ; Thu, 6 Mar 2003 16:12:06 -0600 
Message-ID: <3E67C7B6.8060402@labs.mot.com>
Date: Thu, 06 Mar 2003 16:12:06 -0600
From: "Aron Silverton"<ajs@labs.mot.com>
Reply-To: ajs@labs.mot.com
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20020918
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Thomas Dreibholz<dreibh@irmgard.exp-math.uni-essen.de>
CC: <rserpool@ietf.org>
Subject: Re: [Rserpool] RSerPool implementations
References: <3E6796E6.8070700@labs.mot.com> <200303062124.18525.dreibh@irmgard.exp-math.uni-essen.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit
Sender: rserpool-admin@ietf.org
Errors-To: rserpool-admin@ietf.org
X-BeenThere: rserpool@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=unsubscribe>
List-Id: Reliable Server Pooling <rserpool.ietf.org>
List-Post: <mailto:rserpool@ietf.org>
List-Help: <mailto:rserpool-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit

Thank you Thomas.

If others could also provide any associated URLs as Thomas did, that 
would be great.

I will send a PDF version of my summary slides to anybody that requests 
them sometime around 3/17.

Regards,

Aron

Thomas Dreibholz wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> On Donnerstag, 6. März 2003 19:43, Aron Silverton wrote:
> 
>>Hello all,
>>
>>If you are working on an implementation of RSerPool or plan on working
>>on an implementation, can you please provide me a few bits of
>>information including:
>>
>>-Who you are
> 
> 
> Thomas Dreibholz, Institute for Experimental Mathematics at the University of 
> Essen, Germany
> 
> 
> 
>>-Status
> 
> 
> - - ASAP implemented (except control channel)
> - - nameserver (currently without ENRP)
> - - example application (echo service)
> - - Currently, we support Linux, FreeBSD and DarwinOS
> - - Uses sctplib userland implementation of the University of Essen
> 
> 
> 
>>-Goal
> 
> 
> Complete, open source, prototype implementation of the RSerPool architecture: 
> the rsplib prototype.
> 
> 
> 
>>-Timeline
> 
> 
> - - Soon: ASAP control channel
> - - Soon: Support for kernel SCTP under FreeBSD
> - - About summer 2003: Implementation of ENRP
> 
> 
> 
>>-Anything else you would like to add
> 
> 
> For more information about our implementation, see 
> http://tdrwww.exp-math.uni-essen.de/dreibholz/rserpool/ and 
> http://www.sctp.de/rserpool.html. An introduction to design and 
> implementation of our rsplib prototype is given in our paper at 
> http://tdrwww.exp-math.uni-essen.de/dreibholz/rserpool/#Research. It has been 
> presented by me at the Linux Conference Australia 2003.
> 
> 
> 
>>I'll be making some remarks about the various implementation efforts at
>>the IETF 56 meeting in San Francisco.
> 
> 
> Please send me a copy of your remarks. I am very interested who else is 
> implementing RSerPool.
> 
> 
> Best regards
> - -- 
> =======================================================================
>  Dipl.-Inform. Thomas Dreibholz
>  Molbachweg 7
>  D-51674 Wiehl-Forst    Mail: dreibh@exp-math.uni-essen.de
>  Germany                WWW:  http://www.exp-math.uni-essen.de/~dreibh
> =======================================================================
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.0.6 (GNU/Linux)
> Comment: For info see http://www.gnupg.org
> 
> iD8DBQE+Z65x32BbsHYPLWURAmcRAJ0Vy8eT+sBKIiUdfxuSj+by3kfmcgCggQ3f
> aoFUZeVcv3ZNb8HoVDe/Ut8=
> =FWgK
> -----END PGP SIGNATURE-----
> 
> 


-- 
Aron J. Silverton
Senior Staff Research Engineer
Motorola Laboratories, Networks and Infrastructure Research
Motorola, Inc.

Telephone: 847-576-8747
Fax: 847-576-3240
mailto: ajs@labs.mot.com

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


From mailnull@www1.ietf.org  Thu Mar  6 17:11:54 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 RAA15433
	for <rserpool-archive@odin.ietf.org>; Thu, 6 Mar 2003 17:11:54 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h26MN6U21472
	for rserpool-archive@odin.ietf.org; Thu, 6 Mar 2003 17:23:06 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h26MMSO21424;
	Thu, 6 Mar 2003 17:22:28 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h26MLnO21377
	for <rserpool@optimus.ietf.org>; Thu, 6 Mar 2003 17:21:49 -0500
Received: from ftpbox.mot.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA15374
	for <rserpool@ietf.org>; Thu, 6 Mar 2003 17:10:06 -0500 (EST)
Received: from pobox3.mot.com (pobox3.mot.com [10.64.251.242])
	by ftpbox.mot.com (Motorola/Ftpbox) with ESMTP id h26MC96N026057
	for <rserpool@ietf.org>; Thu, 6 Mar 2003 15:12:10 -0700 (MST)
Received: [from az33exr03.mot.com (az33exr03.mot.com [10.64.251.233]) by pobox3.mot.com (MOT-pobox3 2.0) with ESMTP id PAA23501 for <rserpool@ietf.org>; Thu, 6 Mar 2003 15:10:16 -0700 (MST)]
Received: from pobox.cstl.labs.mot.com (pobox.cstl.labs.mot.com [173.23.1.1])
	by az33exr03.mot.com (Motorola/az33exr03) with ESMTP id h26MC7D13124
	for <rserpool@ietf.org>; Thu, 6 Mar 2003 16:12:08 -0600
Received: from labs.mot.com ([173.23.93.76]) by
          pobox.cstl.labs.mot.com (Netscape Messaging Server 4.15) with
          ESMTP id HBCLO600.1XZ; Thu, 6 Mar 2003 16:12:06 -0600 
Message-ID: <3E67C7B6.8060402@labs.mot.com>
Date: Thu, 06 Mar 2003 16:12:06 -0600
From: "Aron Silverton"<ajs@labs.mot.com>
Reply-To: ajs@labs.mot.com
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20020918
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Thomas Dreibholz<dreibh@irmgard.exp-math.uni-essen.de>
CC: <rserpool@ietf.org>
Subject: Re: [Rserpool] RSerPool implementations
References: <3E6796E6.8070700@labs.mot.com> <200303062124.18525.dreibh@irmgard.exp-math.uni-essen.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit
Sender: rserpool-admin@ietf.org
Errors-To: rserpool-admin@ietf.org
X-BeenThere: rserpool@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=unsubscribe>
List-Id: Reliable Server Pooling <rserpool.ietf.org>
List-Post: <mailto:rserpool@ietf.org>
List-Help: <mailto:rserpool-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit

Thank you Thomas.

If others could also provide any associated URLs as Thomas did, that 
would be great.

I will send a PDF version of my summary slides to anybody that requests 
them sometime around 3/17.

Regards,

Aron

Thomas Dreibholz wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> On Donnerstag, 6. März 2003 19:43, Aron Silverton wrote:
> 
>>Hello all,
>>
>>If you are working on an implementation of RSerPool or plan on working
>>on an implementation, can you please provide me a few bits of
>>information including:
>>
>>-Who you are
> 
> 
> Thomas Dreibholz, Institute for Experimental Mathematics at the University of 
> Essen, Germany
> 
> 
> 
>>-Status
> 
> 
> - - ASAP implemented (except control channel)
> - - nameserver (currently without ENRP)
> - - example application (echo service)
> - - Currently, we support Linux, FreeBSD and DarwinOS
> - - Uses sctplib userland implementation of the University of Essen
> 
> 
> 
>>-Goal
> 
> 
> Complete, open source, prototype implementation of the RSerPool architecture: 
> the rsplib prototype.
> 
> 
> 
>>-Timeline
> 
> 
> - - Soon: ASAP control channel
> - - Soon: Support for kernel SCTP under FreeBSD
> - - About summer 2003: Implementation of ENRP
> 
> 
> 
>>-Anything else you would like to add
> 
> 
> For more information about our implementation, see 
> http://tdrwww.exp-math.uni-essen.de/dreibholz/rserpool/ and 
> http://www.sctp.de/rserpool.html. An introduction to design and 
> implementation of our rsplib prototype is given in our paper at 
> http://tdrwww.exp-math.uni-essen.de/dreibholz/rserpool/#Research. It has been 
> presented by me at the Linux Conference Australia 2003.
> 
> 
> 
>>I'll be making some remarks about the various implementation efforts at
>>the IETF 56 meeting in San Francisco.
> 
> 
> Please send me a copy of your remarks. I am very interested who else is 
> implementing RSerPool.
> 
> 
> Best regards
> - -- 
> =======================================================================
>  Dipl.-Inform. Thomas Dreibholz
>  Molbachweg 7
>  D-51674 Wiehl-Forst    Mail: dreibh@exp-math.uni-essen.de
>  Germany                WWW:  http://www.exp-math.uni-essen.de/~dreibh
> =======================================================================
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.0.6 (GNU/Linux)
> Comment: For info see http://www.gnupg.org
> 
> iD8DBQE+Z65x32BbsHYPLWURAmcRAJ0Vy8eT+sBKIiUdfxuSj+by3kfmcgCggQ3f
> aoFUZeVcv3ZNb8HoVDe/Ut8=
> =FWgK
> -----END PGP SIGNATURE-----
> 
> 


-- 
Aron J. Silverton
Senior Staff Research Engineer
Motorola Laboratories, Networks and Infrastructure Research
Motorola, Inc.

Telephone: 847-576-8747
Fax: 847-576-3240
mailto: ajs@labs.mot.com

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



From rserpool-admin@ietf.org  Tue Mar 11 18:16:41 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 SAA17982
	for <rserpool-archive@lists.ietf.org>; Tue, 11 Mar 2003 18:16:41 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2BNUAO10356;
	Tue, 11 Mar 2003 18:30:10 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2BNTiO10326
	for <rserpool@optimus.ietf.org>; Tue, 11 Mar 2003 18:29:44 -0500
Received: from motgate4.mot.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA17878
	for <rserpool@ietf.org>; Tue, 11 Mar 2003 18:15:29 -0500 (EST)
Received: from pobox3.mot.com (pobox3.mot.com [10.64.251.242])
	by motgate4.mot.com (Motorola/Motgate4) with ESMTP id h2BNHXZj010432
	for <rserpool@ietf.org>; Tue, 11 Mar 2003 16:17:33 -0700 (MST)
Received: [from il27exb01.cig.mot.com (il27exb01.cig.mot.com [136.182.15.100]) by pobox3.mot.com (MOT-pobox3 2.0) with ESMTP id QAA03013 for <rserpool@ietf.org>; Tue, 11 Mar 2003 16:15:37 -0700 (MST)]
Received: from motorola.com (d50-38cd.cig.mot.com [160.47.56.205]) by il27exb01.cig.mot.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2656.59)
	id WD6N52H8; Tue, 11 Mar 2003 17:16:47 -0600
Message-ID: <3E6E6AA5.DE56290B@motorola.com>
Date: Tue, 11 Mar 2003 17:00:53 -0600
From: Qiaobing Xie <Qiaobing.Xie@motorola.com>
X-Mailer: Mozilla 4.8 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Rserpool <rserpool@ietf.org>
CC: "Randall Stewart (cisco)" <rrs@cisco.com>,
        Maureen Stillman <Maureen.Stillman@nokia.com>,
        "Michael Tuexen (at home)" <micmac@ilsa.franken.de>,
        "Michael Tuexen (at work)" <Michael.Tuexen@icn.siemens.de>
References: <3E662E44.3080704@cisco.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Rserpool] Re: Message channel issues
Sender: rserpool-admin@ietf.org
Errors-To: rserpool-admin@ietf.org
X-BeenThere: rserpool@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=unsubscribe>
List-Id: Reliable Server Pooling <rserpool.ietf.org>
List-Post: <mailto:rserpool@ietf.org>
List-Help: <mailto:rserpool-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Hi, all,

When we started to consider defining a control channel at our interim
meeting (1.5 year ago?), it was thought to be a small addition to the
architecture that would allow the passing of a few optional messages
(buz-card, cookie, etc.). The use of these messages were more meant to
somehow enhance the functionality of RSERPOOL. Now it seems that this
creature is growing rapidly in terms of architectural impact and
complexity. Maybe it's time for us to do a sanity check and re-visit how
much we can gain from this and what we are going to pay for it.

>From the design's perspective, the main thing in the current proposal is
to try to bring the control channel from PE-PU communication link into a
separate entity. This IMHO could have a big implication to RSERPOOL and
raises a lot of open issues. In the following, I will pose a serious of
questions for us to think about.

"Randall Stewart (cisco)" wrote:
> 
> Hi all:
> 
> I was asked to summarize the message channel issue and put out
> one of the solutions (and one other issue) we discussed on yesterdays
> conference call.
> 
> -------------------------
> Issue #1
> -------------------------
> The basic issue is this:
>

Keep in mind that currently we allow a PE to register with 1 or more
transport addresses of diff types (e.g., a PE is _allowed_ to reg with
sctp-trans1, sctp-trans2, tcp-trans, udp-trans1, udp-trans2), and we
have of cause 1 or more PEs in any given pool.
 
> 1) A PE may register a Control channel, Data Channel or Both (in a combined
>     form or seperate).

- A founding principle of RSERPOOL is that all PEs in a pool are
"functionally identical" while "maybe capability-wise different". If we
start to introduce "control-only PEs" via "data-only PEs" via
"control/data PEs" in the same pool, we need to understand the
implications and why we need this complexity. For example, can you
failover from a control-only PE to a data-only PE? What does that mean?

- How does the load sharing should be understood in this picture? I.e.,
can one round robin amongst a mixed set of data-only and data-control
PEs? What's the implication here?

- Are we going to allow a PE to reg as "control channel only"? I'd
strongly advice against that since it seems to be meaningless and should
be disallowed, IMO. After all Rserpool is in the business of moving user
data and I don't see why a PE is useful being control-only.

- It must be made clear that unreachability detection must be tied to
the data side. Otherwise, the redundancy becomes meaningless (e.g., what
if a PE becomes unreachable on its data side while its control side is
still functioning?). Question is how to make sure this happens?

- In a related issue, what if a PE become unreachable over its control
channel while its data channel is ok? We should define what this means.
Should we monitor reachability of control channel at the first place? If
so, how?

- When a PE registers with >1 transports (of maybe mixed types among
SCTP, TCP, UDP), how the control and data channel map to that? Can it do
things like reg[sctp1/control-only, sctp2/control-and-data,
tcp/data-only]? If not, what'are the restrictions and how to enforce
them? If allowed, how those mixed PEs are going to behave in terms of
failover and load sharing (see below also)?

- How the failover will work now? Can a PU failover from a control/data
PE to a data only PE? Or, should we force all PEs in a pool to have the
same control/data config? 

I can go on and on with this type of questions... there are so many
combinations here. And I can imagine it's going to be very expensive to
design and implement them all in RSERPOOL. We really need to understand
why we need each of them before we decide to build it into RSERPOOL. 

As I mentioned above, most of the issues above arise from the fact
that we are now trying to bring the control channel from PE-PU
communication link into a separate entity. One alternate approach would
be to keep the control channel bundled with data channel. This would
solve a lot of issues mentioned above. By this, I mean basically that we
keep our focus on data side and only allow to have a control channel if
the data side is over SCTP (using PPID to mux) or TCP (using mapping to
mux). This is simply and its impact to architecture is little to none.
This also automatically solves the problem of tying control and data.

regards,
-Qiaobing


> 2) If the PE register's a Data channel and a control channel (non-combined) then
>     how does the PE make the association between the PU talking on the two
>     differerent channels?
> 
> Suppose The PU associates with the Data Channel of a PE... Then at
> some point decides to use the Control Channel.. for the PE a message
> arrives on the Control channel and there is no tie back to the conversation
> on the data channel?
> 
> Or suppose the control channel is first associated with, followed by
> the data channel.. how does the PE make the connection..
> 
> One of the proposed solutions we discussed and thought worth considering (to make
> sure we have covered all the bases) is:
> 
> 1) Require that if a PE has both a control and data channel that the PU ALWAYs associate
>    to the Control channel and send a Bussiness card specifying itself.
> 
> 2) The business card will need to be changed so that we can identify that this is a PU only
>    address.
> 
> 3) The PU would need to supply all of the addresses to the PE for its side of the Data channel so
>    if it has two communication endpoints up (SCTP/control and TCP/data for example) it would place
>    in its B-C a indication of the TCP channel id (port/ip address etc) and mark it as "Data channel
>    only, will not accept connections". The SCTP information could be deduced from the
>    association.
> 
> With this proposal we would eliminate the new message that was just added. Expand the
> types that was just added to asap (for TCP and SCTP endpoints) and finally enhance the
> wording of the business card and require that ... if a Control channel exists the PU MUST
> connect and pass its B-C... or something like that.
> 
> ---------------
> Issue #2
> ---------------
> 
> The basic issue:
> 
> There are many possiblities of combinations of Data and Control
> channels.. do we need to have some sort of restrictions on these... here is a table I have
> put together showing the possibilites
> 
> Control Channel Type          |             Data Channel Type
> ------------------------------+--------------------------------------------------------
>   SCTP                        |               SCTP - Multiplexed - same association
> ------------------------------+--------------------------------------------------------
>   SCTP                        |               SCTP - Seperate assocaition
> ------------------------------+--------------------------------------------------------
>   SCTP                        |              TCP
> ------------------------------+--------------------------------------------------------
>   SCTP                        |               UDP
> ------------------------------+--------------------------------------------------------
>   TCP                         |               SCTP
> ------------------------------+--------------------------------------------------------
>   TCP                         |               TCP - Seperate connection
> ------------------------------+--------------------------------------------------------
>   TCP                         |                TCP - Multiplexed - same connection
> ------------------------------+--------------------------------------------------------
>   TCP                         |               UDP
> ------------------------------+--------------------------------------------------------
> 
> So we basically have eight different combinations.. if I have gotten them all
> (remember UDP is not allowed for the control channel)...
> 
> So the question is.. should some limitations be placed on the allowable combinations?
> 
> Thanks
> 
> R
> 
> --
> Randall R. Stewart
> ITD
> Cisco Systems Inc.
> rrs@cisco.com 815-342-5222(cell) or 815-477-2127(office)

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


From mailnull@www1.ietf.org  Tue Mar 11 18:17:12 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 SAA18043
	for <rserpool-archive@odin.ietf.org>; Tue, 11 Mar 2003 18:17:11 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2BNUqt10399
	for rserpool-archive@odin.ietf.org; Tue, 11 Mar 2003 18:30:52 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2BNUAO10356;
	Tue, 11 Mar 2003 18:30:10 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2BNTiO10326
	for <rserpool@optimus.ietf.org>; Tue, 11 Mar 2003 18:29:44 -0500
Received: from motgate4.mot.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA17878
	for <rserpool@ietf.org>; Tue, 11 Mar 2003 18:15:29 -0500 (EST)
Received: from pobox3.mot.com (pobox3.mot.com [10.64.251.242])
	by motgate4.mot.com (Motorola/Motgate4) with ESMTP id h2BNHXZj010432
	for <rserpool@ietf.org>; Tue, 11 Mar 2003 16:17:33 -0700 (MST)
Received: [from il27exb01.cig.mot.com (il27exb01.cig.mot.com [136.182.15.100]) by pobox3.mot.com (MOT-pobox3 2.0) with ESMTP id QAA03013 for <rserpool@ietf.org>; Tue, 11 Mar 2003 16:15:37 -0700 (MST)]
Received: from motorola.com (d50-38cd.cig.mot.com [160.47.56.205]) by il27exb01.cig.mot.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2656.59)
	id WD6N52H8; Tue, 11 Mar 2003 17:16:47 -0600
Message-ID: <3E6E6AA5.DE56290B@motorola.com>
Date: Tue, 11 Mar 2003 17:00:53 -0600
From: Qiaobing Xie <Qiaobing.Xie@motorola.com>
X-Mailer: Mozilla 4.8 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Rserpool <rserpool@ietf.org>
CC: "Randall Stewart (cisco)" <rrs@cisco.com>,
        Maureen Stillman <Maureen.Stillman@nokia.com>,
        "Michael Tuexen (at home)" <micmac@ilsa.franken.de>,
        "Michael Tuexen (at work)" <Michael.Tuexen@icn.siemens.de>
References: <3E662E44.3080704@cisco.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Rserpool] Re: Message channel issues
Sender: rserpool-admin@ietf.org
Errors-To: rserpool-admin@ietf.org
X-BeenThere: rserpool@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=unsubscribe>
List-Id: Reliable Server Pooling <rserpool.ietf.org>
List-Post: <mailto:rserpool@ietf.org>
List-Help: <mailto:rserpool-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Hi, all,

When we started to consider defining a control channel at our interim
meeting (1.5 year ago?), it was thought to be a small addition to the
architecture that would allow the passing of a few optional messages
(buz-card, cookie, etc.). The use of these messages were more meant to
somehow enhance the functionality of RSERPOOL. Now it seems that this
creature is growing rapidly in terms of architectural impact and
complexity. Maybe it's time for us to do a sanity check and re-visit how
much we can gain from this and what we are going to pay for it.

>From the design's perspective, the main thing in the current proposal is
to try to bring the control channel from PE-PU communication link into a
separate entity. This IMHO could have a big implication to RSERPOOL and
raises a lot of open issues. In the following, I will pose a serious of
questions for us to think about.

"Randall Stewart (cisco)" wrote:
> 
> Hi all:
> 
> I was asked to summarize the message channel issue and put out
> one of the solutions (and one other issue) we discussed on yesterdays
> conference call.
> 
> -------------------------
> Issue #1
> -------------------------
> The basic issue is this:
>

Keep in mind that currently we allow a PE to register with 1 or more
transport addresses of diff types (e.g., a PE is _allowed_ to reg with
sctp-trans1, sctp-trans2, tcp-trans, udp-trans1, udp-trans2), and we
have of cause 1 or more PEs in any given pool.
 
> 1) A PE may register a Control channel, Data Channel or Both (in a combined
>     form or seperate).

- A founding principle of RSERPOOL is that all PEs in a pool are
"functionally identical" while "maybe capability-wise different". If we
start to introduce "control-only PEs" via "data-only PEs" via
"control/data PEs" in the same pool, we need to understand the
implications and why we need this complexity. For example, can you
failover from a control-only PE to a data-only PE? What does that mean?

- How does the load sharing should be understood in this picture? I.e.,
can one round robin amongst a mixed set of data-only and data-control
PEs? What's the implication here?

- Are we going to allow a PE to reg as "control channel only"? I'd
strongly advice against that since it seems to be meaningless and should
be disallowed, IMO. After all Rserpool is in the business of moving user
data and I don't see why a PE is useful being control-only.

- It must be made clear that unreachability detection must be tied to
the data side. Otherwise, the redundancy becomes meaningless (e.g., what
if a PE becomes unreachable on its data side while its control side is
still functioning?). Question is how to make sure this happens?

- In a related issue, what if a PE become unreachable over its control
channel while its data channel is ok? We should define what this means.
Should we monitor reachability of control channel at the first place? If
so, how?

- When a PE registers with >1 transports (of maybe mixed types among
SCTP, TCP, UDP), how the control and data channel map to that? Can it do
things like reg[sctp1/control-only, sctp2/control-and-data,
tcp/data-only]? If not, what'are the restrictions and how to enforce
them? If allowed, how those mixed PEs are going to behave in terms of
failover and load sharing (see below also)?

- How the failover will work now? Can a PU failover from a control/data
PE to a data only PE? Or, should we force all PEs in a pool to have the
same control/data config? 

I can go on and on with this type of questions... there are so many
combinations here. And I can imagine it's going to be very expensive to
design and implement them all in RSERPOOL. We really need to understand
why we need each of them before we decide to build it into RSERPOOL. 

As I mentioned above, most of the issues above arise from the fact
that we are now trying to bring the control channel from PE-PU
communication link into a separate entity. One alternate approach would
be to keep the control channel bundled with data channel. This would
solve a lot of issues mentioned above. By this, I mean basically that we
keep our focus on data side and only allow to have a control channel if
the data side is over SCTP (using PPID to mux) or TCP (using mapping to
mux). This is simply and its impact to architecture is little to none.
This also automatically solves the problem of tying control and data.

regards,
-Qiaobing


> 2) If the PE register's a Data channel and a control channel (non-combined) then
>     how does the PE make the association between the PU talking on the two
>     differerent channels?
> 
> Suppose The PU associates with the Data Channel of a PE... Then at
> some point decides to use the Control Channel.. for the PE a message
> arrives on the Control channel and there is no tie back to the conversation
> on the data channel?
> 
> Or suppose the control channel is first associated with, followed by
> the data channel.. how does the PE make the connection..
> 
> One of the proposed solutions we discussed and thought worth considering (to make
> sure we have covered all the bases) is:
> 
> 1) Require that if a PE has both a control and data channel that the PU ALWAYs associate
>    to the Control channel and send a Bussiness card specifying itself.
> 
> 2) The business card will need to be changed so that we can identify that this is a PU only
>    address.
> 
> 3) The PU would need to supply all of the addresses to the PE for its side of the Data channel so
>    if it has two communication endpoints up (SCTP/control and TCP/data for example) it would place
>    in its B-C a indication of the TCP channel id (port/ip address etc) and mark it as "Data channel
>    only, will not accept connections". The SCTP information could be deduced from the
>    association.
> 
> With this proposal we would eliminate the new message that was just added. Expand the
> types that was just added to asap (for TCP and SCTP endpoints) and finally enhance the
> wording of the business card and require that ... if a Control channel exists the PU MUST
> connect and pass its B-C... or something like that.
> 
> ---------------
> Issue #2
> ---------------
> 
> The basic issue:
> 
> There are many possiblities of combinations of Data and Control
> channels.. do we need to have some sort of restrictions on these... here is a table I have
> put together showing the possibilites
> 
> Control Channel Type          |             Data Channel Type
> ------------------------------+--------------------------------------------------------
>   SCTP                        |               SCTP - Multiplexed - same association
> ------------------------------+--------------------------------------------------------
>   SCTP                        |               SCTP - Seperate assocaition
> ------------------------------+--------------------------------------------------------
>   SCTP                        |              TCP
> ------------------------------+--------------------------------------------------------
>   SCTP                        |               UDP
> ------------------------------+--------------------------------------------------------
>   TCP                         |               SCTP
> ------------------------------+--------------------------------------------------------
>   TCP                         |               TCP - Seperate connection
> ------------------------------+--------------------------------------------------------
>   TCP                         |                TCP - Multiplexed - same connection
> ------------------------------+--------------------------------------------------------
>   TCP                         |               UDP
> ------------------------------+--------------------------------------------------------
> 
> So we basically have eight different combinations.. if I have gotten them all
> (remember UDP is not allowed for the control channel)...
> 
> So the question is.. should some limitations be placed on the allowable combinations?
> 
> Thanks
> 
> R
> 
> --
> Randall R. Stewart
> ITD
> Cisco Systems Inc.
> rrs@cisco.com 815-342-5222(cell) or 815-477-2127(office)

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



From rserpool-admin@ietf.org  Tue Mar 11 18:35:32 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 SAA18636
	for <rserpool-archive@lists.ietf.org>; Tue, 11 Mar 2003 18:35:31 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2BNn2O12019;
	Tue, 11 Mar 2003 18:49:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h24CeLp31961
	for <rserpool@optimus.ietf.org>; Tue, 4 Mar 2003 07:40:21 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA14876;
	Tue, 4 Mar 2003 07:29:24 -0500 (EST)
Message-Id: <200303041229.HAA14876@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: rserpool@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Date: Tue, 04 Mar 2003 07:29:24 -0500
Subject: [Rserpool] I-D ACTION:draft-ietf-rserpool-asap-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: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=unsubscribe>
List-Id: Reliable Server Pooling <rserpool.ietf.org>
List-Post: <mailto:rserpool@ietf.org>
List-Help: <mailto:rserpool-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=subscribe>

--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-06.txt
	Pages		: 42
	Date		: 2003-3-3
	
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-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-asap-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-asap-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-3-3145003.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-rserpool-asap-06.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-rserpool-asap-06.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<2003-3-3145003.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 Mar 11 18:35:32 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 SAA18642
	for <rserpool-archive@lists.ietf.org>; Tue, 11 Mar 2003 18:35:32 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2BNn3O12050;
	Tue, 11 Mar 2003 18:49:03 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h25HEl515956
	for <rserpool@optimus.ietf.org>; Wed, 5 Mar 2003 12:14:47 -0500
Received: from sj-core-2.cisco.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA13163
	for <rserpool@ietf.org>; Wed, 5 Mar 2003 12:03:12 -0500 (EST)
Received: from mira-sjc5-c.cisco.com (IDENT:mirapoint@mira-sjc5-c.cisco.com [171.71.163.17])
	by sj-core-2.cisco.com (8.12.6/8.12.6) with ESMTP id h25H593D012858;
	Wed, 5 Mar 2003 09:05:09 -0800 (PST)
Received: from cisco.com (ssh-sjc-1.cisco.com [171.68.225.134])
	by mira-sjc5-c.cisco.com (Mirapoint Messaging Server MOS 3.2.1-GA)
	with ESMTP id AEC96940;
	Wed, 5 Mar 2003 09:05:08 -0800 (PST)
Message-ID: <3E662E44.3080704@cisco.com>
Date: Wed, 05 Mar 2003 11:05:08 -0600
From: "Randall Stewart (cisco)" <rrs@cisco.com>
User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.1) Gecko/20021005
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Rserpool <rserpool@ietf.org>
CC: Maureen Stillman <Maureen.Stillman@nokia.com>,
        Qiaobing Xie <qxie1@email.mot.com>,
        "Michael Tuexen (at home)" <micmac@ilsa.franken.de>,
        "Michael Tuexen (at work)" <Michael.Tuexen@icn.siemens.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Rserpool] Message channel issues
Sender: rserpool-admin@ietf.org
Errors-To: rserpool-admin@ietf.org
X-BeenThere: rserpool@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=unsubscribe>
List-Id: Reliable Server Pooling <rserpool.ietf.org>
List-Post: <mailto:rserpool@ietf.org>
List-Help: <mailto:rserpool-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Hi all:

I was asked to summarize the message channel issue and put out
one of the solutions (and one other issue) we discussed on yesterdays 
conference call.

-------------------------
Issue #1
-------------------------
The basic issue is this:

1) A PE may register a Control channel, Data Channel or Both (in a combined
    form or seperate).
2) If the PE register's a Data channel and a control channel 
(non-combined) then
    how does the PE make the association between the PU talking on the two
    differerent channels?

Suppose The PU associates with the Data Channel of a PE... Then at
some point decides to use the Control Channel.. for the PE a message
arrives on the Control channel and there is no tie back to the conversation
on the data channel?

Or suppose the control channel is first associated with, followed by
the data channel.. how does the PE make the connection..

One of the proposed solutions we discussed and thought worth considering 
(to make
sure we have covered all the bases) is:

1) Require that if a PE has both a control and data channel that the PU 
ALWAYs associate
    to the Control channel and send a Bussiness card specifying itself.

2) The business card will need to be changed so that we can identify 
that this is a PU only
     address.

3) The PU would need to supply all of the addresses to the PE for its 
side of the Data channel so
     if it has two communication endpoints up (SCTP/control and TCP/data 
for example) it would place
     in its B-C a indication of the TCP channel id (port/ip address etc) 
and mark it as "Data channel
     only, will not accept connections". The SCTP information could be 
deduced from the
     association.

With this proposal we would eliminate the new message that was just 
added. Expand the
types that was just added to asap (for TCP and SCTP endpoints) and 
finally enhance the
wording of the business card and require that ... if a Control channel 
exists the PU MUST
connect and pass its B-C... or something like that.

---------------
Issue #2
---------------

The basic issue:

There are many possiblities of combinations of Data and Control 
channels.. do we
need to have some sort of restrictions on these... here is a table I have
put together showing the possibilites

Control Channel Type  |             Data Channel Type
------------------------------+--------------------------------------------------------
  SCTP                           |               SCTP - Multiplexed - 
same association
------------------------------+--------------------------------------------------------
  SCTP                           |               SCTP - Seperate assocaition
------------------------------+--------------------------------------------------------
  SCTP                           |              TCP
------------------------------+--------------------------------------------------------
  SCTP                           |               UDP
------------------------------+--------------------------------------------------------
  TCP                             |               SCTP
------------------------------+--------------------------------------------------------
  TCP                             |               TCP - Seperate connection
------------------------------+--------------------------------------------------------
  TCP                             |                TCP - Multiplexed - 
same connection
------------------------------+--------------------------------------------------------
  TCP                             |               UDP
------------------------------+--------------------------------------------------------
 
So we basically have eight different combinations.. if I have gotten 
them all
(remember UDP is not allowed for the control channel)...

So the question is.. should some limitations be placed on the
allowable combinations?

Thanks

R

-- 
Randall R. Stewart
ITD
Cisco Systems Inc.
rrs@cisco.com 815-342-5222(cell) or 815-477-2127(office)


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


From rserpool-admin@ietf.org  Tue Mar 11 18:35:32 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 SAA18638
	for <rserpool-archive@lists.ietf.org>; Tue, 11 Mar 2003 18:35:32 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2BNn2O12035;
	Tue, 11 Mar 2003 18:49:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h24CeQp31966
	for <rserpool@optimus.ietf.org>; Tue, 4 Mar 2003 07:40:26 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA14897;
	Tue, 4 Mar 2003 07:29:28 -0500 (EST)
Message-Id: <200303041229.HAA14897@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: rserpool@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Date: Tue, 04 Mar 2003 07:29:28 -0500
Subject: [Rserpool] I-D ACTION:draft-ietf-rserpool-common-param-03.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: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=unsubscribe>
List-Id: Reliable Server Pooling <rserpool.ietf.org>
List-Post: <mailto:rserpool@ietf.org>
List-Help: <mailto:rserpool-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=subscribe>

--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) common parameters document
	Author(s)	: R. Stewart, Q. Xie et al.
	Filename	: draft-ietf-rserpool-common-param-03.txt
	Pages		: 26
	Date		: 2003-3-3
	
Aggregate Server Access Protocol (ASAP) [4] in conjunction with the
Endpoint Name Resolution Protocol (ENRP) [5] provides a high
availability data transfer mechanism over IP networks.
Both protocols work together and so share many common parameters used
in message formats.  This document details the common message
parameters shared between the two protocols.  This document provides
parameter formats only, for procedures and message composition please
refer to the respective ASAP [4] and ENRP [5] documents.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-rserpool-common-param-03.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-03.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-03.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-3-3145012.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-rserpool-common-param-03.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-rserpool-common-param-03.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<2003-3-3145012.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 Mar 11 18:35:33 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 SAA18662
	for <rserpool-archive@lists.ietf.org>; Tue, 11 Mar 2003 18:35:33 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2BNn3O12071;
	Tue, 11 Mar 2003 18:49:03 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h26BeMO26633
	for <rserpool@optimus.ietf.org>; Thu, 6 Mar 2003 06:40:23 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA03381;
	Thu, 6 Mar 2003 06:28:52 -0500 (EST)
Message-Id: <200303061128.GAA03381@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: rserpool@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Date: Thu, 06 Mar 2003 06:28:52 -0500
Subject: [Rserpool] I-D ACTION:draft-ietf-rserpool-enrp-05.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: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=unsubscribe>
List-Id: Reliable Server Pooling <rserpool.ietf.org>
List-Post: <mailto:rserpool@ietf.org>
List-Help: <mailto:rserpool-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=subscribe>

--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-05.txt
	Pages		: 42
	Date		: 2003-3-5
	
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-05.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-05.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-05.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-3-5141209.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-rserpool-enrp-05.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-rserpool-enrp-05.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<2003-3-5141209.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 Mar 11 18:35:34 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 SAA18694
	for <rserpool-archive@lists.ietf.org>; Tue, 11 Mar 2003 18:35:34 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2BNn4O12086;
	Tue, 11 Mar 2003 18:49:04 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h27KnJO05941
	for <rserpool@optimus.ietf.org>; Fri, 7 Mar 2003 15:49:19 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA29669;
	Fri, 7 Mar 2003 15:37:08 -0500 (EST)
Message-Id: <200303072037.PAA29669@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: rserpool@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Date: Fri, 07 Mar 2003 15:37:07 -0500
Subject: [Rserpool] I-D ACTION:draft-ietf-rserpool-arch-05.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: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=unsubscribe>
List-Id: Reliable Server Pooling <rserpool.ietf.org>
List-Post: <mailto:rserpool@ietf.org>
List-Help: <mailto:rserpool-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=subscribe>

--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-05.txt
	Pages		: 22
	Date		: 2003-3-7
	
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-05.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-05.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-05.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-3-7151641.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-rserpool-arch-05.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-rserpool-arch-05.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<2003-3-7151641.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 Mar 11 18:36: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 SAA18726
	for <rserpool-archive@odin.ietf.org>; Tue, 11 Mar 2003 18:36:02 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2BNnhf12128
	for rserpool-archive@odin.ietf.org; Tue, 11 Mar 2003 18:49:43 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2BNn2O12019;
	Tue, 11 Mar 2003 18:49:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h24CeLp31961
	for <rserpool@optimus.ietf.org>; Tue, 4 Mar 2003 07:40:21 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA14876;
	Tue, 4 Mar 2003 07:29:24 -0500 (EST)
Message-Id: <200303041229.HAA14876@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: rserpool@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Date: Tue, 04 Mar 2003 07:29:24 -0500
Subject: [Rserpool] I-D ACTION:draft-ietf-rserpool-asap-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: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=unsubscribe>
List-Id: Reliable Server Pooling <rserpool.ietf.org>
List-Post: <mailto:rserpool@ietf.org>
List-Help: <mailto:rserpool-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=subscribe>

--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-06.txt
	Pages		: 42
	Date		: 2003-3-3
	
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-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-asap-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-asap-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-3-3145003.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-rserpool-asap-06.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-rserpool-asap-06.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<2003-3-3145003.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 Mar 11 18:36: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 SAA18728
	for <rserpool-archive@odin.ietf.org>; Tue, 11 Mar 2003 18:36:02 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2BNnhj12141
	for rserpool-archive@odin.ietf.org; Tue, 11 Mar 2003 18:49:43 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2BNn2O12035;
	Tue, 11 Mar 2003 18:49:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h24CeQp31966
	for <rserpool@optimus.ietf.org>; Tue, 4 Mar 2003 07:40:26 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA14897;
	Tue, 4 Mar 2003 07:29:28 -0500 (EST)
Message-Id: <200303041229.HAA14897@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: rserpool@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Date: Tue, 04 Mar 2003 07:29:28 -0500
Subject: [Rserpool] I-D ACTION:draft-ietf-rserpool-common-param-03.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: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=unsubscribe>
List-Id: Reliable Server Pooling <rserpool.ietf.org>
List-Post: <mailto:rserpool@ietf.org>
List-Help: <mailto:rserpool-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=subscribe>

--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) common parameters document
	Author(s)	: R. Stewart, Q. Xie et al.
	Filename	: draft-ietf-rserpool-common-param-03.txt
	Pages		: 26
	Date		: 2003-3-3
	
Aggregate Server Access Protocol (ASAP) [4] in conjunction with the
Endpoint Name Resolution Protocol (ENRP) [5] provides a high
availability data transfer mechanism over IP networks.
Both protocols work together and so share many common parameters used
in message formats.  This document details the common message
parameters shared between the two protocols.  This document provides
parameter formats only, for procedures and message composition please
refer to the respective ASAP [4] and ENRP [5] documents.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-rserpool-common-param-03.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-03.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-03.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-3-3145012.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-rserpool-common-param-03.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-rserpool-common-param-03.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<2003-3-3145012.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 Mar 11 18:36: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 SAA18736
	for <rserpool-archive@odin.ietf.org>; Tue, 11 Mar 2003 18:36:03 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2BNnhu12154
	for rserpool-archive@odin.ietf.org; Tue, 11 Mar 2003 18:49:43 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2BNn3O12050;
	Tue, 11 Mar 2003 18:49:03 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h25HEl515956
	for <rserpool@optimus.ietf.org>; Wed, 5 Mar 2003 12:14:47 -0500
Received: from sj-core-2.cisco.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA13163
	for <rserpool@ietf.org>; Wed, 5 Mar 2003 12:03:12 -0500 (EST)
Received: from mira-sjc5-c.cisco.com (IDENT:mirapoint@mira-sjc5-c.cisco.com [171.71.163.17])
	by sj-core-2.cisco.com (8.12.6/8.12.6) with ESMTP id h25H593D012858;
	Wed, 5 Mar 2003 09:05:09 -0800 (PST)
Received: from cisco.com (ssh-sjc-1.cisco.com [171.68.225.134])
	by mira-sjc5-c.cisco.com (Mirapoint Messaging Server MOS 3.2.1-GA)
	with ESMTP id AEC96940;
	Wed, 5 Mar 2003 09:05:08 -0800 (PST)
Message-ID: <3E662E44.3080704@cisco.com>
Date: Wed, 05 Mar 2003 11:05:08 -0600
From: "Randall Stewart (cisco)" <rrs@cisco.com>
User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.1) Gecko/20021005
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Rserpool <rserpool@ietf.org>
CC: Maureen Stillman <Maureen.Stillman@nokia.com>,
        Qiaobing Xie <qxie1@email.mot.com>,
        "Michael Tuexen (at home)" <micmac@ilsa.franken.de>,
        "Michael Tuexen (at work)" <Michael.Tuexen@icn.siemens.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Rserpool] Message channel issues
Sender: rserpool-admin@ietf.org
Errors-To: rserpool-admin@ietf.org
X-BeenThere: rserpool@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=unsubscribe>
List-Id: Reliable Server Pooling <rserpool.ietf.org>
List-Post: <mailto:rserpool@ietf.org>
List-Help: <mailto:rserpool-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Hi all:

I was asked to summarize the message channel issue and put out
one of the solutions (and one other issue) we discussed on yesterdays 
conference call.

-------------------------
Issue #1
-------------------------
The basic issue is this:

1) A PE may register a Control channel, Data Channel or Both (in a combined
    form or seperate).
2) If the PE register's a Data channel and a control channel 
(non-combined) then
    how does the PE make the association between the PU talking on the two
    differerent channels?

Suppose The PU associates with the Data Channel of a PE... Then at
some point decides to use the Control Channel.. for the PE a message
arrives on the Control channel and there is no tie back to the conversation
on the data channel?

Or suppose the control channel is first associated with, followed by
the data channel.. how does the PE make the connection..

One of the proposed solutions we discussed and thought worth considering 
(to make
sure we have covered all the bases) is:

1) Require that if a PE has both a control and data channel that the PU 
ALWAYs associate
    to the Control channel and send a Bussiness card specifying itself.

2) The business card will need to be changed so that we can identify 
that this is a PU only
     address.

3) The PU would need to supply all of the addresses to the PE for its 
side of the Data channel so
     if it has two communication endpoints up (SCTP/control and TCP/data 
for example) it would place
     in its B-C a indication of the TCP channel id (port/ip address etc) 
and mark it as "Data channel
     only, will not accept connections". The SCTP information could be 
deduced from the
     association.

With this proposal we would eliminate the new message that was just 
added. Expand the
types that was just added to asap (for TCP and SCTP endpoints) and 
finally enhance the
wording of the business card and require that ... if a Control channel 
exists the PU MUST
connect and pass its B-C... or something like that.

---------------
Issue #2
---------------

The basic issue:

There are many possiblities of combinations of Data and Control 
channels.. do we
need to have some sort of restrictions on these... here is a table I have
put together showing the possibilites

Control Channel Type  |             Data Channel Type
------------------------------+--------------------------------------------------------
  SCTP                           |               SCTP - Multiplexed - 
same association
------------------------------+--------------------------------------------------------
  SCTP                           |               SCTP - Seperate assocaition
------------------------------+--------------------------------------------------------
  SCTP                           |              TCP
------------------------------+--------------------------------------------------------
  SCTP                           |               UDP
------------------------------+--------------------------------------------------------
  TCP                             |               SCTP
------------------------------+--------------------------------------------------------
  TCP                             |               TCP - Seperate connection
------------------------------+--------------------------------------------------------
  TCP                             |                TCP - Multiplexed - 
same connection
------------------------------+--------------------------------------------------------
  TCP                             |               UDP
------------------------------+--------------------------------------------------------
 
So we basically have eight different combinations.. if I have gotten 
them all
(remember UDP is not allowed for the control channel)...

So the question is.. should some limitations be placed on the
allowable combinations?

Thanks

R

-- 
Randall R. Stewart
ITD
Cisco Systems Inc.
rrs@cisco.com 815-342-5222(cell) or 815-477-2127(office)


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



From mailnull@www1.ietf.org  Tue Mar 11 18:36:04 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 SAA18762
	for <rserpool-archive@odin.ietf.org>; Tue, 11 Mar 2003 18:36:04 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2BNniF12167
	for rserpool-archive@odin.ietf.org; Tue, 11 Mar 2003 18:49:44 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2BNn3O12071;
	Tue, 11 Mar 2003 18:49:03 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h26BeMO26633
	for <rserpool@optimus.ietf.org>; Thu, 6 Mar 2003 06:40:23 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA03381;
	Thu, 6 Mar 2003 06:28:52 -0500 (EST)
Message-Id: <200303061128.GAA03381@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: rserpool@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Date: Thu, 06 Mar 2003 06:28:52 -0500
Subject: [Rserpool] I-D ACTION:draft-ietf-rserpool-enrp-05.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: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=unsubscribe>
List-Id: Reliable Server Pooling <rserpool.ietf.org>
List-Post: <mailto:rserpool@ietf.org>
List-Help: <mailto:rserpool-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=subscribe>

--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-05.txt
	Pages		: 42
	Date		: 2003-3-5
	
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-05.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-05.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-05.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-3-5141209.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-rserpool-enrp-05.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-rserpool-enrp-05.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<2003-3-5141209.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 Mar 11 18:36:05 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 SAA18778
	for <rserpool-archive@odin.ietf.org>; Tue, 11 Mar 2003 18:36:05 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2BNnjR12180
	for rserpool-archive@odin.ietf.org; Tue, 11 Mar 2003 18:49:45 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2BNn4O12086;
	Tue, 11 Mar 2003 18:49:04 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h27KnJO05941
	for <rserpool@optimus.ietf.org>; Fri, 7 Mar 2003 15:49:19 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA29669;
	Fri, 7 Mar 2003 15:37:08 -0500 (EST)
Message-Id: <200303072037.PAA29669@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: rserpool@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Date: Fri, 07 Mar 2003 15:37:07 -0500
Subject: [Rserpool] I-D ACTION:draft-ietf-rserpool-arch-05.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: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=unsubscribe>
List-Id: Reliable Server Pooling <rserpool.ietf.org>
List-Post: <mailto:rserpool@ietf.org>
List-Help: <mailto:rserpool-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=subscribe>

--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-05.txt
	Pages		: 22
	Date		: 2003-3-7
	
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-05.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-05.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-05.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-3-7151641.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-rserpool-arch-05.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-rserpool-arch-05.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<2003-3-7151641.I-D@ietf.org>

--OtherAccess--

--NextPart--


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



From rserpool-admin@ietf.org  Thu Mar 13 07:43:22 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 HAA28447
	for <rserpool-archive@lists.ietf.org>; Thu, 13 Mar 2003 07:43:22 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2DCvYO23272;
	Thu, 13 Mar 2003 07:57:34 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2DCuIO23229
	for <rserpool@optimus.ietf.org>; Thu, 13 Mar 2003 07:56:18 -0500
Received: from stewart.chicago.il.us (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA28366
	for <rserpool@ietf.org>; Thu, 13 Mar 2003 07:41:19 -0500 (EST)
Received: from stewart.chicago.il.us (stewart.chicago.il.us [127.0.0.1])
	by stewart.chicago.il.us (8.12.8/8.12.3) with ESMTP id h2DCanbY011757;
	Thu, 13 Mar 2003 06:36:50 -0600 (CST)
	(envelope-from randall@stewart.chicago.il.us)
Message-ID: <3E707B61.3040308@stewart.chicago.il.us>
Date: Thu, 13 Mar 2003 06:36:49 -0600
From: Randall Stewart <randall@stewart.chicago.il.us>
User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.1) Gecko/20021005
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Qiaobing Xie <Qiaobing.Xie@motorola.com>
CC: Rserpool <rserpool@ietf.org>, "Randall Stewart (cisco)" <rrs@cisco.com>,
        Maureen Stillman <Maureen.Stillman@nokia.com>,
        "Michael Tuexen (at home)" <micmac@ilsa.franken.de>,
        "Michael Tuexen (at work)" <Michael.Tuexen@icn.siemens.de>
Subject: Re: [Rserpool] Re: Message channel issues
References: <3E662E44.3080704@cisco.com> <3E6E6AA5.DE56290B@motorola.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
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: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=unsubscribe>
List-Id: Reliable Server Pooling <rserpool.ietf.org>
List-Post: <mailto:rserpool@ietf.org>
List-Help: <mailto:rserpool-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Qiaobing Xie wrote:
> Hi, all,
> 
> When we started to consider defining a control channel at our interim
> meeting (1.5 year ago?), it was thought to be a small addition to the
> architecture that would allow the passing of a few optional messages
> (buz-card, cookie, etc.). The use of these messages were more meant to
> somehow enhance the functionality of RSERPOOL. Now it seems that this
> creature is growing rapidly in terms of architectural impact and
> complexity. Maybe it's time for us to do a sanity check and re-visit how
> much we can gain from this and what we are going to pay for it.
> 
>>From the design's perspective, the main thing in the current proposal is
> to try to bring the control channel from PE-PU communication link into a
> separate entity. This IMHO could have a big implication to RSERPOOL and
> raises a lot of open issues. In the following, I will pose a serious of
> questions for us to think about.
> 

And has you know Q, the Buisness card has been in the orginal
Motorola prototype since before 1999.. because it was esential
when two PE's were speaking to each other (one as PU the other
as PE)... this is nothing new.. I will admit Michael's state
cookie is new... but I don't see it as a huge amount more...

Some more comments...

> "Randall Stewart (cisco)" wrote:
> 
>>Hi all:
>>
>>I was asked to summarize the message channel issue and put out
>>one of the solutions (and one other issue) we discussed on yesterdays
>>conference call.
>>
>>-------------------------
>>Issue #1
>>-------------------------
>>The basic issue is this:
>>
> 
> 
> Keep in mind that currently we allow a PE to register with 1 or more
> transport addresses of diff types (e.g., a PE is _allowed_ to reg with
> sctp-trans1, sctp-trans2, tcp-trans, udp-trans1, udp-trans2), and we
> have of cause 1 or more PEs in any given pool.
>  
> 


Yep... but we have no classification of what can be sent on
those channels...


>>1) A PE may register a Control channel, Data Channel or Both (in a combined
>>    form or seperate).
> 
> 
> - A founding principle of RSERPOOL is that all PEs in a pool are
> "functionally identical" while "maybe capability-wise different". If we
> start to introduce "control-only PEs" via "data-only PEs" via
> "control/data PEs" in the same pool, we need to understand the
> implications and why we need this complexity. For example, can you
> failover from a control-only PE to a data-only PE? What does that mean?
> 

And the B-Card was a founding principle from way back as well.. And I 
don't think you understand the idea here... In my original thoughts you
MUST have one of your registered addresses to accept DATA.. the fact
that you have multiple channels is why I added the classification..

Of course Michael T was thinking about it in more of a ... you
register a control only and then talk to the PE to get the "dynamic"
data channell.. sort of like FTP... Don't know which is best but I
see nothing wrong with classifications on how an address can be
used once you introduce multiple address registries...

> - How does the load sharing should be understood in this picture? I.e.,
> can one round robin amongst a mixed set of data-only and data-control
> PEs? What's the implication here?
> 

Again it would depend... if we go with Michaels view, you would have
to contact each of the servers to get a data channel... my throughts
were always that the PE had to have a data channel registered (and
possibly control as well.. if it could accept B-Cards/State-cookies).
load sharing would be no different than it is now... you load
share amongst the multiple PEs...

> - Are we going to allow a PE to reg as "control channel only"? I'd
> strongly advice against that since it seems to be meaningless and should
> be disallowed, IMO. After all Rserpool is in the business of moving user
> data and I don't see why a PE is useful being control-only.
> 

This was Michaels concept... think FTP where you talk to the
PE on the control channel and get a data channel from it... now
I am not sure on this... but it is how a large number of applications
do currently work in the big-i

> - It must be made clear that unreachability detection must be tied to
> the data side. Otherwise, the redundancy becomes meaningless (e.g., what
> if a PE becomes unreachable on its data side while its control side is
> still functioning?). Question is how to make sure this happens?
> 
This is a major problem with allowing multiple address registrations.
Think about it.. if I allow SCTP-T-1, SCTP-T-2, TCP-T-1 ... what
does it mean (forgetting the data/control thing) if TCP-T-1 becomes
unreachable, while SCTP-T-2 and SCTP-T-1 are ok? Same issue... no
matter if you have a "data type channel" or ones marked that can
be control and data... just control or just data...

I think the data only channel concept is more for older apps aka
those that are proxy'ed in...

In fact I wonder if the data-control designation and data designation
are the only valid ones... i.e. if you register with data-control
you can take b-cards etc.. if you register data then you can
accept no control messages and you can't send any...

Might be a workable arrangment.. but I want to think on this one...


> - In a related issue, what if a PE become unreachable over its control
> channel while its data channel is ok? We should define what this means.
> Should we monitor reachability of control channel at the first place? If
> so, how?

Or reverse the case...

Or for that matter, how does a application detect unreachable data
channels (if they say are UDP?)...

All issues that need to be thought on...

> 
> - When a PE registers with >1 transports (of maybe mixed types among
> SCTP, TCP, UDP), how the control and data channel map to that? Can it do
> things like reg[sctp1/control-only, sctp2/control-and-data,
> tcp/data-only]? If not, what'are the restrictions and how to enforce
> them? If allowed, how those mixed PEs are going to behave in terms of
> failover and load sharing (see below also)?
> 

I agree it is in effect a side effect of letting multiple registrations
of different transports be done...

Maybe the solution is no more than two transports be registered
and they must either be

1) A single transport for control and data
2) A single transport for data only
3) Two transports one for control, one for data..

If you select <3> then if EITHER channel does not function
then the PE is considered unreachable..

This better scopes the issue...

Note: now please don't reply with but I want to have an app which does
SCTP and TCP for data... I have always been skeptical of multiple
transport registration... I can see, maybe, having data and
control seperate on different transports .. aka UDP/SCTP
or some such.. but I have a issue with more than
two for sure..


> - How the failover will work now? Can a PU failover from a control/data
> PE to a data only PE? Or, should we force all PEs in a pool to have the
> same control/data config? 

You have the same issue if you allow multiple transports..

Can a PU fail over from a TCP PE to a SCTP PE? I think
the thing is those in the PE should ALL use the same
transports... IMO

> 
> I can go on and on with this type of questions... there are so many
> combinations here. And I can imagine it's going to be very expensive to
> design and implement them all in RSERPOOL. We really need to understand
> why we need each of them before we decide to build it into RSERPOOL. 
> 

This was the whole point of the email.. we have to come up
with a bounded set of limits to what is allowable...

> As I mentioned above, most of the issues above arise from the fact
> that we are now trying to bring the control channel from PE-PU
> communication link into a separate entity. 

No, these issues showed up the minute you allow multiple transport
registrations for a PE.. period... the same issues are present
we just have not thought of them...

One alternate approach would
> be to keep the control channel bundled with data channel. This would
> solve a lot of issues mentioned above. By this, I mean basically that we
> keep our focus on data side and only allow to have a control channel if
> the data side is over SCTP (using PPID to mux) or TCP (using mapping to
> mux). This is simply and its impact to architecture is little to none.
> This also automatically solves the problem of tying control and data.
> 
And this goes along the lines of my earlier statement above..

Data is always implied, and you can add control to data on
your registration... but this also will remove a possible proxy
type situation .. which may be ok..

I also think you still have these same issues with mulitiple transport
registrations.. instead maybe only 1 type is allowed for a whole
PE...

R


> regards,
> -Qiaobing
> 
> 
> 
>>2) If the PE register's a Data channel and a control channel (non-combined) then
>>    how does the PE make the association between the PU talking on the two
>>    differerent channels?
>>
>>Suppose The PU associates with the Data Channel of a PE... Then at
>>some point decides to use the Control Channel.. for the PE a message
>>arrives on the Control channel and there is no tie back to the conversation
>>on the data channel?
>>
>>Or suppose the control channel is first associated with, followed by
>>the data channel.. how does the PE make the connection..
>>
>>One of the proposed solutions we discussed and thought worth considering (to make
>>sure we have covered all the bases) is:
>>
>>1) Require that if a PE has both a control and data channel that the PU ALWAYs associate
>>   to the Control channel and send a Bussiness card specifying itself.
>>
>>2) The business card will need to be changed so that we can identify that this is a PU only
>>   address.
>>
>>3) The PU would need to supply all of the addresses to the PE for its side of the Data channel so
>>   if it has two communication endpoints up (SCTP/control and TCP/data for example) it would place
>>   in its B-C a indication of the TCP channel id (port/ip address etc) and mark it as "Data channel
>>   only, will not accept connections". The SCTP information could be deduced from the
>>   association.
>>
>>With this proposal we would eliminate the new message that was just added. Expand the
>>types that was just added to asap (for TCP and SCTP endpoints) and finally enhance the
>>wording of the business card and require that ... if a Control channel exists the PU MUST
>>connect and pass its B-C... or something like that.
>>
>>---------------
>>Issue #2
>>---------------
>>
>>The basic issue:
>>
>>There are many possiblities of combinations of Data and Control
>>channels.. do we need to have some sort of restrictions on these... here is a table I have
>>put together showing the possibilites
>>
>>Control Channel Type          |             Data Channel Type
>>------------------------------+--------------------------------------------------------
>>  SCTP                        |               SCTP - Multiplexed - same association
>>------------------------------+--------------------------------------------------------
>>  SCTP                        |               SCTP - Seperate assocaition
>>------------------------------+--------------------------------------------------------
>>  SCTP                        |              TCP
>>------------------------------+--------------------------------------------------------
>>  SCTP                        |               UDP
>>------------------------------+--------------------------------------------------------
>>  TCP                         |               SCTP
>>------------------------------+--------------------------------------------------------
>>  TCP                         |               TCP - Seperate connection
>>------------------------------+--------------------------------------------------------
>>  TCP                         |                TCP - Multiplexed - same connection
>>------------------------------+--------------------------------------------------------
>>  TCP                         |               UDP
>>------------------------------+--------------------------------------------------------
>>
>>So we basically have eight different combinations.. if I have gotten them all
>>(remember UDP is not allowed for the control channel)...
>>
>>So the question is.. should some limitations be placed on the allowable combinations?
>>
>>Thanks
>>
>>R
>>
>>--
>>Randall R. Stewart
>>ITD
>>Cisco Systems Inc.
>>rrs@cisco.com 815-342-5222(cell) or 815-477-2127(office)
> 
> 
> _______________________________________________
> rserpool mailing list
> rserpool@ietf.org
> https://www1.ietf.org/mailman/listinfo/rserpool
> 
> 


-- 
Randall R. Stewart
randall@stewart.chicago.il.us 815-342-5222 (cell phone)

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


From mailnull@www1.ietf.org  Thu Mar 13 07:43:53 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 HAA28469
	for <rserpool-archive@odin.ietf.org>; Thu, 13 Mar 2003 07:43:53 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2DCwJW23308
	for rserpool-archive@odin.ietf.org; Thu, 13 Mar 2003 07:58:19 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2DCvYO23272;
	Thu, 13 Mar 2003 07:57:34 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2DCuIO23229
	for <rserpool@optimus.ietf.org>; Thu, 13 Mar 2003 07:56:18 -0500
Received: from stewart.chicago.il.us (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA28366
	for <rserpool@ietf.org>; Thu, 13 Mar 2003 07:41:19 -0500 (EST)
Received: from stewart.chicago.il.us (stewart.chicago.il.us [127.0.0.1])
	by stewart.chicago.il.us (8.12.8/8.12.3) with ESMTP id h2DCanbY011757;
	Thu, 13 Mar 2003 06:36:50 -0600 (CST)
	(envelope-from randall@stewart.chicago.il.us)
Message-ID: <3E707B61.3040308@stewart.chicago.il.us>
Date: Thu, 13 Mar 2003 06:36:49 -0600
From: Randall Stewart <randall@stewart.chicago.il.us>
User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.1) Gecko/20021005
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Qiaobing Xie <Qiaobing.Xie@motorola.com>
CC: Rserpool <rserpool@ietf.org>, "Randall Stewart (cisco)" <rrs@cisco.com>,
        Maureen Stillman <Maureen.Stillman@nokia.com>,
        "Michael Tuexen (at home)" <micmac@ilsa.franken.de>,
        "Michael Tuexen (at work)" <Michael.Tuexen@icn.siemens.de>
Subject: Re: [Rserpool] Re: Message channel issues
References: <3E662E44.3080704@cisco.com> <3E6E6AA5.DE56290B@motorola.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
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: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=unsubscribe>
List-Id: Reliable Server Pooling <rserpool.ietf.org>
List-Post: <mailto:rserpool@ietf.org>
List-Help: <mailto:rserpool-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Qiaobing Xie wrote:
> Hi, all,
> 
> When we started to consider defining a control channel at our interim
> meeting (1.5 year ago?), it was thought to be a small addition to the
> architecture that would allow the passing of a few optional messages
> (buz-card, cookie, etc.). The use of these messages were more meant to
> somehow enhance the functionality of RSERPOOL. Now it seems that this
> creature is growing rapidly in terms of architectural impact and
> complexity. Maybe it's time for us to do a sanity check and re-visit how
> much we can gain from this and what we are going to pay for it.
> 
>>From the design's perspective, the main thing in the current proposal is
> to try to bring the control channel from PE-PU communication link into a
> separate entity. This IMHO could have a big implication to RSERPOOL and
> raises a lot of open issues. In the following, I will pose a serious of
> questions for us to think about.
> 

And has you know Q, the Buisness card has been in the orginal
Motorola prototype since before 1999.. because it was esential
when two PE's were speaking to each other (one as PU the other
as PE)... this is nothing new.. I will admit Michael's state
cookie is new... but I don't see it as a huge amount more...

Some more comments...

> "Randall Stewart (cisco)" wrote:
> 
>>Hi all:
>>
>>I was asked to summarize the message channel issue and put out
>>one of the solutions (and one other issue) we discussed on yesterdays
>>conference call.
>>
>>-------------------------
>>Issue #1
>>-------------------------
>>The basic issue is this:
>>
> 
> 
> Keep in mind that currently we allow a PE to register with 1 or more
> transport addresses of diff types (e.g., a PE is _allowed_ to reg with
> sctp-trans1, sctp-trans2, tcp-trans, udp-trans1, udp-trans2), and we
> have of cause 1 or more PEs in any given pool.
>  
> 


Yep... but we have no classification of what can be sent on
those channels...


>>1) A PE may register a Control channel, Data Channel or Both (in a combined
>>    form or seperate).
> 
> 
> - A founding principle of RSERPOOL is that all PEs in a pool are
> "functionally identical" while "maybe capability-wise different". If we
> start to introduce "control-only PEs" via "data-only PEs" via
> "control/data PEs" in the same pool, we need to understand the
> implications and why we need this complexity. For example, can you
> failover from a control-only PE to a data-only PE? What does that mean?
> 

And the B-Card was a founding principle from way back as well.. And I 
don't think you understand the idea here... In my original thoughts you
MUST have one of your registered addresses to accept DATA.. the fact
that you have multiple channels is why I added the classification..

Of course Michael T was thinking about it in more of a ... you
register a control only and then talk to the PE to get the "dynamic"
data channell.. sort of like FTP... Don't know which is best but I
see nothing wrong with classifications on how an address can be
used once you introduce multiple address registries...

> - How does the load sharing should be understood in this picture? I.e.,
> can one round robin amongst a mixed set of data-only and data-control
> PEs? What's the implication here?
> 

Again it would depend... if we go with Michaels view, you would have
to contact each of the servers to get a data channel... my throughts
were always that the PE had to have a data channel registered (and
possibly control as well.. if it could accept B-Cards/State-cookies).
load sharing would be no different than it is now... you load
share amongst the multiple PEs...

> - Are we going to allow a PE to reg as "control channel only"? I'd
> strongly advice against that since it seems to be meaningless and should
> be disallowed, IMO. After all Rserpool is in the business of moving user
> data and I don't see why a PE is useful being control-only.
> 

This was Michaels concept... think FTP where you talk to the
PE on the control channel and get a data channel from it... now
I am not sure on this... but it is how a large number of applications
do currently work in the big-i

> - It must be made clear that unreachability detection must be tied to
> the data side. Otherwise, the redundancy becomes meaningless (e.g., what
> if a PE becomes unreachable on its data side while its control side is
> still functioning?). Question is how to make sure this happens?
> 
This is a major problem with allowing multiple address registrations.
Think about it.. if I allow SCTP-T-1, SCTP-T-2, TCP-T-1 ... what
does it mean (forgetting the data/control thing) if TCP-T-1 becomes
unreachable, while SCTP-T-2 and SCTP-T-1 are ok? Same issue... no
matter if you have a "data type channel" or ones marked that can
be control and data... just control or just data...

I think the data only channel concept is more for older apps aka
those that are proxy'ed in...

In fact I wonder if the data-control designation and data designation
are the only valid ones... i.e. if you register with data-control
you can take b-cards etc.. if you register data then you can
accept no control messages and you can't send any...

Might be a workable arrangment.. but I want to think on this one...


> - In a related issue, what if a PE become unreachable over its control
> channel while its data channel is ok? We should define what this means.
> Should we monitor reachability of control channel at the first place? If
> so, how?

Or reverse the case...

Or for that matter, how does a application detect unreachable data
channels (if they say are UDP?)...

All issues that need to be thought on...

> 
> - When a PE registers with >1 transports (of maybe mixed types among
> SCTP, TCP, UDP), how the control and data channel map to that? Can it do
> things like reg[sctp1/control-only, sctp2/control-and-data,
> tcp/data-only]? If not, what'are the restrictions and how to enforce
> them? If allowed, how those mixed PEs are going to behave in terms of
> failover and load sharing (see below also)?
> 

I agree it is in effect a side effect of letting multiple registrations
of different transports be done...

Maybe the solution is no more than two transports be registered
and they must either be

1) A single transport for control and data
2) A single transport for data only
3) Two transports one for control, one for data..

If you select <3> then if EITHER channel does not function
then the PE is considered unreachable..

This better scopes the issue...

Note: now please don't reply with but I want to have an app which does
SCTP and TCP for data... I have always been skeptical of multiple
transport registration... I can see, maybe, having data and
control seperate on different transports .. aka UDP/SCTP
or some such.. but I have a issue with more than
two for sure..


> - How the failover will work now? Can a PU failover from a control/data
> PE to a data only PE? Or, should we force all PEs in a pool to have the
> same control/data config? 

You have the same issue if you allow multiple transports..

Can a PU fail over from a TCP PE to a SCTP PE? I think
the thing is those in the PE should ALL use the same
transports... IMO

> 
> I can go on and on with this type of questions... there are so many
> combinations here. And I can imagine it's going to be very expensive to
> design and implement them all in RSERPOOL. We really need to understand
> why we need each of them before we decide to build it into RSERPOOL. 
> 

This was the whole point of the email.. we have to come up
with a bounded set of limits to what is allowable...

> As I mentioned above, most of the issues above arise from the fact
> that we are now trying to bring the control channel from PE-PU
> communication link into a separate entity. 

No, these issues showed up the minute you allow multiple transport
registrations for a PE.. period... the same issues are present
we just have not thought of them...

One alternate approach would
> be to keep the control channel bundled with data channel. This would
> solve a lot of issues mentioned above. By this, I mean basically that we
> keep our focus on data side and only allow to have a control channel if
> the data side is over SCTP (using PPID to mux) or TCP (using mapping to
> mux). This is simply and its impact to architecture is little to none.
> This also automatically solves the problem of tying control and data.
> 
And this goes along the lines of my earlier statement above..

Data is always implied, and you can add control to data on
your registration... but this also will remove a possible proxy
type situation .. which may be ok..

I also think you still have these same issues with mulitiple transport
registrations.. instead maybe only 1 type is allowed for a whole
PE...

R


> regards,
> -Qiaobing
> 
> 
> 
>>2) If the PE register's a Data channel and a control channel (non-combined) then
>>    how does the PE make the association between the PU talking on the two
>>    differerent channels?
>>
>>Suppose The PU associates with the Data Channel of a PE... Then at
>>some point decides to use the Control Channel.. for the PE a message
>>arrives on the Control channel and there is no tie back to the conversation
>>on the data channel?
>>
>>Or suppose the control channel is first associated with, followed by
>>the data channel.. how does the PE make the connection..
>>
>>One of the proposed solutions we discussed and thought worth considering (to make
>>sure we have covered all the bases) is:
>>
>>1) Require that if a PE has both a control and data channel that the PU ALWAYs associate
>>   to the Control channel and send a Bussiness card specifying itself.
>>
>>2) The business card will need to be changed so that we can identify that this is a PU only
>>   address.
>>
>>3) The PU would need to supply all of the addresses to the PE for its side of the Data channel so
>>   if it has two communication endpoints up (SCTP/control and TCP/data for example) it would place
>>   in its B-C a indication of the TCP channel id (port/ip address etc) and mark it as "Data channel
>>   only, will not accept connections". The SCTP information could be deduced from the
>>   association.
>>
>>With this proposal we would eliminate the new message that was just added. Expand the
>>types that was just added to asap (for TCP and SCTP endpoints) and finally enhance the
>>wording of the business card and require that ... if a Control channel exists the PU MUST
>>connect and pass its B-C... or something like that.
>>
>>---------------
>>Issue #2
>>---------------
>>
>>The basic issue:
>>
>>There are many possiblities of combinations of Data and Control
>>channels.. do we need to have some sort of restrictions on these... here is a table I have
>>put together showing the possibilites
>>
>>Control Channel Type          |             Data Channel Type
>>------------------------------+--------------------------------------------------------
>>  SCTP                        |               SCTP - Multiplexed - same association
>>------------------------------+--------------------------------------------------------
>>  SCTP                        |               SCTP - Seperate assocaition
>>------------------------------+--------------------------------------------------------
>>  SCTP                        |              TCP
>>------------------------------+--------------------------------------------------------
>>  SCTP                        |               UDP
>>------------------------------+--------------------------------------------------------
>>  TCP                         |               SCTP
>>------------------------------+--------------------------------------------------------
>>  TCP                         |               TCP - Seperate connection
>>------------------------------+--------------------------------------------------------
>>  TCP                         |                TCP - Multiplexed - same connection
>>------------------------------+--------------------------------------------------------
>>  TCP                         |               UDP
>>------------------------------+--------------------------------------------------------
>>
>>So we basically have eight different combinations.. if I have gotten them all
>>(remember UDP is not allowed for the control channel)...
>>
>>So the question is.. should some limitations be placed on the allowable combinations?
>>
>>Thanks
>>
>>R
>>
>>--
>>Randall R. Stewart
>>ITD
>>Cisco Systems Inc.
>>rrs@cisco.com 815-342-5222(cell) or 815-477-2127(office)
> 
> 
> _______________________________________________
> rserpool mailing list
> rserpool@ietf.org
> https://www1.ietf.org/mailman/listinfo/rserpool
> 
> 


-- 
Randall R. Stewart
randall@stewart.chicago.il.us 815-342-5222 (cell phone)

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



From rserpool-admin@ietf.org  Thu Mar 13 14:06:53 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 OAA13152
	for <rserpool-archive@lists.ietf.org>; Thu, 13 Mar 2003 14:06:53 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2DJLGO22347;
	Thu, 13 Mar 2003 14:21:16 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2DJKmO22289
	for <rserpool@optimus.ietf.org>; Thu, 13 Mar 2003 14:20:48 -0500
Received: from motgate3.mot.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA13101
	for <rserpool@ietf.org>; Thu, 13 Mar 2003 14:05:41 -0500 (EST)
Received: from pobox.mot.com (pobox.mot.com [129.188.137.100])
	by motgate3.mot.com (Motorola/Motgate3) with ESMTP id h2DJ7Gu5019199
	for <rserpool@ietf.org>; Thu, 13 Mar 2003 12:07:16 -0700 (MST)
Received: [from il27exb01.cig.mot.com (il27exb01.cig.mot.com [136.182.15.100]) by pobox.mot.com (MOT-pobox 2.0) with ESMTP id MAA27865 for <rserpool@ietf.org>; Thu, 13 Mar 2003 12:07:50 -0700 (MST)]
Received: from motorola.com (d50-38cd.cig.mot.com [160.47.56.205]) by il27exb01.cig.mot.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2656.59)
	id GY7KK3Y9; Thu, 13 Mar 2003 13:07:01 -0600
Message-ID: <3E70D689.C0AC0097@motorola.com>
Date: Thu, 13 Mar 2003 13:05:45 -0600
From: Qiaobing Xie <Qiaobing.Xie@motorola.com>
X-Mailer: Mozilla 4.8 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Randall Stewart <randall@stewart.chicago.il.us>
CC: Rserpool <rserpool@ietf.org>, "Randall Stewart (cisco)" <rrs@cisco.com>,
        Maureen Stillman <Maureen.Stillman@nokia.com>,
        "Michael Tuexen (at home)" <micmac@ilsa.franken.de>,
        "Michael Tuexen (at work)" <Michael.Tuexen@icn.siemens.de>
Subject: Re: [Rserpool] Re: Message channel issues
References: <3E662E44.3080704@cisco.com> <3E6E6AA5.DE56290B@motorola.com> <3E707B61.3040308@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: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=unsubscribe>
List-Id: Reliable Server Pooling <rserpool.ietf.org>
List-Post: <mailto:rserpool@ietf.org>
List-Help: <mailto:rserpool-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Hi, Randy,

I think we are in general agreement here. I too believe that we may have
allowed too much freedom into the design lately (such as the wide range
of combinations in number and types of transports registration,
combinations in data/control config...). I mean, freedom is good, but as
we all know too well that it does not come free. The cost we may end up
paying could be both in high impl complexity and loss of efficiency and
real-timeliness. More my comments in-line.

Randall Stewart wrote:
...
> 
> And has you know Q, the Buisness card has been in the orginal
> Motorola prototype since before 1999.. because it was esential
> when two PE's were speaking to each other (one as PU the other
> as PE)... this is nothing new.. I will admit Michael's state
> cookie is new... but I don't see it as a huge amount more...

I am not questioning about their usefulness. But we need to do it in the
right way.

...
> And the B-Card was a founding principle from way back as well.. And I
> don't think you understand the idea here... In my original thoughts you
> MUST have one of your registered addresses to accept DATA.. 

Absolutely agree. It is crucial, see below for more on this.

> the fact
> that you have multiple channels is why I added the classification..
> 
> Of course Michael T was thinking about it in more of a ... you
> register a control only and then talk to the PE to get the "dynamic"
> data channell.. sort of like FTP... Don't know which is best but I
> see nothing wrong with classifications on how an address can be
> used once you introduce multiple address registries...

Believe it or not I'd love to see that multiple address reg go away :-)

> 
> > - How does the load sharing should be understood in this picture? I.e.,
> > can one round robin amongst a mixed set of data-only and data-control
> > PEs? What's the implication here?
> >
> 
> Again it would depend... if we go with Michaels view, you would have
> to contact each of the servers to get a data channel... my throughts
> were always that the PE had to have a data channel registered (and
> possibly control as well.. if it could accept B-Cards/State-cookies).
> load sharing would be no different than it is now... you load
> share amongst the multiple PEs...
> 
> > - Are we going to allow a PE to reg as "control channel only"? I'd
> > strongly advice against that since it seems to be meaningless and should
> > be disallowed, IMO. After all Rserpool is in the business of moving user
> > data and I don't see why a PE is useful being control-only.
> >
> 
> This was Michaels concept... think FTP where you talk to the
> PE on the control channel and get a data channel from it... now
> I am not sure on this... but it is how a large number of applications
> do currently work in the big-i

Here we must not lose our original design focus here... RSERPOOL is not
originally invented for apps like FTP. It will work well to enhance apps
like FTP, but RSERPOOL's primary application area is to support fast
session fail-over for **real-time or near-real-time apps**. This means
things that work well for FTP type of apps may not satisfy RSERPOOL
requirements (as stated in RFC3237). This is precisely why I've been
constantly worried about complexity. IMO keeping it simple enhances our
chance of reaching that goal. 

> 
> > - It must be made clear that unreachability detection must be tied to
> > the data side. Otherwise, the redundancy becomes meaningless (e.g., what
> > if a PE becomes unreachable on its data side while its control side is
> > still functioning?). Question is how to make sure this happens?
> >
> This is a major problem with allowing multiple address registrations.
> Think about it.. if I allow SCTP-T-1, SCTP-T-2, TCP-T-1 ... what
> does it mean (forgetting the data/control thing) if TCP-T-1 becomes
> unreachable, while SCTP-T-2 and SCTP-T-1 are ok? Same issue... no
> matter if you have a "data type channel" or ones marked that can
> be control and data... just control or just data...

With the restriction we've put in - "multiple transports are only for
initial connection establishment, but NOT to fail-over from one
another", I can at least understand how this works. But again, I'd love
to see the multiple addr reg go away :-)

> 
> I think the data only channel concept is more for older apps aka
> those that are proxy'ed in...

Agreed.

> 
> In fact I wonder if the data-control designation and data designation
> are the only valid ones... i.e. if you register with data-control
> you can take b-cards etc.. if you register data then you can
> accept no control messages and you can't send any...

This is for older apps. If they are incapable or unwilling to have a
control channel, they will simply not enjoy the benefit of b-card,
etc.... which can be an incentive for them to upgrade :-)

> 
> Might be a workable arrangment.. but I want to think on this one...
> 
> > - In a related issue, what if a PE become unreachable over its control
> > channel while its data channel is ok? We should define what this means.
> > Should we monitor reachability of control channel at the first place? If
> > so, how?
> 
> Or reverse the case...
> 
> Or for that matter, how does a application detect unreachable data
> channels (if they say are UDP?)...

Data channel outage is easier to deal with... in the sense that the app
is always involved in the detection. In the case of UDP, since the app 
is the ultimate sender/receiver of UDP data, if so desired it will be
able to tell (ie, detect) the loss of data channel. But the control
channel is our own thing and is invisible to the app, this means that if
RSERPOOL doesn't do the detection, no-one else will. This is why I think
we need to understand whether and how this detection should be
performed. Maybe after some analysis we conclude that it's not a big
deal losing control channel. But we need to understand it. Moreover, if
we move to the direction of making data-control always bundled together,
this issue would go away.

> 
> All issues that need to be thought on...
> 
> >
> > - When a PE registers with >1 transports (of maybe mixed types among
> > SCTP, TCP, UDP), how the control and data channel map to that? Can it do
> > things like reg[sctp1/control-only, sctp2/control-and-data,
> > tcp/data-only]? If not, what'are the restrictions and how to enforce
> > them? If allowed, how those mixed PEs are going to behave in terms of
> > failover and load sharing (see below also)?
> >
> 
> I agree it is in effect a side effect of letting multiple registrations
> of different transports be done...
> 
> Maybe the solution is no more than two transports be registered
> and they must either be
> 
> 1) A single transport for control and data
> 2) A single transport for data only
> 3) Two transports one for control, one for data..
> 
> If you select <3> then if EITHER channel does not function
> then the PE is considered unreachable..

I like this... I'd even go a bit further to take out <3>.

> 
> This better scopes the issue...
> 
> Note: now please don't reply with but I want to have an app which does
> SCTP and TCP for data... I have always been skeptical of multiple
> transport registration... I can see, maybe, having data and
> control seperate on different transports .. aka UDP/SCTP
> or some such.. but I have a issue with more than
> two for sure..

I, too, have been skeptical of multiple transport registration. It will
simplify a lot of things if we remove it.

> 
> > - How the failover will work now? Can a PU failover from a control/data
> > PE to a data only PE? Or, should we force all PEs in a pool to have the
> > same control/data config?
> 
> You have the same issue if you allow multiple transports..
> 
> Can a PU fail over from a TCP PE to a SCTP PE? I think
> the thing is those in the PE should ALL use the same
> transports... IMO
> 
> >
> > I can go on and on with this type of questions... there are so many
> > combinations here. And I can imagine it's going to be very expensive to
> > design and implement them all in RSERPOOL. We really need to understand
> > why we need each of them before we decide to build it into RSERPOOL.
> >
> 
> This was the whole point of the email.. we have to come up
> with a bounded set of limits to what is allowable...
> 
> > As I mentioned above, most of the issues above arise from the fact
> > that we are now trying to bring the control channel from PE-PU
> > communication link into a separate entity.
> 
> No, these issues showed up the minute you allow multiple transport
> registrations for a PE.. period... the same issues are present
> we just have not thought of them...
> 
> One alternate approach would
> > be to keep the control channel bundled with data channel. This would
> > solve a lot of issues mentioned above. By this, I mean basically that we
> > keep our focus on data side and only allow to have a control channel if
> > the data side is over SCTP (using PPID to mux) or TCP (using mapping to
> > mux). This is simply and its impact to architecture is little to none.
> > This also automatically solves the problem of tying control and data.
> >
> And this goes along the lines of my earlier statement above..
> 
> Data is always implied, and you can add control to data on
> your registration... but this also will remove a possible proxy
> type situation .. which may be ok..
> 
> I also think you still have these same issues with mulitiple transport
> registrations.. instead maybe only 1 type is allowed for a whole
> PE...

I'd like to see if we can reach some violent consensus to get rid of the
multiple addr reg. Then our data-control discussion would become much
easier.

-Qiaobing

> 
> R
> 
> > regards,
> > -Qiaobing
> >
> >
> >
> >>2) If the PE register's a Data channel and a control channel (non-combined) then
> >>    how does the PE make the association between the PU talking on the two
> >>    differerent channels?
> >>
> >>Suppose The PU associates with the Data Channel of a PE... Then at
> >>some point decides to use the Control Channel.. for the PE a message
> >>arrives on the Control channel and there is no tie back to the conversation
> >>on the data channel?
> >>
> >>Or suppose the control channel is first associated with, followed by
> >>the data channel.. how does the PE make the connection..
> >>
> >>One of the proposed solutions we discussed and thought worth considering (to make
> >>sure we have covered all the bases) is:
> >>
> >>1) Require that if a PE has both a control and data channel that the PU ALWAYs associate
> >>   to the Control channel and send a Bussiness card specifying itself.
> >>
> >>2) The business card will need to be changed so that we can identify that this is a PU only
> >>   address.
> >>
> >>3) The PU would need to supply all of the addresses to the PE for its side of the Data channel so
> >>   if it has two communication endpoints up (SCTP/control and TCP/data for example) it would place
> >>   in its B-C a indication of the TCP channel id (port/ip address etc) and mark it as "Data channel
> >>   only, will not accept connections". The SCTP information could be deduced from the
> >>   association.
> >>
> >>With this proposal we would eliminate the new message that was just added. Expand the
> >>types that was just added to asap (for TCP and SCTP endpoints) and finally enhance the
> >>wording of the business card and require that ... if a Control channel exists the PU MUST
> >>connect and pass its B-C... or something like that.
> >>
> >>---------------
> >>Issue #2
> >>---------------
> >>
> >>The basic issue:
> >>
> >>There are many possiblities of combinations of Data and Control
> >>channels.. do we need to have some sort of restrictions on these... here is a table I have
> >>put together showing the possibilites
> >>
> >>Control Channel Type          |             Data Channel Type
> >>------------------------------+--------------------------------------------------------
> >>  SCTP                        |               SCTP - Multiplexed - same association
> >>------------------------------+--------------------------------------------------------
> >>  SCTP                        |               SCTP - Seperate assocaition
> >>------------------------------+--------------------------------------------------------
> >>  SCTP                        |              TCP
> >>------------------------------+--------------------------------------------------------
> >>  SCTP                        |               UDP
> >>------------------------------+--------------------------------------------------------
> >>  TCP                         |               SCTP
> >>------------------------------+--------------------------------------------------------
> >>  TCP                         |               TCP - Seperate connection
> >>------------------------------+--------------------------------------------------------
> >>  TCP                         |                TCP - Multiplexed - same connection
> >>------------------------------+--------------------------------------------------------
> >>  TCP                         |               UDP
> >>------------------------------+--------------------------------------------------------
> >>
> >>So we basically have eight different combinations.. if I have gotten them all
> >>(remember UDP is not allowed for the control channel)...
> >>
> >>So the question is.. should some limitations be placed on the allowable combinations?
> >>
> >>Thanks
> >>
> >>R
> >>
> >>--
> >>Randall R. Stewart
> >>ITD
> >>Cisco Systems Inc.
> >>rrs@cisco.com 815-342-5222(cell) or 815-477-2127(office)
> >
> >
> > _______________________________________________
> > rserpool mailing list
> > rserpool@ietf.org
> > https://www1.ietf.org/mailman/listinfo/rserpool
> >
> >
> 
> --
> Randall R. Stewart
> randall@stewart.chicago.il.us 815-342-5222 (cell phone)
_______________________________________________
rserpool mailing list
rserpool@ietf.org
https://www1.ietf.org/mailman/listinfo/rserpool


From mailnull@www1.ietf.org  Thu Mar 13 14:07:24 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 OAA13177
	for <rserpool-archive@odin.ietf.org>; Thu, 13 Mar 2003 14:07:24 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2DJLvA22368
	for rserpool-archive@odin.ietf.org; Thu, 13 Mar 2003 14:21:57 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2DJLGO22347;
	Thu, 13 Mar 2003 14:21:16 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2DJKmO22289
	for <rserpool@optimus.ietf.org>; Thu, 13 Mar 2003 14:20:48 -0500
Received: from motgate3.mot.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA13101
	for <rserpool@ietf.org>; Thu, 13 Mar 2003 14:05:41 -0500 (EST)
Received: from pobox.mot.com (pobox.mot.com [129.188.137.100])
	by motgate3.mot.com (Motorola/Motgate3) with ESMTP id h2DJ7Gu5019199
	for <rserpool@ietf.org>; Thu, 13 Mar 2003 12:07:16 -0700 (MST)
Received: [from il27exb01.cig.mot.com (il27exb01.cig.mot.com [136.182.15.100]) by pobox.mot.com (MOT-pobox 2.0) with ESMTP id MAA27865 for <rserpool@ietf.org>; Thu, 13 Mar 2003 12:07:50 -0700 (MST)]
Received: from motorola.com (d50-38cd.cig.mot.com [160.47.56.205]) by il27exb01.cig.mot.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2656.59)
	id GY7KK3Y9; Thu, 13 Mar 2003 13:07:01 -0600
Message-ID: <3E70D689.C0AC0097@motorola.com>
Date: Thu, 13 Mar 2003 13:05:45 -0600
From: Qiaobing Xie <Qiaobing.Xie@motorola.com>
X-Mailer: Mozilla 4.8 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Randall Stewart <randall@stewart.chicago.il.us>
CC: Rserpool <rserpool@ietf.org>, "Randall Stewart (cisco)" <rrs@cisco.com>,
        Maureen Stillman <Maureen.Stillman@nokia.com>,
        "Michael Tuexen (at home)" <micmac@ilsa.franken.de>,
        "Michael Tuexen (at work)" <Michael.Tuexen@icn.siemens.de>
Subject: Re: [Rserpool] Re: Message channel issues
References: <3E662E44.3080704@cisco.com> <3E6E6AA5.DE56290B@motorola.com> <3E707B61.3040308@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: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=unsubscribe>
List-Id: Reliable Server Pooling <rserpool.ietf.org>
List-Post: <mailto:rserpool@ietf.org>
List-Help: <mailto:rserpool-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Hi, Randy,

I think we are in general agreement here. I too believe that we may have
allowed too much freedom into the design lately (such as the wide range
of combinations in number and types of transports registration,
combinations in data/control config...). I mean, freedom is good, but as
we all know too well that it does not come free. The cost we may end up
paying could be both in high impl complexity and loss of efficiency and
real-timeliness. More my comments in-line.

Randall Stewart wrote:
...
> 
> And has you know Q, the Buisness card has been in the orginal
> Motorola prototype since before 1999.. because it was esential
> when two PE's were speaking to each other (one as PU the other
> as PE)... this is nothing new.. I will admit Michael's state
> cookie is new... but I don't see it as a huge amount more...

I am not questioning about their usefulness. But we need to do it in the
right way.

...
> And the B-Card was a founding principle from way back as well.. And I
> don't think you understand the idea here... In my original thoughts you
> MUST have one of your registered addresses to accept DATA.. 

Absolutely agree. It is crucial, see below for more on this.

> the fact
> that you have multiple channels is why I added the classification..
> 
> Of course Michael T was thinking about it in more of a ... you
> register a control only and then talk to the PE to get the "dynamic"
> data channell.. sort of like FTP... Don't know which is best but I
> see nothing wrong with classifications on how an address can be
> used once you introduce multiple address registries...

Believe it or not I'd love to see that multiple address reg go away :-)

> 
> > - How does the load sharing should be understood in this picture? I.e.,
> > can one round robin amongst a mixed set of data-only and data-control
> > PEs? What's the implication here?
> >
> 
> Again it would depend... if we go with Michaels view, you would have
> to contact each of the servers to get a data channel... my throughts
> were always that the PE had to have a data channel registered (and
> possibly control as well.. if it could accept B-Cards/State-cookies).
> load sharing would be no different than it is now... you load
> share amongst the multiple PEs...
> 
> > - Are we going to allow a PE to reg as "control channel only"? I'd
> > strongly advice against that since it seems to be meaningless and should
> > be disallowed, IMO. After all Rserpool is in the business of moving user
> > data and I don't see why a PE is useful being control-only.
> >
> 
> This was Michaels concept... think FTP where you talk to the
> PE on the control channel and get a data channel from it... now
> I am not sure on this... but it is how a large number of applications
> do currently work in the big-i

Here we must not lose our original design focus here... RSERPOOL is not
originally invented for apps like FTP. It will work well to enhance apps
like FTP, but RSERPOOL's primary application area is to support fast
session fail-over for **real-time or near-real-time apps**. This means
things that work well for FTP type of apps may not satisfy RSERPOOL
requirements (as stated in RFC3237). This is precisely why I've been
constantly worried about complexity. IMO keeping it simple enhances our
chance of reaching that goal. 

> 
> > - It must be made clear that unreachability detection must be tied to
> > the data side. Otherwise, the redundancy becomes meaningless (e.g., what
> > if a PE becomes unreachable on its data side while its control side is
> > still functioning?). Question is how to make sure this happens?
> >
> This is a major problem with allowing multiple address registrations.
> Think about it.. if I allow SCTP-T-1, SCTP-T-2, TCP-T-1 ... what
> does it mean (forgetting the data/control thing) if TCP-T-1 becomes
> unreachable, while SCTP-T-2 and SCTP-T-1 are ok? Same issue... no
> matter if you have a "data type channel" or ones marked that can
> be control and data... just control or just data...

With the restriction we've put in - "multiple transports are only for
initial connection establishment, but NOT to fail-over from one
another", I can at least understand how this works. But again, I'd love
to see the multiple addr reg go away :-)

> 
> I think the data only channel concept is more for older apps aka
> those that are proxy'ed in...

Agreed.

> 
> In fact I wonder if the data-control designation and data designation
> are the only valid ones... i.e. if you register with data-control
> you can take b-cards etc.. if you register data then you can
> accept no control messages and you can't send any...

This is for older apps. If they are incapable or unwilling to have a
control channel, they will simply not enjoy the benefit of b-card,
etc.... which can be an incentive for them to upgrade :-)

> 
> Might be a workable arrangment.. but I want to think on this one...
> 
> > - In a related issue, what if a PE become unreachable over its control
> > channel while its data channel is ok? We should define what this means.
> > Should we monitor reachability of control channel at the first place? If
> > so, how?
> 
> Or reverse the case...
> 
> Or for that matter, how does a application detect unreachable data
> channels (if they say are UDP?)...

Data channel outage is easier to deal with... in the sense that the app
is always involved in the detection. In the case of UDP, since the app 
is the ultimate sender/receiver of UDP data, if so desired it will be
able to tell (ie, detect) the loss of data channel. But the control
channel is our own thing and is invisible to the app, this means that if
RSERPOOL doesn't do the detection, no-one else will. This is why I think
we need to understand whether and how this detection should be
performed. Maybe after some analysis we conclude that it's not a big
deal losing control channel. But we need to understand it. Moreover, if
we move to the direction of making data-control always bundled together,
this issue would go away.

> 
> All issues that need to be thought on...
> 
> >
> > - When a PE registers with >1 transports (of maybe mixed types among
> > SCTP, TCP, UDP), how the control and data channel map to that? Can it do
> > things like reg[sctp1/control-only, sctp2/control-and-data,
> > tcp/data-only]? If not, what'are the restrictions and how to enforce
> > them? If allowed, how those mixed PEs are going to behave in terms of
> > failover and load sharing (see below also)?
> >
> 
> I agree it is in effect a side effect of letting multiple registrations
> of different transports be done...
> 
> Maybe the solution is no more than two transports be registered
> and they must either be
> 
> 1) A single transport for control and data
> 2) A single transport for data only
> 3) Two transports one for control, one for data..
> 
> If you select <3> then if EITHER channel does not function
> then the PE is considered unreachable..

I like this... I'd even go a bit further to take out <3>.

> 
> This better scopes the issue...
> 
> Note: now please don't reply with but I want to have an app which does
> SCTP and TCP for data... I have always been skeptical of multiple
> transport registration... I can see, maybe, having data and
> control seperate on different transports .. aka UDP/SCTP
> or some such.. but I have a issue with more than
> two for sure..

I, too, have been skeptical of multiple transport registration. It will
simplify a lot of things if we remove it.

> 
> > - How the failover will work now? Can a PU failover from a control/data
> > PE to a data only PE? Or, should we force all PEs in a pool to have the
> > same control/data config?
> 
> You have the same issue if you allow multiple transports..
> 
> Can a PU fail over from a TCP PE to a SCTP PE? I think
> the thing is those in the PE should ALL use the same
> transports... IMO
> 
> >
> > I can go on and on with this type of questions... there are so many
> > combinations here. And I can imagine it's going to be very expensive to
> > design and implement them all in RSERPOOL. We really need to understand
> > why we need each of them before we decide to build it into RSERPOOL.
> >
> 
> This was the whole point of the email.. we have to come up
> with a bounded set of limits to what is allowable...
> 
> > As I mentioned above, most of the issues above arise from the fact
> > that we are now trying to bring the control channel from PE-PU
> > communication link into a separate entity.
> 
> No, these issues showed up the minute you allow multiple transport
> registrations for a PE.. period... the same issues are present
> we just have not thought of them...
> 
> One alternate approach would
> > be to keep the control channel bundled with data channel. This would
> > solve a lot of issues mentioned above. By this, I mean basically that we
> > keep our focus on data side and only allow to have a control channel if
> > the data side is over SCTP (using PPID to mux) or TCP (using mapping to
> > mux). This is simply and its impact to architecture is little to none.
> > This also automatically solves the problem of tying control and data.
> >
> And this goes along the lines of my earlier statement above..
> 
> Data is always implied, and you can add control to data on
> your registration... but this also will remove a possible proxy
> type situation .. which may be ok..
> 
> I also think you still have these same issues with mulitiple transport
> registrations.. instead maybe only 1 type is allowed for a whole
> PE...

I'd like to see if we can reach some violent consensus to get rid of the
multiple addr reg. Then our data-control discussion would become much
easier.

-Qiaobing

> 
> R
> 
> > regards,
> > -Qiaobing
> >
> >
> >
> >>2) If the PE register's a Data channel and a control channel (non-combined) then
> >>    how does the PE make the association between the PU talking on the two
> >>    differerent channels?
> >>
> >>Suppose The PU associates with the Data Channel of a PE... Then at
> >>some point decides to use the Control Channel.. for the PE a message
> >>arrives on the Control channel and there is no tie back to the conversation
> >>on the data channel?
> >>
> >>Or suppose the control channel is first associated with, followed by
> >>the data channel.. how does the PE make the connection..
> >>
> >>One of the proposed solutions we discussed and thought worth considering (to make
> >>sure we have covered all the bases) is:
> >>
> >>1) Require that if a PE has both a control and data channel that the PU ALWAYs associate
> >>   to the Control channel and send a Bussiness card specifying itself.
> >>
> >>2) The business card will need to be changed so that we can identify that this is a PU only
> >>   address.
> >>
> >>3) The PU would need to supply all of the addresses to the PE for its side of the Data channel so
> >>   if it has two communication endpoints up (SCTP/control and TCP/data for example) it would place
> >>   in its B-C a indication of the TCP channel id (port/ip address etc) and mark it as "Data channel
> >>   only, will not accept connections". The SCTP information could be deduced from the
> >>   association.
> >>
> >>With this proposal we would eliminate the new message that was just added. Expand the
> >>types that was just added to asap (for TCP and SCTP endpoints) and finally enhance the
> >>wording of the business card and require that ... if a Control channel exists the PU MUST
> >>connect and pass its B-C... or something like that.
> >>
> >>---------------
> >>Issue #2
> >>---------------
> >>
> >>The basic issue:
> >>
> >>There are many possiblities of combinations of Data and Control
> >>channels.. do we need to have some sort of restrictions on these... here is a table I have
> >>put together showing the possibilites
> >>
> >>Control Channel Type          |             Data Channel Type
> >>------------------------------+--------------------------------------------------------
> >>  SCTP                        |               SCTP - Multiplexed - same association
> >>------------------------------+--------------------------------------------------------
> >>  SCTP                        |               SCTP - Seperate assocaition
> >>------------------------------+--------------------------------------------------------
> >>  SCTP                        |              TCP
> >>------------------------------+--------------------------------------------------------
> >>  SCTP                        |               UDP
> >>------------------------------+--------------------------------------------------------
> >>  TCP                         |               SCTP
> >>------------------------------+--------------------------------------------------------
> >>  TCP                         |               TCP - Seperate connection
> >>------------------------------+--------------------------------------------------------
> >>  TCP                         |                TCP - Multiplexed - same connection
> >>------------------------------+--------------------------------------------------------
> >>  TCP                         |               UDP
> >>------------------------------+--------------------------------------------------------
> >>
> >>So we basically have eight different combinations.. if I have gotten them all
> >>(remember UDP is not allowed for the control channel)...
> >>
> >>So the question is.. should some limitations be placed on the allowable combinations?
> >>
> >>Thanks
> >>
> >>R
> >>
> >>--
> >>Randall R. Stewart
> >>ITD
> >>Cisco Systems Inc.
> >>rrs@cisco.com 815-342-5222(cell) or 815-477-2127(office)
> >
> >
> > _______________________________________________
> > rserpool mailing list
> > rserpool@ietf.org
> > https://www1.ietf.org/mailman/listinfo/rserpool
> >
> >
> 
> --
> Randall R. Stewart
> randall@stewart.chicago.il.us 815-342-5222 (cell phone)
_______________________________________________
rserpool mailing list
rserpool@ietf.org
https://www1.ietf.org/mailman/listinfo/rserpool



From rserpool-admin@ietf.org  Mon Mar 17 00:15:16 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 AAA20406
	for <rserpool-archive@lists.ietf.org>; Mon, 17 Mar 2003 00:15:16 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2H5VLO22247;
	Mon, 17 Mar 2003 00:31:21 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2H5UQO22159
	for <rserpool@optimus.ietf.org>; Mon, 17 Mar 2003 00:30:26 -0500
Received: from smtp.comcast.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA20166
	for <rserpool@ietf.org>; Mon, 17 Mar 2003 00:13:41 -0500 (EST)
Received: from ROVER.acm.org
 (wl-135-176.wireless.ietf56.ietf.org [130.129.135.176])
 by mtaout04.icomcast.net
 (iPlanet Messaging Server 5.2 HotFix 1.12 (built Feb 13 2003))
 with ESMTPA id <0HBV00FNBNYF4C@mtaout04.icomcast.net> for rserpool@ietf.org;
 Mon, 17 Mar 2003 00:15:54 -0500 (EST)
Date: Mon, 17 Mar 2003 00:15:37 -0500
From: Phillip Conrad <conrad@acm.org>
Subject: Re: [Rserpool] Re: Message channel issues
In-reply-to: <3E70D689.C0AC0097@motorola.com>
X-Sender: phillipconrad@mail.comcast.net
To: Qiaobing Xie <Qiaobing.Xie@motorola.com>,
        Randall Stewart <randall@stewart.chicago.il.us>
Cc: Rserpool <rserpool@ietf.org>, "Randall Stewart (cisco)" <rrs@cisco.com>,
        Maureen Stillman <Maureen.Stillman@nokia.com>,
        "Michael Tuexen (at home)" <micmac@ilsa.franken.de>,
        "Michael Tuexen (at work)" <Michael.Tuexen@icn.siemens.de>
Message-id: <5.1.1.6.0.20030316235723.01981338@joda.cis.temple.edu>
MIME-version: 1.0
X-Mailer: QUALCOMM Windows Eudora Version 5.1.1
Content-type: text/plain; charset=us-ascii; format=flowed
Content-transfer-encoding: 7BIT
References: <3E662E44.3080704@cisco.com> <3E6E6AA5.DE56290B@motorola.com>
 <3E707B61.3040308@stewart.chicago.il.us>
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: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=unsubscribe>
List-Id: Reliable Server Pooling <rserpool.ietf.org>
List-Post: <mailto:rserpool@ietf.org>
List-Help: <mailto:rserpool-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7BIT

Some comments:

At 01:05 PM 3/13/2003 -0600, Qiaobing Xie wrote:
>Randall Stewart wrote:
> > Maybe the solution is no more than two transports be registered
> > and they must either be
> >
> > 1) A single transport for control and data
> > 2) A single transport for data only
> > 3) Two transports one for control, one for data..
> >
> > If you select <3> then if EITHER channel does not function
> > then the PE is considered unreachable..
>
>I like this... I'd even go a bit further to take out <3>.

Believe it or not, I'm in agreement with Qiaobing on several 
points.   First, I agree that we can probably live without multiple 
transport registrations.   Why did we want these in the first place?   For 
two reasons I think.

(1) We wanted to allow for migration from TCP to SCTP for pool users; i.e. 
allow some pool users that have not yet adopted SCTP to participate in a 
pool for service X.   However, this can be handled more simply by 
maintaining separate pools, with separate pool handles, e.g. X-SCTP and 
X-TCP.   This preserves the principle that a pool should be made up of 
equivalent services... this concept should include "equivalent in terms of 
which transport protocol is used".

(2) We wanted to allow for separate data and control channels on two 
different protocols.  E.g. control channel over SCTP (or mapped TCP) and 
data channel over UDP, or protocol XYZ, or whatever.    However, Qiaobing 
makes a case that we can acheive better simplicity by simply requiring that 
applications that use a transport other than SCTP or TCP for their data 
channel do NOT benefit from the extended features that the control channel 
allows.  I.e., you should either use a multplexed control/data channel, or 
you shoudl not use a control channel at all.   (Interestingly, this is 
pretty much exactly what I had in mind when I suggested two "modes"  in the 
original version of the services draft.    I think perhaps it is time to 
take a second look at that concept.  Qiaobing doesn't seem to like the 
terms "failover" vs. "nameservice" mode  for the services you get from a 
muxed control/data channel, or a data only channel (respectively), but I 
think that the concepts in the services draft are the right ones.

Let me invite folks to re-read the services draft and make some 
suggestions: is the problem with the concepts, or only with the 
terminology?     Can we come up with better terms that "failover" vs. 
"nameservice" mode?

Thanks,
Phill
  

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


From mailnull@www1.ietf.org  Mon Mar 17 00:15:47 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 AAA20439
	for <rserpool-archive@odin.ietf.org>; Mon, 17 Mar 2003 00:15:46 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2H5W0q22284
	for rserpool-archive@odin.ietf.org; Mon, 17 Mar 2003 00:32:00 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2H5VLO22247;
	Mon, 17 Mar 2003 00:31:21 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2H5UQO22159
	for <rserpool@optimus.ietf.org>; Mon, 17 Mar 2003 00:30:26 -0500
Received: from smtp.comcast.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA20166
	for <rserpool@ietf.org>; Mon, 17 Mar 2003 00:13:41 -0500 (EST)
Received: from ROVER.acm.org
 (wl-135-176.wireless.ietf56.ietf.org [130.129.135.176])
 by mtaout04.icomcast.net
 (iPlanet Messaging Server 5.2 HotFix 1.12 (built Feb 13 2003))
 with ESMTPA id <0HBV00FNBNYF4C@mtaout04.icomcast.net> for rserpool@ietf.org;
 Mon, 17 Mar 2003 00:15:54 -0500 (EST)
Date: Mon, 17 Mar 2003 00:15:37 -0500
From: Phillip Conrad <conrad@acm.org>
Subject: Re: [Rserpool] Re: Message channel issues
In-reply-to: <3E70D689.C0AC0097@motorola.com>
X-Sender: phillipconrad@mail.comcast.net
To: Qiaobing Xie <Qiaobing.Xie@motorola.com>,
        Randall Stewart <randall@stewart.chicago.il.us>
Cc: Rserpool <rserpool@ietf.org>, "Randall Stewart (cisco)" <rrs@cisco.com>,
        Maureen Stillman <Maureen.Stillman@nokia.com>,
        "Michael Tuexen (at home)" <micmac@ilsa.franken.de>,
        "Michael Tuexen (at work)" <Michael.Tuexen@icn.siemens.de>
Message-id: <5.1.1.6.0.20030316235723.01981338@joda.cis.temple.edu>
MIME-version: 1.0
X-Mailer: QUALCOMM Windows Eudora Version 5.1.1
Content-type: text/plain; charset=us-ascii; format=flowed
Content-transfer-encoding: 7BIT
References: <3E662E44.3080704@cisco.com> <3E6E6AA5.DE56290B@motorola.com>
 <3E707B61.3040308@stewart.chicago.il.us>
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: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=unsubscribe>
List-Id: Reliable Server Pooling <rserpool.ietf.org>
List-Post: <mailto:rserpool@ietf.org>
List-Help: <mailto:rserpool-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7BIT

Some comments:

At 01:05 PM 3/13/2003 -0600, Qiaobing Xie wrote:
>Randall Stewart wrote:
> > Maybe the solution is no more than two transports be registered
> > and they must either be
> >
> > 1) A single transport for control and data
> > 2) A single transport for data only
> > 3) Two transports one for control, one for data..
> >
> > If you select <3> then if EITHER channel does not function
> > then the PE is considered unreachable..
>
>I like this... I'd even go a bit further to take out <3>.

Believe it or not, I'm in agreement with Qiaobing on several 
points.   First, I agree that we can probably live without multiple 
transport registrations.   Why did we want these in the first place?   For 
two reasons I think.

(1) We wanted to allow for migration from TCP to SCTP for pool users; i.e. 
allow some pool users that have not yet adopted SCTP to participate in a 
pool for service X.   However, this can be handled more simply by 
maintaining separate pools, with separate pool handles, e.g. X-SCTP and 
X-TCP.   This preserves the principle that a pool should be made up of 
equivalent services... this concept should include "equivalent in terms of 
which transport protocol is used".

(2) We wanted to allow for separate data and control channels on two 
different protocols.  E.g. control channel over SCTP (or mapped TCP) and 
data channel over UDP, or protocol XYZ, or whatever.    However, Qiaobing 
makes a case that we can acheive better simplicity by simply requiring that 
applications that use a transport other than SCTP or TCP for their data 
channel do NOT benefit from the extended features that the control channel 
allows.  I.e., you should either use a multplexed control/data channel, or 
you shoudl not use a control channel at all.   (Interestingly, this is 
pretty much exactly what I had in mind when I suggested two "modes"  in the 
original version of the services draft.    I think perhaps it is time to 
take a second look at that concept.  Qiaobing doesn't seem to like the 
terms "failover" vs. "nameservice" mode  for the services you get from a 
muxed control/data channel, or a data only channel (respectively), but I 
think that the concepts in the services draft are the right ones.

Let me invite folks to re-read the services draft and make some 
suggestions: is the problem with the concepts, or only with the 
terminology?     Can we come up with better terms that "failover" vs. 
"nameservice" mode?

Thanks,
Phill
  

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



From rserpool-admin@ietf.org  Mon Mar 17 14:32:50 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 OAA26453
	for <rserpool-archive@lists.ietf.org>; Mon, 17 Mar 2003 14:32:50 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2HJnEO28538;
	Mon, 17 Mar 2003 14:49:14 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2HJmQO28506
	for <rserpool@optimus.ietf.org>; Mon, 17 Mar 2003 14:48:26 -0500
Received: from smtp.comcast.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA26351
	for <rserpool@ietf.org>; Mon, 17 Mar 2003 14:31:21 -0500 (EST)
Received: from ROVER.acm.org
 (wl-135-176.wireless.ietf56.ietf.org [130.129.135.176])
 by mtaout10.icomcast.net
 (iPlanet Messaging Server 5.2 HotFix 1.12 (built Feb 13 2003))
 with ESMTPA id <0HBW00KTERLUMN@mtaout10.icomcast.net> for rserpool@ietf.org;
 Mon, 17 Mar 2003 14:32:20 -0500 (EST)
Date: Mon, 17 Mar 2003 11:32:06 -0800
From: Phillip Conrad <conrad@acm.org>
In-reply-to: <5.1.1.6.0.20030316235723.01981338@joda.cis.temple.edu>
X-Sender: phillipconrad@mail.comcast.net
To: Rserpool <rserpool@ietf.org>
Cc: Phillip Conrad <conrad@acm.org>
Message-id: <5.1.1.6.0.20030317110804.0341e678@joda.cis.temple.edu>
MIME-version: 1.0
X-Mailer: QUALCOMM Windows Eudora Version 5.1.1
Content-type: text/plain; charset=us-ascii; format=flowed
Content-transfer-encoding: 7BIT
References: <3E70D689.C0AC0097@motorola.com> <3E662E44.3080704@cisco.com>
 <3E6E6AA5.DE56290B@motorola.com> <3E707B61.3040308@stewart.chicago.il.us>
Content-Transfer-Encoding: 7BIT
Subject: [Rserpool] Directions for next version of service draft
Sender: rserpool-admin@ietf.org
Errors-To: rserpool-admin@ietf.org
X-BeenThere: rserpool@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=unsubscribe>
List-Id: Reliable Server Pooling <rserpool.ietf.org>
List-Post: <mailto:rserpool@ietf.org>
List-Help: <mailto:rserpool-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7BIT

Here are some suggested directions for RSerPool:

To the working group: do we have rough consensus on these points?  I and 
others (Peter, Randy, Qiaobing et al)  will ask for rough consensus on 
these points in the working group meeting later today in San Francisco... 
and for the sake of those that are NOT in the meeting today, please 
consider this email as your opportunity to express support, dissent, or to 
ask for further clarification on the points below.

(1) In the service draft, replace "failover mode" vs. "nameservice mode" 
with "multiplexed data channel" vs. "non multiplexed data channel".

(2) In the service draft, remove application layer acks from protocol, and 
write up as use case instead.

(3)  In general: No multiple transport registrations: you either

(a) register the transport address of either an SCTP or TCP (but not both) 
multiplexed control and data over a single transport 
association/connection.  (Note: you _can_ register both, but if you do so, 
they should be in different pools, preserving the principle that all PE's 
in a pool should be functionally equivalent, including all using the same 
transport protocol to provide service.)

(b) you register the transport address of a data channel only, not managed 
by rserpool (and do without the services that would be provided by a 
control channel.)


(4) A Note: when you register for SCTP, you may register multiple IP 
addresses, but only a single port... i.e, you are only registering a single 
SCTP endpoint.  This is already reflected in the current drafts.


Thanks,
Phill Conrad

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


From mailnull@www1.ietf.org  Mon Mar 17 14:33:22 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 OAA26561
	for <rserpool-archive@odin.ietf.org>; Mon, 17 Mar 2003 14:33:21 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2HJnri28590
	for rserpool-archive@odin.ietf.org; Mon, 17 Mar 2003 14:49:53 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2HJnEO28538;
	Mon, 17 Mar 2003 14:49:14 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2HJmQO28506
	for <rserpool@optimus.ietf.org>; Mon, 17 Mar 2003 14:48:26 -0500
Received: from smtp.comcast.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA26351
	for <rserpool@ietf.org>; Mon, 17 Mar 2003 14:31:21 -0500 (EST)
Received: from ROVER.acm.org
 (wl-135-176.wireless.ietf56.ietf.org [130.129.135.176])
 by mtaout10.icomcast.net
 (iPlanet Messaging Server 5.2 HotFix 1.12 (built Feb 13 2003))
 with ESMTPA id <0HBW00KTERLUMN@mtaout10.icomcast.net> for rserpool@ietf.org;
 Mon, 17 Mar 2003 14:32:20 -0500 (EST)
Date: Mon, 17 Mar 2003 11:32:06 -0800
From: Phillip Conrad <conrad@acm.org>
In-reply-to: <5.1.1.6.0.20030316235723.01981338@joda.cis.temple.edu>
X-Sender: phillipconrad@mail.comcast.net
To: Rserpool <rserpool@ietf.org>
Cc: Phillip Conrad <conrad@acm.org>
Message-id: <5.1.1.6.0.20030317110804.0341e678@joda.cis.temple.edu>
MIME-version: 1.0
X-Mailer: QUALCOMM Windows Eudora Version 5.1.1
Content-type: text/plain; charset=us-ascii; format=flowed
Content-transfer-encoding: 7BIT
References: <3E70D689.C0AC0097@motorola.com> <3E662E44.3080704@cisco.com>
 <3E6E6AA5.DE56290B@motorola.com> <3E707B61.3040308@stewart.chicago.il.us>
Content-Transfer-Encoding: 7BIT
Subject: [Rserpool] Directions for next version of service draft
Sender: rserpool-admin@ietf.org
Errors-To: rserpool-admin@ietf.org
X-BeenThere: rserpool@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=unsubscribe>
List-Id: Reliable Server Pooling <rserpool.ietf.org>
List-Post: <mailto:rserpool@ietf.org>
List-Help: <mailto:rserpool-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7BIT

Here are some suggested directions for RSerPool:

To the working group: do we have rough consensus on these points?  I and 
others (Peter, Randy, Qiaobing et al)  will ask for rough consensus on 
these points in the working group meeting later today in San Francisco... 
and for the sake of those that are NOT in the meeting today, please 
consider this email as your opportunity to express support, dissent, or to 
ask for further clarification on the points below.

(1) In the service draft, replace "failover mode" vs. "nameservice mode" 
with "multiplexed data channel" vs. "non multiplexed data channel".

(2) In the service draft, remove application layer acks from protocol, and 
write up as use case instead.

(3)  In general: No multiple transport registrations: you either

(a) register the transport address of either an SCTP or TCP (but not both) 
multiplexed control and data over a single transport 
association/connection.  (Note: you _can_ register both, but if you do so, 
they should be in different pools, preserving the principle that all PE's 
in a pool should be functionally equivalent, including all using the same 
transport protocol to provide service.)

(b) you register the transport address of a data channel only, not managed 
by rserpool (and do without the services that would be provided by a 
control channel.)


(4) A Note: when you register for SCTP, you may register multiple IP 
addresses, but only a single port... i.e, you are only registering a single 
SCTP endpoint.  This is already reflected in the current drafts.


Thanks,
Phill Conrad

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



From rserpool-admin@ietf.org  Tue Mar 18 01:00: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 BAA19947
	for <rserpool-archive@lists.ietf.org>; Tue, 18 Mar 2003 01:00:44 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2I6HEO09785;
	Tue, 18 Mar 2003 01:17:14 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2I6GPO09747
	for <rserpool@optimus.ietf.org>; Tue, 18 Mar 2003 01:16:25 -0500
Received: from grebe.mail.pas.earthlink.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA19917
	for <rserpool@ietf.org>; Tue, 18 Mar 2003 00:59:09 -0500 (EST)
Received: from user-38lc0tk.dialup.mindspring.com ([209.86.3.180] helo=ROVER.acm.org)
	by grebe.mail.pas.earthlink.net with esmtp (Exim 3.33 #1)
	id 18vAA4-00017T-00; Mon, 17 Mar 2003 22:01:21 -0800
Message-Id: <5.1.1.6.0.20030317133257.01995ea0@joda.cis.temple.edu>
X-Sender: phillipconrad@earthlink.net@mail.earthlink.net
X-Mailer: QUALCOMM Windows Eudora Version 5.1.1
Date: Mon, 17 Mar 2003 16:17:38 -0800
To: Rserpool <rserpool@ietf.org>
From: Phillip Conrad <conrad@acm.org>
Cc: Phillip Conrad <conrad@acm.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Subject: [Rserpool] Issues for architecture draft, asap draft
Sender: rserpool-admin@ietf.org
Errors-To: rserpool-admin@ietf.org
X-BeenThere: rserpool@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=unsubscribe>
List-Id: Reliable Server Pooling <rserpool.ietf.org>
List-Post: <mailto:rserpool@ietf.org>
List-Help: <mailto:rserpool-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=subscribe>

Some suggestions regarding latest versions of the architecture draft and 
ASAP drafts

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

(a) Section 2.2.3, Figure 1

The figure indicates SCTP as the transport protocol over which ASAP 
operates for PU<->NS communication.   A mention should be added that this 
communication may also take place over TCP (following the protocol 
specified in 
http://www.ietf.org/internet-drafts/draft-conrad-rserpool-tcpmapping-01.txt)

Note that the figure in 2.2.4 (which has no figure number) is correct in 
indicating only SCTP.

(b)  Section 2.2.5, PU <-> PE Communication

Based on current direction to simplify the protocols, avoiding multiple 
transport registrations, this section should be updated as follows:

An application can interact with an RSerPool implementation in one of two ways:

   (1) a multiplexed control/data channel, where the data channel is 
accessed through RSerPool primitives, where this multiplexed data/control 
channel is one of only two options: (a) a single SCTP association, with 
control/data separated by PPID or (b) a single TCP connection, with 
control/data separated by PPID via the TCP mapping layer described in 
http://www.ietf.org/internet-drafts/draft-conrad-rserpool-tcpmapping-01.txt

   (2) a data channel with NO control channel, where the data channel is 
provided by a transport protocol directly, and is NOT accessed through 
RSerPool primitives.    Note that certain enhanced failover services (e.g. 
business cards, state cookies, message failover) are not available when 
this method of interaction is used.

Note that for a given pool, since a fundamental principle of RSerPool is 
that all PEs provide equivalent service, all PUs and PEs should make the 
same choice for the style of interaction between the applicaiton layer and 
the RSerPool layer: that is, for a given pool, either all PEs and PUs in 
that pool use a multiplexed control/data channel for PE-PU communication,, 
or all PEs and PUs in that pool use a data channel only for PE-PU 
communication.

When the multiplexed control/data channel is used, enhanced failover 
services may be provided, including:

    o  The PE can send a testament (business card) to the PU for providing 
information to
       which other PE the PU should failover in case of a failover.

    o  The PE can send cookies to the PU. The PE would store only the
       last cookie and send it to the new PE in case of a failover.

etc...

(c) 2.3.2 Cookies

"Cookies may be sent from the PE to the PU if the PE wants this to do."

Minor grammar point: "wants to do this"  would sound more natural in 
English. :-)

(d) 2.3.1 vs. 2.3.3... are business cards and testaments the same or 
different concepts?
If they are the same, we should adopt one term or the other.  I like 
"testament" as a good metaphor for the idea of "this is what to do in case 
of my death".  Also, check spelling of "szenario."

now, Comments on 
http://www.ietf.org/internet-drafts/draft-ietf-rserpool-asap-06.txt

(e) In section 4.3, 4.4

cache.populate.request([Pool-Handle |Pool-Element-Handle])
cache.purge.request([Pool-Handle | Pool-Element-Handle])

    Can you help clarify the role and purpose of these from the standpoint 
of the user application code.. are these called
    by the PU? by the PE?    Are they really user service primitives, or 
are they operations that are internal to the PU/PE in response to certain 
message types, but not directly accessible to the user?  An example use 
case might be helpful.


(f) Section 4.5.4.   We have an opportunity to clarify an issue that may be 
a little fuzzy right now: how does a PE "respond" to a message from a PU 
(particularly if that PU is _not_ a PE in any pool).    The easiest way to 
imagine this happening is that when the PE receives a 
data.received.notification, that notification contains either the transport 
address of the PU, or some handle that ASAP can use to refer to that 
address.    The PE then uses the "data.send.request" primitive as per 
section 4.5.4 to transmit the "reply" back to the PU that originated the 
message.

Of course, the actual API may look quite different from this... e.g. the 
"handle" might be the file descriptor that points to a particular SCTP 
association or TCP connection, etc.   but _conceptually_, the 
data.send.primitive by transport addresss is how the PE gets the message 
back to the PU.   And this is something that is a bit mysterious in the 
current versions of the drafts, and which I think we should clear up.


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


From mailnull@www1.ietf.org  Tue Mar 18 01:01: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 BAA19972
	for <rserpool-archive@odin.ietf.org>; Tue, 18 Mar 2003 01:01:15 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2I6HxX09798
	for rserpool-archive@odin.ietf.org; Tue, 18 Mar 2003 01:17:59 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2I6HEO09785;
	Tue, 18 Mar 2003 01:17:14 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2I6GPO09747
	for <rserpool@optimus.ietf.org>; Tue, 18 Mar 2003 01:16:25 -0500
Received: from grebe.mail.pas.earthlink.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA19917
	for <rserpool@ietf.org>; Tue, 18 Mar 2003 00:59:09 -0500 (EST)
Received: from user-38lc0tk.dialup.mindspring.com ([209.86.3.180] helo=ROVER.acm.org)
	by grebe.mail.pas.earthlink.net with esmtp (Exim 3.33 #1)
	id 18vAA4-00017T-00; Mon, 17 Mar 2003 22:01:21 -0800
Message-Id: <5.1.1.6.0.20030317133257.01995ea0@joda.cis.temple.edu>
X-Sender: phillipconrad@earthlink.net@mail.earthlink.net
X-Mailer: QUALCOMM Windows Eudora Version 5.1.1
Date: Mon, 17 Mar 2003 16:17:38 -0800
To: Rserpool <rserpool@ietf.org>
From: Phillip Conrad <conrad@acm.org>
Cc: Phillip Conrad <conrad@acm.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Subject: [Rserpool] Issues for architecture draft, asap draft
Sender: rserpool-admin@ietf.org
Errors-To: rserpool-admin@ietf.org
X-BeenThere: rserpool@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=unsubscribe>
List-Id: Reliable Server Pooling <rserpool.ietf.org>
List-Post: <mailto:rserpool@ietf.org>
List-Help: <mailto:rserpool-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=subscribe>

Some suggestions regarding latest versions of the architecture draft and 
ASAP drafts

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

(a) Section 2.2.3, Figure 1

The figure indicates SCTP as the transport protocol over which ASAP 
operates for PU<->NS communication.   A mention should be added that this 
communication may also take place over TCP (following the protocol 
specified in 
http://www.ietf.org/internet-drafts/draft-conrad-rserpool-tcpmapping-01.txt)

Note that the figure in 2.2.4 (which has no figure number) is correct in 
indicating only SCTP.

(b)  Section 2.2.5, PU <-> PE Communication

Based on current direction to simplify the protocols, avoiding multiple 
transport registrations, this section should be updated as follows:

An application can interact with an RSerPool implementation in one of two ways:

   (1) a multiplexed control/data channel, where the data channel is 
accessed through RSerPool primitives, where this multiplexed data/control 
channel is one of only two options: (a) a single SCTP association, with 
control/data separated by PPID or (b) a single TCP connection, with 
control/data separated by PPID via the TCP mapping layer described in 
http://www.ietf.org/internet-drafts/draft-conrad-rserpool-tcpmapping-01.txt

   (2) a data channel with NO control channel, where the data channel is 
provided by a transport protocol directly, and is NOT accessed through 
RSerPool primitives.    Note that certain enhanced failover services (e.g. 
business cards, state cookies, message failover) are not available when 
this method of interaction is used.

Note that for a given pool, since a fundamental principle of RSerPool is 
that all PEs provide equivalent service, all PUs and PEs should make the 
same choice for the style of interaction between the applicaiton layer and 
the RSerPool layer: that is, for a given pool, either all PEs and PUs in 
that pool use a multiplexed control/data channel for PE-PU communication,, 
or all PEs and PUs in that pool use a data channel only for PE-PU 
communication.

When the multiplexed control/data channel is used, enhanced failover 
services may be provided, including:

    o  The PE can send a testament (business card) to the PU for providing 
information to
       which other PE the PU should failover in case of a failover.

    o  The PE can send cookies to the PU. The PE would store only the
       last cookie and send it to the new PE in case of a failover.

etc...

(c) 2.3.2 Cookies

"Cookies may be sent from the PE to the PU if the PE wants this to do."

Minor grammar point: "wants to do this"  would sound more natural in 
English. :-)

(d) 2.3.1 vs. 2.3.3... are business cards and testaments the same or 
different concepts?
If they are the same, we should adopt one term or the other.  I like 
"testament" as a good metaphor for the idea of "this is what to do in case 
of my death".  Also, check spelling of "szenario."

now, Comments on 
http://www.ietf.org/internet-drafts/draft-ietf-rserpool-asap-06.txt

(e) In section 4.3, 4.4

cache.populate.request([Pool-Handle |Pool-Element-Handle])
cache.purge.request([Pool-Handle | Pool-Element-Handle])

    Can you help clarify the role and purpose of these from the standpoint 
of the user application code.. are these called
    by the PU? by the PE?    Are they really user service primitives, or 
are they operations that are internal to the PU/PE in response to certain 
message types, but not directly accessible to the user?  An example use 
case might be helpful.


(f) Section 4.5.4.   We have an opportunity to clarify an issue that may be 
a little fuzzy right now: how does a PE "respond" to a message from a PU 
(particularly if that PU is _not_ a PE in any pool).    The easiest way to 
imagine this happening is that when the PE receives a 
data.received.notification, that notification contains either the transport 
address of the PU, or some handle that ASAP can use to refer to that 
address.    The PE then uses the "data.send.request" primitive as per 
section 4.5.4 to transmit the "reply" back to the PU that originated the 
message.

Of course, the actual API may look quite different from this... e.g. the 
"handle" might be the file descriptor that points to a particular SCTP 
association or TCP connection, etc.   but _conceptually_, the 
data.send.primitive by transport addresss is how the PE gets the message 
back to the PU.   And this is something that is a bit mysterious in the 
current versions of the drafts, and which I think we should clear up.


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



From rserpool-admin@ietf.org  Tue Mar 18 19:32: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 TAA08408
	for <rserpool-archive@lists.ietf.org>; Tue, 18 Mar 2003 19:32:19 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2J0nIO02231;
	Tue, 18 Mar 2003 19:49:18 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2J0kvO01987
	for <rserpool@optimus.ietf.org>; Tue, 18 Mar 2003 19:46:57 -0500
Received: from sunserver1.ietf56.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA08083
	for <rserpool@ietf.org>; Tue, 18 Mar 2003 19:29:20 -0500 (EST)
Received: from wl-137-157.wireless.ietf56.ietf.org ([130.129.137.157] helo=motorola.com)
	by sunserver1.ietf56.ietf.org with esmtp (Exim 4.12)
	id 18vRUT-0000qQ-00; Tue, 18 Mar 2003 19:31:33 -0500
Message-ID: <3E77BA8D.E58E3C72@motorola.com>
Date: Tue, 18 Mar 2003 18:32:13 -0600
From: Qiaobing Xie <Qiaobing.Xie@motorola.com>
X-Mailer: Mozilla 4.8 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Phillip Conrad <conrad@acm.org>
CC: Rserpool <rserpool@ietf.org>
Subject: Re: [Rserpool] Issues for architecture draft, asap draft
References: <5.1.1.6.0.20030317133257.01995ea0@joda.cis.temple.edu>
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: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=unsubscribe>
List-Id: Reliable Server Pooling <rserpool.ietf.org>
List-Post: <mailto:rserpool@ietf.org>
List-Help: <mailto:rserpool-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Hi, Phill,

I agree with your comments in general. Just a few minor additions. Pls
see in-line.

regards,
-Qiaobing

Phillip Conrad wrote:
...
> (b)  Section 2.2.5, PU <-> PE Communication
> 
> Based on current direction to simplify the protocols, avoiding multiple
> transport registrations, this section should be updated as follows:
> 
> An application can interact with an RSerPool implementation in one of two ways:
> 
>    (1) a multiplexed control/data channel, where the data channel is
> accessed through RSerPool primitives, where this multiplexed data/control
> channel is one of only two options: (a) a single SCTP association, with
> control/data separated by PPID or (b) a single TCP connection, with
> control/data separated by PPID via the TCP mapping layer described in
> http://www.ietf.org/internet-drafts/draft-conrad-rserpool-tcpmapping-01.txt

ok

> 
>    (2) a data channel with NO control channel, where the data channel is
> provided by a transport protocol directly, and is NOT accessed through
> RSerPool primitives.    

Maybe we should note that if so desired an implementor is of cause still
allowed to build a unified API to handle ASAP messages and user data,
even though the ASAP layer in this case will not touch the user data. 

> Note that certain enhanced failover services (e.g.
> business cards, state cookies, message failover) are not available when
> this method of interaction is used.

Message failover is independent to the existence of a control channel.
Think about the simple case where a PU sends user data to a pool over
SCTP with no control channel. The PU in this case can still enjoy a good
degree of message failover service by using features provided by SCTP
(e.g., ASAP layer in the PU will always be able to re-send to an
alternate PE any un-sent/un-acked messages kicked back by the SCTP assoc
to the failed PE).

How about we change the text to:

====
   (2) a data channel with NO control channel, where the data channel is 
provided by a transport protocol directly, and is NOT accessed through 
RSerPool primitives (Note, an implementor can of cause still choose to
use a unified API to handle ASAP and user messages in his/her
implementation). Note that certain enhanced failover services (e.g.
business cards, state cookies) are not available when this method of
interaction is used.
====

> 
> Note that for a given pool, since a fundamental principle of RSerPool is
> that all PEs provide equivalent service, all PUs and PEs should make the
> same choice for the style of interaction between the applicaiton layer and
> the RSerPool layer: that is, for a given pool, either all PEs and PUs in
> that pool use a multiplexed control/data channel for PE-PU communication,,
> or all PEs and PUs in that pool use a data channel only for PE-PU
> communication.
> 
> When the multiplexed control/data channel is used, enhanced failover
> services may be provided, including:
> 
>     o  The PE can send a testament (business card) to the PU for providing
> information to
>        which other PE the PU should failover in case of a failover.
> 
>     o  The PE can send cookies to the PU. The PE would store only the
>        last cookie and send it to the new PE in case of a failover.
> 
> etc...

Ok.

...
> (d) 2.3.1 vs. 2.3.3... are business cards and testaments the same or
> different concepts?
> If they are the same, we should adopt one term or the other.  I like
> "testament" as a good metaphor for the idea of "this is what to do in case
> of my death".  Also, check spelling of "szenario."

I think the new buz card can be considered to contain the info "I am a
member of pool X". In Randy's old definition, buz-card = new buz-card +
testament. I wouldn't disagree if we want to move back to Randy's old
definition. In that case, we would only need one def. Either way will be
fine with me.

> 
> now, Comments on
> http://www.ietf.org/internet-drafts/draft-ietf-rserpool-asap-06.txt
> 
> (e) In section 4.3, 4.4
> 
> cache.populate.request([Pool-Handle |Pool-Element-Handle])
> cache.purge.request([Pool-Handle | Pool-Element-Handle])
> 
>     Can you help clarify the role and purpose of these from the standpoint
> of the user application code.. are these called
>     by the PU? by the PE?    

By the PU.

> Are they really user service primitives, or
> are they operations that are internal to the PU/PE in response to certain
> message types, but not directly accessible to the user?  An example use
> case might be helpful.

I think they are both user primitives. cache.populate.request is called
whenever the user desires to refresh or pre-fetch the info of a pool
handle in its local cache. cache.purge.request is used by the user to
"forget" a pool (so that when it sends to the same pool next time a
fresh query is guaranteed to occur).

> 
> (f) Section 4.5.4.   We have an opportunity to clarify an issue that may be
> a little fuzzy right now: how does a PE "respond" to a message from a PU
> (particularly if that PU is _not_ a PE in any pool).    The easiest way to
> imagine this happening is that when the PE receives a
> data.received.notification, that notification contains either the transport
> address of the PU, or some handle that ASAP can use to refer to that
> address.    The PE then uses the "data.send.request" primitive as per
> section 4.5.4 to transmit the "reply" back to the PU that originated the
> message.

Yes. 

> Of course, the actual API may look quite different from this... e.g. the
> "handle" might be the file descriptor that points to a particular SCTP
> association or TCP connection, etc.   

agreed.

> but _conceptually_, the
> data.send.primitive by transport addresss is how the PE gets the message
> back to the PU.   And this is something that is a bit mysterious in the
> current versions of the drafts, and which I think we should clear up.

Or a "reply-to-sender" primitive (like in the case of a HTTP server, the
response is sent back to where the query comes from). Of cause, as you
pointed out, the detail is up to the API designer.
_______________________________________________
rserpool mailing list
rserpool@ietf.org
https://www1.ietf.org/mailman/listinfo/rserpool


From mailnull@www1.ietf.org  Tue Mar 18 19:32:50 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 TAA08482
	for <rserpool-archive@odin.ietf.org>; Tue, 18 Mar 2003 19:32:50 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2J0nu302263
	for rserpool-archive@odin.ietf.org; Tue, 18 Mar 2003 19:49:56 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2J0nIO02231;
	Tue, 18 Mar 2003 19:49:18 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2J0kvO01987
	for <rserpool@optimus.ietf.org>; Tue, 18 Mar 2003 19:46:57 -0500
Received: from sunserver1.ietf56.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA08083
	for <rserpool@ietf.org>; Tue, 18 Mar 2003 19:29:20 -0500 (EST)
Received: from wl-137-157.wireless.ietf56.ietf.org ([130.129.137.157] helo=motorola.com)
	by sunserver1.ietf56.ietf.org with esmtp (Exim 4.12)
	id 18vRUT-0000qQ-00; Tue, 18 Mar 2003 19:31:33 -0500
Message-ID: <3E77BA8D.E58E3C72@motorola.com>
Date: Tue, 18 Mar 2003 18:32:13 -0600
From: Qiaobing Xie <Qiaobing.Xie@motorola.com>
X-Mailer: Mozilla 4.8 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Phillip Conrad <conrad@acm.org>
CC: Rserpool <rserpool@ietf.org>
Subject: Re: [Rserpool] Issues for architecture draft, asap draft
References: <5.1.1.6.0.20030317133257.01995ea0@joda.cis.temple.edu>
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: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=unsubscribe>
List-Id: Reliable Server Pooling <rserpool.ietf.org>
List-Post: <mailto:rserpool@ietf.org>
List-Help: <mailto:rserpool-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Hi, Phill,

I agree with your comments in general. Just a few minor additions. Pls
see in-line.

regards,
-Qiaobing

Phillip Conrad wrote:
...
> (b)  Section 2.2.5, PU <-> PE Communication
> 
> Based on current direction to simplify the protocols, avoiding multiple
> transport registrations, this section should be updated as follows:
> 
> An application can interact with an RSerPool implementation in one of two ways:
> 
>    (1) a multiplexed control/data channel, where the data channel is
> accessed through RSerPool primitives, where this multiplexed data/control
> channel is one of only two options: (a) a single SCTP association, with
> control/data separated by PPID or (b) a single TCP connection, with
> control/data separated by PPID via the TCP mapping layer described in
> http://www.ietf.org/internet-drafts/draft-conrad-rserpool-tcpmapping-01.txt

ok

> 
>    (2) a data channel with NO control channel, where the data channel is
> provided by a transport protocol directly, and is NOT accessed through
> RSerPool primitives.    

Maybe we should note that if so desired an implementor is of cause still
allowed to build a unified API to handle ASAP messages and user data,
even though the ASAP layer in this case will not touch the user data. 

> Note that certain enhanced failover services (e.g.
> business cards, state cookies, message failover) are not available when
> this method of interaction is used.

Message failover is independent to the existence of a control channel.
Think about the simple case where a PU sends user data to a pool over
SCTP with no control channel. The PU in this case can still enjoy a good
degree of message failover service by using features provided by SCTP
(e.g., ASAP layer in the PU will always be able to re-send to an
alternate PE any un-sent/un-acked messages kicked back by the SCTP assoc
to the failed PE).

How about we change the text to:

====
   (2) a data channel with NO control channel, where the data channel is 
provided by a transport protocol directly, and is NOT accessed through 
RSerPool primitives (Note, an implementor can of cause still choose to
use a unified API to handle ASAP and user messages in his/her
implementation). Note that certain enhanced failover services (e.g.
business cards, state cookies) are not available when this method of
interaction is used.
====

> 
> Note that for a given pool, since a fundamental principle of RSerPool is
> that all PEs provide equivalent service, all PUs and PEs should make the
> same choice for the style of interaction between the applicaiton layer and
> the RSerPool layer: that is, for a given pool, either all PEs and PUs in
> that pool use a multiplexed control/data channel for PE-PU communication,,
> or all PEs and PUs in that pool use a data channel only for PE-PU
> communication.
> 
> When the multiplexed control/data channel is used, enhanced failover
> services may be provided, including:
> 
>     o  The PE can send a testament (business card) to the PU for providing
> information to
>        which other PE the PU should failover in case of a failover.
> 
>     o  The PE can send cookies to the PU. The PE would store only the
>        last cookie and send it to the new PE in case of a failover.
> 
> etc...

Ok.

...
> (d) 2.3.1 vs. 2.3.3... are business cards and testaments the same or
> different concepts?
> If they are the same, we should adopt one term or the other.  I like
> "testament" as a good metaphor for the idea of "this is what to do in case
> of my death".  Also, check spelling of "szenario."

I think the new buz card can be considered to contain the info "I am a
member of pool X". In Randy's old definition, buz-card = new buz-card +
testament. I wouldn't disagree if we want to move back to Randy's old
definition. In that case, we would only need one def. Either way will be
fine with me.

> 
> now, Comments on
> http://www.ietf.org/internet-drafts/draft-ietf-rserpool-asap-06.txt
> 
> (e) In section 4.3, 4.4
> 
> cache.populate.request([Pool-Handle |Pool-Element-Handle])
> cache.purge.request([Pool-Handle | Pool-Element-Handle])
> 
>     Can you help clarify the role and purpose of these from the standpoint
> of the user application code.. are these called
>     by the PU? by the PE?    

By the PU.

> Are they really user service primitives, or
> are they operations that are internal to the PU/PE in response to certain
> message types, but not directly accessible to the user?  An example use
> case might be helpful.

I think they are both user primitives. cache.populate.request is called
whenever the user desires to refresh or pre-fetch the info of a pool
handle in its local cache. cache.purge.request is used by the user to
"forget" a pool (so that when it sends to the same pool next time a
fresh query is guaranteed to occur).

> 
> (f) Section 4.5.4.   We have an opportunity to clarify an issue that may be
> a little fuzzy right now: how does a PE "respond" to a message from a PU
> (particularly if that PU is _not_ a PE in any pool).    The easiest way to
> imagine this happening is that when the PE receives a
> data.received.notification, that notification contains either the transport
> address of the PU, or some handle that ASAP can use to refer to that
> address.    The PE then uses the "data.send.request" primitive as per
> section 4.5.4 to transmit the "reply" back to the PU that originated the
> message.

Yes. 

> Of course, the actual API may look quite different from this... e.g. the
> "handle" might be the file descriptor that points to a particular SCTP
> association or TCP connection, etc.   

agreed.

> but _conceptually_, the
> data.send.primitive by transport addresss is how the PE gets the message
> back to the PU.   And this is something that is a bit mysterious in the
> current versions of the drafts, and which I think we should clear up.

Or a "reply-to-sender" primitive (like in the case of a HTTP server, the
response is sent back to where the query comes from). Of cause, as you
pointed out, the detail is up to the API designer.
_______________________________________________
rserpool mailing list
rserpool@ietf.org
https://www1.ietf.org/mailman/listinfo/rserpool



From rserpool-admin@ietf.org  Wed Mar 19 03:06:10 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 DAA15716
	for <rserpool-archive@lists.ietf.org>; Wed, 19 Mar 2003 03:06:10 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2J8NFO09565;
	Wed, 19 Mar 2003 03:23:15 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2J8KYO09493
	for <rserpool@optimus.ietf.org>; Wed, 19 Mar 2003 03:20:34 -0500
Received: from snipe.mail.pas.earthlink.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA15677
	for <rserpool@ietf.org>; Wed, 19 Mar 2003 03:02:47 -0500 (EST)
Received: from user-2ivfj81.dialup.mindspring.com ([165.247.205.1] helo=ROVER.acm.org)
	by snipe.mail.pas.earthlink.net with esmtp (Exim 3.33 #1)
	id 18vYZ9-0005up-00; Wed, 19 Mar 2003 00:04:51 -0800
Message-Id: <5.1.1.6.0.20030318234337.028bdc60@joda.cis.temple.edu>
X-Sender: phillipconrad@earthlink.net@mail.earthlink.net
X-Mailer: QUALCOMM Windows Eudora Version 5.1.1
Date: Wed, 19 Mar 2003 00:04:36 -0800
To: Qiaobing Xie <Qiaobing.Xie@motorola.com>, Phillip Conrad <conrad@acm.org>
From: Phillip Conrad <conrad@acm.org>
Subject: Re: [Rserpool] Issues for architecture draft, asap draft
Cc: Rserpool <rserpool@ietf.org>
In-Reply-To: <3E77BA8D.E58E3C72@motorola.com>
References: <5.1.1.6.0.20030317133257.01995ea0@joda.cis.temple.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: rserpool-admin@ietf.org
Errors-To: rserpool-admin@ietf.org
X-BeenThere: rserpool@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=unsubscribe>
List-Id: Reliable Server Pooling <rserpool.ietf.org>
List-Post: <mailto:rserpool@ietf.org>
List-Help: <mailto:rserpool-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=subscribe>

Some replies to a subset of your comments inline (the omitted ones are 
places where we are generally in accord)

At 06:32 PM 3/18/2003 -0600, Qiaobing Xie wrote:
> > An application can interact with an RSerPool implementation in one of 
> two ways:
> >
> >    (1) a multiplexed control/data channel, where the data channel is
> > accessed through RSerPool primitives, where this multiplexed data/control
> > channel is one of only two options: (a) a single SCTP association, with
> > control/data separated by PPID or (b) a single TCP connection, with
> > control/data separated by PPID via the TCP mapping layer described in
> > http://www.ietf.org/internet-drafts/draft-conrad-rserpool-tcpmapping-01.txt
>
>ok
>
> >
> >    (2) a data channel with NO control channel, where the data channel is
> > provided by a transport protocol directly, and is NOT accessed through
> > RSerPool primitives.
>
>Maybe we should note that if so desired an implementor is of cause still
>allowed to build a unified API to handle ASAP messages and user data,
>even though the ASAP layer in this case will not touch the user data.

I agree to the extent that what you indicate is true... an API could 
certainly be built that way.   On the other hand, I wonder why you feel 
this needs to be noted.   My sense is that in the first of these two modes, 
a unified API is required, and in the second mode, a unified API, while it 
could be built, adds no value whatsoever.

   When you are in "mode one", you certainly are sending all your user data 
messages through a unified RSerPool (ASAP) API.

But when you are in "mode two", there really aren't any ASAP messages 
except between PU and ENRP server.   So, why would it make sense to build a 
unified API, especially if that API just ends up being a straight pass 
through for the native transport protocol API?  It seems like a waste of 
time, particularly since part of the point of mode two is to allow "any 
arbitrary transport"to be used.   Any "unified API" you build would 
necessarily limit the underlying transports to the ones that unified API is 
designed to support.

Perhaps  I am not clear on your meaning.

In any case, I'm not sure if the ASAP draft is the right place to make this 
note...  perhaps it should go in the API draft instead.  However, on this 
point I only have a "concern", not a strong objection.   I would defer to 
the lead author of the ASAP draft to decide which way to go here; perhaps 
he will perceive your intent more clearly than I. :-)

  In any case, if it doesn't make it into the ASAP draft, we can 
certainly  note it in the API draft.


> > Note that certain enhanced failover services (e.g.
> > business cards, state cookies, message failover) are not available when
> > this method of interaction is used.
>
>Message failover is independent to the existence of a control channel.
>Think about the simple case where a PU sends user data to a pool over
>SCTP with no control channel. The PU in this case can still enjoy a good
>degree of message failover service by using features provided by SCTP
>(e.g., ASAP layer in the PU will always be able to re-send to an
>alternate PE any un-sent/un-acked messages kicked back by the SCTP assoc
>to the failed PE).
>
>How about we change the text to:
>
>====
>    (2) a data channel with NO control channel, where the data channel is
>provided by a transport protocol directly, and is NOT accessed through
>RSerPool primitives (Note, an implementor can of cause still choose to
>use a unified API to handle ASAP and user messages in his/her
>implementation). Note that certain enhanced failover services (e.g.
>business cards, state cookies) are not available when this method of
>interaction is used.
>====

OK, now I think I see where you are going with this.  You want to failover 
user messages, even when we are in mode two (perhaps, for example, UDP or 
DCCP messages).

You are right, of course, that we do not need a control channel in order to 
be able to failover user messages.. only a unified API that understands 
multiple transports.

I'm concerned that this is a slippery slope to extra complexity, something 
we are trying to get away from.   But we can try to accommodate this... 
perhaps it will not be as complex as I fear.   Let me think about it, and 
see if I can write some text that will take your wishes here into account.

...
> > (e) In section 4.3, 4.4
> >
> > cache.populate.request([Pool-Handle |Pool-Element-Handle])
> > cache.purge.request([Pool-Handle | Pool-Element-Handle])
> >
> >     Can you help clarify the role and purpose of these from the standpoint
> > of the user application code.. are these called
> >     by the PU? by the PE?
>
>By the PU.
>
> > Are they really user service primitives, or
> > are they operations that are internal to the PU/PE in response to certain
> > message types, but not directly accessible to the user?  An example use
> > case might be helpful.
>
>I think they are both user primitives. cache.populate.request is called
>whenever the user desires to refresh or pre-fetch the info of a pool
>handle in its local cache. cache.purge.request is used by the user to
>"forget" a pool (so that when it sends to the same pool next time a
>fresh query is guaranteed to occur).

Ok.. thanks.. that explanation helps.    We may want to include some text 
like that in the draft to clarify this.

...

Thanks for reading and providing thoughtful comments!

Best Regards,
Phill

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


From mailnull@www1.ietf.org  Wed Mar 19 03:06:42 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 DAA15733
	for <rserpool-archive@odin.ietf.org>; Wed, 19 Mar 2003 03:06:42 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2J8NwY09587
	for rserpool-archive@odin.ietf.org; Wed, 19 Mar 2003 03:23:58 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2J8NFO09565;
	Wed, 19 Mar 2003 03:23:15 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2J8KYO09493
	for <rserpool@optimus.ietf.org>; Wed, 19 Mar 2003 03:20:34 -0500
Received: from snipe.mail.pas.earthlink.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA15677
	for <rserpool@ietf.org>; Wed, 19 Mar 2003 03:02:47 -0500 (EST)
Received: from user-2ivfj81.dialup.mindspring.com ([165.247.205.1] helo=ROVER.acm.org)
	by snipe.mail.pas.earthlink.net with esmtp (Exim 3.33 #1)
	id 18vYZ9-0005up-00; Wed, 19 Mar 2003 00:04:51 -0800
Message-Id: <5.1.1.6.0.20030318234337.028bdc60@joda.cis.temple.edu>
X-Sender: phillipconrad@earthlink.net@mail.earthlink.net
X-Mailer: QUALCOMM Windows Eudora Version 5.1.1
Date: Wed, 19 Mar 2003 00:04:36 -0800
To: Qiaobing Xie <Qiaobing.Xie@motorola.com>, Phillip Conrad <conrad@acm.org>
From: Phillip Conrad <conrad@acm.org>
Subject: Re: [Rserpool] Issues for architecture draft, asap draft
Cc: Rserpool <rserpool@ietf.org>
In-Reply-To: <3E77BA8D.E58E3C72@motorola.com>
References: <5.1.1.6.0.20030317133257.01995ea0@joda.cis.temple.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: rserpool-admin@ietf.org
Errors-To: rserpool-admin@ietf.org
X-BeenThere: rserpool@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=unsubscribe>
List-Id: Reliable Server Pooling <rserpool.ietf.org>
List-Post: <mailto:rserpool@ietf.org>
List-Help: <mailto:rserpool-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=subscribe>

Some replies to a subset of your comments inline (the omitted ones are 
places where we are generally in accord)

At 06:32 PM 3/18/2003 -0600, Qiaobing Xie wrote:
> > An application can interact with an RSerPool implementation in one of 
> two ways:
> >
> >    (1) a multiplexed control/data channel, where the data channel is
> > accessed through RSerPool primitives, where this multiplexed data/control
> > channel is one of only two options: (a) a single SCTP association, with
> > control/data separated by PPID or (b) a single TCP connection, with
> > control/data separated by PPID via the TCP mapping layer described in
> > http://www.ietf.org/internet-drafts/draft-conrad-rserpool-tcpmapping-01.txt
>
>ok
>
> >
> >    (2) a data channel with NO control channel, where the data channel is
> > provided by a transport protocol directly, and is NOT accessed through
> > RSerPool primitives.
>
>Maybe we should note that if so desired an implementor is of cause still
>allowed to build a unified API to handle ASAP messages and user data,
>even though the ASAP layer in this case will not touch the user data.

I agree to the extent that what you indicate is true... an API could 
certainly be built that way.   On the other hand, I wonder why you feel 
this needs to be noted.   My sense is that in the first of these two modes, 
a unified API is required, and in the second mode, a unified API, while it 
could be built, adds no value whatsoever.

   When you are in "mode one", you certainly are sending all your user data 
messages through a unified RSerPool (ASAP) API.

But when you are in "mode two", there really aren't any ASAP messages 
except between PU and ENRP server.   So, why would it make sense to build a 
unified API, especially if that API just ends up being a straight pass 
through for the native transport protocol API?  It seems like a waste of 
time, particularly since part of the point of mode two is to allow "any 
arbitrary transport"to be used.   Any "unified API" you build would 
necessarily limit the underlying transports to the ones that unified API is 
designed to support.

Perhaps  I am not clear on your meaning.

In any case, I'm not sure if the ASAP draft is the right place to make this 
note...  perhaps it should go in the API draft instead.  However, on this 
point I only have a "concern", not a strong objection.   I would defer to 
the lead author of the ASAP draft to decide which way to go here; perhaps 
he will perceive your intent more clearly than I. :-)

  In any case, if it doesn't make it into the ASAP draft, we can 
certainly  note it in the API draft.


> > Note that certain enhanced failover services (e.g.
> > business cards, state cookies, message failover) are not available when
> > this method of interaction is used.
>
>Message failover is independent to the existence of a control channel.
>Think about the simple case where a PU sends user data to a pool over
>SCTP with no control channel. The PU in this case can still enjoy a good
>degree of message failover service by using features provided by SCTP
>(e.g., ASAP layer in the PU will always be able to re-send to an
>alternate PE any un-sent/un-acked messages kicked back by the SCTP assoc
>to the failed PE).
>
>How about we change the text to:
>
>====
>    (2) a data channel with NO control channel, where the data channel is
>provided by a transport protocol directly, and is NOT accessed through
>RSerPool primitives (Note, an implementor can of cause still choose to
>use a unified API to handle ASAP and user messages in his/her
>implementation). Note that certain enhanced failover services (e.g.
>business cards, state cookies) are not available when this method of
>interaction is used.
>====

OK, now I think I see where you are going with this.  You want to failover 
user messages, even when we are in mode two (perhaps, for example, UDP or 
DCCP messages).

You are right, of course, that we do not need a control channel in order to 
be able to failover user messages.. only a unified API that understands 
multiple transports.

I'm concerned that this is a slippery slope to extra complexity, something 
we are trying to get away from.   But we can try to accommodate this... 
perhaps it will not be as complex as I fear.   Let me think about it, and 
see if I can write some text that will take your wishes here into account.

...
> > (e) In section 4.3, 4.4
> >
> > cache.populate.request([Pool-Handle |Pool-Element-Handle])
> > cache.purge.request([Pool-Handle | Pool-Element-Handle])
> >
> >     Can you help clarify the role and purpose of these from the standpoint
> > of the user application code.. are these called
> >     by the PU? by the PE?
>
>By the PU.
>
> > Are they really user service primitives, or
> > are they operations that are internal to the PU/PE in response to certain
> > message types, but not directly accessible to the user?  An example use
> > case might be helpful.
>
>I think they are both user primitives. cache.populate.request is called
>whenever the user desires to refresh or pre-fetch the info of a pool
>handle in its local cache. cache.purge.request is used by the user to
>"forget" a pool (so that when it sends to the same pool next time a
>fresh query is guaranteed to occur).

Ok.. thanks.. that explanation helps.    We may want to include some text 
like that in the draft to clarify this.

...

Thanks for reading and providing thoughtful comments!

Best Regards,
Phill

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



From rserpool-admin@ietf.org  Wed Mar 19 16:36:05 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 QAA10163
	for <rserpool-archive@lists.ietf.org>; Wed, 19 Mar 2003 16:36:05 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2JLrSO08891;
	Wed, 19 Mar 2003 16:53:28 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2JLqGO08770
	for <rserpool@optimus.ietf.org>; Wed, 19 Mar 2003 16:52:16 -0500
Received: from sunserver1.ietf56.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA10033
	for <rserpool@ietf.org>; Wed, 19 Mar 2003 16:34:11 -0500 (EST)
Received: from wl-137-157.wireless.ietf56.ietf.org ([130.129.137.157] helo=motorola.com)
	by sunserver1.ietf56.ietf.org with esmtp (Exim 4.12)
	id 18vlEX-0002Yt-00; Wed, 19 Mar 2003 16:36:25 -0500
Message-ID: <3E78E34A.A851D8D7@motorola.com>
Date: Wed, 19 Mar 2003 15:38:18 -0600
From: Qiaobing Xie <Qiaobing.Xie@motorola.com>
X-Mailer: Mozilla 4.8 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Phillip Conrad <conrad@acm.org>
CC: Rserpool <rserpool@ietf.org>
Subject: Re: [Rserpool] Issues for architecture draft, asap draft
References: <5.1.1.6.0.20030317133257.01995ea0@joda.cis.temple.edu> <5.1.1.6.0.20030318234337.028bdc60@joda.cis.temple.edu>
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: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=unsubscribe>
List-Id: Reliable Server Pooling <rserpool.ietf.org>
List-Post: <mailto:rserpool@ietf.org>
List-Help: <mailto:rserpool-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Hi, Phill,

Please see my comments in-line.

Phillip Conrad wrote:
.....
> >Maybe we should note that if so desired an implementor is of cause still
> >allowed to build a unified API to handle ASAP messages and user data,
> >even though the ASAP layer in this case will not touch the user data.
> 
> I agree to the extent that what you indicate is true... an API could
> certainly be built that way.   On the other hand, I wonder why you feel
> this needs to be noted.   My sense is that in the first of these two modes,
> a unified API is required, and in the second mode, a unified API, while it
> could be built, adds no value whatsoever.

I think we are in general agreement here. I guess my intention to have
this noted is to avoid give the reader the wrong impression that two
different styles of implementation are required to use the two operation
modes. 

In fact, the most likely (and also the highly recommended, IMHO)
implementation scenario should be to have a single Rserpool stack with a
single "socket-like" API. And the same stack and API should always be
capable of supporting both modes. It is only when a PU or PE app is
built on top of this common stack, based on the nature of the
application, the app developer then make the choice of whether to use a
control channel or not (in fact the PU or PE may even make this choice
dynamically based the current sys configuration). In such a scenario, it
would be more nature and easier to me that the same unified API would be
used no matter whether or not a control channel is used. On the other
hand, to make the app use a unified API when control channel is used but
a separate API when no control channel is used of cause is do-able, but
it may turn out to be a more complicated implementation approach.

> 
>    When you are in "mode one", you certainly are sending all your user data
> messages through a unified RSerPool (ASAP) API.
> 
> But when you are in "mode two", there really aren't any ASAP messages
> except between PU and ENRP server.   So, why would it make sense to build a
> unified API, especially if that API just ends up being a straight pass
> through for the native transport protocol API?  It seems like a waste of
> time, particularly since part of the point of mode two is to allow "any
> arbitrary transport"to be used.   Any "unified API" you build would
> necessarily limit the underlying transports to the ones that unified API is
> designed to support.

ditto.

> 
> Perhaps  I am not clear on your meaning.
> 
> In any case, I'm not sure if the ASAP draft is the right place to make this
> note...  perhaps it should go in the API draft instead.  However, on this
> point I only have a "concern", not a strong objection.   I would defer to
> the lead author of the ASAP draft to decide which way to go here; perhaps
> he will perceive your intent more clearly than I. :-)
> 
>   In any case, if it doesn't make it into the ASAP draft, we can
> certainly  note it in the API draft.

Either place would be fine, as long as the intention is worded in a
consistent way.

> 
> > > Note that certain enhanced failover services (e.g.
> > > business cards, state cookies, message failover) are not available when
> > > this method of interaction is used.
> >
> >Message failover is independent to the existence of a control channel.
> >Think about the simple case where a PU sends user data to a pool over
> >SCTP with no control channel. The PU in this case can still enjoy a good
> >degree of message failover service by using features provided by SCTP
> >(e.g., ASAP layer in the PU will always be able to re-send to an
> >alternate PE any un-sent/un-acked messages kicked back by the SCTP assoc
> >to the failed PE).
> >
> >How about we change the text to:
> >
> >====
> >    (2) a data channel with NO control channel, where the data channel is
> >provided by a transport protocol directly, and is NOT accessed through
> >RSerPool primitives (Note, an implementor can of cause still choose to
> >use a unified API to handle ASAP and user messages in his/her
> >implementation). Note that certain enhanced failover services (e.g.
> >business cards, state cookies) are not available when this method of
> >interaction is used.
> >====
> 
> OK, now I think I see where you are going with this.  You want to failover
> user messages, even when we are in mode two (perhaps, for example, UDP or
> DCCP messages).
> 
> You are right, of course, that we do not need a control channel in order to
> be able to failover user messages.. only a unified API that understands
> multiple transports.

yes. We always assume the ASAP implementation would be able to handle
this.

> 
> I'm concerned that this is a slippery slope to extra complexity, something
> we are trying to get away from.   But we can try to accommodate this...
> perhaps it will not be as complex as I fear.   Let me think about it, and
> see if I can write some text that will take your wishes here into account.

I think it is not complicated. As we talked about at the meeting, we
should always remind the implementor to build a full stack capable of
operating in both modes. We should discourage them to build incomplete
stack that only do a subset of Rserpool.

regards,
-Qiaobing
_______________________________________________
rserpool mailing list
rserpool@ietf.org
https://www1.ietf.org/mailman/listinfo/rserpool


From mailnull@www1.ietf.org  Wed Mar 19 16:36:37 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 QAA10187
	for <rserpool-archive@odin.ietf.org>; Wed, 19 Mar 2003 16:36:37 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2JLsAF08988
	for rserpool-archive@odin.ietf.org; Wed, 19 Mar 2003 16:54:10 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2JLrSO08891;
	Wed, 19 Mar 2003 16:53:28 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2JLqGO08770
	for <rserpool@optimus.ietf.org>; Wed, 19 Mar 2003 16:52:16 -0500
Received: from sunserver1.ietf56.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA10033
	for <rserpool@ietf.org>; Wed, 19 Mar 2003 16:34:11 -0500 (EST)
Received: from wl-137-157.wireless.ietf56.ietf.org ([130.129.137.157] helo=motorola.com)
	by sunserver1.ietf56.ietf.org with esmtp (Exim 4.12)
	id 18vlEX-0002Yt-00; Wed, 19 Mar 2003 16:36:25 -0500
Message-ID: <3E78E34A.A851D8D7@motorola.com>
Date: Wed, 19 Mar 2003 15:38:18 -0600
From: Qiaobing Xie <Qiaobing.Xie@motorola.com>
X-Mailer: Mozilla 4.8 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Phillip Conrad <conrad@acm.org>
CC: Rserpool <rserpool@ietf.org>
Subject: Re: [Rserpool] Issues for architecture draft, asap draft
References: <5.1.1.6.0.20030317133257.01995ea0@joda.cis.temple.edu> <5.1.1.6.0.20030318234337.028bdc60@joda.cis.temple.edu>
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: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=unsubscribe>
List-Id: Reliable Server Pooling <rserpool.ietf.org>
List-Post: <mailto:rserpool@ietf.org>
List-Help: <mailto:rserpool-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Hi, Phill,

Please see my comments in-line.

Phillip Conrad wrote:
.....
> >Maybe we should note that if so desired an implementor is of cause still
> >allowed to build a unified API to handle ASAP messages and user data,
> >even though the ASAP layer in this case will not touch the user data.
> 
> I agree to the extent that what you indicate is true... an API could
> certainly be built that way.   On the other hand, I wonder why you feel
> this needs to be noted.   My sense is that in the first of these two modes,
> a unified API is required, and in the second mode, a unified API, while it
> could be built, adds no value whatsoever.

I think we are in general agreement here. I guess my intention to have
this noted is to avoid give the reader the wrong impression that two
different styles of implementation are required to use the two operation
modes. 

In fact, the most likely (and also the highly recommended, IMHO)
implementation scenario should be to have a single Rserpool stack with a
single "socket-like" API. And the same stack and API should always be
capable of supporting both modes. It is only when a PU or PE app is
built on top of this common stack, based on the nature of the
application, the app developer then make the choice of whether to use a
control channel or not (in fact the PU or PE may even make this choice
dynamically based the current sys configuration). In such a scenario, it
would be more nature and easier to me that the same unified API would be
used no matter whether or not a control channel is used. On the other
hand, to make the app use a unified API when control channel is used but
a separate API when no control channel is used of cause is do-able, but
it may turn out to be a more complicated implementation approach.

> 
>    When you are in "mode one", you certainly are sending all your user data
> messages through a unified RSerPool (ASAP) API.
> 
> But when you are in "mode two", there really aren't any ASAP messages
> except between PU and ENRP server.   So, why would it make sense to build a
> unified API, especially if that API just ends up being a straight pass
> through for the native transport protocol API?  It seems like a waste of
> time, particularly since part of the point of mode two is to allow "any
> arbitrary transport"to be used.   Any "unified API" you build would
> necessarily limit the underlying transports to the ones that unified API is
> designed to support.

ditto.

> 
> Perhaps  I am not clear on your meaning.
> 
> In any case, I'm not sure if the ASAP draft is the right place to make this
> note...  perhaps it should go in the API draft instead.  However, on this
> point I only have a "concern", not a strong objection.   I would defer to
> the lead author of the ASAP draft to decide which way to go here; perhaps
> he will perceive your intent more clearly than I. :-)
> 
>   In any case, if it doesn't make it into the ASAP draft, we can
> certainly  note it in the API draft.

Either place would be fine, as long as the intention is worded in a
consistent way.

> 
> > > Note that certain enhanced failover services (e.g.
> > > business cards, state cookies, message failover) are not available when
> > > this method of interaction is used.
> >
> >Message failover is independent to the existence of a control channel.
> >Think about the simple case where a PU sends user data to a pool over
> >SCTP with no control channel. The PU in this case can still enjoy a good
> >degree of message failover service by using features provided by SCTP
> >(e.g., ASAP layer in the PU will always be able to re-send to an
> >alternate PE any un-sent/un-acked messages kicked back by the SCTP assoc
> >to the failed PE).
> >
> >How about we change the text to:
> >
> >====
> >    (2) a data channel with NO control channel, where the data channel is
> >provided by a transport protocol directly, and is NOT accessed through
> >RSerPool primitives (Note, an implementor can of cause still choose to
> >use a unified API to handle ASAP and user messages in his/her
> >implementation). Note that certain enhanced failover services (e.g.
> >business cards, state cookies) are not available when this method of
> >interaction is used.
> >====
> 
> OK, now I think I see where you are going with this.  You want to failover
> user messages, even when we are in mode two (perhaps, for example, UDP or
> DCCP messages).
> 
> You are right, of course, that we do not need a control channel in order to
> be able to failover user messages.. only a unified API that understands
> multiple transports.

yes. We always assume the ASAP implementation would be able to handle
this.

> 
> I'm concerned that this is a slippery slope to extra complexity, something
> we are trying to get away from.   But we can try to accommodate this...
> perhaps it will not be as complex as I fear.   Let me think about it, and
> see if I can write some text that will take your wishes here into account.

I think it is not complicated. As we talked about at the meeting, we
should always remind the implementor to build a full stack capable of
operating in both modes. We should discourage them to build incomplete
stack that only do a subset of Rserpool.

regards,
-Qiaobing
_______________________________________________
rserpool mailing list
rserpool@ietf.org
https://www1.ietf.org/mailman/listinfo/rserpool



From rserpool-admin@ietf.org  Fri Mar 21 05:17: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 FAA09589
	for <rserpool-archive@lists.ietf.org>; Fri, 21 Mar 2003 05:17:17 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2LAZKO26044;
	Fri, 21 Mar 2003 05:35:20 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2LAYXO26007
	for <rserpool@optimus.ietf.org>; Fri, 21 Mar 2003 05:34:33 -0500
Received: from hal-4.inet.it (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA09574
	for <rserpool@ietf.org>; Fri, 21 Mar 2003 05:15:42 -0500 (EST)
Received: from  [::ffff:213.92.1.193] by hal-4.inet.it via I-SMTP-4.3.7-430
	id ::ffff:213.92.1.193+I8ogkkCSgL2t; Fri, 21 Mar 2003 11:17:43 +0100
Date: Fri, 21 Mar 2003 11:20:33 +0100
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v551)
Cc: Harrie Hazewinkel <harrie@lisanza.net>
To: WG IETF rserpool <rserpool@ietf.org>
From: Harrie Hazewinkel <harrie@jumpy.it>
Content-Transfer-Encoding: 7bit
Message-Id: <BFC8FFD2-5B86-11D7-B329-0003934A5A7E@jumpy.it>
X-Mailer: Apple Mail (2.551)
Content-Transfer-Encoding: 7bit
Subject: [Rserpool] draft-ietf-rserpool-common-param-03.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: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=unsubscribe>
List-Id: Reliable Server Pooling <rserpool.ietf.org>
List-Post: <mailto:rserpool@ietf.org>
List-Help: <mailto:rserpool-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Hi all,


Below some comments on draft-ietf-rserpool-common-param-03.txt.

Harrie

>  Aggregate Server Access Protocol (ASAP) and Endpoint Name  Resolution
>                Protocol (ENRP) common parameters document

'document' adds nothing to the title, I suggest to drop it.

While reading this document, I got the impression that not all
items defined are common for both protocols. Some are for ASAP
and some are for ENRP only. If so, I would suggest to reflect this
in the title, abstract and introduction.
A simple mean to achieve this is to
   do 'common parameters' -> 'parameters'

> Abstract

Abstract equals the Introduction, I suggest a new (following) abstract.

This document details the common parameters of the Aggregate Server
Access Protocol (ASAP) and Endpoint Name Resolution Protocol (ENRP)
protocols defined within the Reliable Server Pooling (RSERPOOL)
architecture.

> 2. Parameters in General
>
>    .. For fields with a length bigger than 4 octets, a
>    number in a pair of parentheses may follow the field name to 
> indicate
>    the length of the field in number of octets.

I do not understand this sentence.

> 3. ENRP-ASAP Common Parameters
>
>    Parameters are defined in the following Type-length-value (TLV)
                                                   ^      ^
NIT: capitals??

>    Parameter Type:  16 bits (unsigned integer)
>
>    The Type field is a 16 bit identifier of the type of parameter.  It
>    takes a value of 0 to 65534.
>
>    The value of 65535 is reserved for IETF-defined extensions.  Values
>    other than those defined in specific ENRP parameter description are
>    reserved for use by IETF.

How can enterprise specifc extensions be done??
Is there a potential future need for this??

>
>    Parameter Value: variable-length.
>
>    The Parameter Value field contains the actual information to be
>    transferred in the parameter.

IMHO, it would clarify if you mention that the

>
>    The total length of a parameter (including Type, Parameter Length 
> and
>    Value fields) MUST be a multiple of 4 bytes.  If the length of the
>    parameter is not a multiple of 4 bytes, the sender pads the 
> Parameter

'the sender pads' -> 'the sender MUST pad'
(although, the MUST is also defined just before)

>    at the end (i.e., after the Parameter Value field) with all zero
>    bytes.  The length of this padding is not included in the parameter
>    length field.  A sender SHOULD NOT pad with more than 3 bytes.  The
>    receiver MUST ignore the padding bytes.

I am not sure, but 'SHOULD NOT' is 'MUST NOT'.
Correct me if I am wrong. Since the padding is not included in the 
length
there is otherwise no way to find out where the new TLV starts.

>
>    (Editor's note: clarify further that any padding inside in the
>    parameter, such as the padding in sub-param is included in the total
>    length)

You could specify that one or more TLVs inside another TLV is just seen
as the parameter value. Then immplicit it is defined and some examples 
can
provide the clarity.



>    The Parameter Types are encoded such that the highest-order two bits
>    specify the action that must be taken if the processing endpoint 
> does
>    not recognize the Parameter Type.

The part above until section 3.1 is better to be moved to the
Parameter Type explaination before. In the document you are now
at Parameter Value and jump back.

> 3.3 SCTP Transport Parameter
>
>    Transport use: 16 bits (unsigned interger)
                                          ^
'interger' -> 'integer'
(Happens for more 'Transport ....' lines)

>    IPv4 or IPv6 Address #1 - #n:
>
>    Each indicates an IPv4 or IPv6 address parameter (as defined above 
> in
>    Section 3.1 and Section 3.2) assigned to this SCTP user transport.
>    At least one IP address parameter MUST be present in an SCTP
>    transport parameter.

Just to be sure, but are IPv4 and IPv6 addresses allowed to be
mixed?? Or is it only IPv4 addresses or only IPv6 addresses??

>
> 3.5 UDP Transport Parameter
>
>    Note: A UDP port MUST NOT be used for control information.  For this
>    reason, no Transport Use field is provided.  UDP MUST always be
>    treated as a "Data Only" type transport use.

Why not 'forcing' the value 'DATA ONLY'??

> 3.6 Pool Member Selection Policy Parameter
>
>    This parameter defines a pool member selection policy.  RSERPOOL
>    supports multiple pool member selection polices and also allows
                                                ^^^
'polices' -> 'policies'

>    definition of new selection polices in the future.
                                     ^^^
'polices' -> 'policies'

>     0                   1                   2                   3
>     0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>    |        Type = 0x6             |      Length = variable        |
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>    | Policy Type   |     Policy-specific Data....
>    +-+-+-+-+-+-+-+-+------------------------------------------------

Why would you suddenly do not align in 4 bytes??


>
>    Length: 16 bits (unsigned integer)
>
>    Indicates the entire length of the parameter in number of octets,
>    including the Type, Length, Policy Type fields, and the
>    Policy-specific Data.

Not sure, but in  the figure is a single 'Policy Type' specified and you
speak here of 'Policy Type fields'.
>
>    Note, the value in Length field will NOT cover any padding at the 
> end
>    of the parameter, if there is one.

'one' -> 'padding' (clarity)

>      Value     Policy
>      -----     ---------
>      0x0       (reserved by IETF)
>      0x1       Round Robin
>      0x2       Least Used
>      0x3       Least Used with Degradation (a.k.a. dog pile)
>      0x4       Weighted Round Robin
>      others    (reserved by IETF)

How are enterprise specific policies handled?? Or is that not foreseen
now and in the future??

>
>    Policy-specific Data:
>
>    The structure and fields for each presently defined policy types are

'types are' -> 'type is'
Not native speaker, but each makes it single, or not??

>    described in detail in the following subsections.  The enforcement
>    rules and handling procedures of these policies are defined in
>    Section xxxxx in ASAP [4].

If those policy types are ASAP specific, maybe the types should be 
described in
that document, since they are not common to ENRP and ASAP.

> 3.6.1 Round Robin Policy
> 3.6.2 Least Used Policy
> 3.6.3 Least Used with Degradation Policy
> 3.6.4 Weighted Round Robin Policy

These are examples of useages from the first format presented in 
section 3.6, right??
I believe it is better to make this more clear, since I was first 
confused if this
needed to go into the 'Policy-specifc Data' field.


>
>
> 3.8 Pool Element Parameter
>
>    This parameter is used in multiple ENRP messages to represent an 
> ASAP
>    endpoint (i.e., a PE in a pool) and the associated information, such
>    as its transport address(es), selection policy, and other 
> operational
>    or status information of the PE.
>
>
>     0                   1                   2                   3
>     0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>    |         Type = 0x8            |       Length=variable         |
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>    |                         PE Identifier                         |
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>    |                  Home ENRP Server Identifier                  |
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>    |                      Registration Life                        |
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>    :                    User Transport param #1                    :
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>    :                    User Transport param #2                    :
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>    :                                                               :
>    :                             .....                             :
>    :                                                               :
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>    :                    User Transport param #k                    :
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>    :                 Member Selection Policy param                 :
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>
>    Member Selection Policy:

I would suggest to move this parameter before the User Transport,
since there is not a specific count of 'User Transport' parameters.
OK, you can calculate it from the length of the complete parameter,
but I beleive it eases implementation.


>    Server Transport:
>
>    This is an SCTP Transport Parameter, as defined in Section 3.3 that
>    contains the network access address(es), SCTP port number, etc.  of
>    the ENRP server.

Is this only SCTP?? (Not sure)

>    Error causes are defined as variable-length parameters using the
>    format described in 3.2.1 of RFC2960 [3], i.e.:

  I suggest the start of new section 'Error Cause Parameter'.
Also why the reference to [3]. Since you copy the complete
definition it is redundant and let people believe this is SCTP.

>    Defines the type of error condition being reported.
>          Cause Code
>          Value           Cause Code
>          ---------      ----------------
>           1              Unrecognized Parameter
>           2              Unrecognized Message
>           3              Invalid Values
>           4              Non-unique PE Identifier
>           5              Pooling Policy Inconsistent
>           6              Lack of Resources
>          other values    reserved by IETF
>
>    Cause-specific Information: variable length

Assuming this is completely implementation dependant, I believe that
in this case also needs something as what caused it. For instance when
error cause '1' happens it must be indicated which parameter it was.
Although, this is maybe protocol specific semantics.

>    The following subsections (Section 3.10.1 - Section 3.10.2) define
>    specific error causes.

1) I believe that only specifying the first 2 error causes is not 
enough.
They all should be defined.

2) Are these really all errors that are possible??

3) How can one make new error causes and/or enterprise specific ones.
Maybe it is better to define this and forsee already how new error 
causes
can be added and how compatibility of implementations that do not know
those new error codes must be handled.
An idea is adding an Unrecognized Error to which it than can be mapped.
>
> 3.13 Communication Restrictions Parameter
>
>    This parameter defines a TLV that can be used by the sender to
>    restrict name server searches to a limited number of transport 
> types.
>
>
>     0                   1                   2                   3
>     0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>    |            Type = 0xd         |         Length=0x8            |
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>    |        Control Type           |          Data Type            |
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

Previous the doc always specifies the item Length also.
Why not here?

>    Type       |    Value
>    -----------+-------------
>    ANY        |   0x0000
>    SCTP ONLY  |   0x0001
>    TCP ONLY   |   0x0002

Why not specifying other as well. Allows extension and backwards 
compatibility
for the future (maybe).
>
>
>    Data Type:  16 bits (unsigned integer)
>
>    This field requests the search be restricted to PE's that have a 
> data
>    channel type of the specified type.  One of the following values 
> MUST
>    be used:
>
>    Type       |    Value
>    -----------+-------------
>    ANY        |   0x0000
>    SCTP ONLY  |   0x0001
>    TCP ONLY   |   0x0002
>    UDP ONLY   |   0x0003

I neither understand why the values of 'Data Type' and 'Control Type'
are different. A 'Control Type' of UDP could be possible. Whether it
will work well is a different thing.

Making these values equal eases it for implementors I guess too.

>
> 4. Common Message Formats
>
>    10 reserved.
>
>    11 reserved.

Although reserved, but what is suggested for to do when these values
are received?? Handle it as '00'?

>    This value represents the size of the message in bytes including the
>    Message Type, Message Flags, Message Length, and Message Value
>    fields.  Therefore, if the Message Value field is zero-length, the
>    Length field will be set to 4.  The Message Length field does not
>    count any padding.
>
>    Note, the value in Message Length field will NOT cover any padding 
> at
>    the end of this message.

The 'Note,..' is equal in semantics to the previous sentence.
IMHO, drop it.

>
> 5. Security Considerations
>
>    Details on ENRP and ASAP security constraints are a addressed in 
> ENRP
                                                        ^

'are a addressed' -> 'are addressed'

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


From mailnull@www1.ietf.org  Fri Mar 21 05:17: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 FAA09605
	for <rserpool-archive@odin.ietf.org>; Fri, 21 Mar 2003 05:17:47 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2LAa5P26061
	for rserpool-archive@odin.ietf.org; Fri, 21 Mar 2003 05:36:05 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2LAZKO26044;
	Fri, 21 Mar 2003 05:35:20 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2LAYXO26007
	for <rserpool@optimus.ietf.org>; Fri, 21 Mar 2003 05:34:33 -0500
Received: from hal-4.inet.it (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA09574
	for <rserpool@ietf.org>; Fri, 21 Mar 2003 05:15:42 -0500 (EST)
Received: from  [::ffff:213.92.1.193] by hal-4.inet.it via I-SMTP-4.3.7-430
	id ::ffff:213.92.1.193+I8ogkkCSgL2t; Fri, 21 Mar 2003 11:17:43 +0100
Date: Fri, 21 Mar 2003 11:20:33 +0100
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v551)
Cc: Harrie Hazewinkel <harrie@lisanza.net>
To: WG IETF rserpool <rserpool@ietf.org>
From: Harrie Hazewinkel <harrie@jumpy.it>
Content-Transfer-Encoding: 7bit
Message-Id: <BFC8FFD2-5B86-11D7-B329-0003934A5A7E@jumpy.it>
X-Mailer: Apple Mail (2.551)
Content-Transfer-Encoding: 7bit
Subject: [Rserpool] draft-ietf-rserpool-common-param-03.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: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=unsubscribe>
List-Id: Reliable Server Pooling <rserpool.ietf.org>
List-Post: <mailto:rserpool@ietf.org>
List-Help: <mailto:rserpool-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Hi all,


Below some comments on draft-ietf-rserpool-common-param-03.txt.

Harrie

>  Aggregate Server Access Protocol (ASAP) and Endpoint Name  Resolution
>                Protocol (ENRP) common parameters document

'document' adds nothing to the title, I suggest to drop it.

While reading this document, I got the impression that not all
items defined are common for both protocols. Some are for ASAP
and some are for ENRP only. If so, I would suggest to reflect this
in the title, abstract and introduction.
A simple mean to achieve this is to
   do 'common parameters' -> 'parameters'

> Abstract

Abstract equals the Introduction, I suggest a new (following) abstract.

This document details the common parameters of the Aggregate Server
Access Protocol (ASAP) and Endpoint Name Resolution Protocol (ENRP)
protocols defined within the Reliable Server Pooling (RSERPOOL)
architecture.

> 2. Parameters in General
>
>    .. For fields with a length bigger than 4 octets, a
>    number in a pair of parentheses may follow the field name to 
> indicate
>    the length of the field in number of octets.

I do not understand this sentence.

> 3. ENRP-ASAP Common Parameters
>
>    Parameters are defined in the following Type-length-value (TLV)
                                                   ^      ^
NIT: capitals??

>    Parameter Type:  16 bits (unsigned integer)
>
>    The Type field is a 16 bit identifier of the type of parameter.  It
>    takes a value of 0 to 65534.
>
>    The value of 65535 is reserved for IETF-defined extensions.  Values
>    other than those defined in specific ENRP parameter description are
>    reserved for use by IETF.

How can enterprise specifc extensions be done??
Is there a potential future need for this??

>
>    Parameter Value: variable-length.
>
>    The Parameter Value field contains the actual information to be
>    transferred in the parameter.

IMHO, it would clarify if you mention that the

>
>    The total length of a parameter (including Type, Parameter Length 
> and
>    Value fields) MUST be a multiple of 4 bytes.  If the length of the
>    parameter is not a multiple of 4 bytes, the sender pads the 
> Parameter

'the sender pads' -> 'the sender MUST pad'
(although, the MUST is also defined just before)

>    at the end (i.e., after the Parameter Value field) with all zero
>    bytes.  The length of this padding is not included in the parameter
>    length field.  A sender SHOULD NOT pad with more than 3 bytes.  The
>    receiver MUST ignore the padding bytes.

I am not sure, but 'SHOULD NOT' is 'MUST NOT'.
Correct me if I am wrong. Since the padding is not included in the 
length
there is otherwise no way to find out where the new TLV starts.

>
>    (Editor's note: clarify further that any padding inside in the
>    parameter, such as the padding in sub-param is included in the total
>    length)

You could specify that one or more TLVs inside another TLV is just seen
as the parameter value. Then immplicit it is defined and some examples 
can
provide the clarity.



>    The Parameter Types are encoded such that the highest-order two bits
>    specify the action that must be taken if the processing endpoint 
> does
>    not recognize the Parameter Type.

The part above until section 3.1 is better to be moved to the
Parameter Type explaination before. In the document you are now
at Parameter Value and jump back.

> 3.3 SCTP Transport Parameter
>
>    Transport use: 16 bits (unsigned interger)
                                          ^
'interger' -> 'integer'
(Happens for more 'Transport ....' lines)

>    IPv4 or IPv6 Address #1 - #n:
>
>    Each indicates an IPv4 or IPv6 address parameter (as defined above 
> in
>    Section 3.1 and Section 3.2) assigned to this SCTP user transport.
>    At least one IP address parameter MUST be present in an SCTP
>    transport parameter.

Just to be sure, but are IPv4 and IPv6 addresses allowed to be
mixed?? Or is it only IPv4 addresses or only IPv6 addresses??

>
> 3.5 UDP Transport Parameter
>
>    Note: A UDP port MUST NOT be used for control information.  For this
>    reason, no Transport Use field is provided.  UDP MUST always be
>    treated as a "Data Only" type transport use.

Why not 'forcing' the value 'DATA ONLY'??

> 3.6 Pool Member Selection Policy Parameter
>
>    This parameter defines a pool member selection policy.  RSERPOOL
>    supports multiple pool member selection polices and also allows
                                                ^^^
'polices' -> 'policies'

>    definition of new selection polices in the future.
                                     ^^^
'polices' -> 'policies'

>     0                   1                   2                   3
>     0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>    |        Type = 0x6             |      Length = variable        |
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>    | Policy Type   |     Policy-specific Data....
>    +-+-+-+-+-+-+-+-+------------------------------------------------

Why would you suddenly do not align in 4 bytes??


>
>    Length: 16 bits (unsigned integer)
>
>    Indicates the entire length of the parameter in number of octets,
>    including the Type, Length, Policy Type fields, and the
>    Policy-specific Data.

Not sure, but in  the figure is a single 'Policy Type' specified and you
speak here of 'Policy Type fields'.
>
>    Note, the value in Length field will NOT cover any padding at the 
> end
>    of the parameter, if there is one.

'one' -> 'padding' (clarity)

>      Value     Policy
>      -----     ---------
>      0x0       (reserved by IETF)
>      0x1       Round Robin
>      0x2       Least Used
>      0x3       Least Used with Degradation (a.k.a. dog pile)
>      0x4       Weighted Round Robin
>      others    (reserved by IETF)

How are enterprise specific policies handled?? Or is that not foreseen
now and in the future??

>
>    Policy-specific Data:
>
>    The structure and fields for each presently defined policy types are

'types are' -> 'type is'
Not native speaker, but each makes it single, or not??

>    described in detail in the following subsections.  The enforcement
>    rules and handling procedures of these policies are defined in
>    Section xxxxx in ASAP [4].

If those policy types are ASAP specific, maybe the types should be 
described in
that document, since they are not common to ENRP and ASAP.

> 3.6.1 Round Robin Policy
> 3.6.2 Least Used Policy
> 3.6.3 Least Used with Degradation Policy
> 3.6.4 Weighted Round Robin Policy

These are examples of useages from the first format presented in 
section 3.6, right??
I believe it is better to make this more clear, since I was first 
confused if this
needed to go into the 'Policy-specifc Data' field.


>
>
> 3.8 Pool Element Parameter
>
>    This parameter is used in multiple ENRP messages to represent an 
> ASAP
>    endpoint (i.e., a PE in a pool) and the associated information, such
>    as its transport address(es), selection policy, and other 
> operational
>    or status information of the PE.
>
>
>     0                   1                   2                   3
>     0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>    |         Type = 0x8            |       Length=variable         |
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>    |                         PE Identifier                         |
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>    |                  Home ENRP Server Identifier                  |
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>    |                      Registration Life                        |
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>    :                    User Transport param #1                    :
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>    :                    User Transport param #2                    :
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>    :                                                               :
>    :                             .....                             :
>    :                                                               :
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>    :                    User Transport param #k                    :
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>    :                 Member Selection Policy param                 :
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>
>    Member Selection Policy:

I would suggest to move this parameter before the User Transport,
since there is not a specific count of 'User Transport' parameters.
OK, you can calculate it from the length of the complete parameter,
but I beleive it eases implementation.


>    Server Transport:
>
>    This is an SCTP Transport Parameter, as defined in Section 3.3 that
>    contains the network access address(es), SCTP port number, etc.  of
>    the ENRP server.

Is this only SCTP?? (Not sure)

>    Error causes are defined as variable-length parameters using the
>    format described in 3.2.1 of RFC2960 [3], i.e.:

  I suggest the start of new section 'Error Cause Parameter'.
Also why the reference to [3]. Since you copy the complete
definition it is redundant and let people believe this is SCTP.

>    Defines the type of error condition being reported.
>          Cause Code
>          Value           Cause Code
>          ---------      ----------------
>           1              Unrecognized Parameter
>           2              Unrecognized Message
>           3              Invalid Values
>           4              Non-unique PE Identifier
>           5              Pooling Policy Inconsistent
>           6              Lack of Resources
>          other values    reserved by IETF
>
>    Cause-specific Information: variable length

Assuming this is completely implementation dependant, I believe that
in this case also needs something as what caused it. For instance when
error cause '1' happens it must be indicated which parameter it was.
Although, this is maybe protocol specific semantics.

>    The following subsections (Section 3.10.1 - Section 3.10.2) define
>    specific error causes.

1) I believe that only specifying the first 2 error causes is not 
enough.
They all should be defined.

2) Are these really all errors that are possible??

3) How can one make new error causes and/or enterprise specific ones.
Maybe it is better to define this and forsee already how new error 
causes
can be added and how compatibility of implementations that do not know
those new error codes must be handled.
An idea is adding an Unrecognized Error to which it than can be mapped.
>
> 3.13 Communication Restrictions Parameter
>
>    This parameter defines a TLV that can be used by the sender to
>    restrict name server searches to a limited number of transport 
> types.
>
>
>     0                   1                   2                   3
>     0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>    |            Type = 0xd         |         Length=0x8            |
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>    |        Control Type           |          Data Type            |
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

Previous the doc always specifies the item Length also.
Why not here?

>    Type       |    Value
>    -----------+-------------
>    ANY        |   0x0000
>    SCTP ONLY  |   0x0001
>    TCP ONLY   |   0x0002

Why not specifying other as well. Allows extension and backwards 
compatibility
for the future (maybe).
>
>
>    Data Type:  16 bits (unsigned integer)
>
>    This field requests the search be restricted to PE's that have a 
> data
>    channel type of the specified type.  One of the following values 
> MUST
>    be used:
>
>    Type       |    Value
>    -----------+-------------
>    ANY        |   0x0000
>    SCTP ONLY  |   0x0001
>    TCP ONLY   |   0x0002
>    UDP ONLY   |   0x0003

I neither understand why the values of 'Data Type' and 'Control Type'
are different. A 'Control Type' of UDP could be possible. Whether it
will work well is a different thing.

Making these values equal eases it for implementors I guess too.

>
> 4. Common Message Formats
>
>    10 reserved.
>
>    11 reserved.

Although reserved, but what is suggested for to do when these values
are received?? Handle it as '00'?

>    This value represents the size of the message in bytes including the
>    Message Type, Message Flags, Message Length, and Message Value
>    fields.  Therefore, if the Message Value field is zero-length, the
>    Length field will be set to 4.  The Message Length field does not
>    count any padding.
>
>    Note, the value in Message Length field will NOT cover any padding 
> at
>    the end of this message.

The 'Note,..' is equal in semantics to the previous sentence.
IMHO, drop it.

>
> 5. Security Considerations
>
>    Details on ENRP and ASAP security constraints are a addressed in 
> ENRP
                                                        ^

'are a addressed' -> 'are addressed'

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



From rserpool-admin@ietf.org  Fri Mar 28 08:37:39 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 IAA28305
	for <rserpool-archive@lists.ietf.org>; Fri, 28 Mar 2003 08:37:39 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2SDxCO04802;
	Fri, 28 Mar 2003 08:59:12 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2SDvbO04705
	for <rserpool@optimus.ietf.org>; Fri, 28 Mar 2003 08:57:37 -0500
Received: from beamer.mchh.siemens.de (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA28242;
	Fri, 28 Mar 2003 08:35:18 -0500 (EST)
Received: from moody.mchh.siemens.de ([139.21.205.85])
	by beamer.mchh.siemens.de (8.9.3/8.9.3) with ESMTP id OAA09332;
	Fri, 28 Mar 2003 14:37:40 +0100 (MET)
Received: from mchh273e.demchh201e.icn.siemens.de (mchh273e.mchh.siemens.de [139.21.200.83])
	by moody.mchh.siemens.de (8.9.3/8.9.1) with ESMTP id OAA25795;
	Fri, 28 Mar 2003 14:37:40 +0100 (MET)
Received: by mchh273e.mchh.siemens.de with Internet Mail Service (5.5.2656.59)
	id <GGVN4FQJ>; Fri, 28 Mar 2003 14:37:22 +0100
Message-ID: <F92978223B01D311ACFF0008C71EE19D015DFB3B@mchh225e.mchh.siemens.de>
From: Tuexen Michael <michael.tuexen@siemens.com>
To: "'sigtran@ietf.org'" <sigtran@ietf.org>,
        "'tsvwg@ietf.org'"
	 <tsvwg@ietf.org>,
        "'rserpool@ietf.org'" <rserpool@ietf.org>
Date: Fri, 28 Mar 2003 14:37:21 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2656.59)
Content-Type: text/plain;
	charset="ISO-8859-1"
Subject: [Rserpool] New e-mail address
Sender: rserpool-admin@ietf.org
Errors-To: rserpool-admin@ietf.org
X-BeenThere: rserpool@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=unsubscribe>
List-Id: Reliable Server Pooling <rserpool.ietf.org>
List-Post: <mailto:rserpool@ietf.org>
List-Help: <mailto:rserpool-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=subscribe>

Dear all,

my Siemens e-mail address will no longer work.
Please use

tuexen@fh-muenster.de

in case you want to contact me.

Best regards
Michael

Michael Tuexen   Tel.:   +49 89 722 47210
Siemens AG       Fax:    +49 89 722 48212
ICN CP SE C 7    e-mail: Michael.Tuexen@siemens.com
_______________________________________________
rserpool mailing list
rserpool@ietf.org
https://www1.ietf.org/mailman/listinfo/rserpool


From mailnull@www1.ietf.org  Fri Mar 28 08:38:09 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 IAA28332
	for <rserpool-archive@odin.ietf.org>; Fri, 28 Mar 2003 08:38:09 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2SDxub04850
	for rserpool-archive@odin.ietf.org; Fri, 28 Mar 2003 08:59:56 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2SDxCO04802;
	Fri, 28 Mar 2003 08:59:12 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2SDvbO04705
	for <rserpool@optimus.ietf.org>; Fri, 28 Mar 2003 08:57:37 -0500
Received: from beamer.mchh.siemens.de (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA28242;
	Fri, 28 Mar 2003 08:35:18 -0500 (EST)
Received: from moody.mchh.siemens.de ([139.21.205.85])
	by beamer.mchh.siemens.de (8.9.3/8.9.3) with ESMTP id OAA09332;
	Fri, 28 Mar 2003 14:37:40 +0100 (MET)
Received: from mchh273e.demchh201e.icn.siemens.de (mchh273e.mchh.siemens.de [139.21.200.83])
	by moody.mchh.siemens.de (8.9.3/8.9.1) with ESMTP id OAA25795;
	Fri, 28 Mar 2003 14:37:40 +0100 (MET)
Received: by mchh273e.mchh.siemens.de with Internet Mail Service (5.5.2656.59)
	id <GGVN4FQJ>; Fri, 28 Mar 2003 14:37:22 +0100
Message-ID: <F92978223B01D311ACFF0008C71EE19D015DFB3B@mchh225e.mchh.siemens.de>
From: Tuexen Michael <michael.tuexen@siemens.com>
To: "'sigtran@ietf.org'" <sigtran@ietf.org>,
        "'tsvwg@ietf.org'"
	 <tsvwg@ietf.org>,
        "'rserpool@ietf.org'" <rserpool@ietf.org>
Date: Fri, 28 Mar 2003 14:37:21 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2656.59)
Content-Type: text/plain;
	charset="ISO-8859-1"
Subject: [Rserpool] New e-mail address
Sender: rserpool-admin@ietf.org
Errors-To: rserpool-admin@ietf.org
X-BeenThere: rserpool@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=unsubscribe>
List-Id: Reliable Server Pooling <rserpool.ietf.org>
List-Post: <mailto:rserpool@ietf.org>
List-Help: <mailto:rserpool-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=subscribe>

Dear all,

my Siemens e-mail address will no longer work.
Please use

tuexen@fh-muenster.de

in case you want to contact me.

Best regards
Michael

Michael Tuexen   Tel.:   +49 89 722 47210
Siemens AG       Fax:    +49 89 722 48212
ICN CP SE C 7    e-mail: Michael.Tuexen@siemens.com
_______________________________________________
rserpool mailing list
rserpool@ietf.org
https://www1.ietf.org/mailman/listinfo/rserpool



