This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[iot-wg] IoT BCOP Document
- Previous message (by thread): [iot-wg] IoT BCOP Document
- Next message (by thread): [iot-wg] New on RIPE Labs: Visualisations of Periodic IoT Traffic
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
sandoche Balakrichenan
sandoche.balakrichenan at afnic.fr
Wed Mar 18 13:14:22 CET 2020
Dear all, The mail below has been intended for the Volunteers who have volunteered during RIPE 79 to write the BCOP. Jim is championing this document and if any of you would like to contribute, please contact Jim. Sandoche. On 18/03/2020 11:13, sandoche Balakrichenan wrote: > > Dear all and Michael, > > 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. > > Last time, we discussed there was a brief consensus for this subject > within RIPE Scope : "/Best Current Operational Practice (BCOP) > document in RIPE scope for proactively mitigating IoT attacks/". If > there is an alternative opinion, *please express*. > > There were proposals from Eliot and others, that we should begin with > an *outline*. The initial outline was as follows: > > ------- > > The threat >    Some background on device capabilities and limitations >    Who can do what to improve the situation? >        Devices >        CPE gear >        Upstreams >        IoT Manufacturers >        Consumers (let's not ask much) > > ------- > > The functionality for controlling the home network traffic would > typically include: > >    Insight in all the devices connected to the home network. >    Possibility to block traffic. >    End-user friendly GUI and traffic management possibility. >    Option to have the traffic management outsourced (e.g. to an ISP). >    Blocking of compromised IoT devices. > ------- > > We could have discussion on the following points: > > 1. Outline > > 2. Volunteers (who wish to contribute) > > 3. Champions (who will lead the work) - We could limit the number of > Champions > > 4. A deadline > > These are my two cents. Please feel free with your feedback/contributions. > > Sandoche. > > > _______________________________________________ > iot-wg mailing list > iot-wg at ripe.net > https://mailman.ripe.net/ -------------- next part -------------- An HTML attachment was scrubbed... URL: </ripe/mail/archives/iot-wg/attachments/20200318/9634db1e/attachment.html>
- Previous message (by thread): [iot-wg] IoT BCOP Document
- Next message (by thread): [iot-wg] New on RIPE Labs: Visualisations of Periodic IoT Traffic
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ iot-wg Archives ]