[aprssig] IGate wildcards/Telpac data

[AE5PL Lists]

> -----Original Message-----
> From: A.J. Farmer (AJ3U)
> Posted At: Tuesday, February 15, 2005 10:31 AM
> Subject: RE: [aprssig] IGate wildcards/Telpac data
> 
> I don't think we should stray from the AX.25 specs for 
> convenience or filtering purposes.
> 
> Should we start prefixing weather stations with WX- , 
> balloons with BA- , Digi's with DI- , etc. ?  Of course not.  

You could and it wouldn't hurt a thing (other than findu).  Don't get
hung up on the AX.25 spec when it comes to APRS-IS.  We do not use AX.25
on APRS-IS.  We use text/binary strings that loosely follow the TNC-2
monitor mode format.  As Bob points out, that has always been assumed to
mean ANY 9 characters for a callsign-SSID.

> As far as IGate wildcards, I also agree that it should be 
> discouraged.  By restricting the use of wildcards, it 
> encourages IGate operators to monitor and attend to their 
> stations which is part of network stewardship.  To many "set 
> it and forget it" abilities when dealing with the tremendous 
> amount of data on the APRS-IS combined with an unattended 
> IGate just opens up the network to potential problems. 

Maybe so.  Guess we should also force trackers to have speakers in the
vehicles (and be visible) so the operator is a good "steward" of the
network and doesn't transmit too often or get stuck on or uses too long
of a path or etc. etc. etc.  Most of the APRS RF bandwidth is consumed
by these types of problems, not IGate operators "set it and forget it"
abilities.  Many IGates are similar to digipeaters: located in places
where "set it and" (more accurately) don't change it is not only
desirable but necessary.

73,

Pete Loveall AE5PL
mailto:pete at ae5pl.net