<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><meta name="Generator" content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
        {font-family:"Cambria Math";
        panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
        {font-family:Calibri;
        panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
        {font-family:Georgia;
        panose-1:2 4 5 2 5 4 5 2 3 3;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
        {mso-style-priority:99;
        color:blue;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {mso-style-priority:99;
        color:purple;
        text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
        {mso-style-priority:34;
        margin-top:0in;
        margin-right:0in;
        margin-bottom:0in;
        margin-left:.5in;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:"Times New Roman",serif;}
span.EmailStyle17
        {mso-style-type:personal-reply;
        font-family:"Calibri",sans-serif;
        color:#1F497D;}
.MsoChpDefault
        {mso-style-type:export-only;
        font-family:"Calibri",sans-serif;}
@page WordSection1
        {size:8.5in 11.0in;
        margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
        {page:WordSection1;}
/* List Definitions */
@list l0
        {mso-list-id:608048619;
        mso-list-type:hybrid;
        mso-list-template-ids:1482590532 67698705 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
        {mso-level-text:"%1\)";
        mso-level-tab-stop:none;
        mso-level-number-position:left;
        text-indent:-.25in;}
@list l0:level2
        {mso-level-number-format:alpha-lower;
        mso-level-tab-stop:none;
        mso-level-number-position:left;
        text-indent:-.25in;}
@list l0:level3
        {mso-level-number-format:roman-lower;
        mso-level-tab-stop:none;
        mso-level-number-position:right;
        text-indent:-9.0pt;}
@list l0:level4
        {mso-level-tab-stop:none;
        mso-level-number-position:left;
        text-indent:-.25in;}
@list l0:level5
        {mso-level-number-format:alpha-lower;
        mso-level-tab-stop:none;
        mso-level-number-position:left;
        text-indent:-.25in;}
@list l0:level6
        {mso-level-number-format:roman-lower;
        mso-level-tab-stop:none;
        mso-level-number-position:right;
        text-indent:-9.0pt;}
@list l0:level7
        {mso-level-tab-stop:none;
        mso-level-number-position:left;
        text-indent:-.25in;}
@list l0:level8
        {mso-level-number-format:alpha-lower;
        mso-level-tab-stop:none;
        mso-level-number-position:left;
        text-indent:-.25in;}
@list l0:level9
        {mso-level-number-format:roman-lower;
        mso-level-tab-stop:none;
        mso-level-number-position:right;
        text-indent:-9.0pt;}
ol
        {margin-bottom:0in;}
ul
        {margin-bottom:0in;}
--></style></head><body lang="EN-US" link="blue" vlink="purple"><div class="WordSection1"><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">The only problem I see with the No-Source-Rouiting (NSR) idea is that it requires constant management at every digipeater (node) with lists of allowed calls and routes.  The problem I see here (if I understand it correctly) are:</span></p><p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"><span style="mso-list:Ignore">1)<span style="font:7.0pt "Times New Roman"">      </span></span></span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">Nothing in Ham radio survices that requires this level of daily management  (some digis have not been touched in a decade).</span></p><p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"><span style="mso-list:Ignore">2)<span style="font:7.0pt "Times New Roman"">      </span></span></span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">How do mobiles and portables and special events work.  I guess the answer is that they will always get one hop anywhere anytime.  And then the network has to be adjusted and configured if there is any need beyond that…  (this is workable for big special events… but also is vulnerable to a lot of wpecial work for smaller events? (see #1)</span></p><p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"><span style="mso-list:Ignore">3)<span style="font:7.0pt "Times New Roman"">      </span></span></span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">It makes operations completely vulnerable to potential draconian sysops and fiefdoms…</span></p><p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"><span style="mso-list:Ignore">4)<span style="font:7.0pt "Times New Roman"">      </span></span></span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">It removes the experimention by the end user from amateur radio</span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"> </span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">Just some initial thoughts.  But it will be included in any attempt we make at documenting AX.25-UI</span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"> </span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">Bob, WB4APR</span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"> </span></p><p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> aprssig [mailto:<a href="mailto:aprssig-bounces@tapr.org">aprssig-bounces@tapr.org</a>] <b>On Behalf Of </b>Jim Alles<br><b>Sent:</b> Friday, January 06, 2017 8:23 AM<br><b>To:</b> TAPR APRS Mailing List<br><b>Subject:</b> Re: [aprssig] Documenting the APRS Generic Digipeating spec?</span></p><p class="MsoNormal"> </p><div><div><p class="MsoNormal"><span style="font-family:"Georgia",serif">I found this, It looks like Pete did it!</span></p></div><div><p class="MsoNormal"><span style="font-family:"Georgia",serif"> </span></p></div><div><p class="MsoNormal"><span style="font-family:"Georgia",serif"><a href="https://www.tapr.org/pdf/DCC2005-EliminatingDigipeaters-AE5PL.pdf">PDF attached</a></span></p></div><div><p class="MsoNormal"><span style="font-family:"Georgia",serif"> </span></p></div><div><p class="MsoNormal"><span style="font-family:"Georgia",serif">Regards,</span></p></div><div><p class="MsoNormal"><span style="font-family:"Georgia",serif"> </span></p></div><div><p class="MsoNormal"><span style="font-family:"Georgia",serif">Jim A.</span></p></div></div><div><p class="MsoNormal"> </p><div><p class="MsoNormal">On Thu, Jan 5, 2017 at 3:18 PM, Robert Bruninga <<a href="mailto:bruninga@usna.edu" target="_blank">bruninga@usna.edu</a>> wrote:</p><blockquote style="border:none;border-left:solid #cccccc 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in"><div><div><p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">APRS Authors:</span></p><p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"> </span></p><p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">We all came up with the “Generic-digipeating” concepts for APRS in 1995 or so and is pretty well established in most modern TNC’s </span></p><p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"> </span></p><p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">But its been so long and maybe I am having a senior moment, but I am drawing a blank in trying to think where it is actually documented in AX.25!??  The APRS spec only addresses the data formats (and the use of the AX.25 Destination callsign field in its non-standard way).  The APRS spec (I don’t think) addresses any of the generic digipeating techniques used.</span></p><p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"> </span></p><p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">I think we need to nail this down by spec, since there are some weird implementations that cause confusion.  And if there are new ideas we want to add, then we should have a documented baseline starting point.</span></p><p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"> </span></p><p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">We could call it AX.25-UI for clarification.</span></p><p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span></p><p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">My source for how this all works is my decade old <a href="http://aprs.org/fix14439.html" target="_blank">http://aprs.org/fix14439.html</a> web page.</span></p><p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Is there another better starting point for extracting exactly what UI digipeating is?</span></p><p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span></p><p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Or am I having a senior moment?</span></p><p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span></p><p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Bob, WB4APR</span></p></div></div><p class="MsoNormal" style="margin-bottom:12.0pt"><br>_______________________________________________<br>aprssig mailing list<br><a href="mailto:aprssig@tapr.org">aprssig@tapr.org</a><br><a href="http://www.tapr.org/mailman/listinfo/aprssig" target="_blank">http://www.tapr.org/mailman/listinfo/aprssig</a></p></blockquote></div><p class="MsoNormal"> </p></div></div></body></html>