View Issue Details

IDProjectCategoryView StatusLast Update
000332510000-004: ServicesSpecpublic2017-05-16 18:37
Reporterrandyarmstrong Assigned ToMatthias Damm  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionfixed 
Product Version1.02 
Summary0003325: 5.5.2.2 (Table 7) Add clarification
Description

For the parameter requestedLifetime lower and upperbounds are missing. (In the reference implementation of the communication stack an hour will be used.) Please recommend lower and upperbounds here.

TagsNo tags attached.
Commit Version
Fix Due Date

Relationships

related to 0003366 closedPaul Hunkar 10000-002: Security BSI: Expand Best-Practices Descriptions. 

Activities

randyarmstrong

2016-02-23 01:08

administrator   ~0006747

Will add a reference to the discussion in Part 2 that explains the factors that affect the choice of value.

Jim Luth

2016-02-23 17:29

administrator   ~0006749

Will not define lower and upper bounds, only add discussion about the factors that affect the choice.

Matthias Damm

2016-12-19 16:46

developer   ~0007646

Last edited: 2016-12-19 16:51

Look up text in Part 2, add reference to Part 2 and check if we need some text from there. Check with Part 2 updates.

Matthias Damm

2017-05-16 10:47

developer   ~0008040

Added the following paragraph to the parameter description in OPC UA Part 4 - Services RC 1.04.14 Specification.docx:

Several cryptanalytic attacks become easier as more material encrypted with a specific key is available. By limiting the amount of data processed using a particular key, those attacks are made more difficult. Therefore the number of exchanged messages between Client and Server must be limited by establishing a new SecurityToken after the lifetime.
The setting of the requested lifetime depends on the expected number of exchanged messages in the lifetime. A higher number of messages requires a shorter lifetime.

Jim Luth

2017-05-16 18:37

administrator   ~0008070

Agreed to changes edited in Raleigh meeting.

Issue History

Date Modified Username Field Change
2016-02-23 01:07 randyarmstrong New Issue
2016-02-23 01:08 randyarmstrong Note Added: 0006747
2016-02-23 01:08 randyarmstrong Summary 5.5.2.2 (Table 7) Fix text => 5.5.2.2 (Table 7) Add clarification
2016-02-23 01:08 randyarmstrong Description Updated
2016-02-23 17:29 Jim Luth Note Added: 0006749
2016-02-23 17:29 Jim Luth Assigned To => Matthias Damm
2016-02-23 17:29 Jim Luth Status new => assigned
2016-12-19 16:46 Matthias Damm Note Added: 0007646
2016-12-19 16:51 Matthias Damm Note Edited: 0007646
2016-12-19 16:54 Matthias Damm Relationship added related to 0003366
2017-05-16 10:47 Matthias Damm Note Added: 0008040
2017-05-16 10:47 Matthias Damm Status assigned => resolved
2017-05-16 10:47 Matthias Damm Resolution open => fixed
2017-05-16 18:37 Jim Luth Note Added: 0008070
2017-05-16 18:37 Jim Luth Status resolved => closed
2017-05-16 18:37 Jim Luth Fixed in Version => 1.04