Re: [nemo] Multihoming and Load sharing.

William D Ivancic <wivancic@grc.nasa.gov> Tue, 11 November 2003 18:19 UTC

Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA14139 for <nemo-archive@lists.ietf.org>; Tue, 11 Nov 2003 13:19: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 1AJd6T-0000LG-1u; Tue, 11 Nov 2003 13:19:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AJbVa-0005Vy-5c for nemo@optimus.ietf.org; Tue, 11 Nov 2003 11:36:50 -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 LAA08735 for <nemo@ietf.org>; Tue, 11 Nov 2003 11:36:37 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AJbVZ-0005b0-00 for nemo@ietf.org; Tue, 11 Nov 2003 11:36:49 -0500
Received: from seraph2.grc.nasa.gov ([128.156.10.11]) by ietf-mx with esmtp (Exim 4.12) id 1AJbVY-0005aE-00 for nemo@ietf.org; Tue, 11 Nov 2003 11:36:48 -0500
Received: from lombok-fi.grc.nasa.gov (lombok-fi.grc.nasa.gov [139.88.112.33]) by seraph2.grc.nasa.gov (Postfix) with ESMTP id D1ED9689E6 for <nemo@ietf.org>; Tue, 11 Nov 2003 11:36:17 -0500 (EST)
Received: from acs-viruswall.grc.nasa.gov (acs-viruswall.grc.nasa.gov [139.88.112.21]) by lombok-fi.grc.nasa.gov (NASA GRC TCPD 8.12.10/8.12.10) with ESMTP id hABGaDgG016093; Tue, 11 Nov 2003 11:36:13 -0500 (EST)
Received: from GR7700006462.grc.nasa.gov (localhost [127.0.0.1]) by acs-viruswall.grc.nasa.gov (NASA GRC 8.12.10/8.12.10) with ESMTP id hABGa87J016356; Tue, 11 Nov 2003 11:36:10 -0500 (EST)
X-Info: ODIN / NASA Glenn Research Center
Message-Id: <5.1.1.5.2.20031111112645.02171de8@popserve.grc.nasa.gov>
X-Sender: caivanc@popserve.grc.nasa.gov
X-Mailer: QUALCOMM Windows Eudora Version 5.1.1
Date: Tue, 11 Nov 2003 11:35:13 -0500
To: Thierry Ernst <ernst@sfc.wide.ad.jp>
From: William D Ivancic <wivancic@grc.nasa.gov>
Subject: Re: [nemo] Multihoming and Load sharing.
Cc: nemo@ietf.org
In-Reply-To: <20031111044540.07973228.ernst@sfc.wide.ad.jp>
References: <5.1.1.5.2.20031108092238.02148788@popserve.grc.nasa.gov> <5.1.1.5.2.20031108092238.02148788@popserve.grc.nasa.gov>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Sender: nemo-admin@ietf.org
Errors-To: nemo-admin@ietf.org
X-BeenThere: nemo@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nemo>, <mailto:nemo-request@ietf.org?subject=unsubscribe>
List-Id: NEMO Working Group <nemo.ietf.org>
List-Post: <mailto:nemo@ietf.org>
List-Help: <mailto:nemo-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nemo>, <mailto:nemo-request@ietf.org?subject=subscribe>

Hello Theirry,

Actually most if not all of the multihoming documents refer to load sharing 
a policy routing.

draft-charbon-nemo-multihoming-evaluation-00
draft-ng-nemo-multihoming-issues-02
draft-paik-nemo-multihoming-problem-00

I agree that load sharing is not a MUST.  However it certainly may be 
desirable as is policy-based routing.   I simply want to point out that one 
should be careful to use such mechanisms wisely least your performance may 
suffer (or at least not gain as much benefit as thought) and/or you budget 
may suffer.  The later can be much more painful.

Will



At 04:45 AM 11/11/2003 +0900, Thierry Ernst wrote:

>Hi Will,
>
>When speaking about load-sharing, do you refer to a particular document
>?
>
>As far I know, load-sharing is only described as a potential benefit,
>not as something that must be supported. This is a result of being
>multihomed, not as pre-requisite. That fully allow it, other mechanisms
>are necessary on top of the signaling mechanism. The former may not be
>an IETF task.
>
>Thierry.
>
> > Whereas I can see configurations where it would be advantageous to allow
> > load sharing such as if one has two or three G3 wireless links up all with
> > relatively the same cost and bandwidth.
> >
> > However, IMHO there should definitely be a mechanism to turn load sharing
> > off.  It would be quite useless and very expensive to load share between
> > and WiFi link cost $80.00 per month unlimited service  and a 64 kbps
> > satellite link costing $1.00 per minute.