--- layout: post title: Overview and Logs for the tini2p Dev Meeting Held on 2019-08-22 summary: Current project status, Roadmap, Meta issues, and miscellaneous tags: [dev diaries, i2p, crypto] author: el00ruobuob / oneiric --- # Logs **\** 0: Greetings **\** hi **\** 1: What's been done **\** A lot **\** I've more-or-less finished the tunnel message processing classes (Hop, InboundEndpoint, InboundGateway, OutboundEndpoint, OutboundGateway) **\** still making changes as I impl tunnel management classes (InboundTunnel, OutboundTunnel, TransitTunnel, Pool, PoolManager), but the changes are fairly minor **\** had a few big, time-consuming refactors for the processing classes, but most of those are finished now (hopefully) **\** I am almost done with the TransitTunnel class (used for participating in Tunnels created by remote routers) **\** :wave: **\** hi @DavidBurkett, how are you? **\** Great! And yourself? **\** doing well, thanks :) **\** welcome **\** to the meeting **\** Happy to be here. Will observe and try not to interrupt :) **\** right on, feel free to ask or comment at will **\** happy to have you, as always **\** so Tunnels are almost done, and have been what I've spent all of my time on over the last two weeks **\** 2: What's next **\** so, the last few I2P LS2 meetings have been a bit hairy **\** we've been discussing, mainly, changes to 144 (ECIES-X25519 end-to-end sessions) **\** admittedly, I could have handled things much better than I did **\** thankfully, things seem to be moving forward again, and we've concluded that reuse of ephemeral keys is a bad idea **\** it will require some changes to my ECIES-X25519 impl, which I will do after finishing tunnels **\** whether to follow the drop-until-secure or send-NewSession-until-secure is still to be determined **\** drop-until-secure is what I prefer, and means routers with drop end-to-end messages, until a secure channel to the Destination is established **\** only requires one round-trip, and support sending one 0-RTT payload in the initial NewSession and NewSessionReply messages **\** zzz is of the opinion that drop-until-secure will not work for performance and client-related reasons **\** I haven't begun to implement client stuff, so maybe zzz is right **\** NewSession-until-secure basically sends NewSession messages to the Destination until the first NewSessionReply is received **\** Is that discussion in the PR for 144 or something? **\** Or was that in IRC? **\** was on Irc2P, the meeting logs are here: tini2p/meta#29 **\** Thanks :) **\** and here: tini2p/meta#28 **\** guess it might be a bit much to rehash the discussion here, just trying to summarize **\** I'll read through and understand **\** YOu have good TL;DR's **\** NewSession-until-secure also has its problems, but should be workable **\** thanks :) **\** anyway, I'll be implementing the drop-until-secure until we come to consensus on what actually becomes spec **\** it's simpler, more secure, and more efficient **\** though latency/performance may be a killer for it **\** after the changes for ECIES-X25519, I'll be gluing everything together with a RouterContext class **\** with RouterContext, I'll be able to have the NTCP2 transport talk to the Tunnels and NetDB classes **\** I'll create some basic unit tests, if they make sense. the majority of the tests for RouterContext will be net-tests (integration/functional tests) **\** with RouterContext finished, tini2p library users will be able to build their own router **\** that will likely be alpha-release time **\** I'm shooting for a one-week impl time on RouterContext, but may run into bugs/refactor work that pushes that timescale back a week or two **\** it's really just gluing stuff together though, so I'm hoping it goes quickly **\** I also need to make a small update to NTCP2 for the testnet-separation update to specs from 147 **\** basically it's a netID check that ensures no cross-talk between mainnet and testnet routers **\** it's important for I2P network health, so I am happy to impl **\** That's awesome! I'll watch for updates on that RouterContext. I'll try setting one up once you're finished **\** for sure :) **\** will likely be adding a docker setup, so you can run a full testnet entirely locally **\** Nice! **\** definitely! also allows spinning up 10+ routers on different /16 pretty easily, so it may be a good way to do integration tests with I2P Java and i2pd once I add ElGamal tunnel building **\** ElGamal tunnel building is post-alpha though **\** :) **\** so that's about it for stuff until alpha release **\** 3: Questions/Comments **\** Nothing from me. :thumbsup: **\** for sure **\** 4: Next meeting **\** staying on normal schedule, two weeks from today: 2019-09-05 18:00 UTC **\** that's all, thanks all for the meeting **\<@tini2p\_gitlab>** gaffer banger