eDelivery CMB meeting 2023-02-16 minutes

Owned by Philip Helger
Feb 16, 2023
4 min read

Date: 2023-02-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) (excuses received)

Risto Collanus (Visma) (excuses received)

Iacopo.Arduini@regione.emilia-romagna.it (Emilia Romagna)

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-02-02 minutes

Status: Approved

New tasks and Issues

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


  1. TICC-250 - Getting issue details... STATUS
    1. Information: remove the Participant Identifier Scheme 9908 from the codelist
    2. Decision: CMB approved the change - will be 3 month in the future
    3. Responsible: Philip Helger
  2. TICC-248 - Getting issue details... STATUS
    1. Information: remove the Transport Profiles "START" and "Peppol AS4 v1" from the code lists
    2. Decision: CMB approved the change
    3. Responsible: Philip Helger
  3. TICC-246 - Getting issue details... STATUS
    1. Information: update the SMP digest algorithms from SHA-1 to SHA-256
    2. Update: none
    3. Responsible: Philip Helger
  4. TICC-245 - Getting issue details... STATUS
    1. Information: Request to remove Deprecated XRechnung Document Type Identifiers
    2. Update: none
    3. Responsible: Philip Helger
  5. TICC-244 - Getting issue details... STATUS
    1. Information: Add XRechnung 2.3 Extension Document Type Identifiers to the Peppol Code Lists
    2. Update: none
    3. Responsible: Philip Helger:
  6. TICC-243 - Getting issue details... STATUS
    1. Information: Add XRechnung 2.3 Document Type Identifiers to the Peppol Code Lists
    2. Update: none
    3. Responsible: Philip Helger
  7. TICC-235 - Getting issue details... STATUS
    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
  8. TICC-234 - Getting issue details... STATUS
    1. Information: RFC about Ppfuoi changes for PINT - making DDTS officially supported
    2. Update: none
    3. Responsible: Philip Helger
  9. TICC-233 - Getting issue details... STATUS
    1. Information; Its about a wording issue in the Peppol Envelope Policy (SBDH)
    2. Update: none
    3. Responsible: Elly Stinchcombe (Unlicensed)
  10. TICC-232 - Getting issue details... STATUS
    1. Information: Request to remove 9906 and 9907
    2. Update: none
    3. Responsible: Philip Helger
  11. TICC-229 - Getting issue details... STATUS
    1. Information: Deprecation of 9955 identifier
    2. Update: none
    3. Responsible: Philip Helger
  12. TICC-228 - Getting issue details... STATUS
    1. Information: Request to remove 9958
    2. Update: none
    3. Responisble: Philip Helger
  13. TICC-227 - Getting issue details... STATUS
    1. Information: New Participant Identifier scheme 0221 for Japan
    2. Update: none
    3. Responsible: Elly Stinchcombe (Unlicensed)
  14. TICC-226 - Getting issue details... STATUS
    1. Information: New SMP API proposal (migration code exchange)
  15. TICC-225 - Getting issue details... STATUS
    1. Information: New SMP API proposal (health check)
  16. TICC-224 - Getting issue details... STATUS
    1. Information: New SMP API proposal (identify)
  17. TICC-223 - Getting issue details... STATUS
    1. Information: Collection issue: Peppol, EESPA, BPC
  18. TICC-218 - Getting issue details... STATUS
    1. Information: Clarify case sensitivity of Peppol Seat ID
    2. Update: none
    3. Responsible: Philip Helger
  19. TICC-211 - Getting issue details... STATUS
    1. Information: New Participant Identifier Scheme 0205
    2. Update: none
    3. Responsible: Elly Stinchcombe (Unlicensed)
  20. TICC-206 - Getting issue details... STATUS
    1. Information: Number of retries on an AS4 level
    2. Update: none
    3. Responsible: Philip Helger
  21. TICC-203 - Getting issue details... STATUS
    1. Information: Please add SHA256 XMLsig to Peppol-SMP specs because Java17-security change
    2. Update: none
    3. Responsible: Philip Helger
  22. TICC-202 - Getting issue details... STATUS
    1. Information: Information about caching of SMP results for usage in a Peppol AP is missing
    2. Update: none
    3. Responsible: Philip Helger
  23. TICC-201 - Getting issue details... STATUS
    1. Information: Review of new/updated OASIS specifications
    2. Update: none
    3. Responsible: Elly Stinchcombe (Unlicensed)
  24. TICC-197 - Getting issue details... STATUS
    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
  25. TICC-187 - Getting issue details... STATUS
    1. Information: Allow 0080 as new Participant Identifier scheme
    2. Update: none
    3. Responsible: Elly Stinchcombe (Unlicensed)
  26. TICC-184 - Getting issue details... STATUS
    1. Information: Align Participant Identifier Scheme Code lists of PoAC and eDEC
    2. Update: none
    3. Responsible: Philip Helger
  27. TICC-174 - Getting issue details... STATUS
    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
  28. TICC-168 - Getting issue details... STATUS
    1. Information: Have a separate participant identifier prefix for testing purposes.
    2. Update: none
  29. TICC-167 - Getting issue details... STATUS
    1. Information: regarding joint information on news and noteworthy
    2. Update: none
    3. Responsible: Philip Helger
  30. TICC-166 - Getting issue details... STATUS
    1. Information: Clarification on the words "custom validation" in the AS4 profile was sought.
    2. Update: none
    3. Responsible: Philip Helger
  31. TICC-153 - Getting issue details... STATUS
    1. Information: https for SMP
    2. Update: none
    3. Responsible: Philip Helger
  32. TICC-151 - Getting issue details... STATUS
    1. Information: (Whitepaper) Enforce people to use SMK for testing?
    2. Update: none
    3. Responsible: Philip Helger
  33. TICC-149 - Getting issue details... STATUS
    1. Information: add a Schematron for verifying the AS4 headers. Updates directly in the issue.
    2. Update: none
    3. Responsible: Philip Helger
  34. TICC-146 - Getting issue details... STATUS
    1. Information: (Whitepaper) Creation of the Whitepaper.
    2. Responsible: Philip Helger
  35. TICC-142 - Getting issue details... STATUS
    1. Information: (Whitepaper)
    2. Responsible: Philip Helger
  36. TICC-140 - Getting issue details... STATUS
    1. Information: (Whitepaper)
    2. Responsible: Philip Helger
  37. TICC-19 - Getting issue details... STATUS
    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-02, 9:00 to 11:00 CET
  2. SPC meeting summary - Service Provider Community meetings
    1. Content was pitched on the right level
    2. Continue to provide updates in the upcoming SPC meetings - if something noteworthy available
  3. MC++ Meeting last week
    1. Klaus Vilstrup to become the new OO architect
    2. List of eDEC activities was discussed - priorisation needed
      1. Key initiatives for 2022 – Peppol Network Community (eDeC)
        • Continue improvements to the change release process in line with the new agreement change processes including communication of change candidates
        • Investigate possible upgrades of Peppol specifications taking into account newer versions of underlying standards from Oasis, such as SMP and XHE
        • Improvements to the security and resilience of the Peppol network
        • Continue support for International Invoicing and Continuous Transaction Control
      2. Potential Key initiatives for 2023 (proposal)
        1. Continue improvements to the change release process in line with the new agreement change processes including communication of change candidates
        2. Continue upgrades of Peppol specifications based on newer versions of underlying standards from OASIS
        3. Commence discussions on future planning of SML - focus on business requirements first before quickly jumping to a solution
        4. Create full description and documentation of the Peppol Network Architecture
        5. Maintain the safe and secure operations of the eDelivery network on a day-to-day basis
    3. Discussion on Peppol Directory
      1. Should it be made mandatory or not?
      2. Proposal to use mandatory with opt-out, instead of optional with an opt-in
      3. Responsibilities need to be clarified (OO, eDEC, ...)
  4. Reporting
    1. EUSR reporting public review lead to ~40 comments →  changes are very likely → another round of review will be needed
    2. TSR reporting stays unchanged
    3. ==> no date and other details when it becomes mandatory
  5. SBDH 2.0 update
    1. Only the senders (C1) Country Code will be part of the SDBH (C2 needs to know through KYC)
    2. C4 Country Code will NOT be contained. C3 needs to know the country code of C4 through KYC
    3. For Senders reporting: subtotals with country codes MUST NOT be provided (checked through Schematron only - no Schema changes)
    4. For Receiver reporting: subtotals with country codes MUST be provided
    5. Philip Helger to receive eDEC flowchart for releasing new or updated artefacts
    6. Agreed by eDEC CMB
  6. AS2 removal
    1. Presented in last SPC meeting - no objections
    2. Continue as planned with the steps described in the document circulated to the eDEC CMB mailing list
  7. Policy for use of Identifiers Update for Peppol Wildcard [Document Type Identifier] Scheme (previously DDTS)
    1. Aligned with PoAC on the migration plan
    2. PINT data model is meant to be published in ~ June/July for public review
  8. SMP 2.0 internal Work group
    1. No updates
  9. Removal of participant identifier schemes
    1. No updates
  10. eDEC Updates to the Community
    1. Continue presenting in the SPC meetings if possible


  • Internal priorities
    1. Get code list updates out (remove AS2, remove Participant Identifier Schemes, add Doc Types)
    2. SBDH 2.0 documentation finalization for Reporting
    3. Policy for use of Identifiers update for Peppol Wildcard Scheme (previously known as DDTS)
    4. SMP signature algorithm update
    5. SMP 2.0 specification update

SPC relevant

  • Change name from "DDTS" to "Peppol Wildcard Scheme" (the short form of  "Peppol Wildcard Document Type Identifier Scheme")
  • Together with OO clarify to Service Providers, that there is no date yet for mandatory Reporting (neither TSR nor EUSR)
    1. Last release info from https://peppol.eu/reporting-bis-release/ states "is expected to be operational in Q3 of 2023"
    2. Release is at least 6 month AFTER notification from OpenPeppol - this notification hasn't be send out yet

Attachments