Re: [44net] Why rip44d?

Thanks for the replies, especially from Heikki, who provided really detailed responses. A couple more questions: 1) Currently, I have the ip munge stuff putting the amprnet routes in a separate routing table. This makes my main routing table manageable/readable. Does rip44d put its routes in a separate table or in the main table? 2) I'm confused about the update/delete interval. Some have said they slow down the deletions to avoid problems with the main gateway (route sender) going away. But others have said that rip44d doesn't remove routes if it's not hearing from the route sender. In that case, it would be better not to delay the deletions. Which is correct? Comment: I did have to chuckle at Heikki's comment about how important a quick update would be if people were putting up useful services. To use a service, I first have to know about it. And I'll probably learn about it more than 24 hours after it's available. So 15 minutes routing udates don't help. But what made me chuckle was the suggestion that people would be putting up new, useful services. Several on this list keep pushing for a discussion of new services. But everyone seems to focused on routing. So we'll end up with a more complicated, albeit probably better routing path between 44-net and the Internet. But still no services! It's like the infamous bridge to nowhere. How about: 1) Split DNS (yes, this is mostly hidden infrastructure, but would help with services that shouldn't be made publically available or with services that get different treatment depending on if the user is in 44.x or not) 2) Email-APRS two-way gateway. What I can find seems to be a jumbled mess of this or that not-quite-there "solution". I don't find a universal gateway between BBS and APRS or between SMTP and APRS. The 44-net could be used to insure that SMTP to APRS messages are coming from amateurs. WL2K has something (http://www.winlink.org/aprslink). 3) Online graph of gateways and systems behind gateways to help users locate a way to contact people. WL2K: http://www.winlink.org/userPositions. IRLP: http://www.irlp.net/google.html 4) Directory. How does a user find where someone is so he/she can send them a message? From what I've seen, WP is not widely implemented due to: bugs, improper configuration, and maybe because it just doesn't work very well. Just like WL2K has <callsign>(a)winlink.orgnk.org, it would be nice to be able to reach someone using a simplified address. My own efforts are currently being spent on BBS to email gateways at all of our BBS sites. Due to the 3rd party traffic restrictions previously discussed, we're working on Internet access at each site, plus implementing email servers with spam/virus detection, etc. That's a service that the users can actually use. Michael N6MEF