Re: [mdnsext] mDNSext features/requirements rollup

[nudge <[e-mail]>]

On Mon, Jan 28, 2013, at 06:34 PM, Andrew Sullivan wrote:
> On Mon, Jan 28, 2013 at 11:51:02AM -0500, RJ Atkinson wrote:
> 
> > Some of us would like to see mDNS support multiple IP subnets
> > (e.g. multiple buildings, multiple groups, multiple (V)LANs)
> > within a single administrative domain (e.g. university campus,
> > corporate campus).  
> > 
> >   This implies having a straight-forward way to configure 
> >   networking devices (e.g. firewalls, routers) at the edge 
> >   of one's administrative domain to exclude certain interfaces 
> >   (e.g. exterior uplink interfaces) from all mDNS traffic 
> >   of the administrative domain using mDNS.
> 
> I still do not understand why this sort of thing isn't better handled
> by vastly improved tools for real DNS management.  It seems to me that
> people are asking for a single, unifed namespace outside the
> link-local context, and we invented a mechanism for that many years
> ago.  The problem is that the support tools for that mechanism sort of
> suck.  Instead of inventing a new protocol which, by definition, is
> going to run into conflicts with the existing protocols in this space,
> why wouldn't it be better to take that energy and expend it on the
> missing tools?

Because there's more money to be made being dns experts in a poorly
equipped world ?