[aprssig] Modification to AE5PL's routing idea
AE5PL Lists HamLists at ametx.comTue Feb 15 15:29:29 UTC 2005
- Previous message: [aprssig] Modification to AE5PL's routing idea
- Next message: [aprssig] IGate wildcards/Telpac data
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Good comments, Wes. The difficulty I see with your concept, however, is that supporting any source routing is detrimental and far too easy to abuse. As for your example of the NWS info, it should only be gated to RF for LAN use. If someone 100 miles away is covered by the same NWS office, they can gate those packets to their LAN, if they desire. The whole concept is that local digipeater operators define what their local area is thereby reducing the potential for abuse, either intentional or, more likely, accidental. With interconnection of LAN's available both via RF and Internet backbones, the user really shouldn't have to care what that local RF area is nor should the user need to ever modify their path. 73, Pete Loveall AE5PL mailto:pete at ae5pl.net > -----Original Message----- > From: Wes Johnston > Posted At: Tuesday, February 15, 2005 9:09 AM > Subject: [aprssig] Modification to AE5PL's routing idea > > The thing I didn't like about this idea was that the users > could not specify a smaller area than the area of digipeaters > who were programmed for a given area
- Previous message: [aprssig] Modification to AE5PL's routing idea
- Next message: [aprssig] IGate wildcards/Telpac data
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the aprssig mailing list
