eDelivery CMB meeting 2023-05-11 minutes

Owned by Philip Helger
May 11, 2023
3 min read

Date: 2023-05-11

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


Guests (without voting right)

Philip Helger (OpenPeppol OO)

Klaus Vilstrup (OpenPeppol OO) (apologies received)

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-04-13 minutes

Status: Approved

Information/Discussion items

  1. Next meeting 2023-05-25, 9:00 to 11:00 CET
    1. PH on vacation
  2. Meeting on 2023-06-08 is moved to 2023-06-05 same time slot due to overlap with the OpenPeppol GA
  3. Reporting
    1. Specfications were published (EUSR 1.0.0 and TSR 1.0.1)
      1. Minor issues with the generated text were found - so Micro version update will be needed soon
    2. Waiting for OO to put in use (not before 2023-10-12 - exact date is unknown)
    3. In last SPC meeting (May 2nd) Reporting was presented
  4. Policy for use of Identifiers Update v4.2.0 for Peppol Wildcard [Document Type Identifier] Scheme (previously DDTS)
    1. Sent out for public review until June 1st 2023
    2. Two Webinars on Tue May 16th and Wed May 17th to present the changes and impacts - eDEC + PINT jointly
      1. Goal: Audience has a better understanding of what we did
      2. Goal: get less comments, but more useful ones
    3. Waiting for comments
  5. SMP 2.0 internal Work group
    1. Working progresses in Google Docs
    2. Next meeting: May 15th, 2023
  6. Code List release process
    1. Foreseen release process with member review etc. seems too cumbersome and slow for the impact it has
    2. Discuss with CC on the opportunity to provide a different release process for code lists
      1. Eventually separate release process based on the impact of the proposed changes, so that "low impact only" changes can use the "quick process"
    3. Alignment with PoAC and PrAC releases is of course important
    4. Actions to take
      1. eDEC to make a proposal how to make things differently - affects release workflow and IR changes
        1. Major/minor/revision should link to impact high/medium/low
      2. Present proposal at next CC meeting
  7. Last MC++ on Wed April 19th
    1. Continued conversation around existing topics - no additional eDEC-specific input
  8. Peppol in France
    1. Currently just a PoC
    2. OpenPeppol provided a test SMP specific for French PoC registrations (using 0225 participant identifier scheme)
    3. Is the current model a violation of the Peppol guidelines?
    4. PH to ask Didier if he can present the French PoC to the eDEC CMB for 10 to 15 minutes
  9. Retrospective stuff on 2022 for the operational plan and presentation at GA in June
    1. Provide an update based on the mail from Elly, until May 12th, EoB


Internal priorities

  1. SMP signature algorithm update
  2. Create a structure how to fulfill the 2023 priorities
  3. SMP 2.0 specification update (joint effort)

SPC relevant

  • Nothing atm

New tasks and Issues

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


  1. TICC-259 - Getting issue details... STATUS
    1. Information: Request to add Participant Identifier scheme 0218
    2. Decision: None yet
    3. Responsible: Philip Helger
  2. TICC-256 - Getting issue details... STATUS
    1. Information: Remove participant identifier scheme 9956
    2. Update: On hold until BOSA decides on May 16th
    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-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
  5. TICC-234 - Getting issue details... STATUS
    1. Information: RFC about Ppfuoi changes for PINT - making DDTS officially supported
    2. Update: Approved in last CMB
    3. Responsible: Philip Helger
  6. 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)
  7. TICC-226 - Getting issue details... STATUS
    1. Information: New SMP API proposal (migration code exchange)
  8. TICC-225 - Getting issue details... STATUS
    1. Information: New SMP API proposal (health check)
  9. TICC-224 - Getting issue details... STATUS
    1. Information: New SMP API proposal (identify)
  10. TICC-223 - Getting issue details... STATUS
    1. Information: Collection issue: Peppol, EESPA, BPC
  11. TICC-218 - Getting issue details... STATUS
    1. Information: Clarify case sensitivity of Peppol Seat ID
    2. Update: none
    3. Responsible: Philip Helger
  12. TICC-206 - Getting issue details... STATUS
    1. Information: Number of retries on an AS4 level
    2. Update: none
    3. Responsible: Philip Helger
  13. 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
  14. 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
  15. TICC-201 - Getting issue details... STATUS
    1. Information: Review of new/updated OASIS specifications
    2. Update: none
    3. Responsible: Elly Stinchcombe (Unlicensed)
  16. TICC-187 - Getting issue details... STATUS
    1. Information: Allow 0080 as new Participant Identifier scheme
    2. Update: none
    3. Responsible: Elly Stinchcombe (Unlicensed)
  17. 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
  18. 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
  19. TICC-168 - Getting issue details... STATUS
    1. Information: Have a separate participant identifier prefix for testing purposes.
    2. Update: none
  20. TICC-167 - Getting issue details... STATUS
    1. Information: regarding joint information on news and noteworthy
    2. Update: none
    3. Responsible: Philip Helger
  21. 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
  22. TICC-153 - Getting issue details... STATUS
    1. Information: https for SMP
    2. Update: none
    3. Responsible: Philip Helger
  23. TICC-151 - Getting issue details... STATUS
    1. Information: (Whitepaper) Enforce people to use SMK for testing?
    2. Update: none
    3. Responsible: Philip Helger
  24. 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
  25. TICC-146 - Getting issue details... STATUS
    1. Information: (Whitepaper) Creation of the Whitepaper.
    2. Responsible: Philip Helger
  26. TICC-142 - Getting issue details... STATUS
    1. Information: (Whitepaper)
    2. Responsible: Philip Helger
  27. TICC-140 - Getting issue details... STATUS
    1. Information: (Whitepaper)
    2. Responsible: Philip Helger
  28. 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

Attachments

none