<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)">
<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;}
@font-face
{font-family:Georgia;
panose-1:2 4 5 2 5 4 5 2 3 3;}
/* 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.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Georgia",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"><span style="font-family:"Georgia",serif">Dear Holger,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia",serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia",serif">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”. <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia",serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia",serif">Best regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia",serif">-Erik<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia",serif"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> CSS-CSTS <css-csts-bounces@mailman.ccsds.org> <b>
On Behalf Of </b>Holger Dreihahn via CSS-CSTS<br>
<b>Sent:</b> Thursday, January 26, 2023 23:42<br>
<b>To:</b> smwg@mailman.ccsds.org; css-csts@mailman.ccsds.org<br>
<b>Subject:</b> [EXTERNAL] [Css-csts] Survey - Space Link Extension—Application Program Interface Magenta Books<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Dear CSS Area Colleagues,<o:p></o:p></p>
<p class="MsoNormal">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.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">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.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">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.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">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.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Best regards,<o:p></o:p></p>
<p class="MsoNormal">Holger<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"><o:p> </o:p></p>
<p class="MsoNormal">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 (<a href="mailto:dpo@esa.int">dpo@esa.int</a>).
<o:p></o:p></p>
</div>
</body>
</html>