When will the upstream yocto recipe be updated for 0.9.1? On Wed, Apr 15, 2015 at 9:44 AM, Lankswert, Patrick < patrick.lankswert at intel.com> wrote:
> June, > > > > One point of note: I misspoke. I should have said that ?very few > contributors report to me directly?. I am working on getting status on all > of the features listed. > > > > Pat > > > > *From:* ???(June Yong Young) [mailto:juney at samsung.com] > *Sent:* Tuesday, April 14, 2015 9:04 PM > *To:* Lankswert, Patrick; Keany, Bernie; '???'; > iotivity-dev at lists.iotivity.org; Skarpness, Mark > *Subject:* RE: [dev] Schedule for IoTivity v0.9.1 Release > > > > Hi Pat, > > > > Maybe, I guess my thought has not been shared enough. > > The initial goal of 0.9.1 release was as below, and in conversation with > Thiago, > > I said that we were schedule driven, but we had to be feature driven > regarding some important features such as 1 branch(CA, Android API), > BT/BLE, etc > > because it can be the purpose of 0.9.1 release if 0.9.1 cannot be full > Spec vA compliant. > > > > - Main features > > . Merge CA(connectivity Abstraction) branch onto one master branch > > . BT/BLE Support, Noti. Manager, Android API (Belkin Plugin, Server) > > . Scheduled/Recursive Group Action, Secure Bootstrapping, > > . Spec vA Compliant Pre-Release > > . No OIC Spec. Conformance Test > > > > > > Now, we now see the situation as below > > - BT/BLE : delayed, need to find out when it will be completed. > > - Android API : not clear about delay, need to find out when it will > be completed. > > - Security : not full vA compliant definitely. > > > > Based on this situation, we have to judge what plan can be for 0.9.1. > > In my personal opinion, > > - if BT/BLE & Android API can be completed early(i.e end of April or early > May), I want to wait for BT/BLE & Android to be in 0.9.1. > > . Of cource, I need to get confirmation about delay of 0.9.1 release > from ISG in this case. > > - but if they are too far away from early of May, then we don?t need to > wait for BT/BLE and have to release 0.9.1 as schedule driven by 4/27. > > . In this case, we have to consider what we can annouce about 0.9.1. ( no > major feature added, no 1 branch, no vA compliant, then what?) > > > > That?s why I eagerly want to know what is the next schedule for BT/BLE, > Android API. > > > > Regards > > June > > > > > > *June Yong Young* > > Principal Engineer > > Web & Convergence Team, Software R&D Center > > Samsung Electronics Co.,Ltd. > > T: +82-31-301-6107, M: +82-10-9530-6107 > > E-mail :juney at samsung.com > > > > *From:* Lankswert, Patrick [mailto:patrick.lankswert at intel.com > <patrick.lankswert at intel.com>] > *Sent:* Wednesday, April 15, 2015 12:41 AM > *To:* juney at samsung.com; Keany, Bernie; ???; > iotivity-dev at lists.iotivity.org; Skarpness, Mark > *Subject:* RE: [dev] Schedule for IoTivity v0.9.1 Release > > > > June, > > > > I am confused. Are we schedule driven or feature driven? I am being sent > two messages regarding what must be in the release and the date that it > must be released. As very few of the contributors do not report to me, I > really can only drive to schedule (and cut features) or features (and wait > until we meet quality standards), not both. > > > > My current priorities are quality then features. With these priorities, as > Thiago and I have said it will be done when it is done. > > > > Pat > > > > *From:* iotivity-dev-bounces at lists.iotivity.org [ > mailto:iotivity-dev-bounces at lists.iotivity.org > <iotivity-dev-bounces at lists.iotivity.org>] *On Behalf Of *??? > *Sent:* Tuesday, April 14, 2015 7:51 AM > *To:* ???; Keany, Bernie; ???; iotivity-dev at lists.iotivity.org; > Skarpness, Mark > *Subject:* Re: [dev] Schedule for IoTivity v0.9.1 Release > > > > Pat, > > > > Could you feedback to BT/BLE review complete by 4/20, so that we can > release 0.9.1-RC2? > > We need a exact schedule urgently, so that we can plan 0.9.1 regarding > > - if 4/27 is possible > > - if not, when it will be possible, > > - what features to be supported if we release 0.9.1 on 4/27 as schedule > driven > > - judging the purpose of 0.9.1 > > > > Regards > > June > > > > ------------- > > 4/15 Release Iotivity Official Q/A Version IoTivity > > > > - Tag Name: 0.9.1-RC1 > > > > - CA merged version > > > > - Need to all Q/A issues > > > > 4/17 Complete merge of Android API > > > > 4/20 IoTivity v0.9.1_RC1 Test Report > > > > 4/21 Release IoTiviy 0.9.1-RC2 version, incldue followings > > > > - Tag Name: 0.9.1-RC2 > > > > - Andorid API > > > > - BT/BLE should be completed > > > > 4/24 Q/A Exit (Need consent between Q/A & Dev) > > > > 4/27 Web Site Open > > > > *June Yong Young* > > Principal Engineer > > IoT Solution Lab. | Web & Convergence Team > > Software R&D Center, Samsung Electronics Co.,Ltd. > > T: +82-31-301-6107, M: +82-10-9530-6107 > > E-mail :juney at samsung.com > > > > > > > > ------- *Original Message* ------- > > *Sender* : ???<juney at samsung.com> S6(??)/??/IoT Solution Lab(S/W??)/???? > > *Date* : 2015-04-14 19:03 (GMT+09:00) > > *Title* : Re: [dev] Schedule for IoTivity v0.9.1 Release > > > > Hi Bernie, > > > > Junmo?s schedule is not new one. The schedule below & in the attached mail > was shared on 3/24 and discussion has been on-going. > > And actually April release as Spec vA compliant release was reported to > BoD at the OIC OSWG F2F meeting. > > IoTivity QA release was supposed to start from 4/6, but it is being > delayed by almost 2 weeks. > > > > We need to get excat schedule to complete Android API, so that we can make > a plan for 0.9.1 release. > > So, I?d like you to discuss with Uze and Junmo and find out when Android > API review can be completed. > > > > Regards > > June > > > > > > ------------ > > > > - Schedule > > . 4/6, entry to QA as the official release > > . 4/24, exit from QA > > . 4/27, Website Open > > . Targetting 3 times release to QA before open, 3 days test required per > each QA turn > > . Snapshot release to be made on master branch (not creating release > branch) > > > > - Main features > > . Merge CA(connectivity Abstraction) branch onto one master branch > > . BT/BLE Support, Noti. Manager, Android API (Belkin Plugin, Server) > > . Scheduled/Recursive Group Action, Secure Bootstrapping, > > . Spec vA Compliant Pre-Release > > . No OIC Spec. Conformance Test > > > > - QA > > . Need Full QA test although revision release is to run basic TCs > > because there lots of changes since 0.9.0 > > . Refer to QA criteria in the attached(QA_criteria_major > release_v1_150313.pptx) > > : not finalized, still under discussion among IoTivity member company > QA teams. > > > > > > > > June Yong Young > > > > Principal Engineer > > Web & Convergence Team, Software R&D Center > > Samsung Electronics Co.,Ltd. > > > > T: +82-31-301-6107, M: +82-10-9530-6107 > > E-mail :juney at samsung.com > > > > > > -----Original Message----- > From: iotivity-dev-bounces at lists.iotivity.org [ > mailto:iotivity-dev-bounces at lists.iotivity.org > <iotivity-dev-bounces at lists.iotivity.org>] On Behalf Of Keany, Bernie > Sent: Tuesday, April 14, 2015 10:12 AM > To: junmo2.yang at samsung.com; iotivity-dev at lists.iotivity.org > Subject: Re: [dev] Schedule for IoTivity v0.9.1 Release > > > > Hello Junmo > > > > If this schedule has ever been shared I have never seen it and it is > contrary to any timeline that I have presented either at the Face-to-Face > in Santa Clara or in OSWG or DCTG calls since the beginning of the year. > > > > Starting with the Android API .. > > As I?ve reported the Android API is on it?s own branch which has been > based on the Master branch, over the course of 0.9.0 we?ve pulled changes > committed into Master out to the Android API. We have never been able to > rebase against the CA branch as until very recently the CA branch would not > build for Android. In fact, even today after the merge we?re still not able > to build Master for Android (our developers will send an output log shortly > as the build limitation is in the connectivity directory). > > > > Once the have a stable Master branch that builds for Android we can > integrated the Android API branch into Master this is about 13K lines of > code including unit tests, samples and the Java API and JNI implementation. > This process should take about a week and then we will be ready to push the > code for review to the Master Branch. Depending on how long the review > takes if the decision is to hold the 0.9.1 release for the Android API then > testing will want to verify the resulting base and a release can be done. > Alternatively you can release 0.9.1 without the Android API and it can be > included in 0.9.2 the PPRTG can make a recommendation on the best course of > action. > > > > The BT/BLE feature you?ve mentioned is not clear, is it intended to be the > Linux capability for the OIC GATT Service Profile? > > If it is then there are two clarifications we need to consider. The code > for the OIC GATT service profile that we shared in the DCTG some weeks ago > should be code complete by the end of April and then it could be pushed for > review. The implementation is not complete yet but is will be a > significant amount of code and will need careful review. The second and > more important point is that the Linux implementation would not be > interoperable with the Android or Tizen versions that are part of Master > today. The issues about the differences in the protocol specification have > been documented and discussed in DCTG calls but there has been no > commitment for the protocol in the Android and Tizen implementations to be > modified to match the specification and implementation of the Linux > capability. > > > > In summary, the dates are mentioned in schedule that appears below are not > achievable, the likely dates would be: > > Android-API push for review April 22nd assuming the build for Android > issues are fixed today or tomorrow. > > OIC GATT Service Profile for Linux would push for review the week of the > April 27th. > > Availability for release would be dependent on the review process for both > components. > > > > Please let me know if you have any questions. > > > > Bernie Keany > > Principal Engineer > > OIC Development Engineering Team, Open Source Technology Center. > > > > > > > > > > From: ??? <junmo2.yang at samsung.com<mailto:junmo2.yang at samsung.com>> > > Reply-To: "junmo2.yang at samsung.com<mailto:junmo2.yang at samsung.com>" < > junmo2.yang at samsung.com<mailto:junmo2.yang at samsung.com>> > > Date: Sunday, April 12, 2015 at 11:24 PM > > To: " > iotivity-dev at lists.iotivity.org<mailto:iotivity-dev at > lists.iotivity.org>" < > iotivity-dev at lists.iotivity.org<mailto:iotivity-dev at lists.iotivity.org>> > > Subject: [dev] Schedule for IoTivity v0.9.1 Release > > > > > > Dear IoTivity Dev. Members, > > > > > > > > I'd like to kindly remind the schedlue of Iotivity v0.9.1. > > > > If anyone has any comment or suggestion, please share it. > > > > > > > > 4/15 Release Iotivity Official Q/A Version IoTivity > > > > - Tag Name: 0.9.1-RC1 > > > > - CA merged version > > > > - Need to all Q/A issues > > > > 4/17 Complete merge of Android API > > > > 4/20 IoTivity v0.9.1_RC1 Test Report > > > > 4/21 Release IoTiviy 0.9.1-RC2 version, incldue followings > > > > - Tag Name: 0.9.1-RC2 > > > > - Andorid API > > > > - BT/BLE should be completed > > > > 4/24 Q/A Exit (Need consent between Q/A & Dev) > > > > 4/27 Web Site Open > > > > > > > > BR, > > > > - Junmo Yang > > > > > > > > > > ??? (Junmo Yang, Ph.D.) > > Principal Engineer > > IoT Solution Lab./Web & Convergence Team Software R&D Center, Samsung > Electronics Co.,Ltd. > > Mobile: +82-10-7260-7032 E-mail: > junmo2.yang at samsung.com<mailto:junmo2.yang at samsung.com> > > > > > > > > [cid:MKNRCZHWKC3T at namo.co.kr] > > > > > > > > > -------Original Message-------- > Sent: "JuneYong Young" <juney at samsung.com> > Date: Tue, 24 Mar 2015 19:29:32 +0900 > > Subject: Re: [dev] [Request for feedback] IoTivity 0.9.1 Release Schedule & > Feature > > One thing important is missing in blue below. > > IoTivity 0.9.1 should be Spec vA Compliant Pre-release, so please check if > anything important that can not be released and let us know > > > > Hi George, Felix, > > I'm still waiting for your feedback about the QA release schedule and > features to be added. > > Would you please check this out? > > > > Hi JunMo,(He is in Samsung release management function) > > Whould you please gather the feature list from George and Felix? > > > > Regards > > June > > > > *June Yong Young* > > Principal Engineer > > IoT Solution Lab. | Web & Convergence Team > > Software R&D Center, Samsung Electronics Co.,Ltd. > > T: +82-31-301-6107, M: +82-10-9530-6107 > > E-mail :juney at samsung.com > > > > > > > > ------- *Original Message* ------- > > *Sender* : ???<juney at samsung.com> S6(??)/??/IoT Solution Lab(S/W??)/???? > > *Date* : 2015-03-17 13:56 (GMT+09:00) > > *Title* : [dev] [Request for feedback] IoTivity 0.9.1 Release Schedule & > Feature > > > > Dear IoTivity Members > > > > This is the announcement for IoTivity 0.9.1 release schedule in April. > > (IoTivity 1.0.0 is to be released as full compliant of the Spec in around > Sep./Oct. timeframe according the direction of BoD.) > > *Please let us know your opinion about the schedule and confirm the > features to be applied in April release.* > > > > - Schedule > > . 4/6, entry to QA as the official release > > . 4/24, exit from QA > > . 4/27, Website Open > > . Targetting 3 times release to QA before open, 3 days test required per > each QA turn > > . Snapshot release to be made on master branch (not creating release > branch) > > > > - Main features > > . Merge CA(connectivity Abstraction) branch onto one master branch > > . BT/BLE Support, Noti. Manager, Android API (Belkin Plugin, Server) > > . Scheduled/Recursive Group Action, Secure Bootstrapping, > > . Spec vA Compliant Pre-Release > > . No OIC Spec. Conformance Test > > > > - QA > > . Need Full QA test although revision release is to run basic TCs > > because there lots of changes since 0.9.0 > > . Refer to QA criteria in the attached(QA_criteria_major > release_v1_150313.pptx) > > : not finalized, still under discussion among IoTivity member company > QA teams. > > > > - Featues to be added > > . *Please let us all know any additional features* which are not > addressed in the exel file.(IoTivity_Features_0.9.0_0.9.1_eng_150313.xlsx) > > > > > > George, Felix, > > > > Please refer to the feaures sorted out in the exel file and > please feedback the features to be added from your side for 0.9.1. > > > > > > Regards > > June > > > > > > *Features on V0.9.0 vs V0.9.1* > > *Features* > > *V0.9.0* > > *V0.9.1* > > *Ownership* > > *Feature* > > *Detail* > > *Remark* > > *12-30* > > *4-27* > > *????* > > *Company* > > Notification > Manager > > Lite Device Resource Discovery > > N > > Y > > Samsung > > Formation of the Virtual Resource for Lite Device > > N > > Y > > Samsung > > Resource proxy instead of Lite Device using Virtual Resource > > N > > Y > > Samsung > > Soft Sensor > Manager > > ?Physical Sensor Data Listening > > Y > > Y > > Samsung > > Developing template for Sensor Fusion as a library andDeploying/Executing > the library > > Y > > Y > > Samsung > > Query-based Sensor Data Request > > Y > > Y > > Samsung > > Reference soft sensors > > Y > > Y > > Samsung > > Bridging in a local network using Pluggable Protocols Converters > > Y > > Y > > Samsung > > Protocol Plugin > > C/C++ and Java Support for Multi Platforms > - Linux, Android, Tizen > > N > > Y > > Samsung > > Hue Plugin with JAVA (Android only) > - On/Off, Change Color, Dimming > > N > > Y > > Samsung > > MQTT Plugin with C/C++ > - FAN On/Off > > Y > > Y > > Samsung > > Gear Plugin with Java(Android only) > - Notification to Gear > - User Activity Event Receiving from Gear > > Y > > Y > > Samsung > > Belkin Wemo Plugin with Java(Android only) > - Motion Sensor, Switch On/Off > > N > > Y > > Samsung > > Things Manager > > Find appropriate resources for the specific group > > Y > > Y > > Samsung > > Find/Create/Delete a group > > Y > > Y > > Samsung > > Join/Leave > > Y > > Y > > Samsung > > Let the other devices to join the specific group > > Y > > Y > > Samsung > > Get the information of all groups > > Y > > Y > > Samsung > > Check presence information of group (member resource's > connectivity/resource change) > > Y > > Y > > Samsung > > Take a single action on a group to affect all member resources (Group > Action using ActionSet) > > Y > > Y > > Samsung > > CRUD function for ActionSet > > Y > > Y > > Samsung > > Send configuration/diagnostics command to multiple things > > Y > > Y > > Samsung > > Get the parameter list of configuration feature > > Y > > Y > > Samsung > > Get the functionality list of diagnostics feature > > Y > > Y > > Samsung > > Control Manager > > Provides framework and services to implement a Controller with Smart Home > Data Model > > Y > > Y > > Samsung > > Provides RESTful Resource Request/Response handler with Device Discovery > and Subscription/Notification Manager > > Y > > Y > > Samsung > > Provides framework and services to implement a Controlee > > Y > > Y > > Samsung > > Provides RESTful Resource request Handler to perform the action requested > by the Controllers > > Y > > Y > > Samsung > > Provides discovery of the devices and resources a device hosts > > Y > > Y > > Samsung > > Handles subscription requests from the Controllers > > Y > > Y > > Samsung > > Provides HTTP based REST framework for Control Manager > > Y > > Y > > Samsung > > Android Support > > Supports client side Java APIs for Android > > Y > > Y > > Intel > > Requires Android NDK version 10 or later > > Y > > Y > > Intel > > Requires Android SDK API level 19 > > Y > > Y > > Intel > > Sample applications demonstrate Java SDK > > Y > > Y > > Intel > > Android API refactoring and completion (Server API Support) > > N > > Y > > Intel/Samsung > > Security > > Adds TLS_ECDH_anon_WITH_AES_128_CBC_SHA cipher suite in tinyDTLS for > unauthenticated security configuration only > > ? > > Y > > Samsung > > Authentication method during security configuration (by checking confirm > code in the device which has display) > > ? > > Y > > Samsung > > Security Configuration(BootStrapping) API for admin device & sample > > ? > > Y > > Samsung > > Security Resource Manager > > ? > > TBD > > Intel/Samsung > > Connectivity Abstraction > > This feature integrates the resource model (aka Resource Introspection - > RI) and Connectivity Abstraction (CA) layers. > > Y > > Y > > Intel > > The CA layer provides abstraction to the RI layer from adaptors and > transport protocols. This release showcases the integration of RI and CA > layers over multiple heterogeneous adaptors (Wi-Fi and Ethernet). > > Y > > Y > > Samsung > > Features existing with RI and CA integration- Discovery (multicast and > unicast), GET, PUT, POST, DELETE and Observe and Active Discovery (aka > presence). > > Y > > Y > > Samsung > > Supports both secure and non-secure resources. > > Y > > Y > > Samsung > > The user has the option to include/exclude the CA layer using compiler > flag CA_INT. In the current code by default the CA_INT compiler flag is > included and hence the CA layer is included. > > Y > > Y > > Intel > > Some of the C/C++ APIs have changed for CA integration. These changes are > included in the CA_INT flag in the header files. > > Y > > Y > > Intel > > During resource discovery it is possible for the same resource to be > discovered on multiple adaptors. To resolve this a Server Identifier (SID) > is included in the resource discovery response. > > Y > > Y > > Intel > > The discovery response also includes the adaptor type on which the > resource was discovered (Ethernet, Wi-Fi, etc) and this information is > passed to the application. If the same resource is reachable via multiple > adaptors, i.e. it has been discovered on multiple connectivity types, the > application must specify which interface to use for subsequent > GET/PUT/POST/DELETE/observe operations. > > Y > > Y > > Samsung > > Unicast discovery uses port 5683; multicast discovery uses port 5298 > > Y > > Y > > Samsung > > Sample application demonstrating CA integration: > - ocserver and occlient in C sample. > - simpleserver and simpleclient C++ sample. > - presenceserver C31and presenceclient C++ sample. > > Y > > Y > > Samsung > > BT/BLE Support > > N > > Y > > Samsung > > ?Support for HIGH QoS. > > N > > Y > > Samsung > > slow response. > > N > > Y > > Samsung > > Device discovery works on a single adaptor. > > N > > Y > > Samsung > > Only unicast presence supported. > > N > > Y > > Samsung > > CA integration has been tested only on Ubuntu. > > N > > Y > > Samsung > > Discovery and Connectivity > > CoAP model- IoTvity supports information exchange and control based on the > messaging/CoAP model. IoTivity also manages radio connections between > devices (Wi-Fi, LAN) and across any available transport, whether it?s > device-to-device or across the same network > > Intel > > Discovery- This feature provides discovery mechanisms for finding > resources in proximity. > > Intel > > Device Discovery- This feature provides a mechanism to find devices based > on specific device-level attributes. > > Intel > > Active Discovery- This feature provides presence notifications based on a) > a resource coming online or b) a change in a resource's properties or c) a > resource going offline. It allows a client to subscribe/unsubscribe > (unicast or multicast) for presence notifications. > > Intel > > Resource Management > > Resource model operations- IoTivity supports fundamental resource model > based operations such as GET, PUT, POST, DELETE apart from Observations and > its notifications. Observe notifications can be sent to all clients or to a > specific set of clients. > > Intel > > Entity Handler support- This allows a server app developer to handle > incoming client requests and respond after processing the requests. A > default device entity handler is also supported to handle a request that > does not match the existing registered resource. > > Intel > > Header Options support- This feature allows the client to send custom > header options to the server and vice-versa. > > Intel > > QoS support- This feature allows the app developer to choose the quality > of service which currently translates to non-confirmable (LOW_QoS) and > confirmable (HIGH_QoS) in CoAP. > > Intel > > SDK- The SDK abstracts all the OS APIs for radio connections into simpler > APIs. SDK provides APIs for platform initialization > (Client/Server/Client-Server mode in In-Proc model), discovery of > resources, discovery of devices, registration/creation of resources and > resource model operations. > > Intel > > Collection- This feature provides a root resource to point to other > resources. This features includes operations on default, linklist and batch > interfaces on a collection resource. > > Intel > > JSON format- IoTivity uses JSON data format with JSON serialization and > de-serialization in C++ SDK layer. > > Intel > > Slow response- This feature allows a server application to indicate 'slow > response' to a client on an incoming request. This enables the server > process the request, then send a response at a later time. > > Intel > > Security- This feature provides security that allows app developers to > create secure resources and communicate with resources in a secured channel. > > Intel > > Tizen Support > > IoTivity project build supported on Tizen 2.3 and 3.0 (both on IA and ARM > version) > > Intel > > No new specific APIs for Tizen; Tizen development support and build > process provided in "Readme.scons.txt" > > Intel > > Yocto Support > > meta-oic software layer for Yocto separately hosted on > git.yoctoproject.org. > > Intel > > Contains recipes to build the IoTivity framework and SDK for Yocto based > embedded targets. > > Intel > > Can utilize Yocto provisioned infrastructure to construct target > toolchains to cross-compile IoTivity applications for that target. > > Intel > > Tested successfully on Intel Edison and MinnowBoard MAX platforms. > > Intel > > Currently supports the resource layer (runtimes and applications) of the > IoTivity stack. > > Intel > > OICSensorBoard provides sample IoTivity application for the Intel Edison > Platform. > > Intel > > Demonstrates IoTivity Server capabilities on the Edison through the > integration of an add-on breadboard that hosts temperature, ambient light > and LED resources. > > Intel > > Client-server functionality successfully tested by building server using > Yocto toolchain for Edison and client for Ubuntu. > > Intel > > Fully documented connection diagram of sensors to Edison, build > configuration, supported IoTivity interfaces and methods, and client/server. > > Intel > > Scons Support > > SCons provides cross-platform build tool. > > Intel > > IoTivity project can be built on Linux, Windows, MAC OSX for various > OS(Linux, Tizen, Android, Arduino, Windos, MAC OSX, iOS). > SCons readme file available at parent folder 'iotivity'. > > Intel > > > > > > *June Yong Young* > > Principal Engineer > > IoT Solution Lab. | Web & Convergence Team > > Software R&D Center, Samsung Electronics Co.,Ltd. > > T: +82-31-301-6107, M: +82-10-9530-6107 > > E-mail :juney at samsung.com > > > > [image: cid:image001.gif at 01D0775A.947D8380] > > [image: > http://ext.samsung.net/mailcheck/SeenTimeChecker?do=d083a0c0528fae522cfd0bc800463dcdac3e5864f9d7d54bc13f49ee879cb6cf65afe93a9dd766927f71ac62d5c138b2195f377979c7bbe51b20909a04efd4d2748cfe1d4e847419cf878f9a26ce15a0] > > _______________________________________________ > iotivity-dev mailing list > iotivity-dev at lists.iotivity.org > https://lists.iotivity.org/mailman/listinfo/iotivity-dev > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20150415/34b6829a/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 13168 bytes Desc: not available URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20150415/34b6829a/attachment.gif>
