View Issue Details

IDProjectCategoryView StatusLast Update
000344710000-006: MappingsSpecpublic2016-09-13 15:31
ReporterMatthias Damm Assigned Torandyarmstrong  
PrioritynormalSeveritymajorReproducibilityhave not tried
Status closedResolutionfixed 
Product Version1.03 
Target Version1.03 
Summary0003447: Definition of min send and receive buffer size wrong
Description

Table 36 – OPC UA TCP Acknowledge Message
ReceiveBufferSize and SendBufferSize

Current definition: This value shall be greater than 8 192 bytes.

I assume the intend was:
This value shall be greater or equal than 8 192 bytes.

If this assumption is right, we need an errata for OPC UA Part 6 V1.03.

TagsNo tags attached.
Commit Version
Fix Due Date

Relationships

has duplicate 0003530 closedJim Luth Unconsistent buffer sizes 

Activities

kevin

2016-06-08 21:48

reporter   ~0007008

While you're at it, there are two places in Part 6 that mention a minimum buffer or chunk size of 8196.

Just search '8196' and you'll find them.

Bernd Edlinger

2016-06-11 17:18

reporter   ~0007011

I remember the BSI also raised a question if 8192 is the "correct" value here.
Randy pointed out that changing this value creates a potential incompatibility.
Therefore the current stack implements this check exactly as it was written in
the spec. That means Send/ReceiveBufferSize must be > 8192 and we fail to
connect if Send/ReceiveBufferSize is <= 8192.

Jim Luth

2016-06-14 15:11

administrator   ~0007014

See section 6.7.1 and 6.7.2. to make sure they are consistent with the fix (table 36).

kevin

2016-06-15 18:16

reporter   ~0007015

Does anybody know what the resolution to this will be? Will the specification change and an errata be issued, or will the current definition stand?

Matthias Damm

2016-06-15 18:26

developer   ~0007016

BSI complained about two different numbers

Table 35 – OPC UA TCP Hello Message
ReceiveBufferSize and SendBufferSize
This value shall be greater than 8 192 bytes.

Table 36 – OPC UA TCP Acknowledge Message
ReceiveBufferSize and SendBufferSize
This value shall be greater than 8 192 bytes.

6.7 OPC UA Secure Conversation
UASC requires a TransportProtocol buffer size that is at least 8196 bytes.

6.7.2 MessageChunk structure
The MessageChunkSize depends on the transport protocol but shall be at least 8196 bytes.

The official answer was:
8196 is correct because of 4 bytes used for message size

Not sure where this statement is coming from.
Table 34 – OPC UA TCP Message header
MessageSize
The length of the Message, in bytes. This value includes the 8 bytes for the Message header.

I would expect that both numbers should be the same.

From a logical point of view, a min message size of 8KByte = 8192Byte makes sense. Therefore >= 8192 would be the logical definition.

Several implementations use >= 8192.
Changing such implementations to force > 8192 creates more interoperability issues. I think this is a bad idea and this was not requested by the BSI. They just asked for clarification why there are two different numbers.

randyarmstrong

2016-06-16 15:44

administrator   ~0007017

Remove the limits from the OPC UA TCP description.
Change the limit to >= 8192 for OPC UA Secure Conversation.

Jim Luth

2016-06-21 15:25

administrator   ~0007030

Reviewed and accepted changes edited in the meeting in DRAFT 1.04.02 and the 1.03 Errata.

Issue History

Date Modified Username Field Change
2016-06-07 21:11 Matthias Damm New Issue
2016-06-07 21:12 Matthias Damm Description Updated
2016-06-08 21:48 kevin Note Added: 0007008
2016-06-11 17:18 Bernd Edlinger Note Added: 0007011
2016-06-14 15:11 Jim Luth Note Added: 0007014
2016-06-14 15:12 Jim Luth Assigned To => randyarmstrong
2016-06-14 15:12 Jim Luth Status new => assigned
2016-06-15 18:16 kevin Note Added: 0007015
2016-06-15 18:26 Matthias Damm Note Added: 0007016
2016-06-16 15:44 randyarmstrong Note Added: 0007017
2016-06-16 15:44 randyarmstrong Status assigned => resolved
2016-06-16 15:44 randyarmstrong Fixed in Version => 1.03
2016-06-16 15:44 randyarmstrong Resolution open => fixed
2016-06-21 15:25 Jim Luth Note Added: 0007030
2016-06-21 15:25 Jim Luth Status resolved => closed
2016-06-21 15:25 Jim Luth Fixed in Version 1.03 => 1.04
2016-09-13 15:31 Jim Luth Relationship added has duplicate 0003530