View Issue Details

IDProjectCategoryView StatusLast Update
0009336Part 81: UAFX Connecting Devices and Information ModelSpecpublic2024-03-15 15:13
ReporterJan Murzyn Assigned ToGeorg Biehler  
PrioritynormalSeverityminorReproducibilityhave not tried
Status closedResolutionwon't fix 
Product Version1.00.02 
Summary0009336: Clarify validation rules for FunctionalEntityNode parameter of EstablishConnection.
Description

From the perspective of an AC (EstablishConnection implementation), the FunctionalEntityNode input parameter is redundant, if the Endpoint already exists, and its NodeId is also passed as an input parameter. The implementation can find the Endpoint using its NodeId, and perform the requested action e.g. enable communication, without even checking the FunctionalEntityNode.

Is it still expected that the implementation returns an error (as specified in Table 11), if the passed FunctionalEntityNode is invalid?

TagsNo tags attached.

Activities

Jan Murzyn

2024-01-05 22:34

developer   ~0020583

Looking at the same thing from the caller's perspective:
Is it required to set the FunctionalEntityNode to a valid value, if I only want to e.g. enable the endpoint, and I'm passing the endpoint's NodeId anyway?

Georg Biehler

2024-01-12 08:09

developer   ~0020614

I don't think that we should optimize this case.

The interface currently states FE as NodeId, but CEP as BrowseName (relative to the CEP Folder of the FE). That means that we do not have the NodeId of the CEP.

Thus propose to reject the Mantis ...

Georg Biehler

2024-01-15 09:52

developer   ~0020633

Clarified with Jan; we keep the specified behavior.

Paul Hunkar

2024-03-15 12:28

manager   ~0020901

Agreed to no fix

Issue History

Date Modified Username Field Change
2024-01-05 21:35 Jan Murzyn New Issue
2024-01-05 22:34 Jan Murzyn Note Added: 0020583
2024-01-12 08:09 Georg Biehler Note Added: 0020614
2024-01-12 08:09 Georg Biehler Assigned To => Georg Biehler
2024-01-12 08:09 Georg Biehler Status new => assigned
2024-01-15 09:52 Georg Biehler Status assigned => resolved
2024-01-15 09:52 Georg Biehler Resolution open => won't fix
2024-01-15 09:52 Georg Biehler Note Added: 0020633
2024-03-15 12:28 Paul Hunkar Status resolved => closed
2024-03-15 12:28 Paul Hunkar Note Added: 0020901