[cssm] Survey - Space Link Extension—Application Program Interface Magenta Books

[Holger Dreihahn]

Dear Erik,
Thanks. That seems in line with many responses. So in the next CSTS WG meeting on 2nd we will discuss and eventually decide to drop these Magenta Books. Please advise if an informal request to you is enough.

Best regards,
Holger

From: "Barkley, Erik J (US 3970)" <erik.j.barkley at jpl.nasa.gov>
Date: Tuesday, 28. February 2023 at 01:58
To: Holger Dreihahn <Holger.Dreihahn at esa.int>, "smwg at mailman.ccsds.org" <smwg at mailman.ccsds.org>, "css-csts at mailman.ccsds.org" <css-csts at mailman.ccsds.org>
Subject: RE: Survey - Space Link Extension—Application Program Interface Magenta Books

Dear Holger,

I have queried the folks at the DSN knowledgeable with regard to the local implementation of SLE, and have a received a short message “Okay to decommission the books”.

Best regards,
-Erik

From: CSS-CSTS <css-csts-bounces at mailman.ccsds.org> On Behalf Of Holger Dreihahn via CSS-CSTS
Sent: Thursday, January 26, 2023 23:42
To: smwg at mailman.ccsds.org; css-csts at mailman.ccsds.org
Subject: [EXTERNAL] [Css-csts] Survey - Space Link Extension—Application Program Interface Magenta Books

Dear CSS Area Colleagues,
As you may remember, the SLE FSP recommendation has been silverized because there was no operational adoption. In that context Erik remarked correctly, that also the corresponding SLE API C++ recommended practice for FSP (aka magenta book) should be retired.

In that context some general considerations about the benefits provided by the SLE API C++ API magenta books vs the maintenance effort came up. It was certainly a valid idea to specify C++ APIs for implementations of the SLE services in magenta books. To my understanding the ultimate goal was to promote the interchangeability of SLE API C++ implementations or even components of it. Technically you can really take an SLE API C++ implementation from one vendor and exchange it easily with one from another vendor. However, practically I am not aware that such an exchange of SLE API implementation ever happened or is of practical relevance for the future.

Now this email is asking for your feedback if today the effort to maintain the SLE API magenta books is matched by the provided benefits. In my mind it would be really an option to retire all SLE API magenta.

Please respond to this email until February 28, stating  your opinion (representing ideally your organizations position), if SLE API magenta books should be retired or not. Clearly these books do not impact interoperability.

Best regards,
Holger




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>).
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).
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.ccsds.org/pipermail/smwg/attachments/20230228/f0cd529a/attachment-0001.htm>