<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>I am using T&. Packets from -IS go out with WIDE2-1 because I have a wide footprint.</div><div id="AppleMailSignature"><br></div><div id="AppleMailSignature">What's the verdict on 2& and 3&?<br><br><div><div><br></div></div><div><span style="background-color: rgba(255, 255, 255, 0);">-- <br><br>David Andrzejewski<br>E-mail/iMessage/Jabber: <a dir="ltr" href="mailto:david@davidandrzejewski.com" x-apple-data-detectors="true" x-apple-data-detectors-type="link" x-apple-data-detectors-result="1">david@davidandrzejewski.com</a><br>PGP Key ID: 5EBA8A72<br></span><span style="font-family: UICTFontTextStyleBody; font-size: 14px; -webkit-text-size-adjust: auto;"></span><br style="font-family: UICTFontTextStyleBody; font-size: 14px; -webkit-text-size-adjust: auto;"></div></div><div><br>On Jun 29, 2016, at 21:07, Lee Bengston via aprssig <<a href="mailto:aprssig@tapr.org">aprssig@tapr.org</a>> wrote:<br><br></div><blockquote type="cite"><div><div dir="ltr"><div class="gmail_default" style="font-family:verdana,sans-serif;font-size:small">Hi all,<br><br></div><div class="gmail_default" style="font-family:verdana,sans-serif;font-size:small">Remember this thread?<br></div><div class="gmail_default" style="font-family:verdana,sans-serif;font-size:small"><br></div><div class="gmail_extra"><div class="gmail_quote">On Mon, Sep 19, 2011 at 11:39 AM, Bob Bruninga <span dir="ltr"><<a href="mailto:bruninga@usna.edu" target="_blank">bruninga@usna.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">All IGate operators please read and consider action on this proposal.<br>
<br>
RX-only IGates kill the functionality of the APRS-IS as a universal system!<br>
And they give casual observers the impression that APRS has global<br>
connectivity, when in fact, that view has lots of invisible holes because of<br>
RX-only IGates.<br>
<br></blockquote><div><div class="gmail_default" style="font-family:verdana,sans-serif;font-size:small;display:inline">I'm noticing a few relatively new Rx-only IGates on the air using Raspberry Pi's. My guess is they are using sound card software instead of a hardware TNC and not implementing anything for PTT.<br></div></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
Compounding this problem is that we have no way of knowing if people are<br>
using the right symbol for their IGate. Are they using "I" because it is<br>
really a TX Igate, or just because it seems logical?<br>
<br>
Using <a href="http://www.findu.com/cgi-bin/symbol.cgi?icon=Iamp&limit=2000" rel="noreferrer" target="_blank">http://www.findu.com/cgi-bin/symbol.cgi?icon=Iamp&limit=2000</a> I see 960<br>
"I&" Igates<br>
Using <a href="http://www.findu.com/cgi-bin/symbol.cgi?icon=Ramp&limit=2000" rel="noreferrer" target="_blank">http://www.findu.com/cgi-bin/symbol.cgi?icon=Ramp&limit=2000</a> I see 130<br>
"R&" Igates<br>
<br>
Maybe we need to have a 3rd symbol, a "T" Overlay so that operators of<br>
serious two-way IGates and indicate their dedicated intent to provide good<br>
APRS-IS local service. These guys will take the trouble to indicate a TX<br>
Igate. When we see one of those, we have proof-positive that the IGate<br>
includes a two-way TX capability.<br></blockquote><div><br><div class="gmail_default" style="font-family:verdana,sans-serif;font-size:small;display:inline">The new Rx IGates I've noticed are using the R& symbol, so at least they're indicating what they are.<br><br></div></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
We could even go one step farther. We could indicate the NUMBER OF HOPS<br>
that the IGate uses by default for IS-to-RF packets. This could help us<br>
better manage overlapping IGate coverage... So how about this plan:<br>
<br>
I& - is an IGate, but is ambiguous with respect to transmitting<br>
R& - means it is definitely an RX only IGate<br>
T& - Means it is definitely a TX IGate with one hop path only<br>
2& - means it is a TX igate clobbering two hops in all directions<br>
3& - means it is a TX SPAM GENERATOR , (or a legitimate special case)<br>
Etc..<br>
<br>
Should we do this???<br></blockquote><div><br><div class="gmail_default" style="font-family:verdana,sans-serif;font-size:small">I haven't seen anyone using 2& or 3&, but I've seen a few that are using T&.</div><div class="gmail_default" style="font-family:verdana,sans-serif;font-size:small"></div></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
Bob, WB4APR<br>
<br></blockquote><div><div class="gmail_default" style="font-family:verdana,sans-serif;font-size:small;display:inline">In hindsight it appears this message and the subsequent discussion did some good.
I'm bringing it up now because it was almost 5 years ago, and perhaps
there are several list members out there that were not on the list when
this was discussed previously - some of which could be new IGate operators.<br><br></div><div class="gmail_default" style="font-family:verdana,sans-serif;font-size:small;display:inline">Lee - K5DAT<br><br></div></div></div></div></div>
</div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>aprssig mailing list</span><br><span><a href="mailto:aprssig@tapr.org">aprssig@tapr.org</a></span><br><span><a href="http://www.tapr.org/mailman/listinfo/aprssig">http://www.tapr.org/mailman/listinfo/aprssig</a></span><br></div></blockquote></body></html>