/
eDelivery CMB meeting 2025-11-06 minutes

eDelivery CMB meeting 2025-11-06 minutes

Date: 2025-11-06

Time: 10:30-12:00 CET

Type of meeting: Teams

Participants and absents

 

Chair

@GEOK_Seong_Wah@imda.gov.sg as eDelivery Community Leader

 

Elected members (with voting right)

@Bård Langöy (Pagero)

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

@Arun Kumar Sharma (Basware)

1 seat is currently vacant

 

Guests (without voting right)

@Philip Helger (OpenPeppol OO)

@Klaus Vilstrup (OpenPeppol OO) (apologies received)

@Erwin Wulterkens (OpenPeppol OO)

Agenda

  1. Open Tasks

  2. New Tickets

  3. Any other business

Approval of Minutes

eDelivery CMB meeting 2025-09-11 minutes

Status: approved

Information/Discussion items

 

  1. Open Tasks

    1. Code List alignment (not handled in this meeting)

    2. eDEC Specifications (not handled in this meeting)

      1. Add that new specifications take effect at 00:00 UTC unless noted otherwise

    3. Tasks in scope:

      1. OpenPeppol PKI Migration

        1. OO conducted a Webinar on the PKI Migration on September 10th, 2025 - recording available at https://openpeppol.atlassian.net/wiki/x/AQAUDwE

          1. The webinar was attended by more then 270 participants

      2. MLS tasks

        1. OO to create a draft a Policy around MLS

          1. The rules for MLS will be part of the new “Peppol Network Policy” (PNP) document

            1. The document will initially primarily contain MLS rules but also some additional Network transmission rules

            2. In the future additional policies and rules will be added to this document (e.g. Policy for Transport Security, PFUOI, SLA…)

          2. There are planned minor changes to the MLS specification as well, which are currently worked out by OO

          3. This document will go out for formal member review for 4 weeks

            1. Ideally in combination with the MLS specification update as well as the SBDH specification update

        2. OO to create a draft SPOG on MLS

          1. Work on the SPOG has been started, as the content of the policy seems quite stable now

          2. The SPOG will eventually go out for member review

          3. SPOG should contain the note, that each SP MUST be able to receive MLS, even if they only requested negative MLS

          4. SPOG should also contain a statement, how different document types may have different response time requirements

          5. Clarify that the Scope of MLS activities does not mean they have to be done

          6. Highlight the architectural change in the document exchange itself

          7. If C2 requested always MLS and does not get an MLS in time - what then?

        3. eDEC to create an internal document: “Evaluation of the mandatory usage of MLS in the Peppol Network” (no progress since last)

          1. Remember the discussions and decisions and their foundations

          2. Will be done after the official MLS documents are finalized

        4. Draft a few slides on the status of the MLS for presenting it in the PAC (and SPC?) meeting

          1. Seong Wah will draft a first version and will align with OO

  2. Organisational topics

    1. In case an eDEC CMB member is not able to attend, it is recommend to share that information in advance with the other eDEC CMB members, and MAY transmit their voting rights (“proxy vote”) to another eDEC CMB member (in case of rejection by the proxy vote receiver, the rejection must be done explicitly).

      1. If a proxy vote is provided, it may be one of the following modes:

        1. general (unconditionally) or

        2. specific or

        3. general but excluding certain topics (unconditionally with exception)

      2. Topics for the eDEC CMB should be provided at least 3 days in advance by email to the eDEC CMB member, so that they can prepare accordingly.

    2. Optimizing the RFC, Development, Review and Publishing processes.

      1. #

    3. Noteworthy absences 2025

      1. Seong Wah: none atm

      2. Bard: none atm

      3. Arun: Nov 20th to 26th

      4. Iacopo: none atm

      5. Klaus: none atm

      6. Erwin: none atm

      7. Philip: none atm

  3. News (not handled in this meeting)

    1. News from the Peppol Network

    2. CIWG

    3. Service Provider Identification Scheme (identify C2 and C3)

      1. Out for member review

    4. SMP 2.0 WG

      1. Paused until end of March

    5. OO Internal Peppol Directory Initiative

  4. Activities for this year (not handled in this meeting)

    1. Initial draft for Activities 2024 was circulated internally

    2. Published

      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

    3. Resource problem is still pressing

    4. Ad activity 2: Discussion on the comparison of new and existing standards should be done in a less "ad hoc way"

      1. Start documenting findings in a more structured way

    5. Ad activity 3: Brainstorming for Peppol Architecure v2 has been started

      1. Check if a restricted Confluence page can be used instead

      2. Crosscheck with the long term tasks

  5. Next meeting(s)

    1. Next meeting: Thursday September 25th 2025, 10:30 to 12:00 CEST, Teams

New tasks and Issues (from last meeting)

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

 

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

    1. Information: Request to change Scheme ID of 0190 from “NL:OINO” to “NL:OIN”

    2. Decision: Conditionally approved by eDEC CMB in combination with the change of TICC-380 which will change the “Scheme ID” from a “key column” to an informational column. This will be part of the upcoming codelist release v10

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

    1. Information: Request to remove 9954 in favour of 0190

    2. Decision: Approved by eDEC CMB

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

    1. Information: request to add EN 16931 2026 code list identifier

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

    1. Information: request to provide and enforce Participant Identifier Scheme structure

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

    1. Information: Request for new code list entry

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

    1. Small wording improvements in MLS needed

    2. Update: approved wording update; clarification on the Architecture Framework needed

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

    1. Information: Wording in PFUOI policy not consistent

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

    1. Information: Alignment between PPFUI and SBDH specification on non-XML payloads

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

    1. Information: This RFC requests to update the Peppol SBDH spec to include MLS_TO and MLS_TYPE as contained in the Peppol MLS specification

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

    1. Information: Change the example values to lowercase and add a recommendation to use lowercase

    2. Decision: not handled yet

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

    1. Information: Specify the HTTP status code for AS4 message exchanges in greater clarity

    2. Decision: not handled yet

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

    1. Information: Request to remove column from Participant Identifier Scheme Code List

    2. Decision: Generally agreed to move forward and include in next major release

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

    1. Information: Request for an error correction on Peppol AS4 profile on Content-Transfer-Encoding

    2. Decision: Generally agreed

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

    1. Information: Update reference style in Peppol AS4 specification

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

    1. Information: Internal task to cleanup document type identifier code list based on Service Domain feedback

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

    1. Information: Internal task to define rules how to name code list entries issued by OpenPeppol

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

    1. Information: Error correction request in SMP specification

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

    1. Information: Make identifier scheme mandatory in SBDH

  19. https://openpeppol.atlassian.net/browse/TICC-347
    a. Information: support for larger documents in the Peppol Network

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

    1. Information: Error correction for Reporting Specification needed

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

    1. Information: Create official clarification between the use of a Participant Identifier and a Legal Identifier

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

    1. Information: Change Lower boundary of Business Entity within Business Card

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

    1. Information: Peppol Reporting name change

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

    1. Information: Use UTC as timezone for all Peppol publications date time

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

    1. Information: Codelist alignment

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

    1. Information: Codelist alignment

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

    1. Information: internal activity: create AP Operational Guideline

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

    1. Information: extract Business Card specification from Peppol Directory specification

  29. https://openpeppol.atlassian.net/browse/TICC-285

    1. Information: Proposal to make mandatoriness of Directory API in SMP specification more clear

  30. https://openpeppol.atlassian.net/browse/TICC-269

    1. Information: Request to improve consistency in AS4 error handling

  31. https://openpeppol.atlassian.net/browse/TICC-263

    1. Information: Peppol Participant (Corner 4) served by more than one Access Point

  32. 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

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

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

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

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

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

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

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

    1. Information: New SMP API proposal (identify)

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

    1. Information: Number of retries on an AS4 level

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

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

  39. 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.

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

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

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

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

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

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

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

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

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

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

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

    1. Information: (Whitepaper)

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

    1. Information: (Whitepaper)

Attachments

 

none