Re: VCC cost models .... (was Re: Limits on SVCCs)
schulter@zk3.dec.com Wed, 01 May 1996 18:27 UTC
Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa24626; 1 May 96 14:27 EDT
Received: from guelah.nexen.com by IETF.CNRI.Reston.VA.US id aa24621; 1 May 96 14:27 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 OAA06705; Wed, 1 May 1996 14:19:12 -0400 (EDT)
Received: (from root@localhost) by maelstrom.nexen.com (8.7.3/8.7.3) id OAA23560 for rolc-out; Wed, 1 May 1996 14:17:15 -0400 (EDT)
Received: from nexen.nexen.com (nexen.nexen.com [204.249.96.18]) by maelstrom.nexen.com (8.7.3/8.7.3) with ESMTP id OAA23551 for <rolc@nexen.com>; Wed, 1 May 1996 14:17:12 -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 nexen.nexen.com (8.7.3/8.7.3) with SMTP id OAA29892 for <rolc@nexen.com>; Wed, 1 May 1996 14:17:10 -0400 (EDT)
Received: from ohunch.zk3.dec.com by mail13.digital.com (5.65v3.2/1.0/WV) id AA17711; Wed, 1 May 1996 14:10:00 -0400
Received: from dogfish.zk3.dec.com by hunch.zk3.dec.com; (5.65v3.2/1.1.8.2/11Mar96-0342PM) id AA20430; Wed, 1 May 1996 14:09:56 -0400
Received: from localhost by dogfish.zk3.dec.com (5.65v3.2/1.1.10.3/27Jun95-1215PM) id AA23313; Wed, 1 May 1996 14:09:59 -0400
Message-Id: <9605011809.AA23313@dogfish.zk3.dec.com>
X-Mailer: exmh version 1.6.1 5/23/95
To: "Eric W. Gray" <gray@ctron.com>
Cc: Grenville Armitage <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 12:25:12 EDT." <31879068.26AB@ctron.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Wed, 01 May 1996 14:09:59 -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/
Eric, > My point was that the right place to make the decision to allow for a short- > cut is most often in the network (not the host). My point is that the right place to make this decision is at the entity which will (ultimately) pay the bill. >> Interesting problem, no? >> > > Only as an implementation detail... I think it's more than just an implementation detail, it's a major shift in the way that people (users or the owners of edge devices) have to deal with the costs of Internet usage. > It may be due to my somewhat faulty intuition, but I suspect that _you_ > (whoever _you_ is) pays... This is another interesting problem, moreso than the unicast case. I agree that it's unreasonable to expect the senders to pay for the call. So, if the MC sender (either a sender or MCS) places the call to the receiver (the _you_ in this case), and we expect the receiver (the user or an edge device) to pay, this looks to me like a collect call (and in the MCS case, who pays for the calls from the senders to the MCS?). So if a receiver joins an MC group then it (or the edge device which connects it to the ATM network) could get hit with any number of collect calls (one per possible sender) as the result? If so, this is a big change in how people will have to deal with the costs of operating and administering the Internet. This is also a technical issue. That is, what mechanism do we have for properly screening incoming collect calls at any directly connected ATM device? How would any directly connected device determine which collect calls to accept and, if passing on the charges to users, how to bill them. MC cut-through raises a lot of really interesting (and nasty?) issues. Again, all this really only applies to the Internet when the cost of these connections would be high. LAN and campus networks (where presumably the costs are negligable or very low) would appear to be in a position to benifit more from cut-through (unicast or MC). --- 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
- VCC cost models .... (was Re: Limits on SVCCs) Andrew Smith
- Re: VCC cost models .... (was Re: Limits on SVCCs) Keith McCloghrie
- Re: VCC cost models .... (was Re: Limits on SVCCs) schulter
- Re: VCC cost models .... (was Re: Limits on SVCCs) Tim Salo
- Re: VCC cost models .... (was Re: Limits on SVCCs) Curtis Villamizar
- Re: VCC cost models .... (was Re: Limits on SVCCs) Eric W. Gray
- Re: VCC cost models .... (was Re: Limits on SVCCs) schulter
- Re: VCC cost models .... (was Re: Limits on SVCCs) Eric W. Gray
- Re: VCC cost models .... (was Re: Limits on SVCCs) Grenville Armitage
- Re: VCC cost models .... (was Re: Limits on SVCCs) schulter
- Re: VCC cost models .... (was Re: Limits on SVCCs) Eric W. Gray
- Re: VCC cost models .... (was Re: Limits on SVCCs) Grenville Armitage
- Re: VCC cost models .... (was Re: Limits on SVCCs) Andrew Smith
- Re: VCC cost models .... (was Re: Limits on SVCCs) schulter
- Re: VCC cost models .... (was Re: Limits on SVCCs) schulter
- Re: VCC cost models .... (was Re: Limits on SVCCs) bgleeson
- Re: VCC cost models .... (was Re: Limits on SVCCs) Joel Halpern
- Re: VCC cost models .... (was Re: Limits on SVCCs) Grenville Armitage
- Re: VCC cost models .... (was Re: Limits on SVCCs) Eric W. Gray
- Re: VCC cost models .... (was Re: Limits on SVCCs) Eric W. Gray
- Re: Re: VCC cost models .... (was Re: Limits on S… Charles J. Ludinsky