[Css-csts] First draft of Tracking Data CSTS on CWE

[John Pietras]

CSTSWG colleagues --
I have uploaded the first White Book version of the Tracking Data Cross
Support Transfer Service specification (TD-CSTS_W-0.01-080618.doc) to
the CCSDS Collaborative Work Environment (CWE) > Cross Support Services
Area (CSS) > Documents > CSS-CSTS > CWE Private > Future Services using
Toolkit folder at URL
http://cwe.ccsds.org/css/docs/CSS-CSTS/CWE%20Private/Future%20Services%2
0using%20Toolkit/TD-CSTS_W-0.01-080618.doc

This specification reflects out discussions with the NavWG at the spring
2008 meeting, and incorporates the new "non-discardable" notifications
of the Buffered Data Delivery procedure. Please review this draft for
both specific technical content related to tracking data, and general
style as a model for other CSTS specifications.

Please note that this draft does not support all possible tracking
service configurations that can be represented in the Tracking Data
Message (TDMs). Specifically, it does not support tracking data
configurations in which the same TDM Data keywords must be used multiple
times concurrently to represent the services being provided. In the
Blue-1 version of the TDM specification, the same TDM Data keywords may
be required to be used to represent similar but different tracking
services, and the only thing that distinguishes the different
occurrences of the keywords is the metadata used to define them. In such
cases, concurrent use of the same keywords results in the metadata being
repeated for each tracking data measurement period, which is not the
mode supported by this draft version of the Tracking Data CSTS (TD-CSTS)
specification. In a previous email I addressed the essence of the
problem, i.e., tracking data types associated with signal paths
involving different (or different combinations of) participants.

Several possible approaches exist to solve this issue, each with its set
of advantages and disadvantages. We will need further discussion and
analysis to determine which is the best approach to take. Subsequent
updates of this White Book will reflect the outcome of those discussions
and decisions.

Best regards,
John