Path: utzoo!mnetor!uunet!husc6!think!ames!necntc!jeff
From: jeff@necntc.nec.com (Jeff Janock)
Newsgroups: news.sysadmin
Subject: Re: To those who are asking me to (re-)post UNaXcess...
Message-ID: <13319@necntc.nec.com>
Date: 20 Jan 88 18:26:42 GMT
References: <7072@ncoast.UUCP> <12948@necntc.NEC.COM> <7088@ncoast.UUCP> <268@tmsoft.UUCP>
Organization: NEC Electronics Inc.  Natick, MA 01760
Lines: 31

In article <268@tmsoft.UUCP> mason@tmsoft.UUCP (Dave Mason) writes:
>
>Well then, change the PUBLISHED map information to show
>necntc<-->ncoast as expensive, and no one (or at least no smart mailer)
>WILL use it.  Your private (Path.local) can show the real info for low
>traffic transfers.  It is unreasonable to expect people to hard code
>paths when the map gets as large as it is now, and changes from week
>to week.  Fudge the data to get the results you want :-).
>
>In our local area this is quite a popular game.  Site x notices a lot
>of traffic going over a fast long distance link, so changes the map
>entry.... lo and behold, next week all the traffic has switched to
>site y, so they change their map entry.... great fun :-)
>	../Dave

This is an interesting observation - I would like to point out in this
case, necntc made the ncoast cost WEEKLY*8 for a period of time -
email still flowed to ncoast via necntc, but only when hardcoded
to do so...  The changes made to the path database was also
interesting as routing changed as expected!  Keeping a Path.Local
is also a good idea as link info changes rather dramically sometimes
and the admins of each site know best what is happening to the
neighboring sites (most of the time :-)

Map updates now can go out quite swiftly, so admins should not hesitate
to update their map entries WHENEVER needed...

	-jj
-- 
Jeff Janock - UUCP Project New England Map Coordinator
{decvax,harvard,mit-eddie,linus,adelie, etc}!necntc!nemap