>> Your turn now. Could you please describe the UI that you envision?
> The list of names (from the internal mDNS/DNS-SD, as well as DHCP hostnames)
> is presented to the house owner, they click on the ones that the want to
> be publically visible.
Are you assuming here there's a central Homenet controller that presents
a web interface where the "house owner" can choose which names get
published?
Daniel's original draft used the term "CPE" for the hidden primary. At
the time, I pointed out two things:
- there's no single CPE in Homenet, there's zero, one or more edge
routers which might or might not be ISP-controlled devices;
- no Homenet service should be bound to an ISP-controlled device.
I believe that these requirements still reflect WG consensus.
Assuming that I'm right, I can only see two ways to provide global naming
without giving up on the properties above:
- we avoid relying on a central controller (hidden primary with web
interface);
- we define a way to elect the central controller (hidden primary)
in a way that doesn't bind the election to an ISP-controlled device.
(Am I missing a third option?)
The protocol that I have outlined is certainly not perfect, but it has the
virtue of avoiding the need for a central controller in the Homenet by
outsourcing naming using an end-to-end protocol between the host being
named and an external DNS primary.
I'm probably missing something, Michael, so please explain if you agree
with the analysis above, whether you're assuming a central controller,
and, if so, where is the central controller located in a network that has
multiple edge routers.
-- Juliusz
_______________________________________________
homenet mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/homenet
