On 11/04/2016 08:11 AM, JORDI PALET MARTINEZ wrote:
I guess the problem is that this document is NOT targeted to CPEs:In principle these requirements apply to all hosts that connect to the Internet, but this list of requirements is specifically targeted at devices that are constrained in their capabilities, more than general-purpose programmable hosts (PCs, servers, laptops, tablets, etc.), routers, middleboxes, etc. While this is a fuzzy boundary, it reflects the current understanding of IoT. A more detailed treatment of some of the constraints of IoT devices can be found in [RFC7228].
This might be something we could discuss among the authors of draft-moore-iot-bcp. We literally started talking about the draft last Friday, so it was a rush job to get something out by Monday. My feeling is that the minimum requirements are valid across pretty much anything that connects to the network (including homenet CPEs). But if we make the document too wide in scope, people might miss it. For instance, you and I know what we mean by "Internet hosts" (and that's traditional language for the IETF community) but an IoT vendor might never think to look at such requirements. I was recently working with a client developing an embedded Internet-connected instrumentation device and I had a hard time convincing them that IETF standards (much less IETF security standards) were even applicable to their product.
So it might make sense to fork this document sooner or later for homenet, but maybe wait until revision -03 or so, so that we have the basics collected in one place? It will be more difficult to manage multiple documents in multiple working groups, because I think we'll still want to cross-check for consistency to some degree.
Also is BCP the way if we want authorities to mandate it?
My thinking is that BCP is appropriate for any standard for which interoperability cannot be tested. Otherwise the document would be stuck at Proposed Standard forever.
Keith _______________________________________________ homenet mailing list homenet@ietf.org https://www.ietf.org/mailman/listinfo/homenet
