Discussion: Update/Refactor CLA Interface
We should rethink and refactor our BPA-to-CLA interface with the following goals:
- Support of CL-protocol-level acknowledgments and the generation of feedback to the BPA
- An important design issue here is how to do asynchronous reporting of a "TX result". See the below-mentioned draft regarding the assignment of a transmission ID etc.
- An indication to the BPA 1) when the whole bundle is "in flight" and 2) after is has been acknowledged by the receiver would be helpful.
- We also need support on the RX side, to report successful parsing of a bundle to the sending peer via the CL protocol.
- Reporting of link and transfer details to the BPA
- Support of partial transfers and reactive fragmentation
- Reduction of code duplication
- Support of special CLAs such as a CLA for storage #13
Helpful resources we should consider:
- https://datatracker.ietf.org/doc/draft-sipos-dtn-bpv7-cla-services/
- https://cloudstore.zih.tu-dresden.de/index.php/s/9SjPyY5wW7yXwJX
When done and implemented, we might want to contribute to the draft: https://github.com/BrianSipos/dtn-bpv7-cla-services
Edited by Felix Walter