View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
000417910000-012: DiscoverySpecpublic2018-02-28 14:162021-12-06 18:15
ReporterRandy Armstrong Assigned ToRandy Armstrong  
PrioritynormalSeveritymajorReproducibilityhave not tried
Status closedResolutionreopened 
Fixed in Version1.05.02 RC1 
Summary0004179: Subscribers should not register. Remove SUB server capability.
Description

Subscribers should not register. Remove SUB server capability.

TagsNo tags attached.
Commit Version
Fix Due Date

Activities

Randy Armstrong

2018-03-13 01:59

administrator   ~0008915

Fixed in 1.05 DRAFT 02.

Jim Luth

2018-03-13 15:42

administrator   ~0008920

Agreed to changes in 1.05 Draft and 1.04 Errata.

Matthias Damm

2018-09-20 13:11

developer   ~0009379

I do not understand why SUB was removed.

I want to find servers that support PubSub capabilities to configure server to server communication. Therefore I need to find Publishers AND Subscribers.

Randy Armstrong

2020-06-15 06:53

administrator   ~0012290

Sounds like what is needed is an FLC Configuration Model capability.
Please confirm,

Matthias Damm

2021-11-27 13:34

developer   ~0015402

This is independent of FLC.

At the moment we have no specific Publisher registration or discovery with any OPC UA discovery service.
Discovery for PubSub works with PubSub messages. There is no capablity needed at all for this.

The capability would be of interest for client/server discovery only where the client is a PubSub configuration client and the servers allow PubSub configuration for their application. In this case the main feature is to be able to configure the Publisher AND the Subscriber side. Therefore I want to find also servers where the application can only act as Subscriber.

Randy Armstrong

2021-11-28 02:56

administrator   ~0015410

Added PubSub Configuration (PSC) ServerCapability to Annex D.

Jim Luth

2021-12-06 18:15

administrator   ~0015473

Agreed to changes in VirtualF2F.

Issue History

Date Modified Username Field Change
2018-02-28 14:16 Randy Armstrong New Issue
2018-02-28 14:16 Randy Armstrong Assigned To => Randy Armstrong
2018-02-28 14:16 Randy Armstrong Status new => assigned
2018-03-13 01:59 Randy Armstrong Note Added: 0008915
2018-03-13 01:59 Randy Armstrong Status assigned => resolved
2018-03-13 01:59 Randy Armstrong Resolution open => fixed
2018-03-13 15:42 Jim Luth Note Added: 0008920
2018-03-13 15:42 Jim Luth Status resolved => closed
2018-03-13 20:04 Jim Luth Fixed in Version => 1.05
2018-03-13 20:05 Jim Luth Target Version => 1.05
2018-09-20 13:11 Matthias Damm Note Added: 0009379
2018-09-20 13:11 Matthias Damm Status closed => feedback
2018-09-20 13:11 Matthias Damm Resolution fixed => reopened
2020-06-15 06:52 Randy Armstrong Assigned To Randy Armstrong => Matthias Damm
2020-06-15 06:53 Randy Armstrong Status feedback => acknowledged
2020-06-15 06:53 Randy Armstrong Note Added: 0012290
2021-11-27 13:34 Matthias Damm Assigned To Matthias Damm => Randy Armstrong
2021-11-27 13:34 Matthias Damm Status acknowledged => assigned
2021-11-27 13:34 Matthias Damm Note Added: 0015402
2021-11-28 02:56 Randy Armstrong Status assigned => resolved
2021-11-28 02:56 Randy Armstrong Note Added: 0015410
2021-12-06 18:15 Jim Luth Status resolved => closed
2021-12-06 18:15 Jim Luth Fixed in Version => 1.05.02 RC1
2021-12-06 18:15 Jim Luth Note Added: 0015473