Years ago I used TCP over 1200bps AX25 connections using UI frames.
It worked quite well as long as you don't expect to much. Receiving an
email (back when emails were just some ascii text) worked fine, but
forget about protocols like HTTP.
The current datalink code in freedv can compress headers (the ethernet
ones) to some degree, especially if you transmit to the broadcast address.
In combination with voice it makes more sense to use protocols with high
data density and relativly low information rates. For example with FPRS
I don't use the extra IP layer and can transmit identification together
with position and altitude in just three frames or 120ms.
On 03/24/2018 09:25 PM, Bruce Perens wrote:
> FreeDV voice packets are around 7 bytes per 40 milliseconds. Even a
> single IPV6 /address /is twice the size, not to mention the rest of
> the header. So, realistic expectations are called for. Header
> compression is helpful. Retransmission of a TCP packet could easily be
> a 1500 or more byte repeat, taking most of a second. The best mix of
> FEC to reduce repeats while minimizing overhead is still open for your
> research.
>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>
>
> _______________________________________________
> Freetel-codec2 mailing list
> Freetel-codec2@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freetel-codec2
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Freetel-codec2 mailing list
Freetel-codec2@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freetel-codec2
