<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=us-ascii"><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:Aptos;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:Aptos;
mso-ligatures:standardcontextual;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#467886;
text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
font-size:11.0pt;
font-family:Aptos;
mso-ligatures:standardcontextual;}
span.MsoSmartlink
{mso-style-priority:99;
color:blue;
background:#F3F2F1;
text-decoration:underline;}
span.EmailStyle23
{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;}
/* List Definitions */
@list l0
{mso-list-id:25717128;
mso-list-template-ids:-2098157896;}
@list l0:level1
{mso-level-start-at:3;
mso-level-text:%1;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:24.0pt;
text-indent:-24.0pt;}
@list l0:level2
{mso-level-start-at:4;
mso-level-text:"%1\.%2";
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:24.0pt;
text-indent:-24.0pt;}
@list l0:level3
{mso-level-text:"%1\.%2\.%3";
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:.5in;
text-indent:-.5in;}
@list l0:level4
{mso-level-text:"%1\.%2\.%3\.%4";
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:.5in;
text-indent:-.5in;}
@list l0:level5
{mso-level-text:"%1\.%2\.%3\.%4\.%5";
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:.75in;
text-indent:-.75in;}
@list l0:level6
{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6";
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:.75in;
text-indent:-.75in;}
@list l0:level7
{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7";
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:1.0in;
text-indent:-1.0in;}
@list l0:level8
{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8";
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:1.0in;
text-indent:-1.0in;}
@list l0:level9
{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8\.%9";
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:1.25in;
text-indent:-1.25in;}
@list l1
{mso-list-id:1169953161;
mso-list-type:hybrid;
mso-list-template-ids:934961296 134807569 134807577 134807579 134807567 134807577 134807579 134807567 134807577 134807579;}
@list l1:level1
{mso-level-text:"%1\)";
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l1:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l1:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></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="#467886" vlink="#96607D" style='word-wrap:break-word'><div class=WordSection1><p class=MsoNormal><span style='font-family:"Calibri",sans-serif'>Felix, I think that sounds good. This strategy is used in other CBOR-based encodings so not bespoke for this situation.<o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Calibri",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-family:"Calibri",sans-serif'>If you would like to include CDDL for the entire structures, I could help out. I think there is non-normative value in CDDL for helping to interpret the normative statements. It also makes example data generation and validation easier and more automated.<o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Calibri",sans-serif'><o:p> </o:p></span></p><div style='border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt'><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-family:"Calibri",sans-serif;mso-ligatures:none'>From:</span></b><span style='font-family:"Calibri",sans-serif;mso-ligatures:none'> Felix Flentge <Felix.Flentge@esa.int> <br><b>Sent:</b> Friday, May 16, 2025 10:47 AM<br><b>To:</b> Sipos, Brian J. <Brian.Sipos@jhuapl.edu>; sis-dtn@mailman.ccsds.org<br><b>Cc:</b> Juan A. Fraire <juan.fraire@inria.fr>; Alice Le Bihan <alice.le-bihan@insa-lyon.fr>; Jeck, Yanik <yanik.jeck@cgi.com>; Kramp, Paul-Niklas <paul-niklas.kramp@cgi.com><br><b>Subject:</b> [EXT] RE: New Draft: COMPRESSED CUSTODY SIGNALING AND BUNDLE STATUS REPORTING<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><div><div id=APLWarningText><table class=MsoNormalTable border=0 cellspacing=0 cellpadding=0 align=left><tr><td width="100%" style='width:100.0%;background:#E0E0E0;padding:0in 0in 0in 0in'><p class=MsoNormal style='mso-element:frame;mso-element-frame-hspace:2.25pt;mso-element-wrap:around;mso-element-anchor-vertical:paragraph;mso-element-anchor-horizontal:column;mso-height-rule:exactly'><b><span style='font-family:"Calibri",sans-serif;color:red;mso-ligatures:none'>APL external email warning: </span></b><span style='font-family:"Calibri",sans-serif;color:black;mso-ligatures:none'>Verify sender <a href="mailto:Felix.Flentge@esa.int">Felix.Flentge@esa.int</a> before clicking links or attachments</span><span style='font-family:"Calibri",sans-serif;mso-ligatures:none'><o:p></o:p></span></p></td></tr></table><p><span lang=EN-GB> <o:p></o:p></span></p></div></div><p class=MsoNormal><span lang=EN-GB>Hi Brian,<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-GB>I have discussed with Yanik (who may still not have access to the CCSDS mailinglist...) and he came up with the following proposal:<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB><o:p> </o:p></span></p><p class=MsoNormal>In terms of wording, I think it would be clearer to keep the definition for<o:p></o:p></p><p class=MsoNormal>the Bundle Sequence Range as is and modify the definition for the Bundle Sequence instead. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I.e., we could append an “or a CBOR uint” to describe the Bundle Sequence Range (field).<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>This could e.g., look like:<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Bundle Sequence Range – A Bundle Sequence Range as defined in 3.3.2 below <o:p></o:p></p><p class=MsoNormal style='margin-left:1.0in;text-indent:.5in'> or <o:p></o:p></p><p class=MsoNormal style='margin-left:1.5in'> A CBOR unsigned integer if there is only a single sequence to be included, representing the length of that sequence<o:p></o:p></p><p class=MsoNormal style='margin-left:1.5in'><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I suppose, put in CDDL, this could then look like this instead:<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal style='margin-left:.5in'><span style='font-family:"Calibri",sans-serif'>seq = [<o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span style='font-family:"Calibri",sans-serif'> seq-id: uint / eid,<o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span style='font-family:"Calibri",sans-serif'> seq-start: uint,<o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span style='font-family:"Calibri",sans-serif'> range: seq-range <span style='background:yellow;mso-highlight:yellow'>/ seq-incl-len</span>,<o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span style='font-family:"Calibri",sans-serif'> ? blk-source: eid<o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span style='font-family:"Calibri",sans-serif'>]<o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span style='font-family:"Calibri",sans-serif'>seq-range = [ seq-incl-len, + ( seq-excl-len, seq-incl-len) ]<o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span style='font-family:"Calibri",sans-serif'>seq-incl-len = uint .gt 0 ; inclusive length<o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span style='font-family:"Calibri",sans-serif'>seq-excl-len = uint .gt 0 ; exclusive length<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-GB><o:p> </o:p></span></p><div><p class=MsoNormal><span lang=EN-GB style='mso-ligatures:none'>Regards,<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB style='mso-ligatures:none'>Felix<o:p></o:p></span></p></div><p class=MsoNormal><span lang=EN-GB><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 style='margin-left:.5in'><b><span style='font-family:"Calibri",sans-serif;mso-ligatures:none'>From:</span></b><span style='font-family:"Calibri",sans-serif;mso-ligatures:none'> Sipos, Brian J. <<a href="mailto:Brian.Sipos@jhuapl.edu">Brian.Sipos@jhuapl.edu</a>> <br><b>Sent:</b> 15 May 2025 15:09<br><b>To:</b> Felix Flentge <<a href="mailto:Felix.Flentge@esa.int">Felix.Flentge@esa.int</a>>; <a href="mailto:sis-dtn@mailman.ccsds.org">sis-dtn@mailman.ccsds.org</a><br><b>Cc:</b> Juan A. Fraire <<a href="mailto:juan.fraire@inria.fr">juan.fraire@inria.fr</a>>; Alice Le Bihan <<a href="mailto:alice.le-bihan@insa-lyon.fr">alice.le-bihan@insa-lyon.fr</a>>; Jeck, Yanik <<a href="mailto:yanik.jeck@cgi.com">yanik.jeck@cgi.com</a>>; Kramp, Paul-Niklas <<a href="mailto:paul-niklas.kramp@cgi.com">paul-niklas.kramp@cgi.com</a>><br><b>Subject:</b> RE: New Draft: COMPRESSED CUSTODY SIGNALING AND BUNDLE STATUS REPORTING<o:p></o:p></span></p></div></div><p class=MsoNormal style='margin-left:.5in'><span lang=EN-GB><o:p> </o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span style='font-family:"Calibri",sans-serif'>Felix,<o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span style='font-family:"Calibri",sans-serif'>Thanks for consideration of my earlier suggestion. I think the definition of Bundle Sequence Range in Sec 3.3 is consistent and understandable.<o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span style='font-family:"Calibri",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span style='font-family:"Calibri",sans-serif'>There is one possible compression, saving one byte, in the case where the array would have a single uint item it can be substituted with the uint itself. It doesn’t affect the information model being encoded, but does add a small coding / decoding overhead to apply the compression. So it’s completely optional if you think there is that much value in one byte. (This compressed form would also degenerate to your earlier form of start + length if there are no excluded intervals)<o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span style='font-family:"Calibri",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span style='font-family:"Calibri",sans-serif'>Put in CDDL, the `seq-range` would include the following (with rule `eid` taken from RFC 9171 appendix)<o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span style='font-family:"Calibri",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span style='font-family:"Calibri",sans-serif'>seq = [<o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span style='font-family:"Calibri",sans-serif'> seq-id: uint / eid,<o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span style='font-family:"Calibri",sans-serif'> seq-start: uint,<o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span style='font-family:"Calibri",sans-serif'> seq-range,<o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span style='font-family:"Calibri",sans-serif'> ? blk-source: eid<o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span style='font-family:"Calibri",sans-serif'>]<o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span style='font-family:"Calibri",sans-serif'>seq-range = [ seq-incl-len, + ( seq-excl-len, seq-incl-len) ] <span style='background:yellow;mso-highlight:yellow'>/ seq-incl-len</span><o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span style='font-family:"Calibri",sans-serif'>seq-incl-len = uint .gt 0 ; inclusive length<o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span style='font-family:"Calibri",sans-serif'>seq-excl-len = uint .gt 0 ; exclusive length<o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span style='font-family:"Calibri",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span style='font-family:"Calibri",sans-serif'><o:p> </o:p></span></p><div style='border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt'><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal style='margin-left:.5in'><b><span style='font-family:"Calibri",sans-serif;mso-ligatures:none'>From:</span></b><span style='font-family:"Calibri",sans-serif;mso-ligatures:none'> SIS-DTN <<a href="mailto:sis-dtn-bounces@mailman.ccsds.org">sis-dtn-bounces@mailman.ccsds.org</a>> <b>On Behalf Of </b>Felix Flentge via SIS-DTN<br><b>Sent:</b> Wednesday, May 14, 2025 9:11 AM<br><b>To:</b> Dr. Keith L Scott via SIS-DTN <<a href="mailto:sis-dtn@mailman.ccsds.org">sis-dtn@mailman.ccsds.org</a>><br><b>Cc:</b> Juan A. Fraire <<a href="mailto:juan.fraire@inria.fr">juan.fraire@inria.fr</a>>; Alice Le Bihan <<a href="mailto:alice.le-bihan@insa-lyon.fr">alice.le-bihan@insa-lyon.fr</a>>; Jeck, Yanik <<a href="mailto:yanik.jeck@cgi.com">yanik.jeck@cgi.com</a>>; Kramp, Paul-Niklas <<a href="mailto:paul-niklas.kramp@cgi.com">paul-niklas.kramp@cgi.com</a>><br><b>Subject:</b> [EXT] [Sis-dtn] New Draft: COMPRESSED CUSTODY SIGNALING AND BUNDLE STATUS REPORTING<o:p></o:p></span></p></div></div><p class=MsoNormal style='margin-left:.5in'><o:p> </o:p></p><div><div id=APLWarningText><table class=MsoNormalTable border=0 cellspacing=0 cellpadding=0 align=left width="100%" style='width:100.0%'><tr><td width="100%" style='width:100.0%;background:#E0E0E0;padding:0in 0in 0in 0in'><p class=MsoNormal style='mso-element:frame;mso-element-frame-hspace:2.25pt;mso-element-wrap:around;mso-element-anchor-vertical:paragraph;mso-element-anchor-horizontal:column;mso-height-rule:exactly'><b><span style='font-family:"Calibri",sans-serif;color:red;mso-ligatures:none'>APL external email warning: </span></b><span style='font-family:"Calibri",sans-serif;color:black;mso-ligatures:none'>Verify sender <a href="mailto:sis-dtn-bounces@mailman.ccsds.org">sis-dtn-bounces@mailman.ccsds.org</a> before clicking links or attachments</span><span style='font-family:"Calibri",sans-serif;mso-ligatures:none'><o:p></o:p></span></p></td></tr></table><p style='margin-left:.5in'><span lang=EN-GB> <o:p></o:p></span></p></div></div><p class=MsoNormal style='margin-left:.5in'><span lang=EN-GB>Hi,<o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span lang=EN-GB><o:p> </o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span lang=EN-GB>I have just uploaded Draft H of the ‘Compressed Custody Signaling And Bundle Status Reporting’ Orange Book to CWE:<o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span lang=EN-GB><o:p> </o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span lang=EN-GB><a href="https://spacecomm.sharepoint.com/:w:/r/sites/SIS/_layouts/15/Doc.aspx?sourcedoc=%7B10790F7B-6318-4BD0-9D53-8813C83BE941%7D&file=CompressedBundleStatusReportingAndCustodySignaling_OrangeBook_Draft_H.docx&action=default&mobileredirect=true"><span class=MsoSmartlink>CompressedBundleStatusReportingAndCustodySignaling_OrangeBook_Draft_H.docx</span></a><o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span lang=EN-GB><o:p> </o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span lang=EN-GB>We have introduced the following changes:<o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span lang=EN-GB><o:p> </o:p></span></p><p class=MsoListParagraph style='margin-left:1.0in;text-indent:-.25in;mso-list:l1 level1 lfo2'><![if !supportLists]><span lang=EN-GB><span style='mso-list:Ignore'>1)<span style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]><span lang=EN-GB>Based on Brian’s proposal to make the reporting even more efficient, Yanik analysed and designed a new way to encode bundle sequences which may contain some gaps (see updated Section 3.3). It is not so easy to come up with some concise language for that, so please let us know if you have suggestions for improvement.<o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span lang=EN-GB><o:p> </o:p></span></p><p class=MsoListParagraph style='margin-left:1.0in;text-indent:-.25in;mso-list:l1 level1 lfo2'><![if !supportLists]><span lang=EN-GB><span style='mso-list:Ignore'>2)<span style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]><span lang=EN-GB>I took the opportunity to not allow processing of the CREB/CTEB blocks in fragments:<o:p></o:p></span></p><p class=MsoListParagraph style='margin-left:1.5in;text-indent:-.5in;mso-list:l0 level3 lfo4'><![if !supportLists]><span style='mso-list:Ignore'>3.4.1<span style='font:7.0pt "Times New Roman"'> </span></span><![endif]>Extension Blocks specified in this specification shall only be added and processed in non-fragmented bundles.<o:p></o:p></p><p class=MsoNormal style='margin-left:1.0in'><o:p> </o:p></p><p class=MsoNormal style='mso-margin-top-alt:0in;margin-right:0in;margin-bottom:12.0pt;margin-left:1.0in'>NOTE – As later fragmentation of bundles using the extension blocks specified in this specification may lead to unintended effects such as loss of expected reporting or custody signals as fragmented bundles are never re-assembled (RfC 9171 does only specify Application Data Unit Re-Assembly), it is recommended to set the ‘Bundle Must Not be Fragmented’ flag at the source if the application of custody transfer or compressed status reporting according to this specification is intended. <span lang=EN-GB><o:p></o:p></span></p><p class=MsoListParagraph style='margin-left:1.0in;text-indent:-.25in;mso-list:l1 level1 lfo2'><![if !supportLists]><span lang=EN-GB><span style='mso-list:Ignore'>3)<span style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]><span lang=EN-GB>The compressed reporting signal (see 5.2.3) has been changed to include the reporting reason code as integer (and not as an integer interpreted as bit field). Please note that the Status Report Request Flags (5.1.4.1) shall actually be processed as a bit field. However, we align the Bit Number with the reason code integer for consistency. <o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span lang=EN-GB><o:p> </o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span lang=EN-GB style='mso-ligatures:none'>Regards,<o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span lang=EN-GB style='mso-ligatures:none'>Felix<o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span lang=EN-GB><o:p> </o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span lang=EN-GB style='font-family:"Calibri",sans-serif;mso-ligatures:none'>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></span></p></div><p class=MsoNormal><span lang=EN-GB style='font-family:"Calibri",sans-serif;mso-ligatures:none'>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></span></p></div></div></body></html>