<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
The spec page says "<font color="#000000"><font size="3"><b>no
archive</b></font></font>", 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).<br>
<br>
Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32<br>
<br>
On 12/30/2011 11:40 AM, <a class="moz-txt-link-abbreviated" href="mailto:la3qma@aprs.la">la3qma@aprs.la</a> wrote:
<blockquote cite="mid:20111230174055.5877363owko62x0k@83.143.81.62"
type="cite">Quoting "Steve Dimse" <a class="moz-txt-link-rfc2396E" href="mailto:steve@dimse.com"><steve@dimse.com></a>:
<br>
<br>
<blockquote type="cite">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.
<br>
</blockquote>
<br>
But where should the packet be dropped? By the IGATE and/or by the
APRS-IS?
<br>
Because if it's the APRS-IS then APRS.FI is not the "bad guy"
here.
<br>
<br>
Then we have to look on APRX wich is used by the IGATE receiving
LB9KE-7
<br>
<br>
<br>
Kai Gunter
<br>
LA3QMA
<br>
<br>
_______________________________________________
<br>
aprssig mailing list
<br>
<a class="moz-txt-link-abbreviated" href="mailto:aprssig@tapr.org">aprssig@tapr.org</a>
<br>
<a class="moz-txt-link-freetext" href="https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig">https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig</a>
<br>
<br>
</blockquote>
<br>
</body>
</html>