<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>We still really should consider a new transport such as OpenTrac for data encapsulation. This text stuff is really getting monotonous and extensibility inabilities have continued to plague so many potential applications.</div><div><br></div><div>Gregg Wonderly</div><div>W5GGW<br><br>Sent from my iPhone</div><div><br>On Nov 30, 2012, at 1:00 PM, Jason KG4WSV <<a href="mailto:kg4wsv@gmail.com">kg4wsv@gmail.com</a>> wrote:<br><br></div><blockquote type="cite"><div><br><br><div class="gmail_quote">On Fri, Nov 30, 2012 at 12:54 PM, Andrew P. <span dir="ltr"><<a href="mailto:andrewemt@hotmail.com" target="_blank">andrewemt@hotmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Just as a reminder, these bits are in AX.25 headers.</blockquote></div><br>IMO, it's a mistake to shove layer 3+ data into layer 2 (data link) fields, both for specific reasons like Andrew points out, and just on general principle.<br clear="all">
<div><br></div>-Jason<br>kg4wsv<br>
</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="https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig">https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig</a></span><br></div></blockquote></body></html>