Hi everyone, With one week having passed since this posting, and one week to go until the meeting, I thought I'd send a reminder - folks, please consider taking a look at this. For a fast way of reading this:
- keep in mind that we removed all transport features that either don't require application-specific knowledge (knowledge that only applications have) or don't have a fall-back to TCP - start reading from section 4 ! This gives you about 13 pages to read instead of the total 35'ish, and it contains all the ineresting stuff. The pretty long section 3 can be used to go back and check, for things that make you go "huh??". Thanks! Michael > On 13 Mar 2017, at 17:06, Michael Welzl <mich...@ifi.uio.no> wrote: > > Dear TAPS WG, > > This update addresses the feedback that we got at the last meeting: people > said that this minset isn't much of a minset. ... that's because we had only > worked on the first step: categorizing transport features such that the list > can then be reduced. > > Now, in this update: > - we've brought the list in line with the latest version of the -usage draft > (the list is a lot longer now, and includes what we think are *all* transport > features of TCP, MPTCP, SCTP, UDP(-Lite) ... except for TCP Authentication. > We'll fix this one in the next version. > - we then shortened the list brutally :) by only allowing "functional" and > "optimizing" transport features, and also removing transport features for > which it doesn't seem possible to fall back to TCP > - we then wrote text discussing the strange list that we got ... some weird > things there need consideration when designing a TAPS system > - and then we made a first stab at constructing a "minimum set", derived from > the above. > > I hope folks will find this interesting despite its length - it captures > several things that I've had in mind for a while, and partially talked about > to people, but never really wrote up anywhere. A lot of love has gone into > this document ;-) > > Cheers, > Michael > > > >> Begin forwarded message: >> >> From: <internet-dra...@ietf.org> >> Subject: New Version Notification for draft-gjessing-taps-minset-04.txt >> Date: 13 Mar 2017 16:55:05 CET >> To: Michael Welzl <mich...@ifi.uio.no>, Stein Gjessing <ste...@ifi.uio.no> >> Resent-From: <mich...@ifi.uio.no> >> >> >> A new version of I-D, draft-gjessing-taps-minset-04.txt >> has been successfully submitted by Michael Welzl and posted to the >> IETF repository. >> >> Name: draft-gjessing-taps-minset >> Revision: 04 >> Title: A Minimal Set of Transport Services for TAPS Systems >> Document date: 2017-03-13 >> Group: Individual Submission >> Pages: 38 >> URL: >> https://www.ietf.org/internet-drafts/draft-gjessing-taps-minset-04.txt >> Status: https://datatracker.ietf.org/doc/draft-gjessing-taps-minset/ >> Htmlized: https://tools.ietf.org/html/draft-gjessing-taps-minset-04 >> Diff: >> https://www.ietf.org/rfcdiff?url2=draft-gjessing-taps-minset-04 >> >> 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 given in the TAPS document >> draft-ietf-taps-transports-usage-03. >> >> >> >> >> 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 _______________________________________________ Taps mailing list Taps@ietf.org https://www.ietf.org/mailman/listinfo/taps
