VCC cost models .... (was Re: Limits on SVCCs)

Andrew Smith <fddi1-ncd@baynetworks.com> Tue, 30 April 1996 00:10 UTC

Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa21002; 29 Apr 96 20:10 EDT
Received: from guelah.nexen.com by IETF.CNRI.Reston.VA.US id aa20998; 29 Apr 96 20:10 EDT
Received: from maelstrom.nexen.com (maelstrom.nexen.com [204.249.97.5]) by guelah.nexen.com (8.7.3/8.7.3) with ESMTP id UAA25858; Mon, 29 Apr 1996 20:02:56 -0400 (EDT)
Received: (from root@localhost) by maelstrom.nexen.com (8.7.3/8.7.3) id UAA25690 for rolc-out; Mon, 29 Apr 1996 20:02:31 -0400 (EDT)
Received: from guelah.nexen.com (guelah.nexen.com [204.249.96.19]) by maelstrom.nexen.com (8.7.3/8.7.3) with ESMTP id UAA25681 for <rolc@nexen.com>; Mon, 29 Apr 1996 20:02:28 -0400 (EDT)
Received: from lightning.synoptics.com (lightning.synoptics.com [134.177.3.18]) by guelah.nexen.com (8.7.3/8.7.3) with SMTP id UAA25854 for <rolc@nexen.com>; Mon, 29 Apr 1996 20:02:27 -0400 (EDT)
Received: from pobox ([134.177.1.95]) by lightning.synoptics.com (4.1/SMI-4.1) id AA10466; Mon, 29 Apr 96 16:44:13 PDT
Received: from milliways-le0.engwest by pobox (4.1/SMI-4.1) id AA07382; Mon, 29 Apr 96 16:39:41 PDT
Received: by milliways-le0.engwest (4.1/SMI-4.1) id AA29264; Mon, 29 Apr 96 16:39:41 PDT
Date: Mon, 29 Apr 1996 16:39:41 -0700
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Andrew Smith <fddi1-ncd@baynetworks.com>
Message-Id: <9604292339.AA29264@milliways-le0.engwest>
To: dhc2@gte.com, gja@bellcore.com
Subject: VCC cost models .... (was Re: Limits on SVCCs)
Cc: rolc@nexen.com
X-Orig-Sender: owner-rolc@nexen.com
Precedence: bulk
X-Info: [Un]Subscribe to rolc-request@nexen.com, submissions to rolc@nexen.com
X-Info: Email archive at ftp://ietf.cnri.reston.va.us/ietf-mail-archive/rolc/
X-Info: Hypermail archive at http://cell-relay.indiana.edu/mail/archives/rolc/
X-Info: FTP archive at ftp://ftp.nexen.com/pub/rolc/

> From owner-rolc@nexen.com Mon Apr 29 13:27:06 1996
> To: Derya Cansever <dhc2@gte.com>
> Cc: rolc@nexen.com, gja@thumper.bellcore.com
> Subject: Re: Limits on SVCCs 
> In-Reply-To: Your message of Mon, 29 Apr 1996 15:44:43 -0400.
>              <199604291944.PAA02276@ns.gte.com> 
> Date: Mon, 29 Apr 1996 16:17:47 -0400
> From: Grenville Armitage <gja@bellcore.com>

> Thirdly, the cost of the new VC wrt the original one that the client
> presumably had open to their default router. Customers need to
> be able to characterize the total benefit to themselves before
> they'll be happy having NHRP tell them to place a long-distance
> ATM call instead of a local call. 

This, in a nutshell, is one of the big NHRP issues: the client is in a 
position to know how much it wants to pay for the connection but the network 
is the only place that knows how much it will cost. With NHRP as the
signaling protocol, there is no way to set up a mutually beneficial deal.
Even worse than this is a situation with an intervening "low-cost" proxy-client 
which probably does not communicate any form of cost information with the real 
client (who is the one with the open wallet).

> cheers,
> gja
> 

Andrew

********************************************************************************
Andrew Smith					TEL:	+1 408 764 1574
Bay Networks, Inc. 				FAX:	+1 408 988 5525
Santa Clara, CA					E-m:	asmith@baynetworks.com
********************************************************************************