[Sls-slp] **New ** Confirmation of changes before Agency Review of USLP and TC Blue Books

[Kazz, Greg J (US 312B)]

Dear SLP WG,

I received one slight modification of the proposed change to Annex A, page A-5 below which I am sharing with all of you:

FROM: O.1 It is mandatory to support one of these options.

TO:       O.1 It is mandatory to support none or at least one of these options.



So the term, “at least one” does not preclude the possibility of both. Highly unlikely that an agency would implement both, but it does not preclude it.


This new draft version of the USLP Blue book (732.1-B) with date Dec 14 in the filename is now in the CWE under the URL: https://tinyurl.com/yxlkgy95

The current draft version of the TC Space Data Link Protocol  (232.0-B-3) which contains the pink sheet material changes is still in the CWE under the URL: https://tinyurl.com/y68opdsx



Other than this comment on 732.1-B , I have received no other feedback to report on the proposed changes to the USLP Blue Book nor the TC SDLP Blue book. So it is my intention to provide the SLS Area Director and the CCSDS Secretariat these two documents, so that pink sheets can be prepared for both.



Best regards,

Greg Kazz, SLP WG Chair



From: "Kazz, Greg J (US 312B)" <greg.j.kazz at jpl.nasa.gov>
Date: Tuesday, December 8, 2020 at 11:49 AM
To: "Kazz, Greg J (US 312B) via SLS-SLP" <sls-slp at mailman.ccsds.org>
Subject: Confirmation of changes before Agency Review of USLP and TC Blue Books

Dear SLP WG,

Please take a look at the following two blue books that we modified during our Fall 2020 Virtual Meeting and let me know if you have any more comments or issues with them. I would like a reply back by Dec. 16. The objective is to use these files as the starting point for the Secretariat to draw up pink sheets for agency review per the new projects generated by SLP WG during this meeting cycle.

Concerning the draft USLP update:
Please see this URL - https://tinyurl.com/y68opdsx

I have made one small change to the PICS Proforma Annex A as follows, which responds to the case in which a project chooses NONE for the Virtual Channel Managed Parameter, “COP in Effect”:
From re-reading the USLP draft specification, we already have a Managed Parameter, “COP in Effect” which contains the 3 values: None, COP-1, COP-P.
So the “zero” option is clearly there.
Furthermore, it is clear in 2.1.2.4 that the use of the COP is optional.
Therefore, I think the only modification needed is in the PICs under PICs items USLP-39, 40, with a slight change to the text from:

ANNEX A page A-5
FROM: O.1 It is mandatory to support one of these options.
TO: O.1 An Implementation may support none or one of these options.

Concerning the draft TC update as discussed at the meeting:
Please see this URL - https://tinyurl.com/y3gvxh5w


Regards,
Greg




Greg Kazz
Principal Engineer
Technical Group Supervisor,
PSSE/EEISE/PPSE (312B)
Jet Propulsion Laboratory
4800 Oak Grove Dr., M/S 301-490
Pasadena, CA 91109
1+(818)393 6529(voice)
1+(818)393 6871(fax)
email: greg.j.kazz at jpl.nasa.gov

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.ccsds.org/pipermail/sls-slp/attachments/20201216/addd685d/attachment.htm>