Chul Lee, The bracket format for IPv6 is appropriate for places like web addressing, where ambiguity can?t be handled otherwise. Here we have additional flags that resolve the ambiguity. Also, adding the brackets in the place you found the IPv6 address would add overhead to forming and processing IPv6 addresses. (For example, the text address would have to have the brackets removed before using getaddrinfo to turn it into a sockaddr.) I am confident that once people become familiar with IPv6, the existing usage will no longer confuse them. John Light Intel OTC OIC Development
From: ?? [mailto:[email protected]] Sent: Thursday, August 27, 2015 12:53 AM To: Light, John J; iotivity-dev at lists.iotivity.org Subject: Re: RE: [dev] IP address in OCClientResponse seems invalid. Dear Thiago and John, Yes this is a valid IPv6 address format. The problem is encountered from my lack of understanding about IPv6 useage. In order to resolve the security module issue in IPv6, I've uploaded new changeset(http://suprem.sec.samsung.net/gerrit/#/c/45811/) in master branch. In my opinion, If CA(Connectivity Abstraction) add square bracket as "[fe80::52b7:c3ff:fea1:9e6a]" when it generate a OCClientResponse for response handler. It will make easier for all developers who use OCStack. BR, Chul Lee. ------- Original Message ------- Sender : Light, John J<john.j.light at intel.com<mailto:john.j.light at intel.com>> Date : 2015-08-27 02:27 (GMT+09:00) Title : RE: [dev] IP address in OCClientResponse seems invalid. Chul Lee, There is nothing wrong with that address. It is a valid IPv6 address. The IoTivity stack has been able to handle IPv6 connections for several weeks. Last week a change was merged that makes IPv6 the preferred network. It uses a Dual Stack approach that allows both to work, but prefers IPv6. Of course, the security code will need to work with IPv6 as well. I am supporting that effort, in the form of answering any questions you have. You can force IoTivity to revert to IPv4-only. Let me know if you want to do that, but that can only be temporary. John Light Intel OTC OIC Development From: iotivity-dev-bounces at lists.iotivity.org<mailto:iotivity-dev-bounces at lists.iotivity.org> [mailto:[email protected]] On Behalf Of ?? Sent: Tuesday, August 25, 2015 9:17 PM To: iotivity-dev at lists.iotivity.org<mailto:iotivity-dev at lists.iotivity.org> Cc: ??? Subject: [dev] IP address in OCClientResponse seems invalid. Dear all, While testing security module(provisioning tool) with master branch. I performed the multicast device discovery. And then I try to extract endpoint information from OCCleintResponse such as IP address, etc. BTW, IP address in OCClientResponse seems invalid format as "fe80::52b7:c3ff:fea1:9e6a". Here is information for my test. - branch : latest master - Commit ID : "a3b45596b23319cc31826bd407adf80c7a69b12f" If anyone has information regarding this issue, please share to me. Thanks, Chul Lee. [cid:image001.gif at 01D0E168.D6374860] [http://ext.samsung.net/mailcheck/SeenTimeChecker?do=664566a9d0d36222b7fd8463bbd57ea006954ea5036d28ec696e920b30f6b71514e1f8fcc37c44e79dd130b31b023ef15296970253332b3707805447a154a46fcf878f9a26ce15a0] -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20150828/30f954f6/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 13168 bytes Desc: image001.gif URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20150828/30f954f6/attachment.gif>
