<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
span.EmailStyle22
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body bgcolor="white" lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">Coming to the point of the 10% BER I think the main objection that a reader (i.e., a CESG member for the review of the green book) may give is that with 10% BER the probability of losing 100
bytes packet is almost 1. It means that no matter how many times you are going to retransmit the lost packet, it will be never received (or with a very low probability almost 0). Obviously this is from a probabilistic standpoint; if you are lucky enough to
pick the fortunate “realization” then you can make it.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">In the last tests Carlo did (paper at the ASMS 2016 conference), performance were tested with packet error rate up to 30%. In this case instead we have a packet error rate around 99.999…99999%
(and I stop here with the 9 </span><span style="font-size:11.0pt;font-family:Wingdings;color:#1F497D">J</span><span style="font-size:11.0pt;color:#1F497D">). Practically speaking, having in mind the target of CCSDS TM standards it should be very difficult
to have BER=10%, but should be rather below 1e-4.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">Tomaso<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:dimgray">————————————————————————</span><span style="font-family:"Times New Roman","serif";color:#1F497D">
<br>
</span><b><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:dimgray">Deutsches Zentrum für Luft- und Raumfahrt</span></b><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:dimgray"> (DLR)</span><span style="font-family:"Times New Roman","serif";color:#1F497D">
<br>
</span><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:dimgray">German Aerospace Center</span><span style="font-family:"Times New Roman","serif";color:#1F497D">
<br>
</span><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:dimgray">Institute of Communications and Navigation | Satellite Networks | Oberpfaffenhofen | 82234 Wessling | Germany</span><span style="font-family:"Times New Roman","serif";color:#1F497D">
<o:p></o:p></span></p>
<p class="MsoNormal"><b><span lang="IT" style="font-size:10.0pt;font-family:"Arial","sans-serif";color:dimgray">Tomaso de Cola, Ph.D.</span></b><span lang="IT" style="font-size:11.0pt;color:#1F497D">
<br>
</span><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:dimgray">Telefon +49 8153 28-2156 | Telefax +49 8153 28-2844 |</span><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D">
</span><span style="font-size:11.0pt;color:#1F497D"><a href="mailto:tomaso.decola@dlr.de"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:blue">tomaso.decola@dlr.de</span></a>
<br>
</span><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D"><a href="http://www.dlr.de/kn/institut/abteilungen/san"><span style="color:blue">http://www.dlr.de/kn/institut/abteilungen/san</span></a></span><span style="font-size:11.0pt;color:#1F497D">
<o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"><o:p> </o:p></span></p>
<div style="border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt">
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> SIS-MIA [mailto:sis-mia-bounces@mailman.ccsds.org]
<b>On Behalf Of </b>Burleigh, Scott C (312B)<br>
<b>Sent:</b> Tuesday, December 13, 2016 7:06 PM<br>
<b>To:</b> Scott, Keith L.; Grubbs, Rodney P. (MSFC-EO50); Mayer, Jeremy<br>
<b>Cc:</b> sis-mia@mailman.ccsds.org<br>
<b>Subject:</b> Re: [Sis-mia] Questions on Video Streaming Green Book<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">Keith, a couple more thoughts on these questions:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">On 5.4: as you say, we probably don’t want to get into this topic in this Green Book, but I think I would say that simplex links at the layer underlying the convergence layer (like the LTP link
service layer) are probably no problem for the IMC spanning tree, so long as every node is able to both send and receive at the convergence layer somehow or other. They might even be okay at the convergence layer itself, so long as the node can both send
and receive bundles, though I’m less confident there. But I can’t think of any way that a node that is truly simplex can participate in IMC.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">On 6.1: I think Leigh did a lot of stress-testing LTP at 5% BER but I can’t recall whether or not he ever got any results at 10% BER. On paper it ought to work: you lose an awful lot of segments,
but if you set maxber high enough, you keep on retransmitting checkpoints and reports until eventually everything gets through. Carlo Caini did some testing at 40% packet loss rate, which worked, so I think some optimism makes sense. You get a pretty low
throughput rate, though.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">Scott<o:p></o:p></span></p>
<p class="MsoNormal"><a name="_MailEndCompose"><span style="font-size:11.0pt;color:#1F497D"><o:p> </o:p></span></a></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:11.0pt">From:</span></b><span style="font-size:11.0pt"> SIS-MIA [<a href="mailto:sis-mia-bounces@mailman.ccsds.org">mailto:sis-mia-bounces@mailman.ccsds.org</a>]
<b>On Behalf Of </b>Scott, Keith L.<br>
<b>Sent:</b> Monday, December 12, 2016 9:49 AM<br>
<b>To:</b> Grubbs, Rodney P. (MSFC-EO50) <<a href="mailto:rodney.grubbs@nasa.gov">rodney.grubbs@nasa.gov</a>>;
<a href="mailto:Jeremy.Mayer@dlr.de">Jeremy.Mayer@dlr.de</a><br>
<b>Cc:</b> <a href="mailto:sis-mia@mailman.ccsds.org">sis-mia@mailman.ccsds.org</a><br>
<b>Subject:</b> [Sis-mia] Questions on Video Streaming Green Book<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Hey,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Attached are some light edits and some questions about the Bundle Streaming Requirements Green Book (the comments in the markup). Since CESG review is the only thing the Green Book goes through, can I get
your feedback on the commented items before I submit to CESG?<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Summary of questions:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">5.2: The DLR transparent gateway – encapsulates UDP datagrams and is otherwise agnostic to the video protocol running over UDP, yes?<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">5.2.1: the comment in the second paragraph – is the addition correct or is it the gateway timestamp that’s being used (or something else)?<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">5.2.2: where you say that MPEG-TS and BP are doing some of the same things (robustness for error-recovery and interleaving) – can you say a bit more on the implications of that?<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">5.2.2: BP does interleaving? I’m thinking ‘traditional’ interleaving where data items are assigned to a matrix row-by-row and read out column-by-column once the matrix is full. I think you’re thinking of
something else – can you tell me what it is you mean?<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">5.4: probably a question for later.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">6.1: 10% BER w/ what I assume is LTP red – how does that EVER succeed? Chances of getting 100 Bytes through correctly at 10% BER are really low.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> --keith<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
</div>
</div>
</body>
</html>