<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=utf-8">
<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:"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: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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",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;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
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:12.0pt;
font-family:"Times New Roman",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:12.0pt;
font-family:"Times New Roman",serif;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Georgia",serif;
color:#1F497D;}
.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:1814323607;
mso-list-type:hybrid;
mso-list-template-ids:-1750404224 1011111964 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
{mso-level-number-format:roman-upper;
mso-level-text:"%1\)";
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:.75in;
text-indent:-.5in;}
@list l0:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0: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"><span style="font-family:"Georgia",serif;color:#1F497D">Hello Holger,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia",serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia",serif;color:#1F497D">I have completed my review of the FF-CSTS book. It is quite an impressive document! Especially so, considering that it was developed quite quickly. I think the document is in quite
good shape but I think there is some relatively minor update required before proceeding to polling for agency review – please see the document with my comments in the CWE --
<a href="https://cwe.ccsds.org/css/docs/CSS-CSTS/CWE%20Private/Future%20Services%20using%20Toolkit/Forward%20Frame%20CSTS/FF-CSTS-922x3-r-0_11-for_AD_review-comments-eb.doc">
https://cwe.ccsds.org/css/docs/CSS-CSTS/CWE%20Private/Future%20Services%20using%20Toolkit/Forward%20Frame%20CSTS/FF-CSTS-922x3-r-0_11-for_AD_review-comments-eb.doc</a><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia",serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia",serif;color:#1F497D">I do have one general question -- do you and or the working group think that the FF-CSTS book as currently written, will retire the EFCLTU book (in its entirety)?
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia",serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia",serif;color:#1F497D">I look forward to the responses and any updates with regard to the comments and I think once that is done we can very likely move forward to requesting an agency review.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia",serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia",serif;color:#1F497D">Best regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia",serif;color:#1F497D">-Erik<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia",serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia",serif;color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia",serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> Holger.Dreihahn@esa.int <Holger.Dreihahn@esa.int>
<br>
<b>Sent:</b> Monday, June 18, 2018 11:37 PM<br>
<b>To:</b> Barkley, Erik J (3970) <erik.j.barkley@jpl.nasa.gov><br>
<b>Cc:</b> Colin.Haddow@esa.int; CCSDS_CSTSWG <css-csts@mailman.ccsds.org>; John Pietras <john.pietras@gst.com>; Wolfgang Hell <wo_._he@t-online.de><br>
<b>Subject:</b> RE: Draft Red FF book on CWE<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif">Hi Erik and John,</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">I think John summarizes quite nicely the position of the CSTS WG as discussed in Gaithersburg (yes, saves some typing :-). However, since the CSTS SFW should contain soon all changes required for
CSTS FF I wanted to talk to Wolfgang, back in July, when he thinks the updates can be done and how close we are to a SFW B-2 ready for AD review and submission to secretariat for Agency Review. As far as I had understood, the current changes to the SFW impact
mostly the forward procedures, which justifies the prototyping approach (SFW covered by FF prototyping). For SFW updates impacting return procedures we have to be a little bit careful to</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif"> a) not impact TD (as far as we can)</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif"> b) avoid the need of prototyping again the SFW return procedures, which is not covered yet by anything</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">I have (had) the hope that we could reach these two conditions for the SFW and even more, that it would be perhaps possible to go down the route Erik outlines, namely to pass the SFW also for review
relatively soon. Clearly we can then prioritize the FF over the SFW.</span> <br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">What I always have in mind is that we must by all means work on the Functional Resources. Currently I believe they are not completed to an extent that allows an MD implementation.</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Best regards,</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Holger</span> <br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Holger Dreihahn<br>
European Spacecraft Operations Centre | European Space Agency | S-431<br>
+49 6151 90 2233 | </span><a href="http://www.esa.int/esoc"><span style="font-size:10.0pt;font-family:"Arial",sans-serif">http://www.esa.int/esoc</span></a>
<br>
<br>
<br>
<br>
<span style="font-size:7.5pt;font-family:"Arial",sans-serif;color:#5F5F5F">From: </span><span style="font-size:7.5pt;font-family:"Arial",sans-serif">"Barkley, Erik J (3970)" <<a href="mailto:erik.j.barkley@jpl.nasa.gov">erik.j.barkley@jpl.nasa.gov</a>></span>
<br>
<span style="font-size:7.5pt;font-family:"Arial",sans-serif;color:#5F5F5F">To: </span><span style="font-size:7.5pt;font-family:"Arial",sans-serif">John Pietras <<a href="mailto:john.pietras@gst.com">john.pietras@gst.com</a>>, "<a href="mailto:Holger.Dreihahn@esa.int">Holger.Dreihahn@esa.int</a>"
<<a href="mailto:Holger.Dreihahn@esa.int">Holger.Dreihahn@esa.int</a>></span> <br>
<span style="font-size:7.5pt;font-family:"Arial",sans-serif;color:#5F5F5F">Cc: </span><span style="font-size:7.5pt;font-family:"Arial",sans-serif">CCSDS_CSTSWG <<a href="mailto:css-csts@mailman.ccsds.org">css-csts@mailman.ccsds.org</a>>, "<a href="mailto:Colin.Haddow@esa.int">Colin.Haddow@esa.int</a>"
<<a href="mailto:Colin.Haddow@esa.int">Colin.Haddow@esa.int</a>></span> <br>
<span style="font-size:7.5pt;font-family:"Arial",sans-serif;color:#5F5F5F">Date: </span><span style="font-size:7.5pt;font-family:"Arial",sans-serif">19/06/2018 04:04</span>
<br>
<span style="font-size:7.5pt;font-family:"Arial",sans-serif;color:#5F5F5F">Subject: </span><span style="font-size:7.5pt;font-family:"Arial",sans-serif">RE: Draft Red FF book on CWE</span>
<o:p></o:p></p>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="2" width="100%" noshade="" style="color:#A0A0A0" align="center">
</div>
<p class="MsoNormal"><br>
<br>
<br>
<span style="font-family:"Georgia",serif;color:#004080">John,</span> <br>
<span style="font-family:"Georgia",serif;color:#004080"> </span> <br>
<span style="font-family:"Georgia",serif;color:#004080">Thanks for the inputs, background. I certainly am aware of the priorities that NASA has expressed with regard to FF CSTS. We have TD CSTS which will likely be going forward for blue book publication
consideration as soon as the prototyping completes and I would very much not like to have this upset by changes to the framework (probably slim-to-none chance of that as no doubt the FF CSTS supporting changes affect the forward side of the framework only?
). In any case, I still look forward to hearing what Holger has to say – perhaps you have saved him some typing :-) </span>
<br>
<span style="font-family:"Georgia",serif;color:#004080"> </span> <br>
<span style="font-family:"Georgia",serif;color:#004080">Best regards,</span> <br>
<span style="font-family:"Georgia",serif;color:#004080">-Erik</span> <br>
<span style="font-family:"Georgia",serif;color:#004080"> </span> <br>
<b><span style="font-family:"Calibri",sans-serif">From:</span></b><span style="font-family:"Calibri",sans-serif"> John Pietras <<a href="mailto:john.pietras@gst.com">john.pietras@gst.com</a>>
<b><br>
Sent:</b> Monday, June 18, 2018 6:27 PM<b><br>
To:</b> Barkley, Erik J (3970) <<a href="mailto:erik.j.barkley@jpl.nasa.gov">erik.j.barkley@jpl.nasa.gov</a>>;
<a href="mailto:Holger.Dreihahn@esa.int">Holger.Dreihahn@esa.int</a><b><br>
Cc:</b> CCSDS_CSTSWG <<a href="mailto:css-csts@mailman.ccsds.org">css-csts@mailman.ccsds.org</a>><b><br>
Subject:</b> RE: Draft Red FF book on CWE</span> <br>
<br>
<span style="font-family:"Calibri",sans-serif;color:#004080">Erik,</span> <br>
<span style="font-family:"Calibri",sans-serif;color:#004080">If I can offer some thoughts, I believe that I can address the WG’s position on this. Of course, if I’ve misunderstood something I’m sure that Holger can set the record straight.
</span><br>
<span style="font-family:"Calibri",sans-serif;color:#004080"> </span> <br>
<span style="font-family:"Calibri",sans-serif;color:#004080">First, we did (and do) have the understanding that getting the FF book published is a very high priority, at least for NASA. We are hoping to have the F Red-1 review completed and the RID resolutions
determined (that is, know the answers even if they aren’t updated in the book itself) by 31 December, on a path to get a Blue-1 in the summer of 2019. We were concerned that delaying the review of the FF book until both it and the updated SFW can get through
the Secretariat editing process and have both of them formally reviewed simultaneously could seriously jeopardize that schedule. We thought maybe you (and maybe Peter) could pull some strings to bump up the priority in the Secretariat’s queue for the FF book,
but didn’t want to push our luck with doing that for 2 books. Throw August slowdown in the middle of all of this and you can see our motivation for focusing as narrowly as we could justifiably get away with.</span>
<br>
<span style="font-family:"Calibri",sans-serif;color:#004080"> </span> <br>
<span style="font-family:"Calibri",sans-serif;color:#004080">Second, although we are quite confident that the current draft SFW Pink Book addresses the issues raised by the FF book in the procedures most directly associated with the FF services, there may be
some residual “echoes” that affect other procedures in the book. Due to our focus on supporting the progression of the FF book, the focus on the SFW draft Pink Book has been primarily on those FF-related procedures. There is also the issue of re-prototyping
the other procedures that have been affects, for which the current thinking is that the WG can do some regression testing of the changes with the other CSTSes (MD and TD) that use them.
</span><br>
<span style="font-family:"Calibri",sans-serif;color:#004080"> </span> <br>
<span style="font-family:"Calibri",sans-serif;color:#004080">So the approach that we WG developed in Gaithersburg was as follows:</span>
<br>
<span style="font-family:"Calibri",sans-serif;color:#004080">1. Get the SFW draft Pink Book to a point where it accurately reflects the current thinking, and matches and supports the FF book.</span>
<br>
<span style="font-family:"Calibri",sans-serif;color:#004080">2. Make the SFW *<b>informal draft</b>* Pink Book available *<b>as a review aid</b>* for the FF Red-1 review. Perhaps by posting it to the public folder of the CSTSWG CWE. We could even informally
solicit comments on the SFW changes in case anyone wishes to offer them.</span> <br>
<span style="font-family:"Calibri",sans-serif;color:#004080">3. While the FF Red-1 review is underway (e.g., late summer into fall), work more on the SFW Pink Book, ideally to the point where it could be ready for submission the Secretariat. However,
depending on the actual timing of the FF red-1 book review completion and the process of completion of the SFW Pink Book generation, the WG might decide to wait to see if any of the FF review comments are significant enough to ripple back into the SFW itself.</span>
<br>
<span style="font-family:"Calibri",sans-serif;color:#004080">4. Conduct the formal CCSDS review of the SFW Pink Book while the FF book is being updated to Blue-1 (hopefully) or Red-2. In any case, the goal would be to have an approved Blue-2 SFW in the
next spring/summer timeframe, ready to support Blue-1 FF if we are fortunate enough to be able to go directly to FF Blue-1.
</span><br>
<span style="font-family:"Calibri",sans-serif;color:#004080"> </span> <br>
<span style="font-family:"Calibri",sans-serif;color:#004080">Peter Shames was in the room with us when we discussed this and he thought it was a good approach.</span>
<br>
<span style="font-family:"Calibri",sans-serif;color:#004080"> </span> <br>
<span style="font-family:"Calibri",sans-serif;color:#004080">Holger, have a done a reasonably good job of summarizing our approach?</span>
<br>
<span style="font-family:"Calibri",sans-serif;color:#004080"> </span> <br>
<span style="font-family:"Calibri",sans-serif;color:#004080">Best regards,</span>
<br>
<span style="font-family:"Calibri",sans-serif;color:#004080">John</span> <br>
<span style="font-family:"Calibri",sans-serif;color:#004080"> </span> <br>
<b><span style="font-family:"Calibri",sans-serif">From:</span></b><span style="font-family:"Calibri",sans-serif"> CSS-CSTS [</span><a href="mailto:css-csts-bounces@mailman.ccsds.org"><span style="font-family:"Calibri",sans-serif">mailto:css-csts-bounces@mailman.ccsds.org</span></a><span style="font-family:"Calibri",sans-serif">]
<b>On Behalf Of </b>Barkley, Erik J (3970)<b><br>
Sent:</b> Monday, June 18, 2018 8:00 PM<b><br>
To:</b> </span><a href="mailto:Holger.Dreihahn@esa.int"><span style="font-family:"Calibri",sans-serif">Holger.Dreihahn@esa.int</span></a><b><span style="font-family:"Calibri",sans-serif"><br>
Cc:</span></b><span style="font-family:"Calibri",sans-serif"> CCSDS_CSTSWG <</span><a href="mailto:css-csts@mailman.ccsds.org"><span style="font-family:"Calibri",sans-serif">css-csts@mailman.ccsds.org</span></a><span style="font-family:"Calibri",sans-serif">><b><br>
Subject:</b> Re: [Css-csts] Draft Red FF book on CWE</span> <br>
<br>
<span style="font-family:"Georgia",serif;color:#004080">Dear Holger,</span> <br>
<span style="font-family:"Georgia",serif;color:#004080">Thank you very much for sending the notification and the link to the FF CSTS book. I will endeavor to take a look and get through the review as soon as possible. However, in the meantime, I do have a question
as to approaching agency review for this. To me it makes sense, if we can, to run the reviews of the updated SFW (pink sheets) in parallel with those of the FF CSTS book. The rationale being that if a reviewer is being thorough (yes it might happen :-)) it
would be good to have both books available. Can you please let me know your thoughts on this?</span>
<br>
<span style="font-family:"Georgia",serif;color:#004080"> </span> <br>
<span style="font-family:"Georgia",serif;color:#004080">Best regards,</span> <br>
<span style="font-family:"Georgia",serif;color:#004080">-Erik</span> <br>
<span style="font-family:"Georgia",serif;color:#004080"> </span> <br>
<b><span style="font-family:"Calibri",sans-serif">From:</span></b><span style="font-family:"Calibri",sans-serif">
</span><a href="mailto:Holger.Dreihahn@esa.int"><span style="font-family:"Calibri",sans-serif">Holger.Dreihahn@esa.int</span></a><span style="font-family:"Calibri",sans-serif"> <</span><a href="mailto:Holger.Dreihahn@esa.int"><span style="font-family:"Calibri",sans-serif">Holger.Dreihahn@esa.int</span></a><span style="font-family:"Calibri",sans-serif">>
<b><br>
Sent:</b> Monday, June 18, 2018 5:21 AM<b><br>
To:</b> Barkley, Erik J (3970) <</span><a href="mailto:erik.j.barkley@jpl.nasa.gov"><span style="font-family:"Calibri",sans-serif">erik.j.barkley@jpl.nasa.gov</span></a><span style="font-family:"Calibri",sans-serif">><b><br>
Cc:</b> CCSDS_CSTSWG <</span><a href="mailto:css-csts@mailman.ccsds.org"><span style="font-family:"Calibri",sans-serif">css-csts@mailman.ccsds.org</span></a><span style="font-family:"Calibri",sans-serif">><b><br>
Subject:</b> Fw: Draft Red FF book on CWE</span> <br>
<br>
<span style="font-family:"Arial",sans-serif">Dear Erik,</span> <span style="font-family:"Arial",sans-serif">
<br>
Please find below the link to the CSTS FF Red-1 book for your review and approval for submission to secretariat. Below is also a link to the updated CSTS SFW (now a Draft Pink Book). There are some CSTS SFW changes pending, but as said below we believe the
CSTS SFW is fine for serving the purpose of reviewing the CSTS FF.</span> <br>
<span style="font-family:"Arial",sans-serif"><br>
Please let us know your comments and then how to proceed.</span> <br>
<span style="font-family:"Arial",sans-serif"><br>
Best regards,</span> <span style="font-family:"Arial",sans-serif"><br>
Holger</span> <br>
<span style="font-family:"Arial",sans-serif"><br>
Holger Dreihahn<br>
European Spacecraft Operations Centre | European Space Agency | S-431<br>
+49 6151 90 2233 | </span><a href="http://www.esa.int/esoc"><span style="font-family:"Arial",sans-serif">http://www.esa.int/esoc</span></a>
<span style="font-family:"Arial",sans-serif;color:purple"><br>
----- Forwarded by Holger Dreihahn/esoc/ESA on 18/06/2018 14:18 -----</span> <br>
<span style="font-family:"Arial",sans-serif;color:#5F5F5F"><br>
From: </span><span style="font-family:"Arial",sans-serif">John Pietras <</span><a href="mailto:john.pietras@gst.com"><span style="font-family:"Arial",sans-serif">john.pietras@gst.com</span></a><span style="font-family:"Arial",sans-serif">></span>
<span style="font-family:"Arial",sans-serif;color:#5F5F5F"><br>
To: </span><span style="font-family:"Arial",sans-serif">"</span><a href="mailto:Holger.Dreihahn@esa.int"><span style="font-family:"Arial",sans-serif">Holger.Dreihahn@esa.int</span></a><span style="font-family:"Arial",sans-serif">" <</span><a href="mailto:Holger.Dreihahn@esa.int"><span style="font-family:"Arial",sans-serif">Holger.Dreihahn@esa.int</span></a><span style="font-family:"Arial",sans-serif">>,
"Pham, Timothy T (3300) (</span><a href="mailto:timothy.t.pham@jpl.nasa.gov"><span style="font-family:"Arial",sans-serif">timothy.t.pham@jpl.nasa.gov</span></a><span style="font-family:"Arial",sans-serif">)" <</span><a href="mailto:timothy.t.pham@jpl.nasa.gov"><span style="font-family:"Arial",sans-serif">timothy.t.pham@jpl.nasa.gov</span></a><span style="font-family:"Arial",sans-serif">>,
Wolfgang Hell <</span><a href="mailto:wo_._he@t-online.de"><span style="font-family:"Arial",sans-serif">wo_._he@t-online.de</span></a><span style="font-family:"Arial",sans-serif">></span>
<span style="font-family:"Arial",sans-serif;color:#5F5F5F"><br>
Date: </span><span style="font-family:"Arial",sans-serif">17/06/2018 21:14</span>
<span style="font-family:"Arial",sans-serif;color:#5F5F5F"><br>
Subject: </span><span style="font-family:"Arial",sans-serif">Draft Red FF book on CWE</span>
<o:p></o:p></p>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="2" width="100%" noshade="" style="color:#A0A0A0" align="center">
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
<br>
<br>
<span style="font-family:"Calibri",sans-serif"><br>
Dear Holger, Tim, and Wolfgang,</span> <span style="font-family:"Calibri",sans-serif">
<br>
I have finished my updates of the FF book, which include the updates from Wolfgang’s review plus those resulting from the discussion that Wolfgang and I had last Monday. I believe that unless you have additional comments, this is ready to send to Erik for his
AD review and approval for submission to the Secretariat to request Red-1 review. The draft FF book can be found at URL</span>
<u><span style="color:blue"><br>
</span></u><a href="https://cwe.ccsds.org/css/docs/CSS-CSTS/CWE%20Private/Future%20Services%20using%20Toolkit/Forward%20Frame%20CSTS/FF-CSTS-r-0_1-180615.zip"><span style="font-family:"Calibri",sans-serif;color:#0082BF">https://cwe.ccsds.org/css/docs/CSS-CSTS/CWE%20Private/Future%20Services%20using%20Toolkit/Forward%20Frame%20CSTS/FF-CSTS-r-0_1-180615.zip</span></a>
<span style="font-family:"Calibri",sans-serif"><br>
</span> <span style="font-family:"Calibri",sans-serif"><br>
Note that there is a difference between the information Annex “Cross References to Cross Support Transfer Service Specification Framework” (Annex L) and the corresponding annexes in the MD and TD book and Guidelines. Section 4.18 of the Guidelines states “The
CSTS shall provide in an informative annex a table listing the specific (sub)sections and paragraphs of the CSTS Specification Framework (reference [1]) that are referenced by the new CSTS, and identifies the (sub)sections and paragraphs of this new CSTS that
make specific reference to each of those CSTS Specification Framework (sub)sections/paragraphs.” The reason that this annex is to exist is to aid the updating of the CSTS specification if and when the SFW is updated. I had suggested this particular approach.
However, I have found that constructing this annex is a time-consuming and error-prone process. For the Forward Frames book I have instead listed the pages of the FF book on which the references exist instead of the (sub)sections of the FF book in which the
cross-references appear. This allowed me to use Word’s built-in indexing capability. This produces a much more complete and consistent cross reference annex, and it serves the same purpose as the originally-defined annex. I recommend that we use this approach
from now on. If you do not agree that this approach can be used, I can generate the (sub)section-based annex in the coming weeks, but for the purposes of Erik’s review the current form is fine. (Note also that if we take this approach, we don’t necessarily
need to change the corresponding annexes MD and TD books because they still meet the intent of the annexes.) </span>
<span style="font-family:"Calibri",sans-serif"><br>
</span> <span style="font-family:"Calibri",sans-serif"><br>
Wolfgang had sent to me his markup of the CSTS SFW, to which I aligned the FF book. In our discussion last Monday, Wolfgang and discovered a few more changes that need to be made to the SFW, which he will make when he returns in July. In the process of finishing
the FF book edits, I also discovered a very few more items that need to be updated in the SFW, mostly along the lines of making agreed changes consistent across the DP, BDP, and SCPD procedures. I have documented these needed changes in detail and will send
them tomorrow to Wolfgang and copy you. I have also changed the labelling of the draft SFW to that of a Draft Pink Book and uploaded it to the CWE at URL
</span><u><span style="color:blue"><br>
</span></u><a href="https://cwe.ccsds.org/css/docs/CSS-CSTS/CWE%20Private/CSTS%20Framework%20and%20Concept/CSTS%20SFW%20Pink%20Book/921x1p1x1%20draft%20180613.doc"><span style="font-family:"Calibri",sans-serif;color:#0082BF">https://cwe.ccsds.org/css/docs/CSS-CSTS/CWE%20Private/CSTS%20Framework%20and%20Concept/CSTS%20SFW%20Pink%20Book/921x1p1x1%20draft%20180613.doc</span></a>
<span style="font-family:"Calibri",sans-serif"><br>
</span> <span style="font-family:"Calibri",sans-serif"><br>
Wolfgang and I agreed that for the purposes of Erik’s review the changes that are still to be made to the SFW are in the noise, and so we agree that we can safely point Erik to this draft for whatever cross-referencing he might choose to do.</span>
<span style="font-family:"Calibri",sans-serif"><br>
</span> <span style="font-family:"Calibri",sans-serif"><br>
Best regards,</span> <span style="font-family:"Calibri",sans-serif"><br>
John</span> <span style="font-family:"Calibri",sans-serif"><br>
</span> <br>
<span style="font-family:"Courier New"">This message is sent for information and/or discussion purposes only.</span>
<br>
<span style="font-family:"Courier New"">It shall neither be binding nor construed as constituting a commitment for ESA.</span>
<br>
<span style="font-family:"Courier New"">It is intended only for the recipient(s) named above.</span>
<br>
<span style="font-family:"Courier New"">It may contain proprietary information and/or protected content.</span>
<br>
<span style="font-family:"Courier New"">Any unauthorised disclosure, use, retention or dissemination is prohibited.</span>
<br>
<span style="font-family:"Courier New"">If you have received this e-mail in error, please notify the sender immediately.</span>
<br>
<span style="font-family:"Courier New"">ESA applies appropriate organisational measures to protect personal data.</span>
<br>
<span style="font-family:"Courier New"">In case of data privacy queries, please contact the ESA Data Protection Officer (</span><a href="mailto:dpo@esa.int"><span style="font-family:"Courier New"">dpo@esa.int</span></a><span style="font-family:"Courier New"">).</span>
<br>
<span style="font-family:"Courier New""> </span> <br>
<span style="font-family:"Courier New"">Thank you.</span> <o:p></o:p></p>
<pre>This message is sent for information and/or discussion purposes only.<o:p></o:p></pre>
<pre>It shall neither be binding nor construed as constituting a commitment for ESA.<o:p></o:p></pre>
<pre>It is intended only for the recipient(s) named above.<o:p></o:p></pre>
<pre>It may contain proprietary information and/or protected content.<o:p></o:p></pre>
<pre>Any unauthorised disclosure, use, retention or dissemination is prohibited.<o:p></o:p></pre>
<pre>If you have received this e-mail in error, please notify the sender immediately.<o:p></o:p></pre>
<pre>ESA applies appropriate organisational measures to protect personal data.<o:p></o:p></pre>
<pre>In case of data privacy queries, please contact the ESA Data Protection Officer (<a href="mailto:dpo@esa.int">dpo@esa.int</a>).<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Thank you.<o:p></o:p></pre>
</div>
</body>
</html>