From rserpool-admin@ietf.org  Mon Nov  3 17:36:23 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA29472
	for <rserpool-archive@lists.ietf.org>; Mon, 3 Nov 2003 17:36:23 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AGnIp-0005xK-0t; Mon, 03 Nov 2003 17:36:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AEUsN-0003YW-Jz
	for rserpool@optimus.ietf.org; Tue, 28 Oct 2003 09:31:15 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA23506;
	Tue, 28 Oct 2003 09:31:03 -0500 (EST)
Message-Id: <200310281431.JAA23506@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, 28 Oct 2003 09:31:03 -0500
Subject: [Rserpool] I-D ACTION:draft-ietf-rserpool-asap-08.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-08.txt
	Pages		: 44
	Date		: 2003-10-27
	
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-08.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-08.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-08.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

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

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

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

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

--OtherAccess--

--NextPart--



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


From exim@www1.ietf.org  Mon Nov  3 17:36:23 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA29476
	for <rserpool-archive@odin.ietf.org>; Mon, 3 Nov 2003 17:36:23 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AGnIq-0005zt-CY
	for rserpool-archive@odin.ietf.org; Mon, 03 Nov 2003 17:36:04 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hA3Ma4Lo023003
	for rserpool-archive@odin.ietf.org; Mon, 3 Nov 2003 17:36:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AGnIp-0005xV-80; Mon, 03 Nov 2003 17:36:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AEUsX-0003Zh-65
	for rserpool@optimus.ietf.org; Tue, 28 Oct 2003 09:31:25 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA23523;
	Tue, 28 Oct 2003 09:31:13 -0500 (EST)
Message-Id: <200310281431.JAA23523@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, 28 Oct 2003 09:31:12 -0500
Subject: [Rserpool] I-D ACTION:draft-ietf-rserpool-common-param-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		: Aggregate Server Access Protocol (ASAP) and Endpoint Name Resolution (ENRP) Parameters
	Author(s)	: R. Stewart, Q. Xie, M. Tuexen
	Filename	: draft-ietf-rserpool-common-param-05.txt
	Pages		: 27
	Date		: 2003-10-27
	
This document details the parameters of the Aggregate Server Access
Protocol (ASAP) and Endpoint Name Resolution Protocol (ENRP)
protocols defined within the Reliable Server Pooling (RSERPOOL)
architecture.

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

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

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

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

--OtherAccess--

--NextPart--



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



From exim@www1.ietf.org  Mon Nov  3 17:36:26 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA29534
	for <rserpool-archive@odin.ietf.org>; Mon, 3 Nov 2003 17:36:26 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AGnIq-000604-Ik
	for rserpool-archive@odin.ietf.org; Mon, 03 Nov 2003 17:36:04 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hA3Ma4AK023021
	for rserpool-archive@odin.ietf.org; Mon, 3 Nov 2003 17:36:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AGnIp-0005xs-J3; Mon, 03 Nov 2003 17:36:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AEUsd-0003a9-IL
	for rserpool@optimus.ietf.org; Tue, 28 Oct 2003 09:31:31 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA23543;
	Tue, 28 Oct 2003 09:31:19 -0500 (EST)
Message-Id: <200310281431.JAA23543@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, 28 Oct 2003 09:31:19 -0500
Subject: [Rserpool] I-D ACTION:draft-ietf-rserpool-enrp-07.txt
Sender: rserpool-admin@ietf.org
Errors-To: rserpool-admin@ietf.org
X-BeenThere: rserpool@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <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-07.txt
	Pages		: 47
	Date		: 2003-10-27
	
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-07.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-rserpool-enrp-07.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-rserpool-enrp-07.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

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

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

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

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

--OtherAccess--

--NextPart--



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



From rserpool-admin@ietf.org  Mon Nov  3 17:36:27 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA29564
	for <rserpool-archive@lists.ietf.org>; Mon, 3 Nov 2003 17:36:27 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AGnIp-0005xV-80; Mon, 03 Nov 2003 17:36:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AEUsX-0003Zh-65
	for rserpool@optimus.ietf.org; Tue, 28 Oct 2003 09:31:25 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA23523;
	Tue, 28 Oct 2003 09:31:13 -0500 (EST)
Message-Id: <200310281431.JAA23523@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, 28 Oct 2003 09:31:12 -0500
Subject: [Rserpool] I-D ACTION:draft-ietf-rserpool-common-param-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		: Aggregate Server Access Protocol (ASAP) and Endpoint Name Resolution (ENRP) Parameters
	Author(s)	: R. Stewart, Q. Xie, M. Tuexen
	Filename	: draft-ietf-rserpool-common-param-05.txt
	Pages		: 27
	Date		: 2003-10-27
	
This document details the parameters of the Aggregate Server Access
Protocol (ASAP) and Endpoint Name Resolution Protocol (ENRP)
protocols defined within the Reliable Server Pooling (RSERPOOL)
architecture.

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

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

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

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

--OtherAccess--

--NextPart--



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


From rserpool-admin@ietf.org  Mon Nov  3 17:36:32 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA29599
	for <rserpool-archive@lists.ietf.org>; Mon, 3 Nov 2003 17:36:32 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AGnIp-0005xs-J3; Mon, 03 Nov 2003 17:36:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AEUsd-0003a9-IL
	for rserpool@optimus.ietf.org; Tue, 28 Oct 2003 09:31:31 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA23543;
	Tue, 28 Oct 2003 09:31:19 -0500 (EST)
Message-Id: <200310281431.JAA23543@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, 28 Oct 2003 09:31:19 -0500
Subject: [Rserpool] I-D ACTION:draft-ietf-rserpool-enrp-07.txt
Sender: rserpool-admin@ietf.org
Errors-To: rserpool-admin@ietf.org
X-BeenThere: rserpool@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <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-07.txt
	Pages		: 47
	Date		: 2003-10-27
	
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-07.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-rserpool-enrp-07.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-rserpool-enrp-07.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

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

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

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

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

--OtherAccess--

--NextPart--



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


From exim@www1.ietf.org  Mon Nov  3 18:25:08 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA29475
	for <rserpool-archive@odin.ietf.org>; Mon, 3 Nov 2003 17:36:23 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AGnIq-0005zl-Bv
	for rserpool-archive@odin.ietf.org; Mon, 03 Nov 2003 17:36:04 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hA3Ma4HO022992
	for rserpool-archive@odin.ietf.org; Mon, 3 Nov 2003 17:36:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AGnIp-0005xK-0t; Mon, 03 Nov 2003 17:36:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AEUsN-0003YW-Jz
	for rserpool@optimus.ietf.org; Tue, 28 Oct 2003 09:31:15 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA23506;
	Tue, 28 Oct 2003 09:31:03 -0500 (EST)
Message-Id: <200310281431.JAA23506@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, 28 Oct 2003 09:31:03 -0500
Subject: [Rserpool] I-D ACTION:draft-ietf-rserpool-asap-08.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-08.txt
	Pages		: 44
	Date		: 2003-10-27
	
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-08.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-08.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-08.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

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

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

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

Content-Type: text/plain
Content-ID:	<2003-10-28095057.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 Nov  4 11:44:19 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA21943
	for <rserpool-archive@lists.ietf.org>; Tue, 4 Nov 2003 11:44:19 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AH4Hh-0008Hn-33; Tue, 04 Nov 2003 11:44:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AH4H1-0008Gp-HJ
	for rserpool@optimus.ietf.org; Tue, 04 Nov 2003 11:43:20 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA21899
	for <rserpool@ietf.org>; Tue, 4 Nov 2003 11:43:07 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AH4H0-0000R6-00
	for rserpool@ietf.org; Tue, 04 Nov 2003 11:43:18 -0500
Received: from motgate.mot.com ([129.188.136.100])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AH4Gz-0000R2-00
	for rserpool@ietf.org; Tue, 04 Nov 2003 11:43:17 -0500
Received: from il06exr02.mot.com (pobox.mot.com [129.188.137.100])
	by motgate.mot.com (Motorola/Motgate) with ESMTP id hA4GhGpV007194
	for <rserpool@ietf.org>; Tue, 4 Nov 2003 09:43:16 -0700 (MST)
Received: from il02exb02.corp.mot.com (il02exb02.corp.mot.com [10.0.100.67])
	by il06exr02.mot.com (Motorola/il06exr02) with ESMTP id hA4GfoLv023714
	for <rserpool@ietf.org>; Tue, 4 Nov 2003 10:41:50 -0600
Received: by il02exb02.corp.mot.com with Internet Mail Service (5.5.2657.2)
	id <T7SBWWHM>; Tue, 4 Nov 2003 10:43:14 -0600
Message-ID: <6F8DFFA2C996D711945800065BFC9E4A022287AE@il02exm11.corp.mot.com>
From: Silverton Aron-C1710C <Aron.J.Silverton@motorola.com>
To: rserpool@ietf.org
Cc: Xie Qiaobing-QXIE1 <Qiaobing.Xie@motorola.com>,
        "'Michael Tuxen'"
	 <tuexen@fh-muenster.de>,
        "'Thomas Dreibholz'"
	 <dreibh@exp-math.uni-essen.de>, conrad@acm.org
Subject: RE: [Rserpool] RSERPOOL Implementation status updates
Date: Tue, 4 Nov 2003 10:43:05 -0600 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.2)
Content-Type: text/plain
Sender: rserpool-admin@ietf.org
Errors-To: rserpool-admin@ietf.org
X-BeenThere: rserpool@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <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>

Please try to send me updates by Friday, 11/7.

Thanks,

Aron

Silverton Aron-C1710C wrote:
> Hello all,
> 
> I will be updating the Implementation Status Report for the IETF
> meeting next month.  I invite all of you to provide me with
> updates to the existing status report from earlier this year. 
> Those slides are available at
> http://www.ietf.org/proceedings/03mar/slides/rserpool-4/index.html.
> 
> Please provide any additional information not included in the
> existing template as you see fit.  If you can provide details on
> your intended use and any modeling or simulation that you might
> have done, I would like to include that information as well.  I
> understand if your day-job-provider puts limits on the amount of
> information that you can share.     
> 
> Regards,
> 
> Aron
> 
> Aron J. Silverton
> Senior Staff Research Engineer
> Motorola Labs, Networks and Infrastructure Research
> Motorola, Inc.
> 
> Telephone: 847-576-8747
> Fax: 847-576-3240
> mailto:Aron.J.Silverton@motorola.com
> 
> _______________________________________________
> rserpool mailing list
> rserpool@ietf.org https://www1.ietf.org/mailman/listinfo/rserpool

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


From exim@www1.ietf.org  Tue Nov  4 11:44:21 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA21961
	for <rserpool-archive@odin.ietf.org>; Tue, 4 Nov 2003 11:44:21 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AH4Hi-0008IO-3E
	for rserpool-archive@odin.ietf.org; Tue, 04 Nov 2003 11:44:03 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hA4Gi1Pi031870
	for rserpool-archive@odin.ietf.org; Tue, 4 Nov 2003 11:44:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AH4Hh-0008Hn-33; Tue, 04 Nov 2003 11:44:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AH4H1-0008Gp-HJ
	for rserpool@optimus.ietf.org; Tue, 04 Nov 2003 11:43:20 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA21899
	for <rserpool@ietf.org>; Tue, 4 Nov 2003 11:43:07 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AH4H0-0000R6-00
	for rserpool@ietf.org; Tue, 04 Nov 2003 11:43:18 -0500
Received: from motgate.mot.com ([129.188.136.100])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AH4Gz-0000R2-00
	for rserpool@ietf.org; Tue, 04 Nov 2003 11:43:17 -0500
Received: from il06exr02.mot.com (pobox.mot.com [129.188.137.100])
	by motgate.mot.com (Motorola/Motgate) with ESMTP id hA4GhGpV007194
	for <rserpool@ietf.org>; Tue, 4 Nov 2003 09:43:16 -0700 (MST)
Received: from il02exb02.corp.mot.com (il02exb02.corp.mot.com [10.0.100.67])
	by il06exr02.mot.com (Motorola/il06exr02) with ESMTP id hA4GfoLv023714
	for <rserpool@ietf.org>; Tue, 4 Nov 2003 10:41:50 -0600
Received: by il02exb02.corp.mot.com with Internet Mail Service (5.5.2657.2)
	id <T7SBWWHM>; Tue, 4 Nov 2003 10:43:14 -0600
Message-ID: <6F8DFFA2C996D711945800065BFC9E4A022287AE@il02exm11.corp.mot.com>
From: Silverton Aron-C1710C <Aron.J.Silverton@motorola.com>
To: rserpool@ietf.org
Cc: Xie Qiaobing-QXIE1 <Qiaobing.Xie@motorola.com>,
        "'Michael Tuxen'"
	 <tuexen@fh-muenster.de>,
        "'Thomas Dreibholz'"
	 <dreibh@exp-math.uni-essen.de>, conrad@acm.org
Subject: RE: [Rserpool] RSERPOOL Implementation status updates
Date: Tue, 4 Nov 2003 10:43:05 -0600 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.2)
Content-Type: text/plain
Sender: rserpool-admin@ietf.org
Errors-To: rserpool-admin@ietf.org
X-BeenThere: rserpool@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <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>

Please try to send me updates by Friday, 11/7.

Thanks,

Aron

Silverton Aron-C1710C wrote:
> Hello all,
> 
> I will be updating the Implementation Status Report for the IETF
> meeting next month.  I invite all of you to provide me with
> updates to the existing status report from earlier this year. 
> Those slides are available at
> http://www.ietf.org/proceedings/03mar/slides/rserpool-4/index.html.
> 
> Please provide any additional information not included in the
> existing template as you see fit.  If you can provide details on
> your intended use and any modeling or simulation that you might
> have done, I would like to include that information as well.  I
> understand if your day-job-provider puts limits on the amount of
> information that you can share.     
> 
> Regards,
> 
> Aron
> 
> Aron J. Silverton
> Senior Staff Research Engineer
> Motorola Labs, Networks and Infrastructure Research
> Motorola, Inc.
> 
> Telephone: 847-576-8747
> Fax: 847-576-3240
> mailto:Aron.J.Silverton@motorola.com
> 
> _______________________________________________
> rserpool mailing list
> rserpool@ietf.org https://www1.ietf.org/mailman/listinfo/rserpool

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



From exim@www1.ietf.org  Mon Nov 10 06:24:17 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA15969
	for <rserpool-archive@odin.ietf.org>; Mon, 10 Nov 2003 06:24:17 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJA9J-0007ZA-M2
	for rserpool-archive@odin.ietf.org; Mon, 10 Nov 2003 06:24:01 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAABO1rt029062
	for rserpool-archive@odin.ietf.org; Mon, 10 Nov 2003 06:24:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJA9I-0007Yd-SY; Mon, 10 Nov 2003 06:24:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJA8m-0007Y6-2I
	for rserpool@optimus.ietf.org; Mon, 10 Nov 2003 06:23:28 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA15951
	for <rserpool@ietf.org>; Mon, 10 Nov 2003 06:23:13 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJA8i-00031b-00
	for rserpool@ietf.org; Mon, 10 Nov 2003 06:23:24 -0500
Received: from smtp02.uc3m.es ([163.117.136.122] helo=smtp.uc3m.es)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJA8h-00031G-00
	for rserpool@ietf.org; Mon, 10 Nov 2003 06:23:23 -0500
Received: from smtp02.uc3m.es (localhost [127.0.0.1])
	by smtp.uc3m.es (Postfix) with ESMTP id 15499431C6
	for <rserpool@ietf.org>; Mon, 10 Nov 2003 12:22:54 +0100 (CET)
Received: from requiem.it.uc3m.es (requiem.it.uc3m.es [163.117.139.166])
	by smtp02.uc3m.es (Postfix) with ESMTP id 073729A070
	for <rserpool@ietf.org>; Mon, 10 Nov 2003 12:22:54 +0100 (CET)
From: Manuel =?ISO-8859-1?Q?Urue=F1a?= <muruenya@it.uc3m.es>
To: rserpool@ietf.org
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-21xX1+aUu+O/zpW2zCBC"
Organization: Universidad Carlos III de Madrid
Message-Id: <1068463190.2508.86.camel@requiem.it.uc3m.es>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.4.4-8mdk 
Date: Mon, 10 Nov 2003 12:19:52 +0100
Subject: [Rserpool] Should ASAP be splitted?
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>


--=-21xX1+aUu+O/zpW2zCBC
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

Hi,

Reading the ASAP draft I felt that it seems a little overloaded. In
particular, registration operations are just employed by PEs.

Maybe it would be good to put those operations in another protocol. Or
exactly the same ASAP protocol but without PU related operations. Of
course PE would require both protocols.

This will ease firewall protection, I mean, with ASAP firewalls should
allow ASAP connections to both PEs and NSs. Therefore, remote PUs are
able to send Registration operations to NSs. With two separate
protocols, registration port could be filtered.

Has been this discussed before? comments?

Regards,
--Manuel

--=20
Manuel Uruen~a - Universidad Carlos III de Madrid
GPG FP: 9BE9 9FFF ACFF 2887 80E6 50FE FABC A79F 5535 5A75

--=-21xX1+aUu+O/zpW2zCBC
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: Esta parte del mensaje =?ISO-8859-1?Q?est=E1?= firmada
	digitalmente

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQA/r3RT+rynn1U1WnURAgMbAJ9Z7XkxbA0GRZOBLAGmpbQA3yM1EQCgjTpi
buqiRiYWp7iHNnY4WaXCg48=
=LhRd
-----END PGP SIGNATURE-----

--=-21xX1+aUu+O/zpW2zCBC--


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



From rserpool-admin@ietf.org  Mon Nov 10 06:24:17 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA15966
	for <rserpool-archive@lists.ietf.org>; Mon, 10 Nov 2003 06:24:17 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJA9I-0007Yd-SY; Mon, 10 Nov 2003 06:24:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJA8m-0007Y6-2I
	for rserpool@optimus.ietf.org; Mon, 10 Nov 2003 06:23:28 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA15951
	for <rserpool@ietf.org>; Mon, 10 Nov 2003 06:23:13 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJA8i-00031b-00
	for rserpool@ietf.org; Mon, 10 Nov 2003 06:23:24 -0500
Received: from smtp02.uc3m.es ([163.117.136.122] helo=smtp.uc3m.es)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJA8h-00031G-00
	for rserpool@ietf.org; Mon, 10 Nov 2003 06:23:23 -0500
Received: from smtp02.uc3m.es (localhost [127.0.0.1])
	by smtp.uc3m.es (Postfix) with ESMTP id 15499431C6
	for <rserpool@ietf.org>; Mon, 10 Nov 2003 12:22:54 +0100 (CET)
Received: from requiem.it.uc3m.es (requiem.it.uc3m.es [163.117.139.166])
	by smtp02.uc3m.es (Postfix) with ESMTP id 073729A070
	for <rserpool@ietf.org>; Mon, 10 Nov 2003 12:22:54 +0100 (CET)
From: Manuel =?ISO-8859-1?Q?Urue=F1a?= <muruenya@it.uc3m.es>
To: rserpool@ietf.org
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-21xX1+aUu+O/zpW2zCBC"
Organization: Universidad Carlos III de Madrid
Message-Id: <1068463190.2508.86.camel@requiem.it.uc3m.es>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.4.4-8mdk 
Date: Mon, 10 Nov 2003 12:19:52 +0100
Subject: [Rserpool] Should ASAP be splitted?
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>


--=-21xX1+aUu+O/zpW2zCBC
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

Hi,

Reading the ASAP draft I felt that it seems a little overloaded. In
particular, registration operations are just employed by PEs.

Maybe it would be good to put those operations in another protocol. Or
exactly the same ASAP protocol but without PU related operations. Of
course PE would require both protocols.

This will ease firewall protection, I mean, with ASAP firewalls should
allow ASAP connections to both PEs and NSs. Therefore, remote PUs are
able to send Registration operations to NSs. With two separate
protocols, registration port could be filtered.

Has been this discussed before? comments?

Regards,
--Manuel

--=20
Manuel Uruen~a - Universidad Carlos III de Madrid
GPG FP: 9BE9 9FFF ACFF 2887 80E6 50FE FABC A79F 5535 5A75

--=-21xX1+aUu+O/zpW2zCBC
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: Esta parte del mensaje =?ISO-8859-1?Q?est=E1?= firmada
	digitalmente

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQA/r3RT+rynn1U1WnURAgMbAJ9Z7XkxbA0GRZOBLAGmpbQA3yM1EQCgjTpi
buqiRiYWp7iHNnY4WaXCg48=
=LhRd
-----END PGP SIGNATURE-----

--=-21xX1+aUu+O/zpW2zCBC--


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


From rserpool-admin@ietf.org  Tue Nov 11 17:01:20 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA23810
	for <rserpool-archive@lists.ietf.org>; Tue, 11 Nov 2003 17:01:20 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJgZJ-0000pw-7U; Tue, 11 Nov 2003 17:01:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJgYQ-0000bJ-Rw
	for rserpool@optimus.ietf.org; Tue, 11 Nov 2003 17:00:06 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA23629
	for <rserpool@ietf.org>; Tue, 11 Nov 2003 16:59:53 -0500 (EST)
From: Maureen.Stillman@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJgYO-0002qS-00
	for rserpool@ietf.org; Tue, 11 Nov 2003 17:00:04 -0500
Received: from mgw-x4.nokia.com ([131.228.20.27])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJgYN-0002qG-00
	for rserpool@ietf.org; Tue, 11 Nov 2003 17:00:03 -0500
Received: from esvir04nok.ntc.nokia.com (esvir04nokt.ntc.nokia.com [172.21.143.36])
	by mgw-x4.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id hABM03s12869
	for <rserpool@ietf.org>; Wed, 12 Nov 2003 00:00:03 +0200 (EET)
Received: from daebh002.NOE.Nokia.com (unverified) by esvir04nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T65d9a58e37ac158f24077@esvir04nok.ntc.nokia.com> for <rserpool@ietf.org>;
 Wed, 12 Nov 2003 00:00:02 +0200
Received: from daebe007.NOE.Nokia.com ([10.241.35.107]) by daebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6747);
	 Tue, 11 Nov 2003 15:59:15 -0600
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
Date: Tue, 11 Nov 2003 15:59:15 -0600
Message-ID: <57A26D272F67A743952F6B4371B8F811021CFFAD@daebe007.americas.nokia.com>
Thread-Topic: Papers on Reliable Server Pooling
Thread-Index: AcOonwuiEBBk6P+zS8C769EYcjlKBg==
To: <rserpool@ietf.org>
X-OriginalArrivalTime: 11 Nov 2003 21:59:15.0589 (UTC) FILETIME=[0C491B50:01C3A89F]
Content-Transfer-Encoding: quoted-printable
Subject: [Rserpool] Papers on Reliable Server Pooling
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: quoted-printable

I haven't read any of these yet, but here are the URLs FYI.=20

Performance study of reliable server pooling=20
Umit Uyar, M.; Jianliang Zheng; Fecko, M.A.; Samtani, S.;=20
Network Computing and Applications, 2003. NCA 2003. Second IEEE =
International Symposium on , 16-18 April 2003=20
Page(s): 205 -212

http://csdl.computer.org/comp/proceedings/nca/2003/1938/00/19380205abs.ht=
m

Reliable server pooling in highly mobile wireless networks=20
Uyar, M.U.; Jianliang Zheng; Fecko, M.A.; Samtani, S.;=20
Computers and Communication, 2003. (ISCC 2003). Proceedings. Eighth IEEE =
International Symposium on , 2003=20
Page(s): 627 -632


INCREASING INFRASTRUCTURE SURVIVABILITY THROUGH RELIABLE SERVER POOLS
Mariusz A. Fecko1, M. =A8 Umit Uyar2, Jianliang Zheng2, Phill T. =
Conrad3, Sunil Samtani1

(submitted to Army Science Conf., Orlando, FL, Dec 2002) July 24, 2002)
http://www.asc2002.com/Abstracts_only/o/OA06.pdf


M. U. Uyar, J. Zheng, M. A. Fecko, S. Samtani, P. T. Conrad. Evaluation =
of Architectures for Reliable Server Pooling in Wired and Wireless =
Environments. (invited paper) IEEE JSAC Special Issue on Recent Advances =
in Service Overlay Networks (in press).   =20

The JSAC paper should appear later this year or early next year.

-- maureen

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


From exim@www1.ietf.org  Tue Nov 11 18:15:02 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA23812
	for <rserpool-archive@odin.ietf.org>; Tue, 11 Nov 2003 17:01:20 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJgZK-0000qx-Gt
	for rserpool-archive@odin.ietf.org; Tue, 11 Nov 2003 17:01:02 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hABM12xI003259
	for rserpool-archive@odin.ietf.org; Tue, 11 Nov 2003 17:01:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJgZJ-0000pw-7U; Tue, 11 Nov 2003 17:01:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJgYQ-0000bJ-Rw
	for rserpool@optimus.ietf.org; Tue, 11 Nov 2003 17:00:06 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA23629
	for <rserpool@ietf.org>; Tue, 11 Nov 2003 16:59:53 -0500 (EST)
From: Maureen.Stillman@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJgYO-0002qS-00
	for rserpool@ietf.org; Tue, 11 Nov 2003 17:00:04 -0500
Received: from mgw-x4.nokia.com ([131.228.20.27])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJgYN-0002qG-00
	for rserpool@ietf.org; Tue, 11 Nov 2003 17:00:03 -0500
Received: from esvir04nok.ntc.nokia.com (esvir04nokt.ntc.nokia.com [172.21.143.36])
	by mgw-x4.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id hABM03s12869
	for <rserpool@ietf.org>; Wed, 12 Nov 2003 00:00:03 +0200 (EET)
Received: from daebh002.NOE.Nokia.com (unverified) by esvir04nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T65d9a58e37ac158f24077@esvir04nok.ntc.nokia.com> for <rserpool@ietf.org>;
 Wed, 12 Nov 2003 00:00:02 +0200
Received: from daebe007.NOE.Nokia.com ([10.241.35.107]) by daebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6747);
	 Tue, 11 Nov 2003 15:59:15 -0600
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
Date: Tue, 11 Nov 2003 15:59:15 -0600
Message-ID: <57A26D272F67A743952F6B4371B8F811021CFFAD@daebe007.americas.nokia.com>
Thread-Topic: Papers on Reliable Server Pooling
Thread-Index: AcOonwuiEBBk6P+zS8C769EYcjlKBg==
To: <rserpool@ietf.org>
X-OriginalArrivalTime: 11 Nov 2003 21:59:15.0589 (UTC) FILETIME=[0C491B50:01C3A89F]
Content-Transfer-Encoding: quoted-printable
Subject: [Rserpool] Papers on Reliable Server Pooling
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: quoted-printable

I haven't read any of these yet, but here are the URLs FYI.=20

Performance study of reliable server pooling=20
Umit Uyar, M.; Jianliang Zheng; Fecko, M.A.; Samtani, S.;=20
Network Computing and Applications, 2003. NCA 2003. Second IEEE =
International Symposium on , 16-18 April 2003=20
Page(s): 205 -212

http://csdl.computer.org/comp/proceedings/nca/2003/1938/00/19380205abs.ht=
m

Reliable server pooling in highly mobile wireless networks=20
Uyar, M.U.; Jianliang Zheng; Fecko, M.A.; Samtani, S.;=20
Computers and Communication, 2003. (ISCC 2003). Proceedings. Eighth IEEE =
International Symposium on , 2003=20
Page(s): 627 -632


INCREASING INFRASTRUCTURE SURVIVABILITY THROUGH RELIABLE SERVER POOLS
Mariusz A. Fecko1, M. =A8 Umit Uyar2, Jianliang Zheng2, Phill T. =
Conrad3, Sunil Samtani1

(submitted to Army Science Conf., Orlando, FL, Dec 2002) July 24, 2002)
http://www.asc2002.com/Abstracts_only/o/OA06.pdf


M. U. Uyar, J. Zheng, M. A. Fecko, S. Samtani, P. T. Conrad. Evaluation =
of Architectures for Reliable Server Pooling in Wired and Wireless =
Environments. (invited paper) IEEE JSAC Special Issue on Recent Advances =
in Service Overlay Networks (in press).   =20

The JSAC paper should appear later this year or early next year.

-- maureen

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



From rserpool-admin@ietf.org  Mon Nov 17 21:53:18 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA19951
	for <rserpool-archive@lists.ietf.org>; Mon, 17 Nov 2003 21:53:18 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ALvzA-0001G6-MD; Mon, 17 Nov 2003 21:53:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ALvyT-0001Ez-5E
	for rserpool@optimus.ietf.org; Mon, 17 Nov 2003 21:52:17 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA19857
	for <rserpool@ietf.org>; Mon, 17 Nov 2003 21:52:03 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ALvyQ-00047g-00
	for rserpool@ietf.org; Mon, 17 Nov 2003 21:52:14 -0500
Received: from motgate4.mot.com ([144.189.100.102])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ALvyP-00047d-00
	for rserpool@ietf.org; Mon, 17 Nov 2003 21:52:13 -0500
Received: from az33exr01.mot.com (az33exr01.mot.com [10.64.251.231])
	by motgate4.mot.com (Motorola/Motgate4) with ESMTP id hAI2qCJ3001785;
	Mon, 17 Nov 2003 19:52:12 -0700 (MST)
Received: from motorola.com (d1421-0a1070d5.cig.mot.com [10.16.112.213])
	by az33exr01.mot.com (Motorola/az33exr01) with ESMTP id hAI2p3F7002811;
	Mon, 17 Nov 2003 20:51:04 -0600
Message-ID: <3FB98A05.5169F370@motorola.com>
Date: Mon, 17 Nov 2003 20:55:01 -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: Manuel =?iso-8859-1?Q?Urue=F1a?= <muruenya@it.uc3m.es>
CC: rserpool@ietf.org
Subject: Re: [Rserpool] Should ASAP be splitted?
References: <1068463190.2508.86.camel@requiem.it.uc3m.es>
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by motgate4.mot.com id hAI2qCJ3001785
Content-Transfer-Encoding: quoted-printable
Sender: rserpool-admin@ietf.org
Errors-To: rserpool-admin@ietf.org
X-BeenThere: rserpool@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <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: quoted-printable

Hi, Manuel,

I think you have raised a quite interesting point. But to further split
ASAP seems not a good idea, since we already see the difficult for
people to have to read two documents (ENRP and ASAP) at the same time in
order to under RSERPOOL operations. This is because they are tightly
related. Further split of ASAP will make this even harder.

We may be able to achieve the same thing you described by asking for two
separate ports for PU and PE. Just a though.

regards,
-Qiaobing

Manuel Urue=F1a wrote:
>=20
> Hi,
>=20
> Reading the ASAP draft I felt that it seems a little overloaded. In
> particular, registration operations are just employed by PEs.
>=20
> Maybe it would be good to put those operations in another protocol. Or
> exactly the same ASAP protocol but without PU related operations. Of
> course PE would require both protocols.
>=20
> This will ease firewall protection, I mean, with ASAP firewalls should
> allow ASAP connections to both PEs and NSs. Therefore, remote PUs are
> able to send Registration operations to NSs. With two separate
> protocols, registration port could be filtered.
>=20
> Has been this discussed before? comments?
>=20
> Regards,
> --Manuel
>=20
> --
> Manuel Uruen~a - Universidad Carlos III de Madrid
> GPG FP: 9BE9 9FFF ACFF 2887 80E6 50FE FABC A79F 5535 5A75
>=20
>   ---------------------------------------------------------------------=
---
>                        Name: signature.asc
>    signature.asc       Type: application/pgp-signature
>                 Description: Esta parte del mensaje =3D?ISO-8859-1?Q?es=
t=3DE1?=3D firmada digitalmente

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


From exim@www1.ietf.org  Mon Nov 17 21:53:18 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA19957
	for <rserpool-archive@odin.ietf.org>; Mon, 17 Nov 2003 21:53:18 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ALvzA-0001GH-V3
	for rserpool-archive@odin.ietf.org; Mon, 17 Nov 2003 21:53:01 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAI2r025004849
	for rserpool-archive@odin.ietf.org; Mon, 17 Nov 2003 21:53:00 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ALvzA-0001G6-MD; Mon, 17 Nov 2003 21:53:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ALvyT-0001Ez-5E
	for rserpool@optimus.ietf.org; Mon, 17 Nov 2003 21:52:17 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA19857
	for <rserpool@ietf.org>; Mon, 17 Nov 2003 21:52:03 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ALvyQ-00047g-00
	for rserpool@ietf.org; Mon, 17 Nov 2003 21:52:14 -0500
Received: from motgate4.mot.com ([144.189.100.102])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ALvyP-00047d-00
	for rserpool@ietf.org; Mon, 17 Nov 2003 21:52:13 -0500
Received: from az33exr01.mot.com (az33exr01.mot.com [10.64.251.231])
	by motgate4.mot.com (Motorola/Motgate4) with ESMTP id hAI2qCJ3001785;
	Mon, 17 Nov 2003 19:52:12 -0700 (MST)
Received: from motorola.com (d1421-0a1070d5.cig.mot.com [10.16.112.213])
	by az33exr01.mot.com (Motorola/az33exr01) with ESMTP id hAI2p3F7002811;
	Mon, 17 Nov 2003 20:51:04 -0600
Message-ID: <3FB98A05.5169F370@motorola.com>
Date: Mon, 17 Nov 2003 20:55:01 -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: Manuel =?iso-8859-1?Q?Urue=F1a?= <muruenya@it.uc3m.es>
CC: rserpool@ietf.org
Subject: Re: [Rserpool] Should ASAP be splitted?
References: <1068463190.2508.86.camel@requiem.it.uc3m.es>
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by motgate4.mot.com id hAI2qCJ3001785
Content-Transfer-Encoding: quoted-printable
Sender: rserpool-admin@ietf.org
Errors-To: rserpool-admin@ietf.org
X-BeenThere: rserpool@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <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: quoted-printable

Hi, Manuel,

I think you have raised a quite interesting point. But to further split
ASAP seems not a good idea, since we already see the difficult for
people to have to read two documents (ENRP and ASAP) at the same time in
order to under RSERPOOL operations. This is because they are tightly
related. Further split of ASAP will make this even harder.

We may be able to achieve the same thing you described by asking for two
separate ports for PU and PE. Just a though.

regards,
-Qiaobing

Manuel Urue=F1a wrote:
>=20
> Hi,
>=20
> Reading the ASAP draft I felt that it seems a little overloaded. In
> particular, registration operations are just employed by PEs.
>=20
> Maybe it would be good to put those operations in another protocol. Or
> exactly the same ASAP protocol but without PU related operations. Of
> course PE would require both protocols.
>=20
> This will ease firewall protection, I mean, with ASAP firewalls should
> allow ASAP connections to both PEs and NSs. Therefore, remote PUs are
> able to send Registration operations to NSs. With two separate
> protocols, registration port could be filtered.
>=20
> Has been this discussed before? comments?
>=20
> Regards,
> --Manuel
>=20
> --
> Manuel Uruen~a - Universidad Carlos III de Madrid
> GPG FP: 9BE9 9FFF ACFF 2887 80E6 50FE FABC A79F 5535 5A75
>=20
>   ---------------------------------------------------------------------=
---
>                        Name: signature.asc
>    signature.asc       Type: application/pgp-signature
>                 Description: Esta parte del mensaje =3D?ISO-8859-1?Q?es=
t=3DE1?=3D firmada digitalmente

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



From rserpool-admin@ietf.org  Tue Nov 18 09:04:22 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA21301
	for <rserpool-archive@lists.ietf.org>; Tue, 18 Nov 2003 09:04:22 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AM6SW-0006Ff-TG; Tue, 18 Nov 2003 09:04:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AM6RZ-0006EJ-K4
	for rserpool@optimus.ietf.org; Tue, 18 Nov 2003 09:03:01 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA21188
	for <rserpool@ietf.org>; Tue, 18 Nov 2003 09:02:49 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AM6RY-0005dh-00
	for rserpool@ietf.org; Tue, 18 Nov 2003 09:03:00 -0500
Received: from smtp01.uc3m.es ([163.117.136.121] helo=smtp.uc3m.es)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AM6RX-0005dX-00
	for rserpool@ietf.org; Tue, 18 Nov 2003 09:02:59 -0500
Received: from smtp01.uc3m.es (localhost [127.0.0.1])
	by smtp.uc3m.es (Postfix) with ESMTP
	id 612A043163; Tue, 18 Nov 2003 15:02:27 +0100 (CET)
Received: from requiem.it.uc3m.es (requiem.it.uc3m.es [163.117.139.166])
	by smtp01.uc3m.es (Postfix) with ESMTP
	id 2D11199F9B; Tue, 18 Nov 2003 15:02:27 +0100 (CET)
Subject: Re: [Rserpool] Should ASAP be splitted?
From: Manuel =?ISO-8859-1?Q?Urue=F1a?= <muruenya@it.uc3m.es>
To: Qiaobing Xie <Qiaobing.Xie@motorola.com>
Cc: rserpool@ietf.org
In-Reply-To: <3FB98A05.5169F370@motorola.com>
References: <1068463190.2508.86.camel@requiem.it.uc3m.es>
	 <3FB98A05.5169F370@motorola.com>
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-x+yRqtETtur9Xxchl7HJ"
Organization: Universidad Carlos III de Madrid
Message-Id: <1069163958.2464.54.camel@requiem.it.uc3m.es>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.4.4-8mdk 
Date: Tue, 18 Nov 2003 14:59:20 +0100
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>


--=-x+yRqtETtur9Xxchl7HJ
Content-Type: text/plain; charset=iso-8859-15
Content-Transfer-Encoding: quoted-printable

Hi Qiaobing,

Good suggestion, two ports would be enough if ENRP Servers only accept
Register operations from the PE port. That port should be filtered for
IP addresses outside the Pool range to provide an additional security
level.

Just another question, I was not able to go to the IETF #58 Rserpool
meeting. Does anybody raise the MAX-BAD-PE-REPORT DoS issue?

Thanks,
--Manuel


Quiaobing Xie wrote:
>
> Hi, Manuel,
>
> I think you have raised a quite interesting point. But to further split
> ASAP seems not a good idea, since we already see the difficult for
> people to have to read two documents (ENRP and ASAP) at the same time in
> order to under RSERPOOL operations. This is because they are tightly
> related. Further split of ASAP will make this even harder.
>=20
> We may be able to achieve the same thing you described by asking for two
> separate ports for PU and PE. Just a though.
>
> regards,
> -Qiaobing
>
> Manuel Urue=F1a wrote:
> >=20
> > Hi,
> >=20
> > Reading the ASAP draft I felt that it seems a little overloaded. In
> > particular, registration operations are just employed by PEs.
> >=20
> > Maybe it would be good to put those operations in another protocol. Or
> > exactly the same ASAP protocol but without PU related operations. Of
> > course PE would require both protocols.
> >=20
> > This will ease firewall protection, I mean, with ASAP firewalls should
> > allow ASAP connections to both PEs and NSs. Therefore, remote PUs are
> > able to send Registration operations to NSs. With two separate
> > protocols, registration port could be filtered.
> >=20
> > Has been this discussed before? comments?
> >=20
> > Regards,
> > --Manuel
--=20
Manuel Uruen~a - Universidad Carlos III de Madrid
GPG FP: 68A1 164B EE28 52C9 87CB  EBF9 616E 52B5 451A B6B2

--=-x+yRqtETtur9Xxchl7HJ
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: Esta parte del mensaje =?ISO-8859-1?Q?est=E1?= firmada
	digitalmente

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQA/uiWzYW5StUUatrIRAkNeAJ9lTwW5OTXCmBjVfVHBO/KyX/sjkgCdHJSR
nG2TGji+GsePghVQ3TXw5aY=
=M5uV
-----END PGP SIGNATURE-----

--=-x+yRqtETtur9Xxchl7HJ--


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


From exim@www1.ietf.org  Tue Nov 18 09:04:23 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA21305
	for <rserpool-archive@odin.ietf.org>; Tue, 18 Nov 2003 09:04:23 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AM6SZ-0006G6-SU
	for rserpool-archive@odin.ietf.org; Tue, 18 Nov 2003 09:04:04 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAIE432O024058
	for rserpool-archive@odin.ietf.org; Tue, 18 Nov 2003 09:04:03 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AM6SW-0006Ff-TG; Tue, 18 Nov 2003 09:04:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AM6RZ-0006EJ-K4
	for rserpool@optimus.ietf.org; Tue, 18 Nov 2003 09:03:01 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA21188
	for <rserpool@ietf.org>; Tue, 18 Nov 2003 09:02:49 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AM6RY-0005dh-00
	for rserpool@ietf.org; Tue, 18 Nov 2003 09:03:00 -0500
Received: from smtp01.uc3m.es ([163.117.136.121] helo=smtp.uc3m.es)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AM6RX-0005dX-00
	for rserpool@ietf.org; Tue, 18 Nov 2003 09:02:59 -0500
Received: from smtp01.uc3m.es (localhost [127.0.0.1])
	by smtp.uc3m.es (Postfix) with ESMTP
	id 612A043163; Tue, 18 Nov 2003 15:02:27 +0100 (CET)
Received: from requiem.it.uc3m.es (requiem.it.uc3m.es [163.117.139.166])
	by smtp01.uc3m.es (Postfix) with ESMTP
	id 2D11199F9B; Tue, 18 Nov 2003 15:02:27 +0100 (CET)
Subject: Re: [Rserpool] Should ASAP be splitted?
From: Manuel =?ISO-8859-1?Q?Urue=F1a?= <muruenya@it.uc3m.es>
To: Qiaobing Xie <Qiaobing.Xie@motorola.com>
Cc: rserpool@ietf.org
In-Reply-To: <3FB98A05.5169F370@motorola.com>
References: <1068463190.2508.86.camel@requiem.it.uc3m.es>
	 <3FB98A05.5169F370@motorola.com>
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-x+yRqtETtur9Xxchl7HJ"
Organization: Universidad Carlos III de Madrid
Message-Id: <1069163958.2464.54.camel@requiem.it.uc3m.es>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.4.4-8mdk 
Date: Tue, 18 Nov 2003 14:59:20 +0100
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>


--=-x+yRqtETtur9Xxchl7HJ
Content-Type: text/plain; charset=iso-8859-15
Content-Transfer-Encoding: quoted-printable

Hi Qiaobing,

Good suggestion, two ports would be enough if ENRP Servers only accept
Register operations from the PE port. That port should be filtered for
IP addresses outside the Pool range to provide an additional security
level.

Just another question, I was not able to go to the IETF #58 Rserpool
meeting. Does anybody raise the MAX-BAD-PE-REPORT DoS issue?

Thanks,
--Manuel


Quiaobing Xie wrote:
>
> Hi, Manuel,
>
> I think you have raised a quite interesting point. But to further split
> ASAP seems not a good idea, since we already see the difficult for
> people to have to read two documents (ENRP and ASAP) at the same time in
> order to under RSERPOOL operations. This is because they are tightly
> related. Further split of ASAP will make this even harder.
>=20
> We may be able to achieve the same thing you described by asking for two
> separate ports for PU and PE. Just a though.
>
> regards,
> -Qiaobing
>
> Manuel Urue=F1a wrote:
> >=20
> > Hi,
> >=20
> > Reading the ASAP draft I felt that it seems a little overloaded. In
> > particular, registration operations are just employed by PEs.
> >=20
> > Maybe it would be good to put those operations in another protocol. Or
> > exactly the same ASAP protocol but without PU related operations. Of
> > course PE would require both protocols.
> >=20
> > This will ease firewall protection, I mean, with ASAP firewalls should
> > allow ASAP connections to both PEs and NSs. Therefore, remote PUs are
> > able to send Registration operations to NSs. With two separate
> > protocols, registration port could be filtered.
> >=20
> > Has been this discussed before? comments?
> >=20
> > Regards,
> > --Manuel
--=20
Manuel Uruen~a - Universidad Carlos III de Madrid
GPG FP: 68A1 164B EE28 52C9 87CB  EBF9 616E 52B5 451A B6B2

--=-x+yRqtETtur9Xxchl7HJ
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: Esta parte del mensaje =?ISO-8859-1?Q?est=E1?= firmada
	digitalmente

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQA/uiWzYW5StUUatrIRAkNeAJ9lTwW5OTXCmBjVfVHBO/KyX/sjkgCdHJSR
nG2TGji+GsePghVQ3TXw5aY=
=M5uV
-----END PGP SIGNATURE-----

--=-x+yRqtETtur9Xxchl7HJ--


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



