Brian E Carpenter <brian.e.carpenter@xxxxxxxxx> wrote:
> (I can see some issues with that as applied in a pure mesh
> network, where we'd need a mechanism to prevent every pledge
> also becoming a join proxy.)
There is work in ROLL that deals with some of this concern.
Specifically that in constrained LLNs, devices run out of neighbor cache
entries, and need to ration how many are used for joining (enrolling, onboarding).
In an Enterprise or ISP ACP, when the L2 fabric is ACP aware, there actually
aren't any broadcast domains left. Every link is pretty much a p2p ethernet,
so actually there aren't too many join proxies.
It's only when we play stupid L2 games, joining many links into a "LAN" that
the problem of too many join proxies becomes a concern :-)
--
Michael Richardson <mcr+IETF@xxxxxxxxxxxx> . o O ( IPv6 IøT consulting )
Sandelman Software Works Inc, Ottawa and Worldwide
Attachment:
signature.asc
Description: PGP signature
-- last-call mailing list last-call@xxxxxxxx https://www.ietf.org/mailman/listinfo/last-call
