[Css-csts] Required version of SFW for CSTSes

[Hugh Kelliher]

Hi John et al,

 

It seems to me that this problem applies across the board to potentially all
books produced in CCSDS. For example in CSTS, SLE APIs are built on the
basis of a particular set of specifications and it takes time and additional
funding to catch up with new versions of the SLE transfer specs. There can
be problems if users and providers use APIs that use different versions of
the reference documents. 

 

Perhaps the register that the CCSDS Secretariat maintain should be expanded
to include a list or table showing which versions of the reference documents
are valid with a particular version of a CCSDS specification? Lists or
tables could be maintained by the relevant WG. This would provide positive
guidance to users rather than inviting them to work out for themselves which
version of a reference document they should use. 

 

In the meantime, I think your proposed text addresses the issue for the one
document you are considering at the moment.

 

Best regards,

Hugh

 

From: CSS-CSTS [mailto:css-csts-bounces at mailman.ccsds.org] On Behalf Of John
Pietras
Sent: 30 May 2019 21:15
To: CCSDS_CSTSWG (css-csts at mailman.ccsds.org); Wolfgang Hell
Subject: [Css-csts] Required version of SFW for CSTSes

 

CSTSWG colleagues ---

At the spring workshop we discussed the misleading nature of the
CCSDS-standard "boilerplate" text for the (normative) References subsection
of section 1, which reads:

"The following publications contain provisions which, through reference in
this text, constitute provisions of this document.  At the time of
publication, the editions indicated were valid.  All publications are
subject to revision, and users of this document are encouraged to
investigate the possibility of applying the most recent editions of the
publications indicated below.  The CCSDS Secretariat maintains a register of
currently valid CCSDS publications."

 

The problem with this text is that it implies that if a later version of a
the CSTS SFW (the most important of the referenced documents), an
implementer may attempt to use that later version. But a given version
(issue) of a CSTS Blue Book may use only the specific version of the SAFW
upon which that version of the CSTS was developed. This is a concern for all
CSTSes, not just Forward Frame.

 

As part of the resolution of pseudo-RID JP-7 (Require Specific Issue of the
SFW) I have modified the boilerplate text in an attempt to make this point.
I see that Wolfgang has taken an action to produce similar text for the
TD-book - I don't know if he has done anything about this yet. 

 

Obviously we should use the same modified boilerplate in all CSTS books
(another Guideline! :-) ). Here is what I have written as a starting point.
I am not strongly attached to it and would welcome any improvements
[modifications are in red]:

"The following publications contain provisions which, through reference in
this text, constitute provisions of this document.  At the time of
publication, the editions indicated were valid.  It is important to note
that the edition of the Cross Support Transfer Service-Specification
Framework that is named in reference [1] is the only edition that can be
used as a source of requirements for this edition of the Forward Frame
service Recommended Standard. All other publications in the list are subject
to revision, and users of this document are encouraged to investigate the
possibility of applying the most recent editions of the publications (other
than the Specification Framework) indicated below.  The CCSDS Secretariat
maintains a register of currently valid CCSDS publications."

 

Best regards,

John

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.ccsds.org/pipermail/css-csts/attachments/20190531/7ec21897/attachment.html>