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

Grenville Armitage <gja@bellcore.com> Wed, 01 May 1996 14:53 UTC

Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa17276; 1 May 96 10:53 EDT
Received: from guelah.nexen.com by IETF.CNRI.Reston.VA.US id aa17268; 1 May 96 10:53 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 KAA04506; Wed, 1 May 1996 10:45:42 -0400 (EDT)
Received: (from root@localhost) by maelstrom.nexen.com (8.7.3/8.7.3) id KAA20852 for rolc-out; Wed, 1 May 1996 10:44:25 -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 KAA20843 for <rolc@nexen.com>; Wed, 1 May 1996 10:44:22 -0400 (EDT)
Received: from thumper.bellcore.com (thumper.bellcore.com [128.96.41.1]) by guelah.nexen.com (8.7.3/8.7.3) with SMTP id KAA04494 for <rolc@nexen.com>; Wed, 1 May 1996 10:44:20 -0400 (EDT)
Received: from thumper (localhost [127.0.0.1]) by thumper.bellcore.com (8.6.12/8.6.11) with ESMTP id KAA18246; Wed, 1 May 1996 10:44:04 -0400
Message-Id: <199605011444.KAA18246@thumper.bellcore.com>
To: "Eric W. Gray" <gray@ctron.com>
cc: gja@bellcore.com, rolc@nexen.com
Subject: Re: VCC cost models .... (was Re: Limits on SVCCs)
In-reply-to: Your message of Wed, 01 May 1996 10:03:06 -0400. <31876F1A.4691@ctron.com>
Date: Wed, 01 May 1996 10:43:47 -0400
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Grenville Armitage <gja@bellcore.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/

Eric,

>>	BTW, the "user" - sometimes referred to as the loose connection between
 the
>>keyboard and the seat - is frequently and uniquely unqualified to determine b
enefit
>>for a connection as well.  Just ask yourself how many of your users can disti
nguish
>>TCP and UDP...

Let's not get too carried away with the detail :-)

The 'service' is not TCP or UDP from this users's perspective. It's
a web page, a RealAudio connection, an mpeg movie snippet. For
these things I have a personal and somtimes dynamic sense of their worth.
If you can collapse trade-offs like TCP vs UDP, or hop-by-hop vs cut-through,
into some sort of comparative dollar figure, I can tell you which option
I think is 'worth it'. Right at the moment, the axis along which most
people will find cost sensitivity will be the long-vs-short distance
ATM call. Which NHRP impacts on.

Interesting problem, no?

cheers,
gja

(for the last year or so the related question of cut-through MARS
has popped up a number of times. needless to say this, umm, makes
for interesting back-of-the-envelope calculations as you figure
out who pays when _you_ request to join a Class D group and suddenly
force a number of senders to add a long-distance leaf node to their
pt-mpt VCs.)