/
eDelivery CMB meeting 2023-06-22 minutes

eDelivery CMB meeting 2023-06-22 minutes

Jun 22, 2023

Date: 2023-06-22

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 MC 2023-06-20

  2. Reporting request by OO

  3. Policy for use of Identifiers 4.2.0

  4. SMP 1.3.0

  5. France PoC

  6. SMP 2.0 work group

  7. Other

Approval of Minutes

eDelivery CMB meeting 2023-06-05 minutes

Status: approved

Information/Discussion items

  1. News

    1. Last MC meeting outcome

      1. PINT specification including Peppol Policy for use of Identifiers 4.2.0 was approved per July 1st

      2. No official information received from MC yet

    2. Last MC++ meeting

      1. Proposal to MC to increase membership fees, to increase capacity issues - outcome unknown

      2. Vision, Mission, Goals

      3. Priorities suggested to eDEC: SML, SMP 2.0, New trust model for a multi-domain network

    3. Last GA outcome

      1. Risto and Bard continue to be valuable eDEC CMB members

      2. PAC lead: Roel (from NL)

      3. PA representative for MC: Craig Smith (from NZ)

      4. Elly presented eDEC wrap up 2022 and plan for 2023

        1. Questions: SMP 2.0 internal working group; Updates from eDEC as standing agenda item on SPC meetings

  2. Delegate Reporting update release to OO

    1. MC approved Reporting mandatory date of 2024-01-01

    2. The main reporting RFC was approved in TICC-265

    3. Request from OO to make a "fix" to EUSR to include new subsets on their behalf, to have it finished by end of June, so that the 6 month period until 2024-01-01 is maintained

    4. No process for "delegation" is present, eDEC is supposed to make the fix; the reason for the request to delegate is unknown

    5. Proposed changes

      1. Create new EUSR-Subset with "End User Country" only

      2. Create new EUSR-Subset with "End User Country" and "Document Type ID"

      3. Modifications to the Specification Document

      4. Modifications to the Schematron Rules

      5. Modifications to the rules and structure part of the Specification

    6. eDEC sees the delegation process as an exceptional case and this should not happen again; next time better planning is needed

      1. eDEC wants to be informed about the changes done, and if anything else, besides the planned changes happens (when it has "change of material impact")

    7. What's the probability for a push back from the SPC? A communication strategy is needed by OO.

    8. Remediations needed

      1. Service Provider need to be proactively informed by email (at least)

      2. Include in next SPC meeting

      3. OO to prepare information material on the delta

  3. Other

    1. Communication channels from MC to the communities need to be approved. Proposed way MC → OO → eDEC

  4. Policy for use of Identifiers 4.2.0

    1. Next steps for publication: final document version 4.2.0 with status "In Use" and publication date "July 1st, 2023" will be added to https://docs.peppol.eu/edelivery

    2. Provide a small impact analysis document for Service Providers

      1. For peppol-doctype-wildcard

      2. For the new codelist state policies

    3. OO to publish the processed collected comments

  5. SMP 1.3.0

    1. Based on TICC-246 - contains the draft specification change and an impact analysis proposal

    2. eDEC members to please comment and eventually approve in the ticket itself or by email

    3. Migration plan for that change needs to be created

    4. A follow-up, if the implementation was done, should be done by OO

  6. France PoC

    1. Presentation on Wed July 5th, 9 to 10, PH to send out invite

  7. Update on SMP 2.0 work group

    1. Last meeting 2023-06-19; Klaus was phased in

  8. Tasks

    1. @Elly Stinchcombe (Unlicensed) to check with OO how to progress in this particular case (PINT + Reporting)

    2. @Elly Stinchcombe (Unlicensed) to put the topic of MC result communication on the agenda of the next MC++ meeting

    3. Afterwards: communicate as eDEC to Peppol Service Providers on PPFUOI and Reporting, once official information is available

    4. eDEC to send out a statement, when the Peppol Business Message Envelope 2.0 specification becomes mandatory: 2024-01-01, in alignment with Reporting being mandatory

      1. @Philip Helger to draft a proposal

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

    6. @Philip Helger to send comment resolution to OO for publication

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

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

    9. @Philip Helger send out invite for France PoC presentation

    10. @Philip Helger to finalize TICC-19

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

  9. Next meeting

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

SPC relevant

  • Nothing atm

New tasks and Issues (from last meeting)

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

 

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

    1. Information: Request for test document type ID

    2. Decision: not handled

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

    1. Information: New Document Type: SETU TimeCard

    2. Update: none

    3. Responsible: @Philip Helger

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

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

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

  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

none