That's one way of doing the renaming, sure. It's not that simple though. You'd probably have to populate both names and mark one of them as deprecated. The problem is that this creates a bit of a mess.
Regarding specifying a UI, I think that is it of scope, but it's an interesting problem that would be worth talking about. On Thu, May 31, 2018, 15:06 Michael Thomas <m...@mtcc.com> wrote: > On 05/31/2018 02:32 PM, Ted Lemon wrote: > > In practice, you just change the device's name in its web ui. Then > > it's starts advertising the new name, and the old name stops working. > > If you have enough of a model of this to change the name, you also > > know enough to select the printer under it's new name. Of course it > > would be nice if we could have it publish some kind of announcement > > about the name change. > > On the subject of naming, it's not really necessary to change the name > to give it a pretty display name in DNS... you can just give it a CNAME > or something like that. That would at least give me one source of truth > on naming without having to go to every grotty web interface on low end > devices (assuming it exists at all). > > Mike > > _______________________________________________ > homenet mailing list > homenet@ietf.org > https://www.ietf.org/mailman/listinfo/homenet >
_______________________________________________ homenet mailing list homenet@ietf.org https://www.ietf.org/mailman/listinfo/homenet
