Updates to eDelivery AS4 2.0 and SMP 2.0 profiles & new eDelivery BDXL 2.0 profile
The eDelivery AS4 2.0 and SMP 2.0 profiles have been updated to reflect comments received during the 2023 public consultations on the eDelivery AS4 and SMP 2.0 specifications. In addition, the eDelivery team decided to offer a draft for the eDelivery BDXL profile version 2.0. Look out for the upcoming consultation on eDelivery AS4 2.0 and SMP 2.0 profiles and find out about activities and support towards their adoption!
Response to the previous consultation
In June 2023, the eDelivery team called for a consultation on the AS4 and SMP 2.0 specifications. At the time, the initial draft specification of the eDelivery AS4 profile 2.0 included updates for the security section and proposed two new Profile Enhancements. The initial draft specification of the eDelivery SMP profile 2.0 included support for OASIS SMP version 2.0, allowed publishing multiple certificates (signing, encryption and key exchange) for a transport and supported both eDelivery AS4 profiles 1.x and 2.0. Both draft Specifications mark a backwards-incompatible evolution of the profiles, where Access Points operating with profile version 2.0 cannot exchange messages with Access Points operating with profile version 1.x.
We would like to thank our stakeholders again for their input towards the consultations on the initial AS4 and SMP 2.0 draft specifications. For full transparency, you can find the disposition for public review comments added to the consultation pages. The documents include the feedback from the eDelivery team on each comment individually:
- Consultation on the eDelivery AS4 profile version 2.0 public review comments and response
- Consultation on the eDelivery SMP profile version 2.0 public review comments and response
Updated profiles available
In our continuous commitment to develop state-of-the-art data exchange in the EU, the eDelivery team is delighted to share significant developments regarding the eDelivery AS4 2.0 and SMP 2.0 profiles. Following the 2023 public consultation, the team has meticulously addressed the feedback received and are excited to present the updated eDelivery AS4 2.0 and SMP 2.0 specifications:
The profiles have not only been updated based on public feedback, but also based on internal progress. During the process it was necessary to update the BDXL profile too, a draft is available here:
Changes to AS4 2.0 profile
AS4: 3 changes, one form the consultation, 2 from internal conversations
Second draft version of a major update of the eDelivery AS4 profile that builds on the 2023 working draft and adds further changes to the AS4 profile:
In the common profile, in the message encryption section:
- HKDF is used as key derivation function instead of ConcatKDF. It is preferred from a cryptographic point of view. The specification for using HKDF in XML Security is part of the draft update RFC 9231bis. The output of HKDF is used to wrap a symmetric encryption key.
- In section 3.4.1, the use of the type attribute on PartyId is recommended
In the profile enhancements section:
- Removal of the optional SBDH profile enhancement. It has seen limited adoption by eDelivery users, the common profile already supports multiple payloads and the SBDH specification has been superseded by other standards. Users can still use SBDH or similar schemas in their payloads.
- Listed mandatory curves to support in the ECC Option Curve conformance clause.
- In 4.1.2, the four corner topology profile, recommend the use of the type attribute for originalSender and finalRecipeint
Changes to SMP 2.0 profile
Changes:
- Clarified the mapping table in section 3.2.
- Updated the section on eDelivery ebCore Party Identifiers to recommend the use of the schemeID attribute of the ParticipantID element in SMP 2.0 documents.
- Editorial.
New BDXL 2.0 profile
Changes:
- ... (Meta:SMP2)
- Updated section 4.1 to mention separate ebCore Party Id Type and identifier value must be concatenated into an ebCore Party Identifier for use with BDXL.
Adoption in 2024
To foster inclusivity and address any potential concerns on the draft of the latest profiles, we will invite you to participate in a public consultation on these updates soon - look out for the news! The final publication of the change will conclude the Specification Change Process and is expected soon after the second consultation.
We recommend that EC colleagues operating or preparing eDelivery-based ecosystems as well as eDelivery solution providers plan their adoption of the new specifications starting from now. Read about how eDelivery will support the adoption of these updated profiles. Exciting events, including meetings and an interoperability event, are on the horizon as we take a step into the future with eDelivery in 2024.
Working towards adoption is particularly important as both the AS4 2.0 as well as the SMP 2.0 specifications mark a backwards-incompatible evolution of the profile. While the old 1.15 specifications will remain functional during the transitional period, backwards incompatibility means that Access Points operating with profile version 2.0 cannot exchange messages with Access Points operating with profile version 1.x and where SMP data compatible with profile version 2.0 cannot be consumed by legacy clients.
The eDelivery Building Block
eDelivery is a building block that provides technical specifications and standards, installable software and ancillary services to allow projects to create a network of nodes for secure digital data exchange.
| Excerpt | ||
|---|---|---|
| ||
Read about the updates to the eDelivery AS4 2.0 and SMP 2.0 profiles and why we are updating the eDelivery BDXL profile. |