<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: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;}
/* 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";}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:"Calibri","sans-serif";}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";}
@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:1567914352;
mso-list-type:hybrid;
mso-list-template-ids:355635620 67698689 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:1.0in;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:1.5in;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:2.0in;
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;
margin-left:2.5in;
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;
margin-left:3.0in;
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;
margin-left:3.5in;
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;
margin-left:4.0in;
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;
margin-left:4.5in;
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;
margin-left:5.0in;
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="MsoPlainText">A few comments on the book:<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Section 1.2.2 (Scope) states:<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:.5in">"...whereby a file may be delivered by the TFT along with metadata that enables the files to be injected into a CCSDS File Transfer Protocol (CFDP, see Refs. [1]and [2]) entity."<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:.5in"><o:p> </o:p></p>
<p class="MsoPlainText" style="margin-left:.5in">OK, I haven't read past here yet<span style="color:red">*</span>, but I suspect that the 'metadata' really wants to be part of the file as far as the underlying file transfer mechanism is concerned. That is,
the 'application' in this example is "send a file that can then be forwarded via CFDP". Two points:<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:.5in"><o:p> </o:p></p>
<p class="MsoPlainText" style="margin-left:1.0in;text-indent:-.25in;mso-list:l0 level1 lfo1">
<![if !supportLists]><span style="font-family:Symbol"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]>I think the 'real' implementation for this example should be and end-to-end CFDP file transfer over the BP network protocol.<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:1.0in;text-indent:-.25in;mso-list:l0 level1 lfo1">
<![if !supportLists]><span style="font-family:Symbol"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]>If we're intent on using something like SFTP on the ground, let's keep all the metadata WITH the file. For instance, one could define some sort of extensible header information to be placed at the front of the file data.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">I don’t think the CFDP Green Book can be a normative reference from a Magenta book (or at least I don’t think it makes sense to do so).<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Section 2.6.2.3 – Directory Names<o:p></o:p></p>
<p class="MsoPlainText">Why not put the wrappter_file.FILE_TYPE (labelled wrapper_file.xxx in figure 2-2) in the wrapper_file directory? Or is the figure supposed to be showing two options, one where there’s just the one file that would unwrap into cwd and
one where there are multiple attachments (including the ‘base’ file?) that would unwrap into a directory?<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<div style="mso-element:para-border-div;border:none;border-bottom:solid windowtext 1.0pt;padding:0in 0in 1.0pt 0in;margin-left:.5in;margin-right:0in">
<p class="MsoPlainText" style="text-indent:.5in;border:none;padding:0in">--keith<o:p></o:p></p>
<p class="MsoPlainText" style="text-indent:.5in;border:none;padding:0in"><o:p> </o:p></p>
<p class="MsoPlainText" style="text-indent:.5in;border:none;padding:0in"><o:p> </o:p></p>
</div>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoNormal"><span style="color:red">* EXCELLENT! </span>Section 2.6 “In view of this it is suggested that each delivery of a file or files is accompanied by a manifest file that contains the metadata relevant to the file or files being delivered and
that this manifest file and the data file(s) are “wrapped” into one file.” is exactly what I was looking for! THANKS! [OK, on further inspection you’re essentially taring or zipping the manifest file together with the actual file? Maybe not how I was thinking
of it, but fine.]<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoPlainText"><o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">-----Original Message-----<br>
From: css-gft-bounces@mailman.ccsds.org [mailto:css-gft-bounces@mailman.ccsds.org] On Behalf Of Colin.Haddow@esa.int<br>
Sent: Thursday, July 10, 2014 12:43 PM<br>
To: smwg@mailman.ccsds.org; css-gft@mailman.ccsds.org<br>
Cc: Nestor.Peccia@esa.int<br>
Subject: [CSS-GFT] Terrestrial File Transfer - Concept Book Update</p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Dear all,<o:p></o:p></p>
<p class="MsoPlainText"> I've update the Terrestrial File Transfer Concept book draft and uploaded this to CWE where you can find it at the following URL.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"><a href="http://cwe.ccsds.org/css/docs/CSS-SM/CWE%20Private/Terrestrial%20File%20Transfer%20-%20Concept%20Book/File%20Transfer%20Concept%20NNNxNN-g0.03.doc"><span style="color:windowtext;text-decoration:none">http://cwe.ccsds.org/css/docs/CSS-SM/CWE%20Private/Terrestrial%20File%20Transfer%20-%20Concept%20Book/File%20Transfer%20Concept%20NNNxNN-g0.03.doc</span></a><o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Note that since the discussions at Noordwijkerhout this now falls under the Cross Support Service Area - Service Management (CSS-SM) Working group. I've therefore sent this e-mail to both the SMWG (i.e. CSS-SM) and CSS-GFTS (i.e.<o:p></o:p></p>
<p class="MsoPlainText">the BoF) mailing list.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Currently I'm not sure what the best thing to do with the mailing lists is as I'm fairly sure that not everybody who is interested in File Transfer is going to be interested in all the other aspects of Service management (exciting though
those are..) and possibly vice versa. In view of this it may be useful to maintain the CSS-GFTS mailing list for File Transfer issues.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Cheers for now,<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Colin<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">---------------------------------------------------------------------------------------------------------<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Dr. Colin R. Haddow,<o:p></o:p></p>
<p class="MsoPlainText">HSO-GI, European Space Agency,<o:p></o:p></p>
<p class="MsoPlainText">European Space Operations Centre,<o:p></o:p></p>
<p class="MsoPlainText">Robert-Bosch-Str 5,<o:p></o:p></p>
<p class="MsoPlainText">64293 Darmstadt,<o:p></o:p></p>
<p class="MsoPlainText">Germany.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Phone; +49 6151 90 2896<o:p></o:p></p>
<p class="MsoPlainText">Fax; +49 6151 90 3010<o:p></o:p></p>
<p class="MsoPlainText">E-Mail; <a href="mailto:colin.haddow@esa.int"><span style="color:windowtext;text-decoration:none">colin.haddow@esa.int</span></a><o:p></o:p></p>
<p class="MsoPlainText">---------------------------------------------------------------------------------------------------------<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">This message and any attachments are intended for the use of the addressee or addressees only.<o:p></o:p></p>
<p class="MsoPlainText">The unauthorised disclosure, use, dissemination or copying (either in whole or in part) of its content is not permitted.<o:p></o:p></p>
<p class="MsoPlainText">If you received this message in error, please notify the sender and delete it from your system.<o:p></o:p></p>
<p class="MsoPlainText">Emails can be altered and their integrity cannot be guaranteed by the sender.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Please consider the environment before printing this email.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">_______________________________________________<o:p></o:p></p>
<p class="MsoPlainText">CSS-GFT mailing list<o:p></o:p></p>
<p class="MsoPlainText"><a href="mailto:CSS-GFT@mailman.ccsds.org"><span style="color:windowtext;text-decoration:none">CSS-GFT@mailman.ccsds.org</span></a><o:p></o:p></p>
<p class="MsoPlainText"><a href="http://mailman.ccsds.org/cgi-bin/mailman/listinfo/css-gft"><span style="color:windowtext;text-decoration:none">http://mailman.ccsds.org/cgi-bin/mailman/listinfo/css-gft</span></a><o:p></o:p></p>
</div>
</body>
</html>