[Smwg] TGFT UPDATE RESULTING FROM EMAIL "TGFT yellow book updates"

Ciocirlan Claudia Claudia.Ciocirlan at cnes.fr
Mon Feb 5 08:49:45 UTC 2018

Hi John,

Great, thanks for the updates. Now it is in line with the other documents.
I am also ok with all your answers to my previous email, thank you.

I went through your update and I am wondering. WebDAV is still present everywhere. For example is section 2.2 "With this in mind the protocol chosen for the TGFT is WebDAV."

In my comprehension WebDAV was no longer imposed, it was at least HTTPs with the possibility to use WebDAV if needed. Did I got it wrong?

Thank you and hear you tomorrow.

De : John Pietras [mailto:john.pietras at gst.com]
Envoyé : lundi 29 janvier 2018 15:29
À : Ciocirlan Claudia <Claudia.Ciocirlan at cnes.fr>; CCSDS SMWG ML (smwg at mailman.ccsds.org) <smwg at mailman.ccsds.org>
Objet : TGFT UPDATE RESULTING FROM EMAIL "TGFT yellow book updates"

Dear Claudia,
In updating the Tech Note diagram to use terminology consistently throughout the book, I accidentally switched the in-tray labels and I also mislabeled the files sources for files V and W. The correct diagram is this:

[cid:image001.png at 01D39E66.A6E5FEE0]

which is now consistent with your Yellow Book diagram if one assumes, for example, that file T = file V and the Agency B file recipient for file T simples turns the file around to send it back to Agency A.

I have updated the draft TGFT White Book to correct the figure and have posted it at URL:

Have you had a chance to look at the other changes that I made in response to your comments, and if so, did my responses satisfy your concerns? Thanks.

Finally, in thinking about the in-tray concept in which an "Agency" (more likely a given node of an Agency) conceptually has a single in-tray for all XFDU Packages from another "Agency", it occurs to me that if different applications (programs or human operators) set their own XFDU Package naming conventions on their own they might accidentally gravitate to conventions that are so simple that it is impossible to tell who the intended file recipient is from the file names in the in-trays. So even though the TGFT Blue Book doesn't establish any naming conventions beyond the limitations on the character set and the timetag convention for the XFDU Package, the SANA Considerations section of Annex C (which is currently To Be Written) should establish (or mandate the establishment of) a TGFT file naming convention registry to ensure that any application that uses TGFT uses file names that are unique to that application and cannot be confused for any other application.

Best regards,

From: SMWG [mailto:smwg-bounces at mailman.ccsds.org] On Behalf Of Ciocirlan Claudia
Sent: Thursday, January 25, 2018 5:26 AM
To: CCSDS SMWG ML (smwg at mailman.ccsds.org<mailto:smwg at mailman.ccsds.org>)
Subject: [Smwg] TGFT yellow book updates,

Hello all,

During the last TGFT splitter telecon I took one action to update the yellow book. One of the updates mentioned the image bellow.
I had to switch the   A in tray with the B in tray.

[cid:image002.png at 01D39E66.A6E5FEE0]

The problem is that this schema is based on the TGFT tech note Figure 2-1 and also specified in section 3.2.3 of the White Book
[cid:image003.png at 01D39E66.A6E5FEE0]

I propose to keep the yellow book as it is and only to update the presence of WebDAV; Is that ok with you? If not we need to update all the documents related to this concept.


Claudia Ciocirlan CNES/DNO/OP/SSO
Mission Operations Ground Segment
phone : +33 (0)5 61 28 17 11
email : claudia.ciocirlan at cnes.fr<mailto:claudia.ciocirlan at cnes.fr>
P Save a tree ! Think before printing


Not spam<https://filter.gst.com/canit/b.php?c=n&i=01V2yqdRR&m=a4b4368df320>
Forget previous vote<https://filter.gst.com/canit/b.php?c=f&i=01V2yqdRR&m=a4b4368df320>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.ccsds.org/pipermail/smwg/attachments/20180205/2f172bf4/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 87532 bytes
Desc: image001.png
URL: <http://mailman.ccsds.org/pipermail/smwg/attachments/20180205/2f172bf4/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 37718 bytes
Desc: image002.png
URL: <http://mailman.ccsds.org/pipermail/smwg/attachments/20180205/2f172bf4/attachment-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.png
Type: image/png
Size: 72058 bytes
Desc: image003.png
URL: <http://mailman.ccsds.org/pipermail/smwg/attachments/20180205/2f172bf4/attachment-0002.png>

More information about the SMWG mailing list