[aprssig] Paths - Solution proposal

Mark Cheavens mcheavens at usa.net
Fri Jul 18 20:16:17 CDT 2014


Bob,
What I have suggested would not eliminate 
"source" routing, but only be a better/smarter 
system based solution for "generic" paths.
- A specific source routed packet could be given 
HIGHER priority based upon that alone.
- Think if you were in DC, but needed to "flood" 
or try to flood packets a few 100 miles away.
         - You could "source route" to that area 
(with the highest priority) and then "flood" from that point around.

I like the idea.

Mark Cheavens
KC5EVE

At 09:29 AM 7/18/2014, Robert Bruninga wrote:
>I use source routing frequently. Â Rather than 
>shotgunning my APRS packets in all directions, 
>If I am doing something special (quite often 
>actually) I will chose specific digipeaters by 
>callsign to get my packte going in the right 
>direction and then let it go out from there.
>
>Or the opposite, do a generic 1 or 21 hops to 
>cover the area where I am operating but then 
>letting it go one more hop to a known intended area.
>
>This is common when one is in the highest 
>density of APRS traffic in the country, and it 
>makes no sense to flood the greater mid-atlantic 
>when a smart selection of an entry in the DIGI 
>field can tailor the path to only the area of interest.
>
>Some people can just plug-n-play, but some 
>others like to understand the network and hone 
>their skills to use it effectively.. Â - by choosing where their packets go --
>
>Bob, WB4APR
>Bob, Wb4APR
>
>
>On Fri, Jul 18, 2014 at 4:45 AM, Jason KG4WSV 
><<mailto:kg4wsv at gmail.com>kg4wsv at gmail.com> wrote:
>
> > On Jul 18, 2014, at 1:58 AM, Robert Bruninga 
> <<mailto:bruninga at usna.edu>bruninga at usna.edu> wrote:
> >
> > WHen was the last time you dialed 911?
> > I assume zero. Â Therefore we dont need it right?
>
>You are equating source routing with 911 service?
>
>I assume this response is to avoid admitting you 
>have never used it, never needed it, and you are 
>holding back the entire APRS network 
>infrastructure to preserve a feature you think you might need one day.
>
>-j
>
>
>_______________________________________________
>aprssig mailing list
><mailto:aprssig at tapr.org>aprssig at tapr.org
>http://www.tapr.org/mailman/listinfo/aprssig
>
>
>_______________________________________________
>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/20140718/b5349263/attachment.html>


More information about the aprssig mailing list