> On 21 Mar 2017, at 09:06, Yoshifumi Nishida <nish...@sfc.wide.ad.jp> wrote: > > On Thu, Mar 9, 2017 at 7:43 AM, Michael Welzl <mich...@ifi.uio.no> wrote: > > > On Mar 8, 2017, at 9:36 AM, Michael Welzl <mich...@ifi.uio.no> wrote: > > > > Dear all, > > > > This is a quite major update: from our (author's) point of view, it now (at > > last!) captures all the RFC-defined API primitives / transport features of > > TCP, MPTCP, SCTP, UDP(-Lite) and LEDBAT. > > Sigh, with one exception - I had a plan to include it but when I checked > again I overlooked section 7.1: TCP-AO (RFC 5925) requires some changes to > the TCP user interface, not covered in this document. That one will go into > the next update, together with any other suggestions we’ll receive… > > This is just out of my curiosity... > Why there is no mention on DCCP in the draft while we there are some > descriptions of DCCP in RFC8095? I am just curious about the reason for it. > Sorry if this has already been discussed.
RFC 8095 contains many more things that this one doesn't contain... We did have someone signed up to write the DCCP stuff but it never happened, so at some point we had to give up on it. At some past meeting, we checked with the TAPS group to agree on the list of protocols that this draft now contains. Cheers, Michael _______________________________________________ Taps mailing list Taps@ietf.org https://www.ietf.org/mailman/listinfo/taps
