Hi DNDOP, My name is Andrea Ferro. I recently submitted an I-D proposing a standardized protocol for consumer Dynamic DNS services.
There is also an TXT version available at: https://www.ietf.org/archive/id/draft-ferro-dnsop-apertodns-protocol-00.txt The IETF datatracker status page for this Internet-Draft is: https://datatracker.ietf.org/doc/draft-ferro-dnsop-apertodns-protocol/ There is also an HTML version available at: https://www.ietf.org/archive/id/draft-ferro-dnsop-apertodns-protocol-00.html The motivation is simple: consumer DDNS has been around for 25+ years (ddclient, inadyn, countless routers and IoT devices), but there's never been a formal specification. Everyone just reverse-engineered the dyndns2 protocol and built their own variations. This has led to inconsistent implementations, fragmented IPv6 support, and vendor lock-in. The draft proposes a RESTful alternative using well-known URIs (RFC 8615), JSON, and bearer tokens. It's designed to be provider-agnostic - any DDNS service can implement it. I have a working implementation in production at apertodns.com, so this isn't just theoretical. I'm looking for feedback on whether this is appropriate work for DNSOP, and whether there's interest in adoption. Happy to present at a future session if useful. Best regards, Andrea Ferro [email protected]
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ DNSOP mailing list -- [email protected] To unsubscribe send an email to [email protected]
