Versions Compared

Version Old Version 1 New Version Current
Changes made by

Philip Helger

Philip Helger

Saved on

Key

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

Date: 2025-02-27

Time: 10:00-11:30 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) (apologies received)

Risto Collanus (Visma)

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

Arun Kumar (Basware) (apologies received)

Guests (without voting right)

...

Klaus Vilstrup (OpenPeppol OO)

Agenda

  1. Open Tasks

  2. New Tickets

  3. Any other business

Approval of Minutes

eDelivery CMB meeting 2025-02-13 minutes

...

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. Jira Legacy
        serverSystem Jira
        serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
        keyTICC-332
        MLS

        1. The current work was reviewed and comments were resolved

        2. Additional images were add to the specification

        3. MLS positioning in the Network to be stated in the Operational Guideline

          1. Will it be mandatory for Service Providers or not

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

        4. Next steps

          1. Start working on the Service Provider Operational Guideline

          2. Decide on the way forward how to introduce the MLS into the Peppol Network BEFORE the public review

          3. Package for public review

            1. MLS as a deployment on test-docs.peppol.eu

              1. Includes Documentation and supporting material

            2. SPIS specification Public Review Draft

          4. Run the public review

            1. Plan for 6 to 8 weeks

          5. Collect and resolve comments and get eDEC CMB approval on final version

          6. Publish version

  2. Organisational topics

    1. Feedback for General Assembly

      1. Reflection of last year and plan for 2025 to be presented

        1. PH to send information from last year to CMB

        2. eDEC CMB members to provide their thoughts on this topic by email to Seong Wah (asap)

      2. Proposal to create a new document in 2025 "Peppol Network Policy" to create a holistic view of the network, to better support Peppol SPs

    2. Alternate time slot for eDEC CMB March 27th is needed

      1. Proposal: Tue March 25th, 10:00 to 11:00 CET - email will be sent out

    3. Peppol Conference on June 17th (Tue) and 18th (Wed), 2025 (Brussels)

      1. Prepare a technical track

      2. Two parallel tracks for two half days (Tue afternoon, Wed morning) - one technical, one other

        1. to be shared with PoAC

      3. Brainstorm for technical topics

        1. Information on current migrations

          1. PINT migration busdox/wildcard - incl. Q&A

          2. CNAME / NAPTR record changes in DNS - incl. Q&A

        2. WG updates

          1. CIWG update

          2. MLS

        3. Panel discussion on Security and resilience (speakers from different groups)

        4. Testbed

        5. ViDA / CTC / DCTCE - Architectural perspective

        6. eB2B and the consequences on Peppol specifications

        7. Peppol Directory???

      4. Brainstorm for business topics:

        1. Peppol France

  3. News (not handled in this meeting)

    1. News from the Peppol Network

      1. Public review for eDEC specification changes for SML operational improvements

        1. 2024.12.20 review for SML Operational Improvements

        2. Public Review period was extended by two weeks compared to the original proposal (until February 2nd)

    2. Peppol - GENA consolidation

    3. CIWG

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

    5. SMP 2.0 WG

      1. Paused until end of February

    6. MLA work group (for MLS)

    7. OO Internal Peppol Directory Initiative

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

    1. Initial draft for Activities 2024 was ciruclated 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 February 20th 2025, 10:00 to 11:30 CET

New tasks and Issues (from last meeting)

...

Not updated and not handled in this meeting.

  1. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-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

  2. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-378

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

    2. Decision: Generally agreed

  3. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-370

    1. Information: Update reference style in Peppol AS4 specification

  4. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-369

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

  5. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-368

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

  6. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-366

    1. Information: Change document type identifier code list names

  1. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-354

    1. Information: Clarification on PFUOI length of participant identifiers is requested (Policy 1)

  2. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-352

    1. Information: Error correction request in SMP specification

  3. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-351

    1. Information: Make identifier scheme mandatory in SBDH

  4. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-347

    1. Information: support for larger documents in the Peppol Network

  5. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-336

    1. Information: Create a Service Provider Identification Scheme

  6. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-332

    1. Information: RFC to convert the output of the MLA work group (the Message Level Status, MLS) into an eDEC specification

    2. Update:

  7. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-327

    1. Information: Error correction for Reporting Specification needed

  8. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-325

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

  9. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-323

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

  10. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-315

    1. Information: Peppol Reporting name change

  11. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-311

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

  12. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-310

    1. Information: Codelist alignment

  13. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-309

    1. Information: Codelist alignment

  14. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-308

    1. Information: internal activity: create AP Operational Guideline

  15. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-303

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

  16. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-285

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

  17. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-282

    1. Update: Deprecate old Business Card Formats

  18. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-269

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

  19. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-263

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

  20. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-235

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

  21. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-233

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

  22. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-226

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

  23. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-225

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

  24. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-224

    1. Information: New SMP API proposal (identify)

  25. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-206

    1. Information: Number of retries on an AS4 level

  26. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-202

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

  27. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-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.

  28. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-168

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

  29. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-166

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

  30. Jira Legacy
    serverSystem

...

  1. Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-153

    1. Information: https for SMP

  2. Jira Legacy
    serverSystem

...

  1. Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-151

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

  2. Jira Legacy
    serverSystem

...

  1. Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-149

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

  2. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-146

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

  3. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-142

    1. Information: (Whitepaper)

  4. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-140

    1. Information: (Whitepaper)

Attachments

none