[aprssig] !x!

[Lynn W. Deffenbaugh (Mr)]

The spec page says "*no archive*", so I would think it should be 
transported through the APRS-IS, but not recorded by any APRS 
databases.  Otherwise, it would be a NOGATE or RFONLY if transmitted on 
RF to keep it out of the APRS-IS (IGate responsibility) and just don't 
even inject it into the APRS-IS to start with if you don't want it 
transported (originating client responsibility).

Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32

On 12/30/2011 11:40 AM, la3qma at aprs.la wrote:
> Quoting "Steve Dimse" <steve at dimse.com>:
>
>> A quick check of LB9KE-7 shows aprs.fi ignores it and APRSWorld  
>> respects it (the latter has a posit from Dec 6 that did not include  
>> !x!). That aprs.fi never got called on it shows just how few people  
>> care.
>
> But where should the packet be dropped? By the IGATE and/or by the 
> APRS-IS?
> Because if it's the APRS-IS then APRS.FI is not the "bad guy" here.
>
> Then we have to look on APRX wich is used by the IGATE receiving LB9KE-7
>
>
> Kai Gunter
> LA3QMA
>
> _______________________________________________
> aprssig mailing list
> aprssig at tapr.org
> https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.tapr.org/pipermail/aprssig_lists.tapr.org/attachments/20111230/9e39ce46/attachment.html>