Versions Compared

Old Version 12

changes.mady.by.user Hans Berg

Saved on

compared with

New Version 13

changes.mady.by.user Philip Helger

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Updated Technical Implementation matrix

...

v2: current PKI version.

v3: new PKI version



Access PointSMP

PEPPOL Directory

SMLOpenPEPPOL

SendingReceivingServerClient


After T1
No action required.
  • Must be able to validate MDNs signed with PKI v3
  • MUST accept an incoming transaction signed with either PKI v2 or PKI v3.
  • MUST update AP configuration in SMP if PKI v3 is used.
    • No action required
    • Must accept responses signed with PKI v2 and v3
    • MUST accept SMP client certificates for both PKI v2 and v3.
    • MUST accept SMP client certificates for both PKI v2 and v3.

    After C1





    No certificates issued for PKI v2.

    ??Question PH: doesn't that also mean: every participant received a new v3 certificate?

    No later than T2
    • MUST be able to sign transactions with PKI v3.
    No action required.Deploy SMP client cert for PKI v3
    • Must use PKI v3 to sign MDNs
    • MUST update AP configuration in SMP if PKI v3 is used.
    • Provide PKI v3 SMP certificate to SML operator so they can update their entry.
    • Update all SMP entries to use a PKI v3 AP certficate
    • Must use PKI v3
    • Must use PKI v3
    • Must use PKI v3

    After T2
    • Disable PKI v2 support
    • Disable support for receiving transactions signed with PKI v2.
    • Disable PKI v2 support
    • Disable PKI v2 support
    • Disable PKI v2 support
    • Disable support for SMP client PKI v2 certs.


    How to act as a service provider?

    ...