Date: 2018-05-25
...
Collanus, Risto <risto.collanus@visma.com>
Helger, Philip <philip.helger@brz.gv.at>
Langøy, Bård <bard.langoy@pagero.com>
...
Berg, Anna-Lis <anna-lis.berg@difi.no> during agenda topic 2,3 and 4 only.
Observers (without voting right)
...
- Approval of this agenda
- Info: PEPPOL Directory status (Anna-Lis Berg)
- Info: Testbed status (Anna-Lis Berg)
- Info: PKI Migration status (Anna-Lis Berg)
- Approval of minutes from previous meetings 2018-04-27 and 2018-05-03.
- Follow up on decisions and action items from previous meetings 2018-04-27 and 2018-05-03.
- TVR (follow up meeting no.2 scheduled Jun 4, 15:00 CEST)
- Danish OIOUBL doc type id's requested (
)Jira Legacy server System JIRA serverId b5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004 key TICC-37 - Approval of NHS document types (
)Jira Legacy server System JIRA serverId b5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004 key TICC-45 - Approval of Danish ICD 0184 (
)Jira Legacy server System JIRA serverId b5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004 key TICC-26 - Approval of v 3.1 of "PEPPOL policy for use of identifiers" (https://github.com/OpenPEPPOL/documentation/tree/master/TransportInfrastructure)
- Use of ICD in PEPPOL Policy for Identifiers, policy 8 (
)Jira Legacy server System JIRA serverId b5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004 key TICC-46 - AS2 SHA256 update
- Comment from André Hoddevik (May 4, 2018 8:02 PM)
- The SHA256 update was only one of the capability extension WG issues handled last year. Timestamp in the MDN was another. Will you in this process follow up on other change requests than the SHA256/512 for the AS2 spec when a version 1.2 will be prepared?
- Annex 3 needs to updated as well to reflect correct references (please find it on Document Repository - Current Agreement Documents/wiki/spaces/Public/pages/90308614)
- Comment from André Hoddevik (May 4, 2018 8:02 PM)
- Propose a procedure for adding ISO6523 identifiers including
- How to apply for new identifier
- OpenPEPPOL decision process
- OpenPEPPOL Announcement
- Implementation (including migration process if ID was changed)
- Scheduled meetings:
- 2018-06-08, 14:00-16:00 CEST
- 2018-06-22, 14:00-16:00 CEST (re-schedule due to public Swedish and Finnish holiday)
- Any other Business
...
- Agenda approved
- Anna-Lis Berg informed about # 2,3 and 4
- Approval of minutes from TICC CMB meetings 2018-04-27 and 2018-05-03.
- #11 "PEPPOL policy for use of identifiers v.3.1" was approved. It is available on https://github.com/OpenPEPPOL/documentation/tree/master/TransportInfrastructure.
- #9 The customizationIds for Order and OrderResponse described in
were approved by TICC CMB assuming POACC CMB has approved the business documents.Jira Legacy server System JIRA serverId b5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004 key TICC-45
Action items
- Send out a call for candidate for one CMB member (to succeed Olav Kristansen, Difi) in mid June so that the new member can be elected.
- Consider introducing a global CMB decision log and action log to enable swift follow up of decisions and actions.
- Hans Berg will add edit restrictions to previous meeting minutes
- Hans Berg to ask Former user (Deleted) to attend a CMB to discuss/inform about
- ISO6523 id inclusion in OpenPEPPOL: process
- #7 TVR
- Philip Helger to integrate comment from public review etc.
- PUBLIC_KEY of C2 required for PEPPOL AS4 profile
- In the same formatting as provided in SMP
- SENDER_CERTIFICATE key for SBDH
- State that MLR SMP registration should not be considered
- Annex on how to handle C4 validation
- 2.5.5 add note on certificate change (Martin’s comment #4)
- Comment Martin #5: severity MUST be failure, EBMS:0001, PEPPOL AS4 spec states, that participant check is needed -> same check here
- 2.5.3: if negative TVR is received later than 2:30 than the problem must be resolved out-of-band
- PUBLIC_KEY of C2 required for PEPPOL AS4 profile
- Philip Helger to integrate comment from public review etc.
- #2 PEPPOL Directory
- Hans Berg to trigger an information to all SMP providers (Oct 31st 2018) in accordance with Former user (Deleted) (according to decision # 3 in TICC CMB 2018-04-27 minutes)
- Billing BIS v3
- Philip Helger to contact POACC on the usage of document type and process identifiers (and schemes) for Billing BIS v3
- PEPPOL AS4 vs. eSENS profile conformance
- Philip Helger to provide has distributed Sander's response to TICC CMB when availableon May 2nd.
- # 13 PEPPOL AS2 1.01 date of obligation
- Hans Berg to send out information to all AP members (in accordance with Former user (Deleted)) that the new PEPPOL AS2 profile is mandatory by June 1st, 2018. Also an information item should be published on the peppol.eu websiteA post on the the website is available at https://peppol.eu/updated-peppol-as2-specification.
- Hans Berg to draft a change request (to agreement workgroup) for Annex 4 to remove hard coded references to technical specs.
- PEPPOL AS2 1.2 - SHA-256 support
- Non-XML Payload specification
- Define real action items in next TICC CMB meeting
- New identifier issuing agencies
- Philip Helger to create has uploaded PEPPOL Policy for the use of identifiers 3.1 with the sole purpose to decouple codelist from usage guideline. No content related changes are done except from removing codelists from the document.
- The changes can be used in production immediately
- The code lists as well as the updated policy document will be made available publically on the OpenPEPPOL GitHub repository on https://github.com/OpenPEPPOL/documentation/blob/master/TransportInfrastructure/PEPPOL_Policy%20for%20use%20of%20identifiers-310.pdf and
- Philip Helger to create has uploaded PEPPOL Policy for the use of identifiers 3.1 with the sole purpose to decouple codelist from usage guideline. No content related changes are done except from removing codelists from the document.
- #12 Bård Langöy to draft a proposal as commented in
.Jira Legacy server System JIRA serverId b5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004 key TICC-46 - #10 '0184' approved as requested in
, even though it was already in the PEPPOL identifier scheme list for quite some time.Jira Legacy server System JIRA serverId b5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004 key TICC-26
Attachments
Attachments |
---|