>> https://mailarchive.ietf.org/arch/msg/homenet/7JmkTCBSSMs5nnH3VWPj6JAL0cA/
> I didn't find any clear definition of how DDNS works in that email. [...] > What's the Performance Specification that describes this process? Yes, > I know where the vendor specific documentation is. As far as I'm aware, all the REST-like DDNS protocols are vendor-specific. However, they are widely deployed. To give a data point, the ISP-provided CPE I'm using right now implements no less than three distinct vendor protocols for name registration (disabled by default, thankfully). Michael, it would probably take you 20 minutes to write up an I-D describing a reasonable REST-based DDNS protocol, another 5 minutes to write a client implementation in Javascript, and one hour to write a robust server that is well integrated with Bind. > Second, how are the credentials for that communication established? > [...] What name does your NAS pick? [...] Once the 14 year old in the > house does this, how does the parent find out about the name that was > used? [...] > If the device renumbers, or experiences a flash renumbering, how does it > know to re-register? All of these are interesting issues. However, I don't see how they depend on whether the update is carried over HTTPS or AXFR. -- Juliusz _______________________________________________ homenet mailing list homenet@ietf.org https://www.ietf.org/mailman/listinfo/homenet
