Hi Pascal, Thank you for your response. This makes sense to me, with one observation.
On Mon, Mar 11, 2024 at 3:11 PM Pascal Thubert <pascal.thub...@gmail.com> wrote: > > 2. The deployment and backwards compatibility sections are quite good, but is > there a recommended strategy for updating existing deployments in the field? > > This specification introduces a new MoP (14.5. > <https://datatracker.ietf.org/doc/html/draft-ietf-6lo-multicast-registration-16#section-14.5>New > RPL Mode of Operation > <https://datatracker.ietf.org/doc/html/draft-ietf-6lo-multicast-registration-16#name-new-rpl-mode-of-operation>) > . This means that you cannot update a live network. You have to create a > new instance with MoP 5 and migrate nodes to that instance by allowing them > to join it. MoPs a re tradictional RPL since RFC 6550, meaning that the > behavior is already known outside of this specification. > > > With the other hat that I sometimes wear, the one of an OPS-DIR reviewer, I would say that this needs to be clarified in an Operational Considerations statement. Regards, Dan
_______________________________________________ Gen-art mailing list Gen-art@ietf.org https://www.ietf.org/mailman/listinfo/gen-art
