View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
000816710000-006: MappingsSpecpublic2022-07-28 11:472023-01-17 17:20
ReporterBernd Edlinger Assigned ToRandy Armstrong  
PrioritynormalSeveritymajorReproducibilityalways
Status closedResolutionfixed 
Fixed in Version1.05.03 RC1 
Summary0008167: Unclear and/or misleading wording in the ECC Amendment - misleading comment on the initial LastSequenceNumber in Table 49c
Description

I refer to this document:

https://reference.opcfoundation.org/src/v104/Core/docs/Amendment4/readme.htm

In "Table 49c - Creating a Mask for the Initialization Vector"
at LastSequenceNumber we have this probably misleading wording:

"The SequenceNumber specified in the SequenceHeader of last MessageChunk
sent in the same direction on the SecureChannel.
This number is 0 for the first message."

That is probably not how it is implemented.
Since the this number is in fact ALWAYS initialized by the first
OpenSecureChannel Request/Response sent in the same direction.

Suggested fix: Change the spec or add an Errata,
instead of using a fixed initial value, state that the SequenceNumber from the
OpenSecureChannel message in the same direction initializes this number.

TagsNo tags attached.
Commit Version
Fix Due Date

Activities

Randy Armstrong

2022-08-03 15:54

administrator   ~0017223

The first sequence number is randomized for security reasons in other parts of the specification.

Remove reference to 0 in Table 62 – Creating a Mask for the Initialization Vector.

Say that the number is the same as the sequence number for the previous OSC message in the same direction.

Randy Armstrong

2022-12-29 08:26

administrator   ~0018371

Removed statement that the first SequenceNumber is 0 in Table 62.

Randy Armstrong

2023-01-17 17:19

administrator   ~0018530

The original text was fine. Reworded to make what is supposed to happen more clear:

The value is 0 to indicate there is no LastSequenceNumber for the first MessageChunk.

Jim Luth

2023-01-17 17:20

administrator   ~0018531

Agreed to changes edited in web meeting,

Issue History

Date Modified Username Field Change
2022-07-28 11:47 Bernd Edlinger New Issue
2022-07-28 11:47 Bernd Edlinger Status new => assigned
2022-07-28 11:47 Bernd Edlinger Assigned To => Randy Armstrong
2022-07-28 12:05 Randy Armstrong Project Specifications => 10000-006: Mappings
2022-07-28 12:30 Randy Armstrong Status assigned => new
2022-08-03 15:54 Randy Armstrong Note Added: 0017223
2022-08-03 15:54 Randy Armstrong Status new => assigned
2022-12-29 08:26 Randy Armstrong Status assigned => resolved
2022-12-29 08:26 Randy Armstrong Resolution open => fixed
2022-12-29 08:26 Randy Armstrong Fixed in Version => 1.05.03 RC1
2022-12-29 08:26 Randy Armstrong Note Added: 0018371
2023-01-17 17:19 Randy Armstrong Note Added: 0018530
2023-01-17 17:20 Jim Luth Status resolved => closed
2023-01-17 17:20 Jim Luth Note Added: 0018531