<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)">
<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:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
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.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;
font-family:"Georgia",serif;
color:#1F497D;}
span.EmailStyle21
{mso-style-type:personal-compose;
font-family:"Georgia",serif;
color:windowtext;}
.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;}
--></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="MsoNormal"><span style="font-family:"Georgia",serif;color:#1F497D">Dear 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">Thank you for the updated recommendation. I am happy to see the remaining items addressed and I think we can indeed move forward to requesting agency review for the draft FF-CSTS
recommended standard. <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"><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> Tuesday, August 14, 2018 5:17 AM<br>
<b>To:</b> Barkley, Erik J (3970) <erik.j.barkley@jpl.nasa.gov><br>
<b>Cc:</b> CCSDS_CSTSWG <css-csts@mailman.ccsds.org>; Wolfgang Hell <wo_._he@t-online.de><br>
<b>Subject:</b> Final candidate Red-1 FF book<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif">Dear Erik,</span>
<br>
<span style="font-family:"Calibri",sans-serif">Attached is the draft FF-CSTS Red Book, ready for submission to the Secretariat. It contains the following updates:</span>
<br>
<span style="font-family:"Calibri",sans-serif">a. Final coordination tweaks for alignment with the draft SFW Pink Book;</span>
<br>
<span style="font-family:"Calibri",sans-serif">b. Responses to the three outstanding comments from your review of the previous version of that document (more on that in a moment); and</span>
<br>
<span style="font-family:"Calibri",sans-serif">c. A reworking the Forward AOS sections of annex I to incorporate Ken Andrews’ comments.
</span><br>
<span style="font-family:"Calibri",sans-serif"> </span> <br>
<span style="font-family:"Calibri",sans-serif">Regarding the three outstanding comments from your review:</span>
<br>
<span style="font-family:"Calibri",sans-serif">a. The last sentence in the Note under section 3.1 addresses the FF variance from the Guidelines with respect to having two modes for the prime procedure type. You asked if it was consistent with the Guidelines.
The WG had decided that rather than explicitly address the topic of multiple prime procedures, the approach would be to state that the Guidelines could be deviated from if such deviation is necessary to make a service work. All that the deviating service specification
would need to do is point out the nature of the deviation. Wolfgang has confirmed that section 1.1 of the May 2018 draft of the Guidelines states
<br>
<br>
“Any CSTS specification should follow this Recommended Practice to the greatest extent possible and practical, but if a service has circumstances that are not addressed by this document, that service specification can go beyond these guidelines as long as those
extensions are explicitly identified in the service specification.” <br>
<br>
Section 3.1 of the FF-CSTS specification contains a NOTE that states<br>
<br>
“Normally, CSTSes do not have modes that require different prime procedure types. However, because each Forward Frame service instance must support one of several space data link protocols, some of which require capabilities provided by the Sequence-Controlled
Frame Data Processing (SCFDP) procedure and some that require the Buffered Frame Data Processing (BFDP) procedure, the Forward Frame service must allow the SCFDP procedure to be prime in some service instantiations and the BFDP procedure to be prime in other
service instantiations. The approach adopted in this specification is to define two modes, each with its own prime procedure. This approach is not documented in the Guidelines (reference [3]) and is used in this service only because the requirements are outside
the provisions of the Guidelines. Note that section 1.1 of the Guidelines permits such variances as long as they are necessary to the service and are identified in the service specification as being a variance from the Guidelines.”<br>
<br>
Thus the FF book is consistent with the Guidelines on this point, and the WG believes this item to be closed.<br>
</span><br>
<span style="font-family:"Calibri",sans-serif">b. You (commented that the title of table A-5 is “Required Procedures”, but some of the procedures are optional. The title of the table has been changed to “Procedures Used by the FF-CSTS Specification”.
<br>
</span><br>
<span style="font-family:"Calibri",sans-serif">c. You suggested putting “ASN.1” in the title of the annexes that specify ASN.1 modules. The annexes in question have two parts: the first one has an ASN.1 specification of the module, and the second part
specifies that the transfer syntax be the Basic Encoding Rules (BER). We have added “ASN.1” to the titles of the subsections that contain the ASN.1 specifications, e.g., “Forward Frame Object Identifiers ASN.1 Module”.
</span><br>
<span style="font-family:"Calibri",sans-serif"> </span> <br>
<span style="font-family:"Calibri",sans-serif">John will follow up with Ken by providing a copy of the updated material related to the Forward AOS Sync and Channel Coding functions. However, we do not believe that we should continue to iterate on this material
prior to submission for Red-1 review. </span><br>
<span style="font-family:"Calibri",sans-serif"> </span> <br>
<span style="font-family:"Calibri",sans-serif">The Working Group requests that you begin the process of submitting this document to the Secretariat for Agency Red Book review. We will be holding a WG splinter meeting this coming Thursday to discuss the prospects
for having the SFW Pink Book ready for its review, and we’ll inform you of our findings. But we believe that whatever the outcome there, Tom G should get started on the FF book as soon as possible.
</span><br>
<span style="font-family:"Calibri",sans-serif"> </span> <br>
<span style="font-family:"Calibri",sans-serif">Best regards,</span> <br>
<span style="font-family:"Calibri",sans-serif">Holger, on behalf of John, Wolfgang, Tim and the CSTS WG</span>
<br>
<span style="font-family:"Calibri",sans-serif"> </span> <o:p></o:p></p>
<pre>This message is intended only for the recipient(s) named above. It may contain proprietary information and/or<o:p></o:p></pre>
<pre>protected content. Any unauthorised disclosure, use, retention or dissemination is prohibited. If you have received<o:p></o:p></pre>
<pre>this e-mail in error, please notify the sender immediately. ESA applies appropriate organisational measures to protect<o:p></o:p></pre>
<pre>personal data, 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>
</div>
</body>
</html>