View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
000107710000-004: Servicespublic2010-04-06 18:392012-02-09 22:44
ReporterNathan PocockAssigned ToMatthias Damm  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionfixed 
Fixed in Version1.02 
Summary0001077: EndpointDescription.SecurityLevel (Byte) description is vague
Description

The description of the SecurityLevel parameter in Table 124 (EndpointDescription) does not specify HOW the ranking system should occur.

Currently, the only specification is that a value of zero is not recommended as it exists for backwards compatibility only.

Guidance should be provided to state the order of the ranking, for example:
value of 1 = HIGHEST RANK?
value of 127 = HIGHEST RANK?
value of 1 = LOWEST RANK?
value of -128 = LOWEST RANK?

What about recommendations on increments and limits? e.g.
value 1 to 5 = least secure to most secure?

Or, should the server simply rank each endpoint as in: 5 endpoints returned to the Client with the lowest rank = 1 and the highest rank = 5.

TagsNo tags attached.
Commit Version
Fix Due Date

Activities

Randy Armstrong

2010-07-06 17:31

administrator   ~0001908

July 6th - Add text to description that says 'higher values indicate better security'

Matthias Damm

2011-03-13 19:57

developer   ~0002394

Added clarification that a higher value indicates better security.l

Change is part of the draft version "OPC UA Part 4 - Services Draft 1.02.02 Body.doc"

Randy Armstrong

2011-05-23 10:26

administrator   ~0002711

Reviewed in Walldorf.

Issue History

Date Modified Username Field Change
2010-04-06 18:39 Nathan Pocock New Issue
2010-07-06 17:31 Randy Armstrong Note Added: 0001908
2010-07-06 17:31 Randy Armstrong Status new => assigned
2010-07-06 17:31 Randy Armstrong Assigned To => Matthias Damm
2011-03-13 19:57 Matthias Damm Status assigned => resolved
2011-03-13 19:57 Matthias Damm Resolution open => fixed
2011-03-13 19:57 Matthias Damm Note Added: 0002394
2011-05-23 10:26 Randy Armstrong Status resolved => closed
2011-05-23 10:26 Randy Armstrong Note Added: 0002711
2012-02-09 22:44 Jim Luth Fixed in Version => 1.02