Project

General

Profile

Support #460

The usage of ClientLN in RptEna is optional. What does this mean. 61850-6 made this option for backward compatibility with ED.1.

Added by Herbert Falk about 3 years ago. Updated almost 2 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Solved / Missunderstanding
Start date:
Due date:
% Done:

0%

Estimated time:
ID:
17
Source:
IOP_2013
TF Unique ID:
17 # IOP_2013
WG10 Proposal:

According to Cathedral City meeting (ref. to UFTF-CathedralMOM20160219) this issue is closed.

Estimated Completion:
Discuss in Upcoming Meeting:
To discuss in WG10:
Short Proposal:

Please refer to sentence 2 page 78 part 6 Ed.2 (page 60 Ed.1).

Standard(s):
Needs More Information:
Assigned TF:

Description

The usage of ClientLN in RptEna is optional. What does this mean.
61850-6 made this option for backward compatibility with ED.1. However, in order to standardize reservation mechanisms, it needs to be made mandatory. This means some type of a profile for turning optional into mandatory for ED.2. Additionally, this impacts SCL Issue 1. From an IOP perspective there is agreement that ClientLN should be the only mechanism for reserving a RCB. Proprietary mechanisms should not be allowed.

#1

Updated by Carlos Rodriguez del Castillo almost 2 years ago

  • Status changed from New to Closed

Also available in: Atom PDF