Stephane, I don't have a larger view of the platforms we support, so I can't answer your question directly.
A larger issue is that we take network infrastructure for granted with IPv4, but we shouldn't with IPv6. All the nodes on a network might fully support IPv6, yet if the network infrastructure (platform configuration, routers, gateways, DNS servers, etc.) don't adequately support IPv6, you might not want to use IPv6. Thus, a dual stack approach is need during the transition. John From: Stephane Lejeune (stlejeun) [mailto:[email protected]] Sent: Tuesday, March 17, 2015 5:22 AM To: Light, John J Cc: iotivity-dev at lists.iotivity.org Subject: RE: IPv6 changes to IoTivity Hi John, This is a great achievement! Is there any iotivity target platform under consideration today(/or planned) that doesn't have an IPv6 stack? Thank you, Stephane. From: iotivity-dev-bounces at lists.iotivity.org<mailto:iotivity-dev-bounces at lists.iotivity.org> [mailto:[email protected]] On Behalf Of Light, John J Sent: Monday, 16 March, 2015 7:18 PM To: iotivity-dev at lists.iotivity.org<mailto:iotivity-dev at lists.iotivity.org> Subject: [dev] IPv6 changes to IoTivity We have completed the first phase of changes to support IPv6 in Iotivity. They will soon be pushed to the ca-ipv6 branch (branch of connectivity-abstraction branch). In the meantime, a document that describes the extent of the changes is attached to this message. The first phase has concentrated on IoTivity-wide changes to support a Dual Stack approach to adding IPv6 support. * It supports both IPv6 and IPv4 sending and receiving for both the Server and Client. * It only involves the Ethernet adapter in CA, but it does so without regard to interfaces, so it should work on Wi-Fi as well. * It skipped several other variations: o No DTLS support. o No Single Thread support. o No network interface support. o Only IPv6 Link Local multicast and addressing. * Aside from the obvious changes to the lowest levels of socket handling, the changes involve the round trip the IPv6 addresses make through the entire stack from top to bottom. The details of those changes are in the document. * We minimized the external changes to IoTivity. There are small upward-compatible changes to OCConnectivityType and CAConnectivityType and to the method argument for OCDoResource. The OCDevAddr structure and some helper functions were changed to handle IPv6. The rest of the changes should be transparent, but they impact nearly every level of the stack. I'll let you know when the source changes are pushed to Gerrit. (The only delay at this point is some fine points of Git artistry.) John Light Intel OTC OIC Dev group -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20150317/9efba32a/attachment.html>
