[Sls-sea-dls] [EXTERNAL] SDLS EP GB figures 4-1, 4-2

Fri Jun 4 16:03:05 UTC 2021

The two diagrams were intended to show contrasting scenarios:

*        4-2 shows packets routed to the onboard computer, and from there to the destination security unit.  In this scenario the onboard computer must be available and functioning correctly.

*        4-1 shows data link frame data routed to an onboard destination security unit, independently of the onboard computer.  The details of this are necessarily fuzzy, and I did not want to stipulate any more than the conceptual use of data link capabilities (implemented in a baseband processor, SDR, or whatever) to reach (and potentially to recover) an onboard security unit when the communications processing components nominally used to reach it are unavailable or malfunctioning.

I don't want to stipulate any particular physical implementation, and welcome everyone's help in pointing out where one could be assumed from the diagrams.

Best regards,

Craig

From: Gian.Paolo.Calzolari at esa.int <Gian.Paolo.Calzolari at esa.int>
Sent: Friday, June 4, 2021 10:12 AM
To: Kazz, Greg J (JPL-312B)[JPL Employee] <greg.j.kazz at jpl.nasa.gov>
Cc: Biggerstaff, Craig (JSC-CD42)[SGT, INC] <craig.biggerstaff at nasa.gov>; sls-sea-dls at mailman.ccsds.org; Marco.Rovatti at esa.int
Subject: Re: [Sls-sea-dls] [EXTERNAL] SDLS EP GB figures 4-1, 4-2

Greg, Craig,
        my questionis that your diagrams seems to implicitly state that
1) Packets go to the Onboard Computer A
2) VC.MAP frames do not go to the onboard computer
        Is this your intention?
If yes, I am not sure this architectural detail is always true.
I guess Ignacio and Marco Rovatti (cc'ed here) can better comment on this from the ESA point of view.

Given the two remarks above, is it relevant to show Onboard Computer B?
Does the side B have duplicated features for forward/return link?
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.
Removing non touched boxes could make the diagram simpler just adding a remark about what Security Function B could be in various architectures.

I hope I am not missing something..

Regards

Gian Paolo

From:        "Kazz, Greg J\(US 312B\) via SLS-SEA-DLS" <sls-sea-dls at mailman.ccsds.org<mailto:sls-sea-dls at mailman.ccsds.org>>
To:        "Biggerstaff, Craig (JSC-CD42)[SGT, INC]" <craig.biggerstaff at nasa.gov<mailto:craig.biggerstaff at nasa.gov>>, "sls-sea-dls at mailman.ccsds.org<mailto:sls-sea-dls at mailman.ccsds.org>" <sls-sea-dls at mailman.ccsds.org<mailto:sls-sea-dls at mailman.ccsds.org>>
Date:        29-05-21 22:59
Subject:        Re: [Sls-sea-dls] [EXTERNAL]  SDLS EP GB figures 4-1, 4-2
Sent by:        "SLS-SEA-DLS" <sls-sea-dls-bounces at mailman.ccsds.org<mailto:sls-sea-dls-bounces at mailman.ccsds.org>>
________________________________

Hi Craig,

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 unit. 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.

Regards,

Greg

From: SLS-SEA-DLS <sls-sea-dls-bounces at mailman.ccsds.org<mailto:sls-sea-dls-bounces at mailman.ccsds.org>> on behalf of "Biggerstaff, Craig (JSC-CD42)[SGT, INC] via SLS-SEA-DLS" <sls-sea-dls at mailman.ccsds.org<mailto:sls-sea-dls at mailman.ccsds.org>>
Reply-To: "Biggerstaff, Craig (JSC-CD42)[SGT, INC]" <craig.biggerstaff at nasa.gov<mailto:craig.biggerstaff at nasa.gov>>
Date: Friday, May 28, 2021 at 7:12 AM
To: "sls-sea-dls at mailman.ccsds.org<mailto:sls-sea-dls at mailman.ccsds.org>" <sls-sea-dls at mailman.ccsds.org<mailto:sls-sea-dls at mailman.ccsds.org>>
Subject: [EXTERNAL] [Sls-sea-dls] SDLS EP GB figures 4-1, 4-2

Dear SDLS WG,

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.

Thanks and best regards,

Craig Biggerstaff

[KBR - Copy]

KBR  |  Senior Engineer Specialist, Mission Systems Operations Contract

2101 NASA Parkway, Mail Code CD4  |  Houston, Texas 77058  |  USA

Office: +1 281.483.2027  |  craig.biggerstaff at nasa.gov<mailto:craig.biggerstaff at nasa.gov>

________________________________

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.

 _______________________________________________
SLS-SEA-DLS mailing list
SLS-SEA-DLS at mailman.ccsds.org<mailto:SLS-SEA-DLS at mailman.ccsds.org>
https://mailman.ccsds.org/cgi-bin/mailman/listinfo/sls-sea-dls<https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmailman.ccsds.org%2Fcgi-bin%2Fmailman%2Flistinfo%2Fsls-sea-dls&data=04%7C01%7Ccraig.biggerstaff%40nasa.gov%7C398e00ec9bfb41aabed808d9276b2442%7C7005d45845be48ae8140d43da96dd17b%7C0%7C0%7C637584163399021109%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=gJblEp0V2xwwaEPHsUubTLvfbtcJmghRbaxMU9A%2BHmA%3D&reserved=0>

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 at esa.int<mailto:dpo at esa.int>).
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.ccsds.org/pipermail/sls-sea-dls/attachments/20210604/f0460c41/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.jpg
Type: image/jpeg
Size: 2487 bytes
Desc: image002.jpg
URL: <http://mailman.ccsds.org/pipermail/sls-sea-dls/attachments/20210604/f0460c41/attachment-0001.jpg>