Subj : Old Versus New - Ways
To   : Ross Cassell
From : Bob Seaborn
Date : Sun Jul 13 2008 05:14 pm

 > Hello All!
 >
 > As we see people muse over the issues of netmail routing, we do run into
 > a issue caused by the ways people link together to move or get mail.
 >
 > In the old days, one could reasonably point a routing table entry for an
 > entire network to one hub and that every routed piece of netmail for
 > anyone or everyone in that net would arrive at the target destination.
 >
 > Today it is not unusual for a network of a few people or several people
 > to have some if not all of its members /each/ have a unique separate
 > feed and then not be interconnected amongst each other.
 >
 > This poses a challenge for ones route table, its easier to point netmail
 > towards an entire net, whereas having a table that has to have
 > individual nodes pointed to several locations.
 >
 > Here in NET123, I do feed most of the nodes, but a few do feed
 > elsewhere, Joe Hub Sysop doesnt know which ones feed where, then thusly
 > gets fingered as being a netmail bottleneck, unjustly so.
 >
 > I do plan on putting up a mechanism that will allow nets/nodes and hubs
 > to report routing, but it is going to take some time.



      Every node should be prepared, and able to connect with their NC
regularly, just as every NC should be able to do the same with their RC, that 
way routing can always default to host-routed.  I believe this is stated so in 
pee4.





                       .....Bob





                       .....Bob

--- GEcho/32 & IM 2.50
 * Origin: www.nwstar.com - Backbone Provider (1:140/12)

.