Industry Govenance - Mandatory Requirement - ebMS Header Validation

Sunsuper operates an ebms AS4 gateway which interacts with the Australian Taxation Office and the Superannuation Transaction Network (STN).   As part of being a participant in STN, Sunsuper has become a member of the Gateway Network Governance Body (GNGB) which governs the STN.  A MoU binds Sunsuper to the Service Standards for the STN.  Part of this requires STN gateways to abide by Binding Implmentation Practice (BIP) notes. 

The GNGB has ratified BIP Note 17 - ebms Header Validation - a copy is attached.

Sunsuper raised PMR 17979,999,616 -  and received this response from IBM L3 support indicating that IBM B2BAC is not compliant with BIP Note 17

From: sterling_support@ecurep.ibm.com [mailto:sterling_support@ecurep.ibm.com]
Sent: Friday, 6 April 2018 4:37 PM
To: Stephen Milburn
Subject: PMR 17979,999,616

Hi Stephen,

Good Day! Please find the response from L3 on this query:

B2b Advanced Communications is NOT complaint to the specification https://ecurep.mainz.de.ibm.com/rest/download/17979,999,616/2018-03-13/17979.999.616.BIP-Note-17-ebMS-Header-Validation.pdf completely .  There are few elements which are validated because it was used during exchange profile look up, visibility events processing or some other requirements for protocols  and these includes the elements like MessageInfo, PartyInfo and CollaborationInfo. The whole incoming xml schema validation of xml against schema (ebms-header-3_0-200704.xsd) is not supported which means the elements like MessageProperties and PayloadInfo are not validated against xsd, Also, please note that b2bAC does not support xlinks.

Hope this answers your query . Please feel free to let me know if you have any queries.
Regards
Ravi

Based on the advice from IBM, this RFE is being raised to formally request this enhancement to be considered.  If IBM choose to not proceed with this enhancement in a reasonable timeframe, under the partnership with Sunsuper/Precision, IBM should be prepared to provide evidence about a) any delay; b) application or implementation mitigations that are fully supported and tested so relevant discussions can be held with the Gateway Network Governance Body (GNGB)