Hi, Ashwini/Randeep


Following items are to be in this release from security perspective. Please
modify or add/delete.



-       Only coaps communication (without coap://) should be established
for secure resource (p=true case)

-       Resolve security threat in ACL table (DO should be cared in ACL
table also)

-       Multiple Ownership Transfer feature

-       dtls library replacement by mbed-dtls

-       Cloud provisioning feature for Android device.

-       How to handle Resource creation with Non secure option, in
Secured=1 mode.



BR, Uze Choi

From: [email protected] [mailto:iotivity-dev-
bounces at lists.iotivity.org] On Behalf Of ???(Uze Choi)
Sent: Wednesday, September 21, 2016 5:28 PM
To: iotivity-dev at lists.iotivity.org
Subject: Re: [dev] [WebEx info] RE: [This Week] IoTivity Bug Triage Meeting
for release.



Hi All,



Please find the meeting minutes for today?s CC given below.



Participants:


Uze Choi

Samsung


Ashwini

Samsung


Ashok Channa

Samsung



Highlights:

?         Currently registered Defects should be specified for Fix
Version/s field. If not specified, Uze will tag as IoTivity 1.2.0 for until
this coming release.

?         Security project still has items to be merged into git. It
should be shared in public. (Todo: Ashwini)

?         CoAP redirection implementation is not required for this release
(Ashok)

o   Backward compatibility could be achieved if we put the payload
versioning scheme in the next release.

?         Ask to QA function whether QA activity can include the test with
CTT tool. (Sungkyu, please check it)



BR, Uze Choi

From: [email protected] [mailto:iotivity-dev-
bounces at lists.iotivity.org] On Behalf Of ???(Uze Choi)
Sent: Wednesday, September 21, 2016 2:28 PM
To: iotivity-dev at lists.iotivity.org
Subject: [dev] [WebEx info] RE: [This Week] IoTivity Bug Triage Meeting for
release.



Hi Maintainer/Feature developer,



Please participate 1.5 hour later CC. 

This week IoTivity Bug Triage meeting schedule as follows.



This Week.

1st CC - Time: 21 Sep (Wed) 16:00~17:00. KST (For Asia/Europe time zone
people Attending)


<https://openconnectivity.webex.com/openconnectivity/j.php?MTID=m1524c94f48d
7d2f49c388c0fbe2271cc> Join WebEx meeting 

Meeting number (access code): 928 011 229              

Host key: 592524              

Meeting password:            1234      

https://openconnectivity.webex.com/openconnectivity/j.php?MTID=m1524c94f48d7
d2f49c388c0fbe2271cc



2nd CC - Time: 22 Sep (Thu) 9:00~10:00. KST (For Asia/North America time
zone people Attending) - (21 Sep 17:00~18:00 PST)


<https://openconnectivity.webex.com/openconnectivity/j.php?MTID=mff955063d5f
fe45636471c4072ab2880> Join WebEx meeting 

Meeting number (access code): 929 849 054              

Host key: 925470              

Meeting password:            1234      

https://openconnectivity.webex.com/openconnectivity/j.php?MTID=mff955063d5ff
e45636471c4072ab2880



Next Week.

Date&Time: 28 Sep (Wed) 16:00~17:00. KST (for Asia/Europe time zone people
attending)

Date&Time: 29 Sep (Thu) 9:00~10:00. KST (for Asia/North America time zone
people attending)



I requested the WebEX CC to OCF staff, you can find it from OCF OSWG
calendar. Of course I?ll announce it also.



BR, Uze Choi

From: ???(Uze Choi) [mailto:[email protected]] 
Sent: Tuesday, September 06, 2016 7:07 PM
To: iotivity-dev at lists.iotivity.org
Subject: IoTivity Bug Triage Meeting for release.



Hi Maintainer/Feature developer,



I?d like to plan to have a weekly CC on every Wed.

As the first CC for this coming release, I arranged time tomorrow as
follows.



Time: 7/9 (Wed) 16:00~17:00. KST (Asia/Europe)

Time: 7/10 (Thu) 9:00~10:00. KST (North America)



Please notify if you want to attend it.

Otherwise I?ll close to set up slot.



I?ll share the detail CC info tomorrow.

BR, Uze Choi

-------------- next part --------------
HTML ?????? ??????????????...
URL: 
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20160921/42aeab71/attachment.html>

Reply via email to