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. The initial draft specifications presented several key updates, including enhancements in security measures and support for newer technologies. Notably, the initial AS4 profile 2.0 proposed the introduction of two new Profile Enhancements, while the initial SMP profile 2.0 included support for the latest OASIS SMP version 2.0, among other features. These updates signaled a backwards-incompatible evolution, where older versions of the profiles would not be interoperable with the newer ones.

The consultation aimed to gather feedback from stakeholders and experts to refine the specifications and ensure they meet the evolving needs of the digital ecosystems. Acknowledging the invaluable input received during the consultation process, the eDelivery team meticulously reviewed and addressed each comment and suggestion provided in response to the consultation. The disposition for public review comments is available online, showcasing the team's commitment to transparency and collaboration. The documents include the feedback from the eDelivery team on each comment individually:

We would like to thank our stakeholders again for their input towards the consultations on the initial AS4 and SMP 2.0 draft specifications.

What changed?

In response to the public review comments on the initial AS4 2.0 profile, several changes were incorporated. Notably, the team decided to remove the optional SBDH profile enhancement and the availability of alternative standards. Additionally, recommendations from cryptography and XML security experts influenced modifications in key transport algorithms, including the adoption of HKDF over ConcatKDF and the support for elliptic curve cryptography with the introduction of additional curves.

The second draft version of the eDelivery AS4 2.0 profile encapsulates these changes, emphasizing the adoption of HKDF for key derivation and recommending the use of the type attribute for PartyId. Furthermore, it clarifies the removal of the SBDH profile enhancement and lists mandatory curves for elliptic curve cryptography.

Similarly, the SMP 2.0 profile underwent significant revisions based on feedback received during the consultation. Adjustments were made to improve clarity and structure, such as rephrasing sentences and adding semantics for empty process collections. Additionally, the service field value for U-NAPTR records was updated to align with the OASIS SMP 2.0 standard, ensuring canonical profiling while allowing operational flexibility during network transitions.

Noteworthy changes in the SMP profile include clarifications in mapping tables, recommendations for using the schemeID attribute in SMP 2.0 documents, and editorial corrections to enhance readability.

In direct response to feedback received during the consultation process, the eDelivery initiative has introduced significant updates to the eDelivery BDXL profile, now designated as BDXL 2.0 draft. These enhancements directly address stakeholder concerns and suggestions, particularly regarding the need for improved standardization and interoperability in data exchange protocols.

Notably, the dynamic service field settings, adapting to OASIS SMP 2.0 standards, and the clear guidelines provided for handling ebCore Party Id Type identifiers in section 4.1 directly stem from comments and recommendations gathered during the consultation period. By incorporating these suggestions, the eDelivery team aims to ensure that the BDXL profile meets the evolving needs of stakeholders and facilitates seamless data exchange in the digital landscape.

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:

eDelivery BDXL 2.0 draft specification

Changes to AS4 2.0 profile

The second draft version of a major update of the eDelivery AS4 profile, building on the 2023 working draft and adding further changes to the AS4 profile:

Message Encryption: HKDF Replaces ConcatKDF
In the common profile, there is a shift in the message encryption section. Instead of ConcatKDF, we now use HKDF (HMAC-based Key Derivation Function). From a cryptographic standpoint, HKDF offers superior security. The specification for HKDF usage in XML Security is detailed in the draft update RFC 9231bis. The output of HKDF is employed to wrap a symmetric encryption key, ensuring robust protection for your data.

PartyId Type Attribute Recommendation
Section 3.4.1 introduces a recommendation to use the type attribute on PartyId. This enhancement streamlines identification and improves interoperability across systems. By adopting this practice, the profile will enhance the clarity and consistency of PartyId usage.

Streamlining SBDH and ECC Curves
There are two changes to the profile enhancements section, :

SBDH Profile Removal: The optional SBDH (Standard Business Document Header) profile enhancement has been removed. While it served a purpose, limited adoption by eDelivery users led us to streamline the common profile. Users are free to incorporate SBDH or similar schemas in their payloads.
Mandatory ECC Curves: We’ve listed specific elliptic curve cryptography (ECC) curves that are now mandatory for compliance. These curves ensure robust security and efficient key exchange.

Four Corner Topology: Type Attribute for OriginalSender and FinalRecipient

In section 4.1.2, which covers the four corner topology profile, there is a new recommendation for using the type attribute for both originalSender and finalRecipient. This small adjustment enhances clarity and consistency in topology descriptions, making eDelivery implementations more robust.

Changes to SMP 2.0 profile

This is the second draft version of a major update of the eDelivery SMP profile, building on the 2023 working draft and adding further changes to the SMP profile:

Clarified Mapping Table
The Mapping table in Section 3.2 serves as a crucial reference point for understanding the relationships between various elements. With improved clarity, it will be easier to navigate and interpret the metadata mappings.

eDelivery ebCore Party Identifiers: SchemeID Recommendation
The section dedicated to eDelivery ebCore Party Identifiers now includes a recommendation to use the schemeID attribute of the ParticipantID element in eDelivery SMP 2.0 documents. This practice enhances consistency and ensures seamless interoperability across systems. By adopting this approach, you’ll streamline the identification process and facilitate smoother data exchange.

Editorial Enhancements
The eDelivery team has invested effort in editorial improvements. These subtle tweaks enhance readability, eliminate ambiguities, and make the SMP 2.0 specification more user-friendly.

New BDXL 2.0 profile

Enhanced ebCore Party Identifiers
As now outlined in section 4.1, when dealing with BDXL, ebCore Party Identifiers now follow a specific format. The identifier value must be concatenated with the ebCore Party Id Type, ensuring seamless integration with BDXL. This streamlined approach simplifies identification and enhances interoperability across systems.

Streamlined Metadata Handling
We recognize the importance of efficient metadata management. By aligning ebCore Party Identifiers with BDXL requirements, we’ve paved the way for smoother data exchange.

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.

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. 

Blog