[OASIS Issue Tracker] (ENERGYINTEROP-735) Security & Privacy

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

     [ https://issues.oasis-open.org/browse/ENERGYINTEROP-735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

William Cox updated ENERGYINTEROP-735:
--------------------------------------
    Resolution: 
No action.

Plan to rewrite Privacy section after Public Review 2.

> Security & Privacy
> ------------------
>
>                 Key: ENERGYINTEROP-735
>                 URL: https://issues.oasis-open.org/browse/ENERGYINTEROP-735
>             Project: OASIS Energy Interoperation TC
>          Issue Type: Bug
>          Components: cts
>    Affects Versions: CTSPR01
>         Environment: Horia Pop; Lateral Inc https://lists.oasis-open.org/archives/energyinterop-comment/202112/msg00001.html
>            Reporter: Toby Considine
>            Assignee: Toby Considine
>            Priority: Major
>              Labels: CLARITY, OTHER
>
> *Security and Privacy*
> Line 916 refers to encryption of messages using a lower case "should" whilst on line 985 the same encryption of messages is referred to with RFC uppercase MAY. This may inflict contradicting/vague recommendations in terms of message encryption. I suggest you use the same term for the use of encryption. I also believe that encryption, if not an absolute requirement, should be at least referred to with the word SHOULD and RECOMMENDED as defined by RFC2119. The example on line 979 in reference to a distribution system operator does not seem to be related to either security or privacy. Line 988 is using a confusing statement format. Consider rephrasing for clarity "counterparty of the market" to "market as the counterparty".
> _[Lines 916,985,979,988]_



--
This message was sent by Atlassian Jira
(v8.3.3#803004)