Sorry for cross-posting, but this is one of those (set of) question(s) that
likeley need it.
RFC7390 (and its -bis draft) define CoAP discovery via ASM IP Multicast
request/reply
on ff0x::fd, with link-local (ff02::fd) for LANs and ff05::fd (Admin Scope) for
L3 networks.
I am wondering what insight we have about actual use of the L3 version via
ff05::fd:
- What multicast routing protocols do those networks use this type of resource
discover ?
- Specifically wireless mesh networks ?
- Specifically 802.15.4 wireless mesh networks ?
- How many / which known 802.15.4 implementation do or do not support rfc7731 ?
Any insight welcome!
Background: In anima, two drafts are planning to rely on this ASM IP multicast
method,
(draft-ietf-anima-constrained-{voucher,join-proxy}) and i have no good insight
whether
it is prudent to expect that the mayority of target deployment would be able to
support this ASM IP multicast routing, or whether we would (worst case) create
standard
RFC that will not be adopted purely because one dependency (ASM IP Multicast
routing
for ff05::fd) fails to become supportable well enough in the target networks.
And my concerns stems from a range of experiences in challenges with getting
ASM IP
multicast adopted in non-wireless-mesh networks, rfc8815 is one example (not
directly
applicable here), rfc8766 and draft-ietf-dnssd-advertising-proxy are actual
IETF work
also in response to the challenges with ASM IP multicast.
But, as said, no direct experience with routed wireless mesh networks such as
802.15.4,
although i seem to remember that i was previously told by folks from ROLL that
MPL
(rfc7731) was also not commonly supported in implementations.
Cheers
Toerless
_______________________________________________
Anima mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/anima
