FYI. A relatively minor update: still based on the -00 usage draft (except for a few corrections that will also make it into its -01 version)…
But there ARE a few notable changes - e.g. we added some discussion about implementation possibilities. I do hope that the prospect of discussing implementations increases the group’s interest in this document… it would be nice to see some discussion of this before the meeting! Cheers, Michael > Begin forwarded message: > > From: <[email protected]> > Subject: New Version Notification for draft-gjessing-taps-minset-02.txt > Date: 7. juli 2016 kl. 22.25.33 CEST > To: Stein Gjessing <[email protected]>, Michael Welzl <[email protected]> > Resent-From: <[email protected]> > > > A new version of I-D, draft-gjessing-taps-minset-02.txt > has been successfully submitted by Michael Welzl and posted to the > IETF repository. > > Name: draft-gjessing-taps-minset > Revision: 02 > Title: A Minimal Set of Transport Services for TAPS Systems > Document date: 2016-07-07 > Group: Individual Submission > Pages: 15 > URL: > https://www.ietf.org/internet-drafts/draft-gjessing-taps-minset-02.txt > Status: https://datatracker.ietf.org/doc/draft-gjessing-taps-minset/ > Htmlized: https://tools.ietf.org/html/draft-gjessing-taps-minset-02 > Diff: > https://www.ietf.org/rfcdiff?url2=draft-gjessing-taps-minset-02 > > 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 services given in the TAPS document > draft-ietf-taps-transports-usage-00. > > > > > 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
