I support this adoption. To response of challenges to use case and
applicability, I would share a concrete use case described as follows:
Companies(including CMCC) build more and more huge datacenters as the
development of business. However, not all of them comply with the newest
regulations fo
Dear 6lo,
For the past 3 weeks, I saw many people support the adoption of the
draft-li-6lo-native-short-address-03. Meanwhile, we received some concerns on
the applicability and reliability of the NSA solution as well. Regarding to the
applicability, the draft clearly states that the NSA solut
longrong wrote:
> for connection because of electromagnetic interference. Field
> supervision unit(FSU) will connect to sensor by wired technology, such
> as AI/DI/RS232/RS485/single pair ethernet. Multiple FSUs will connect
> to hierarchical supervision centers and then make data
Hello,
I would also like express my support for the adoption of this draft as it
provides a better solution for wired IoT applications as stated in the 6lo use
case draft.
Thanks,
-Marinos
> On 16 Aug 2022, at 03:08, Kiran Makhijani wrote:
>
> Hello,
> I have quickly skimmed through the
Dear all,
I have a lot of questions and some serious issues with the applicability
and the general description of the solution.
*So, there are two reasons for which I am against adoption of this
document.*
*Justification and use-case*
In terms of the positioning of this draft and justification of
Hi Alexander,
Thanks for your feedback. Please send us the tons of questions you have we will
do our best to answer them.
In general I think that the concerns that you are expressing can be solved
during the normal life cycle of a draft as a WG item.
A few more specific comments inline.
Ciao
Hi Alexander,
Thank you for reviewing our draft so detailed, it’s indeed helpful. Above
Luigi’s reply, just complement some points on technical section.
About the address length, I think you fully understand this draft, and you
should know that the average length of all packets’ header is signi
