Hi Uze,


I?ll let Nathan and/or Dongik provide specific details about any Security-
related issues if needed.  Here is my understanding of where we are right
now:



Items to be fixed on CTT v1.4

?         CT1.7.7.1 updated to append ACE with random UUID rather than
adding a ?*? ACE for /oic/p which already exists

?         Update CT1.7.8.1 for Clients - CTT sends a GET to /oic/d which
has an ACE installed

?         Update CT1.7.8.2 to allow any 4.xx error code (CTT now allows
4.01 Unauthorized only)

?         Update to align with Security CR46 which allows only doxm and
pstat to be accessed over CoAP rather than all SVRs.  There is already an
IoTivity patch for this (#14137)



Items still to be fixed on IoTivity v1.2-rel

?         IPv4/IPv6 changes as discussed by Thiago

?         NON block-wise transfer (current analysis indicates this is an
IoTivity issue - email attached)

?         Add Policy ?p? to any Collection as discussed by Joey from
Intel (email attached)



Items to be added to the IoTivity Reference Device or still to be tested:

?         Collections

?         Run all sever-role test cases against a device that is primarily
in the Client role



Core schema file changes (Richard)

?         Update changes to OIC Link schema file as agreed at the F2F

?         Update OIC Link schema file to address issues found by Comarch
(pull request 30)



Thanks,

Mitch



From: ??? (Uze Choi) [mailto:[email protected]] 
Sent: Sunday, November 20, 2016 11:32 PM
To: ???; Heldt-Sheller, Nathan; Mitch Kettrick
Cc: iotivity-dev at lists.iotivity.org; cert_wg at openconnectivity.org
Subject: CTT Gap status sharing request



Hi Nathan/Dongik/Mitch



As a main IoTivity/CTT developer, I?d like to ask you to share IoTivity
1.2.1 and CTT1.4 Gap.



Items To be fixed on CTT 1.4

-       aaa

-       bbb

Items To be fixed on IoTivity 1.2-rel

-       ccc

-       ddd

Interoperability Test status

-       the lastest testing event: IOTIVITY 1.2-rel (changeID: xxx), CTT
1.3.kk

-       fail 1: aaa/ccc

-       fail 2: bbb/ddd



Currently there are several pieces of mail, but too fragmented and detail.

Following format or equivalent simple format will be helpful I think.



BR, Uze Choi

-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20161121/18294ea4/attachment.html>
-------------- next part --------------
An embedded message was scrubbed...
From: "Mitch Kettrick" <[email protected]>
Subject: Potential IoTivity /CTT bug: BWT for NON request messages
Date: Thu, 17 Nov 2016 08:33:58 -0800
Size: 395170
URL: 
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20161121/18294ea4/attachment.mht>
-------------- next part --------------
An embedded message was scrubbed...
From: "Morrow, Joseph L" <[email protected]>
Subject: RE: [architecture_tg] RE: "bm" discoverable bit for Collections
Date: Mon, 21 Nov 2016 09:03:01 -0800
Size: 35353
URL: 
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20161121/18294ea4/attachment-0001.mht>

Reply via email to