Date: 2018-10-26

Time: 14:00-16:00 CEST

Type of meeting: Gotomeeting (https://global.gotomeeting.com/join/704521469)

Participants and absents

Chair

Berg, Hans <hans.berg@tickstar.com> as eDelivery Community Leader

Elected members (with voting right)

Kristiansen, Olav Astad <Olav.AstadKristiansen@difi.no>

Collanus, Risto <risto.collanus@visma.com>

Helger, Philip <philip.helger@brz.gv.at>

Langøy, Bård <bard.langoy@pagero.com>

Guests

Jesper Larsen, OpenPEPPOL Support Lead (to discuss upcoming EHF v.3 outside the formal CMB meeting)

Agenda

1. Approval of previous meeting minutes
2. Continue with the PEPPOL AS4 Profile v.2.0.0 review with input from Maarten Daniels (via e-mail) and Jerry Dimitriou.
3. Decide on Singapore 0195 (SG:UEN) identifier ( TICC-60 - Getting issue details... STATUS )
4. Norwegian Annex 5
5. Service Provider reporting (see zip file in attachments)
6. SHA1 mandatory in AS2 still, but has been reported Oxalis Testbed AP is now using SHA256 or SHA512 (see TICC work meeting 2018-04-20)
7. Base64 encoding of AS2 MDN: OK or not?
8. Open issues and tickets in the Action Log

Topics not discussed

1. #8

Information items

1. #4 The Norwegian Annex 5 SLAs were discussed (see them attached below). The opinion of TICC CMB is that country specific and domain specific (where the PEPPOL infrastructure is used) SLA is discouraged. Also the SLA (on Attachment B) includes Corner 4, which is out of scope. The MDN requirement (from C3 to C2) is stated to 2 seconds. This is done very rarely today according to CMB members with insights into day-to-day AP operations.
2. #5 Service Provider reporting: No decision made, please find attached zip files below.
3. #7 Content transfer encoding is not mentioned at all in the PEPPOL AS2 Specs (but referenced to "RFC 2045 to 2049 MIME RFCs" on line 42 in https://github.com/OpenPEPPOL/documentation/blob/master/TransportInfrastructure/ICT-Transport-AS2_Service_Specification-1.01-2018-02-09.pdf). Also not specifically mentioned in https://www.ietf.org/rfc/rfc4130.txt, page 45. Recommendation is to add a transfer encoding section with a list of approved encodings. 

Decisions

1. See eDelivery CMB decision log

Action items

1. see TICC CMB action log.

Attachments