<span style=" font-size:10pt;font-family:sans-serif">Greg, Craig,</span>
<br><span style=" font-size:10pt;font-family:sans-serif">
my questionis that your diagrams seems to implicitly
state that</span>
<br><span style=" font-size:10pt;font-family:sans-serif">1) Packets go
to the Onboard Computer A</span>
<br><span style=" font-size:10pt;font-family:sans-serif">2) VC.MAP frames
do not go to the onboard computer</span>
<br><span style=" font-size:10pt;font-family:sans-serif"><b>
Is this your intention?</b></span>
<br><span style=" font-size:10pt;font-family:sans-serif">If yes, I am not
sure this architectural detail is always true.</span>
<br><span style=" font-size:10pt;font-family:sans-serif">I guess Ignacio
and Marco Rovatti (cc'ed here) can better comment on this from the ESA
point of view.</span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">Given the two
remarks above, is it relevant to show Onboard Computer B?</span>
<br><span style=" font-size:10pt;font-family:sans-serif">Does the side
B have duplicated features for forward/return link?</span>
<br><span style=" font-size:10pt;font-family:sans-serif">The 3 boxes just
mentioned are never touched by the lines for your data paths. The could
be there but they could also not be there in case your Security Function
B is only a different security funcrion within a single spacecraft (e.g.
there could be a payload using Security A and another payload using Security
B.</span>
<br><span style=" font-size:10pt;font-family:sans-serif">Removing non touched
boxes could make the diagram simpler just adding a remark about what Security
Function B could be in various architectures.</span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">I hope I am not
missing something..</span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">Regards</span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">Gian Paolo</span>
<br>
<br>
<br>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">From:
</span><span style=" font-size:9pt;font-family:sans-serif">"Kazz,
Greg J\(US 312B\) via SLS-SEA-DLS" <sls-sea-dls@mailman.ccsds.org></span>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">To:
</span><span style=" font-size:9pt;font-family:sans-serif">"Biggerstaff,
Craig (JSC-CD42)[SGT, INC]" <craig.biggerstaff@nasa.gov>, "sls-sea-dls@mailman.ccsds.org"
<sls-sea-dls@mailman.ccsds.org></span>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">Date:
</span><span style=" font-size:9pt;font-family:sans-serif">29-05-21
22:59</span>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">Subject:
</span><span style=" font-size:9pt;font-family:sans-serif">Re:
[Sls-sea-dls] [EXTERNAL] SDLS EP GB figures 4-1, 4-2</span>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">Sent
by: </span><span style=" font-size:9pt;font-family:sans-serif">"SLS-SEA-DLS"
<sls-sea-dls-bounces@mailman.ccsds.org></span>
<br>
<hr noshade>
<br>
<br>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri">Hi
Craig,</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri">My
only comment is by including “Physical Elements” such as the “Onboard
Computer X, Command and Data Handling ” as well as busses, the diagrams
to me come across very implementation like, i.e., like a C&DH <i>unit</i>.
The other elements in the diagram are functional except for the generic
buses. I suspect some implementation could do this all in a Software reprogrammable
radio instead of having a C&DH. It clearly implies a certain architecture.
Maybe there is no way to avoid this. Not sure.</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri">Regards,</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri">Greg
</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;font-family:Calibri"><b>From:
</b>SLS-SEA-DLS <sls-sea-dls-bounces@mailman.ccsds.org> on behalf
of "Biggerstaff, Craig (JSC-CD42)[SGT, INC] via SLS-SEA-DLS"
<sls-sea-dls@mailman.ccsds.org><b><br>
Reply-To: </b>"Biggerstaff, Craig (JSC-CD42)[SGT, INC]" <craig.biggerstaff@nasa.gov><b><br>
Date: </b>Friday, May 28, 2021 at 7:12 AM<b><br>
To: </b>"sls-sea-dls@mailman.ccsds.org" <sls-sea-dls@mailman.ccsds.org><b><br>
Subject: </b>[EXTERNAL] [Sls-sea-dls] SDLS EP GB figures 4-1, 4-2</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri">Dear
SDLS WG,</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri">Attached
are proposed updates to Figures 4-1 and 4-2, modified to illustrate more
clearly the data paths and the differences between using MAP/VC versus
e.g. APID to address separate security units. Please provide any
suggested improvements.</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri">Thanks
and best regards,</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#5f5f5f;font-family:Arial"><b>Craig
Biggerstaff</b></span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Arial"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><img src=cid:_2_09AC3E240D625D5C00538135C12586EA width=86 height=48 alt="KBR - Copy" style="border:0px solid;"></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:9pt;color:#5f5f5f;font-family:Arial">KBR
| Senior Engineer Specialist, Mission Systems Operations Contract</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:9pt;color:#5f5f5f;font-family:Arial">2101
NASA Parkway, Mail Code CD4 | Houston, Texas 77058 |
USA</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:9pt;color:#5f5f5f;font-family:Arial">Office:
+1 281.483.2027 | </span><a href=mailto:craig.biggerstaff@nasa.gov><span style=" font-size:9pt;color:#0082bf;font-family:Arial"><u>craig.biggerstaff@nasa.gov</u></span></a></p>
<div align=center><span style=" font-size:12pt;font-family:Times New Roman"> </span>
<br>
<hr></div>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:8pt;color:#5f5f5f;font-family:Arial">This
e-mail, including any attached files, may contain confidential and privileged
information for the sole use of the intended recipient. Any review,
use, distribution, or disclosure by others is strictly prohibited. If
you are not the intended recipient (or authorized to receive information
for the intended recipient), please contact the sender by reply e-mail
and delete all copies of this message.</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"> </span><tt><span style=" font-size:10pt">_______________________________________________<br>
SLS-SEA-DLS mailing list<br>
SLS-SEA-DLS@mailman.ccsds.org<br>
</span></tt><a href="https://mailman.ccsds.org/cgi-bin/mailman/listinfo/sls-sea-dls"><tt><span style=" font-size:10pt">https://mailman.ccsds.org/cgi-bin/mailman/listinfo/sls-sea-dls</span></tt></a><tt><span style=" font-size:10pt"><br>
</span></tt></p>
<p style="margin-top:0px;margin-Bottom:0px"></p>
<p style="margin-top:0px;margin-Bottom:0px"></p>
<PRE>This message is intended only for the recipient(s) named above. It may contain proprietary information and/or
protected content. Any unauthorised disclosure, use, retention or dissemination is prohibited. If you have received
this e-mail in error, please notify the sender immediately. ESA applies appropriate organisational measures to protect
personal data, in case of data privacy queries, please contact the ESA Data Protection Officer (dpo@esa.int).
</PRE>