/
eDelivery CMB meeting 2024-03-14 minutes

eDelivery CMB meeting 2024-03-14 minutes

Mar 14, 2024

Date: 2024-03-14

Time: 08:30-10:30 CET

Type of meeting: Zoom

Participants and absents



Chair

@Elly Stinchcombe (Unlicensed) as eDelivery Community Leader (apologies received)

@Philip Helger (OpenPeppol OO, without voting right)



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)

@Klaus Vilstrup (OpenPeppol OO)



Agenda

  1. News from the Peppol Network

  2. Open Tasks

  3. New Tickets

  4. Other

Approval of Minutes

eDelivery CMB meeting 2024-02-08

Status: approved

Information/Discussion items

  1. Organisational topics

    1. Operational plan needs to be done

    2. MC++ meeting took place last week

      1. Strategic discussions on a general level

      2. Peppol Conference May 29/30; specific round table on the next steps about eDelivery in Peppol; Conference flyer to be send around soon

      3. Discussions on the Operational Plan 2024

    3. Code List alignment between POAC and eDEC needs to start - @Georg Birgisson and @Philip Helger to start analysing the issue; eDEC CMB approved the centralization of code lists

    4. Critical Infrastructure WG: Kick off took place on March 12th; close cooperation with eDEC CMB required

    5. Seong Wah Geok is the elected successor of Elly as eDEC CMB lead. See 4. Positions elected by eDEC (2024)

  2.  News

    1. News from the Peppol Network

      1. No update

    2. Peppol - EESPA/GENA consolidation

      1. Consolidation of the GENA requirements; consolidated documents on the SP capabilities on the business layers are created; @Klaus Vilstrup to ask GENA for permission to share documents with this group

    3. Service Provider Identification Scheme

      1. Still in alignment with GENA - no decision yet

    4. MLA work group (for MLS)

      1.  No update

    5. Reporting

      1. Reporting period for Februrary was prolonged until March 22nd

      2. For January, approx. 70% of all the SPs delivered correct TSR and EUSR

      3. PA are actively using the data and ask for additional reports

      4. Still messages are exchanged without the correct C1 country code - these senders are non-compliant

      5. eDEC CMB recommends to the OO to reach out to all non-compliant C2s either directly or through their respective PA (based on the February 2024 data). Todo @Philip Helger

    6. SMP 2.0.0

      1. Check with OO if the mandate is sufficient to engage SPs directly, or if the mandate needs an update

      2. Next steps would be

        1. Call for participation to eDEC and/or SPC members (check with OO) - eDEC CMB hands over the responsibility to OO to do that. TODO @Philip Helger

        2. Schedule a kick-off meeting (proposal: Wed April 3rd, 8:30 to 10:00 CET)

        3. Schedule for regular bi-weekly meetings

      3. Preparatory work needed

        1. Prepare outcome of internal eDEC CMB focus group

      4. Response to presentation in last SPC meeting will be the call for participation and a presentation in the next SPC meeting

  3. Open Tasks @Philip Helger

    1. Finalize TICC-19

      1. Add hint on upcoming SMP 2.0 specification

    2. Code List alignment (see above)

  4. Activities for this year

    1. Initial draft for Activities 2024 was ciruclated internally - due by Feb 9th

    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: Wednesday March 27th, 8:30 to 10:30 CET

SPC relevant

  • Planned activities 2024

  • SMP 2.0 Work Group announcement

  • Rename "Peppol Reporting" to "Peppol Network Reporting"

New tasks and Issues (from last meeting)

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



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

    1. Information: add additional SETU document types to the codelist

    2. Decision: Postponed

    3. Responsible: 

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

    1. Information: Corrections to the codelist from Denmark

    2. Decision: Agreed to change, once the data is consistent

    3. Responsible: @Philip Helger

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

    1. Information: Clarification on the Peppol AS4 profile on the usage of BinarySecurityToken

    2. Decision: Agree to provide the error correction to the AS4 profile.

    3. Responsible: @Philip Helger

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

    1. Information: Peppol Reporting name change

    2. Decision: Approved

    3. Responsible: @Philip Helger

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

    1. Information: change to Business Card specification

    2. Decision: Postponed

    3. Responsible:

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

    1. Information: added Participant Identifier Scheme 0234 to the eDEC CodeList

    2. Decision: The value is for the ICD codelist but not for the eDEC Participant Identifier Scheme code list, as Finland uses only OVT (0216) for that

    3. Responsible: @Philip Helger

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

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

    2. Update: agreed for all publications - should also be considered on a broader scope

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

    1. Information: Codelist alignment

    2. Update: none

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

    1. Information: Codelist alignment

    2. Update: none

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

    1. Information: internal activity: create AP Operational Guideline

    2. Update: none

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

    1. Information: deprecate and remove old DE specific document type

    2. Update: none

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

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

    2. Update: none

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

    1. Suggestion on C4 Country Code

    2. Decision: Wait for full CMB group participation

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

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

    2. Update: none

    3. Decision: OO to clarify on the mandatory use of Business Cards.

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

    1. Information: AS4 inconclusive specification on signing of AS4 Error messages

    2. Update: none

    3. Responsible: @Elly Stinchcombe (Unlicensed)

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

    1. Update: Impact Analysis was provided

    2. Update: none

    3. Responsible: PH

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

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

    2. Update: none

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

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

    2. Update: none

    3. Responsible: @Philip Helger

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

    1. Information: Request to add Participant Identifier scheme 0218

    2. Update: Approved by eDEC CMB

    3. Responsible: @Philip Helger

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

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

  22. 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)

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

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

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

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

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

    1. Information: New SMP API proposal (identify)

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

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

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

    1. Information: Clarify case sensitivity of Peppol Seat ID

    2. Update: none

    3. Responsible: @Philip Helger

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

    1. Information: Number of retries on an AS4 level

    2. Update: none

    3. Responsible: @Philip Helger

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

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

    1. Information: Review of new/updated OASIS specifications

    2. Update: none

    3. Responsible: @Elly Stinchcombe (Unlicensed)

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

    1. Information: Allow 0080 as new Participant Identifier scheme

    2. Update: none

    3. Responsible: @Elly Stinchcombe (Unlicensed)

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

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

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

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

    2. Update: none

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

    1. Information: regarding joint information on news and noteworthy

    2. Update: none

    3. Responsible: @Philip Helger

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

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

    1. Information: https for SMP

    2. Update: none

    3. Responsible: @Philip Helger

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

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

    2. Update: none

    3. Responsible: @Philip Helger

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

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

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

    2. Responsible: @Philip Helger

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

    1. Information: (Whitepaper)

    2. Responsible: @Philip Helger

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

    1. Information: (Whitepaper)

    2. Responsible: @Philip Helger

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

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

    2. Update: work in progress

    3. Responsible: @Philip Helger

Attachments



none