> On Mar 1, 2018, at 3:54 PM, Brian Trammell (IETF) <[email protected]> wrote: > > hi Zahed, Aaron, all, > >> On 27 Feb 2018, at 18:28, Tommy Pauly <[email protected] >> <mailto:[email protected]>> wrote: >> >> Hi Zahed & Aaron, >> >> We’ve posted the first of three new documents proposed for milestone 3, "An >> Architecture for Transport Services” (please go read it, everyone!): >> >> https://datatracker.ietf.org/doc/draft-pauly-taps-arch >> <https://datatracker.ietf.org/doc/draft-pauly-taps-arch> >> https://tools.ietf.org/html/draft-pauly-taps-arch-00 >> <https://tools.ietf.org/html/draft-pauly-taps-arch-00> >> >> The API and Implementation documents are forthcoming, and will be posted >> before the submission deadline. > > And now we have posted the second document (please go read it, everyone!): > > https://datatracker.ietf.org/doc/draft-trammell-taps-interface > <https://datatracker.ietf.org/doc/draft-trammell-taps-interface>. > > The document combines concepts of the Post Sockets, NEAT, and Socket Intents > approaches to provide an interface to the architecture in the first document > at the level of a language-independent, abstract asynchronous interface > definition. > > We'd like 10-15 minutes after Tommy to build on the architecture and > introduce the concepts. ISTM (though I haven't discussed with Tommy, Anna, > and Micheal, the other editors) that the discussion time for these documents > can probably be combined.
Definitely, I say, as one of them! Cheers, Michael
_______________________________________________ Taps mailing list [email protected] https://www.ietf.org/mailman/listinfo/taps
