Date: 	02-06-2016 15:55:32
Name: 	Jaroslav Kysela

Message:

Hello,

some SAT>IP clients allow to use RTP/AVP/TCP transport mechanism (embedded RTP through the TCP RTSP connection). Using UDP protocol mean that these packets might be lost on the network (even with good configuration/hardware - it depends on all ethernet network components which forwards the packets).

Please, implement RTP/AVP/TCP transport mechanism (RFC2326 internet standard) to your octopusnet server software.

Jaroslav Kysela

Date: 	14-06-2016 17:21:25
Name: 	Dieter Rimmle

Message:

Hello Mr. Kysela
as Octopus Net is a very low latencey FPGA Solution, there is no possibility to implement TCP.
we do not see any advantage in using TCP as the disturbance of a retransmit has higher impact than packet loss with UDP.
The packet loss in a local network with normal switches could be is neglected.

in addition we support Ethernet QOS
best regards
Dieter Rimmele


Date: 	14-06-2016 20:17:11
Name: 	Jaroslav Kysela

Message:

Hello,

as the main developer of the TVHeadend application (http://tvheadend.org), I don't agree that UDP is sufficient, because it depends on the right packet timing (which you probably manage with your FPGA solution) and on the ethernet components (input and output buffer sizes). Yes, every network can saturate, but we're talking about sporadic packet loss, which the TCP protocol corrects. For example, if my SuperMicro home server is busy with backup (or any other intensive network task), several packets might be dropped in the ethernet card / switch. It's a real use-case. Also, imagine to forward four full DVB-S2 transponders where the bandwidth can be beyond 200Mbit..

I'm also author of the alternate firmware for Inverto IDL400s with the minisatip open source solution and the TCP protocol resolves the problem with the packet lost for most of users.

BTW: I asked all GPL sources for your product Octopus Net on GPL@digitaldevices.de - I own one box. but I have not received the sources nor a reply yet.

Jaroslav Kysela