You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Need to implement new TIMEOUT state similar to RESET Devices do not normally respond to network when in this state, and have to be manually reset and onboarded
Need to implement new /oic/sec/doxm:timeout Property The property is automatically set to 1800 at RFOTM, and starts counting down. If Device is not onboarded by the time it reaches 0, the Device shall enter the TIMEOUT state
Drop or upload designs to attach
Linked issues
0
Related merge requests
1
Resolve "[Feature] TIMEOUT state and "timer" Property"
!28
Avatar for Kishen Maloor
George Nash
George Nash @george · 1 year ago
Developer
Oleksandr,
Is this a new OCF secuirty requirement for a future release?
Oleksandr Andrieiev
Oleksandr Andrieiev @oleksandr · 1 year ago
Contributor
Yes. See https://bugzilla.openconnectivity.org/show_bug.cgi?id=2750 for details I think we should have a field somewhere for references to the BZ items, but for now I'll just add a link in the comments
Oleksandr Andrieiev @oleksandr assigned to @oleksandr 1 year ago
Oleksandr Andrieiev @oleksandr created merge request !28 to address this issue 1 year ago
Oleksandr Andrieiev @oleksandr mentioned in merge request !28 1 year ago
Oleksandr Andrieiev @oleksandr added
specification
label 1 year ago
Oleksandr Andrieiev @oleksandr mentioned in issue #123 (closed) 1 year ago
Oleksandr Andrieiev @oleksandr assigned to @KISHEN and unassigned @oleksandr 9 months ago
Oleksandr Andrieiev
Oleksandr Andrieiev @oleksandr · 9 months ago
Contributor
Unfortunately, I can no longer work on this feature. I think CableLabs had interest in the feature, so you can reassign it to Kyle, if he gets a profile here.
Kishen Maloor
Kishen Maloor @KISHEN · 8 months ago
Maintainer @oleksandr Thanks, I will check with CableLabs about getting this done.
TIMEOUT state and "timer" Property
Open
[Feature] TIMEOUT state and "timer" Property
Need to implement new TIMEOUT state similar to RESET Devices do not normally respond to network when in this state, and have to be manually reset and onboarded
Need to implement new /oic/sec/doxm:timeout Property The property is automatically set to 1800 at RFOTM, and starts counting down. If Device is not onboarded by the time it reaches 0, the Device shall enter the TIMEOUT state
Drop or upload designs to attach
Linked issues
0
Related merge requests
1
Resolve "[Feature] TIMEOUT state and "timer" Property"
!28
Avatar for Kishen Maloor
George Nash
George Nash @george · 1 year ago
Developer
Oleksandr,
Is this a new OCF secuirty requirement for a future release?
Oleksandr Andrieiev
Oleksandr Andrieiev @oleksandr · 1 year ago
Contributor
Yes. See https://bugzilla.openconnectivity.org/show_bug.cgi?id=2750 for details I think we should have a field somewhere for references to the BZ items, but for now I'll just add a link in the comments
Oleksandr Andrieiev @oleksandr assigned to @oleksandr 1 year ago
Oleksandr Andrieiev @oleksandr created merge request !28 to address this issue 1 year ago
Oleksandr Andrieiev @oleksandr mentioned in merge request !28 1 year ago
Oleksandr Andrieiev @oleksandr added
specification
label 1 year ago
Oleksandr Andrieiev @oleksandr mentioned in issue #123 (closed) 1 year ago
Oleksandr Andrieiev @oleksandr assigned to @KISHEN and unassigned @oleksandr 9 months ago
Oleksandr Andrieiev
Oleksandr Andrieiev @oleksandr · 9 months ago
Contributor
Unfortunately, I can no longer work on this feature. I think CableLabs had interest in the feature, so you can reassign it to Kyle, if he gets a profile here.
Kishen Maloor
Kishen Maloor @KISHEN · 8 months ago
Maintainer
@oleksandr Thanks, I will check with CableLabs about getting this done.
merge request on gitlab:
https://gitlab.iotivity.org/iotivity/iotivity-lite/-/tree/14-feature-timeout-1
branch on github:
https://github.com/iotivity/iotivity-lite/tree/14-feature-timeout-1
The text was updated successfully, but these errors were encountered: