Hi, FWIW, I agree with all of these changes. I’m an author of the second and third document, so for these it is obvious, but I’m not an author of the first one.
Cheers, Michael > On 10 Mar 2023, at 01:26, Reese Enghardt <i...@tenghardt.net> wrote: > > Dear TAPS, > > As you may have seen, our three documents were updated to address Zahed's AD > review comments (Thank you to everyone involved!). > > Please note that there were normative language changes in the Interface > document. > > If you have any questions about or any objections to these changes, please > respond to the list within the next two weeks, i.e., by Thursday March 23rd, > 5pm PT. (This is Thursday before IETF 116.) > > If we don't hear anything by this date, we will assume that there is WG > consensus on these changes. > > For your convenience, here are the diffs for all three documents: > > > https://author-tools.ietf.org/iddiff?url2=draft-ietf-taps-arch-16 > > https://author-tools.ietf.org/iddiff?url2=draft-ietf-taps-interface-19 > > https://author-tools.ietf.org/iddiff?url2=draft-ietf-taps-impl-15 > > > Best, > Reese > > > On 3/9/23 10:01, internet-dra...@ietf.org wrote: >> A New Internet-Draft is available from the on-line Internet-Drafts >> directories. >> This Internet-Draft is a work item of the Transport Services WG of the IETF. >> >> Title : An Abstract Application Layer Interface to >> Transport Services >> Authors : Brian Trammell >> Michael Welzl >> Theresa Enghardt >> Godred Fairhurst >> Mirja Kuehlewind >> Colin Perkins >> Philipp S. Tiesel >> Tommy Pauly >> Filename : draft-ietf-taps-interface-19.txt >> Pages : 91 >> Date : 2023-03-09 >> >> Abstract: >> This document describes an abstract application programming >> interface, API, to the transport layer that enables the selection of >> transport protocols and network paths dynamically at runtime. This >> API enables faster deployment of new protocols and protocol features >> without requiring changes to the applications. The specified API >> follows the Transport Services architecture by providing >> asynchronous, atomic transmission of messages. It is intended to >> replace the BSD sockets API as the common interface to the transport >> layer, in an environment where endpoints could select from multiple >> interfaces and potential transport protocols. >> >> >> The IETF datatracker status page for this Internet-Draft is: >> https://datatracker.ietf.org/doc/draft-ietf-taps-interface/ >> >> There is also an HTML version available at: >> https://www.ietf.org/archive/id/draft-ietf-taps-interface-19.html >> >> A diff from the previous version is available at: >> https://author-tools.ietf.org/iddiff?url2=draft-ietf-taps-interface-19 >> >> >> Internet-Drafts are also available by rsync at >> rsync.ietf.org::internet-drafts >> >> >> _______________________________________________ >> 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 _______________________________________________ Taps mailing list Taps@ietf.org https://www.ietf.org/mailman/listinfo/taps
