Hi TAPS,

This update addresses the comments from Mirja about 2 weeks ago (avoiding to 
talk about “the TAPS system” and a “TAPS connection”, and merging sections 3 
and 4). We also took care of some editorial nits (removed some 
implementation-specific text that was marked to be removed later, updated 
references, ..).

Cheers,
Michael


> On Feb 28, 2018, at 10:30 AM, [email protected] wrote:
> 
> 
> A New Internet-Draft is available from the on-line Internet-Drafts 
> directories.
> This draft is a work item of the Transport Services WG of the IETF.
> 
>        Title           : A Minimal Set of Transport Services for TAPS Systems
>        Authors         : Michael Welzl
>                          Stein Gjessing
>       Filename        : draft-ietf-taps-minset-02.txt
>       Pages           : 46
>       Date            : 2018-02-28
> 
> Abstract:
>   This draft recommends a minimal set of IETF Transport Services
>   offered by end systems supporting TAPS, and gives guidance on
>   choosing among the available mechanisms and protocols.  It is based
>   on the set of transport features in RFC 8303.
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-taps-minset/
> 
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-ietf-taps-minset-02
> https://datatracker.ietf.org/doc/html/draft-ietf-taps-minset-02
> 
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-taps-minset-02
> 
> 
> 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.
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> _______________________________________________
> Taps mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/taps

_______________________________________________
Taps mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/taps

Reply via email to