/
eDelivery CMB meeting 2023-05-25 minutes

eDelivery CMB meeting 2023-05-25 minutes

May 29, 2023

Date: 2023-05-25

Time: 09:00-11:00 CET

Type of meeting: MS Teams

Participants and absents

 

Chair

@Elly Stinchcombe (Unlicensed) as eDelivery Community Leader

 

Elected members (with voting right)

@Bård Langöy (Pagero)

@Risto Collanus (Visma)

@Iacopo.Arduini@regione.emilia-romagna.it (Emilia Romagna)

@Arun Kumar Sharma (Basware)

 

Guests (without voting right)

@Philip Helger (OpenPeppol OO) (apologies received)

@Klaus Vilstrup (OpenPeppol OO)

Agenda

  1. Progress alignment with change and release management based on new agreement change processes

  2. Continue Peppol specification upgrade based on latest version of underlying standard e.g., OASIS

  3. Commence work on future of SML – defining business requirements followed by solution implementation in due course

  4. Documentation of Peppol eDelivery Network Architecture

  5. Ensure and maintain safe & secure operation over Peppol eDelivery Network

  6. Other

Approval of Minutes

eDelivery CMB meeting 2023-05-11 minutes

Status: moved to next meeting

Information/Discussion items

  1. Next meeting Monday (2023-06-06, 9:00 to 11:00 CET

    1. Moved due to overlap with the OpenPeppol GA

Issues 

  1. Progress alignment with change and release management based on new agreement change processes

    1. Status and questions around specifications and codelists.

    2. Mostly we believe we are following these processes.

    3. Need to ensure POAC use the same definition of major v minor changes.

    4. Need to ensure good coordination between POAC and eDEC i.e.alignment of codes list release times and alignment of codes.

    5. Do we have a discussion group to coordinate? OO to assist (@Klaus Vilstrup).

  2. Continue Peppol specification upgrade based on latest version of underlying standard e.g., OASIS

    1. Internal WG is in place and work is progressing well with clearly defined scope and outcomes

    2. High level timeline to be developed with some key milestones (while keeping group informal)

    3. Invite to be extended to @Klaus Vilstrup, Klaus talks to @Philip Helger  about this group.

  3. Commence work on future of SML – defining business requirements followed by solution implementation in due course

    1. Need to dig out previous commentary from eDec discussions on this topic (on Google Drive – (@Bård Langöy)

    2. BPC have done a POC on a federated/distributed SML – We need details and the results (@Philip Helger was a part of the WG). 

    3. Need to ensure we properly understand expectation of MC

    4. Need to define business requirements and understand various options and their pros/cons

    5. Kick this work off once SMP work is done, @Klaus Vilstrup to take the lead

  4. Documentation of Peppol eDelivery Network Architecture

    1.  Low priority

    2. Recommend to be done post SMP and SML work

    3. Revisit when ready

  5. Ensure and maintain safe & secure operation over Peppol eDelivery Network  

    1. Our BAU work, we need to look at open tickets on this and see what needs to be done

    2. Are we hooked into Security WG? Arun participates irregularly

    3. Interconnected with number 2: Need for an architecture overview of existing and future technologies.

  6. Other

    1. Consider SBDH and XHE? Should this go in SMP WG or run it separately?

    2. What is future state of Peppol Directory e.g. do we make Peppol Directory mandatory and switch from an opt-in to an opt-out process, and is this an eDec responsibility to progress?

    3. Technology review (@Klaus Vilstrup)

    4. Resourcing view (@Klaus Vilstrup)

    5. @Philip Helger - a reminder of the action from last CMB to speak to Didier and ask if he can present the French PoC to the eDEC CMB for 10 to 15 minutes

SPC relevant

  • Nothing atm

New tasks and Issues (from last meeting)

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

 

  1. https://openpeppol.atlassian.net/browse/TICC-259

    1. Information: Request to add Participant Identifier scheme 0218

    2. Decision: none

    3. Responsible: @Philip Helger

  2. https://openpeppol.atlassian.net/browse/TICC-256

    1. Information: Remove participant identifier scheme 9956

    2. Update: none

    3. Responsible: @Philip Helger

  3. https://openpeppol.atlassian.net/browse/TICC-246

    1. Information: update the SMP digest algorithms from SHA-1 to SHA-256

    2. Update: none

    3. Responsible: @Philip Helger

  4. https://openpeppol.atlassian.net/browse/TICC-235

    1. Information: Start definining potential actions for removing identifiers in the Code List States Document. Start with TICC-228

    2. Update: none

    3. Responsible: @Philip Helger

  5. https://openpeppol.atlassian.net/browse/TICC-234

    1. Information: RFC about Ppfuoi changes for PINT - making DDTS officially supported

    2. Update: Approved in last CMB

    3. Responsible: @Philip Helger

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

    1. Information; Its about a wording issue in the Peppol Envelope Policy (SBDH)

    2. Update: none

    3. Responsible: @Elly Stinchcombe (Unlicensed)

  7. https://openpeppol.atlassian.net/browse/TICC-226

    1. Information: New SMP API proposal (migration code exchange)

  8. https://openpeppol.atlassian.net/browse/TICC-225

    1. Information: New SMP API proposal (health check)

  9. https://openpeppol.atlassian.net/browse/TICC-224

    1. Information: New SMP API proposal (identify)

  10. https://openpeppol.atlassian.net/browse/TICC-223

    1. Information: Collection issue: Peppol, EESPA, BPC

  11. https://openpeppol.atlassian.net/browse/TICC-218

    1. Information: Clarify case sensitivity of Peppol Seat ID

    2. Update: none

    3. Responsible: @Philip Helger

  12. https://openpeppol.atlassian.net/browse/TICC-206

    1. Information: Number of retries on an AS4 level

    2. Update: none

    3. Responsible: @Philip Helger

  13. https://openpeppol.atlassian.net/browse/TICC-203

    1. Information: Please add SHA256 XMLsig to Peppol-SMP specs because Java17-security change

    2. Update: none

    3. Responsible: @Philip Helger

  14. https://openpeppol.atlassian.net/browse/TICC-202

    1. Information: Information about caching of SMP results for usage in a Peppol AP is missing

    2. Update: none

    3. Responsible: @Philip Helger

  15. https://openpeppol.atlassian.net/browse/TICC-201

    1. Information: Review of new/updated OASIS specifications

    2. Update: none

    3. Responsible: @Elly Stinchcombe (Unlicensed)

  16. https://openpeppol.atlassian.net/browse/TICC-187

    1. Information: Allow 0080 as new Participant Identifier scheme

    2. Update: none

    3. Responsible: @Elly Stinchcombe (Unlicensed)

  17. https://openpeppol.atlassian.net/browse/TICC-184

    1. Information: Align Participant Identifier Scheme Code lists of PoAC and eDEC

    2. Update: none

    3. Responsible: @Philip Helger

  18. https://openpeppol.atlassian.net/browse/TICC-174

    1. Information: The term "Subject Unique Identifier" in the Peppol SMP specification 1.1.0 requires clarification, as this certificate field is not present in the Peppol certificates.

    2. Update: none

    3. Responsible: @Philip Helger

  19. https://openpeppol.atlassian.net/browse/TICC-168

    1. Information: Have a separate participant identifier prefix for testing purposes.

    2. Update: none

  20. https://openpeppol.atlassian.net/browse/TICC-167

    1. Information: regarding joint information on news and noteworthy

    2. Update: none

    3. Responsible: @Philip Helger

  21. https://openpeppol.atlassian.net/browse/TICC-166

    1. Information: Clarification on the words "custom validation" in the AS4 profile was sought.

    2. Update: none

    3. Responsible: @Philip Helger

  22. https://openpeppol.atlassian.net/browse/TICC-153

    1. Information: https for SMP

    2. Update: none

    3. Responsible: @Philip Helger

  23. https://openpeppol.atlassian.net/browse/TICC-151

    1. Information: (Whitepaper) Enforce people to use SMK for testing?

    2. Update: none

    3. Responsible: @Philip Helger

  24. https://openpeppol.atlassian.net/browse/TICC-149

    1. Information: add a Schematron for verifying the AS4 headers. Updates directly in the issue.

    2. Update: none

    3. Responsible: @Philip Helger

  25. https://openpeppol.atlassian.net/browse/TICC-146

    1. Information: (Whitepaper) Creation of the Whitepaper.

    2. Responsible: @Philip Helger

  26. https://openpeppol.atlassian.net/browse/TICC-142

    1. Information: (Whitepaper)

    2. Responsible: @Philip Helger

  27. https://openpeppol.atlassian.net/browse/TICC-140

    1. Information: (Whitepaper)

    2. Responsible: @Philip Helger

  28. https://openpeppol.atlassian.net/browse/TICC-19

    1. Information: Information on how to determine and handle inactive SMP providers

    2. Update: none

    3. Responsible: @Philip Helger

Attachments

none