[SLS-CC] JSC CCSDS 732.0-P-4.1 RIDs

Tue Dec 5 16:24:20 UTC 2023

I like Marco’s solution to RID #3. It removes the duplication but provides more useful information.

Best regards,
Greg

Get Outlook for iOS<https://aka.ms/o0ukef>
________________________________
From: Marco Rovatti <Marco.Rovatti at esa.int>
Sent: Tuesday, December 5, 2023 1:20:25 AM
To: Kazz, Greg (US 312B) <greg.j.kazz at jpl.nasa.gov>; Kazz, Greg (US 312B) via SLS-SLP <sls-slp at mailman.ccsds.org>; Space Link Coding & Synchronization Working Group <sls-cc at mailman.ccsds.org>
Subject: [EXTERNAL] RE: JSC CCSDS 732.0-P-4.1 RIDs

Dear Greg, dear all,

Here’s my take:

  1.  NASA-JSC-RID001. I have no preferences. I leave it to the C&S WG experts to decide.
  2.  NASA-JSC-RID002. Reject. I agree with Greg’s considerations. Moreover, I could not figure out in which binary scheme “all ones minus one” could lead to all zeroes as suggested by the RID’s author. Certainly neither in one’s nor two’s complement representation.
  3.  NASA-JSC-RID003. I’m in favour of reducing duplicated information, however, the better solution, in my opinion is to merge the two sentences. That is,
     *    to remove the sentence: Generated data pattern in both cases: FF FF FF FF 6D B6 D8 61 45 1F 11 F1 97 16 72 3C BE 7E 00 B1 . . .
     *   To change the sentence:
The first 10 bytes of the OID data pattern, in hexadecimal, are: FF FF FF FF 6D B6 D8 61 45 1F
into
In both cases the first 20 bytes of the OID data pattern, in hexadecimal, are: FF FF FF FF 6D B6 D8 61 45 1F 11 F1 97 16 72 3C BE 7E 00 B1 . . .

Perhaps I should generate a RID ??

Best regards

Marco

From: SLS-CC <sls-cc-bounces at mailman.ccsds.org> On Behalf Of Kazz, Greg (US 312B) via SLS-CC
Sent: Monday, December 4, 2023 9:27 PM
To: Kazz, Greg (US 312B) via SLS-SLP <sls-slp at mailman.ccsds.org>; Space Link Coding & Synchronization Working Group <sls-cc at mailman.ccsds.org>
Subject: [SLS-CC] FW: JSC CCSDS 732.0-P-4.1 RIDs

Dear SLP WG,

** Here is an update on the 3 NASA-JSC RIDs proposed above in italics below **

My preference (Greg as WG chair) would be to 1. Reject the first RID, since the C&S WG supplied that information which is useful and putting it into the AOS GB makes it less assessable. Reject RID 2, because there was no change to it in the Pink Sheets and no missions have complained about it – plus see additional info below. Accept RID 3, since the first 10 bytes of the OID sequence is indeed duplicated on that same page, ergo it should only be mentioned once.

Again, your comments are welcome. The AOS SDLP (CCSDS 732.0-B) pink sheet review ends Dec 11, 2023.

I have received 3 additional (besides Andrea Modenini’s RID, which we discussed in The Hague) from NASA which I would like to get your comments on.

URL of the pink sheets are at:  https://public.ccsds.org/review/CCSDS%20732.0-P-4.1/732x0p41.pdf<https://urldefense.us/v3/__https://public.ccsds.org/review/CCSDS*20732.0-P-4.1/732x0p41.pdf__;JQ!!PvBDto6Hs4WbVuu7!PgP0DN7cBf1J8Ij_yplpbeiqI8ibNJ5PxFlI7kgxTXPva6YN7EbXtcsUiJhRDVR_6Sq_NybLzBW6J_YNMZ0fnAzonfMcrle0$>

The first one, NASA-JSC-RID001, requests a reduction in the amount of information provided. Since the C&S WG provided this input, I’ve asked Ken Andrews (who supplied that change), NASA to give me his opinion on how to proceed. Your input is also welcome.

The 2nd one,  NASA-JSC-RID002, recommends to define “all ones minus one”. This requested change would actually have an impact in several locations in AOS SDLP but also in USLP.

My take on this RID is not to explicitly “define” it, because one can easily use a binary calculator to determine that “all ones minus one” equals decimal 254. Also since the FHP field could be 11 bits (legacy implementations) vs 16 bits (new implementations), the “all ones minus one” terminology works in both cases, without having to spell out specific decimal or binary sequences of bits.

The 3rd one, NASA-JSC-RID003, recommends removal of some duplicate information in Annex D, however, I believe that information was duplicated with the intent to help the user understand the output of the OID Frame Randomizer up front, so I don’t have a strong reason to remove it or to leave it. I also asked Ken Andrews (who supplied that change) to comment on this RID as well.

Again, your comments are welcome. The AOS SDLP (CCSDS 732.0-B) pink sheet review ends Dec 11, 2023.

Best regards,

Greg Kazz

Chair SLP WG

From: "Wagner, Raymond S. (JSC-EV811)" <raymond.s.wagner at nasa.gov<mailto:raymond.s.wagner at nasa.gov>>
Date: Monday, November 27, 2023 at 3:40 PM
To: "Kazz, Greg (US 312B)" <greg.j.kazz at jpl.nasa.gov<mailto:greg.j.kazz at jpl.nasa.gov>>
Cc: "Ni, David (JSC-EV811)[Jacobs Technology, Inc.]" <david.ni-1 at nasa.gov<mailto:david.ni-1 at nasa.gov>>, "Wagner, Raymond S. (JSC-EV811)" <raymond.s.wagner at nasa.gov<mailto:raymond.s.wagner at nasa.gov>>
Subject: JSC CCSDS 732.0-P-4.1 RIDs

Greg,

Please attached please find three JSC RIDs on CCSDS 732.0-P-4.1, all submitted by David Ni (cc’d).  Please let us know if you have any questions.  Thanks!

  *   Ray

__________________________________________________________________

Raymond S. Wagner, Ph.D.

Wireless and Communication Systems Branch (EV8) NASA Johnson Space Center

281.244.2428

281.483.5830 fax

raymond.s.wagner at nasa.gov<mailto:raymond.s.wagner at nasa.gov>

2101 NASA Parkway, Mail Code EV014

Houston, TX 77058

U.S.A.

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).
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.ccsds.org/pipermail/sls-cc/attachments/20231205/1e4f8720/attachment-0001.htm>