Florin Coras | 8ef8f8f | 2020-01-03 00:23:13 +0000 | [diff] [blame] | 1 | --- |
| 2 | name: Session Layer |
| 3 | maintainer: Florin Coras <fcoras@cisco.com> |
| 4 | features: |
| 5 | - Manages allocation and tracking of sessions (6-tuple lookup tables) |
| 6 | - App namespaces that constrain application access to network resources |
| 7 | - Conveys data and notifications (ctrl and io) between transport protocols |
| 8 | and apps |
| 9 | - Transport protocol interface: |
| 10 | - Provides generic transport protocol template |
| 11 | - Converts between transport and application representation of data |
| 12 | - Schedules sessions/connections for sending |
| 13 | - Application interface: |
| 14 | - Maintains per application state |
| 15 | - Manages allocation of shared memory resources used for exchanging data |
| 16 | between applications and transports |
| 17 | - Exposes a native C and a binary api for builtin and external apps |
| 18 | respectively |
| 19 | description: "The session layer facilitates the interaction between northbound |
| 20 | applications and southbound transport protocols. To this end, |
| 21 | northbound, through the app-interface sub layer, the session |
| 22 | layer exposes APIs for applications to interact with abstract |
| 23 | units of communication, i.e., sessions. And southbound, through |
| 24 | the transport protocol interface, it exposes APIs that allow |
| 25 | transport protocols to exchange data and events (ctrl and io) |
| 26 | with applications, without actually being aware of how that |
| 27 | communication is carried out." |
| 28 | state: production |
| 29 | properties: [API, CLI, STATS, MULTITHREAD] |