Improvement #6992
Add identifier to KDC
Status:
Triage
Priority:
Normal
Category:
-
Start date:
09/20/2024
Due date:
% Done:
0%
Estimated time:
ID:
Source:
TF Unique ID:
WG10 Proposal:
Estimated Completion:
Discuss in Upcoming Meeting:
Yes
To discuss in WG10:
No
Short Proposal:
Standard(s):
IEC 61850-6
Needs More Information:
No
Assigned TF:
61850-6
Description
KDC itself does not have any identifier. Proposal is to add 'name' attribute in addition to existing 'iedName' and 'apName'.
Updated by Carlos Rodriguez del Castillo 21 days ago
- Discuss in Upcoming Meeting changed from No to Yes
Updated by Carlos Rodriguez del Castillo 20 days ago
- Status changed from New to Triage
This issue comes up when you have differente KDC servers in the system, and you need to know which one the client has to use. The proposal is to add an identifier in SCL to help the client the KDC server to use.
We will ask Ivan Goring to attend next meeting and explain the issue to us.
Use Cases:
- Redundant KDC servers
- If the publisher is in another security domain
Is it possible to have multiple KDC servers, one for several groups, other for other several groups?
We need to identify why there could be more than one KDC server for one client.