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 TF Document - Call for comments
- Previous message (by thread): [iot-wg] IoT BCOP TF Document - Call for comments
- Next message (by thread): [iot-wg] IoT BCOP TF Document - Call for comments
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Michael Richardson
mcr+ietf at sandelman.ca
Fri Oct 23 16:24:38 CEST 2020
<#secure method=pgpmime mode=sign> sb> The IoT BCOP TF (/Jim Reid, Eliott Lear, Michael Richardson, Phil sb> Stanhope, Peter Steinhäuser, Jelte Jansen, Jan Zorz, Sandoche sb> Balakrichenan/) has been meeting almost every friday since RIPE 80 to sb> produce the document titled : /"Architectural Considerations for IoT sb> Device Security in the Home - //A guide for ISPs specifying CPE sb> devices"/. The intention is to publish the final version of this sb> document as RIPE Best Current Operational Practice (BCOP) document in sb> the IoT scope. Some feedback that we have received is that the document isn't able to provide clear guidance that would make it a BCOP. It is perhaps more of a technical report. An initial goal had been to be able to say what ISPs are currently doing with IoT devices, and thereby enable those who are writing RFPs to know what kind of things they might expect to be able to ask for. But, it's still too soon for that. So a question is: what category should we put on this document? -- Michael Richardson <mcr+IETF at sandelman.ca> . o O ( IPv6 IøT consulting ) Sandelman Software Works Inc, Ottawa and Worldwide
- Previous message (by thread): [iot-wg] IoT BCOP TF Document - Call for comments
- Next message (by thread): [iot-wg] IoT BCOP TF Document - Call for comments
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ iot-wg Archives ]