Re: int-serv over e.g. ATM

Andrew Smith <asmith@baynetworks.com> Tue, 14 November 1995 03:23 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa27972; 13 Nov 95 22:23 EST
Received: from guelah.nexen.com by IETF.CNRI.Reston.VA.US id aa27968; 13 Nov 95 22:23 EST
Received: from maelstrom.nexen.com (maelstrom.nexen.com [204.249.99.5]) by guelah.nexen.com (8.6.12/8.6.12) with ESMTP id VAA01603; Mon, 13 Nov 1995 21:52:50 -0500
Received: (from root@localhost) by maelstrom.nexen.com (8.6.12/8.6.12) id WAA16820 for rolc-out; Mon, 13 Nov 1995 22:06:06 -0500
Received: from nexen.nexen.com (nexen.nexen.com [204.249.96.18]) by maelstrom.nexen.com (8.6.12/8.6.12) with ESMTP id WAA16811 for <rolc@nexen.com>; Mon, 13 Nov 1995 22:06:03 -0500
Received: from lightning.synoptics.com (lightning.synoptics.com [134.177.3.18]) by nexen.nexen.com (8.6.12/8.6.12) with SMTP id WAA01599 for <rolc@nexen.com>; Mon, 13 Nov 1995 22:03:38 -0500
Received: from pobox.synoptics.com ([134.177.1.95]) by lightning.synoptics.com (4.1/SMI-4.1) id AA07879; Mon, 13 Nov 95 19:00:14 PST
Received: from milliways-le0.engwest (milliways-le0.synoptics.com) by pobox.synoptics.com (4.1/SMI-4.1) id AA09554; Mon, 13 Nov 95 19:01:38 PST
Received: by milliways-le0.engwest (4.1/SMI-4.1) id AA07911; Mon, 13 Nov 95 19:01:37 PST
Date: Mon, 13 Nov 95 19:01:37 PST
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Andrew Smith <asmith@baynetworks.com>
Message-Id: <9511140301.AA07911@milliways-le0.engwest>
To: int-serv@isi.edu, rolc@nexen.com, jnc@ginger.lcs.mit.edu
Subject: Re: int-serv over e.g. ATM
X-Orig-Sender: owner-rolc@nexen.com
Precedence: bulk
X-Info: Submissions to rolc@nexen.com
X-Info: [Un]Subscribe requests to rolc-request@nexen.com
X-Info: Archives for rolc via ftp://ietf.cnri.reston.va.us/ietf-mail-archive/rolc/

> Date: Sat, 11 Nov 95 12:14:32 -0500
> From: jnc@ginger.lcs.mit.edu (Noel Chiappa)
> To: curtis@ans.net, int-serv@ISI.EDU, rolc@nexen.com, rsvp@ISI.EDU
> Subject: Re: int-serv over e.g. ATM
> Cc: jnc@ginger.lcs.mit.edu

Noel,

>     From: Curtis Villamizar <curtis@ans.net>
> 
>     On the other hand, SVCs may cost money. ... If you can often use either a
>     shared VC to the router (shared with other traffic from the same router) or
>     use a VC to that router rather than a direct VC all the way, you might
>     still get the QoS you want and reduce your costs when the router is lightly
>     loaded, and get the QoS you want when rejected using a direct VC.
> 
> This sounds to me like a pricing anomaly, i.e. an artifact of prices that
> don't correspond to the actual resources used. Carrying the packets around
> should cost the same in terms of resources consumed, no matter how many layers
> of mechanism you use to do it. So, I'm not sure how imporant this case is; it
> might go away since the market tends to drive prices toward "real" prices.

Unfortunately, reality intervenes in the short term :-( 

> About the only reason I can think of where it might be genuinely cheaper is if
> you have saved the overhead of state/setup required for a separate VC all
> through the net. If this is that big a deal, how come ATM isn't trying to
> aggregate VC's? 

The state overhead of VCs is considerable and relatively badly understood. The 
state involved for connectionless (best-effort) forwarding in a router is minimal 
and is well understood. The state for QoS-based forwarding in a router is significantly
less than that for VCs. ATM is trying to crawl before it tries running or even 
walking. VC aggregation into VPs will come later.

> But the "do we have to aggregate flows" is a whole separate
> can of worms.

It is not yet clear whether explicit-QoS flows need to be aggregated (the answer
is probably: "yes, but not urgently right now"). It is clear that best-effort flows 
do need to be, just in order to be able to build ATM-based networks as large as 
existing LAN-based ones are are now, let alone allowing for growth.

> 	Noel
> 

Andrew


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