/
eDelivery CMB meeting 2023-07-06 minutes

eDelivery CMB meeting 2023-07-06 minutes

Jul 06, 2023

Date: 2023-07-06

Time: 09:00-11:00 CEST

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)

@Klaus Vilstrup (OpenPeppol OO)

Agenda

  1. News from the Peppol Network

  2. SMP 1.3.0

  3. New Tickets

  4. Other

Approval of Minutes

eDelivery CMB meeting 2023-06-22 minutes

Status: approved

Information/Discussion items

  1. News

    1. New from the Peppol network

      1. Internal Regulations 2.0.0 are out for public review: Review of Internal Regulations v2.0.0 - 23 June 2023

      2. Updated OpenPeppol membership fees

      3. PINT and Wildcard was approved and released to the public

        1. Clarification needed on migration

      4. New EUSR Update 1.1.0

        1. https://docs.peppol.eu/edelivery/ needs to be updated. Task @Philip Helger

        2. Reporting Guideline needs to be updated and published. Task @Philip Helger

  2. Migration period of PPFUOI 4.2.0

    1. eDEC CMB has decided to give Service Providers at least 6 months, until January 1st 2024 (according to the requirements for minimum implementation time in the current version of the Internal Regulations), to implement the changes in the Policy for use of Identifiers 4.2.0. So the PPFUOI 4.2.0 cannot be made mandatory before January 1st, 2024.

    2. Inform OO, send out email to SP and PA mailing list

  3. Reporting Guideline

    1. Reporting Guideline needs to be updated to reflect changes in EUSR 1.1.0. Task @Philip Helger

    2. No formal approval of the document is necessary, nevertheless it will be sent out to eDEC CMB for comments.

    3. It will be published as part of the "Change Log" inside https://docs.peppol.eu/edelivery/changelog.html and referenced directly in respective communication to the Service Providers

    4. After the guideline was published, send out email to SP and PA mailing list - include Business Message Envelope Specification update (see below)

  4. SBDH 2.0

    1. Page 11, Scope should be "3...unbounded" instead of "4..unbounded"

    2. Task @Philip Helger: fix the editorial error in the specification and get it published

    3. eDEC CMB has decided to give Service Providers at least 6 months, until January 1st 2024 (according to the requirements for minimum implementation time in the current version of the Internal Regulations), to implement the changes in the Peppol Business Message Envelope secification 2.0. So this specification cannot be enforced before January 1st, 2024.

  5. French PoC

    1. Presentation by Didier on July 12th, 2023 from 9 to 10am CEST

  6. SMP 1.3.0 update

    1. eDEC CMB doesn't see any issue with the change to SHA-256 as the signature algorithms in SMP

    2. Start switching to SHA-256 asap/whenever you are ready

    3. You have to switch to SHA-256 no later then January 31st, 2024

  7.  Task

    1. Result communication of MC is to be placed on the next CC agenda, next CC meeting will be after European summer

    2. @Philip Helger to draft proposal for communication on PPFUOI 4.2.0

    3. @Philip Helger to draft proposal for communication on Reporting and Business Message Envelope

    4. @Philip Helger to create an impact analysis on PPFUOI 4.2.0 (in July)

    5. @Philip Helger to send comment resolution to OO for publication (crosscheck if not just done already)

    6. @Philip Helger to create a migration plan for SMP 1.3.0 specification (gradual implementation on SMP side should work, no big bang)

    7. @Philip Helger to provide a plan how to monitor SMP 1.3.0 implementation progress

    8. @Philip Helger to finalize TICC-19

    9. @Philip Helger to send out new Code List State document v0.6 to eDEC CMB

  8. Next meeting

    1. Thursday August 17th, 9:00 to 11:00 CEST - then summer break up until August 17th

      1. Iacopo still on holidays

SPC relevant

  • Migration period for Policy for use of Identifiers 4.2.0

  • EUSR 1.1.0 update and Guideline update

  • Migration period for Peppol Business Message Envelope specification 2.0.

  • SMP 1.3.0 update

New tasks and Issues (from last meeting)

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

 

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

    1. Information: New Document Type for Japan Non-Tax-Invoice

    2. Decision: approved by eDEC CMB

    3. Responsible: @Philip Helger

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

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

    2. Decision: eDEC CMB agreed to evaluate the request over the summer and discuss it in the next meeting

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

    1. Information: Request for test document type ID

    2. Decision: approved by eDEC CMB

    3. Responsible: @Philip Helger

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

    1. Information: New Document Type: SETU TimeCard

    2. Update: none

    3. Responsible: @Philip Helger

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

    1. Information: Add to the EUSR BIS that EU statistics must be provided per country

    2. Decision: none

    3. Responsible: @Philip Helger

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

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

    2. Decision: Duplicate from https://openpeppol.atlassian.net/browse/TICC-108 and https://openpeppol.atlassian.net/browse/TICC-142. eDEC to propose a way forward and discuss the possibilities with OO

    3. Responsible: @Philip Helger

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

    1. Information: TSR and EUSR Document Type Identifier is outdated

    2. Decision: Deprecated existing Reporting Dcument Type Identifiers (for removal per Sept 5th, 2023) and add the new ones

    3. Responsible: @Philip Helger

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

    1. Information: Request to add Participant Identifier scheme 0218

    2. Decision: none

    3. Responsible: @Philip Helger

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

    1. Information: Remove participant identifier scheme 9956

    2. Update: none

    3. Responsible: @Philip Helger

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

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

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

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

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

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

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

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

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

    1. Information: New SMP API proposal (identify)

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

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

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

    1. Information: Clarify case sensitivity of Peppol Seat ID

    2. Update: none

    3. Responsible: @Philip Helger

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

    1. Information: Number of retries on an AS4 level

    2. Update: none

    3. Responsible: @Philip Helger

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

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

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

    1. Information: Review of new/updated OASIS specifications

    2. Update: none

    3. Responsible: @Elly Stinchcombe (Unlicensed)

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

    1. Information: Allow 0080 as new Participant Identifier scheme

    2. Update: none

    3. Responsible: @Elly Stinchcombe (Unlicensed)

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

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

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

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

    2. Update: none

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

    1. Information: regarding joint information on news and noteworthy

    2. Update: none

    3. Responsible: @Philip Helger

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

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

    1. Information: https for SMP

    2. Update: none

    3. Responsible: @Philip Helger

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

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

    2. Update: none

    3. Responsible: @Philip Helger

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

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

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

    2. Responsible: @Philip Helger

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

    1. Information: (Whitepaper)

    2. Responsible: @Philip Helger

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

    1. Information: (Whitepaper)

    2. Responsible: @Philip Helger

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