Hello Pascal,
Please see inline.
Best Regards,
Guangpeng
> -Original Message-
> From: Pascal Thubert (pthubert)
> Sent: Monday, August 22, 2022 2:18 PM
> To: Liguangpeng (Roc, Network Technology Laboratory)
>
> Cc: Michael Richardson ; 6lo <6lo@ietf.org>
> Subject: Re: [6lo] Call for W
Hi, Michael,
As matter of fact, we are dealing with this problem right now, the smart
data center transformation cost a lot of money and additional power
consumptions because of those additional sensors. So, yes, we are looking for
such technologies that can reduce power consumption
"Liguangpeng (Roc, Network Technology Laboratory)" wrote:
> 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
"Liguangpeng (Roc, Network Technology Laboratory)" wrote:
>> -Original Message- From: Pascal Thubert (pthubert)
>> Sent: Monday, August 22, 2022
>> 2:18 PM To: Liguangpeng (Roc, Network Technology Laboratory)
>> Cc: Michael Richardson
>> ; 6lo <6lo@ietf.org> Subject:
I’m with you Michael
Though in the case of this proposal I would have one IP address per constrained
Device and multiple L2NSA to account for the redundant networks.
I would thus not derive the IP from l2NSA but use a table eg a SCHC rule or a
6LoWPAN context to map the IP from the MAC.
I’m st
Hello Rong
Please keep us tuned on the use case and what your final preference is. We
could help you skim through possible solutions and do procons games.
Regards,
Pascal
> Le 22 août 2022 à 11:59, longrong a écrit :
>
> Hi, Michael,
>
>
> As matter of fact, we are dealing with thi
You read me wrong Guangpeng.
I’m advocating for multiple NSA L2 addresses to reflect redundancy in the
network.
And a single IP address that remains even if the network changes and maps all
the MAC addresses.
The consequence is that the IP must not derive from MAC.
Though I agree with Micha
> -Original Message-
> From: Michael Richardson
> Sent: Monday, August 22, 2022 11:41 PM
> To: Liguangpeng (Roc, Network Technology Laboratory)
>
> Cc: 6lo <6lo@ietf.org>
> Subject: Re: [6lo] Call for WG adoption of
> draft-li-6lo-native-short-address-03
>
>
> "Liguangpeng (Roc, Netw
> -Original Message-
> From: Michael Richardson
> Sent: Monday, August 22, 2022 11:44 PM
> To: Liguangpeng (Roc, Network Technology Laboratory)
>
> Cc: Pascal Thubert (pthubert) ; 6lo
> <6lo@ietf.org>
> Subject: Re: [6lo] Call for WG adoption of
> draft-li-6lo-native-short-address-03
>
Hello Pascal,
My apologies for late reply (I am taking some time off). Since I last
wrote, thread has progressed quite a bit. Anyways...·
What attracted my attention is the header structure in Figure 6. It is
often the case that field devices are smaller 8-bit or16-bit addresses
connected to
Hi Pascal,
As you raised before, the redundancy in network is a significant case for the
addressing to solve. That's why we wrote another separate draft to discuss this
in IETF 114. Multiple L2 MAC addresses may be a solution, but I can not see the
whole view of it now.
I also support a perma
Thanks Kiran;
My view is that IPv6 must smoothly / silently adapt to the network as it
exists, which is something that SCHC can help happen. 6LoWPAN can implicitly
derive the IPv6 address from the 8 or 16 bits address, that’s the base of the
design, with a resulting very short header; in that c
12 matches
Mail list logo
