Re: [6lo] Call for WG adoption of draft-li-6lo-native-short-address-03

2022-08-21 Thread Michael Richardson
"Liguangpeng (Roc, Network Technology Laboratory)" wrote: > Thanks for share of Carpenter's draft. I fully agree with the content > of it after a quick read. I think it's for all adoption process, not > only for this adoption call. I believe 6lo Chairs' professional > actions.

Re: [6lo] Call for WG adoption of draft-li-6lo-native-short-address-03

2022-08-21 Thread Pascal Thubert (pthubert)
I agree about your point on BIER Michael. The cool thing with it is that it can do both unicast and multicast both with the short address. Also it will reroute on failure. I’m still thinking about whether the model is relevant in IIoT as was claimed in this thread. I have not seen that any of t

Re: [6lo] Call for WG adoption of draft-li-6lo-native-short-address-03

2022-08-21 Thread Liguangpeng (Roc, Network Technology Laboratory)
Hi Michael, Thanks for the clarification. Please see below: > If I insert a new device in the tree, then all of the tree below that device > has to > renumber. Technically saying, it may exist but it seems weird to insert a new device in the middle of the tree. When a user wants a new device, a

Re: [6lo] Call for WG adoption of draft-li-6lo-native-short-address-03

2022-08-21 Thread Pascal Thubert (pthubert)
Hello Guangpeng If we take the DC sensors as use case and racks are organized in trees, and you add a new rack then there will be renumbering. This is why it’s safer to use this tech at L2. For the better and the worse IoT standards happen to use the IP address as a node ID. I was there when I