Thanks for your answer, Daniel. > If I understand it properly, the use case you consider: 1) you set up > a web server in your homenet, 2) you want it to be accessed from the > outside so you register your domain name and register the IP address to > the zone. Note that In this case, the Authoritative Naming service is > outsourced to a third party which is what we want to achieve to.
No, I think that I'm speaking of the same use case as your draft. (I'm not sure, since your draft takes the use case for granted -- I'm probably missing some background here, sorry for not being more attentive previously.) I've got a device that wants to be advertised in the global DNS (a web server is the obvious example, but it doesn't matter). Your draft suggests (I think) that the device should speak to the CPE which will take care of the interaction with the public DNS (arrow 6 in Figure 1 is missing, by the way). I'd like to understand why the device needs to go through the middleman rather than speaking directly to the authoritative DNS server. My family was poor but honest, Daniel, and NATed addresses were all we could afford. Notwithstanding our difficult conditions, my parents took a lot of care to bring me up to believe that end-to-end is always better than proxying. Since you're advocating proxying, I'd like to understand why you think it is necessary. What is more, I'd like to understand why you require that the proxy be co-located with the CPE. (It could certainly be implemented on the CPE, but I don't understand why the protocol requires that.) You give some good reasons below, and I think they should be included in the draft: > - Ease the naming of device of various nature. Please explain. > - CPE remains in the homenet and may be easier to be authenticated > than all different devices. Good point. > - CPE presents a centralized point for end user interactions I'm not convinced about that, the authoritative DNS master seems like the natural place for end-user interactions. (Note that this does not prevent the CPE's web interface from implementing some sort of proxy to the DNS master's interface.) > - CPE are "powerful enough" to handle complex policies... Everything is powerful enough nowadays. My abacus has a four-core chip. > - CPE can integrate multiple protocols to publish a zone. Suppose mDNS is > used by a node, than registration of its IP address and name cannot be > perfomed on a public authoritative server cannot be performed using mDNS. I strongly disagree. I don't want mDNS->DNS proxying. Registering in the global DNS is something that should be under user control, while mDNS is something that happens automatically (for better or worse). -- Juliusz _______________________________________________ homenet mailing list homenet@ietf.org https://www.ietf.org/mailman/listinfo/homenet
