20160426 - Meeting minutes, Tuesday, April 26th, 2016 - OpenNCP Technical Committee Meeting
OpenNCP Technical Committee Meeting
Estimated - 15:00 to 16:00 CET
Performed - 15:00 to 16:00 CET
AGENDA
- Connectathon
- Feedback on the tests
- Issues
- Renewal of certificates, URL issue
- Schedule release 2.4.1
- Communication
- Cache mechanism
- Update task force meetings and tasks forces to relaunch (Security? Release management?)
- AOB
- Next meeting
Adobe Connect
http://ec-wacs.adobeconnect.com/openncp/
Room Passcode: markus.kalliola or Licinio Kustra Mano
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
If you have never attended an Adobe Connect meeting before:
Test your connection: http://ec-wacs.adobeconnect.com/common/help/en/support/meeting_test.htm
Get a quick overview: http://www.adobe.com/products/adobeconnect.html
Adobe, the Adobe logo, Acrobat and Adobe Connect are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States and/or other countries.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
PARTICIPANTS
Today's Meeting Participants:
MEETING NOTES
- Connectathon
- Feedback on the tests and issues
20160426 - Meeting minutes, Tuesday 26th March 2016 - Retrospective on CAT participation
- Feedback on the tests and issues
- Renewal of certificates, URL issue
- Issue regarding URL property certificate (related to topic raised by Marcello)
- What is the problem?
- the only url in the certificate is a CRL (italian certificate authority one)?
- In the original epsos specs (3.4) there is an url which is public... cf section assersion certificate, p1 to 5
- Need to contact Milan to better understand what is the problem
- Kostas Karkaletsis will take contact with Milan
- Issue regarding URL property certificate (related to topic raised by Marcello)
- Schedule release 2.4.1
- Communication: fix the bugs that we found first or do we make the announcement now?
- There are 4 issues to be fixed, ideally we should wait for those issues to be fixed
- Timeline? Maybe 2 weeks, it looks quick to fix but see if we include: openncp 92 (S), UTIL 17 (S), AM 25 and 26 + new ones still to be created
- we should add those issues to OpenNCP affected version 2.4.0 & tag them as "Connectathon issues"
- Communication: fix the bugs that we found first or do we make the announcement now?
- Cache mechanism
- All the properties are currently stored in the db
- Idea was to remove db and store properties in properties file. Then properties stored in hashmap (singleton). If key absent, trigger the query or TSL synchronizer. This would prevent redundant mysql call
- if we agree, we could push the idea to the SMP task force this Friday
- Heiko Zimmermann: some of the properties are sometimes updated.; Will they be updated in the properties file? Need a restart?
- TSL syncro updating the properties file
- either TSL synchro to notify or let it fail (url not longer valid), then check to reconnect and db query
- Update task force meetings and tasks forces to relaunch
- Security task force will be relaunched as soon as we start component per component testing, which should start very soon.
- We will communicate the process and tools used
- Release management task force will also be relaunched to improve and reduce release time
- Same members as previously: Natasha Carl, S, Kostas Karkaletsis, Joao Cunha, Alexandre Santos
- First meeting: 3pm
- Security task force will be relaunched as soon as we start component per component testing, which should start very soon.
- AOB
- eSENS meeting in Brussels: non-repudiation, eID level 3 and SMP/SML: the willingness to pilot again was expressed in order to show the evidence that OpenNCP is able to work with eSENS BB (non-repudiation and eID). The idea is to simulate an encounter with the doctor
- eID - ongoing discussion with technical and legal
- For the time being this topic is handled by eSENS WP 5.2, if OpenNCP need to support, Massi and Joao will do the liaison with OpenNCP
- eSENS meeting in Brussels: non-repudiation, eID level 3 and SMP/SML: the willingness to pilot again was expressed in order to show the evidence that OpenNCP is able to work with eSENS BB (non-repudiation and eID). The idea is to simulate an encounter with the doctor
- Next meeting 11 am