Wrote ‘Carbon-aware Name Resolution’ with Patrick for HotCarbon but ultimately decided not to submit it as the conference doesn’t seem to align with our interests and the paper could use more polishing. We’re planning on polishing it up and sticking it on arxiv as a basis for a HotNets submission. We spoke to Anil about this and came away with a bunch of ideas, including
- Managing the power schedule of resource-constrained devices.
- Re-visiting the idea of giving each service a unique IPv6 address.
- Store-and-forward energy budgeting for low powered sensor networks.
- Why isn’t the whole Internet a Filesytem (could the DNS encode file paths?).
- Providing TLS to MQTT.
- Having a BGP IPv6 testbed for this with Mythic Beasts.
- Workload scheduling in a compute cluster.
Some ideas that I wasn’t so convinced about where emissions aware-routing (encoding carbon information in an IP address) and putting the carbon schedule in the TTL (resolvers won’t decrement this).
I also read about Guix’s service manager being augmented with a capability system for distrusted systems. It seems our name-based service management overlaps with this significantly.