home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.dcom.cell-relay
- Path: sparky!uunet!stanford.edu!kronos.arc.nasa.gov!iscnvx!news
- From: bantha.decnet.lockheed.com!young
- Subject: Paths Revisited
- Message-ID: <1992Sep1.164341.19063@iscnvx.lmsc.lockheed.com>
- Reply-To: young@bantha.decnet.lockheed.com
- Sender: news@iscnvx.lmsc.lockheed.com (News)
- Organization: LMSC, Sunnyvale, California
- Date: Tue, 1 Sep 92 16:43:41 GMT
- Lines: 24
-
-
- |>
- |> For a user connected to an arbitrary local ATM switch it is unlikely
- |> the DNS will be able to return a VCI/VPI pair having any meaningful
- |> value. The VCI/VPI which finally carries IP packets into foo@bar.sna.fu
- |> will be different to the the VCI (and/or VPI) that any given user
- |> needs to send packets to their local ATM switch on.
- |>
- > As you've indicated, a VCI/VPI pair is only meaningful between host and
- > first switch. At the switch it's translated into a different VCI/VPI.
-
- Examine this basic assumption. In private networks, it is likely that
- a few vci/vpi pair values will be reserved for global usage. Also it
- is likely that departmental enterprises will be granted some permanent
- VCI pair for use over their geographic domain. Thus some VCI will have
- global functions though not necessarily associated with a particular
- host.
-
- We agree that the VCI is a local pointer only, generally only valid on
- a temporary scale, but the use of virtual paths does solve a host of
- customer problems directly. Super computers have been based upon virtual
- paths (look at some transputer architectures). However, these
- supercomputers allowed self-routing and track building by the application
- themselves, the applications actually becoming migratory.
-