[143212] in North American Network Operators' Group
Re: dynamic or static IPv6 prefixes to residential customers
daemon@ATHENA.MIT.EDU (Blake Dunlap)
Wed Aug 3 00:33:57 2011
In-Reply-To: <4E38C59D.8000201@jima.tk>
From: Blake Dunlap <ikiris@gmail.com>
Date: Tue, 2 Aug 2011 23:33:00 -0500
To: nanog@nanog.org
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
Or, alternately, don't care what your printer's ridiculously long IPv6 IP is
at this moment, (ULA/GUA/assigned: it really doesn't matter) and use mdns
like normal people. Otherwise we're ignoring the forest for the trees, I
don't expect to try to explain to my grandma how to type in
2001:45ea:344b:dead:beef::27 and/or remember it, when "printer1" will do.
This just makes me think of this: http://bash.org/?14258
If we need a way to mdns to work across subnet boundries in a single
administrative domain, so be it. If we need a better mdns, lets make that
too, but we *really* need to get away from direct IPs in general.
-Blake
