<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:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
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;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle21
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle23
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle24
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.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:5324697;
mso-list-type:hybrid;
mso-list-template-ids:815011446 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;
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;
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;
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:809978205;
mso-list-type:hybrid;
mso-list-template-ids:1051361406 67698703 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l1:level1
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l1:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l1:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l2
{mso-list-id:1880046023;
mso-list-type:hybrid;
mso-list-template-ids:-1573634610 67698703 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l2:level1
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l2:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l2:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
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="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> Eddy, Wesley M. (GRC-LCI0)[MTI SYSTEMS, INC.] <br>
<b>Sent:</b> Wednesday, January 3, 2018 3:52 PM<br>
<b>To:</b> 'John Pietras' <john.pietras@gst.com><br>
<b>Cc:</b> Barkley, Erik J (JPL-3970)[Jet Propulsion Laboratory] <erik.j.barkley@jpl.nasa.gov>; Colin.Haddow@esa.int<br>
<b>Subject:</b> RE: Updated TGFT White Book on CWE<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Hi John, I took a look at your draft, and here are a few comments, questions, and typo catches on the TGFT book you posted. I copied Erik and Colin, but don’t know if this is something the rest of the working group would normally be interested
in, or if comments are typically just unicast to the book editors.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">First just a few easy typos:<o:p></o:p></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoNormal" style="mso-list:l0 level1 lfo1">page 14 (or 1-2), in list item b) bullet q. should "vent" be "event"?<o:p></o:p>
<ul style="margin-top:0in" type="circle">
<li class="MsoNormal" style="mso-list:l0 level2 lfo1">in list item c) should "Post Mission" be "Post-mission"?<o:p></o:p></li></ul>
</li><li class="MsoNormal" style="mso-list:l0 level1 lfo1">page 16 (or 1-4), in section 1.3.2, first paragraph, last sentence, "seem" should be "seen"<o:p></o:p></li><li class="MsoNormal" style="mso-list:l0 level1 lfo1">page 17 (or 1-5), in 2nd paragraph, "underlying TFGT" should be "underlying "TGFT"?<o:p></o:p></li><li class="MsoNormal" style="mso-list:l0 level1 lfo1">page 19 (or 1-7), in item h) "containg" should be "containing"<o:p></o:p></li><li class="MsoNormal" style="mso-list:l0 level1 lfo1">page 25 (or 3-1) in the first paragraph of 3.1 "Senderto" should be "Sender to"<o:p></o:p></li><li class="MsoNormal" style="mso-list:l0 level1 lfo1">page 28, the section title for 3.2 is jumbled somehow<o:p></o:p></li><li class="MsoNormal" style="mso-list:l0 level1 lfo1">bad reference in 3.2.1.1 part a)<o:p></o:p></li><li class="MsoNormal" style="mso-list:l0 level1 lfo1">page 31 (or 3-7), "deliveredwith" is missing a space and "paload" should be "payload"<o:p></o:p></li><li class="MsoNormal" style="mso-list:l0 level1 lfo1">page 34, in 4.2.5.2 "volumenInfo" looks like it has an extra n?<o:p></o:p></li></ul>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">More substantial thoughts/comments/questions:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<ol style="margin-top:0in" start="1" type="1">
<li class="MsoNormal" style="mso-list:l2 level1 lfo2">On page 27 (or 3-3) in the 2nd paragraph, I think the service provider/user terminology should more correctly be file sender/receiver (as the terminology is discussed earlier in the document).<o:p></o:p></li></ol>
<p class="MsoListParagraph"><o:p> </o:p></p>
<ol style="margin-top:0in" start="2" type="1">
<li class="MsoNormal" style="mso-list:l2 level1 lfo2">In section 1.8, why are TLS 1.0 and 1.1 references provided in addition to TLS 1.2? It wasn’t clear if there is some technical or practical reason. Both are obsoleted, and TLS 1.3 is going to be standardized
soon, so it's not clear why anything more than just 1.2 would make sense.<o:p></o:p></li></ol>
<p class="MsoNormal"><o:p> </o:p></p>
<ol style="margin-top:0in" start="3" type="1">
<li class="MsoNormal" style="mso-list:l2 level1 lfo2">Is TGFT only intended to work with HTTP 1.1 and not HTTP/2? maybe this is related to relying on WebDAV, since it's unclear if people are using these together yet in industry? Maybe this is something to
bookmark for future work, but not worry about now, since the software tooling available predominately supports 1.1 and it isn’t really obsolete yet?<o:p></o:p></li></ol>
<p class="MsoNormal"><o:p> </o:p></p>
<ol style="margin-top:0in" start="4" type="1">
<li class="MsoNormal" style="mso-list:l2 level1 lfo2">It probably doesn't matter much in practice as TGFT is envisioned to be used, but there may be some friction between use of "file" concepts in TGFT versus more generic concept of "resources" in HTTP. In
the HTTP server, the resources are often stored and managed as files, but definitely not always (e.g. in the case of REST applications, etc). I doubt this is a real issue for us at the moment, but maybe just a terminology question to think about, if perhaps
there is some use case where the XFDUs and contents are processed straight to/from database entries or something. That would be more like a typical REST application, and I guess TGFT is using HTTP and WebDAV for transport of XFDUs as files *<b>only</b>*,
and not really intended to fit into a REST-like architecture?<o:p></o:p></li></ol>
<p class="MsoNormal"><o:p> </o:p></p>
<ol style="margin-top:0in" start="5" type="1">
<li class="MsoNormal" style="mso-list:l2 level1 lfo2">For cross-system compatibility, TGFT limits the valid characters that can be used in the filename, but I didn't notice a limit on the length of a filename? It seems like there should be a limit on the number
of characters for similar compatibility reasons.<o:p></o:p></li></ol>
<p class="MsoNormal"><o:p> </o:p></p>
<ol style="margin-top:0in" start="6" type="1">
<li class="MsoNormal" style="mso-list:l2 level1 lfo2">Should there be a limit to the size of files and/or XFDUs? Maybe this is something for appendix A, in addition to the data volume already there?<o:p></o:p></li></ol>
<p class="MsoNormal"><o:p> </o:p></p>
<ol style="margin-top:0in" start="7" type="1">
<li class="MsoNormal" style="mso-list:l2 level1 lfo2">In 3.3, there is a suggestion to append a hash value within the filename with a colon separator, but the colon is illegal in filenames in some systems, and adding it could make the filename too long?<o:p></o:p></li></ol>
<p class="MsoNormal"><o:p> </o:p></p>
<ol style="margin-top:0in" start="8" type="1">
<li class="MsoNormal" style="mso-list:l2 level1 lfo2">Hash values or signatures can just be provided separately in files on the side, if needed. This is how it's done normally for large downloads on the Internet like Linux installation images, signed RPM files,
etc. I don’t think doing anything fancier (like embedding in the filename) adds value, and probably creates complexity.<o:p></o:p></li></ol>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> SMWG [<a href="mailto:smwg-bounces@mailman.ccsds.org">mailto:smwg-bounces@mailman.ccsds.org</a>]
<b>On Behalf Of </b>John Pietras<br>
<b>Sent:</b> Sunday, November 26, 2017 5:53 PM<br>
<b>To:</b> <a href="mailto:Colin.Haddow@esa.int">Colin.Haddow@esa.int</a><br>
<b>Cc:</b> CCSDS SMWG ML (<a href="mailto:smwg@mailman.ccsds.org">smwg@mailman.ccsds.org</a>) <<a href="mailto:smwg@mailman.ccsds.org">smwg@mailman.ccsds.org</a>><br>
<b>Subject:</b> [Smwg] Updated TGFT White Book on CWE<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Colin,<o:p></o:p></p>
<p class="MsoNormal">During the Fall 2017 CCSDS Workshop, I took the action to update the TGFT White Book in two specific areas:<o:p></o:p></p>
<ol style="margin-top:0in" start="1" type="1">
<li class="MsoNormal" style="mso-list:l1 level1 lfo3">To add my comments on the November 2016 version of the White Book to the latest (v0.2) version (taking into account intermediate revisions and changes in concepts)<o:p></o:p></li><li class="MsoNormal" style="mso-list:l1 level1 lfo3">To make the user/provider, sender/recipient, etc., terminology consistent throughout the book.<o:p></o:p></li></ol>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I have updated the white book, which I have posted at URL<o:p></o:p></p>
<p class="MsoNormal"><a href="https://cwe.ccsds.org/css/docs/CSS-SM/CWE%20Private%20-%20Beta/Book%20Production/Blue/Terrestrial%20Generic%20File%20Transfer/White%20Book/Drafts/Terrestrial%20Generic%20File%20Transfer%20927x1w0.02-JVP-171126.doc">https://cwe.ccsds.org/css/docs/CSS-SM/CWE%20Private%20-%20Beta/Book%20Production/Blue/Terrestrial%20Generic%20File%20Transfer/White%20Book/Drafts/Terrestrial%20Generic%20File%20Transfer%20927x1w0.02-JVP-171126.doc</a><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Besides the two categories of changes listed above, I also:<o:p></o:p></p>
<ol style="margin-top:0in" start="3" type="1">
<li class="MsoNormal" style="mso-list:l1 level1 lfo3">Consolidated all file naming requirements into section 3.2.1 (these had been spread out over several sections), and<o:p></o:p></li><li class="MsoNormal" style="mso-list:l1 level1 lfo3">Replaced “cross support service” as the user of TGFT with the more-general “application” so as to encompass not only CCSDS cross support services but Agency-unique or situation-specific uses of TGFT.<o:p></o:p></li></ol>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Best regards,<o:p></o:p></p>
<p class="MsoNormal">John<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>