/
eDelivery CMB meeting 2023-04-13 minutes

eDelivery CMB meeting 2023-04-13 minutes

Apr 13, 2023

Date: 2023-04-13

Time: 09:15-10:00 CET

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. Approval of minutes

  2. New tasks and Issues

  3. Actions

  4. Information items

  5. Input from email

Approval of Minutes

eDelivery CMB meeting 2023-03-30 minutes

Status: Approved

New tasks and Issues

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

 

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

    1. Information: Remove participant identifier scheme 9956

    2. Decision: Approved for removal in code list v8.6

    3. Responsible: @Philip Helger

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

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

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

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

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

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

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

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

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

    1. Information: New SMP API proposal (identify)

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

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

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

    1. Information: Clarify case sensitivity of Peppol Seat ID

    2. Update: none

    3. Responsible: @Philip Helger

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

    1. Information: Number of retries on an AS4 level

    2. Update: none

    3. Responsible: @Philip Helger

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

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

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

    1. Information: Review of new/updated OASIS specifications

    2. Update: none

    3. Responsible: @Elly Stinchcombe (Unlicensed)

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

    1. Information: Allow 0080 as new Participant Identifier scheme

    2. Update: none

    3. Responsible: @Elly Stinchcombe (Unlicensed)

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

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

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

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

    2. Update: none

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

    1. Information: regarding joint information on news and noteworthy

    2. Update: none

    3. Responsible: @Philip Helger

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

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

    1. Information: https for SMP

    2. Update: none

    3. Responsible: @Philip Helger

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

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

    2. Update: none

    3. Responsible: @Philip Helger

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

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

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

    2. Responsible: @Philip Helger

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

    1. Information: (Whitepaper)

    2. Responsible: @Philip Helger

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

    1. Information: (Whitepaper)

    2. Responsible: @Philip Helger

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

Information/Discussion items

  1. Next meeting 2023-05-11, 9:00 to 11:00 CET

    1. 2023-04-27 is cancelled

  2. Reporting

    1. Additional examples were added to the TSR 1.0.1 and EUSR 1.0.0 specification

    2. Both reporting specifications and the Peppol Envelope 2.0.0 specification was published on docs.peppol.eu with a 6 month grace period (October 12th, 2023)

  3. Policy for use of Identifiers Update for Peppol Wildcard [Document Type Identifier] Scheme (previously DDTS)

    1. No further steps in the direction of member review were done

    2. Question from last SPC meeting

      1. Why do we need the wildcard registration for PINT? PINT will work without it as well...

  4. SMP 2.0 internal Work group

    1. Agreed to work in Google Docs

    2. Next meeting: May 4th, 2023

  5. Code List update v8.5.1

    1. Contains one removed document type that was accidentally added in v8.5 based on Japan PA requirement

  6. Peppol in France

    1. Currently just a PoC

    2. Is the current model a violation of the Peppol guidelines?

    3. PH to ask Didier if he can present the French PoC to the eDEC CMB for 10 to 15 minutes

  7. Next MC++ on Wed April 19th

    1. Provide additional input to Elly by email asap

 

Internal priorities

  1. Prepare next SPC meeting slides

  2. Publish for use of Identifiers update for Peppol Wildcard Scheme (previously known as DDTS)

  3. SMP signature algorithm update

  4. SMP 2.0 specification update (joint effort)

SPC relevant

Next SPC meeting: May 2nd, 9:00 to 10:30 CET (Preparation: April 25th)

  • Policy for use of Identifiers 4.2.0 draft (Wildcard formerly DDTS stuff)

    • Design choices were done a long time ago

    • Align with POAC

    • Show with an example

  • Publication of Reporting 1.0 and Envelope 2.0 specifications

  • Publication of Code Lists v8.5 and v8.5.1

  • Removal of Participant identifier scheme 9956 in favour of 0208 in next code list release v8.6

Attachments

none