Approval of previous meeting minutes
Continue with the PEPPOL AS4 Profile v.2.0.0 review with input from Maarten Daniels (via e-mail) and Jerry Dimitriou.
Decide on Singapore 0195 (SG:UEN) identifier (
Jira Legacy
server System JIRA
serverId b5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
key TICC-60
)
Norwegian Annex 5
Service Provider reporting (see zip file in attachments)
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 minutes)
Base64 encoding of AS2 MDN: OK or not?
Open issues and tickets in the Action Log

Topics not discussed

Information items

The #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 a bad idea.

...

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.
#5 Service Provider reporting: No decision made, please find attached zip files below.
#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.

...