<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Dear all and Michael, <br>
</p>
<p>I am piggybacking on Michael's last mail on the IoT BCOP
document. We have been discussing this topic for a while and we
need to go further. </p>
<p>Last time, we discussed there was a brief consensus for this
subject within RIPE Scope : "<i>Best Current Operational Practice
(BCOP) document in RIPE scope for proactively mitigating IoT
attacks</i>". If there is an alternative opinion, <b>please
express</b>.</p>
<p>There were proposals from Eliot and others, that we should begin
with an <b>outline</b>. The initial outline was as follows:</p>
<p>-------</p>
<p>The threat<br>
Some background on device capabilities and limitations<br>
Who can do what to improve the situation?<br>
Devices<br>
CPE gear<br>
Upstreams<br>
IoT Manufacturers<br>
Consumers (let's not ask much)</p>
<p>-------</p>
<p>The functionality for controlling the home network traffic would
typically include:<br>
<br>
Insight in all the devices connected to the home network.<br>
Possibility to block traffic.<br>
End-user friendly GUI and traffic management possibility.<br>
Option to have the traffic management outsourced (e.g. to an
ISP).<br>
Blocking of compromised IoT devices.<br>
-------</p>
<p>We could have discussion on the following points:<br>
</p>
<p>1. Outline</p>
<p>2. Volunteers (who wish to contribute)</p>
<p>3. Champions (who will lead the work) - We could limit the number
of Champions<br>
</p>
<p>4. A deadline</p>
<p>These are my two cents. Please feel free with your
feedback/contributions.</p>
<p>Sandoche.<br>
</p>
</body>
</html>