Hi, I agree.
Regarding the API, to make a concrete proposal: one of the things we didn’t get to, in Bangkok, is caching: Slide 4: https://datatracker.ietf.org/meeting/103/materials/slides-103-taps-4-draft-ietf-taps-archimplinterface-topics-00 There’s this PR that’s been open for a long time now: https://github.com/taps-api/drafts/pull/244 and the related issue: https://github.com/taps-api/drafts/issues/45 We could discuss this for a bit, see if we can make some progress. Cheers, Michael > On Jan 11, 2019, at 5:37 PM, Brian Trammell (IETF) <[email protected]> wrote: > > IMO the architecture is pretty solid, the unresolved issues currently under > discussion are primarily interface details (a couple of which we should bring > out of github to the list)... > > Cheers, > > Brian > >> On 11 Jan 2019, at 17:35, Aaron Falk <[email protected]> wrote: >> >> <nudge> Brian, Michael, Tommy: do we have any ‘unresolved architectural >> topics’ to discuss next week? </n> >> >> >> >> On 9 Jan 2019, at 18:17, Aaron Falk wrote: >> >> Reminder that we have an interim call scheduled for next week. >> >> Since the last wg meeting there has been a fair amount of activity on GitHub >> around the three interface docs. Can the authors expand on the ‘unresolved >> architecture topics’ you’d like to discuss (preferably with a volunteer to >> lead the discussion)? >> >> Also, are there any additional topics to add to the agenda? >> >> --aaron >> >> On 19 Nov 2018, at 10:05, IESG Secretary wrote: >> The Transport Services (taps) Working Group will hold a virtual interim >> meeting on 2019-01-15 from 11:00 to 13:00 America/New_York. >> >> Agenda: >> Draft agenda: >> 1. Unresolved architecture topics >> 2. TAPS Registry proposal >> 3. Use of GitHub >> >> Information about remote participation: >> https://ietf.webex.com/meet/taps | Access code: 316 448 940 >> > _______________________________________________ Taps mailing list [email protected] https://www.ietf.org/mailman/listinfo/taps
