Date: 2020-10-01

Time: 09:00-10:45 20 CEST

Type of meeting: Gotomeeting (https://www.gotomeet.me/MartinMane)

...

Espen Kørra (Unlicensed) (DigDir) (excused)

Guests (without voting right)

...

1. Jira Legacy
   server System Jira serverId b5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004 key TICC-146

   1. Information: Based on a discussion in the CC meeting 2020-09-03
   2. Decision: Start a draft document version; link it in the TICC-132 issue
   3. Responsible: Philip Helger

2. Jira Legacy
   server System Jira serverId b5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004 key TICC-145

   1. Information: Since the Directory specification needs clarification based on TICC-144, the design should be updated as well
   2. Decision: Update the document; link it in the TICC-132 issue
   3. Responsible: Philip Helger

3. Jira Legacy
   server System Jira serverId b5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004 key TICC-144

   1. Information: Peppol Directory clarifications are approvided
   2. Decision: details are contained in the issue
   3. Responsible: Philip Helger

4. Jira Legacy
   server System Jira serverId b5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004 key TICC-143

   1. Information: It was decided, that the value MUST be checked since it is a "MUST" in the specification. Messages having a different value MUST be rejected.
   2. Decision: A clarification to be written in the issue and communicated to the caller.
   3. Responsible: Martin Mane (Unlicensed)

5. Jira Legacy
   server System Jira serverId b5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004 key TICC-142

   1. Information: "Participant highjacking" happened quite often in Singapore some time ago.
   2. Decision: To be parked for discussion in future CMB meetings.

6. Jira Legacy
   server System Jira serverId b5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004 key TICC-140

   1. Information: It's about the harmonization of identifier values and identifier schemes.
   2. Action: To be parked for discussion in the upcoming CC meeting.Related to TICC-146 as well
   3. Responsible: Martin Mane (Unlicensed)

7. Jira Legacy
   server System Jira serverId b5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004 key TICC-138

   1. Information: New participant identifier scheme for GS1
   2. Action: Still parked.
   3. Responsible: Philip Helger

8. Jira Legacy
   server System Jira serverId b5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004 key TICC-133

   1. Update: No changesReceived email from Bård Langöy on the same topic; We're planning to conduct a survey on Service Providers/eDEC members related to the following topics
      
      1. Maximum file size
      2. Maximum payload
      3. Network timeouts
      4. Differentiation between sending and receiving?
   2. Responsible: Martin Mane (Unlicensed)

9. Jira Legacy
   server System Jira serverId b5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004 key TICC-132

   1. Update: Still pending
   2. Responsible: Martin Mane (Unlicensed)

10. Jira Legacy
    server System Jira serverId b5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004 key TICC-98

    1. Update: none

11. Jira Legacy
    server System Jira serverId b5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004 key TICC-19

    1. Update: Philip to send the summary to EDEC CMB for further evaluation
    2. Responsible: Philip Helger

...

1. Next meeting on Thursday October 15th, 9:00 to 11:00 CEST
2. Bard received an informal information that the "Peppol Policy for Transport Security" is to be revoked and integrated into an Agreement Framework Update document.
   1. Martin Mane (Unlicensed) to follow up with Jostein on the ownership transition of the document
3. Bard asked about the status on the reporting in relation to the Agreement Framework Update. The current document is not an eDEC document but requires an eDEC specification on top of it.
   1. Martin Mane (Unlicensed) to follow up with Jostein on the eDEC related parts of the reporting strategy
   2. Germany also introduced a national reporting requirement for German service providers
4. DDTS update
   1. Peppol Policy for use of Identifiers 4.2.0 draft, comment deadline until October 1st, EOD
5. SML 2.0 work group has been paused to be able to focus on the SML 1.0 transition/migration

Attachments