Issues #5912
sSrv6 checking the read-only part is always applicable
Description
sSrv6 step 1 and 2 can always be executed. Step 3-4-5-6 only when an attribute is writable.
Propose to make sSrv6 mandatory and change the text before step 4 into "When write-enabled data-attributes are available perform for each type"
Files
Updated by IEC 61850 TPWG over 1 year ago
- Due date set to 09/06/2022
- Status changed from New to In Progress
make sSrv6 mandatory and change the text before step 4 into "When write-enabled data-attributes are available perform for each type"
Updated by Richard Schimmel over 1 year ago
- File Solution to redmine sSrv6 5912.docx Solution to redmine sSrv6 5912.docx added
- Test Case ID set to sSrv6
Pls review attached proposal.
Updated by IEC 61850 TPWG over 1 year ago
- Due date changed from 09/06/2022 to 09/20/2022
- Closed Reason Test Procedure Update added
- Closed Reason deleted (
--Not Set---)
We need to define the criteria for determining what is read only.
Updated by Thierry Dufaure over 1 year ago
We need to define criteria for determining what is writable. Maybe we can get inspired from sSrvN2. FC=CF/DC/SP and valKind != Set or absent.
Updated by Richard Schimmel over 1 year ago
sSrv6 expected result already specifies what valKind is read-only and writable:
2. DUT sends SetDataValues(FC=BL, CF, SP, DC) response- for read-only data and response+ for write enabled data as specified in the ICD using valKind=”RO” for read-only and valKind=“Set” or missing for write enabled data attributes.
Updated by Richard Schimmel about 2 months ago
- Status changed from Resolved to Closed
- Updated Test Document set to TP1.3