Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Agenda

  1. Approval of minutes
  2. Note Out-of-session approvals
  3. New tasks and Issues
  4. Actions
  5. Information items
  6. AoB

...

  1. Jira Legacy
    serverSystem JIRA
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-153
    1. Information: "https on SMP calls"
    2. Decision: Setup a call on experts to discuss options in more detail
    3. Responsible: Philip Helger
  2. TICC-151
    Jira Legacy
    serverSystem JIRA
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-152
    Jira Legacy
    serverSystem JIRA
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    key
    1. Information: "End to end security" - is it worth going down this road from an eDEC perspective?
    2. Decision: Martin to speak to Jerry regarding end to end encryption in the Pre-Award space.
    3. Responsible:  Martin Mane (Unlicensed)
  3. Jira Legacy
    serverSystem JIRA
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-150151
    1. Information: Enforce people to use SMK for testing?
    2. Decision:
  4. Jira Legacy
    serverSystem JIRA
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-149150
    1. Decision: Response sent back to Ger to clarify issue.Information: Jira using the old Logo - not of interest to this group
  5. Jira Legacy
    serverSystem JIRA
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-148149
    1. Information: DDTS Working Group has provided a recommendation. 
    2. Decision: eDEC members to review the recommendation from DDTS Working Group and the updated 4.2.0 policy and provide out-of-session approval. TICC-148 has been approved.
    3. Responsible: All CMB members.add a Schematron for verifying the AS4 headers?
    4. Decision: The group sees value in this. Next step is to discuss it with OO to determine who is in charge, and who will publish it.
    5. Responsible: Martin Mane (Unlicensed)
  6. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-146
    1. Information: No further updates.
    2. Responsible: Philip Helger
  7. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-145
    1. Information: No further updatesThe changes to the specification were performed and now would need small review.
    2. Responsible: Philip Helger Martin Mane (Unlicensed)
  8. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-143144
    1. Information: No further updatesThe updated XML Schemas were provided in the issue. A small internal review would be good.
    2. Responsible: Martin Mane (Unlicensed)
  9. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-142
    1. Information: Part of Whitepaper.
  10. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-140
    1. Information: Part of Whitepaper
    2. Responsible: Philip Helger
  11. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-138
    1. Information: No further update
    2. Action: Still parked.
    3. Responsible: Philip Helger
  12. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-133
    1. Update: No further update
    2. Responsible: Martin Mane (Unlicensed)
  13. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-132
    1. Update: Still pending
    2. Responsible: Martin Mane (Unlicensed)
  14. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-98
    1. Update: none
  15. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-19
    1. Update: Part of Whitepaper
    2. Responsible: Philip Helger

...

Information/Discussion items

  1. Next meeting on Thursday October 29thNovember 12th, 9:00 to 11:00 CET
  2. "Peppol Policy for Transport Security" - Martin Mane (Unlicensed) provided an update on conversation with Jostein/Lefteris - eDec CMB can provide recommendations to update the policy where it applies to eDec elements.
  3. Reporting - Martin Mane (Unlicensed) provided an update - The reporting policy will be agreed to first (as part of the new Agreement Framework) with any eDec specification that is required to be developed following AFTER agreement has been reached on the reporting policy. Work will not occur 'in parallel'Every PoAC SP should be able to handle a message "payload" with a size of 100 MB. PrAC already has a minimum size limit of 2GB. It was noted that catalog is in both PrAC and PoAC and that this service should have a minimum size requirement aligned to PrAC.

Attachments