<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=iso-8859-1">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@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:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Georgia;
panose-1:2 4 5 2 5 4 5 2 3 3;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
{font-family:ArialMT;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
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.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Plain Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:Consolas;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
span.TextebrutCar
{mso-style-name:"Texte brut Car";
mso-style-priority:99;
mso-style-link:"Texte brut";
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
p.Textebrut, li.Textebrut, div.Textebrut
{mso-style-name:"Texte brut";
mso-style-link:"Texte brut Car";
margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
span.EmailStyle24
{mso-style-type:personal;
font-family:"Georgia","serif";
color:windowtext;}
span.EmailStyle25
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.begin-antispam-voting-links
{mso-style-name:begin-antispam-voting-links;}
span.end-antispam-voting-links
{mso-style-name:end-antispam-voting-links;}
span.EmailStyle28
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.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:1285769118;
mso-list-type:hybrid;
mso-list-template-ids:-561463656 67895297 67895311 67895301 67895297 67895299 67895301 67895297 67895299 67895301;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level2
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l1
{mso-list-id:1404068167;
mso-list-type:hybrid;
mso-list-template-ids:2112642568 67895297 67895299 67895301 67895297 67895299 67895301 67895297 67895299 67895301;}
@list l1:level1
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l1:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l1:level3
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l1:level4
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l1:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l1:level6
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l1:level7
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l1:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l1:level9
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
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="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal"><span style="color:#1F497D">Dear Claudia,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Thank you for the comments on the TGFT and TGFT XFDU. My responses are limited to your comments on XFDU-related items, and are interleaved below in
</span><span style="color:red">red</span><span style="color:#1F497D">.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Best regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">John<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> Ciocirlan Claudia [mailto:Claudia.Ciocirlan@cnes.fr]
<br>
<b>Sent:</b> Wednesday, July 19, 2017 11:32 AM<br>
<b>To:</b> Barkley, Erik J (3970); Colin Haddow/esoc/ESA; John Pietras<br>
<b>Cc:</b> CCSDS Service Mgmt WG<br>
<b>Subject:</b> TGFT comments and Actions <o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span lang="FR" style="color:#1F497D">Hello, </span><span lang="FR"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="FR" style="color:#1F497D"> </span><span lang="FR"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">You may find in the document attached a set of questions directly linked to the white note. Maybe some of those questions were already addressed but I do not have all the context and the history.
</span><span lang="FR"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><span lang="FR"><o:p></o:p></span></p>
<p class="MsoNormal"><b><u><span style="color:#1F497D">AI 2017-0512-45 XSD verification</span></u></b><span lang="FR"><o:p></o:p></span></p>
<p class="MsoPlainText"><span style="color:#1F497D">When “exploring” the zip file provided by John : XFDU_in_TGFT_TechNote-v0x5_Package-2017-137T16-46-00Z (3).ZIP</span><span lang="FR"><o:p></o:p></span></p>
<p class="MsoPlainText"><span style="color:#1F497D">The file XFDU_in_TGFT_TechNote-v0x5.xml does not respect the schema provided.
</span><span lang="FR"><o:p></o:p></span></p>
<p class="MsoPlainText"><span style="color:#1F497D">It seems that the declaration of the attribute maxOccurs (. "maxOccurs="unbounded"" ) is missing in TGFTXFDUschema.xsd, line 419. This is useful in order to allow the declaration of multiple dataObject in
the dataObjectSection (the default value is 1).</span><o:p></o:p></p>
<p class="MsoPlainText"><span lang="FR" style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoPlainText"><b><span lang="FR" style="color:red">Thank you very much for discovering this omission</span></b><span lang="FR" style="color:red">. We had decided to allow multiple dataObjects in the previous review cycle, but I had failed to update
the schema in this respect. Also, the diagram in the Tech Note itself had not been updated. I have uploaded a new zipped XFDU Package to the CWE that contains the correct schema file and Tech Note :</span><span style="color:#1F497D"> <o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="FR"><a href="https://cwe.ccsds.org/css/docs/CSS-SM/CWE%20Private%20-%20Beta/Tech%20Note%20Development/XFDU%20in%20TGFT%20Tech%20Note/XFDU_in_TGFT_TechNote-v0x6_Package-2017-256T19-40-00Z.zip">https://cwe.ccsds.org/css/docs/CSS-SM/CWE%20Private%20-%20Beta/Tech%20Note%20Development/XFDU%20in%20TGFT%20Tech%20Note/XFDU_in_TGFT_TechNote-v0x6_Package-2017-256T19-40-00Z.zip</a><o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="FR"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span style="color:#1F497D"> </span><span lang="FR"><o:p></o:p></span></p>
<p class="MsoPlainText"><b><u><span style="color:#1F497D">White book remarks/questions</span></u></b><span lang="FR"><o:p></o:p></span></p>
<p class="MsoPlainText"><span style="color:#1F497D">In the chapter 1.3.1.2 the CFDP metadata is addressed. Do we have any inputs for this kind of metadata and imagine how we are going to encapsulate it in TGFT?</span><span lang="FR"><o:p></o:p></span></p>
<p class="MsoPlainText"><span style="color:#1F497D"> </span><span lang="FR"><o:p></o:p></span></p>
<p class="MsoPlainText"><span style="color:#1F497D">Which is the final status of using or not using PROPFIND? And which are the errors and the states that we should manage by TGFT?</span><span lang="FR"><o:p></o:p></span></p>
<p class="MsoPlainText"><span style="color:#1F497D"> </span><span lang="FR"><o:p></o:p></span></p>
<p class="MsoPlainText"><span style="color:#1F497D">File naming:</span><span lang="FR"><o:p></o:p></span></p>
<p class="MsoPlainText"><span style="color:#1F497D">Using the naming convention containing the date of the beginning of the upload raises several questions:</span><span lang="FR"><o:p></o:p></span></p>
<p class="MsoPlainText" style="margin-left:.5in;text-indent:-.25in;mso-list:l1 level1 lfo2">
<![if !supportLists]><span lang="FR" style="font-family:Symbol"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="color:#1F497D">it might be a risk if the suffix is not synced or if is added by hand. This means that we have to manage the possibility that the same file name is used twice.
</span><span lang="FR"><o:p></o:p></span></p>
<p class="MsoPlainText" style="margin-left:.5in;text-indent:-.25in;mso-list:l1 level1 lfo2">
<![if !supportLists]><span lang="FR" style="font-family:Symbol"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="color:#1F497D">Is there a special meaning if a file is already present but with a different date? If I understand it well the previous file is kept and there is no meaning or link between 2 files with the same name
and a different date. </span><span lang="FR"><o:p></o:p></span></p>
<p class="MsoPlainText" style="margin-left:.25in"><span style="color:#1F497D"> </span><span lang="FR"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:ArialMT;color:#1F497D"> </span><span lang="FR"><o:p></o:p></span></p>
<p class="MsoNormal"><b><u><span style="font-size:10.0pt;font-family:ArialMT;color:#1F497D">TGFT tech note</span></u></b><span lang="FR"><o:p></o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:ArialMT;color:#1F497D"> </span></b><span lang="FR"><o:p></o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span style="font-size:10.0pt;font-family:ArialMT;color:#1F497D">The usage of provider and user is ambiguous. In the white book the provider is the one that holds the file to be transferred and the user is the
receiver. In the tech note the provider and the user are employed while talking about services or physical ground elements. The white book provider and user are replaced by provider/sender, provider/receiver, user/sender, and user/receiver This makes the comprehension
pretty hard.</span><span lang="FR"><o:p></o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span style="font-size:10.0pt;font-family:ArialMT;color:#1F497D"> </span><span lang="FR"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:ArialMT;color:#1F497D">In the 3.2.6.6.1
</span><span lang="FR"><o:p></o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span style="font-size:10.0pt;font-family:ArialMT;color:#1F497D">“If the TGFT-using service has service-specific metadata that is applicable to individual Content Units, the serviceSpecficContentUnitExtextension
element of the tgftContentUnitExtension element shall contain an instanceof a data type that contains that metadata »</span><span lang="FR"><o:p></o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span style="font-size:10.0pt;font-family:ArialMT;color:#1F497D">The service we are talking about is the service provided by tgft or the service as is defined by the tech note ?
</span><span style="font-size:10.0pt;font-family:ArialMT"><o:p></o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span lang="FR" style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span lang="FR" style="color:red">Yes, we can all agree that the terminology is not as easy as we would like it to be. In section 2 of the Tech Note, I tried to establish the disctinction between
<i>TGFT</i> and the <i>services that use TGFT</i>, such as offline tracking data delivery service, forward file service (in which files are transferred via TGFT to a ground station, which subsequenctly transmits the file when the space link to the target spacecraft
is available), return file service (in which data recevied from a spacecraft by a ground station is delivered to a Mission facility [e.g., a MOC] at some later time), etc.
<o:p></o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span lang="FR" style="color:red"><o:p> </o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span lang="FR" style="color:red">So in section 3.2.6.6.1 of the Tech Note, the reference to ‘service’ is to a service that uses TGFT. These extension types are ones that only make sense on the context of a specific
service that uses TGFT. For example, an XFDU for the Forward File service could contain not only the file to be delivered to the target spacecraft, but also metadata that specify the conditions under which the file is to be transmitted (e.g., earliestAllowedTransmissionDate/Time,
latestAllowedTransmissionDate/Time).<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><span lang="FR"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><span lang="FR"><o:p></o:p></span></p>
<p class="MsoNormal"><b><u><span style="color:#1F497D">Global questions and remarks</span></u></b><span lang="FR"><o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo4"><![if !supportLists]><span lang="FR" style="font-family:Symbol"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="color:#1F497D">The user side usage<br>
we say that the provider needs a standard webdav client, but nothing is said for the user side.
</span><span lang="FR"><o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo4"><![if !supportLists]><span lang="FR" style="font-family:Symbol"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="color:#1F497D">Error cases<br>
The simple errors seem well described in the 3.1.2 chapter but nothing is said if problems like hardware crash or network crashes occur?<br>
Is it possible to clean the possible temporary webdav files without an impact on the others transfers to be made?<br>
May we have a risk of incoherence between the webdav view (operation completed) and the provider point of view (operation cancelled)?</span><span lang="FR"><o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo4"><![if !supportLists]><span lang="FR" style="font-family:Symbol"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="color:#1F497D">Date suffix</span><span lang="FR"><o:p></o:p></span></p>
<p class="MsoListParagraph"><span style="color:#1F497D">The arguments and the semantic may be better argued
<br>
For example what happens if a service user defines 2 servers (a master and a slave one) with the policy to transfer on both servers. The send files must have the same date suffix on both servers, or do we need to use the real transfer starting date on each
server?<br>
Is the date only used for avoiding overwrite, of is the date also used to version a file? Normally this is only to avoid collisions, but in that case we can use any sort of discriminant, like an index and ask to the service provider to guaranty the unicity
of this index. <br>
</span><span style="color:red">These are very good points for discussion.</span><span lang="FR"><o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo4"><![if !supportLists]><span lang="FR" style="font-family:Symbol"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="color:#1F497D">Cleaning policy<br>
Nothing is said on the cleaning matter. <br>
for example how is this scenario managed?</span><span lang="FR"><o:p></o:p></span></p>
<p class="MsoListParagraph" style="margin-left:1.0in;text-indent:-.25in;mso-list:l0 level2 lfo4">
<![if !supportLists]><span lang="FR"><span style="mso-list:Ignore">1.<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="color:#1F497D">SPA send a a file </span>
<span lang="FR" style="font-size:10.0pt;font-family:ArialMT;color:#1F497D">fichier.ext-2017-200T12:00:00Z</span><span lang="FR"><o:p></o:p></span></p>
<p class="MsoListParagraph" style="margin-left:1.0in;text-indent:-.25in;mso-list:l0 level2 lfo4">
<![if !supportLists]><span lang="FR"><span style="mso-list:Ignore">2.<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="color:#1F497D">WebDAV makes the transfer but the connection is lost before sending the ack</span><span lang="FR"><o:p></o:p></span></p>
<p class="MsoListParagraph" style="margin-left:1.0in;text-indent:-.25in;mso-list:l0 level2 lfo4">
<![if !supportLists]><span lang="FR"><span style="mso-list:Ignore">3.<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="color:#1F497D">SUB sees the file and uses it but still lets it on the server</span><span lang="FR"><o:p></o:p></span></p>
<p class="MsoListParagraph" style="margin-left:1.0in;text-indent:-.25in;mso-list:l0 level2 lfo4">
<![if !supportLists]><span lang="FR"><span style="mso-list:Ignore">4.<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="color:#1F497D">SPA tries to resend the file and uses the same date</span><span lang="FR"><o:p></o:p></span></p>
<p class="MsoListParagraph" style="margin-left:1.0in;text-indent:-.25in;mso-list:l0 level2 lfo4">
<![if !supportLists]><span lang="FR"><span style="mso-list:Ignore">5.<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="color:#1F497D">SUB decides to delete the file (while SPA sill transfers it for the second time)…</span><span lang="FR"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><span lang="FR"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Thanks,</span><span lang="FR"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Claudia</span><span lang="FR"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><span lang="FR"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><span lang="FR"><o:p></o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span lang="FR" style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">De :</span></b><span lang="FR" style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> Barkley, Erik J (3970) [</span><a href="mailto:erik.j.barkley@jpl.nasa.gov"><span lang="FR" style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">mailto:erik.j.barkley@jpl.nasa.gov</span></a><span lang="FR" style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">]
<br>
<b>Envoyé :</b> mercredi 19 juillet 2017 01:51<br>
<b>À :</b> Ciocirlan Claudia<br>
<b>Cc :</b> CCSDS Service Mgmt WG<br>
<b>Objet :</b> Response to AI re TGFT file types </span><span lang="FR"><o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><span lang="FR"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Georgia","serif"">Hello Claudia,</span><span lang="FR"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Georgia","serif""> </span><span lang="FR"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Georgia","serif"">I was able to locate the attached file on my computer from the October 2013 San Antonio meeting. This was input to what was then the file transfer BOF. The list of file types
is in the first table that starts on page 1 of the attached document. </span><span lang="FR"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Georgia","serif""> </span><span lang="FR"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Georgia","serif"">Best regards,</span><span lang="FR"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Georgia","serif"">-Erik</span><span lang="FR"><o:p></o:p></span></p>
</div>
</body>
</html>