eDelivery CMB meeting 2025-04-10 minutes
Date: 2025-04-10
Time: 10:00-11:30 CEST
Type of meeting: Teams
Participants and absents
Chair
@GEOK_Seong_Wah@imda.gov.sg as eDelivery Community Leader
Elected members (with voting right)
@Bård Langöy (Pagero) (apologies received)
@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
Open Tasks
New Tickets
Any other business
Approval of Minutes
eDelivery CMB meeting 2025-03-25 minutes
Status: approved
Information/Discussion items
Open Tasks
Code List alignment (not handled in this meeting)
eDEC Specifications (not handled in this meeting)
Add that new specifications take effect at 00:00 UTC unless noted otherwise
Tasks in scope:
No new tickets since last meeting
https://openpeppol.atlassian.net/browse/TICC-332 MLS
The mandatory elements of the SPOG on MLS should go in a “Peppol Policy for use of MLS” (small document - similar to “Peppol Policy for Transport Security”)
Will it be mandatory for Service Providers or not
What is the maximum waiting time for a negative MLS
This document will go out for formal member review for 4 weeks
MLS positioning in the Network to be stated in the SPOG
SPOG should contain the note, that each SP MUST be able to receive MLS, even if they only requested negative MLS
SPOG should also contain a statement, how different document types may have different response time requirements
Clarify that the Scope of MLS activities does not mean they have to be done
Highlight the architectural change in the document exchange itself
If C2 requested always MLS and does not get an MLS in time - what then?
The SPOG will eventually go out for member review
Create an internal document: “Evaluation of the mandatory usage of MLS in the Peppol Network”
Remember the discussions and decisions and their foundations
MLS Webinar took place in April 8th, 2025
Was discussed in Belgium Service Provider Forum as well as with the Finnish Peppol Community
Brief questionnaire was answered by 31 individuals
Next steps
Start working on the Service Provider Operational Guideline
Run the member review
Currently running 2025.03.12 Peppol MLS and SPIS Member Review
Collect and resolve comments and get eDEC CMB approval on final version
Publish version
Organisational topics
Review of General Assembly
Seong Wah presented community updates of eDEC
Peppol Conference on June 17th (Tue) and 18th (Wed), 2025 (Brussels)
Prepare a technical track
eDEC participation
Seong Wah: planned to participate
Risto: planned to participate
Arun: planned to participate
Iacopo: not decided
Bard: status unknown
Klaus: will participate
Philip: will participate
Two parallel tracks for two half days (Tue afternoon, Wed morning) - one technical, one other
to be shared with PoAC
Brainstorm for technical topics
Information on current migrations
PINT migration busdox/wildcard - incl. Q&A
CNAME / NAPTR record changes in DNS - incl. Q&A
WG updates
CIWG update
MLS
Panel discussion on Security and resilience (speakers from different groups)
Testbed
ViDA / CTC / DCTCE - Architectural perspective
eB2B and the consequences on Peppol specifications
Peppol Directory???
Brainstorm for business topics:
Peppol France
News (not handled in this meeting)
News from the Peppol Network
Peppol - GENA consolidation
CIWG
Service Provider Identification Scheme (identify C2 and C3)
Out for member review
SMP 2.0 WG
Paused until end of March
MLA work group (for MLS)
OO Internal Peppol Directory Initiative
Activities for this year (not handled in this meeting)
Initial draft for Activities 2024 was ciruclated internally
Published
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
Resource problem is still pressing
Ad activity 2: Discussion on the comparison of new and existing standards should be done in a less "ad hoc way"
Start documenting findings in a more structured way
Ad activity 3: Brainstorming for Peppol Architecure v2 has been started
Check if a restricted Confluence page can be used instead
Crosscheck with the long term tasks
Next meeting(s)
Next meeting: Thursday April 10th 2025, 10:00 to 11:30 CEST
Note: timezone shift in Europe on Sunday March 30th - 1h forward
New tasks and Issues (from last meeting)
Issues: https://openpeppol.atlassian.net/issues/?filter=10258
Not updated and not handled in this meeting.
https://openpeppol.atlassian.net/issues/TICC-382
Information: fix URLs in PFUOI references
Decision: agreed
https://openpeppol.atlassian.net/browse/TICC-380
Information: Request to remove column from Participant Identifier Scheme Code List
Decision: Generally agreed to move forward and include in next major release
https://openpeppol.atlassian.net/browse/TICC-378
Information: Request for an error correction on Peppol AS4 profile on Content-Transfer-Encoding
Decision: Generally agreed
https://openpeppol.atlassian.net/browse/TICC-370
Information: Update reference style in Peppol AS4 specification
https://openpeppol.atlassian.net/browse/TICC-369
Information: Internal task to cleanup document type identifier code list based on Service Domain feedback
https://openpeppol.atlassian.net/browse/TICC-368
Information: Internal task to define rules how to name code list entries issued by OpenPeppol
https://openpeppol.atlassian.net/browse/TICC-366
Information: Change document type identifier code list names
https://openpeppol.atlassian.net/browse/TICC-354
Information: Clarification on PFUOI length of participant identifiers is requested (Policy 1)
https://openpeppol.atlassian.net/browse/TICC-352
Information: Error correction request in SMP specification
https://openpeppol.atlassian.net/browse/TICC-351
Information: Make identifier scheme mandatory in SBDH
https://openpeppol.atlassian.net/browse/TICC-347
Information: support for larger documents in the Peppol Network
https://openpeppol.atlassian.net/browse/TICC-336
Information: Create a Service Provider Identification Scheme
https://openpeppol.atlassian.net/browse/TICC-332
Information: RFC to convert the output of the MLA work group (the Message Level Status, MLS) into an eDEC specification
Update:
https://openpeppol.atlassian.net/browse/TICC-327
Information: Error correction for Reporting Specification needed
https://openpeppol.atlassian.net/browse/TICC-325
Information: Create official clarification between the use of a Participant Identifier and a Legal Identifier
https://openpeppol.atlassian.net/browse/TICC-323
Information: Change Lower boundary of Business Entity within Business Card
https://openpeppol.atlassian.net/browse/TICC-315
Information: Peppol Reporting name change
https://openpeppol.atlassian.net/browse/TICC-311
Information: Use UTC as timezone for all Peppol publications date time
https://openpeppol.atlassian.net/browse/TICC-310
Information: Codelist alignment
https://openpeppol.atlassian.net/browse/TICC-309
Information: Codelist alignment
https://openpeppol.atlassian.net/browse/TICC-308
Information: internal activity: create AP Operational Guideline
https://openpeppol.atlassian.net/browse/TICC-303
Information: extract Business Card specification from Peppol Directory specification
https://openpeppol.atlassian.net/browse/TICC-285
Information: Proposal to make mandatoriness of Directory API in SMP specification more clear
https://openpeppol.atlassian.net/browse/TICC-282
Update: Deprecate old Business Card Formats
https://openpeppol.atlassian.net/browse/TICC-269
Information: Request to improve consistency in AS4 error handling
https://openpeppol.atlassian.net/browse/TICC-263
Information: Peppol Participant (Corner 4) served by more than one Access Point
https://openpeppol.atlassian.net/browse/TICC-235
Information: Start definining potential actions for removing identifiers in the Code List States Document. Start with TICC-228
https://openpeppol.atlassian.net/browse/TICC-233
Information; Its about a wording issue in the Peppol Envelope Policy (SBDH)
https://openpeppol.atlassian.net/browse/TICC-226
Information: New SMP API proposal (migration code exchange)
https://openpeppol.atlassian.net/browse/TICC-225
Information: New SMP API proposal (health check)
https://openpeppol.atlassian.net/browse/TICC-224
Information: New SMP API proposal (identify)
https://openpeppol.atlassian.net/browse/TICC-206
Information: Number of retries on an AS4 level
https://openpeppol.atlassian.net/browse/TICC-202
Information: Information about caching of SMP results for usage in a Peppol AP is missing
https://openpeppol.atlassian.net/browse/TICC-174
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.
https://openpeppol.atlassian.net/browse/TICC-168
Information: Have a separate participant identifier prefix for testing purposes.
https://openpeppol.atlassian.net/browse/TICC-166
Information: Clarification on the words "custom validation" in the AS4 profile was sought.
https://openpeppol.atlassian.net/browse/TICC-153
Information: https for SMP
https://openpeppol.atlassian.net/browse/TICC-151
Information: (Whitepaper) Enforce people to use SMK for testing?
https://openpeppol.atlassian.net/browse/TICC-149
Information: add a Schematron for verifying the AS4 headers. Updates directly in the issue.
https://openpeppol.atlassian.net/browse/TICC-146
Information: (Whitepaper) Creation of the Whitepaper.
https://openpeppol.atlassian.net/browse/TICC-142
Information: (Whitepaper)
https://openpeppol.atlassian.net/browse/TICC-140
Information: (Whitepaper)
Attachments
none