A lot of our current tech stacks are topheavy. I'm all for re-examining foundational internet technologies and objectively examining how stuff can be pushed dow

A lot of our current tech stacks are topheavy. I'm all for re-examining foundational internet technologies and objectively examining how stuff can be pushed down the stack as it were; I'm arguably one of the people destroying DNS if that's your mindset, seems like a good key-value store and "data diode" to me. I think email (SMTP) still hasn't been fully exploited as a job scheduling tool (events... mini batches... SMTP). Bearing in mind, I don't expect people to burden the public infrastructure with these kinds of activities. I think if you're going to use the DNS for telemetry you need to scale your deployment to handle at least hundreds of requests a second; this isn't hard with DNS, it's just not the mindset of DNS operators intending to use the DNS as it always has been used. There are also some blatantly political considerations which need to be swept away to make it truly seamless. The gnashing of teeth is obviously suspect when you consider the trajectory of HTTP: from web pages to XHR, SOAP and DoH. However questionable you might find the architectural choices, HTTP continues to work in spite of the abuse. Likewise, the demise of DNS is unlikely.