AB
On Friday, December 27, 2013, wrote:
On Friday, December 27, 2013, wrote:
AB
The Moon is arguably a satellite of Earth, but the distances are different from LEO and GEO. That affects TCP performance.
TCP was designed with geostationary satellite hops in mind - see eg RFC829. I use TCP across geostationary satellites daily.
I back up my statements with experience and references. What do you back yours with? Why is UDP inefficient?
Lloyd Wood
http://about.me/lloydwood
________________________________________
From: Abdussalam Baryun [abdussalambaryun@xxxxxxxxx]
Sent: 27 December 2013 06:01
To: Wood L Dr (Electronic Eng)
Cc: mcr+ietf@xxxxxxxxxxxx; ietf@xxxxxxxx
Subject: Re: Chang'E 3
So if TCP has problems then MPTCP has problems then they may not be preferred for that satellite networking. For LEO SATNETs also there are problems for using TCP. The UDP is a good solution in general but not efficient, but always I think the SATNETs may need some special internet transport protocols because they are having more dynamics in the net's lower layers.
AB
AFAIK vanilla ftp/TCP has (only?) been used on CHIPsat from LEO, but that did not have much data to transfer.
We designed http://saratoga.sf.net with the idea of a continuous UDP stream of data from Pluto in mind...
Lloyd Wood
http://sat-net.com/L.Wood/
________________________________________
From: ietf [ietf-bounces@xxxxxxxx<_javascript_:;>] On Behalf Of Abdussalam Baryun [abdussalambaryun@xxxxxxxxx<_javascript_:;>]
Sent: 26 December 2013 16:40
To: Michael Richardson
Cc: ietf@xxxxxxxx<_javascript_:;>
Subject: Chang'E 3
Transport protocol for satellites depend on the applications, the network dynamics, links and transmission channels. IMO the use of MPTCP for Back2Earth may not be the best option making the communication complex, not sure why did you hope to use it with this project.
AB