[aprssig] Ideal Digipeater Behavior

Kenneth Finnegan kennethfinnegan2007 at gmail.com
Thu Aug 25 11:00:27 CDT 2016


 On Thu, Aug 25, 2016 at 5:24 AM, John Langner WB2OSZ <wb2osz at comcast.net>
wrote:

> Duplicate suppression is based on source address, destination address, and
> information field.   In other words, everything other than the via path
> which changes along the way.


Right. You've told me this before -_-
http://www.tapr.org/pipermail/aprssig/2014-May/043364.html

Anyone opposed to me changing the language to:

> No digipeater may transmit the same (source address, destination address,
> information field) twice in any 30 second window. No digipeater may modify
> any contents of any of those fields.


This officially deprecates any routing meaning for the destination SSID,
which is probably ok since no one has mentioned that misfeature in the
original spec for ages.

Can I again express my distaste for mic-e? :-P

--
Kenneth Finnegan
http://blog.thelifeofkenneth.com/

On Thu, Aug 25, 2016 at 5:24 AM, John Langner WB2OSZ <wb2osz at comcast.net>
wrote:

>
> Thanks for trying to clarify this.
>
> Just a couple quick observations.  It will take longer to go through all of
> the examples.
>
>
> > All digipeaters must implement 30 second duplicate suppression. No
> digipeater
> > may transmit the same (source address, information field) twice in any 30
> > second window.
>
> Duplicate suppression is based on source address, destination address, and
> information field.   In other words, everything other than the via path
> which changes along the way.
>
>
> > # The WIDE1-1 alias gets replaced with LOWDIG-1 and is marked as used
> > TRACKR-5>APZTST,WIDE1-1 ->
> >  TRACKR-5>APZTST,LOWDIG-1*
>
> Yes!
> "Replace" when hop count is used up (i.e. -n has been decremented down to
> zero).   "Insert" own call when hops remain.
> Some implementations will both insert their own call and leave the used up
> alias to produce this:
>
> TRACKR-5>APZTST,LOWDIG-1,WIDE1*
>
> This is confusing and ambiguous.  It looks like the packet was digipeated
> twice.  Once by a digipeater that implements tracing (inserting its own
> callsign) and again by another digipeater which did not identify itself.
>
> _______________________________________________
> aprssig mailing list
> aprssig at tapr.org
> http://www.tapr.org/mailman/listinfo/aprssig
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.tapr.org/pipermail/aprssig/attachments/20160825/ee3a2bb9/attachment.html>


More information about the aprssig mailing list