Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

...

...

...

OpenNCP Technical Committee Meeting

 

Estimated - 15:00 to 16:00 CET

Performed -    to  15:00   to 16:00 CET

AGENDA

  1. Connectathon
    1. Feedback on the tests
    2. Issues
  2. Renewal of certificates, URL issue
  3. Schedule release 2.4.1
    1. Communication
  4. Cache mechanism
  5. Update task force meetings and tasks forces to relaunch (Security? Release management?)
  6. AOB
  7. Next meeting 

 

LOCATION

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:

...

Heiko Zimmermann

S

michele.foucart

SUPPORT DOCUMENTS

 

MEETING NOTES

  1. Connectathon
    1. Feedback on the tests and issues
      20160426 - Meeting minutes, Tuesday 26th March 2016 - Retrospective on CAT participation
  2. Renewal of certificates, URL issue
    1. Issue regarding URL property certificate (related to topic raised by Marcello)
      1. What is the problem?
      2. the only url in the certificate is a CRL (italian certificate authority one)?
        1. In the original epsos specs (3.4) there is an url which is public... cf section assersion certificate, p1 to 5
    2. Need to contact Milan to better understand what is the problem
  3. Schedule release 2.4.1
    1. Communication: fix the bugs that we found first or do we announce it make the announcement now?
      1. There are 4 issues to be fixed, ideal would be to ideally we should wait for those issues to be fixed
      2. 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
        1. we should add those issues to OpenNCP affected version 2.4.0 & tag them as "Connectathon issues"
  4. Cache mechanism
    1. store all All the properties are currently stored in the db, when use SMP
    2. 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 synchronizerThis synchronizer. This would prevent redundant mysql call
      1. if we agree, we could push the idea to the SMP task force this Friday
      2. Heiko Zimmermann: some of the properties are sometimes updated.; Will they be updated in the properties file? Need a restart?
        1. TSL syncro updating the properties file
        2. either TSL synchro to notify or let it fail (url not longer valid), then check to reconnect and db query
  5. Update task force meetings and tasks forces to relaunch
    1. (Security?
    2. Release management: Security task force will be relaunched as soon as we start component per component testing, which should start very soon.
      1. We will communicate the process and tools used
    3. Release management task force will also be relaunched to improve and reduce release time + step to fixNatasha, Je, Kostas, Joao, Alexandre +
      1. Same members as previously: Natasha Carl, S, Kostas Karkaletsis, Joao Cunha, Alexandre Santos
      2. First meeting: 3pm
  6. AOB
    1. eSENS meeting in Brussels: non-repudiation, eID level 3 and SMP/SML + express the willingness to pilot again (simulate an encounter with the doctorWe should show evidence that Openncp was expressed in order to show the evidence that OpenNCP is able to comply work with eSENS BB
      Non repudiation in June(non-repudiation and eID). The idea is to simulate an encounter with the doctor
      1. eID - ongoing discussion with technical and legal
      2. For the time being it this topic is handled by eSENS WP 5.2, if OpenNCP need to support, Massi and Joao will contact usdo the liaison with OpenNCP
  7. Next meeting 11 am