/
eDelivery CMB meeting 2023-08-17 minutes

eDelivery CMB meeting 2023-08-17 minutes

Aug 17, 2023

Date: 2023-08-17

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) (apologies received)

@Arun Kumar Sharma (Basware) (apologies received)

 

Guests (without voting right)

@Philip Helger (OpenPeppol OO)

@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 2023-07-06 minutes

Status: approved

Information/Discussion items

  1. News

    1. News from the Peppol network

  1. Open Tasks @Philip Helger

    1. https://docs.peppol.eu/edelivery/ needs to be updated to reflect EUSR 1.1.0 - changes done, to be published

    2. Reporting Guideline needs to be updated for 1.1.0

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

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

    3. SBDH 2.0 Typo → SBDH 2.0.1; changes done, to be published

    4. The summary of all updates to the eDelivery page need to be communicated to PAs and SPs

    5. SMP 1.3.0 Update (Main document changes were done)

      1. create a migration plan for SMP 1.3.0 specification (gradual implementation on SMP side should work, no big bang)

      2. Initiate member review

      3. Get it out for review asap

      4. Provide a plan how to monitor SMP 1.3.0 implementation progress

      5. Collect comments

      6. Publish final version

    6. PPFUOI 4.2.0

      1. Create an impact analysis on PPFUOI 4.2.0 (in July)

      2. Send comment resolution to OO for publication (crosscheck if not just done already)

    7. Finalize TICC-19

    8. Codelist update 8.6 to be published

      1. Including 3 new issues (279, 280, 281)

    9. Quick slide deck for SPC meeting August 22nd needed

  2. Activities for this year

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

    2. Resource problem is still pressing

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

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

  3. Next meeting

    1. Thursday August 31st, 9:00 to 11:00 CEST

SPC relevant

  • Next SPC meeting: 2023-08-22, 9:00 to 10:30 CEST

  • 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 + update 2.0.1

  • SMP 1.3.0 update coming up

  • Code List update 8.6

New tasks and Issues (from last meeting)

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

 

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

    1. Information: Remove 9901, 9902, 9904 and 9905 from the Participant Identifier Codelist

    2. Decision: approved by eDEC CMB; additionally requires deprecation of 9901 in EAS (not yet). Part of Code List update v8.6

    3. Responsible: @Philip Helger

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

    1. Information: Remove 9921 from the Participant Identifier Codelist

    2. Decision: approved by eDEC CMB. Part of Code List update v8.6

    3. Responsible: @Philip Helger

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

    1. Information: new document type IDs for Invoice/Credit Note/Selfbilling Invoice for AUNZ

    2. Decision: approved by eDEC CMB. Part of Code List update v8.6

    3. Responsible: @Philip Helger

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

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

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

    1. Information: Request to add Participant Identifier scheme 0218

    2. Decision: none

    3. Responsible: @Philip Helger

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

    1. Information: Remove participant identifier scheme 9956

    2. Update: none

    3. Responsible: @Philip Helger

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

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

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

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

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

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

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

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

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

    1. Information: New SMP API proposal (identify)

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

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

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

    1. Information: Clarify case sensitivity of Peppol Seat ID

    2. Update: none

    3. Responsible: @Philip Helger

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

    1. Information: Number of retries on an AS4 level

    2. Update: none

    3. Responsible: @Philip Helger

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

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

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

    1. Information: Review of new/updated OASIS specifications

    2. Update: none

    3. Responsible: @Elly Stinchcombe (Unlicensed)

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

    1. Information: Allow 0080 as new Participant Identifier scheme

    2. Update: none

    3. Responsible: @Elly Stinchcombe (Unlicensed)

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

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

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

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

    2. Update: none

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

    1. Information: regarding joint information on news and noteworthy

    2. Update: none

    3. Responsible: @Philip Helger

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

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

    1. Information: https for SMP

    2. Update: none

    3. Responsible: @Philip Helger

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

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

    2. Update: none

    3. Responsible: @Philip Helger

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

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

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

    2. Responsible: @Philip Helger

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

    1. Information: (Whitepaper)

    2. Responsible: @Philip Helger

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

    1. Information: (Whitepaper)

    2. Responsible: @Philip Helger

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

 

Slides from Didier on the French PoC from July 12th, 2023: