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

schulter@zk3.dec.com Wed, 01 May 1996 16:38 UTC

Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa20636; 1 May 96 12:38 EDT
Received: from guelah.nexen.com by IETF.CNRI.Reston.VA.US id aa20631; 1 May 96 12:38 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 MAA05276; Wed, 1 May 1996 12:28:57 -0400 (EDT)
Received: (from root@localhost) by maelstrom.nexen.com (8.7.3/8.7.3) id MAA21955 for rolc-out; Wed, 1 May 1996 12:24:49 -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 MAA21946 for <rolc@nexen.com>; Wed, 1 May 1996 12:24:45 -0400 (EDT)
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: schulter@zk3.dec.com
Received: from mail13.digital.com (mail13.digital.com [192.208.46.30]) by guelah.nexen.com (8.7.3/8.7.3) with SMTP id MAA05241 for <rolc@nexen.com>; Wed, 1 May 1996 12:24:39 -0400 (EDT)
Received: from quarry.zk3.dec.com by mail13.digital.com (5.65v3.2/1.0/WV) id AA26983; Wed, 1 May 1996 12:10:04 -0400
Received: from dogfish.zk3.dec.com by quarry.zk3.dec.com (5.65v3.2/1.1.10.3/13Aug95-0523PM) id AA25427; Wed, 1 May 1996 12:09:40 -0400
Received: from localhost by dogfish.zk3.dec.com (5.65v3.2/1.1.10.3/27Jun95-1215PM) id AA22129; Wed, 1 May 1996 12:09:32 -0400
Message-Id: <9605011609.AA22129@dogfish.zk3.dec.com>
X-Mailer: exmh version 1.6.1 5/23/95
To: "Eric W. Gray" <gray@ctron.com>
Cc: schulter@zk3.dec.com, Keith McCloghrie <kzm@cisco.com>, Andrew Smith <fddi1-ncd@baynetworks.com>, dhc2@gte.com, 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 96 10:03:06 EDT." <31876F1A.4691@ctron.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Wed, 01 May 1996 12:09:31 -0400
X-Mts: smtp
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/

> Often the "user" is not actually paying the bill.  Consequently, very often
> a pop-up dialogue box would be neither appropriate nor appreciated.

Eric,

Well, someone is still paying the bill, and that person will probably want
some accountability so the costs can be passed on to the users.  Someone
still has to pay for the call, so someone has to care (unless there is a very
generous ISP or corporation out there).  If the person paying the bill
cares, then that person will want either control over the calls, our
accountability.  This would generally mean disabling cut-through except
in special cases, or passing the cost back as close as possible to the
user.  In the first case, cut-through isn't very useful because no-one
wants to pay for it (so the user doesn't worry about it).  In the
second case there's a lot of extra accounting, so the user does have
to worry about it.  I would think this would be similar to how
many institutions currently handle long-distance accounting (only
with the Internet I can see the call volume being much higher because
the use is much more casual than a voice call - like clicking on an HTML link).

Yes, many users (especially at corporations and universities) don't have
to worry about costs now, but that's because the costs are fixed.  If these
costs were not fixed, but based on usage, I would expect users would
be made to aware of (and maybe responsible for) the new costs very quickly.

The more I think about it, the more I think cut-through would very rarely
be used in the public net simply because of the cost.  Certainly most
institutions would not allow people to make indescriminate long-distance
calls which get billed to that institution. So, when would people really
want to use cut-through (assuming doing so costs money)?  How would
the cut-through decision be managed (assuming it's not managed by 
simply not using it)?

> is frequently and uniquely unqualified to determine benefit
> for a connection as well.  Just ask yourself how many of your users can 
> distinguish TCP and UDP...

I know of very few users outside this community who could distinguish TCP
from UDP, from ATM, from PPP.  But that's not what a user would be thinking
about.  A user would be thinking "how much am I willing to pay to view
that preview of next week's Babylon 5 episode?".  They don't know or
care what the mechanism used to get it is, but will want to know what
the costs involved are.  Once knowing the cost, the user will have
to decide if the desire for accessing the information is worth the
cost (highly subjective I would say).  I don't think a router could
make this decision.  Currently, these are fixed costs and are pretty
much independent of usage (i.e., local calls, monthly ISP charges, leased
lines).  

In the long run, how will people deal with the Internet if the costs become 
usage based (regardless of who ultimately pays the bills)?  And we're
not necessarily talking about usage as most people think of usage (i.e.,
some hours of local connection to an ISP or leased line charges), but usage
based on underlying network operation which is completely invisible
and magic to most users.

BTW, does cut-through imply turning an Internet-phone session into a 
long-distance phone call? ;-)

 --- pete

------------------
Peter Schulter					schulter@zk3.dec.com
Digital UNIX Networking				voice (603) 881-2920
Digital Equipment Corp				voice (DTN) 381-2920
ZK3-03/U14					FAX   (603) 881-2257
110 Spit Brook Road				FAX   (DTN) 381-2257
Nashua, NH 03062