ONVIFTM Test Specification Ver. 1.02.

2 Errata document

ONVIF

www.onvif.org

info@onvif.org

 2011 by ONVIF: Open Network Video Interface Forum, Inc. All rights reserved.

Recipients of this document may copy, distribute, publish, or display this document so long as this copyright notice, license and disclaimer are retained with all copies of the document. No license is granted to modify this document. THIS DOCUMENT IS PROVIDED "AS IS," AND THE CORPORATION AND ITS MEMBERS AND THEIR AFFILIATES, MAKE NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO, WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, NON-INFRINGEMENT, OR TITLE; THAT THE CONTENTS OF THIS DOCUMENT ARE SUITABLE FOR ANY PURPOSE; OR THAT THE IMPLEMENTATION OF SUCH CONTENTS WILL NOT INFRINGE ANY PATENTS, COPYRIGHTS, TRADEMARKS OR OTHER RIGHTS. IN NO EVENT WILL THE CORPORATION OR ITS MEMBERS OR THEIR AFFILIATES BE LIABLE FOR ANY DIRECT, INDIRECT, SPECIAL, INCIDENTAL, PUNITIVE OR CONSEQUENTIAL DAMAGES, ARISING OUT OF OR RELATING TO ANY USE OR DISTRIBUTION OF THIS DOCUMENT, WHETHER OR NOT (1) THE CORPORATION, MEMBERS OR THEIR AFFILIATES HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES, OR (2) SUCH DAMAGES WERE REASONABLY FORESEEABLE, AND ARISING OUT OF OR RELATING TO ANY USE OR DISTRIBUTION OF THIS DOCUMENT. THE FOREGOING DISCLAIMER AND LIMITATION ON LIABILITY DO NOT APPLY TO, INVALIDATE, OR LIMIT REPRESENTATIONS AND WARRANTIES MADE BY THE MEMBERS AND THEIR RESPECTIVE AFFILIATES TO THE CORPORATION AND OTHER MEMBERS IN CERTAIN WRITTEN POLICIES OF THE CORPORATION.

ONVIF

www.onvif.org

info@onvif.org

1.

Summary
This document lists approved errata in the ONVIF Test Specification ver. 1.02.2 document. All ONVIF members can make use of this document when filing a Declaration of Conformance document. These errata are to be also incorporated into the upcoming Conformance Test Tool.

2.

Approved errata
Subject

Errata #

1
Document reference

Update test case 6.2.24 to include checking of TLS1.0

Clause Sub-Clause Page(s) Line(s)

ONVIF Test Specification v1.02.2

6.2.24

Test Procedure
Change

126

Replace the following text in Test Specification v1.02.2, test case 6.2.24 in, step 5:

5. If NVT supports HTTPS (i.e. GetCapabilitiesResponse message includes Capabilities.Device.Security.TLS1.1 = true or Capabilities.Device.Security.TLS1.2 = true), then continue to next test case.

with this text:

5. If NVT supports HTTPS (i.e. GetCapabilitiesResponse message includes Capabilities.Device.Security.TLS1.0 = true,Capabilities.Device.Security.TLS1.1 = true or Capabilities.Device.Security.TLS1.2 = true), then continue to next test case.

Errata #

Subject

Test case 9.3.7 incorrectly expects PullMessages parameters to be invalid

ONVIF

www.onvif.org

info@onvif.org

Document reference

Clause

Sub-Clause

Page(s)

Line(s)

ONVIF Test Specification v1.02.2

9.3.7

Test Sequence, Test Procedure

Change

338, 339 -

Since there is no mention either in ONVIF Core spec or ONVIF Test Spec that PullMessages request with Timeout=24h; MessageLimit=2000 is invalid, verification steps in Step 11 and Step 12 should be removed. Remove the following test steps in both Test Sequence and Test Procedure.
Step 11, Step 12

Errata #

Subject

3
Document reference

Validation of I-frame caused by SetSynchronizationPoint (8.1.9 and 8.1.13)

Clause Sub-Clause Page(s) Line(s)

ONVIF Test Specification v1.02.2

8.1.9 8.1.13

Test Procedure
Change

The current tests for SetSynchronizationPoint require that it is verified that an I-frame is caused by the request. However, this has proved to be difficult to implement. This proposal is to relax the originally defined verification steps. Change the following sentence in the Test Procedure of test cases 8.1.9 and 8.1.13.
21. NVC verifies that I-frame is sent by NVT before the regular I-frame insertion time interval.

To
21. NVC verifies that I-frame is sent by NVT within 10 seconds.

And also change the following sentence in the Test Result of test cases 8.1.9 and 8.1.13.
DUT did not send I-frame before the regular I-frame insertion time interval upon invoking SetSynchronizationPoint request.

To
ONVIF www.onvif.org info@onvif.org

DUT did not send I-frame within 10 seconds upon invoking SetSynchronizationPoint request.

ONVIF

www.onvif.org

info@onvif.org