Date
Wednesday, 19 April 2017, 9:00 am PDT
Location
Teleconference
Agenda
Refine materials submitted by Working Group members.
Attendees
Heather VanCura
Leonardo Lima
Thomas Lampart
Calinel Pasteanu
Minutes
We used the session to discuss plans to present at the JCP EC Meeting – Georges and Florian will be present. Heather sent the latest document draft to Georges and Florian for their review after the EC Meeting in April, as we had discussed.
We discussed plans to refine the Working Document, specifically the section on Updating older JSRs (see below), and whether any members are willing to lead these JSR efforts. In past discussions this was not the case; however there was some indication that this may have changed, so we should follow up next time and clarify this section as needed.
Updating old JSRs
Some old JSRs need either an update or rework to address evolving technology.
JSR 177
Security is a critical aspect of IoT, and JSR 177 provides Java ME applications with APIs for security and trust services through the integration of a Security Element. Since its latest maintenance release in 2007, new technologies and needs have emerged, access to TEE (Trusted Execution Environment), SE (Secure Element), services like secure storage and handling of credentials for TLS.
JSR 361
JSR 361 updates IMP(-NG) to align with state-of-the-art features and current embedded device market requirements. This brought many needed updated, but some use cases are still hard to be address, specifically when considering multi-midlet environments.
Leonardo will prepare a few slides to guide the discussion at the May EC Meeting.
Next Steps:
Refine for discussion at EC meeting 9 May.
We will meet again on 3 May to prepare for May EC Meeting.
Leonardo and Thomas to get clarity on whether they would be willing to lead JSR efforts.