On 15/04/2016 04:54, Ted Lemon wrote:
> You should read the homenet naming and service discovery architecture
> document. :)
>
> On Thu, Apr 14, 2016 at 12:54 PM, Christopher Morrow <
> morrowc.lists@xxxxxxxxx> wrote:
>
>>
>> On Thu, Apr 14, 2016 at 12:32 PM, Phillip Hallam-Baker <
>> phill@xxxxxxxxxxxxxxx> wrote:
>>
>>> Going to unicast should help. Multicast configuration really doesn't
>>> work on a network with as many hubs and devices as mine has.
>>>
>>
>> multicast would work, if all the hubs/devices did multicast properly,
>> right? :)
Really stupid devices do multicast properly because they are genuinely
transparent to layer 2. The annoying devices are the ones that pretend
to be layer 2 + layer 3 devices but are actually half-baked layer violation
devices. (To be specific, I have recently been burned by a layer 2/3 switch
that does not perform correct MLD snooping. And I agree that you have to be
in the 1% to diagnose that.)
>> it's not clear that unicast works, if the problem you are trying to solve
>> is service-discovery... absent some registry of 'services' for your clients
>> to use, of course (which is the point of the mdns thingy).
It seems to me that doing everything unicast makes life harder for no
reason. I don't know how we could make the Anima signaling work without
multicast, but we are restricting it strictly to link-local multicast.
Brian