Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 4.3bsd-beta 6/6/85; site ucbvax.BERKELEY.EDU
Path: utzoo!watmath!clyde!cbosgd!ucbvax!info-vax
From: MIGLESIAS@UCIVMS.BITNET
Newsgroups: mod.computers.vax
Subject: Re: Problem with async DECnet
Message-ID: <8601171303.AA12051@ucbvax.berkeley.edu>
Date: Fri, 17-Jan-86 08:03:43 EST
Article-I.D.: ucbvax.8601171303.AA12051
Posted: Fri Jan 17 08:03:43 1986
Date-Received: Sat, 18-Jan-86 01:21:00 EST
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 14
Approved: info-vax@sri-kl.arpa

I found the passage in the other site's 4.2 manual after I sent the
message.  I also feel that it is an arbitrary restriction;  a warning
in the manual about high traffic if you are connecting two area
routers (if this is indeed the case for not allowing it) would have
been sufficient.  This restriction gives us less flexibility in
how we set up any campus-wide DECnet; we now have to assign
node numbers to people instead of saying "Here's a DECnet area
for your department; assign the node numbers however you want".

I'd like to hear the reason for this myself;  How about it DEC?


Mike Iglesias
University of California, Irvine