[ODTT v26.06] Possible issue in RECORDING-4-1-16 MaximumRetentionTime check #143
Unanswered
Queenie-vvtk
asked this question in
Q&A
Replies: 2 comments
|
Hello, I think you refer to the following requirement: This was changed recently. @madhurao68 we need to bring this to VEWG, since current description means MaximumRetentionTime is not used anymore. |
0 replies
|
Dear ONVIF Team, Yes, this is the requirement we were referring to. Thank you for confirming that this requirement was changed recently and for bringing the issue to VEWG. We will wait for further clarification on the expected behavior of MaximumRetentionTime and the corresponding conformance test. Thank you. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment

Uh oh!
There was an error while loading. Please reload this page.
Dear ONVIF Team,
We found a possible inconsistency in RECORDING-4-1-16.
The test creates a recording with MaximumRetentionTime taken from the Device Test Tool setting, for example P1D. After CreateRecording, Step 18 compares the returned RecordingConfiguration with the original request using Annex A.44, which includes MaximumRetentionTime. Therefore, a DUT returning PT0S fails the test.
However, Section 5.4 of the ONVIF Recording Control Service Specification Version 26.06 states that after CreateRecording, MaximumRetentionTime shall be set to 0 (unlimited).
The Step 18 assertion therefore appears inconsistent with the normative service specification.
Could you please confirm whether the expected MaximumRetentionTime after CreateRecording should be PT0S, regardless of the value supplied in the request?
Thank you.
All reactions