<span style=" font-size:10pt;font-family:Courier New">Hi Sandoche,</span>
<br>
<br><span style=" font-size:10pt;font-family:Courier New">It`s always good
that we as an industry take security considerations seriously. Thus, we
can´t ignore the European movements regulating the use of CPE on the customer
side. The “BEREC Guidelines on Common Approaches to the Identification
of the Network Termination Point in different Network Topologies” has
to be taken into account. The European NRA`s are (in most cases) following
these guidelines.</span>
<br>
<br><span style=" font-size:10pt;font-family:Courier New">For me this means
that IoT security should be implemented in as little as possible devices
connection the consumer to the internet - one device if at all possible
thus avoiding stacked router scenarios that add unnecessary complexity
and possibly even more IoT security issues.</span>
<br>
<br><span style=" font-size:10pt;font-family:Courier New">See: </span><a href="https://berec.europa.eu/eng/document_register/subject_matter/berec/regulatory_best_practices/guidelines/9033-berec-guidelines-on-common-approaches-to-the-identification-of-the-network-termination-point-in-different-network-topologies"><span style=" font-size:10pt;color:#0082bf;font-family:sans-serif"><u>https://berec.europa.eu/eng/document_register/subject_matter/berec/regulatory_best_practices/guidelines/9033-berec-guidelines-on-common-approaches-to-the-identification-of-the-network-termination-point-in-different-network-topologies</u></span></a><span style=" font-size:10pt;font-family:sans-serif">
</span>
<br>
<br><span style=" font-size:10pt;font-family:Courier New"><br>
</span>
<br><span style=" font-size:10pt;font-family:Arial">Best regards,</span>
<br>
<br><span style=" font-size:10pt;font-family:Arial">Eric van Uden</span>
<br>
<br><span style=" font-size:10pt;font-family:Arial">AVM ICT GmbH</span>
<br><span style=" font-size:10pt;font-family:Arial">Country Manager Netherlands</span>
<br><span style=" font-size:10pt;font-family:Arial">Mr. van Coothlaan 10</span>
<br><span style=" font-size:10pt;font-family:Arial">6602 GT Wijchen</span>
<br><span style=" font-size:10pt;font-family:Arial">Nederland</span>
<br><span style=" font-size:10pt;font-family:Arial">Phone +31 24 6485381</span>
<br><span style=" font-size:10pt;font-family:Arial">Mobile +31 622 948356</span>
<br><span style=" font-size:10pt;font-family:Arial">e.vanuden@avm.de</span>
<br>
<br><span style=" font-size:10pt;font-family:Arial">Bezoek onze website
op </span><a href=http://nl.avm.de/><span style=" font-size:10pt;color:blue;font-family:Arial"><u>http://nl.avm.de/</u></span></a><span style=" font-size:10pt;color:#004080;font-family:Arial">
</span><span style=" font-size:10pt;color:#0082bf;font-family:Arial"><i> </i></span><span style=" font-size:10pt;font-family:Arial">
, vind ons leuk op </span><a href=https://www.facebook.com/fritzboxnederlands><span style=" font-size:10pt;color:blue;font-family:Arial"><u>Facebook</u></span></a><span style=" font-size:10pt;font-family:Arial">
of bekijk onze </span><a href=https://plus.google.com/115631098113092982023/videos><span style=" font-size:10pt;color:blue;font-family:Arial"><u>Google
+-pagina</u></span></a><span style=" font-size:10pt;font-family:Arial">
en </span><a href=https://www.youtube.com/user/fritzboxnederlands><span style=" font-size:10pt;color:blue;font-family:Arial"><u>Youtube-kanaal.</u></span></a>
<br>
<br><span style=" font-size:10pt;color:#c0c0c0;font-family:Arial">AVM GmbH
for International Communication Technology, Alt-Moabit 95, 10559 Berlin,
Germany</span>
<br><span style=" font-size:10pt;color:#c0c0c0;font-family:Arial">HRB 48220
AG Charlottenburg, CEO (Geschäftsführer): Johannes Nill</span><span style=" font-size:10pt;font-family:Courier New">
</span>
<br>
<br>
<br>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">Von:
</span><span style=" font-size:9pt;font-family:sans-serif">"sandoche
Balakrichenan" <sandoche.balakrichenan@afnic.fr></span>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">An:
</span><span style=" font-size:9pt;font-family:sans-serif">"RIPE
IoT WG" <iot-wg@ripe.net></span>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">Datum:
</span><span style=" font-size:9pt;font-family:sans-serif">13-10-2020
16:29</span>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">Betreff:
</span><span style=" font-size:9pt;font-family:sans-serif">[iot-wg]
IoT BCOP TF Document - Call for comments</span>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">Gesendet
von: </span><span style=" font-size:9pt;font-family:sans-serif">"iot-wg"
<iot-wg-bounces@ripe.net></span>
<br>
<hr noshade>
<br>
<br>
<br><span style=" font-size:12pt">Dear all, </span>
<br><span style=" font-size:12pt">The IoT BCOP TF (<i>Jim Reid, Eliott
Lear, Michael Richardson, Phil Stanhope, Peter Steinhäuser, Jelte Jansen,
Jan Zorz, Sandoche Balakrichenan</i>) has been meeting almost every friday
since RIPE 80 to produce the document titled : <i>"Architectural Considerations
for IoT Device Security in the Home - A guide for ISPs specifying CPE devices"</i>.
The intention is to publish the final version of this document as RIPE
Best Current Operational Practice (BCOP) document in the IoT scope.</span>
<br><span style=" font-size:12pt">A Pdf format of the document is attached.
Thanks for sending your comments on this document to the mailing list.
</span>
<br><span style=" font-size:12pt">Constanze & Sandoche (IoT WG Chairs)</span>
<br>
<br>
<br>
<br><span style=" font-size:2pt;font-family:sans-serif">[attachment "ripe-iot-bcop-v2-1.pdf"
deleted by Eric van Uden/AVM] </span><tt><span style=" font-size:10pt">_______________________________________________<br>
iot-wg mailing list<br>
iot-wg@ripe.net<br>
</span></tt><a href="https://mailman.ripe.net/"><tt><span style=" font-size:10pt">https://mailman.ripe.net/</span></tt></a><tt><span style=" font-size:10pt"><br>
</span></tt>
<br>
<br>