View Issue Details

IDProjectCategoryView StatusLast Update
000920510000-014: PubSubSpecpublic2024-03-20 17:22
ReporterMatthias Damm Assigned ToMatthias Damm  
PrioritynormalSeverityminorReproducibilityhave not tried
Status closedResolutionfixed 
Product Version1.05.02 
Fixed in Version1.05.04 RC1 
Summary0009205: Unclear validity time of pubsub security keys
Description

It is not clear how long PubSub security keys can be used if it is not possible to get new keys from the SKS (e.g. SKS down, no network connection possible).

8.4.1 SecurityGroupType definition
The Property KeyLifetime defines the lifetime of a key in milliseconds.

We have definitions for update behavior and update cycles e.g. check for next key in a cycle that is half the key lifetime.
But we have no definition what happens if the update fails.

In Client/Server we define that update should start 1/3 before lifetime expires and keys are valid for 1/3 after lifetime expires.
A similar definition for expiry would make sense.

TagsNo tags attached.
Commit Version1.05.04 RC
Fix Due Date2024-01-15

Activities

Matthias Damm

2024-03-18 00:20

developer   ~0020923

6.2.12.2 SecurityGroupDataType
Table 85 – SecurityGroupDataType structure
KeyLifetime

Added following clarification:
If a Publisher does not receive a new key in two times the KeyLifetime it shall go into Error state and shall stop to send messages secured with the key.
If a Subscriber receives messages for a key longer than two time the KeyLifetime it shall stop to process messages with the old key.

Jim Luth

2024-03-20 17:22

administrator   ~0020981

Agreed to changes edited in Dallas F2F.

Issue History

Date Modified Username Field Change
2023-10-16 11:47 Matthias Damm New Issue
2023-12-06 20:50 Jim Luth Assigned To => Matthias Damm
2023-12-06 20:50 Jim Luth Status new => assigned
2023-12-06 20:50 Jim Luth Commit Version => 1.05.04 RC
2023-12-06 20:50 Jim Luth Fix Due Date => 2024-01-15
2024-03-18 00:20 Matthias Damm Status assigned => resolved
2024-03-18 00:20 Matthias Damm Resolution open => fixed
2024-03-18 00:20 Matthias Damm Fixed in Version => 1.05.04 RC1
2024-03-18 00:20 Matthias Damm Note Added: 0020923
2024-03-20 17:22 Jim Luth Status resolved => closed
2024-03-20 17:22 Jim Luth Note Added: 0020981