Updates to eDelivery AS4 2.0 and SMP 2.0 profiles & new eDelivery BDXL 2.0 profile

Changes to AS4 2.0 profile

This is the second Second draft version of a major update of the eDelivery AS4 profile that builds , building on the 2023 working draft and adds 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 In the profile enhancements section, :

• SBDH Profile Removal of the : The optional SBDH (Standard Business Document Header) profile enhancement . It has seen has been removed. While it served a purpose, limited adoption by eDelivery users , led us to streamline the common profile already supports multiple payloads and the SBDH specification has been superseded by other standards. Users can still use . Users are free to incorporate SBDH or similar schemas in their payloads.   
• Listed mandatory curves to support in the ECC Option Curve conformance clause.
In
• 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

ChangesThis 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

Changes:

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

Image Modified

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.

.