"There’s no plan—just a person."
Last week, we pulled the cover off the research among TLDs that led to the creation of Cascade—our Rust-forged successor to OpenDNSSEC.
This week, @benno and @alexband will show that Cascade isn’t some polite upgrade. It’s a full reset—a ground-up reimagining. In a series of bite-sized videos, we’ll walk you through why Cascade exists—not to patch the old world, but to show the community our take on the way forward in the new one.
See you tomorrow!
@bortzmeyer @benno @alexband We love your enthusiasm, but right now we're putting together all the components that make up Cascade. By the time @dnsoarc 45 comes around, we'll have a package for you that you can just run.
We've got the scaffolding for the installation documentation sitting in a Pull Request here: https://cascade-signer--41.org.readthedocs.build/en/41/installation.html
@bortzmeyer @nlnetlabs @benno @dnsoarc I recommend you give us a few weeks to get everything sorted. If you would try it today, I'm afraid you'd be disappointed with the first impression, as everything is very much in flux.
See you in Stockholm!
@bortzmeyer @nlnetlabs @benno @dnsoarc We'll do a live demo on stage at OARC45—what could possibly go wrong? 😉
So after that, we look forward to you running Cascade through its paces and give us your honest feedback.
That should put us in a position to cross all the t's and dot all the i's before the first production release, towards the end of the year.
% ./target/debug/cascade status
Server status: ServerStatusResult
It works! I am now officially a Cascade expert and I can talk about it on TV :-)
@alexband @nlnetlabs @benno I'll ask ChatGPT to draw a DNSviz-authentic result.
NLnet Labs
Stéphane Bortzmeyer
Alex Band