>>>>> "Evan" == Evan Hunt <[email protected]> writes: >> Do we want applications caching mDNS replies into configuration >> files? I think not, and I think the DNS people will shout loudly >> about that.
Evan> Hm... I'm a DNS people, but I'm not sure I object to this.
Evan> You'd want some mechanism for clearing old records out after
Evan> the devices had been gone from the network for a long-enough
Evan> time, but that's not intrinsically hard.
so, after your ISP renumberers you (not a flash renumber), or if you
change routers (get a new ULA), or change ISPs, you have to discover
your printer again?
Evan> I'm of the opinion that "remote access from offsite" should be
Evan> a service you can configure your printer to provide, but which
Evan> is not the default.
Uhm, so let's seperate discovery, naming, and reachability from
authorization. (being able to reach it doesn't mean you can print...)
Evan> In my ideal world (please indulge me in a moment of
Evan> handwaving), you plug in your printer, and tell it what its
Evan> name is (or let it pick its own default such as
Evan> "LaserPrinter-3"); it announces itself to the local network as
Evan> providing local printing, and its name is placed in the
Evan> .sitelocal domain.
okay, so far.
Evan> *If* you check the box for "let the outside world print to me"
Evan> -- which you and I might want to do but most people wouldn't
I agree that this is a box. I'd like to see some more authentication
and authorization things happen, but that's a detail for CUPS/IPP.
What's relevant here is that we have a new requirement for sitelocal
mDNS:
we need to signal via mDNS from the printer to the holder of the FQDN
zone (probably the CPE).
--
Michael Richardson <[email protected]>, Sandelman Software Works
pgp6yyByM7jRk.pgp
Description: PGP signature
_______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
