Project

General

Profile

Improvement #6992

Add identifier to KDC

Added by Ivan Gorin 3 months ago. Updated 2 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
Standard extension required
Start date:
09/20/2024
Due date:
% Done:

0%

Estimated time:
ID:
Source:
TF Unique ID:
WG10 Proposal:
Estimated Completion:
Discuss in Upcoming Meeting:
No
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'.

#1

Updated by Carlos Rodriguez del Castillo 3 months ago

  • Discuss in Upcoming Meeting changed from No to Yes
#2

Updated by Carlos Rodriguez del Castillo 3 months 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.

#3

Updated by Carlos Rodriguez del Castillo 2 months ago

  • Category set to Standard extension required
  • Status changed from Triage to Resolved

We hade feedback:
"No practical use case regarding that. It`s only an improvement request, because according to Standard, it`s not prohibited for IED to have multiple KDC elements.
In this way, similar to other elements (Access Point, IED etc.) it will be nice also to have “name” attribute for KDC"

TFUF:
KDC is identified from iedName+apName, so "name" is not needed, but we identify we need to add "desc" for the user to introduce its own information.

#4

Updated by Carlos Rodriguez del Castillo 2 months ago

  • Discuss in Upcoming Meeting changed from Yes to No

Also available in: Atom PDF