On Sun, Oct 23, 2022 at 10:30 PM Daniel Migault <mglt.i...@gmail.com> wrote:
> Thanks Paul for the review, > > Most of the DISCUSS was composed of questions we answered all of them, and > updated the text when necessary. You can see the change below: > > https://github.com/ietf-homenet-wg/ietf-homenet-hna/commit/27233e962f66ad72db91dac7ec7b65b7cd3b00f4 > > We clarified the TTL and the use of CDS as an example. Please let us know > if there is anything you want us to change. > I am not much further into my questions on how this is all supposed to work. So instead of going into the details, let me pick the one question that I think is core to my lack of understanding: > I agree the net admin is expected to knwo the domain name, but I think I am missing the comment. > We hardly mention DHCP in this document. We are operating at teh zone level. phones, laptop, tv do not need to implement anything. These two sentences I think show the core of my lack of understanding. Let's say I want to put my sauna on my public home net so I can access it remotely and turn it on before I get home? Is this envisioned as a goal of the homenet architecture? Is it envisioned that this would be done by talking to the device, using a name served by the "homenet public zone" ? If so, can I determine the name of this zone, or is it only CPE auto-generated? If I can determine the name, I am confused how this all would hook into existing DNS infrastructure. It could be in my personal subdomain, a custom generic domain in .com ? But all of these different options requires different things - most things a regular enduser does not have. How is this homenet public zone envisioned to exist? Who runs the homenet Public zone ? Then we get to my sauna device. It calls itself "tylo". How does this end up as a FQDN in the homenet public zone ? How does my home end up being able to query for it? How do the queries go when not at home? It seems these questions are not answered in this draft, or I fail to understand it. So I am guessing. The only known method for hostnames publishing their names into a zone I know of is with Dynamic Updates on a local zone. But perhaps what homenet envisions is that I give my sauna a static IP and configure some webgui on my CPE to add it to my "zone" ? Now that we have a zone of stuff, how do we locally serve it at home, and how do we propagate this to the public internet. What's the role of the CPE vendor and the ISP ? I am not talking about the reverse IPv6 zones. I understand and ISP with some CPE vendor could almost automate this other than the first step of binding the name to the IP. I also do not need to know the name of an IPv6 IP when I am not home to reach my own stuff, so I don't think this matters at all for any enduser. In your answer, please try to formulate a flow of events, and then we can talk about the details of those events after that. Paul
_______________________________________________ homenet mailing list homenet@ietf.org https://www.ietf.org/mailman/listinfo/homenet
