$)C<span style=" font-size:10pt;font-family:sans-serif">Hi Cheol,</span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">sure, we should
talk about the future direction and the timeline.</span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">We should also
discuss the 'trivial CFDP', in particular, CFDP over BP (or LTP directly).</span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">IMHO, we should
try to keep compatibility with current CFDP. However, we may want to make
more features optional for use in such environments (and based on current
implementation experience), eg:</span>
<br><span style=" font-size:10pt;font-family:sans-serif">- implementation
of Class 2 / SFO / Proxy Operations</span>
<br><span style=" font-size:10pt;font-family:sans-serif">- filestore procedures</span>
<br><span style=" font-size:10pt;font-family:sans-serif">- fault handler
overwrites</span>
<br><span style=" font-size:10pt;font-family:sans-serif">- suspension /
resume</span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">For Bundle Protocol/LTP,
we should allow to embed any number of CFDP PDU in a single bundle / LTP
Block (eg, a whole transaction). This may also facilitate CFDP processing
on the receiving side a bit (inactivity timer / limit). </span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">Regards,</span>
<br><span style=" font-size:10pt;font-family:sans-serif">Felix</span>
<br>
<br>
<br>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">From:
</span><span style=" font-size:9pt;font-family:sans-serif">"18C6H8"
<chkoo@kari.re.kr></span>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">To:
</span><span style=" font-size:9pt;font-family:sans-serif">"Felix.Flentge@esa.int"
<Felix.Flentge@esa.int></span>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">Cc:
</span><span style=" font-size:9pt;font-family:sans-serif">"sis-cfdpv1@mailman.ccsds.org"
<sis-cfdpv1@mailman.ccsds.org></span>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">Date:
</span><span style=" font-size:9pt;font-family:sans-serif">13/04/2022
06:02</span>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">Subject:
</span><span style=" font-size:9pt;font-family:sans-serif">RE:
[SIS-CFDPV1] CFDP WG (Virtual) Meeting</span>
<br>
<hr noshade>
<br>
<br>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:10pt;font-family:sans-serif">Hi
Felix, Can we discuss about what the future direction of CFDP revision
would be?</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:10pt;font-family:sans-serif">Also,
can we think about the possibility of much lighter version of CFDP Class
1 like tftp (Trivial FTP)?</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:10pt;font-family:sans-serif"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:10pt;font-family:sans-serif">I
think much of functions in current CFDP are being done by LTP convergence
layer. CFDP is very capable of handling file delivery service for which
LTP/BP is not considered, but when and where LTP/BP are involved I feel
most functions in CFDP redundancy because similar functions are already
provided by LTP layer. I think it may be enough if CFDP has some critical
functions without listing of Metadata/Fdu/NAK/EOF/FIN PDUs, e.g., file
name, file length, NAK, cancel, file creation/deletion/change and so on,
like TFTP.</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:10pt;font-family:sans-serif"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:10pt;font-family:sans-serif">I
am just curious to know how other people think about this.</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:10pt;font-family:sans-serif"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:10pt;font-family:sans-serif">Cheol
</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:10pt;font-family:sans-serif"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"><b>From:</b>
SIS-CFDPV1 <sis-cfdpv1-bounces@mailman.ccsds.org> <b>On Behalf Of
</b>Felix.Flentge--- via SIS-CFDPV1<b><br>
Sent:</b> Saturday, April 9, 2022 6:05 PM<b><br>
To:</b> sis-cfdpv1@mailman.ccsds.org<b><br>
Subject:</b> [SIS-CFDPV1] CFDP WG (Virtual) Meeting</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:10pt;font-family:Arial">Dear
All,</span><span style=" font-size:11pt;font-family:Calibri"> <br>
</span><span style=" font-size:10pt;font-family:Arial"><br>
first, let's see whether this mailing list is still active ...</span><span style=" font-size:11pt;font-family:Calibri">
<br>
</span><span style=" font-size:10pt;font-family:Arial"><br>
It has been very quiet at CCSDS since the publishing of the B5 version.
However, I assume that a lot of agencies have been busy bringing CFDP into
their missions. At least I have received some feedback from ESA missions
I would like to share and discuss with the WG (eg, introduction of an Abandon.Request;
how to react to NAK for unknown transactions; some clarifications). If
there is interest, I can also provide some updates related the planned
Return CFDP PDU Cross-Support Transfer Service Orange Book which we need
to support Distributed CFDP scenarios. </span><span style=" font-size:11pt;font-family:Calibri"><br>
</span><span style=" font-size:10pt;font-family:Arial"><br>
If you have other topics to discuss, please let me know.</span><span style=" font-size:11pt;font-family:Calibri">
<br>
</span><span style=" font-size:10pt;font-family:Arial"><br>
I have set-up a doodle poll in order to find a suitable time for a meeting:</span><span style=" font-size:11pt;font-family:Calibri">
<br>
</span><span style=" font-size:11pt;color:blue;font-family:Calibri"><u><br>
</u></span><a href=https://doodle.com/meeting/participate/id/e73L7POe><span style=" font-size:10pt;color:blue;font-family:Arial"><u>https://doodle.com/meeting/participate/id/e73L7POe</u></span></a><span style=" font-size:11pt;font-family:Calibri">
<br>
</span><span style=" font-size:10pt;font-family:Arial"><br>
Please enter your availability until 28 April.</span><span style=" font-size:11pt;font-family:Calibri">
<br>
</span><span style=" font-size:10pt;font-family:Arial"><br>
Regards,<br>
Felix</span><span style=" font-size:11pt;font-family:Calibri"> <br>
<br>
</span><span style=" font-size:8pt;color:#808080;font-family:Verdana"><b><br>
_________________________________________</b></span><span style=" font-size:11pt;font-family:Calibri">
</span><span style=" font-size:8pt;color:#808080;font-family:Verdana"><b><br>
ESA - European Space Agency </b></span><span style=" font-size:8pt;color:#00a1e0;font-family:Verdana"><br>
Dr. Felix Flentge</span><span style=" font-size:8pt;color:#808080;font-family:Verdana"><br>
Software Engineer, OPS-GSB<br>
Ground Systems Engineering Department<br>
Directorate of Operations</span><span style=" font-size:11pt;font-family:Calibri">
</span><span style=" font-size:8pt;color:#808080;font-family:Verdana"><b><br>
ESA - ESOC</b><br>
Robert-Bosch-Str.5, D-64293 Darmstadt, Germany</span><span style=" font-size:11pt;font-family:Calibri">
</span><span style=" font-size:8pt;color:#808080;font-family:Verdana"><br>
Phone: +49 6151 90 4075 | Email: </span><a href=mailto:Felix.Flentge@esa.int><span style=" font-size:8pt;color:blue;font-family:Verdana"><u>Felix.Flentge@esa.int</u></span></a><span style=" font-size:8pt;color:#808080;font-family:Verdana"><br>
</span><span style=" font-size:11pt;font-family:Calibri"><br>
<br>
</span><span style=" font-size:9pt;color:#808080;font-family:Arial"><b><i><br>
Disclaimer</i></b></span><span style=" font-size:11pt;font-family:Calibri">
</span><span style=" font-size:7pt;color:#808080;font-family:Arial"><i><br>
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
(</i></span><a href=mailto:dpo@esa.int><span style=" font-size:7pt;color:blue;font-family:Arial"><i><u>dpo@esa.int</u></i></span></a><span style=" font-size:7pt;color:#808080;font-family:Arial"><i>).</i></span></p>
<p style="margin-top:0px;margin-Bottom:0px"></p>
<p style="margin-top:0px;margin-Bottom:0px"></p>