...
Langøy, Bård <bard.langoy@pagero.com>
GuestsNone
Agenda
- Continue where we left off yesterday with to discuss remaining issues with PEPPOL AS4 Profile v.2.0.0 review
- TLS port numbers
- Recommend to use port 443, but allow for ports in the range 44300-44399 only if absolutely necessary. The onboarding tests may require the usage of port 443.
- MSH party role values
- see below
- Comments from Difi
- Why are we duplicating information from CEF profile?
- For simplicity of reading because the existing profile is already difficult to understand: EBMS 3 → AS4 → CEF eDelivery → PEPPOL Profile
- Additionally allow for TLS 1.3 (not just 1.2)
- Why are we changing identifiers in chapter 4.5?
- The fact that implementers have already started to implement using the RC is not a valid argument since implementers always have to adapt to specification updates. OpenPEPPOL does not provide specs for specific software implementations. A guiding principle for OpenPEPPOL specs is that they should be open and ensure interoperability.
- TICC CMB agreed to keep the proposed changes to the PEPPOL AS4 Profile v.2.0
- Why are we duplicating information from CEF profile?
- .0RC, to allow for generic reuse of the PEPPOL profile.
- According to the CEF conformance tests rules, Oxalis and other AS4 AP implementations have to be able to modify the roles for testing. The required code are already available in Oxalis at https://github.com/difi/Oxalis-AS4/blob/master/src/main/java/no/difi/oxalis/as4/util/Constants.java
- The documentation of the TLS certificate usage requirements will be in the "Trust Network Certificate Policy" specification, that is already referenced from TIA Annex 4 (see decision below).
- Profile needs to be finished by Monday after lunch.
- TLS port numbers
- Approval of previous meeting minutes (TICC CMB 2018-10-12 minutes, TICC CMB 2018-10-26 minutes)
- Decision on approving Islandic IS:KT 0196 for use in PEPPOL eDelivery network (
) (HB, BL and RC has already approved by commenting the Ticket, now waiting for PH)Jira Legacy server System JIRA serverId b5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004 key TICC-61 - Decide on remaining actions on
Jira Legacy server System JIRA serverId b5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004 key TICC-54 - AP SSL Certificate policy (
and Edicom/EVRY)Jira Legacy server System JIRA columns key,summary,type,created,updated,assignee,reporter,priority,status serverId b5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004 key TICC-57 - Annex 3 and Annex4 updates proposed by Jostein Frömyr (see attachments)
- PEPPOL Directory: Announcment Announcement for mandatory support for SMP's (6 months notice required according to André Hoddevik).
- Go through unresolved issues and tickets in the Action Log
Topics not discussed
- -
Information items
- The publication on the note that PEPPOL Directory becomes mandatory must be published on the PEPPOL web site (see Mail from Ger, from September 28th, 2018)
- Agenda for October F2F:
- Please change the session "SBDH v.1.1 and upcoming v.1.2 (support for non xml payloads)" as follows:
- Half hour only
- Add a second half hour for "PEPPOL AS2 profile 1.01 and upcoming v1.2 (support for new algorithm suites)"
- Please change the session "SBDH v.1.1 and upcoming v.1.2 (support for non xml payloads)" as follows:
...
Decisions
- Topic #5: It was decided to put the SSL certificate policy in the document https://github.com/OpenPEPPOL/documentation/blob/master/TransportInfrastructure/ICT-Transport-Trust_Network_Certificate_Policy-2.00.pdf
- Reference this from AS2 and AS4 transport profiles
Action items
- see TICC CMB action log.
...