/
eDelivery CMB meeting 2019-09-11 minutes

eDelivery CMB meeting 2019-09-11 minutes

Sept 11, 2019

Date: 2019-08-14

Time: 14:00-15:30 CEST

Type of meeting: Gotomeeting (https://global.gotomeeting.com/join/811447525)

Participants and absents

 

Chair

@Klaus Vilstrup Pedersen (Unlicensed) as eDelivery Community Leader

 

Elected members (with voting right)

@Risto Collanus (Visma)

@Bård Langöy (Pagero)

@Rune Kjørlaug (Unlicensed) (DIFI)

@Hans Berg (Deactivated) (Tickstar)

 

Guests (without voting right)

Philip Helger (OpenPEPPOL OO)

Agenda

  1. Approval of minutes

  2. New tasks and Issues

  3. Actions

  4. Information items

  5. AoB

Approval of Minutes

eDelivery CMB meeting 2019-08-28 minutes

Approved

New tasks and Issues

Issues: https://openpeppol.atlassian.net/issues/?filter=10226

  1. #

Other:

  1. #

Actions

Action log: eDelivery CMB action log

Actions handled in this meeting:

  1. https://openpeppol.atlassian.net/browse/TICC-95 - Decision: accepted the CR

    • Action:

      • Merge process identifier code list into the document type code list, assigning each document type identifier exactly the one process identifier in which it can be used

      • The assumption is, that document type and process identifiers are always used in combination

      • Check with Pre-Award, that this does not break any of their requirements

    • Responsible: @Philip Helger to change the code lists and check with @Jerry Dimitriou

  2. https://openpeppol.atlassian.net/browse/TICC-93 : Certificate is missing but was requested - postponed @Philip Helger push Georg

  3. https://openpeppol.atlassian.net/browse/TICC-92 : Certificate is missing but was requested - postponed @Philip Helger push Georg

  4. https://openpeppol.atlassian.net/browse/TICC-88- Decision: allow hyphen

  5. https://openpeppol.atlassian.net/browse/TICC-85 - Action: 

    1. Need clarification in the OpenPEPPOL AS4 profile - on the agenda in 15-16th october in Brussels (how to handle these kinds of issues @Klaus Vilstrup Pedersen (Unlicensed)

  6. https://openpeppol.atlassian.net/browse/TICC-84

    • Proposed Decision:
      1) if empty then it MUST be interpreted as that the service is active (non-expired).
      2) If a date is in either of the elements they MUST be respected by the sending AP (C2) and actions according to SMP specification should apply.

    •  Action: Investigate the consequence of the problem @Philip Helger (count the number of SMP endpoints that use ServiceExpiration/ActivationDate)

  7. https://openpeppol.atlassian.net/browse/TICC-80:  Comment https://github.com/OpenPEPPOL/documentation/tree/master/TransportInfrastructure/work%20in%20progress

    • @Bård Langöy, @Hans Berg (Deactivated), @Rune Kjørlaug (Unlicensed), @Risto Collanus, @Klaus Vilstrup Pedersen (Unlicensed)

      • Deadline 12th of September 2019 EoB!

  8. https://openpeppol.atlassian.net/browse/TICC-19: Remove off boarded SMPs from SML (along with the participants registered) - assign to OO? @Klaus Vilstrup Pedersen (Unlicensed) talk to @Philip Helger. Jesper has list. 

    1. Define rules, when an SMP is considered dead.

  9. Migration policy for AS2 spec., visit TICC CMB 2019-02-12 minutes for input on this topic.

  10. #

Actions not handled in this meeting:

  1. #

Information items

  1. Asset list and processes

  2. Next CC F2F meeting 15-16 October in Brussels

    1. Agenda

      1. Introduction (1 hour)

        1. Recap

          1. AS4, Codelist etc.

        2. New Agreement 

        3. Artifact list

        4. news from CMB

      2. AS4 WG (2 hours)

        1. Transition

        2. Support

        3. Other topics

        4. Next steps

      3. Enhanced security WG (3 hours)

        1. Set up a framework

          1. Needs and requirements

        2. Next steps

      4. SML/SMP WG (3 hours)

        1. Requirements gathering

        2. CEF SML 

          1. Demonstration and insight into the solution

          2. Q&A

        3. Next steps and plan

      5. Misc. (1 hour)

        1. "5-corner model" (1 hour)

          1. Use-cases

  3. Reporting PEPPOL Reporting Work Group - @Philip Helger

    1. Discussion next meeting

Attachments