20160203 - Meeting minutes, Wednesday February 3rd 2016 - Task force SML/SMP

Owned by michele.foucart
Last updated: Feb 04, 2016
4 min read

 

Estimated: 13:00 to 14:00 CET.

Performed: 16:00 to 17:00 CET

Agenda

  1. Introduction:
    1. Approval of previous meeting minutes
    2. Approval of the agenda
    3. Update on action items of previous meetings
  2. Feedback on the Impact assessment made by DIGIT
  3. Status from DIGIT
    1. Consultation on RfCs SMP
    2. Business Analysis
  4. Status of the integration of the SMP with OpenNCP:
    1. Impacts on the specification
      1. Technical documents to be modified
    2. Impacts on the implementation
      1. Cache mechanism design
      2. Assertions
  5. Milestones
    1. Connectathon
  6. AOB
    1. Next meeting

Location

  • AdobeConnect:

http://ec-wacs.adobeconnect.com/openncp/
Room Passcode:  markus.kalliola or michele.foucart
------------------------------------------------------------------------------------------------
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.
------------------------------------------------------------------------------------------------

Joao Cunha

S

Massimiliano Masi

Uwe Roth

YacoubouY

Adrien FERIAL

Yves ADAM

Support documents

See section /wiki/spaces/ncp/pages/72417295 where all support document are published:

  • DIGIT impact assessment on SMP/SML
  • SMP version 0.6

 

Meeting Notes

  1. Introduction:
    1. Approval of previous meeting minutes
      1. No comment on the last Meeting Minutes
    2. Approval of the agenda
      1. 4b: Assertions: this topic is not really related to SMP/SML
        1. It was reported because mentioned in the last meeting, but can be removed if not relevant
    3. Update on action items of previous meetings
      1. Progress on the business analysis
        1. Comment received from Joao
  2. Feedback on the Impact assessment made by DIGIT
    1. Joao Cunha provided feedback on the analysis by e-mail on 26/01. Main points discussed:
      1. Miss use of the Syncapp terminology, this script has no particular name. Page 20, figure 7: it's not "SyncApp" but the central services internal script.
        1. Adrien FERIAL: Ok to correct
      2. Configuration of VPN automatically done by NCP B. Page 27, figure 15: configuration of VPN may not be automatically done by NCP-B (e.g. we in Portugal have to do it manually), although the diagram is OK in a high-level perspective.
        1. Adrien FERIAL:Will update: that it is not mandatory

      3. TESTA seems interesting, removing the burden of a dedicated VPN (one of the points that creates more struggles in configurations and one which hasn't been addressed in order to clarify/simplify, like it was done with the OpenNCP installation manual). It also eases the DNSSEC requirement.

        1. Adrien FERIAL: Ok to update
      4. Certificate should be valid for maximum of 1 year. Why? It is a SHOULD not a MUST
        1. eDelivery: 3 years; best practice: epSOS; 3 years is still acceptable so no update

      5. Page 35: Note: The NCP administrator will use the NCP signing certificate to sign and push the SMP metadata.I'm not sure if this is assuming the dedicated-PKI solution, but in the current one the SMP files should be signed by the scheme operator and not by the NCP signing certificate (that's a relaxation).

        1. scheme operator : certificate issued by a CA, used to sign the TSL
        2. Adrien FERIAL: It is more a matter of configuration so no need to update
      6. Roadmap:
      7. Jan-Apr: deployment of current version of SMP (same as the one hosted by UNIPI) in DIGIT. That is the version towards which development of GET interface must be done. Will that SMP be available for the developments (ending in March) or do we need to continue with UNIPI? Do we need server hosted at the University or DIGIT will provide?
        1. Adrien FERIAL: DIGIT will provide an environment.

      8. From beginning of April to end of May there's "Development | Documentation" square in SANTE. Are those developments the adaptations to the new SMP version? Adaptations to the new SMP version?

        1. Adrien FERIAL: In the beginning you'll have to mock the SMP based on the business analysis document

      9. Only 1 month between phase 1 and phase 2 of the migration

        1. Adrien FERIAL In September, we'll end phase 1. Then we can start the 2nd phase, but planning will depend on the MS

    2. Adrien FERIAL will provide a more detailed feedback to Joao Cunha's e-mail and make the corrections required

    3. Under which umbrella this migration will be made? eSENS? Who will be coordinating it?

      1. Adrien FERIAL will need to be coordinated by DG SANTE => michele.foucart to confirm with markus.kalliola

  3. Status from DIGIT
    1. Consultation on RfCs SMP
      1. Massimiliano Masi: there was already a note from the Technical committee on one of the change request. This note should be included.
      2. Adrien FERIAL will send the link to the public consultation which is not public. There is a space where you can put your comments
        1. https://webgate.ec.europa.eu/CITnet/confluence/display/CEFCOLLAB/Consultation+on+RfCs+OASIS+SMP+specification - but page is only accessible to stakeholders. Massi has also access
    2. Business Analysis (Yves ADAM)
      1. Detailed feedback received from Joao Cunha. Yves ADAM is already integrating the updates
      2. Expecting for more comments? Massi did not receive the document...
      3. Yves ADAM will send an update of the document tomorrow, including Joao Cunha comments
      4. michele.foucart will send the updated document to all with the meeting minutes. It will also be published on the task force page section "workspace"
        1. In the meanwhile, Yves ADAM sent already the updated document, which is also published now in the task force area.
      5. Adrien FERIAL proposes to go through member's feedback during our next meeting
  4. Status of the integration of the SMP with OpenNCP:
    1. Impacts on the specification
      1. Technical documents to be modified - cf. epSOS change proposal which has already identified some of the impacts
    2. Impacts on the implementation - Cache mechanism design
      1. Still need to be analysed
      2. What are the next steps? We should integrate cache in current OpenNCP architecture, in the way it does not take a lot of work + transition to the new architecture. Define in which component the cache should be done + find a way to implement it in an easy way
        1. Do we have resource to implement? Massimiliano Masi proposes that if eSENS is extended; it could be eSENS, and proposes to use the Connectathon as a milestone.
          1. Joao Cunha will raise the question to Licinio Kustra Mano
        2. The Connectathon could be a good milestone according to all the participants. It should also be fine in term of timing according to Joao Cunha.
      3. Assertions: Removed from the agenda
  5. Milestones
    1. Connectathon
  6. AOB
    1. Next meeting
      13:00 14:00.
    2. Support board Task Force SMP: https://openncp.atlassian.net/wiki/x/DwBRB