We've just posted a minor rev to the ID. It contains corrections to INIT_FLOW; fixes to typos. It also includes a diagram, which we did not have time to draw before the meeting, but seemed useful for a discussion.

Gorry


On 13/11/2017, 13:34, [email protected] wrote:
A new version of I-D, draft-fairhurst-taps-neat-01.txt
has been successfully submitted by Godred Fairhurst and posted to the
IETF repository.

Name:           draft-fairhurst-taps-neat
Revision:       01
Title:          The NEAT Interface to Transport Services
Document date:  2017-11-13
Group:          Individual Submission
Pages:          15
URL:            
https://www.ietf.org/internet-drafts/draft-fairhurst-taps-neat-01.txt
Status:         https://datatracker.ietf.org/doc/draft-fairhurst-taps-neat/
Htmlized:       https://tools.ietf.org/html/draft-fairhurst-taps-neat-01
Htmlized:       
https://datatracker.ietf.org/doc/html/draft-fairhurst-taps-neat-01
Diff:           https://www.ietf.org/rfcdiff?url2=draft-fairhurst-taps-neat-01

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
[email protected]
https://www.ietf.org/mailman/listinfo/taps

Reply via email to