On Wednesday, 14 March 2018 14:09:14 PDT Gregg Reynolds wrote: > > No, that means you need to fix IPv6. What you're asking for is like going > > to > > your mechanic and saying "raise the volume of the horn, because the brakes > > don't work". You need to fix your brakes instead. > > More accurately, "raise the volume on my horn, because the other guy's > brakes don't work."
I don't agree with that. Different layers in IoTivity do not make this Someone Else's Problem. It's still one codebase. > I think there's a deeper problem here: OCF conflates protocol layers. The > CRUDN messaging layer is one thing; the transport/networking layers are a > whole 'nother thing. Maybe OCF conformance should be split into > application, transport, and networking level conformance. OCF Certification requires IPv6 and that's not going to change. Your device must support it. Because of that, a bug affecting IPv4 is not a showstopper for local network, since IPv6 must be there. IoTivity should still fix the bug and if you don't care about passing OCF certification, it may be even important for you. > Suppose I have an engine that supports OCF messaging and data model, but > only over TCP/IP. I do not see why that should not be considered > conformant. Certification is a choice. Specifically, we need to choose a combination to require all devices to speak, so that they can talk to each other. If we allow a range of choices so that two devices can be compliant, receive the logo, be on the same network, and not talk to each other, we lose the value of the brand. > Call it OCF/TCP/IPv4 conformant. If you want something for constrained > environments, you want OCF/UDP/IPv6 conformant. Please explain this to your grandmother. > Note that the analog of OCF, namely HTTP, does not mandate a transport > layer, let alone a networking layer. That's not the analog of OCF. HTTP's analog in the OCF world is CoAP and that does not require IPv6. OCF's analog in the HTTP world would be a particular HTTP application or website. For example, we can say it's the web app that controls my Mitsubishi air conditioner (Kumocloud). That particular service requires IPv4. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center _______________________________________________ iotivity-dev mailing list [email protected] https://lists.iotivity.org/mailman/listinfo/iotivity-dev
