Vijay is the one to ask about the token work. As far as the bug-fix issues, I would suspect it'll depend a lot on what comes in with the push on Friday.
On Wed, 2015-03-25 at 20:39 +0000, Lankswert, Patrick wrote: > June (et al.), > > After careful consideration, I would like to accept the ?Confirmable > Message Support?, ?CoAP Token Refactor?, ?Arduino Due Support? and > select bug fixes into the CA branch AND hold all other features until > we merge CA to master. This will frustrate the folks with Bluetooth, > IPv6 and Android API changes. However, waiting, reviewing and > validating these features is just delaying the move to master. > > I would like to know the best case for moving to master. So? > > Vijay, Erich and the DCTG folks, > > Once the token work and confirmable message support is added to CA, > how long will it take to review and refactor the RI layer? > > Jon (Cruz), Erich and the big bug bashers, > > How long do you want to address the biggest issues on CA before moving > to master? > > Validation Teams, > > How much time do you need to make one complete round of validation? > > Pat > > From: iotivity-dev-bounces at lists.iotivity.org > [mailto:iotivity-dev-bounces at lists.iotivity.org] On Behalf Of > Lankswert, Patrick > Sent: Wednesday, March 25, 2015 11:04 AM > To: 'juney at samsung.com'; 'iotivity-dev at lists.iotivity.org'; > 'felix.freimann at mediatek.com'; Bowden, George; '???'; '???' > Subject: Re: [dev] [Request for feedback] IoTivity 0.9.1 Release > Schedule & Feature > > > > > June, > > Per MJ, there are still contributions pending before CA can be merged > to master: > > ? Confirmable Message Support [ 3/27 ] > > ? CoAP Token Refactor [ 3/27 ] > > ? Bluetooth EDR/Ubuntu [ 3/27 ] > > ? Bluetooth EDR/Android [ 3/27 ] > > ? Bluetooth LE/Android [ 3/27 ] > > ? Multi-interface support [ 3/31 ] > > The first two are REQUIRED before merging to master as they would > break existing functionality in master. > > Once this work is pushed to gerrit for the CA branch, it must be > reviewed (and possibly cleaned up), the upper layers need to be > refactored to support the changes and reviewed (and possibly cleaned > up). Then testing engineering validation and merging to master. > > This is not going to be completed by 3/31. I cannot give an updated > estimate until it enters review. > > Pat > > > > From: Lankswert, Patrick > Sent: Tuesday, March 24, 2015 9:41 AM > To: juney at samsung.com; iotivity-dev at lists.iotivity.org; > felix.freimann at mediatek.com; Bowden, George; ???; ??? > Subject: RE: [dev] [Request for feedback] IoTivity 0.9.1 Release > Schedule & Feature > > > > > June, > > Spec vA is still in revision. I would not say that v0.9.1 cannot be > released on any time frame until the specification is solidified. > > Pat > > > > From: iotivity-dev-bounces at lists.iotivity.org > [mailto:iotivity-dev-bounces at lists.iotivity.org] On Behalf Of JuneYong > Young > Sent: Tuesday, March 24, 2015 6:30 AM > To: ???; iotivity-dev at lists.iotivity.org; > felix.freimann at mediatek.com; Bowden, George; ???; ??? > 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 > > > > > > > > > > > _______________________________________________ > iotivity-dev mailing list > iotivity-dev at lists.iotivity.org > https://lists.iotivity.org/mailman/listinfo/iotivity-dev
