On ter?a-feira, 23 de fevereiro de 2016 07:41:11 PST Markus Jung wrote: > Hello, > please find attached a more detailled design proposal how to realize the > first basic group update feature using IPv6 multicasting (including how to > deal with IPv4-only devices). I have tried to incorporate the feedback > received from several people as best as possible. I will prepare a Wiki > page and await feedback from the maintainer. Best regards
I would say IPv4-only devices need not participate in this grouping. If they are all using the same multicast group anyway, there's no power saving. This can be achieved by continuing to use unicast with those devices, but use the IPv6 multicast with those that are capable of it. In summary: don't be shy about designing IPv6-only features. IPv4-only devices will be upgraded by 2017. There are two things still not addressed in your proposal: 1) ensuring the multicast was received by the entire group member list. We cannot assume that any packet sent will be received (it will not). Since the actions we're talking about use CoAP CON in unicast, they should continue to use CON in multicast and the sender needs to know the list of all members so that it can verify that it received all ACKs. 2) address assignment/generation -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center
