[aprssig] Documenting the APRS Generic Digipeating spec?

Robert Bruninga bruninga at usna.edu
Fri Jan 6 13:08:05 EST 2017

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:

1)      Nothing in Ham radio survices that requires this level of daily
management  (some digis have not been touched in a decade).

2)      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)

3)      It makes operations completely vulnerable to potential draconian
sysops and fiefdoms…

4)      It removes the experimention by the end user from amateur radio

Just some initial thoughts.  But it will be included in any attempt we make
at documenting AX.25-UI


*From:* aprssig [mailto:aprssig-bounces at tapr.org] *On Behalf Of *Jim Alles
*Sent:* Friday, January 06, 2017 8:23 AM
*To:* TAPR APRS Mailing List
*Subject:* Re: [aprssig] Documenting the APRS Generic Digipeating spec?

I found this, It looks like Pete did it!

PDF attached


Jim A.

On Thu, Jan 5, 2017 at 3:18 PM, Robert Bruninga <bruninga at usna.edu> wrote:

APRS Authors:

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

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.

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.

We could call it AX.25-UI for clarification.

My source for how this all works is my decade old
http://aprs.org/fix14439.html web page.

Is there another better starting point for extracting exactly what UI
digipeating is?

Or am I having a senior moment?


aprssig mailing list
aprssig at tapr.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.tapr.org/pipermail/aprssig_lists.tapr.org/attachments/20170106/42140480/attachment.html>

More information about the aprssig mailing list