On 20/07/2016 12:01, Ralph Droms wrote:
> Without that definition, I don't think I know where and by whom the > label will actually be used. Will it turn out to be like .local, > which, as far as I know, is rarely used anywhere and only ever by a > certain class of expert user. <nohat> I have three devices in my home that have web interfaces that are accessible as http://<devicename>.local/ because they support Bonjour. That URL is visible in the browser address bar, and not hidden away in some device-specific control panel (e.g. the Printer chooser). One of those devices is a printer, and is therefore _also_ accessible like that, hiding the '.local', but the other two are primarily accessed via a browser. Since those URLs must also be bookmarkable and because devices might move around the network, any solution that mandates any subnet-specific naming scheme would be unacceptable. My expectation is that in a Homenet multi-subnet environment I will be able to just use http://<device>.<TBD>/ and just have it work regardless of which particular subnet that device is on [*]. It's also important to me that I be able to type those addresses in, and for me that rules out the Unicode house symbol. <still nohat> I've previously argued that '.home' is fine for our purposes - I'm coming around to the argument that it's better to start with a greenfield "TBD" than to risk any conflict. Ray [*] notwithstanding name-collision issues... _______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
