Ouroboros Functional Layering: Difference between revisions
Jump to navigation
Jump to search
Line 10: | Line 10: | ||
=== Application End-to-End layer === | === Application End-to-End layer === | ||
The application end-to-end layer provides the functionality to make data transmission reliable and secure, if required. | |||
The application end-to-end layer can provide the following operations: | |||
* Encryption (Public key or symmetric key) | |||
* Authentication (validation/verification of certificate chains) | |||
* Integrity (hash-based checks such as CRC32) | |||
* Reliability, implemented by the FRCP protocol | |||
** Fragmentation | |||
** In order delivery | |||
** Discarding duplicate packets | |||
** Automated-Repeat Request (retransmission of lost packets) | |||
** Flow control | |||
=== Network End-to-End layer / Flow Allocator === | === Network End-to-End layer / Flow Allocator === |
Revision as of 09:53, 13 October 2023
This page is under construction
Unicast model
Unicast API
The Unicast API provides the interface for an application to create, manage and destroy unicast flows and read and write from and to these flows. The API is network-agnostic and provides application primitives for synchronous and asynchronous Inter-Process Communication. It supports message-based and (byte)stream-based communication.
Application End-to-End layer
The application end-to-end layer provides the functionality to make data transmission reliable and secure, if required. The application end-to-end layer can provide the following operations:
- Encryption (Public key or symmetric key)
- Authentication (validation/verification of certificate chains)
- Integrity (hash-based checks such as CRC32)
- Reliability, implemented by the FRCP protocol
- Fragmentation
- In order delivery
- Discarding duplicate packets
- Automated-Repeat Request (retransmission of lost packets)
- Flow control