<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style>
</head>
<body dir="ltr">
<div style="font-family: EmojiFont, "Franklin Gothic Demi", "Avenir Next Condensed Demi Bold", sans-serif, "Apple Color Emoji", "Segoe UI Emoji", NotoColorEmoji, "Segoe UI Symbol", "Android Emoji", EmojiSymbols; font-size: 12pt; color: rgb(0, 0, 0);">
Yes. You terminate the TCP connection locally into a proxy server that "spoofs" the connection into thinking the packet has been accepted and it should send the next one. In reality the proxy has coordinated with the distant end and is transferring the data
using a more delay tolerant protocol. If the PEP function is not included in the modem or you're trying to use modems that don't implement PEP the same way, you can do it in external hardware or create the PEP in software on the communicating devices. The
first time I ran into this many years ago I had a 45 Mbps satellite link but could not get the FTP session to move any faster than 120 Kbps. I've learned a little about how all this network stuff works since then
<span id="🙂" title=":slight_smile:">🙂</span></div>
<div style="font-family: EmojiFont, "Franklin Gothic Demi", "Avenir Next Condensed Demi Bold", sans-serif, "Apple Color Emoji", "Segoe UI Emoji", NotoColorEmoji, "Segoe UI Symbol", "Android Emoji", EmojiSymbols; font-size: 12pt; color: rgb(0, 0, 0);">
<span title=":slight_smile:"><br>
</span></div>
<div style="font-family: EmojiFont, "Franklin Gothic Demi", "Avenir Next Condensed Demi Bold", sans-serif, "Apple Color Emoji", "Segoe UI Emoji", NotoColorEmoji, "Segoe UI Symbol", "Android Emoji", EmojiSymbols; font-size: 12pt; color: rgb(0, 0, 0);">
<span title=":slight_smile:">Howie AB2S</span></div>
<div id="appendonsend"></div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>From:</b> Michelle Thompson <mountain.michelle@gmail.com><br>
<b>Sent:</b> Tuesday, February 26, 2019 1:50 PM<br>
<b>To:</b> Howie DeFelice<br>
<b>Cc:</b> Phil Karn; Michelle Thompson via Ground-Station<br>
<b>Subject:</b> Re: [Ground-station] MPTCP, network coding, ICN, and satellites!</font>
<div> </div>
</div>
<div>
<div dir="ltr">This is the PEPs, right? They get a lot of attention in this book. <br>
<br clear="all">
<div>
<div dir="ltr" class="x_gmail_signature">
<div dir="ltr">
<div>
<div dir="ltr">
<div>
<div dir="ltr">
<div dir="ltr">-Michelle W5NYV<br>
<br>
<div dir="ltr"><br>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<br>
</div>
<br>
<div class="x_gmail_quote">
<div dir="ltr" class="x_gmail_attr">On Tue, Feb 26, 2019 at 10:25 AM Howie DeFelice <<a href="mailto:howied231@hotmail.com">howied231@hotmail.com</a>> wrote:<br>
</div>
<blockquote class="x_gmail_quote" style="margin:0px 0px 0px 0.8ex; border-left:1px solid rgb(204,204,204); padding-left:1ex">
<div dir="ltr">
<div style="font-family:"Franklin Gothic Demi","Avenir Next Condensed Demi Bold",sans-serif; font-size:12pt; color:rgb(0,0,0)">
HTS satellites, at least the ones operated by Intelsat, are not any different than wide beam satellites in terms of TCP performance due to delay. Most all modern satellite modems use an Ethernet interface and have some form of TCP acceleration integrated into
the modem to mitigate the TCP window issue due to transit delay. As Phil stated, BER performance has a significant effect on throughput performance. The higher performance of the smaller spot beams on HTS satellites coupled with improved FEC makes obtaining
good BER much easier than it was even just 10 years ago.</div>
<div style="font-family:"Franklin Gothic Demi","Avenir Next Condensed Demi Bold",sans-serif; font-size:12pt; color:rgb(0,0,0)">
<br>
</div>
<div style="font-family:"Franklin Gothic Demi","Avenir Next Condensed Demi Bold",sans-serif; font-size:12pt; color:rgb(0,0,0)">
Howie AB2S</div>
<div id="x_gmail-m_-8186993015571262810appendonsend"></div>
<hr style="display:inline-block; width:98%">
<div id="x_gmail-m_-8186993015571262810divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" color="#000000" style="font-size:11pt"><b>From:</b> Ground-Station <ground-station-bounces@lists.openresearch.institute> on behalf of Michelle Thompson via Ground-Station
<ground-station@lists.openresearch.institute><br>
<b>Sent:</b> Tuesday, February 26, 2019 8:01 AM<br>
<b>To:</b> Phil Karn<br>
<b>Cc:</b> Michelle Thompson via Ground-Station<br>
<b>Subject:</b> Re: [Ground-station] MPTCP, network coding, ICN, and satellites!</font>
<div> </div>
</div>
<div>
<div dir="auto">
<div>Late 2018. </div>
<div dir="auto"><br>
</div>
<div dir="auto">HTS people seem to have different results, experiences, and opinions with traditional TCP working on their links. </div>
<div dir="auto"><br>
</div>
<div dir="auto">-mdt</div>
<div dir="auto"><br>
<div class="x_gmail-m_-8186993015571262810x_gmail_quote" dir="auto">
<div dir="ltr" class="x_gmail-m_-8186993015571262810x_gmail_attr">On Tue, Feb 26, 2019, 01:43 Phil Karn via Ground-Station <ground-station@lists.openresearch.institute> wrote:<br>
</div>
<blockquote class="x_gmail-m_-8186993015571262810x_gmail_quote" style="margin:0px 0px 0px 0.8ex; border-left:1px solid rgb(204,204,204); padding-left:1ex">
On 2/25/19 09:11, Michelle Thompson via Ground-Station wrote:<br>
> One of the books I picked up at Information Theory and Applications<br>
> Conference was Network and Protocol Architectures for Future Satellite<br>
> Systems. <br>
<br>
When did it come out?<br>
<br>
> The first problem you run into is that TCP views long latency links as<br>
> congestion and does what it's good at and slows things down. <br>
<br>
This problem was addressed 20+ years ago with TCP header timestamps and<br>
window scaling, both of which have been universally deployed for some<br>
time now.<br>
<br>
Header timestamps solves the problem I addressed my round trip timing<br>
algorithm in the late 1980s. I chose to do it without changing TCP, but<br>
given that the protocol could be changed, timestamps was a much better<br>
solution.<br>
<br>
Window scaling got around TCP's original 64KB window limit, meaning that<br>
it couldn't send more than 64 kilobytes per round trip time. This<br>
rapidly became a problem on terrestrial fiber, not just geostationary<br>
satellites. The SYN (synchronize, or connection setup) packets convey a<br>
"scale" parameter that is the base-2 log of the value to be multiplied<br>
by all subsequent window advertisements in the session. E.g., if the<br>
window scale parameter is 5, then all window announcements should be<br>
left-shifted by 5 bits.<br>
<br>
This completely solves the problem for bulk transfers over long delay<br>
channels **provided** that the packet loss rate is kept small. TCP still<br>
has problems when packets are lost more often than roughly once per<br>
round trip time. There are additional enhancements (selective ACKs) to<br>
handle this problem, but it is still best to design the subnet for a<br>
much lower packet loss rate. How you do this is left up to the subnet<br>
designer. See RFC 3819, Advice for Internet Subnetwork Designers.<br>
<br>
Phil<br>
<br>
<br>
_______________________________________________<br>
Ground-Station mailing list<br>
Ground-Station@lists.openresearch.institute<br>
<a href="https://nam02.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists.openresearch.institute%2Fmailman%2Flistinfo%2Fground-station&data=02%7C01%7C%7C9ef0f3e40de549e98a5408d69c1b6c4b%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636868038919582030&sdata=jetjFSMuPUe%2Fr6%2B%2Bb88vFclYNy9CYUXOgbftTxW8Qlk%3D&reserved=0" originalsrc="http://lists.openresearch.institute/mailman/listinfo/ground-station" shash="d3b2GdbP8eHANF+bEolB+a/zx8ldJ0cgxqSNh1R2dry4JCJomfUM/Ef1pIGrlHvNeGCDtq0jBM381ioUP6kRvh99Vlg38M0SOE+0opzG/mWzNfwAFotMXFWdPwt1bp0y0oLzssXTT5u1WE3qOottVtXAPyVYWb5OSA2JmtTlS74=" rel="noreferrer noreferrer" target="_blank">http://lists.openresearch.institute/mailman/listinfo/ground-station</a><br>
</blockquote>
</div>
</div>
</div>
</div>
</div>
</blockquote>
</div>
</div>
</body>
</html>