TAPers,
I've just uploaded an Internet Draft on the NEAT User API, this draft
provides a high-level overview of the transport interface to the actual
NEAT System (available on GIT-Hub) and outlines how this forms an API
that can offer TAPS-like services in an actual system.
Gorry
On 30/10/2017, 15:27, internet-dra...@ietf.org wrote:
A new version of I-D, draft-fairhurst-taps-neat-00.txt
has been successfully submitted by Godred Fairhurst and posted to the
IETF repository.
Name: draft-fairhurst-taps-neat
Revision: 00
Title: The NEAT Interface to Transport Services
Document date: 2017-10-30
Group: Individual Submission
Pages: 14
URL:
https://www.ietf.org/internet-drafts/draft-fairhurst-taps-neat-00.txt
Status: https://datatracker.ietf.org/doc/draft-fairhurst-taps-neat/
Htmlized: https://tools.ietf.org/html/draft-fairhurst-taps-neat-00
Htmlized:
https://datatracker.ietf.org/doc/html/draft-fairhurst-taps-neat-00
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.
Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.
The IETF Secretariat
_______________________________________________
Taps mailing list
Taps@ietf.org
https://www.ietf.org/mailman/listinfo/taps
