<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style></style></head><body lang=ES link=blue vlink=purple style='word-wrap:break-word'><div class=WordSection1>Hi Elliot, all,<o:p></o:p><o:p> </o:p>Fine with most of the points, especially if there are changes for CHIP or ETSI to dig on those issues.<o:p></o:p><o:p> </o:p>Regarding the numbering, I fully understand that the final page numbering depends on the RIPE publication … however, because the “draft” document has an index/ToC, it should not be too much difficult, to improve readability when you forward the new version, to include pages numbers already. It helps to be able to follow the index and also to be able to refer to specific issues, etc.<o:p></o:p><o:p> </o:p><div>Finally, regarding terminology, in the BCOP WG we had this discussion several times, and it seems that in general people prefers to have a specific terminology section. See for example RIPE-690, last section. I’m personally fine either way.<o:p></o:p><o:p> </o:p>Regards,<o:p></o:p>Jordi<o:p></o:p>@jordipalet<o:p></o:p><o:p> </o:p></div><o:p> </o:p><o:p> </o:p><div><div>El 26/2/21 15:45, "iot-wg en nombre de Eliot Lear" <<a href="mailto:iot-wg-bounces@ripe.net">iot-wg-bounces@ripe.net</a> en nombre de <a href="mailto:lear@lear.ch">lear@lear.ch</a>> escribió:<o:p></o:p></div></div><div><o:p> </o:p></div>Hi all,<o:p></o:p>Here are the proposed resolutions to the comments raised:<o:p></o:p><o:p> </o:p><div>On 12.02.21 17:16, JORDI PALET MARTINEZ via iot-wg wrote:<o:p></o:p></div><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'>Hi all,<o:p></o:p> <o:p></o:p>I’m not sure if this should be considered in this document or other future ones, or other foras.<o:p></o:p> <o:p></o:p><![if !supportLists]>1. <![endif]>Should IoT devices be allowed to send information to the cloud “always” or the user must have the choice to disable that? I’ve seen many devices, even CPEs, using OpenWRT or a derivative firmware, sending stuff to the manufacturer, “hijacking DNS”, etc. This may be even a regulatory issue.<o:p></o:p></blockquote><o:p> </o:p>As Michael alluded, this might be suitable for a different document, but ours is more focused on guidance for ISPs and firewall manufacturers, and less so toward IoT device manufacturers, particularly when it comes to regulatory compliance matters.<o:p></o:p><o:p> </o:p><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><![if !supportLists]>2. <![endif]><o:p> </o:p> <o:p></o:p><![if !supportLists]>3. <![endif]>Should IoT devices have a standard API to be managed? Otherwise, consumers are unprotected and they may need to throw to the trash can hundreds of euros in case of a manufacturer Cloud failure, vendor bankruptcy, vendor failure to provide security updates, etc., etc.<o:p></o:p></blockquote>While the authors agree that this is an important issue, it seems like one to be taken up in a different document for the reasons discussed above. This may be a better topic for ETSI. I will also note that there is the possibility that the Connected Home IP Alliance (CHIP) will be going right there very soon.<o:p></o:p><o:p> </o:p><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'> <o:p></o:p>In my opinion both are related to device security in the Home. I’m also not saying is in the scope of this WG, as said, it may come to IETF, other standardizations foras, even regulation. It is like when we regulate if a device complies with FCC, CE mark, UL, etc., etc., but in terms of security or consumer protection.<o:p></o:p></blockquote>Agree, but see above.<o:p></o:p><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'> <o:p></o:p><div>One last point. I think it will be very useful to have page numbers in this (and every) document … also in other BCOP documents, we added an annex with terminology.<o:p></o:p></div></blockquote>Page numbering depends on the publication format, and that is up to RIPE NCC, not the authors. We do explain the terminology as we go, and this is not a lengthy document that risks bloating a bit. Unless people insist, we would rather not.<o:p></o:p>Toma asked for some slight modifications to the text relating to there being only two L4 protocols. We propose the following changes:<o:p></o:p>"Comparing internet layer and layer four information to known deny-lists ("blocklists")" <o:p></o:p>and <o:p></o:p>"Validating that the internet layer and layer four information matches an associated MUD profile"<o:p></o:p>Martin asked for a reference to ntopng. We have added a footnote that points to ntop.org.<o:p></o:p>We'll send an updated version shortly, assuming nobody objects to these resolutions.<o:p></o:p>For the authors,<o:p></o:p>Eliot<o:p></o:p><o:p> </o:p><o:p> </o:p><o:p> </o:p><o:p> </o:p><o:p> </o:p><o:p> </o:p><o:p> </o:p><o:p> </o:p>_______________________________________________ iot-wg mailing list iot-wg@ripe.net https://lists.ripe.net/mailman/listinfo/iot-wg <o:p></o:p></div> ********************************************** IPv4 is over Are you ready for the new Internet ? http://www.theipv6company.com The IPv6 Company This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it. </body></html>