[Css-csts] Updated Functional Resource Reference Model White Book on CWE

Mon Jul 6 16:50:13 UTC 2020

John,

Yes, I agree that this is a CSS area level document ultimately and is in some sense, "bedrock layer" for the CSS Architecture documents. It makes sense to me to give this a 901 number. 901.3 sounds logical to me. Let's see if we can get a book number allocated from the CCSDS Secretariat along these lines. If you like, please feel free to make a request of Tom for allocation of the book number. If you prefer, I will be happy to do it.

Best regards,
-Erik

From: John Pietras <john.pietras at gst.com>
Sent: Tuesday, June 30, 2020 08:57
To: Barkley, Erik J (US 3970) <erik.j.barkley at jpl.nasa.gov>; Wolfgang Hell <whell at gmx.de>; CCSDS SMWG ML (smwg at mailman.ccsds.org) <smwg at mailman.ccsds.org>; CCSDS_CSTSWG (css-csts at mailman.ccsds.org) <css-csts at mailman.ccsds.org>; Wolfgang Hell <wo_._he at t-online.de>
Subject: [EXTERNAL] RE: Updated Functional Resource Reference Model White Book on CWE

Erik,
Fair enough - I had adopted the pseudo-convention that some WGs have of calling pre-Red books "draft Red Book" and giving them a decimal version number (e.g., "0.4"). But that works best if the book is not exposed outside the WG (i.e., where there's no distinction between it and a WB). I'll call whatever gets provided to subject matter experts a "White Book", and tag the CSSA-interanl version that retains all of the "history" with "Complete". So the book that I sent out yesterday (that will only be seen by CSSA members) will be (effectively) "W-0.4 Complete" and the book that gets made available to the SANA FR reviewers simply "W-0.4".

Also, just for the purposes of giving that white book something other than a 000.0 CCSDS number, I tentatively assigned it "902.x" on the cover. However, I'm thinking that it is really more of a pan-CSSA, architecture-level document, so I'd like to propose that we (eventually) register the resultant Magenta Book under "901", along with the SCCS-ADD and SCCS-ARD. Can we tentatively reserve "901.3" for it?

Best regards,
John

From: Barkley, Erik J (US 3970) [mailto:erik.j.barkley at jpl.nasa.gov]
Sent: Monday, June 29, 2020 2:30 PM
To: John Pietras <john.pietras at gst.com<mailto:john.pietras at gst.com>>; Wolfgang Hell <whell at gmx.de<mailto:whell at gmx.de>>; CCSDS SMWG ML (smwg at mailman.ccsds.org<mailto:smwg at mailman.ccsds.org>) <smwg at mailman.ccsds.org<mailto:smwg at mailman.ccsds.org>>; CCSDS_CSTSWG (css-csts at mailman.ccsds.org<mailto:css-csts at mailman.ccsds.org>) <css-csts at mailman.ccsds.org<mailto:css-csts at mailman.ccsds.org>>; Wolfgang Hell <wo_._he at t-online.de<mailto:wo_._he at t-online.de>>
Subject: RE: Updated Functional Resource Reference Model White Book on CWE

John,

Just a note on terminology - I believe a Red book can really only be called as such once it has passed a resolution for going to agency review.  I am a little concerned that calling what goes to the reviewers a "draft Red Book" may confuse people and indicate that this is part of a formal agency review.  Given that, as I understand it, this is going for review internal to CCSDS, I don't think we should be calling it a Red book.  I can appreciate that this will be an edited version of the "comprehensive" white book to assist reviewers focus on just what is being published in SANA.  If possible, could we just indicate that this is a white book - I realize that inside the CSS Area we have to keep things straight - assuming this is about tier-1 resources, could we perhaps use some sort of designation tied to that?  (maybe something like add "tier-1" or "part 1" to the book number)?

Best regards,
-Erik

From: SMWG <smwg-bounces at mailman.ccsds.org<mailto:smwg-bounces at mailman.ccsds.org>> On Behalf Of John Pietras
Sent: Monday, June 29, 2020 07:40
To: Wolfgang Hell <whell at gmx.de<mailto:whell at gmx.de>>; CCSDS SMWG ML (smwg at mailman.ccsds.org<mailto:smwg at mailman.ccsds.org>) <smwg at mailman.ccsds.org<mailto:smwg at mailman.ccsds.org>>; CCSDS_CSTSWG (css-csts at mailman.ccsds.org<mailto:css-csts at mailman.ccsds.org>) <css-csts at mailman.ccsds.org<mailto:css-csts at mailman.ccsds.org>>; Wolfgang Hell <wo_._he at t-online.de<mailto:wo_._he at t-online.de>>
Subject: [EXTERNAL] [cssm] Updated Functional Resource Reference Model White Book on CWE

CSSA colleagues ---
I have uploaded an updated draft of the Functional Resource Reference Model White Book (tentatively dubbed CCSDS 902.x-W-0.4) to the CWE at URL
https://cwe.ccsds.org/css/docs/CSS%20Area/CWE%20Private/Functional%20Resource%20Reference%20Model%20Magenta%20Book/FunctionalResourcesRefModel_MagentaBook-W-04-200629.docx?Web=1

This White Book includes multiple changes from the previous draft, which was uploaded in April. The main focus of this update has been to support the subject-expert review of the so-called "Tier-1" functional resource definitions that are going to be registered in the SANA Candidate FR registry in (hopefully) the next few weeks. Specifically, the FR definitions that are going to be posted in the candidate registry are:

  1.  Antenna;
  2.  CCSDS 401 Space Link Carrier Transmission;
  3.  Ranging Transmission;
  4.  CCSDS 401 Space Link Carrier Reception;
  5.  Range and Doppler Extraction;
  6.  TC PLOP, Synchronization, and Channel Encoding;
  7.  Fixed Length Frame Synchronization, Channel Encoding, and Only-Idle-Data Generation:
  8.  Fixed Length Frame Synchronization and Channel Decoding;
  9.  TC Master Channel Multiplexing;
  10. TC Virtual Channel Multiplexing;
  11. AOS Master Channel Multiplexing;
  12. AOS Virtual Channel Multiplexing;
  13. Fixed Length Frame USLP Master Channel Multiplexing;
  14. Fixed Length Frame USLP Virtual Channel Multiplexing;
  15. TM/AOS Master Channel Demultiplexing;
  16. TM/AOSVirtual Channel Demultiplexing;
  17. Frame Data Sink;
  18. CFDP Entity;
  19. TDM Segment Generation;
  20. Offline Frame Buffer;
  21. TDM Recording Buffer;
  22. F-CLTU Transfer Service Provider;
  23. Forward Frame CSTS Provider;
  24. RAF Transfer Service Provider;
  25. RCF Transfer Service Provider;
  26. ROCF Transfer Service Provider;
  27. Tracking Data CSTS Provider; and
  28. Monitored Data CSTS Provider.

The updated version of the Reference Model focuses on making the material associated with these FRs as complete and correct as possible, including (but not limited to) response from review comments on the previous version provided by Wolfgang, having a different section for each of the Functional Resource Strata, and graphics that are consistent with the graphical conventions for at least all of the aforementioned Tier-1 FRs.

As you may know, the draft Reference Model also contains material on many other functional resources that exists at various levels of maturity, from mere placeholders to well-developed definitions only lacking in the definition of the specific parameters, events, and directives (PEDs) that are registered in the SAN FR registry. In order to help the subject matter experts focus their review on the FRs that are specifically included in the SANA Candidate FR registry, the plan is to make available to those reviewers a "draft Red Book" version (CCSDS 902.x-R-0.4) that addresses only those FR Sets and FRs that are in the SANA Candidate FR registry. In the next few weeks, I will produce that draft Red Book by trimming out the non-applicable material from the White Book.

My intention is to use the material from the White Book version (which has no formal CCSDS standing but has informally been used by CCSDS to document "working group-internal" material) as a source for future updates of the draft Red Book as SANA FR definitions are created for and added to the SANA Candidate FR registry and (eventually) graduated to the SANA Approved FR registry. When some TBD set of FR definitions has been graduated to the SANA Approved FR registry, then the version of the draft Red Book in existence at that time could undergo a CCSDS Agency Red Book review and become the first issue of the FR Reference Model Magenta Book.

Best regards,
John

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.ccsds.org/pipermail/css-csts/attachments/20200706/e28c048f/attachment-0001.htm>