Groups - ebCore Endpoint Update submission uploaded

[Pim van der Eijk<pvde@sonnenglanz.net>]

        Submitter's message
        Our TC has approved ebCore Agreement Update (AU) specification Version 1.0 as Committee Specification in 2016.  

AU defines a request/response protocol that parties can use to update the configuration settings for their message communication.  It consists of a general framework including an XML schema with schema extensibility for various types of updates.

The main application area of AU is updates of certificates.   The OASIS specification also defines an ebCore Certificate Update (CU) as a specialization of the generic ebCore AU protocol and abstract elements to a specific use case and substitution elements. It is similar to the earlier IETF CEM (Certificate Exchange Message) but aligns with the ebXML concept of agreements and aims to work well with ebMS and AS4 messaging protocols.

Since 2016,  ebCore CU has been implemented by a number of AS4 vendors and is endorsed/used by some user communities in Europe.   

This submission extends ebCore CU to support four additional types of changes:  
- endpoint address of a messaging server; 
- security algorithm and possibly related parameters; 
- changing a named messaging protocol profile;
- network security changes (for IP whitelisting).

It is proposed to call this combination of the four and Certificate Update ebCore Endpoint Update.  The idea is that it provides an automated scalable solution for all the common operational peer-to-peer updates of messaging channels without having to resort to something like CPPA3 Agreement Registration. 

The rationale for this submission is a request from a large user community that needs this functionality.  They could implement it as a custom ebCore AU extension,  but ideally would like it to be standardized in OASIS. 

The submission includes:
-  draft schema
-  sample instance
-  generated schema documentation

      
        
-- Mr. Pim van der Eijk

Document Name: ebCore Endpoint Update submission

---

Description
Our TC has approved ebCore Agreement Update (AU) specification Version 1.0
as Committee Specification in 2016.

AU defines a request/response protocol that parties can use to update the
configuration settings for their message communication. It consists of a
general framework including an XML schema with schema extensibility for
various types of updates.

The main application area of AU is updates of certificates. The OASIS
specification also defines an ebCore Certificate Update (CU) as a
specialization of the generic ebCore AU protocol and abstract elements to a
specific use case and substitution elements. It is similar to the earlier
IETF CEM (Certificate Exchange Message) but aligns with the ebXML concept
of agreements and aims to work well with ebMS and AS4 messaging protocols.

Since 2016, ebCore CU has been implemented by a number of AS4 vendors and
is endorsed/used by some user communities in Europe.

This submission extends ebCore CU to support four additional types of
changes:
- endpoint address of a messaging server;
- security algorithm and possibly related parameters;
- changing a named messaging protocol profile;
- network security changes (for IP whitelisting).

It is proposed to call this combination of the four and Certificate Update
ebCore Endpoint Update. The idea is that it provides an automated scalable
solution for all the common operational peer-to-peer updates of messaging
channels without having to resort to something like CPPA3 Agreement
Registration.

The rationale for this submission is a request from a large user community
that needs this functionality. They could implement it as a custom ebCore
AU extension, but ideally would like it to be standardized in OASIS.

The submission includes:
- draft schema
- sample instance
- generated schema documentation
Download Latest Revision
Public Download Link

---

Submitter: Mr. Pim van der Eijk
Group: OASIS ebXML Core (ebCore) TC
Folder: Contributions
Date submitted: 2023-02-26 08:24:54