Research how should CFDP work

CCSDS documents:

We should support:

Service classes
- CLASS 1 (UNRELIABLE TRANSFER)
- Without Transaction closure requested (should be possible via simplex transmission)
- With Transaction closure requested (requires duplex transmission)
- CLASS 2 (RELIABLE TRANSFER) (requires duplex transmission)
- NACK modes (more info: [GREEN BOOK] PART 2: IMPLEMENTERS GUIDE 2.6.3.1)
  - Deferred
  - Immediate
  - Prompted
  - Asnychronous
- ~~CLASS 3 (UNRELIABLE TRANSFER VIA MULTIPLE WAYPOINTS)~~
- ~~CLASS 4 (RELIABLE TRANSFER VIA MULTIPLE WAYPOINTS)~~
  
  New CFDP specification omits classes 3 and 4
User operations
- Proxy
- Proxy Put Request
- Proxy Message to User
- Proxy Filestore Request
- Proxy Fault Handler Override
- Proxy Transmission Mode
- Proxy Flow Label
- Proxy Segmentation Control
- Proxy Put Response
- Proxy Filestore Response
- Proxy Put Cancel
- Proxy Closure Request
- Remote status report
- Remote Status Report Request
- Remote Status Report Response
- Directory
- Directory Listing Request
- Directory Listing Response
- Remote suspend
- Remote Suspend Request
- Remote Suspend Response
- Remote resume
- Remote Resume Request
- Remote Resume Response
  
  User Operations refer to the use of the CFDP services offered by the local CFDP entity to cause the CFDP user of a remote CFDP entity to initiate additional CFDP transactions.
Communication between CFDP User and its local enitity via primitives:
Checksum algorithms:
- Null (no checksum)
- Modular checksum
- In addition, we can implement others from the SANA Checksum Identifiers registry
Transport
- Layer(s)
- UDP
- Any type of TCP
- Should we provide Space Packet implementation on top of transport layers?
CFDP User

uncommon-nickname / cfdp

Research how should CFDP work #20