You're welcome! Debugging SMTP is "fun". Very happy to get this running before the WG meeting started with more than an hour to spare.
This is currently scheduled to run 0 9 * * 5 (every Friday at 09:00 UTC). Let the bikeshedding of the script run time begin. :) Cheers, Brian > On 29 Mar 2019, at 10:06, Aaron Falk <[email protected]> wrote: > > Thanks to Brian Trammell for making this happen! > > On 29 Mar 2019, at 9:28, TAPS WG status robot wrote: > > Friday March 29, 2019 > > Issues > > ietf-tapswg/api-drafts (+5/-12/💬22) > 5 issues created: > > • #303 More expressive multipath transport property (by abrunstrom) API > discuss > • #302 UDP idempotence (by mwelzl) API > • #301 Add an explicit listener object to the API (by philsbln) API > ready for text > • #300 Add property for address privacy (by tfpauly) > • #299 TAPS ARCH - Textual review to notes (by gorryfair) > 16 issues received 22 new comments: > > • #45 Do we need to make state storage explicit in the architecture and > API? (3 by tfpauly) API Architecture ready for text > • #103 Evaluate the applicability of §6.3 to ICE-like protocols (2 by > britram, tfpauly) API > • #206 Define the server-side equivalent of racing (2 by adventureloop, > tfpauly) API Architecture ready for text > • #303 More expressive multipath transport property (2 by philsbln, > tfpauly) API discuss > • #222 Reusing Preconnections? (2 by philsbln, tfpauly) API discuss > • #224 Collapse InitateWithIdempotentData() back in to Initiate() (1 by > britram) > • #257 Not all Events are shown in the diagram (1 by britram) > Architecture > • #188 ARCH: Message Framing, Parsing, and Serialization (1 by tfpauly) > Architecture help wanted > • #209 Add a few example of Specific Properties (1 by britram) > • #178 Architecture privacy and security considerations (1 by tfpauly) > Architecture ready for text > • #147 Issues to consider (Handley) (1 by tfpauly) > • #212 Consider per-context addresses as suggested by > draft-gont-taps-address-usage-* (1 by britram) API Architecture discuss > • #220 Message Context Parameters: Ordered and Final (1 by britram) > discuss > • #285 Group management (1 by mwelzl) API ready for text > • #254 Do we need to have an explicit/separate object for Listener? (1 > by tfpauly) Architecture discuss > • #127 Impl: generalise §4 to incorporate §10 (1 by tfpauly) > Implementation discuss > 12 issues closed: > > • #285 Group management API ready for text > • #254 Do we need to have an explicit/separate object for Listener? > Architecture discuss > • #224 Collapse InitateWithIdempotentData() back in to Initiate() > • #221 Connection.Receive(minIncompleteLength, maxLength) API > • #220 Message Context Parameters: Ordered and Final discuss > • #212 Consider per-context addresses as suggested by > draft-gont-taps-address-usage-* API Architecture discuss > • #209 Add a few example of Specific Properties > • #188 ARCH: Message Framing, Parsing, and Serialization Architecture > help wanted > • #184 Replace long author lists with editors admin stuff wontfix > • #147 Issues to consider (Handley) > • #127 Impl: generalise §4 to incorporate §10 Implementation discuss > • #103 Evaluate the applicability of §6.3 to ICE-like protocols API > Pull requests > > ietf-tapswg/api-drafts (+0/-0/💬2) > 1 pull requests received 2 new comments: > > • #298 Add Pooled Connections (2 by philsbln, mwelzl) API Architecture > discuss > Repositories tracked by this digest: > > • https://github.com/ietf-tapswg/api-drafts > _______________________________________________ > Taps mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/taps > > _______________________________________________ > Taps mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/taps _______________________________________________ Taps mailing list [email protected] https://www.ietf.org/mailman/listinfo/taps
