0006327: GetSecurityKeys parameter TimeToNextKey needs clarification

ID	Project	Category	View Status	Date Submitted	Last Update

0006327	10000-014: PubSub	Spec	public	2020-12-30 11:43	2021-03-30 15:49

Reporter	Matthias Damm	Assigned To	Matthias Damm
Priority	normal	Severity	major	Reproducibility	have not tried
Status	closed	Resolution	fixed

Summary	0006327: GetSecurityKeys parameter TimeToNextKey needs clarification
Description	The description of the GetSecurityKeys parameter TimeToNextKey refers to CurrentKey and FutureKeys. The two parameters CurrentKey and FutureKeys got replaced with Keys and the option to request older keys with StartingTokenId. If the StartingTokenId is 0, the first entry in Keys contains the CurrentKey. In this case the TimeToNextKey makes sense. If the StartingTokenId is set and the first entry in Keys is not the CurrentKey, the TimeToNextKey parameter makes no sense as defined today. But we have also no way to indicate the CurrentKey in Keys.
Tags	No tags attached.

Commit Version
Fix Due Date

Matthias Damm 2021-03-05 12:14 developer ~0013985	8.4 GetSecurityKeys Method Added Publishers using a central SKS shall call GetSecurityKeys always with StartingTokenId set to 0 and shall call the Method at a period of half the KeyLifetime. They can still request more than one key to bridge longer unavalablity time of the SKS. Subscribers should use a StartingTokenId of 0 the first time they call GetSecurityKeys. Subsequent call to request older or future keys can use specific StartingTokenIds. TimeToNextKey Updated first to paragraphs to: The time, in milliseconds, before the currently active key is expected to expire. The currently used SecurityTokenId equals the FirstTokenId and the currently used key is the first one in the returned Keys if the passed StartingTokenId is 0. Therefore the Method shall be called with StartingTokenId set to 0 if there is no previous knowledge about the currently used key. If a Publisher uses this Method to get the keys from a SKS, the TimeToNextKey and KeyLifetime are used to calculate the time the Publisher shall use the next key. The TimeToNextKey defines the time when to switch from the currently used key to the next key and the KeyLifetime defines when to switch from one future key to the next future key. Added in OPC 10000-14 - UA Specification Part 14 - PubSub 1.05.0 Draft31.docx

Jim Luth 2021-03-09 18:03 administrator ~0014019	Needs 1.04 Errata to close.

Jim Luth 2021-03-30 15:49 administrator ~0014133	Agreed to 1.04 Errata.

Date Modified	Username	Field	Change
2020-12-30 11:43	Matthias Damm	New Issue
2021-03-03 16:50	Matthias Damm	Assigned To	=> Matthias Damm
2021-03-03 16:50	Matthias Damm	Status	new => assigned
2021-03-05 12:14	Matthias Damm	Status	assigned => resolved
2021-03-05 12:14	Matthias Damm	Resolution	open => fixed
2021-03-05 12:14	Matthias Damm	Note Added: 0013985
2021-03-09 18:03	Jim Luth	Note Added: 0014019
2021-03-30 15:49	Jim Luth	Status	resolved => closed
2021-03-30 15:49	Jim Luth	Fixed in Version	=> 1.05
2021-03-30 15:49	Jim Luth	Note Added: 0014133