Re: VCC cost models .... (was Re: Limits

"Silverman, Steve" <ssilverman@reston.btna.com> Thu, 02 May 1996 17:24 UTC

Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa07187; 2 May 96 13:24 EDT
Received: from guelah.nexen.com by IETF.CNRI.Reston.VA.US id aa07183; 2 May 96 13:24 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 NAA12431; Thu, 2 May 1996 13:16:23 -0400 (EDT)
Received: (from root@localhost) by maelstrom.nexen.com (8.7.3/8.7.3) id NAA05076 for rolc-out; Thu, 2 May 1996 13:13:00 -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 NAA05067 for <rolc@nexen.com>; Thu, 2 May 1996 13:12:56 -0400 (EDT)
Received: from server1.BTNA.COM (server1.BTNA.COM [204.176.28.225]) by guelah.nexen.com (8.7.3/8.7.3) with SMTP id NAA12419 for <rolc@nexen.com>; Thu, 2 May 1996 13:12:28 -0400 (EDT)
Message-Id: <199605021712.NAA12419@guelah.nexen.com>
Received: from ntserver1.BTNA.COM by server1.BTNA.COM with SMTP (1.38.193.4/16.2) id AA24562; Thu, 2 May 1996 13:12:17 -0400
Date: Thu, 02 May 1996 14:20:00 -0400
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: "Silverman, Steve" <ssilverman@reston.btna.com>
Subject: Re: VCC cost models .... (was Re: Limits
To: rolc <rolc@nexen.com>
Encoding: 59 TEXT
X-Mailer: Microsoft Mail V3.0
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/

There is apparently a widespread assumption that doing an SVC "shortcut or 
cut-thru
will create an additional cost.   If this is true, I doubt that any of this
will get deployed.  I think most of the IP over ATM enthusiasts believe it 
will
cut rather than increase costs.

I think there is confusion over price vs. costs.   The Internet has always
been cheap in price because the US government subsidized it.  If you knew 
what
it actually cost during the early '80s,  those of you who payed those taxes 
would howl!

On the other hand, the U.S. has a long tradition of having long distance
subsidize access costs via a high usage charge far beyond the cost of 
service delivery.
This was a deliberate decision by govt. regulators which was undercut over 
the last 15 years by
the creation of competition among IXCs but the philosophy lives on in 
certain ways.

The assumption is that call setup is a large cost in creating a VC.

For an IP packet: the first packet involves a routing decision and caching 
that decision for each switch.

For a VC, the first packet involves a routing decision (considering traffic 
load in the net), caching that decision
in each switch, and setting up the call accounting info so the user can be 
charged.

In order to do decent QoS, the IP network will have to start considering 
traffic load.
If the VC network did not do usage billing, and simply did no call 
accounting, the cost associated with
the call setup is not that different than the cost of an IP "session". 
 (Look out for TELCO people
committing suicide at the mention of eliminating the usage charge. :-)   ) 

We will need a fair amount of computer power to do call control but that is 
only
a "Small Matter of Silicon" and so far the price of silicon has dropped 
almost as fast as the
software gobbled it up.  Call control would appear to lend itself to 
parallel processing.

In my opinion, one reason for the growth of certain services in the U.S. is 
flat rate charging.
If this industry is going to continue to grow, one helpful factor would 
appear to be such flat
rate charging.  If every Web page click is answered with a reminder of an 
additional charge,
usage will be low, and we are wasting our time.


My personal opinion, not my employer's
Steve Silverman