The NEAT Interface to Transport Services
draft-fairhurst-taps-neat-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Gorry Fairhurst , Tom Jones , Anna Brunstrom , David Ros | ||
| Last updated | 2018-05-16 (Latest revision 2017-11-12) | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
The NEAT System provides an example of a system designed to implement the TAPS Transport Services. This document presents the transport services that the NEAT User API provides to an application or upper- layer protocol. It also describes primitives needed to interface to the NEAT Policy Manager and how policies can be adjusted to match the API behaviour to the properties required by an application or upper- layer protocol using the NEAT User API.
Authors
Gorry Fairhurst
Tom Jones
Anna Brunstrom
David Ros
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)