Re: Last Call for draft-ietf-rolc-apr-00.txt

Tim Salo <salo@msc.edu> Thu, 26 October 1995 03:23 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa00464; 25 Oct 95 23:23 EDT
Received: from guelah.nexen.com by IETF.CNRI.Reston.VA.US id aa00458; 25 Oct 95 23:23 EDT
Received: from maelstrom.nexen.com ([204.249.99.5]) by guelah.nexen.com (8.6.12/8.6.12) with ESMTP id WAA21257; Wed, 25 Oct 1995 22:50:58 -0400
Received: (from root@localhost) by maelstrom.nexen.com (8.6.12/8.6.12) id XAA03216 for rolc-out; Wed, 25 Oct 1995 23:02:00 -0400
Received: from guelah.nexen.com (guelah.nexen.com [204.249.96.19]) by maelstrom.nexen.com (8.6.12/8.6.12) with ESMTP id XAA03207 for <rolc@nexen.com>; Wed, 25 Oct 1995 23:01:57 -0400
Received: from noc.msc.edu (noc.msc.edu [137.66.12.254]) by guelah.nexen.com (8.6.12/8.6.12) with SMTP id WAA21253 for <rolc@nexen.com>; Wed, 25 Oct 1995 22:50:36 -0400
Received: from uh.msc.edu by noc.msc.edu (5.65/MSC/v3.0.1(920324)) id AA14145; Wed, 25 Oct 95 21:58:21 -0500
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Tim Salo <salo@msc.edu>
Received: (salo@localhost) by uh.msc.edu (8.7.1/8.6.6) id VAA04715; Wed, 25 Oct 1995 21:58:20 -0500 (CDT)
Date: Wed, 25 Oct 1995 21:58:20 -0500 (CDT)
Message-Id: <199510260258.VAA04715@uh.msc.edu>
To: jhalpern@newbridge.com
Subject: Re: Last Call for draft-ietf-rolc-apr-00.txt
Cc: rolc@nexen.com
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/

In message <9510251808.AA16063@lobster.Newbridge.COM>OM>, Joel Halpern writes:
> 	[...]
> This leads, to my thinking, to a document (the APR document under
> discussion) whcih discusses when one wants direct VCs.  The important
> observations (I think) are:
> 1) That the desire for direct VCs is not coupled to whether the source
>     and destination are in the same "address aggregate".  In particular, 
>     it is independent of whether they are in the same lowest level
>     "address aggregate" (traditionally known as "subnet").
>	[...]

For what it is worth, in "real world" ATM, there may be some relationship
between the desire for direct VCs and whether the source and destination
are topologically "near" each other.  In particular, SVCs are [perhaps
almost] possible in local ATM networks, but are not available in
wide-area ATM services provided by carriers.  When carriers provide
SVCs, users may want to have different criteria for using local- and
wide-area SVCs, particularly if one costs real money (darn intrusion of
the "real" world) and the other doesn't.

It is not clear to me how "SVCs exist," "SVCs don't exist," "SVCs are
free," and "SVCs cost money" map into "address aggregates."  On the
other hand, it is fairly clear to me that users, (if we asked them and
if they had a clue what we were talking about), would want to control
the portions of their topology over which SVCs were used.

-------

Note that Curtis' reply to Joel included:

> We're engineers.  We don't beleive in magic.  If you want magic
> implement MPOA.  ;-)

-tjs
MAGIC Gigabit Testbed