The patch for IPv6 plumbing is now complete, and it works with IPv4. I haven't been responding to comments while I finished the work. Now I will start.
I want to set some ground rules for the comments. I hope the maintainers will back me up on this. * This work is based on JIRA Issues: o IOT-475 IPv6 address family handling at the socket layer of connectivity<https://jira.iotivity.org/browse/IOT-475> o IOT-476 IPv6/IPv4 address family selection<https://jira.iotivity.org/browse/IOT-476> o IOT-477 IPv6 plumbing throughout the stack<https://jira.iotivity.org/browse/IOT-477> o IOT-488 IPv6 plumbing throughout the stack<https://jira.iotivity.org/browse/IOT-477> o IOT-489 IPv6 Presence changes<https://jira.iotivity.org/browse/IOT-489> o IOT-493 IPv6 changes to OCDoResource and OCStack.c<https://jira.iotivity.org/browse/IOT-493> o IOT-509 IPv6 support for singlethread using co-routine queues<https://jira.iotivity.org/browse/IOT-509> * The results of the work are described in the Wiki. o https://wiki.iotivity.org/ipv6 * Early description of IPv6 changes<https://wiki.iotivity.org/ipv6_changes_to_iotvity> * C API changes for IPv6<https://wiki.iotivity.org/c_api_changes_for_ipv6> * The C++ API changes for IPv6<https://wiki.iotivity.org/the_c_api_changes_for_ipv6> * Discussion of IPv6 API changes<https://wiki.iotivity.org/discussion_of_ipv6_api_changes> * IP address plumbing changes related to IPv6<https://wiki.iotivity.org/ip_address_plumbing_changes_related_to_ipv6> * You should be familiar with all these documents before making substantive comments about the patch. * Comments on the patch should concern how well the patch meets the objectives spelled out in the JIRA issues. * Comments about the need for the changes or the nature of the changes should be addressed to the JIRA Issues or the IoTivity-Dev mailing list generally. (Or even the OSWG mailing list since the API is changed.) * You should be aware that I changed a lot of code. I also avoided changing lots of code. I feel the changes I made were all related to IPv6 and necessary for moving the code base forward. In some cases, I simplified the code with my changes. I hope everyone recognizes that the IoTivity code base will have to be further simplified in order to allow us to add new features while retaining maintainability. I hope everyone involved understands the importance of getting IPv6 into the IoTivity code base. John Light Intel OTC OIC Development -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20150526/43774ebc/attachment.html>
