Peter van der Stok <[email protected]> wrote: > The answer consists of a selection of text of section 7 of the draft. > The discovery follows the standard coap discovery. > ________________________________________________________________
> The discovery of the Join-Proxy by the
> Pledge is an extension to the discovery described in section 4 of
> [I-D.ietf-anima-bootstrapping-keyinfra]. In particular this section
> replaces section 4.2 of [I-D.ietf-anima-bootstrapping-keyinfra].
> The Pledge can discover a Join-Proxy by sending a link-local
> multicast message to ALL CoAP Nodes with address FF01::FD. Multiple
> or no nodes may respond. The handling of multiple responses and the
> absence of responses follow section 4 of
> [I-D.ietf-anima-bootstrapping-keyinfra].
That would be the all-CoAP solution where the pledge attracks attention to
iself. I don't think it would be used in an ANIMA ACP situation, but I think
that Peter has some ideas where it would be useful.
--
Michael Richardson <[email protected]>, Sandelman Software Works
-= IPv6 IoT consulting =-
signature.asc
Description: PGP signature
_______________________________________________ Anima mailing list [email protected] https://www.ietf.org/mailman/listinfo/anima
