IETF Logo Mail Archive

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

john.loughney@nokia.com Wed, 18 February 2004 09:38 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 EAA03821 for <rserpool-archive@lists.ietf.org>; Wed, 18 Feb 2004 04:38: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 1AtO9a-0006P3-KW; Wed, 18 Feb 2004 04:38:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AtO9K-0006Mr-VO for rserpool@optimus.ietf.org; Wed, 18 Feb 2004 04:37:47 -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 EAA03807 for <rserpool@ietf.org>; Wed, 18 Feb 2004 04:37:44 -0500 (EST)
From: john.loughney@nokia.com
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AtO9I-0001Zr-00 for rserpool@ietf.org; Wed, 18 Feb 2004 04:37:44 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AtO8N-0001XM-00 for rserpool@ietf.org; Wed, 18 Feb 2004 04:36:48 -0500
Received: from mgw-x2.nokia.com ([131.228.20.22]) by ietf-mx with esmtp (Exim 4.12) id 1AtO7R-0001UL-00 for rserpool@ietf.org; Wed, 18 Feb 2004 04:35:49 -0500
Received: from esdks003.ntc.nokia.com (esdks003.ntc.nokia.com [172.21.138.158]) by mgw-x2.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id i1I9ZnT15467; Wed, 18 Feb 2004 11:35:49 +0200 (EET)
X-Scanned: Wed, 18 Feb 2004 11:35:40 +0200 Nokia Message Protector V1.3.13 2004020314 - RELEASE
Received: (from root@localhost) by esdks003.ntc.nokia.com (8.12.9/8.12.9) id i1I9Ze0R004952; Wed, 18 Feb 2004 11:35:40 +0200
Received: from mgw-int1.ntc.nokia.com (172.21.143.96) by esdks003.ntc.nokia.com 00Jb64Dc; Wed, 18 Feb 2004 11:35:39 EET
Received: from esebh003.NOE.Nokia.com (esebh003.ntc.nokia.com [172.21.138.82]) by mgw-int1.ntc.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id i1I9Zb729835; Wed, 18 Feb 2004 11:35:37 +0200 (EET)
Received: from esebe023.NOE.Nokia.com ([172.21.138.115]) by esebh003.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6747); Wed, 18 Feb 2004 11:35:33 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Rserpool] FW: AD review of draft-ietf-rserpool-comp-07
Date: Wed, 18 Feb 2004 11:35:31 +0200
Message-ID: <DADF50F5EC506B41A0F375ABEB3206360143B6C7@esebe023.ntc.nokia.com>
Thread-Topic: [Rserpool] FW: AD review of draft-ietf-rserpool-comp-07
Thread-Index: AcP1dBqHde9s4xfYTU+Rv/7OXouGDgAjk+2g
To: Aron.J.Silverton@motorola.com, rserpool@ietf.org
X-OriginalArrivalTime: 18 Feb 2004 09:35:33.0321 (UTC) FILETIME=[8E3C9B90:01C3F602]
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=0.3 required=5.0 tests=AWL, NO_REAL_NAME autolearn=no version=2.60
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 Aron,

> > 4) Text about SLP & l4/l7 I can probably fix.
> 
> John, according to Jon P's email, the L4/L7 stuff is ". . . I 
> think the analysis here is sound. Same for the analysis of 
> L4/L7 switching."  So I wouldn't waste too many cycles on 
> that unless you feel that there is something that needs to be changed.

Agreed.  I think I can just try to clarify the text.
 
> 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.

I think we need to check the documents Jon pointed out &
craft text to cover the issue.

John

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

v2.23.0 | Report a Bug | By Email