Versions Compared

Key

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

🎯 Objective

Capture requirements across all subgroupsPolicies relevant for the Architecture.

\uD83D\uDDD2 Requirements

Requirement

User Story or ValuePolicy

Definition

Importance

Origin

Notes

  1. Improved participant migration process from one SMP to another SMP

#

Coordinate with SMP 2.0 WG

  1. Add support for an “alive” check of the SMP

 #

 

 

Coordinate SMP 2.0 WG topic

  1. Keep the principle of connecting once and reaching every end-user who wants to receive Peppol-business-documents.

#

architecture to find the meta-data to reach any individual end-user.

Need to define rules which ensure uniqueness of a logical identifier of the end-user, which can be as easily shared as an e-mail-address.

  1. DNS-zone should not grow beyond a specific number of entries

#

Lookup and replication is then slower) and that a lookup from the APAC-region in a western-European DNS-zone is slower than in a APAC-region located zone.
  1. Peppol eDelivery is conceptually one highly connected infrastructure/ecosystem

#

High

#

#

  1. Data and Service sovereignity

#

Under investigation

Mandate

(warning) Out of Scope

  • #