[SEA-TIME] Yellow book processes RE: Time Management WG April 2026 Meeting

Thu Apr 30 11:42:06 EDT 2026

In practice, from what I remember there is a repository for the Yellow Books, separate from the public library. There was some concern that the collection there wasn't complete because of inconsistent usage, if I recall.

Two good points confirmed, though - the WG chair documents the Yellow Book, and the non-exercised options/features are removed from the Blue Book.

     ----Jon

From: Lux, Jim (US 430E) <james.p.lux at jpl.nasa.gov>
Sent: Thursday, April 30, 2026 8:30 AM
To: Sinda Mejri <Sinda.Mejri at esa.int>; SEA-TIME at mailman.ccsds.org
Cc: Matsko, Andrey B (US 362J) <andrey.b.matsko at jpl.nasa.gov>; Hamkins, Jon (US 3611) <jon.hamkins at jpl.nasa.gov>
Subject: Yellow book processes RE: Time Management WG April 2026 Meeting

The big yellow book (A02x1y4c2) is silent on what has to happen with test report yellow books:
In theory, there should be a "project" defined for a yellow book (5.5.2.2 Project Parameters)

6.1.6 ADMINISTRATIVE TRACK
The Administrative Track consists of the following:

  *   CCSDS Record (Yellow Book).
Yellow Books may be reports or meeting records, but they are also used for documenting CCSDS internal processes, procedures, and controlling guidelines and for documenting interoperability test plans and reports.  This document is a CCSDS Yellow Book and it is a controlling document describing CCSDS procedures.
[January 2016][CCSDS A02.1-Y-4 Cor. 2][Cor. 2]Yellow Books shall be used to document the test plans and test reports produced in support of CCSDS Blue Book interoperability testing.  Yellow Books may also be used to document CCSDS internal processes, procedures, and controlling guidelines.  This document is itself a CCSDS Yellow Book, and it is a controlling document describing CCSDS procedures.  Any CCSDS Yellow Book that is normative upon CCSDS itself requires CESG and CMC approval polling.
An expanded discussion of CCSDS document types is contained in annex B.

6.2.6 describes the requirements, including the "two implementations"

  1.  Interoperability Testing
                At least two independent and interoperable prototypes or implementations must have been developed and demonstrated in an operationally relevant environment, either real or simulated, unless a waiver of the interoperability testing requirement has been approved:

  *   the WG Chair is responsible for documenting the specific implementations that qualify the specification for CCSDS Recommended Standard status, along with reports relevant to their testing;
  *   if patented or otherwise controlled technology is required for the separate implementations, they each must also have resulted from separate exercise of the licensing process, and it must be demonstrated by the WG Chair that the licensing process and fees are reasonable and non-discriminatory;
  *   in cases in which one or more options or features have not been demonstrated in at least two interoperable prototypes or implementations, the specification may advance to the CCSDS Recommended Standard level only if those options or features are removed;
  *   the documentation of qualifying implementations must include specific statements about the ability to support each of the individual options and features.  The documentation of qualifying implementations may be done by creating a filled out ICS to document which of the mandatory and optional features have been implemented and if there are any deviations or gaps.

  1.  Implementation Conformance Statement
                New projects shall include an Implementation Conformance Statement (ICS) proforma as a normative annex, unless a waiver of the ICS requirement has been approved. An ICS is optional for

  *   revisions of Recommended Standards;
  *   projects already underway at time of publication of issue 4 of this document.
NOTE   -              An ICS for a protocol is a Protocol ICS (PICS).

I'll look in the publication manual for more information

-----Original Appointment-----
From: Sinda Mejri <Sinda.Mejri at esa.int<mailto:Sinda.Mejri at esa.int>>
Sent: Thursday, March 05, 2026 8:43 AM
To: Sinda Mejri; SEA-TIME at mailman.ccsds.org<mailto:SEA-TIME at mailman.ccsds.org>
Cc: Matsko, Andrey B (US 362J); Hamkins, Jon (US 3611); Lux, Jim (US 430E)
Subject: Time Management WG April 2026 Meeting
When: Thursday, April 30, 2026 4:00 PM-5:25 PM (UTC+01:00) Amsterdam, Berlin, Bern, Rome, Stockholm, Vienna.
Where: https://esait.webex.com/esait/j.php?MTID=m218531dade7b76edda36f5c198d2b1c2

________________________________________________________________________________
Microsoft Teams meeting
Join: https://teams.microsoft.com/meet/38806980072583?p=XlKjF1h9ohPr9gd3TI<https://urldefense.us/v3/__https:/teams.microsoft.com/meet/38806980072583?p=XlKjF1h9ohPr9gd3TI__;!!PvBDto6Hs4WbVuu7!MoiRKQPdBtlZtWz3QpuF2fD5jz35NOeTqq-UQT8OTuVTzdK-imJmHXfh3KHy6pj5jTGjkX88LDV5EtWE-e9qx1ghDu8m$>
Meeting ID: 388 069 800 725 83
Passcode: bN9BS6dA
________________________________
Need help?<https://urldefense.us/v3/__https:/aka.ms/JoinTeamsMeeting?omkt=en-US__;!!PvBDto6Hs4WbVuu7!MoiRKQPdBtlZtWz3QpuF2fD5jz35NOeTqq-UQT8OTuVTzdK-imJmHXfh3KHy6pj5jTGjkX88LDV5EtWE-e9qxzXM5nbx$> | System reference<https://urldefense.us/v3/__https:/teams.microsoft.com/l/meetup-join/19*3ameeting_OGVhNzFjZGItNzdiMi00MzViLWI1ZjMtOWQ2NWFkMzc2MTUy*40thread.v2/0?context=*7b*22Tid*22*3a*229a5cacd0-2bef-4dd7-ac5c-7ebe1f54f495*22*2c*22Oid*22*3a*224a1409c0-9663-4d2d-971c-e9149fa2fb92*22*7d__;JSUlJSUlJSUlJSUlJSUl!!PvBDto6Hs4WbVuu7!MoiRKQPdBtlZtWz3QpuF2fD5jz35NOeTqq-UQT8OTuVTzdK-imJmHXfh3KHy6pj5jTGjkX88LDV5EtWE-e9qx8Ofgm7e$>
Dial in by phone
+49 69 667737678,,172835896#<tel:+4969667737678,,172835896> Germany, Frankfurt
Find a local number<https://urldefense.us/v3/__https:/dialin.teams.microsoft.com/24f2f848-5af2-4842-8cf5-07a5ac61afc3?id=172835896__;!!PvBDto6Hs4WbVuu7!MoiRKQPdBtlZtWz3QpuF2fD5jz35NOeTqq-UQT8OTuVTzdK-imJmHXfh3KHy6pj5jTGjkX88LDV5EtWE-e9qx-0IEthR$>
Phone conference ID: 172 835 896#
Join on a video conferencing device
Tenant key: teams at meet.esa.int<mailto:teams at meet.esa.int>
Video ID: 128 302 464 5
More info<https://urldefense.us/v3/__https:/esait.sharepoint.com/sites/esaitServicePortal/SitePages/How-to-connect-to-WebEx-or-Microsoft-Teams-meeting-with-Polycom.aspx__;!!PvBDto6Hs4WbVuu7!MoiRKQPdBtlZtWz3QpuF2fD5jz35NOeTqq-UQT8OTuVTzdK-imJmHXfh3KHy6pj5jTGjkX88LDV5EtWE-e9qx0kNy0ex$>
For organizers: Meeting options<https://urldefense.us/v3/__https:/teams.microsoft.com/meetingOptions/?organizerId=4a1409c0-9663-4d2d-971c-e9149fa2fb92&tenantId=9a5cacd0-2bef-4dd7-ac5c-7ebe1f54f495&threadId=19_meeting_OGVhNzFjZGItNzdiMi00MzViLWI1ZjMtOWQ2NWFkMzc2MTUy@thread.v2&messageId=0&language=en-US__;!!PvBDto6Hs4WbVuu7!MoiRKQPdBtlZtWz3QpuF2fD5jz35NOeTqq-UQT8OTuVTzdK-imJmHXfh3KHy6pj5jTGjkX88LDV5EtWE-e9qxx1E9-IZ$> | Reset dial-in PIN<https://urldefense.us/v3/__https:/dialin.teams.microsoft.com/usp/pstnconferencing__;!!PvBDto6Hs4WbVuu7!MoiRKQPdBtlZtWz3QpuF2fD5jz35NOeTqq-UQT8OTuVTzdK-imJmHXfh3KHy6pj5jTGjkX88LDV5EtWE-e9qxyokDOeG$>
[Company Logo]
Org help<https://urldefense.us/v3/__https:/esait.sharepoint.com/sites/esaitServicePortal/SitePages/How-to-contact-t.aspx__;!!PvBDto6Hs4WbVuu7!MoiRKQPdBtlZtWz3QpuF2fD5jz35NOeTqq-UQT8OTuVTzdK-imJmHXfh3KHy6pj5jTGjkX88LDV5EtWE-e9qx1jz0Ikh$> | Privacy and security<https://urldefense.us/v3/__https:/www.esa.int/About_Us/Law_at_ESA/Highlights_of_ESA_rules_and_regulations__;!!PvBDto6Hs4WbVuu7!MoiRKQPdBtlZtWz3QpuF2fD5jz35NOeTqq-UQT8OTuVTzdK-imJmHXfh3KHy6pj5jTGjkX88LDV5EtWE-e9qx-mDvsUK$>
________________________________________________________________________________

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<mailto:dpo at esa.int>).
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.ccsds.org/pipermail/sea-time/attachments/20260430/206c5f05/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.emz
Type: application/octet-stream
Size: 851 bytes
Desc: image003.emz
URL: <http://mailman.ccsds.org/pipermail/sea-time/attachments/20260430/206c5f05/attachment-0003.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image010.emz
Type: application/octet-stream
Size: 967 bytes
Desc: image010.emz
URL: <http://mailman.ccsds.org/pipermail/sea-time/attachments/20260430/206c5f05/attachment-0004.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image012.png
Type: image/png
Size: 161 bytes
Desc: image012.png
URL: <http://mailman.ccsds.org/pipermail/sea-time/attachments/20260430/206c5f05/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image013.emz
Type: application/octet-stream
Size: 904 bytes
Desc: image013.emz
URL: <http://mailman.ccsds.org/pipermail/sea-time/attachments/20260430/206c5f05/attachment-0005.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 784 bytes
Desc: image001.png
URL: <http://mailman.ccsds.org/pipermail/sea-time/attachments/20260430/206c5f05/attachment-0005.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 1032 bytes
Desc: image002.png
URL: <http://mailman.ccsds.org/pipermail/sea-time/attachments/20260430/206c5f05/attachment-0006.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image005.png
Type: image/png
Size: 467 bytes
Desc: image005.png
URL: <http://mailman.ccsds.org/pipermail/sea-time/attachments/20260430/206c5f05/attachment-0007.png>