<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=ks_c_5601-1987">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Gulim;
panose-1:2 11 6 0 0 1 1 1 1 1;}
@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:"Malgun Gothic";
panose-1:2 11 5 3 2 0 0 2 0 4;}
@font-face
{font-family:"\@Malgun Gothic";}
@font-face
{font-family:"\@Gulim";
panose-1:2 11 6 0 0 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
text-align:justify;
text-justify:inter-ideograph;
text-autospace:none;
word-break:break-all;
font-size:10.0pt;
font-family:"Malgun Gothic",sans-serif;
mso-fareast-language:KO;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:36.0pt;
text-align:justify;
text-justify:inter-ideograph;
text-autospace:none;
word-break:break-all;
font-size:10.0pt;
font-family:"Malgun Gothic",sans-serif;
mso-fareast-language:KO;}
span.EmailStyle21
{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:612.0pt 792.0pt;
margin:3.0cm 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:1398429802;
mso-list-type:hybrid;
mso-list-template-ids:-364583292 134807569 134807577 134807579 134807567 134807577 134807579 134807567 134807577 134807579;}
@list l0:level1
{mso-level-text:"%1\)";
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
ol
{margin-bottom:0cm;}
ul
{margin-bottom:0cm;}
--></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-GB" link="#0563C1" vlink="#954F72" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal" style="word-break:normal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US">Hi,<o:p></o:p></span></p>
<p class="MsoNormal" style="word-break:normal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<ol style="margin-top:0cm" start="1" type="1">
<li class="MsoListParagraph" style="margin-left:0cm;mso-list:l0 level1 lfo1;word-break:normal">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US">Compression: yes, I think this is very mission specific (available resources, file store implementations, file contents), e.g. ESA missions are currently mainly writing
files of space packets for CFDP downlink. They could apply compression to TM packets if they want to; instruments may already have optimised data formats; the MMU could apply some compression; ¡¦<br>
Furthermore, it might in general be preferred to apply compression also for storage and not just the file transfer.<br>
So, I would keep compression outside the CFDP protocol. One way to implement compression for transfer only may be to implement it as part of the Filestore Interface.<br>
<br>
<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:0cm;mso-list:l0 level1 lfo1;word-break:normal">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US">Multiple-Files-In-Single-Transactions: For simplicity, I would recommend to keep the standard as is (at most a single file per transaction). I think a change to allow
multiple files per transactions would have quite an impact as the standard is written with the assumption of having a single file (or none). I don¡¯t see a big efficiency improvement with such a change (we would save a few metadata pdu). It is of course perfectly
valid to concatenate or tar/zip files before sending. Private message to users (e.g., specifying the list of files and length which are sent) or even private file segment metadata might be used to support such practices. However, I would think that in situation
where we really worry about the overhead of metadata PDU, we might also think about applying CFDP in general.<br>
If the concern is more about the need to have multiple proxy put file operations for downlinking multiple files, I think it is already possible to have multiple proxy operations in a single metadata.<o:p></o:p></span></li></ol>
<p class="MsoNormal" style="word-break:normal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal" align="left" style="text-align:left;text-autospace:ideograph-numeric ideograph-other;word-break:normal">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-GB">Regards,<o:p></o:p></span></p>
<p class="MsoNormal" align="left" style="text-align:left;text-autospace:ideograph-numeric ideograph-other;word-break:normal">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-GB">Felix<o:p></o:p></span></p>
</div>
<p class="MsoNormal" style="word-break:normal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal" align="left" style="margin-left:36.0pt;text-align:left;text-autospace:ideograph-numeric ideograph-other;word-break:normal">
<b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif"> SIS-CFDPV1 <sis-cfdpv1-bounces@mailman.ccsds.org>
<b>On Behalf Of </b>Tomaso de Cola via SIS-CFDPV1<br>
<b>Sent:</b> 08 December 2022 09:53<br>
<b>To:</b> chkoo@kari.re.kr<br>
<b>Cc:</b> sis-cfdpv1@mailman.ccsds.org<br>
<b>Subject:</b> Re: [SIS-CFDPV1] Multiple file delivery request in a single Metada PDU and compressed delivery....<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal" align="left" style="margin-left:36.0pt;text-align:left"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-left:36.0pt;word-break:normal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US">For the compression matter, what I¡¯m wondering is whether this operation cannot be directly done at
data archiving level prior to invoking the CFDP service, so that CFDP is solely responsible for the data transmission no matter how and what content is transported in the corresponding transaction. I think this is in any case mission-specific and the other
people here in the mailinglist can say what they think in relation to their agency missions.<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt;word-break:normal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt;word-break:normal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US">Regards,<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt;word-break:normal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt;word-break:normal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US">Tomaso<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt;word-break:normal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal" align="left" style="margin-left:36.0pt;text-align:left;text-autospace:ideograph-other;word-break:normal">
<b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">
</span><span lang="KO" style="font-size:11.0pt">±¸Ã¶È¸</span><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif"> <<a href="mailto:chkoo@kari.re.kr">chkoo@kari.re.kr</a>>
<br>
<b>Sent:</b> Donnerstag, 8. Dezember 2022 09:36<br>
<b>To:</b> Cola, Tomaso de <<a href="mailto:Tomaso.deCola@dlr.de">Tomaso.deCola@dlr.de</a>><br>
<b>Cc:</b> <a href="mailto:sis-cfdpv1@mailman.ccsds.org">sis-cfdpv1@mailman.ccsds.org</a><br>
<b>Subject:</b> RE: Multiple file delivery request in a single Metada PDU and compressed delivery....<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal" align="left" style="margin-left:36.0pt;text-align:left"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US">No. You pointed out a valuable aspect of CFDP for actual use cases in space. If a file is requested in real-time manner, it must be treated as single CFDP transaction as current CFDP specification
states.<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US">Here, I would like to suggest another possible use case for delivering separated files but logically correlated, so these files can be archived by compression tools, tar or gzip, and be delivered
to a receiving entity as single file. Thanks to compression, this scheme will enable efficient bandwidth in a link when sending entity has enough processing power for real-time compression for requested multiple files.<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US">For instance, Filestore request has some Action codes,
</span><span lang="KO">¡®</span><span lang="EN-US">0000</span><span lang="KO">¡¯</span><span lang="EN-US"> for
</span><span lang="KO">¡°</span><span lang="EN-US">Create File</span><span lang="KO">¡±</span><span lang="EN-US">.
</span><span lang="KO">¡®</span><span lang="EN-US">0101</span><span lang="KO">¡¯</span><span lang="EN-US"> for
</span><span lang="KO">¡°</span><span lang="EN-US">Create Directory</span><span lang="KO">¡±</span><span lang="EN-US">.<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US">Then, maybe </span>
<span lang="KO">¡°</span><span lang="EN-US">Copy directory</span><span lang="KO">¡±</span><span lang="EN-US"> action/service won</span><span lang="KO">¡¯</span><span lang="EN-US">t be necessary or useful for some conditions?<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US">Best,<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US">Cheol<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal" align="left" style="margin-left:36.0pt;text-align:left;text-autospace:ideograph-other;word-break:normal">
<b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">
<a href="mailto:Tomaso.deCola@dlr.de">Tomaso.deCola@dlr.de</a> <<a href="mailto:Tomaso.deCola@dlr.de">Tomaso.deCola@dlr.de</a>>
<br>
<b>Sent:</b> Thursday, December 8, 2022 5:10 PM<br>
<b>To:</b> </span><span lang="KO" style="font-size:11.0pt">±¸Ã¶È¸</span><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif"> <<a href="mailto:chkoo@kari.re.kr">chkoo@kari.re.kr</a>><br>
<b>Cc:</b> <a href="mailto:sis-cfdpv1@mailman.ccsds.org">sis-cfdpv1@mailman.ccsds.org</a><br>
<b>Subject:</b> RE: Multiple file delivery request in a single Metada PDU and compressed delivery....<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal" align="left" style="margin-left:36.0pt;text-align:left"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt;word-break:normal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US">About the specification of multiple file names this is certainly doable, although not presently supported
(so that some modification of the blue book will be in any case necessary). My doubt is the overall effectiveness gain you achieve with this given the current CFDP protocol specification. If I understand correctly your idea, all files back to back will be
accommodated in a single FDU, which will be turn into a number of CFDP PDUs and in turn transmitted over a convenient UT. Then I also expect that the FDU will be delivered only when you receive the EOF, i.e. the first file being transmitted will be available
only when all the other files will be received. As such I¡¯d see more effective to have instead separated FDUs for each file, i.e. dedicated transaction for each file transmission that is what CFDP does nowadays.<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt;word-break:normal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt;word-break:normal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US">Am I missing something of your proposal?<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt;word-break:normal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt;word-break:normal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US">Regards,<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt;word-break:normal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt;word-break:normal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US">Tomaso<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt;word-break:normal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal" align="left" style="margin-left:36.0pt;text-align:left;text-autospace:ideograph-other;word-break:normal">
<b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">
</span><span lang="KO" style="font-size:11.0pt">±¸Ã¶È¸</span><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif"> <<a href="mailto:chkoo@kari.re.kr">chkoo@kari.re.kr</a>>
<br>
<b>Sent:</b> Donnerstag, 8. Dezember 2022 01:20<br>
<b>To:</b> Cola, Tomaso de <<a href="mailto:Tomaso.deCola@dlr.de">Tomaso.deCola@dlr.de</a>><br>
<b>Cc:</b> <a href="mailto:sis-cfdpv1@mailman.ccsds.org">sis-cfdpv1@mailman.ccsds.org</a><br>
<b>Subject:</b> RE: Multiple file delivery request in a single Metada PDU and compressed delivery....<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal" align="left" style="margin-left:36.0pt;text-align:left"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US">Hi Tomaso.<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US">Thanks for sharing your thoughts.<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US">Specifying multiple file name wouldn</span><span lang="KO">¡¯</span><span lang="EN-US">t be so complicated, For example, I guess it could be done if<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US">Source file name (LV) --> source file name (TLV), where type is for CSV (comma-separated values).<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US">So multiple file name can be given like
</span><span lang="KO">¡°</span><span lang="EN-US">xx(type code for CSV)</span><span lang="KO">¡± ¡°</span><span lang="EN-US">30</span><span lang="KO">¡± ¡°</span><span lang="EN-US">aaa.txt,bbb.tlm,ccc.img,ddd.dat</span><span lang="KO">¡±</span><span lang="EN-US">.
This can give some potential flexibility on operating CFDP for ground operators and spacecraft itself.<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US">If the compression happens in outside of CFDP app layer, someone must extract the compressed CFDP packet itself to see how the CFDP header is configured.<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US">Or, actually the compression can be done to File Data PDU than the target file itself.
<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US">Best,<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US">Cheol<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal" align="left" style="margin-left:36.0pt;text-align:left;text-autospace:ideograph-other;word-break:normal">
<b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">
<a href="mailto:Tomaso.deCola@dlr.de">Tomaso.deCola@dlr.de</a> <<a href="mailto:Tomaso.deCola@dlr.de">Tomaso.deCola@dlr.de</a>>
<br>
<b>Sent:</b> Wednesday, December 7, 2022 5:05 PM<br>
<b>To:</b> </span><span lang="KO" style="font-size:11.0pt">±¸Ã¶È¸</span><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif"> <<a href="mailto:chkoo@kari.re.kr">chkoo@kari.re.kr</a>><br>
<b>Cc:</b> <a href="mailto:sis-cfdpv1@mailman.ccsds.org">sis-cfdpv1@mailman.ccsds.org</a><br>
<b>Subject:</b> RE: Multiple file delivery request in a single Metada PDU and compressed delivery....<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal" align="left" style="margin-left:36.0pt;text-align:left"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt;word-break:normal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US">Hi Cheol,<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt;word-break:normal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt;word-break:normal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US">My understanding of CFDP is that it¡¯s transaction based, where a transaction is aimed at transferring
a single file. As such, transmission of multiple files has to go over different transactions. Moreover, the metadata allow to specify a single file name (source and destination) so that the possibility of sending multiple files with the same put request does
not seem to me possible.<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt;word-break:normal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US">As to the compression, in my opinion this is something that can happen outside the CFDP operations.<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt;word-break:normal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt;word-break:normal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US">Regards,<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt;word-break:normal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt;word-break:normal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US">Tomaso<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt;word-break:normal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal" align="left" style="margin-left:36.0pt;text-align:left;text-autospace:ideograph-other;word-break:normal">
<b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif"> SIS-CFDPV1 <<a href="mailto:sis-cfdpv1-bounces@mailman.ccsds.org">sis-cfdpv1-bounces@mailman.ccsds.org</a>>
<b>On Behalf Of </b>??? via SIS-CFDPV1<br>
<b>Sent:</b> Mittwoch, 7. Dezember 2022 01:49<br>
<b>To:</b> <a href="mailto:sis-cfdpv1@mailman.ccsds.org">sis-cfdpv1@mailman.ccsds.org</a><br>
<b>Subject:</b> [SIS-CFDPV1] Multiple file delivery request in a single Metada PDU and compressed delivery....<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal" align="left" style="margin-left:36.0pt;text-align:left"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US">Hi, CFDP fellow.<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US">Recently, I am questioning to myself about how I am able to get multiple files from remote space storage through CFDP.<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US">In the current CFDPv1 specification, we have to send multiple put.request commands to a sending entity as many as needed.<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US">Is it possible to think putting multiple file source in a metadata pdu and also possibly compressed by tar, zlib and so on to make it possible?<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US">For example, we can compile a metadata pdu as follows when a sending CFDP entity got requests for the aaa.txt bbb.tlm, ccc.img, ddd.dat separately:<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt;text-indent:10.2pt"><span lang="EN-US">File size : file size of compressed file, i.e., size of measurement_data.gz<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt;text-indent:10.2pt"><span lang="EN-US">Source file name : aaa.txt bbb.tlm, ccc.img, ddd.dat<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt;text-indent:10.2pt"><span lang="EN-US">Destination file name : measurement_data.gz<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US">In my opinion, voluntary compression service by a sending CFDP entity would be good in terms of bandwidth reduction, lower retransmission rate and so on.<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US">Cheol<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US"><o:p> </o:p></span></p>
</div>
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@esa.int).
</body>
</html>