Date: 2023-03-16

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

@Arun Kumar Sharma (Basware)

Guests (without voting right)

@Philip Helger (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-02 minutes

Status: Approved

New tasks and Issues

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

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

   1. Information: Add new Pre Award Document Types

   2. Decision: Agreed to include in next code list update

   3. Responsible: PH

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

   1. Information: Add support for Participant Identifier Scheme 0230

   2. Decision: Agreed to include in next code list update

   3. Responsible: PH

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

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

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

   1. Information: RFC about Ppfuoi changes for PINT - making DDTS officially supported

   2. Update: none

   3. Responsible: @Philip Helger

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

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

   1. Information: New Participant Identifier scheme 0221 for Japan

   2. Update: none

   3. Responsible: @Elly Stinchcombe (Unlicensed)

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

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

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

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

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

    1. Information: New SMP API proposal (identify)

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

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

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

    1. Information: Clarify case sensitivity of Peppol Seat ID

    2. Update: none

    3. Responsible: @Philip Helger

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

    1. Information: Number of retries on an AS4 level

    2. Update: none

    3. Responsible: @Philip Helger

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

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

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

    1. Information: Review of new/updated OASIS specifications

    2. Update: none

    3. Responsible: @Elly Stinchcombe (Unlicensed)

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

    1. Information: how to effectivly apply the new state "removed" for code list entries. This is a subtask of TICC-184.

    2. Update: none

    3. Responsible: @Elly Stinchcombe (Unlicensed) / @Philip Helger

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

    1. Information: Allow 0080 as new Participant Identifier scheme

    2. Update: none

    3. Responsible: @Elly Stinchcombe (Unlicensed)

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

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

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

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

    2. Update: none

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

    1. Information: regarding joint information on news and noteworthy

    2. Update: none

    3. Responsible: @Philip Helger

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

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

    1. Information: https for SMP

    2. Update: none

    3. Responsible: @Philip Helger

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

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

    2. Update: none

    3. Responsible: @Philip Helger

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

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

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

    2. Responsible: @Philip Helger

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

    1. Information: (Whitepaper)

    2. Responsible: @Philip Helger

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

    1. Information: (Whitepaper)

    2. Responsible: @Philip Helger

30. 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-03-30, 9:00 to 11:00 CET

2. AS2 specification was removed

   1. Confluence page: AS2 phase-out

   2. The "Deletion Date" for the AS2 specification in the code list needs to be amended, based on the actual publication date

3. SPC meeting summary - Service Provider Community meetings

   1. Next meeting: March 28, 2023, 09.00 CET

4. Reporting

   1. TSR: v1.0.1 implemented and ready for member publication

   2. EUSR: v1.0.0-RC3 implemented and ready for member publication

5. SBDH 2.0 update

   1. Update sent out to eDEC CMB by email for approval

   2. eDEC CMB agrees to the provided version

      1. Including one minor wording change regarding "AS2" as mentioned by Arun

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

   1. No updates

7. SMP 2.0 internal Work group

   1. The kick-off meeting takes place on March 21st 2023

8. Next Code List update

   1. See new tickets above (TIC-227, TICC-251, TICC-252)

Internal priorities

1. Prepare for next SPC meeting

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

3. Code List v8.5 update

4. SMP signature algorithm update

5. SMP 2.0 specification update (joint effort)

SPC relevant

• Inform members, that a slight update to TSR specification will be done (v1.0.1)

  • Based on the changed Peppol Envelope Specification that does only contain C1 country code (and not C4 country code anymore)

• Change name from "DDTS" to "Peppol Wildcard Scheme" (the short form of  "Peppol Wildcard Document Type Identifier Scheme")

• For Info: there is no date yet for mandatory Reporting (neither TSR nor EUSR)

  • Last release info from https://peppol.eu/reporting-bis-release/ states "is expected to be operational in Q3 of 2023"

  • Release is at least 6 month AFTER notification from OpenPeppol - this notification hasn't be send out yet

• We have developed our priorities for 2023 to inform the Operational Plan, sharing for transparency:

  • Progress alignment with change and release management based on new agreement change processes

  • Continue Peppol specification upgrade based on latest version of underlying standard e.g., OASIS

  • Commence work on future of SML – defining business requirements followed by solution implementation in due course

  • Documentation of Peppol eDelivery Network Architecture

  • Ensure and maintain safe & secure operation over Peppol eDelivery Network

• AS2 Phase Out Comms:

  • https://openpeppol.atlassian.net/wiki/spaces/RR/pages/3021602825/AS2+phase-out

• Codes List Update

  • V 8.4 – 24 February 2023

  • https://docs.peppol.eu/edelivery/codelists/changelog.html

  • Updates to

    • Participant identifier schemes

    • Document type identifiers

    • Transport profiles

Attachments

none