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 solution is suitable for “scenarios and applications with static network topologies and stable network connections leveraging on wired technologies…” In the draft-ietf-6lo-use-cases-13, it lists at least 2 use cases using wireline technologies. For instance the smart grid use case has wide applicability, which typically contains a star/tree-based topology as indicated in the 6lo-use-case draft and many other academic publications.* NSA can be perfectly applied here. On top of that, smart manufacturing as indicated in the Kiran’s email is another use case example. In the shop floor of a factory, most of the devices are connected in wire. In the light of Industry 4.0, the manufacturers expects the sensors and actuators deployed in the shop floor can communicate to the cloud directly. NSA could be a good candidate to bridge most of the industrial Ethernet protocols (e.g. EtherCAT, Sercos, Powerlink, cc-link IE, etc.) towards the Internet. The one mentioned by Rong is another good example. Another concern is the reliability. As NSA is suitable for wireline use cases, the system stability is by nature much higher than wireless systems. In the smart grid use case for instance, I believe the NSA solution defined in the draft-li-6lo-native-short-address-03 could work. One may argue when the electricity is down, the network is off. But in reality, power outage doesn’t happen so often. Anyway, based on the feedback from the community, we wrote another draft-li-nsa-reliability-00 to illustrate how to further improve the reliability of the system by adding an extra redundant link to make sure that one child will have at least 2 parents. We may dive into deep discussion on the reliability draft in a separate thread. As one of the authors, I support the WG adoption of the draft-li-6lo-native-short-address-03. *D. Seo, H. Lee, A. Perrig, “Secure and Efficient Capability-Based Power Management in the Smart Grid”, IEEE Ninth International Symposium on Parallel and Distributed Processing with Applications Workshops, May 2011 *T. Hartmann, F. Fouquet, J. Klein, et. Al, “Generating realistic Smart Grid communication topologies based on real-data”, IEEE International Conference on Smart Grid Communications (SmartGridComm), November, 2014
Kind regards David Lou -----Original Message----- From: 6lo [mailto:6lo-boun...@ietf.org] On Behalf Of longrong Sent: Friday, 19 August 2022 10:33 To: 6lo@ietf.org Subject: Re: [6lo] Call for WG adoption of draft-li-6lo-native-short-address-03 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 for power & environment(P&E) supervision. So, there are requirements to setup extra P&E supervision sensors and devices in those datacenters. The current P&E supervision system employ Field Supervision Unit(FSU) for data transmission and power supply, however, due to the shortage of ports and limitation of voltage supply, FSU cannot fulfill the massive sensor requirement of the smart/intelligent datacenter, which often requires over 600 or 1000 sensors, so additional power supply or batteries are often used. In this case, although massive sensors can help reduce the power consumption of datacenter cooling, but the data transmission of those sensors also caused huge power consumption, which can be improved by low power transmission protocol. And wireless is not the most optimized approach 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 communication with supervision platform by IPv6. I believe the NSA solution is a good attempt to be used in this use case. And Data center supervision is just one typical use case, with emerging of various smart applications, massive terminal or sensors connection will become regular method, thus a low power transmission method is necessary for reduce heavy power consumption. Research Institute of China Mobile 32 West XuanWuMen Ave, Xichen District, Beijing 100053, China Mobile：13701354531 E-mail：longr...@chinamobile.com -----Original Message----- From: 6lo <6lo-boun...@ietf.org> On Behalf Of Michael Richardson Sent: Friday, August 12, 2022 11:43 PM To: 6lo <6lo@ietf.org> Subject: Re: [6lo] Call for WG adoption of draft-li-6lo-native-short-address-03 > believe that it has positive feedback from 6lo WG. As Pascal said, > this draft has better to consider the narrow applicability and try to > find a common/general use case. Why would we spend time on a document that hasn't got a clear use case? I watched the 6lo recording (conflict with jwp BOF) yesterday, and the question about resiliency and alternate paths is a very serious one. Is this a routing protocol or not? I do not support adoption of the document. -- Michael Richardson <mcr+i...@sandelman.ca> . o O ( IPv6 IøT consulting ) Sandelman Software Works Inc, Ottawa and Worldwide _______________________________________________ 6lo mailing list 6lo@ietf.org https://www.ietf.org/mailman/listinfo/6lo _______________________________________________ 6lo mailing list 6lo@ietf.org https://www.ietf.org/mailman/listinfo/6lo
