It looks like TAPS has a 2.5 hour slot, which is good! We’ll be publishing some -01 versions of the architecture, interface, and implementation drafts before the submission deadline, so I think we should have slots for those documents. We haven’t worked out the details yet, but I imagine having 15 minutes architecture, 20 minutes interface, and 10 minutes implementation would make sense based on the diffs.
There should also be a rev of the transport security survey and some initial feedback from the security area, so an update from Chris or Kyle on that (15?) would be good. One other agenda proposal I’d like to make is a section highlighting some implementation experiences that can influence our drafts. I think NEAT has some details they’d like to share, and now that Apple has released its Network.framework new transport API, I’d like to give a 10 minute talk sharing how it looks and some decisions we made while implementing. Best, Tommy > On Jun 28, 2018, at 4:53 AM, Zaheduzzaman Sarker > <[email protected]> wrote: > > Hi TAPS, > > We are planning for the IETF 102 Session. Please send your proposal(s) for > agenda item and also mention – > > The duration of timeslot you prefer. > The points you would like to discuss during the IETF102 meeting during your > timeslot. > > BR > > Zahed & Aaron > > _______________________________________________ > Taps mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/taps
_______________________________________________ Taps mailing list [email protected] https://www.ietf.org/mailman/listinfo/taps
