CFDP Backwards Compatibility

[space-individual]

Checklist (Please check before submitting)

• I reviewed the Contributing Guide.
• I reviewed the CF README.md file to see if the feature is in the major future work.
• I performed a cursory search to see if the feature request is relevant, not redundant, nor in conflict with other tickets.

Is your feature request related to a problem? Please describe.
I have a system that is running CFDP version 3.0 and want to interface it with a system that is running the older version of CFDP 2.2. Are the two versions compatible for file transfers?

Describe the solution you'd like
I would like to know if CFDP version 2.2 and 3.0 are compatible for file transfers.

Describe alternatives you've considered
I have looked at the documentation for CFDP available on the github page and have not seen anything suggesting they are compatible/incompatible with each other.

Additional context
I know certain things have changed across the two versions, such as the HK Telemetry messages having a different format.
Requester Info
Jeff Anderson

[jphickey]

I don't know if anyone has specifically tested that setup but since they both conform to the same CCSDS-defined protocol, it should generally work. The newer CF app does recognize some of the newer features in the CFDP protocol that the old version does not have, but that's mainly on receive to check that those features are NOT set (e.g it still doesn't do large files).

I'd recommend trying it and feeding any insights back.

I'd also recommend deploying the main line version as opposed to the previous v3.0.0 tag - there were a lot of fixes that went in to address troubles with the 3.0.0 version. Should probably be a new tag coming sometime soon I think.

[space-individual]

Hi Joseph, Thanks for the insight. Is there any documentation that is available that lists the upgrade path from 2.2 to 3.0? Thanks, Jeff A. From: Joseph Hickey ***@***.***> Sent: Thursday, May 19, 2022 3:36 PM To: nasa/CF ***@***.***> Cc: Jeffrey Anderson ***@***.***>; Author ***@***.***> Subject: Re: [nasa/CF] CFDP Backwards Compatibility (Issue #246) [EXTERNAL EMAIL] DO NOT CLICK links or attachments unless you recognize the sender and know the content is safe. I don't know if anyone has specifically tested that setup but since they both conform to the same CCSDS-defined protocol, it should generally work. The newer CF app does recognize some of the newer features in the CFDP protocol that the old version does not have, but that's mainly on receive to check that those features are NOT set (e.g it still doesn't do large files). I'd recommend trying it and feeding any insights back. I'd also recommend deploying the main line version as opposed to the previous v3.0.0 tag - there were a lot of fixes that went in to address troubles with the 3.0.0 version. Should probably be a new tag coming sometime soon I think. - Reply to this email directly, view it on GitHub<#246 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AUQKAVS27HNNYID3P7LY44LVK2JZDANCNFSM5WMQOSMA>. You are receiving this because you authored the thread.Message ID: ***@***.******@***.***>> Ecliptic Enterprises Corporation Space Avionics and Sensor Systems -- Home of RocketCam(tm) 398 W. Washington Blvd, Suite 100 Pasadena, CA 91103 Main number: (626) 798-2436 www.EclipticEnterprises.com Notice: This e-mail is intended solely for use of the individual or entity to which it is addressed and may contain information that is proprietary, privileged and exempt from disclosure under applicable law. If the reader is not the intended recipient or agent responsible for delivering the message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. This communication may also contain data subject to U.S. export laws. If so, that data is subject to the International Traffic in Arms Regulation (ITAR) and cannot be disseminated, distributed or copied to foreign nationals, residing in the U.S. or abroad, absent the express prior approval of the U.S. Department of State. If you have received this communication in error, please notify the sender by reply e-mail and destroy the e-mail message and any physical copies made of the communication. Thank you

[jhnphm]

Wouldn't this be an issue for instances of CF talking to one another? #224