<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)">

<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}

o\:* {behavior:url(#default#VML);}

w\:* {behavior:url(#default#VML);}

.shape {behavior:url(#default#VML);}

</style><![endif]--><style><!--

/* Font Definitions */

@font-face

        {font-family:돋움;

        panose-1:2 11 6 0 0 1 1 1 1 1;}

@font-face

        {font-family:굴림;

        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:"맑은 고딕";

        panose-1:2 11 5 3 2 0 0 2 0 4;}

@font-face

        {font-family:"\@맑은 고딕";}

@font-face

        {font-family:"\@굴림";

        panose-1:2 11 6 0 0 1 1 1 1 1;}

@font-face

        {font-family:ArialNarrow;}

@font-face

        {font-family:"\@돋움";

        panose-1:2 11 6 0 0 1 1 1 1 1;}

/* Style Definitions */

p.MsoNormal, li.MsoNormal, div.MsoNormal

        {margin:0cm;

        margin-bottom:.0001pt;

        font-size:11.0pt;

        font-family:"Calibri",sans-serif;}

a:link, span.MsoHyperlink

        {mso-style-priority:99;

        color:#0563C1;

        text-decoration:underline;}

a:visited, span.MsoHyperlinkFollowed

        {mso-style-priority:99;

        color:#954F72;

        text-decoration:underline;}

p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph

        {mso-style-priority:34;

        mso-margin-top-alt:auto;

        margin-right:0cm;

        mso-margin-bottom-alt:auto;

        margin-left:0cm;

        font-size:11.0pt;

        font-family:"Calibri",sans-serif;}

p.msonormal0, li.msonormal0, div.msonormal0

        {mso-style-name:msonormal;

        mso-margin-top-alt:auto;

        margin-right:0cm;

        mso-margin-bottom-alt:auto;

        margin-left:0cm;

        font-size:12.0pt;

        font-family:굴림;}

span.EmailStyle19

        {mso-style-type:personal;

        font-family:"Calibri",sans-serif;

        color:windowtext;}

span.EmailStyle20

        {mso-style-type:personal-reply;

        font-family:"맑은 고딕";

        color:windowtext;}

.MsoChpDefault

        {mso-style-type:export-only;}

@page WordSection1

        {size:612.0pt 792.0pt;

        margin:72.0pt 72.0pt 72.0pt 72.0pt;}

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="KO" link="#0563C1" vlink="#954F72" style="word-wrap:break-word">

<div class="WordSection1">

<p class="MsoNormal" style="word-break:break-hangul"><span lang="EN-US" style="font-size:10.0pt;font-family:"맑은 고딕"">Hi, Felix.<o:p></o:p></span></p>

<p class="MsoNormal" style="word-break:break-hangul"><span lang="EN-US" style="font-size:10.0pt;font-family:"맑은 고딕""><o:p> </o:p></span></p>

<p class="MsoNormal" style="word-break:break-hangul"><span lang="EN-US" style="font-size:10.0pt;font-family:"맑은 고딕"">Of course, I know your point.<o:p></o:p></span></p>

<p class="MsoNormal" style="word-break:break-hangul"><span lang="EN-US" style="font-size:10.0pt;font-family:"맑은 고딕"">IMHO, making

</span><span style="font-size:10.0pt;font-family:"맑은 고딕"">‘<span lang="EN-US">automation</span>’<span lang="EN-US"> as comprehensive as possible when interfacing with different agency/company/hardware, software specifications is the goal of the standardization

process, a.k.a. developing a ‘<span lang="EN-US">Protocol’<span lang="EN-US">.

<o:p></o:p></span></span></p>

<p class="MsoNormal" style="word-break:break-hangul"><span lang="EN-US" style="font-size:10.0pt;font-family:"맑은 고딕""><o:p> </o:p></span></p>

<p class="MsoNormal" style="word-break:break-hangul"><span lang="EN-US" style="font-size:10.0pt;font-family:"맑은 고딕"">I do suspect that working with ICD during interfacing with heterogeneous system is truly helpful for the automation when we talk each other

 via CFDP over LTP/BP. Memorizing and processing separately according to a specific spacecraft specification, e.g., NASA spacecraft A, B and ESA spacecraft C, D, .., are really painful and error-prone.<o:p></o:p></span></p>

<p class="MsoNormal" style="word-break:break-hangul"><span lang="EN-US" style="font-size:10.0pt;font-family:"맑은 고딕"">Let</span><span style="font-size:10.0pt;font-family:"맑은 고딕"">’<span lang="EN-US">s come up with a feasible operating concept in coming CCSDS

 Fall meeting.<o:p></o:p></span></span></p>

<p class="MsoNormal" style="word-break:break-hangul"><span lang="EN-US" style="font-size:10.0pt;font-family:"맑은 고딕""><o:p> </o:p></span></p>

<p class="MsoNormal" style="word-break:break-hangul"><span lang="EN-US" style="font-size:10.0pt;font-family:"맑은 고딕"">Cheol<o:p></o:p></span></p>

<p class="MsoNormal" style="word-break:break-hangul"><span lang="EN-US" style="font-size:10.0pt;font-family:"맑은 고딕""><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"><b><span lang="EN-US">From:</span></b><span lang="EN-US"> Felix Flentge <Felix.Flentge@esa.int>

<br>

<b>Sent:</b> Wednesday, October 18, 2023 3:39 PM<br>

<b>To:</b> </span><span style="font-family:굴림">구철회</span><span lang="EN-US"> <chkoo@kari.re.kr><br>

<b>Cc:</b> Wiegand, Robert E. (GSFC-5830) <robert.e.wiegand@nasa.gov>; sis-cfdpv1@mailman.ccsds.org<br>

<b>Subject:</b> RE: Re: [SIS-CFDPV1] CFDP unbounded transfers<o:p></o:p></span></p>

</div>

</div>

<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>

<p class="MsoNormal"><span lang="EN-GB" style="mso-fareast-language:EN-US">Hi,<o:p></o:p></span></p>

<p class="MsoNormal"><span lang="EN-GB" style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>

<p class="MsoNormal"><span lang="EN-GB" style="mso-fareast-language:EN-US">I would be very careful not to introduce additional complexity by signalling supported or unsupported features within CFDP itself. To me it does not seem to be overly useful as we don’t

 have ‘spontaneous’ file transactions between CFDP entities but careful mission designs with ICDs, validation, etc before we even fly. Based on my experience with flight implementations, I also doubt that such features would be implemented. I think what is

 much more important is to have a clear identification of the capabilities of each implementation and ways to easily communicate this. This is the idea behind the identification of optional CFDP features.<o:p></o:p></span></p>

<p class="MsoNormal"><span lang="EN-GB" style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>

<p class="MsoNormal"><span lang="EN-GB" style="mso-fareast-language:EN-US">We should discuss at the meeting whether there is a need for an additional condition code (there is just one reserved left and we should not change the size). If so, I would make something

 more generic like ‘unsupported feature’ or ‘protocol error’.<o:p></o:p></span></p>

<p class="MsoNormal"><span lang="EN-GB" style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>

<p class="MsoNormal"><span lang="EN-GB" style="mso-fareast-language:EN-US">In the long term, we would hope to run CFDP/BP and we maybe could communicate about supported features using BP network management but I would not try to build something separate for

 CFDP. <o:p></o:p></span></p>

<p class="MsoNormal"><span lang="EN-GB" style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>

<p class="MsoNormal"><span lang="EN-GB">Regards,<o:p></o:p></span></p>

<p class="MsoNormal"><span lang="EN-GB">Felix<o:p></o:p></span></p>

<p class="MsoNormal"><span lang="EN-GB" style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>

<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">

<p class="MsoNormal" style="margin-left:36.0pt"><b><span lang="EN-US">From:</span></b><span lang="EN-US"> chkoo@kari.re.kr <chkoo@kari.re.kr>

<br>

<b>Sent:</b> Wednesday, October 11, 2023 1:20 PM<br>

<b>To:</b> Felix Flentge <Felix.Flentge@esa.int><br>

<b>Cc:</b> Wiegand, Robert E. (GSFC-5830) <robert.e.wiegand@nasa.gov>; sis-cfdpv1@mailman.ccsds.org<br>

<b>Subject:</b> RE: Re: [SIS-CFDPV1] CFDP unbounded transfers<o:p></o:p></span></p>

</div>

<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-GB"><o:p> </o:p></span></p>

<p style="margin-left:36.0pt"><span lang="EN-GB" style="font-size:10.0pt">Hi, Felix.<o:p></o:p></span></p>

<p style="margin-left:36.0pt"><span lang="EN-GB" style="font-size:10.0pt"><o:p> </o:p></span></p>

<p style="margin-left:36.0pt"><span lang="EN-GB" style="font-size:10.0pt">Add my positive vote for this. We should support such limited or constrained CFDP entity here.<o:p></o:p></span></p>

<p style="margin-left:36.0pt"><span lang="EN-GB" style="font-size:10.0pt">We may want to add a condition code for this in Table 5-5 when the limited or constrained CFDP entity receives data which exceeds 32 bit size, such as "Big file is not supported".<o:p></o:p></span></p>

<p style="margin-left:36.0pt"><span lang="EN-GB" style="font-size:10.0pt"><o:p> </o:p></span></p>

<p style="margin-left:36.0pt"><span lang="EN-GB" style="font-size:10.0pt">If the consideration for the system that does not support partial function in the CFDP specification is necessary during the revision of CFDP specification document, I think we need some

 additional features for handing this functional gap between functionally different entities.<o:p></o:p></span></p>

<p style="margin-left:36.0pt"><span lang="EN-GB" style="font-size:10.0pt"><o:p> </o:p></span></p>

<p style="margin-left:36.0pt"><span lang="EN-GB" style="font-size:10.0pt">For example,<o:p></o:p></span></p>

<p style="margin-left:36.0pt"><span lang="EN-GB" style="font-size:10.0pt">I think a function that can be used at figuring out the remote entity's functional status may be helpful, such as the supported CFDP class(class 1 only, class 1&2, class 2 only), big

 file supported or not, existence of CL (none, LTP only, BP only, LTP/BP, ...), remaining capacity of storage, available bandwidth, supported CFDP specification document (B4, B5, B6, ...). It is working like these, "FYI, my current CFDP supporting status have

 been sent. Let me have yours." We can refer the function of the Contact Header or SESS_INIT in the RFC-9174 for this query function.<o:p></o:p></span></p>

<p style="margin-left:36.0pt"><span lang="EN-GB" style="font-size:10.0pt"><o:p> </o:p></span></p>

<p style="margin-left:36.0pt"><span lang="EN-GB" style="font-size:10.0pt">Cheol<o:p></o:p></span></p>

<div style="margin-left:9.6pt;margin-top:22.5pt">

<p class="MsoNormal" style="margin-left:36.0pt"><b><span lang="EN-GB" style="font-size:9.0pt;font-family:돋움;color:#0066CC">---------

</span></b><b><span style="font-size:9.0pt;font-family:돋움;color:#0066CC">원본 메일</span></b><b><span lang="EN-GB" style="font-size:9.0pt;font-family:돋움;color:#0066CC"> ---------<o:p></o:p></span></b></p>

</div>

<blockquote style="border:none;border-left:solid windowtext 1.5pt;padding:0cm 0cm 0cm 12.0pt;margin-left:9.6pt;margin-top:5.0pt;margin-right:0cm;margin-bottom:5.0pt">

<div>

<p class="MsoNormal" style="margin-left:36.0pt"><b><span style="font-size:9.0pt;font-family:"맑은 고딕"">보낸사람</span></b><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif"> : Felix Flentge via SIS-CFDPV1 <</span><span lang="EN-US"><a href="mailto:sis-cfdpv1@mailman.ccsds.org"><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif">sis-cfdpv1@mailman.ccsds.org</span></a></span><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif">><br>

</span><b><span style="font-size:9.0pt;font-family:"맑은 고딕"">받는사람</span></b><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif"> : "Wiegand, Robert E. (GSFC-5830)" <</span><span lang="EN-US"><a href="mailto:robert.e.wiegand@nasa.gov"><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif">robert.e.wiegand@nasa.gov</span></a></span><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif">>,

 "</span><span lang="EN-US"><a href="mailto:sis-cfdpv1@mailman.ccsds.org"><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif">sis-cfdpv1@mailman.ccsds.org</span></a></span><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif">"

 <</span><span lang="EN-US"><a href="mailto:sis-cfdpv1@mailman.ccsds.org"><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif">sis-cfdpv1@mailman.ccsds.org</span></a></span><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif">><br>

</span><b><span style="font-size:9.0pt;font-family:"맑은 고딕"">받은날짜</span></b><span style="font-size:9.0pt;font-family:"Arial",sans-serif">

</span><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif">: 2023-10-11 (</span><span style="font-size:9.0pt;font-family:"맑은 고딕"">수</span><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif">) 16:07:38<br>

</span><b><span style="font-size:9.0pt;font-family:"맑은 고딕"">제목</span></b><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif"> : Re: [SIS-CFDPV1] CFDP unbounded transfers<o:p></o:p></span></p>

<div style="margin-top:3.75pt">

<div>

<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:36.0pt">

<span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif;mso-fareast-language:EN-US">Hi Bob,</span><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif"><o:p></o:p></span></p>

<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:36.0pt">

<span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif;mso-fareast-language:EN-US"> </span><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif"><o:p></o:p></span></p>

<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:36.0pt">

<span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif;mso-fareast-language:EN-US">I tend to agree that we should also allow ‘small’ unbounded files without FSS if the sender ensures that they will be < 4GB.</span><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif"><o:p></o:p></span></p>

<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:36.0pt">

<span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif;mso-fareast-language:EN-US"> </span><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif"><o:p></o:p></span></p>

<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:36.0pt">

<span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif;mso-fareast-language:EN-US">If  there are no objections, I will integrate this change in my B6 draft.</span><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif"><o:p></o:p></span></p>

<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:36.0pt">

<span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif;mso-fareast-language:EN-US"> </span><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif"><o:p></o:p></span></p>

<div>

<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:36.0pt">

<span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif">Regards,<o:p></o:p></span></p>

<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:36.0pt">

<span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif">Felix<o:p></o:p></span></p>

</div>

<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:36.0pt">

<span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif;mso-fareast-language:EN-US"> </span><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif"><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" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:72.0pt">

<b><span lang="EN-US" style="font-size:9.0pt;font-family:"Arial",sans-serif">From:</span></b><span lang="EN-US" style="font-size:9.0pt;font-family:"Arial",sans-serif"> SIS-CFDPV1 <</span><span lang="EN-US"><a href="mailto:sis-cfdpv1-bounces@mailman.ccsds.org"><span style="font-size:9.0pt;font-family:"Arial",sans-serif">sis-cfdpv1-bounces@mailman.ccsds.org</span></a></span><span lang="EN-US" style="font-size:9.0pt;font-family:"Arial",sans-serif">>

<b>On Behalf Of </b>Wiegand, Robert E. (GSFC-5830) via SIS-CFDPV1<br>

<b>Sent:</b> Friday, October 6, 2023 5:09 PM<br>

<b>To:</b> </span><span lang="EN-US"><a href="mailto:sis-cfdpv1@mailman.ccsds.org"><span style="font-size:9.0pt;font-family:"Arial",sans-serif">sis-cfdpv1@mailman.ccsds.org</span></a></span><span lang="EN-US" style="font-size:9.0pt;font-family:"Arial",sans-serif"><br>

<b>Subject:</b> [SIS-CFDPV1] CFDP unbounded transfers</span><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif"><o:p></o:p></span></p>

</div>

</div>

<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:72.0pt">

<span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif"> <o:p></o:p></span></p>

<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:72.0pt">

<span lang="EN-US" style="font-size:10.0pt;font-family:"Arial",sans-serif">Greetings,<br>

<br>

I have a comment/question regarding unbounded file transfers.</span><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif"><o:p></o:p></span></p>

<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:72.0pt">

<span lang="EN-US" style="font-size:10.0pt;font-family:"Arial",sans-serif"> </span><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif"><o:p></o:p></span></p>

<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:72.0pt">

<span lang="EN-US" style="font-size:10.0pt;font-family:"Arial",sans-serif">CCSDS 727.0-B-5 says in Table 5-1: Fixed PDU Header Fields</span><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif"><o:p></o:p></span></p>

<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:72.0pt">

<span lang="EN-US" style="font-size:10.0pt;font-family:"Arial",sans-serif"> </span><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif"><o:p></o:p></span></p>

<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:72.0pt;text-autospace:none">

<span lang="EN-US" style="font-size:10.0pt;font-family:"Arial",sans-serif">… All files of unbounded size shall be flagged ‘large’…</span><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif"><o:p></o:p></span></p>

<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:72.0pt;text-autospace:none">

<span lang="EN-US" style="font-size:10.0pt;font-family:"Arial",sans-serif"> </span><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif"><o:p></o:p></span></p>

<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:72.0pt;text-autospace:none">

<span lang="EN-US" style="font-size:10.0pt;font-family:"Arial",sans-serif">If the sender can ensure the unbounded file being transferred will be of size < 4GB, why must the sender/receiver use FSS size 64 bits for all PDUs?<br>

<br>

Disadvantages:</span><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif"><o:p></o:p></span></p>

<p class="MsoListParagraph" style="margin-left:108.0pt;text-indent:-18.0pt;text-autospace:none">

<span lang="EN-US" style="font-size:10.0pt;font-family:ArialNarrow">-</span><span lang="EN-US" style="font-size:7.0pt;font-family:"Times New Roman",serif">        

</span><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial",sans-serif">each FDU 32 bits larger;</span><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif"><o:p></o:p></span></p>

<p class="MsoListParagraph" style="margin-left:108.0pt;text-indent:-18.0pt;text-autospace:none">

<span lang="EN-US" style="font-size:10.0pt;font-family:ArialNarrow">-</span><span lang="EN-US" style="font-size:7.0pt;font-family:"Times New Roman",serif">        

</span><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial",sans-serif">NAK sequence nearly doubles in size;</span><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif"><o:p></o:p></span></p>

<p class="MsoListParagraph" style="margin-left:108.0pt;text-indent:-18.0pt;text-autospace:none">

<span lang="EN-US" style="font-size:10.0pt;font-family:ArialNarrow">-</span><span lang="EN-US" style="font-size:7.0pt;font-family:"Times New Roman",serif">        

</span><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial",sans-serif">hardware/software built for 32 bit FSS cannot use unbounded file transfers</span><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif"><o:p></o:p></span></p>

<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:72.0pt;text-autospace:none">

<span lang="EN-US" style="font-size:10.0pt;font-family:"Arial",sans-serif"><br>

I am not seeing advantages that cannot be addressed without this constraint.</span><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif"><o:p></o:p></span></p>

<p class="MsoNormal" style="mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:12.0pt;margin-left:72.0pt;text-autospace:none">

<span lang="EN-US" style="font-size:10.0pt;font-family:"Arial",sans-serif"><br>

Any thoughts or explanation?</span><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif"><o:p></o:p></span></p>

<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:72.0pt;text-autospace:none">

<span lang="EN-US" style="font-size:10.0pt;font-family:"Arial",sans-serif">thank you</span><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif"><o:p></o:p></span></p>

<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:72.0pt;text-autospace:none">

<span lang="EN-US" style="font-size:10.0pt;font-family:"Arial",sans-serif">bob</span><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif"><o:p></o:p></span></p>

<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:72.0pt;text-autospace:none">

<span lang="EN-US" style="font-size:10.0pt;font-family:"Arial",sans-serif"> </span><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif"><o:p></o:p></span></p>

<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:72.0pt">

<span lang="EN-US" style="font-size:10.0pt;font-family:"Arial",sans-serif">--</span><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif"><o:p></o:p></span></p>

<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:72.0pt">

<span lang="EN-US" style="font-size:10.0pt;font-family:"Arial",sans-serif">Bob Wiegand</span><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif"><o:p></o:p></span></p>

<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:72.0pt">

<span lang="EN-US" style="font-size:10.0pt;font-family:"Arial",sans-serif">Ground Software Systems Branch</span><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif"><o:p></o:p></span></p>

<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:72.0pt">

<span lang="EN-US" style="font-size:10.0pt;font-family:"Arial",sans-serif">NASA/GSFC Code 583</span><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif"><o:p></o:p></span></p>

<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:72.0pt">

<span lang="EN-US" style="font-size:10.0pt;font-family:"Arial",sans-serif"> </span><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif"><o:p></o:p></span></p>

<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:72.0pt;text-autospace:none">

<span lang="EN-US" style="font-size:10.0pt;font-family:"Arial",sans-serif"> </span><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif"><o:p></o:p></span></p>

</div>

<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif">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 (<span lang="EN-US"><a href="mailto:dpo@esa.int"><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif">dpo@esa.int</a><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif">).

<o:p></o:p></span></p>

</div>

<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif"><o:p> </o:p></span></p>

</div>

</blockquote>

<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-GB" style="border:solid windowtext 1.0pt;padding:0cm"><img border="0" width="1" height="1" style="width:.0083in;height:.0083in" id="그림_x0020_1" src="cid:image002.jpg@01DA01E1.08BA56F0" alt="보낸 사람이 제거한 이미지입니다."></span><span lang="EN-GB"><o:p></o:p></span></p>

<p class="MsoNormal"><span lang="EN-GB" style="font-size:12.0pt;font-family:굴림">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).

<o:p></o:p></span></p>

</div>

</body>

</html>