You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Per requirement CF2002.1, CF should cancel the transaction when a fault is detected. Currently when CF detects a fault it will issue an event message an increment the fault counter. However it will continue to retry or closeout the transaction by issuing ACK or NAK PDUs. Some of this behavior appears to be consistent with CFDP Class 2 handling. Either the requirement needs updating or CF should comply and not attempt to continue the transaction when a fault is detected.
The text was updated successfully, but these errors were encountered:
It seems like the implementation makes sense per the walk through analysis results below. Recommend requirement update to better capture behavior (doesn't "cancel" the transaction, just closes it out per whatever method is appropriate).
Five cases from CF2002.1.2:
Positive Ack Limit Reached
Looks like transaction is reset in this case (class 2 only)
Filestore Rejection
Sends FIN to try to close out transaction with the FILESTORE_REJECTION command code (resets for class 1)
File-CRC Mismatch Failure
This happens at the end for class 1, just deletes the file. For class 2 it'll send FIN to close out with FILE_CHECKSUM_FILAURE command code
File-Size Error
At Eof, sends FIN and close out transaction with FILE_SIZE_ERROR command code
NAK Limit Reached
Sends FIN with NAK_LIMIT_REACHED (class 2 only, NA for class 1)
Inactivity Limit Reached
Sends FIN with INACTIVITY_DETECTED (resets for class 1)
Per requirement CF2002.1, CF should cancel the transaction when a fault is detected. Currently when CF detects a fault it will issue an event message an increment the fault counter. However it will continue to retry or closeout the transaction by issuing ACK or NAK PDUs. Some of this behavior appears to be consistent with CFDP Class 2 handling. Either the requirement needs updating or CF should comply and not attempt to continue the transaction when a fault is detected.
The text was updated successfully, but these errors were encountered: