[Css-csts] Final candidate Red-1 FF book

[Holger.Dreihahn at esa.int]

Dear Erik,
Attached is the draft FF-CSTS Red Book, ready for submission to the 
Secretariat. It contains the following updates:
a.       Final coordination tweaks for alignment with the draft SFW Pink 
Book;
b.       Responses to the three outstanding comments from your review of 
the previous version of that document (more on that in a moment); and
c.       A reworking the Forward AOS sections of annex I to incorporate 
Ken Andrews’ comments. 
 
Regarding the three outstanding comments from your review:
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 

“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.” 

Section 3.1 of the FF-CSTS specification contains a NOTE that states

“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.”

Thus the FF book is consistent with the Guidelines on this point, and the 
WG believes this item to be closed.

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”. 

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”. 
 
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. 
 
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. 
 
Best regards,
Holger, on behalf of John, Wolfgang, Tim and the CSTS WG
 


This message 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 at esa.int).

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.ccsds.org/pipermail/css-csts/attachments/20180814/3d4e1d49/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: FF-CSTS-922x3-r0x4 candidate.zip
Type: application/zip
Size: 2652846 bytes
Desc: not available
URL: <http://mailman.ccsds.org/pipermail/css-csts/attachments/20180814/3d4e1d49/attachment.zip>