On 01/07/2016 18:43, Brian E Carpenter wrote:
> Hi,
>
>> b. MUST: Performs DNS-based Service Discovery [RFC6763] over
>> Multicast DNS [RFC6762] searching for the service
>> "_bootstrapks._tcp.local.".
>
> I missed the bit where we got consensus to only specify DNSSD for
> discovery. My understanding was that since all ANs will contain
> the ANI components, GRASP discovery was an equally valid option.
>
> DNSSD is a fine option for non-ANs that don't contain the ANI
> components.
So after some thought, I believe that we have to change this to better
fit the ANI as a whole by changing it to something like this:
b1. MUST: Performs DNS-based Service Discovery [RFC6763] over
Multicast DNS [RFC6762] searching for the service
"_bootstrapks._tcp.local.".
b2. MUST: If the node in question supports GRASP signaling
[I-D.ietf-anima-grasp], also perform GRASP Discovery searching
for the Objective "_bootstrapks._tcp.local." using a loop
count of 1 to ensure link-local scope.
That allows non-Anima devices to use DNSSD if that's their bag,
and allows Anima deployments to omit DNSSD support if they want.
The device will use the result of whichever discovery replies first.
We can use the same name with no problem.
I would argue that since all ACP nodes will support GRASP anyway,
ACP-creation should use GRASP discovery, so that DNSSD support doesn't
become mandatory in the ANI. I don't really see what we win by
inserting DNSSD unnecessarily. If it's needed for non-ANI reasons,
that's fine of course, but the ACP doesn't need it.
Regards,
Brian
_______________________________________________
Anima mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/anima
