[aprssig] APRS CSMA Settings

[Robert Bruninga]

Sorry, my bad.
Bob, Wb4APR

-----Original Message-----
From: aprssig-bounces at tapr.org [mailto:aprssig-bounces at tapr.org] On Behalf
Of Lynn W. Deffenbaugh (Mr)
Sent: Tuesday, May 20, 2014 5:26 PM
To: TAPR APRS Mailing List
Subject: Re: [aprssig] APRS CSMA Settings

I beg to differ on that one.  APRS messages ARE retried on an increasing
interval until it gives up or an ack is received via a separate APRS
message.  This isn't connected packet, it's APRS messaging.  But it's
retries at the application level, not within the lower protocol stacks.

Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32

On 5/20/2014 4:05 PM, Robert Bruninga wrote:
> Not at all.  That is connected packet.  The whole reason for APRS was
> to get away from that very inefficient way of using packet...
>
> Bob
>
> -----Original Message-----
> From: aprssig-bounces at tapr.org [mailto:aprssig-bounces at tapr.org] On
> Behalf Of Bob Poortinga
> Sent: Tuesday, May 20, 2014 1:15 PM
> To: TAPR APRS Mailing List
> Subject: Re: [aprssig] APRS CSMA Settings
>
> WB4APR writes:
>
>> This does not apply to APRS at all.  APRS never retries (other than
>> simply waiting for the next beacon repeat... 10 minutes for local
>> direct packets, and 30 minutes for 2 hop fixed beacons).
> I thought that the sending station of an APRS messages retries until
> it gets an acknowledgment using an exponential back-off algorithm.
>
> --
> Bob Poortinga NG9M
> _______________________________________________
> aprssig mailing list
> 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
>

_______________________________________________
aprssig mailing list
aprssig at tapr.org
http://www.tapr.org/mailman/listinfo/aprssig