RE: [Rserpool] FW: AD review of draft-ietf-rserpool-comp-07

Manuel Urueña <muruenya@it.uc3m.es> Tue, 17 February 2004 20:27 UTC

Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA02822 for <rserpool-archive@odin.ietf.org>; Tue, 17 Feb 2004 15:27:29 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AtBo5-0003HQ-1O for rserpool-archive@odin.ietf.org; Tue, 17 Feb 2004 15:27:01 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i1HKR0YK012585 for rserpool-archive@odin.ietf.org; Tue, 17 Feb 2004 15:27:00 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AtBo4-0003Gs-IG; Tue, 17 Feb 2004 15:27:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AtBnW-0003Ej-3a for rserpool@optimus.ietf.org; Tue, 17 Feb 2004 15:26:26 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA02771 for <rserpool@ietf.org>; Tue, 17 Feb 2004 15:26:23 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AtBnT-0001VJ-00 for rserpool@ietf.org; Tue, 17 Feb 2004 15:26:23 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AtBmc-0001PX-00 for rserpool@ietf.org; Tue, 17 Feb 2004 15:25:30 -0500
Received: from smtp02.uc3m.es ([163.117.136.122]) by ietf-mx with esmtp (Exim 4.12) id 1AtBll-0001Gc-00 for rserpool@ietf.org; Tue, 17 Feb 2004 15:24:37 -0500
Received: from smtp02.uc3m.es (localhost [127.0.0.1]) by localhost.uc3m.es (Postfix) with ESMTP id C70117F64; Tue, 17 Feb 2004 21:24:06 +0100 (CET)
Received: from requiem.it.uc3m.es (requiem.it.uc3m.es [163.117.139.166]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by smtp02.uc3m.es (Postfix) with ESMTP id B36E47F47; Tue, 17 Feb 2004 21:24:06 +0100 (CET)
Subject: RE: [Rserpool] FW: AD review of draft-ietf-rserpool-comp-07
From: Manuel Urueña <muruenya@it.uc3m.es>
To: Silverton Aron-C1710C <Aron.J.Silverton@motorola.com>
Cc: rserpool@ietf.org
In-Reply-To: <6F8DFFA2C996D711945800065BFC9E4A0389878A@il02exm11>
References: <6F8DFFA2C996D711945800065BFC9E4A0389878A@il02exm11>
Content-Type: text/plain
Organization: Universidad Carlos III de Madrid
Message-Id: <1077049264.3614.37.camel@requiem.it.uc3m.es>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.4.4-8mdk
Date: Tue, 17 Feb 2004 21:21:06 +0100
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: rserpool-admin@ietf.org
Errors-To: rserpool-admin@ietf.org
X-BeenThere: rserpool@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <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

> ...
>
> As for the other portions, I'm not familiar with them so I will have to 
> read the drafts.  I think that some of the comments that Qiaobing made 
> in the past regarding loosely-coupled approaches of trying to integrate 
> many protocols versus a tightly-coupled protocol (RSERPOOL) will hold 
> here as well.  All the more so if we stress that RSERPOOL is intended 
> for system with some degree of real-time performance constraints.
>
> Aron

What do you mean by systems with "real-time" performance constraints?

If it means to quickly obtain the best server from a pool maybe the
mandatory usage of SCTP is not an optimal solution.

Let's imagine an user that wants to access a web-service served by a
pool of servers. That means that first it has to establish a SCTP
connection to the ENRP server (4-way handshake), get server info, and
finally open a TCP connection (3-way handshake) to the selected web
server for the HTTP transaction. It makes more or less 4,5 RTTs.

It seems that querying ENRP servers via UDP will lead to better
server-selection latency for "real-time" services (2'5 RTTS for TCP
connections).

Regards,
--Manuel

-- 
Manuel Uruen~a - Universidad Carlos III de Madrid
GPG FP: 68A1 164B EE28 52C9 87CB  EBF9 616E 52B5 451A B6B2


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