...
Time: 08:30-10:30 CET
Type of meeting: Zoom
Participants and absents
Chair
Elly Stinchcombe (Unlicensed) as eDelivery Community Leader Leader (apologies received)
Philip Helger (OpenPeppol OO, without voting right)
...
Klaus Vilstrup (OpenPeppol OO)
Agenda
- News from the Peppol Network
- Open Tasks
- New Tickets
- Other
Approval of Minutes
eDelivery CMB meeting 2024-0102-1808
Status: approved
Information/Discussion items
- Organisational topics
- Operational plan needs to be doneInput to the progress on the Operation Plan 2023 outcome directly to Elly asap
- MC++ meeting took place last week
- New Workgroup on Critical Infrastructure; Klaus will most likely be leading it
- New Logistics Domain has been approved
- Next GA on April 16th - incl. new eDEC Leader; call for candidates have gone out Requirements and Priorities don't match the Operational Plan of eDEC
- Strategic discussions on a general level
- Peppol Conference May 29/30; specific round table on the next steps about eDelivery in Peppol; Conference flyer to be send around soon
- Discussions on the Operational Plan 2024
- Code List alignment between POAC and eDEC needs to start - Georg Birgisson and Philip Helger to start analysing the issue; eDEC CMB approved the centralization of code lists
- Critical Infrastructure WG: Kick off took place on March 12th; close cooperation with eDEC CMB required
- Seong Wah Geok is the elected successor of Elly as eDEC CMB lead. See 4. Positions elected by eDEC (2024)
- News
- News from the Peppol Network
- Peppol Conference in May 29th and 30th in BrusselsNo update
- Peppol - EESPA/GENA consolidation
- No updateConsolidation of the GENA requirements; consolidated documents on the SP capabilities on the business layers are created; Klaus Vilstrup to ask GENA for permission to share documents with this group
- Service Provider Identification Scheme
- No update - Still in alignment with GENA - no decision yet
- MLA work group (for MLS)
- Next work group meeting is scheduled Feb 12th, 9am to 10am
- BIS Draft 2 was circulated to the work group
- No update
- Reporting
- Reporting period for Februrary was prolonged until March 22nd
- For January, approx. 70% of all the SPs delivered correct TSR and EUSR
- PA are actively using the data and ask for additional reports
- Still messages are exchanged without the correct C1 country code - these senders are non-compliant
- eDEC CMB recommends to the OO to reach out to all non-compliant C2s either directly or through their respective PA (based on the February 2024 data). Todo Philip Helger
- SMP 2.0.0
- Primary decisions:
- Based on OASIS SMP 2.0 specification
- Based on OASIS BDXL 1.0 specification facilitating U-NAPTR DNS records allowing SMPs to use https for access
- Adding new health-check and monitoring APIs
- Automating the Participant Migration Process
- Deeper integration with the Peppol Business Card
- Requires updated alignment with the SML operator
- Next Meeting is scheduled
- Check with OO if the mandate is sufficient to engage SPs directly, or if the mandate needs an update
- Next steps would be
- Call for participation to eDEC and/or SPC members (check with OO) - eDEC CMB hands over the responsibility to OO to do that. TODO Philip Helger
- Schedule a kick-off meeting (proposal: Wed April 3rd, 8:30 to 10:00 CET)
- Schedule for regular bi-weekly meetings
- Preparatory work needed
- Prepare outcome of internal eDEC CMB focus group
- Response to presentation in last SPC meeting will be the call for participation and a presentation in the next SPC meeting
- Primary decisions:
- News from the Peppol Network
- Open Tasks Philip Helger
- Finalize TICC-19
- Add hint on upcoming SMP 2.0 specification
- Code List alignment (see above)
- Finalize TICC-19
- Activities for this year
- Initial draft for Activities 2024 was ciruclated internally - due by Feb 9th
- 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 February 29thWednesday March 27th, 8:30 to 10:30 CET
SPC relevant
- Planned activities 2024
- SMP 2.0 Work Group announcement
- Rename "Peppol Reporting" to "Peppol Network Reporting"
New tasks and Issues (from last meeting)
Issues: https://openpeppol.atlassian.net/issues/?filter=10258
...
Jira Legacy server System Jira serverId b5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004 key TICC-319 - Information: add additional SETU document types to the codelist
- Decision: Postponed
- Responsible:
Jira Legacy server System Jira serverId b5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004 key TICC-317 - Information: Corrections to the codelist from Denmark
- Decision: Agreed to change, once the data is consistent
- Responsible: Philip Helger
Jira Legacy server System Jira serverId b5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004 key TICC-316 - Information: Clarification on the Peppol AS4 profile on the usage of BinarySecurityToken
- Decision: Agree to provide the error correction to the AS4 profile.
- Responsible: Philip Helger
Jira Legacy server System Jira serverId b5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004 key TICC-315 - Information: Peppol Reporting name change
- Decision: Approved
- Responsible: Philip Helger
Jira Legacy server System Jira serverId b5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004 key TICC-314 - Information: change to Business Card specification
- Decision: Postponed
- Responsible:
Jira Legacy server System Jira serverId b5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004 key TICC-313 - Information: added Participant Identifier Scheme 0234 to the eDEC CodeList
- Decision: The value is for the ICD codelist but not for the eDEC Participant Identifier Scheme code list, as Finland uses only OVT (0216) for that
- Responsible: Philip Helger
Jira Legacy server System Jira serverId b5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004 key TICC-311 - Information: Use UTC for all Peppol publications date time
- Update: agreed for all publications - should also be considered on a broader scope
Jira Legacy server System Jira serverId b5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004 key TICC-310 - Information: Codelist alignment
- Update: none
Jira Legacy server System Jira serverId b5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004 key TICC-309 - Information: Codelist alignment
- Update: none
Jira Legacy server System Jira serverId b5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004 key TICC-308 - Information: internal activity: create AP Operational Guideline
- Update: none
Jira Legacy server System Jira serverId b5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004 key TICC-304 - Information: deprecate and remove old DE specific document type
- Update: none
Jira Legacy server System Jira serverId b5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004 key TICC-303 - Information: extract Business Card specification from Peppol Directory specification
- Update: none
Jira Legacy server System Jira serverId b5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004 key TICC-286 - Suggestion on C4 Country Code
- Decision: Wait for full CMB group participation
Jira Legacy server System Jira serverId b5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004 key TICC-285 - Proposal to make mandatoriness of Directory API in SMP specification more clear
- Update: none
- Decision: OO to clarify on the mandatory use of Business Cards.
Jira Legacy server System Jira serverId b5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004 key TICC-284 - Information: AS4 inconclusive specification on signing of AS4 Error messages
- Update: none
- Responsible: Elly Stinchcombe (Unlicensed)
Jira Legacy server System Jira serverId b5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004 key TICC-282 - Update: Impact Analysis was provided
- Update: none
- Responsible: PH
Jira Legacy server System Jira serverId b5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004 key TICC-269 - Information: Request to improve consistency in AS4 error handling
- Update: none
Jira Legacy server System Jira serverId b5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004 key TICC-263 - Information: Peppol Participant (Corner 4) served by more than one Access Point
- Update: none
- Responsible: Philip Helger
Jira Legacy server System Jira serverId b5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004 key TICC-259 - Information: Request to add Participant Identifier scheme 0218
- Update: Approved by eDEC CMB
- Responsible: Philip Helger
Jira Legacy server System Jira serverId b5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004 key TICC-246 - Information: update the SMP digest algorithms from SHA-1 to SHA-256
- Update: none
- Responsible: Philip Helger
Jira Legacy server System Jira serverId b5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004 key TICC-235 - Information: Start definining potential actions for removing identifiers in the Code List States Document. Start with TICC-228
- Update: none
- Responsible: Philip Helger
Jira Legacy server System Jira serverId b5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004 key TICC-233 - Information; Its about a wording issue in the Peppol Envelope Policy (SBDH)
- Update: none
- Responsible: Elly Stinchcombe (Unlicensed)
Jira Legacy server System Jira serverId b5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004 key TICC-226 - Information: New SMP API proposal (migration code exchange)
Jira Legacy server System Jira serverId b5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004 key TICC-225 - Information: New SMP API proposal (health check)
Jira Legacy server System Jira serverId b5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004 key TICC-224 - Information: New SMP API proposal (identify)
Jira Legacy server System Jira serverId b5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004 key TICC-223 - Information: Collection issue: Peppol, EESPA, BPC
Jira Legacy server System Jira serverId b5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004 key TICC-218 - Information: Clarify case sensitivity of Peppol Seat ID
- Update: none
- Responsible: Philip Helger
Jira Legacy server System Jira serverId b5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004 key TICC-206 - Information: Number of retries on an AS4 level
- Update: none
- Responsible: Philip Helger
Jira Legacy server System Jira serverId b5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004 key TICC-202 - Information: Information about caching of SMP results for usage in a Peppol AP is missing
- Update: none
- Responsible: Philip Helger
Jira Legacy server System Jira serverId b5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004 key TICC-201 - Information: Review of new/updated OASIS specifications
- Update: none
- Responsible: Elly Stinchcombe (Unlicensed)
Jira Legacy server System Jira serverId b5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004 key TICC-187 - Information: Allow 0080 as new Participant Identifier scheme
- Update: none
- Responsible: Elly Stinchcombe (Unlicensed)
Jira Legacy server System Jira serverId b5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004 key TICC-184 - Information: Align Participant Identifier Scheme Code lists of PoAC and eDEC
- Update: none
- Responsible: Philip Helger
Jira Legacy server System Jira serverId b5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004 key 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.
- Update: none
- Responsible: Philip Helger
Jira Legacy server System Jira serverId b5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004 key TICC-168 - Information: Have a separate participant identifier prefix for testing purposes.
- Update: none
Jira Legacy server System Jira serverId b5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004 key TICC-167 - Information: regarding joint information on news and noteworthy
- Update: none
- Responsible: Philip Helger
Jira Legacy server System Jira serverId b5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004 key TICC-166 - Information: Clarification on the words "custom validation" in the AS4 profile was sought.
- Update: none
- Responsible: Philip Helger
Jira Legacy server System JIRA serverId b5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004 key TICC-153 - Information: https for SMP
- Update: none
- Responsible: Philip Helger
Jira Legacy server System JIRA serverId b5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004 key TICC-151 - Information: (Whitepaper) Enforce people to use SMK for testing?
- Update: none
- Responsible: Philip Helger
Jira Legacy server System JIRA serverId b5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004 key TICC-149 - Information: add a Schematron for verifying the AS4 headers. Updates directly in the issue.
- Update: none
- Responsible: Philip Helger
Jira Legacy server System Jira serverId b5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004 key TICC-146 - Information: (Whitepaper) Creation of the Whitepaper.
- Responsible: Philip Helger
Jira Legacy server System Jira serverId b5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004 key TICC-142 - Information: (Whitepaper)
- Responsible: Philip Helger
Jira Legacy server System Jira serverId b5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004 key TICC-140 - Information: (Whitepaper)
- Responsible: Philip Helger
Jira Legacy server System Jira serverId b5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004 key TICC-19 - Information: Information on how to determine and handle inactive SMP providers
- Update: work in progress
- Responsible: Philip Helger
Attachments
none