Page Comparison

...

1. Approval of this agenda
2. Approval of minutes from previous meeting
3. Follow up on decisions and action items from previous meeting
4. PEPPOL AS2 profile 1.01 (TLS 1.2) - production date  → May 1st to June 1st
   1. https://github.com/OpenPEPPOL/documentation/blob/master/TransportInfrastructure/ICT-Transport-AS2_Service_Specification-1.01-2018-02-09.pdf
5. AS2 hash algorithm update (SHA2) - AS2 profile 1.2 (TICC work meeting 2018-04-20 minutes)
   
6. Non-XML payload specification
7. TVR
8. PEPPOL Directory
   1. Operations
   2. Decision for making PD integration mandatory (refer to decision #9 in TICC CMB 2017-12-05 minutes)
9. Testbed status
10. Propose a procedure for adding ISO6523 identifiers including
    1. How to apply for new identifier
    2. OpenPEPPOL decision process
    3. OpenPEPPOL Announcement
    4. Implementation (including migration process if ID was changed)
11. Approval of new ISO6523 ids to be used in OpenPEPPOL
    1. 0130 NAL (

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

       ,

       Jira Legacy
       server System JIRA columns key,summary,type,created,updated,assignee,reporter,priority,status serverId b5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004 key TICC-11

       ). 0130 was issued in August 1998 according to https://www.cyber-identity.com/download/ICD-list.pdf.
    2. Estonian Company code, 0191,

       Jira Legacy
       server System JIRA columns key,summary,type,created,updated,assignee,reporter,priority,status serverId b5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004 key TICC-38

       ,
    3. Norwegian Organizations, 0192 (

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

       )
    4. NL:OIN (0190, 

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

        for details) (was previously 9954)
12. New OIOUBL doc type id's requested (

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

    )
13. Scheduled meetings:
1. 2018-05-11, 14:00-16:00, cancelled
   
2. 2018-05-25, 14:00-16:00 CEST
14. Any other Business

...

1. Topic #7: PEPPOL Cross Community meeting on May 4th, 10:00-12:00 CEST
2. Usage of SHA2 in the PEPPOL network - see TICC work meeting 2018-04-20 minutes
3. A PEPPOL Directory work group will be set up, to handle the current open issues. Communication between Ger and Anna-Lis has been started
4. POACC Billing BIS v3 identifiers
   1. BIS v.2: https://github.com/OpenPEPPOL/documentation/blob/master/TransportInfrastructure/PEPPOL_Policy%20for%20use%20of%20identifiers-300.pdf
   2. BIS v.3: http://docs.peppol.eu/poacc/billing/3.0/bis/#_peppol_identifiers
   3. See table below
5. Sander kindly agreed to respond to ECs mail concerning PEPPOL AS4 vs. eSENS profile conformance
6. Official TICC CMB email list members are verified and correct for the current CMB members
7. Topic #5 PEPPOL AS2 1.2
   1. Proposed date for X is Ocotober 31st, 2018 (6 month from now)
   2. Proposed date for Y is January 31st, 2019 (3 month after X)
8. Topic #6 Non-XML payload proposal
   1. How to represent Text and Binary content in the SBDH

...

1. Agenda approved
2. Last meeting minutes approved.
3. #8 The date when all SMPs must technically be capable of connecting to PEPPOL Directory is October 31st, 2018
4. Official POACC Billing BIS v3 document type identifier and process identifier must follow the table in chapter "Information items"
5. #5 PEPPOL AS2 profile 1.2 to be created as suggested in TICC work meeting 2018-04-20 minutes
6. #6 Non-XML payload specification
   1. All changes needed on that topic should go into PEPPOL Envelope specification
7. #11: the new participant identifier issuing agencies with the IDs 0130, 0190, 0191 and 0192 were all unanimously approved, but the details for using them need to be specified separately.
   1. Usage of the new IDs is therefore not allowed yet until the following actions have been completed
      1. Informing the SML
      2. Publish the code list - currently part of PEPPOL Policy for the use of identifiers 3.0.0
      3. Country specific validation artefacts may refer to old IDs (e.g. 9908 --> 0192) - migration period needed?
      4. We need "BIS notation for every ID" (0191 = EE:CC)

...