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/20150316/f44b23c8/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: IPv6 additions to IoTivity v1.pdf
Type: application/pdf
Size: 402871 bytes
Desc: IPv6 additions to IoTivity v1.pdf
URL: 
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20150316/f44b23c8/attachment.pdf>

Reply via email to