View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
000904610000-001: ConceptsSpecpublic2023-07-18 18:312024-01-23 16:37
ReporterJim Luth Assigned ToJim Luth  
PrioritynormalSeverityminorReproducibilityhave not tried
Status closedResolutionfixed 
Product Version1.05.02 
Target Version1.05.04 RC1Fixed in Version1.05.04 RC1 
Summary0009046: Better describe the relation between Parts 12 and 21
Description

Both Parts describe the provisioning of certificates to application and the readers need better info about the purpose and order of that provisioning.

Additional Information

Form the UA meeting from today:

  1. Question on onboarding/provisioning: What are the criteria for a Server to exit TOFU? We cannot find a clear definition in the spec. (David Levine - I’ll be there at 11AM CST)
    We discussed the timings described in Part 21 as to when a device transitions from uncommissioned to onboarded. This seems to be documented well enough in Part 21, but the question was really more about the similar discussion in Part 12 Annex G about the transition from “setup state” to “configured”. In the discussion it became clear we need to provide more high-level information about the relation between Parts 12 and 21. Jim will add a Mantis issue on Part 1 to correct this.
TagsNo tags attached.
Commit Version1.05.04 RC
Fix Due Date2023-10-15

Activities

Jim Luth

2024-01-17 19:45

administrator   ~0020653

Rewrote clause 6.7.6. to read:

6.7.6 Device Onboarding
Historically, devices with network connectivity have been allowed to communicate as soon as they are plugged into the network. For enhanced security, many networks will now require that physical network devices be uniquely identified and authorized to communicate on the network before any additional network based provisioning can be done, for example, the assignment of a Certificate using the Certificate management services described in 6.7.3. OPC 10000-21 defines a standard process for devices to be securely bootstrapped onto the network so that OPC UA Applications can be installed, updated, and provisioned with Certificates over the network.

Jim Luth

2024-01-23 16:37

administrator   ~0020694

Agreed to changes edited in Web meeting.

Issue History

Date Modified Username Field Change
2023-07-18 18:31 Jim Luth New Issue
2023-07-25 15:19 Jim Luth Assigned To => Jim Luth
2023-07-25 15:19 Jim Luth Status new => assigned
2023-07-25 15:20 Jim Luth Commit Version => 1.05.04 RC
2023-07-25 15:20 Jim Luth Fix Due Date => 2023-10-15
2024-01-17 19:45 Jim Luth Status assigned => resolved
2024-01-17 19:45 Jim Luth Resolution open => fixed
2024-01-17 19:45 Jim Luth Fixed in Version => 1.05.04 RC1
2024-01-17 19:45 Jim Luth Note Added: 0020653
2024-01-23 16:37 Jim Luth Status resolved => closed
2024-01-23 16:37 Jim Luth Note Added: 0020694