[OASIS Issue Tracker] (ENERGYINTEROP-694) Binary & Enumerations

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

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

Toby Considine updated ENERGYINTEROP-694:
-----------------------------------------
    Environment: 
Rolando Herrero https://lists.oasis-open.org/archives/energyinterop-comment/202111/msg00003.html 



  was:https://lists.oasis-open.org/archives/energyinterop-comment/202111/msg00003.html Rolando Herrero


> Binary & Enumerations
> ---------------------
>
>                 Key: ENERGYINTEROP-694
>                 URL: https://issues.oasis-open.org/browse/ENERGYINTEROP-694
>             Project: OASIS Energy Interoperation TC
>          Issue Type: Bug
>          Components: cts
>    Affects Versions: CTSPR01
>         Environment: Rolando Herrero https://lists.oasis-open.org/archives/energyinterop-comment/202111/msg00003.html 
>            Reporter: Toby Considine
>            Assignee: William Cox
>            Priority: Minor
>
> Page: 30, Line: 30 -> Some of these fields (like CURRENCY) should be binary encoded as enumerations (whenever possible). Specifically, many (IoT and non-IoT) devices in constrained environments rely on physical/link layer technologies (like IEEE 802.15.4) that are not designed to handle large payloads (even with upper layer adaptation)



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