Page Comparison

Date: 2021-06-10

Time: 09:00-1110:00 45 CEST

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

...

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

   1. Information: General agreement, but further clarifications needed.
   2. Decision: See issue for details

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

   1. Information: Align Participant Identifier Scheme Code lists of PoAC and eDEC
   2. Decision: See issue for details

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

   1. Information: New document type identifiers for PRAC
   2. Decision: Add to Code Lists v7.6
   3. Responsible: Philip Helger

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

   1. Information: Limit the AS4 port range from "443 and 44300-44399" to 443 only
   2. Decision: Agreed to ammend the AS4 profile
   3. Responsible: Philip Helger

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

   1. Information: New document type identifiers for the NO Payment domain.
   2. Decision: Add to Code Lists v7.6
   3. Responsible: Philip Helger

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

   1. Information: Creation Policy for use of Identifiers Migration Document from 4.0.0 to 4.1.0
   2. Responsible: Philip Helger

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

   1. Information: Creation SMP Migration Policy for 1.1.0 to 1.2.0
   2. Responsible: Philip Helger

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

   1. Information: Updated website available, specification documents would be ready for publication
   2. Update: Alignment with CC and OO needed
   3. Responsible:  Martin Mane (Unlicensed), Philip Helger

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

   1. Information: The term "Subject Unique Identifier" in the Peppol SMP specification 1.1.0 requires clarification, as this certificate field is not present in the Peppol certificates.
   2. Decision: It was agreed to use the "X.509 Certificate Subject X.500 Name" as the identifier of the SMP to redirect to. Will be part of the next round of eDEC specifications. The collection issue for this one is

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

      .
   3. Responsible: Philip Helger

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

    1. Information: Have a separate participant identifier prefix for testing purpises.
    2. Decision: Should also be part of the Whitepaper.

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

    1. Information: regarding joint information on news and noteworthy
    2. Decision: see ticket for details. OO to execute the actions.

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

    1. Information: Clarification on the words "custom validation" in the AS4 profile was sought.
    2. Decision: A clarification was stated as a response to the ticket, that "custom validation" does NOT include business document validation. Improvement of the wording in the AS4 spec was put in the backlog.

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

    1. Information: Deprecate the AS2 transport protocol
    2. Update: Questions have been designed by OO and agreed with the PA Community. Most suitable way forward is sought be OO. Waiting for the results.

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

    1. Information: Updated the issue
    2. Decision: Further evaluate if ISO 6523 structuring can be used more efficiently (like in 9915:123456789:sadhjsadghas). Look into the ISO 6523 standard. Is most likely of strategic relevance.
    3. Responsible: Martin Mane (Unlicensed)

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

    1. Information: https for SMP; Philip sent out an email (2020-11-18) with a decision basis paper
    2. Update: CC action CC8-1 refers to this. On hold until the whitepaper is finished.
    3. Responsible: Philip Helger

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

    1. Information: Enforce people to use SMK for testing?
    2. Decision: Part of the Whitepaper.
    3. Responsible: Philip Helger

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

    1. Information: add a Schematron for verifying the AS4 headers. Updates directly in the issue
    2. Update: no update
    3. Responsible: Philip Helger

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

    1. Information: Creation of the Whitepaper. No further updates.
    2. Responsible: Philip Helger

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

    1. Information: Part of Whitepaper.
    2. Responsible: Philip Helger

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

    1. Information: Part of Whitepaper
    2. Responsible: Philip Helger

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

    1. Update: No further update. Wait for OO polling the AS2 usage and than piggyback on this solution
    2. Responsible: Martin Mane (Unlicensed)

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

    1. Information: Publication of the eDEC specification backlog.
    2. Update: Open for feedback until 2021-03-18
    3. Responsible: Martin Mane (Unlicensed)

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

    1. Update: none

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

    1. Update: Part of Whitepaper
    2. Responsible: Philip Helger

...