<font size=2 face="sans-serif">Dear Erik,</font>
<br><font size=2 face="sans-serif">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.</font>
<br>
<br><font size=2 face="sans-serif">Please let us know your comments and
then how to proceed.</font>
<br>
<br><font size=2 face="sans-serif">Best regards,</font>
<br><font size=2 face="sans-serif">Holger</font>
<br>
<br><font size=2 face="sans-serif">Holger Dreihahn<br>
European Spacecraft Operations Centre | European Space Agency | S-431<br>
+49 6151 90 2233 | </font><a href=http://www.esa.int/esoc><font size=2 face="sans-serif">http://www.esa.int/esoc</font></a>
<br><font size=1 color=#800080 face="sans-serif">----- Forwarded by Holger
Dreihahn/esoc/ESA on 18/06/2018 14:18 -----</font>
<br>
<br><font size=1 color=#5f5f5f face="sans-serif">From:
</font><font size=1 face="sans-serif">John Pietras <john.pietras@gst.com></font>
<br><font size=1 color=#5f5f5f face="sans-serif">To:
</font><font size=1 face="sans-serif">"Holger.Dreihahn@esa.int"
<Holger.Dreihahn@esa.int>, "Pham, Timothy T (3300) (timothy.t.pham@jpl.nasa.gov)"
<timothy.t.pham@jpl.nasa.gov>, Wolfgang Hell <wo_._he@t-online.de></font>
<br><font size=1 color=#5f5f5f face="sans-serif">Date:
</font><font size=1 face="sans-serif">17/06/2018 21:14</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Subject:
</font><font size=1 face="sans-serif">Draft Red FF
book on CWE</font>
<br>
<hr noshade>
<br>
<br>
<br><font size=3 face="Calibri">Dear Holger, Tim, and Wolfgang,</font>
<br><font size=3 face="Calibri">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</font>
<br><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"><font size=3 color=#0082bf face="Calibri"><u>https://cwe.ccsds.org/css/docs/CSS-CSTS/CWE%20Private/Future%20Services%20using%20Toolkit/Forward%20Frame%20CSTS/FF-CSTS-r-0_1-180615.zip</u></font></a>
<br><font size=3 face="Calibri"> </font>
<br><font size=3 face="Calibri">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.) </font>
<br><font size=3 face="Calibri"> </font>
<br><font size=3 face="Calibri">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 </font>
<br><a href="https://cwe.ccsds.org/css/docs/CSS-CSTS/CWE%20Private/CSTS%20Framework%20and%20Concept/CSTS%20SFW%20Pink%20Book/921x1p1x1%20draft%20180613.doc"><font size=3 color=#0082bf face="Calibri"><u>https://cwe.ccsds.org/css/docs/CSS-CSTS/CWE%20Private/CSTS%20Framework%20and%20Concept/CSTS%20SFW%20Pink%20Book/921x1p1x1%20draft%20180613.doc</u></font></a>
<br><font size=3 face="Calibri"> </font>
<br><font size=3 face="Calibri">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.</font>
<br><font size=3 face="Calibri"> </font>
<br><font size=3 face="Calibri">Best regards,</font>
<br><font size=3 face="Calibri">John</font>
<br><font size=3 face="Calibri"> </font>
<br>
<PRE>This message is sent for information and/or discussion purposes only.
It shall neither be binding nor construed as constituting a commitment for ESA.
It is intended only for the recipient(s) named above.
It may contain proprietary information and/or protected content.
Any unauthorised disclosure, use, retention or dissemination is prohibited.
If you have received this e-mail in error, please notify the sender immediately.
ESA applies appropriate organisational measures to protect personal data.
In case of data privacy queries, please contact the ESA Data Protection Officer (dpo@esa.int).
Thank you.
</PRE>