home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!cs.utexas.edu!uwm.edu!rutgers!ub!dsinc!cs.widener.edu!iggy.GW.Vitalink.COM!nocsun.NOC.Vitalink.COM!RODIN!dgr
- From: dgr@RODIN (Daniel Robinson)
- Newsgroups: comp.dcom.cell-relay
- Subject: Re: Path Building
- Message-ID: <1992Dec21.172520.7107@NOC.Vitalink.COM>
- Date: 21 Dec 92 17:25:20 GMT
- References: <1992Dec17.211811.6553@iscnvx.lmsc.lockheed.com>
- Sender: usenet@NOC.Vitalink.COM (Usenet News Admin)
- Organization: Vitalink Communications, Fremont, California
- Lines: 14
- Nntp-Posting-Host: rodin.eng.vitalink.com
-
- In article <1992Dec17.211811.6553@iscnvx.lmsc.lockheed.com> myoung@force.ssd.lmsc.lockheed.com writes:
- +OK, I have a problem here:
- +
- + (stuff about path discovery deleted)
- +
- + Don't tell me that a hidden hand in the network management will do this
- +for me, as that just begs the question.
-
- Well, that's the way it is. The paradigm to follow is not one of the
- many network standards, but the trusty phone. The phone does not do
- path discovery; terminal nodes connected to a network mesh should not
- do path discovery either.
-
- Dan Robinson
-