hi Michael, ...inline...
> On 16 Jul 2015, at 13:23, Michael Welzl <[email protected]> wrote: <snip> >> Ideally, I think, then one would use a common term for Nagle(-like) >> bundling for TCP and SCTP. > > Agreed, we actually did that in Michael Welzl, Stefan Jörer, Stein Gjessing: > "Towards a Protocol-Independent Internet Transport API", FutureNet IV > workshop in conjunction with of IEEE ICC 2011, 5-9 June 2011, Kyoto, Japan, > using app PDU bundling because it's more meaningful than Nagle. > > But here the idea was just to copy+paste the list from doc 1 (version 4) and > put things under the correct headings, as a way to show how we *could* apply > categorization methods. hm, so perhaps we should have coordinated here. That list, in that version, wasn't quite complete. In the current version it's still not quite complete, as we're still trying to nail down how to partition the space of features (and how to divide things that are actually features from things that are just accidental effects of the way protocols have evolved). There are also aspects of the interfaces (coming from the interface discussion) we'd like to capture, on which we'd like to discuss f2f next Thursday. Perhaps another way to approach this would be to start with a list of features we think we want in doc 2, and to use the background from doc 1 to fill in the gaps... Cheers, Brian > Cheers, > Michael > > _______________________________________________ > Taps mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/taps
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ Taps mailing list [email protected] https://www.ietf.org/mailman/listinfo/taps
