<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 15 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.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 lang="EN-US" link="#0563C1" vlink="#954F72" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal">Hi Craig,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">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.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Regards,<o:p></o:p></p>
<p class="MsoNormal">Greg <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:12.0pt;color:black">From: </span></b><span style="font-size:12.0pt;color:black">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><br>
<b>Reply-To: </b>"Biggerstaff, Craig (JSC-CD42)[SGT, INC]" <craig.biggerstaff@nasa.gov><br>
<b>Date: </b>Friday, May 28, 2021 at 7:12 AM<br>
<b>To: </b>"sls-sea-dls@mailman.ccsds.org" <sls-sea-dls@mailman.ccsds.org><br>
<b>Subject: </b>[EXTERNAL] [Sls-sea-dls] SDLS EP GB figures 4-1, 4-2<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal">Dear SDLS WG,<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">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.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Thanks and best regards,<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal" style="line-height:105%"><b><span style="font-family:"Arial",sans-serif;color:#545761">Craig Biggerstaff</span></b><o:p></o:p></p>
<p class="MsoNormal" style="line-height:105%"><span style="font-family:"Arial",sans-serif"> </span><o:p></o:p></p>
<p class="MsoNormal" style="line-height:105%"><span style="font-family:"Arial",sans-serif"><img width="86" height="48" style="width:.8958in;height:.5in" id="Picture_x0020_1" src="cid:image001.jpg@01D75492.CC347FB0" alt="KBR - Copy"></span><o:p></o:p></p>
<p class="MsoNormal" style="line-height:105%"><span style="font-size:9.0pt;line-height:105%;font-family:"Arial",sans-serif;color:#545761">KBR | Senior Engineer Specialist, Mission Systems Operations Contract</span><o:p></o:p></p>
<p class="MsoNormal" style="line-height:105%"><span style="font-size:9.0pt;line-height:105%;font-family:"Arial",sans-serif;color:#545761">2101 NASA Parkway, Mail Code CD4 | Houston, Texas 77058 | USA</span><o:p></o:p></p>
<p class="MsoNormal" style="line-height:105%"><span style="font-size:9.0pt;line-height:105%;font-family:"Arial",sans-serif;color:#545761">Office: +1 281.483.2027 |
<a href="mailto:craig.biggerstaff@nasa.gov">craig.biggerstaff@nasa.gov</a></span><o:p></o:p></p>
<p class="MsoNormal" align="center" style="text-align:center;line-height:105%"><span style="font-size:12.0pt;line-height:105%;font-family:"Times New Roman",serif"> </span><o:p></o:p></p>
<div class="MsoNormal" align="center" style="text-align:center;line-height:105%">
<span style="font-size:12.0pt;line-height:105%;font-family:"Times New Roman",serif">
<hr size="0" width="100%" align="center">
</span></div>
<p class="MsoNormal" style="line-height:105%"><span style="font-size:8.0pt;line-height:105%;font-family:"Arial",sans-serif;color:#545761">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><o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
</body>
</html>