OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

bdxr message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Minutes of Atlantic BDXR TC call 01 July 2020 15:00UTC - Voting Meeting

Minutes of Atlantic BDXR TC call 01 July 2020 15:00UTC


Atlantic: 10:00MSP/10:00Lima/11:00Ottawa/15:00UTC/17:00Europe




Todd Albers

Kenneth Bengtsson (chair)

Ger Clancy

Sander Fieten

Philip Helger

Matt Vickers

Dennis Weddig


Pacific call:


Todd Albers

Kenneth Bengtsson (chair)

Erlend Klakegg Bergheim

Ken Holman

Levine Naidoo


Standing items


Review of Pacific call minutes



Review of Atlantic call minutes



Membership status review



Voting status is determined by the following:

existing voting members must not miss two consecutive meetings to maintain voting status

non-voting members must attend two consecutive meetings to obtain voting status

members formally on leave by prior request must not attend and their voting status is not impacted


Current BDXR TC voting member list (alphabetical):


-   Todd Albers

-   Kenneth Bengtsson

-   Erlend Klakegg Bergheim

-   Ger Clancy

-   Sander Fieten

-   Philip Helger

-   Ken Holman

-   Levine Naidoo

-   Matt Vickers

-   Dennis Weddig


SMP 2.0


SMP 2.0 Committee Specification 02 has been approved and published: https://lists.oasis-open.org/archives/bdxr/202001/msg00009.html


Status of Statements of Use:

-   Difi (OpenPEPPOL?)

-   IBM

-   Philip Helger


-   Sander Fieten

-   Business Payments Coalition

-   Efact


Requirements: https://www.oasis-open.org/policies-guidelines/oasis-defined-terms-2018-05-22#dStatementUse


Kenneth and Erlend will set up SMP test servers and share sample participant and service IDs with Sander and Philip for interoperability testing.


Exchange Header Envelope (XHE)


Received Statements of Use:

-   ph-xhe: https://lists.oasis-open.org/archives/bdxr/202006/msg00015.html

-   IBM: https://lists.oasis-open.org/archives/bdxr/202006/msg00017.html

-   Efact: https://lists.oasis-open.org/archives/bdxr/202006/msg00016.html


Does the TC accept the Statements of Use for Exchange Header Envelope (XHE) Version 1.0 approved on 05 September 2019 provided by ph-xhe, IBM and Efact in the above emails?


Ken made the motion, seconded by Todd. Approved by all voting members present at the Pacific and Atlantic TC calls.


Does the TC approve the Chair requesting that TC Administration hold a Special Majority Vote to approve submitting Exchange Header Envelope (XHE) Version 1.0 Committee Specification 02 at https://docs.oasis-open.org/bdxr/xhe/v1.0/cs02/xhe-v1.0-cs02.zip as a Candidate OASIS Standard, subject to any editorial changes that may be required?


Kenneth made the motion, seconded by Ken. Approved by all voting members present at the Pacific and Atlantic TC calls.




BDXL administration API


Proposal from Erlend: https://lists.oasis-open.org/archives/bdxr/201905/msg00015.html


There have been discussions within Peppol regarding requirements for the BDXL Administration API. Sander will reach out to the involved participants to gather further requirements.


Agreed that the updated BDXL 1.1 specification will mention the BDXL Administration API and its features for updating and maintaining BDXL records.


Discussed that the BDXL Administration API could include a section for how to update a primary BDXL in a federated model.


Anyone who wish to take the lead editorship?


BDXL 1.1


Starter document received from OASIS: https://lists.oasis-open.org/archives/bdxr/202002/msg00015.html


Discussed that the hostname to look up the NAPTR record (commonly done as âB-[MD5 hash of participant ID]â) should be standardized.


Federated BDXL


Agreed to add a section about BDXL network federation to BDXL 1.1. Both Peppol and the Business Payment Coalition are working towards federated BDXL designs.


BPC rationale is to create competition among several BDXL service providers, allowing network participants to freely choose among available services. All BDXL services will offer similar and compatible services.

Requirements: https://lists.oasis-open.org/archives/bdxr/202006/msg00003.html


Peppol is looking at delegating control of different participant identifier schemes to different SML services, as well as possibly separating groups of participants based on their ID. There would be an algorithm that enables APs to locate the appropriate SML service based on the a calculation of the participant identifier. Part of the rationale is that the transactional footprint on the current SML has increased with the addition of DNSSEC, and grouping participants into different SML services is a strategy for distributing the load.


Discussion paper for multiple registration services with only one DNS provider: https://lists.oasis-open.org/archives/bdxr/202006/msg00003.html


Discussed that in DNS, zone changes are replicated from primary DNS to secondary DNS services through zone transfers and that the update of primary DNS services can be done using DNS Update: https://tools.ietf.org/html/rfc2136


Sander and Kenneth had a meeting to come up with a proposal for an architectural drawing of a federated BDXL model within the complete 4-corner network, and will share with the TC.


Discussed that the BDXL specification could/should hold information about the current registrar service of a given participant, so that BDXL and registrar services can prevent unauthorized updates of participant identifiers registered through a different registrar service.


Discussed to include a non-normative section describing different network policies and approached to KYC and participant registration.


Kenneth will begin drafting an introduction for BDXL 1.1.


TC conference call schedule


Agreed to hold weekly Atlantic meetings until further notice. Pacific calls will continue to be held biweekly and will follow the current schedule.


Face-to-face meeting

Should we schedule online work sessions to replace the face-to-face meeting?


Call schedule



-  Pacific: No call

-   Atlantic: 10:00MSP/10:00Lima/11:00Ottawa/15:00UTC/17:00Europe


-   Pacific: 17:00MSP/17:00Lima/18:00Ottawa/22:00UTC/08:00Sydney

-   Atlantic: 10:00MSP/10:00Lima/11:00Ottawa/15:00UTC/17:00Europe


-  Pacific: No call

-   Atlantic: 10:00MSP/10:00Lima/11:00Ottawa/15:00UTC/17:00Europe


-   Pacific: 17:00MSP/17:00Lima/18:00Ottawa/22:00UTC/08:00Sydney

-   Atlantic: 10:00MSP/10:00Lima/11:00Ottawa/15:00UTC/17:00Europe


-  Pacific: No call

-   Atlantic: 10:00MSP/10:00Lima/11:00Ottawa/15:00UTC/17:00Europe


-   Pacific: 17:00MSP/17:00Lima/18:00Ottawa/22:00UTC/08:00Sydney

-   Atlantic: 10:00MSP/10:00Lima/11:00Ottawa/15:00UTC/17:00Europe


-  Pacific: No call

-   Atlantic: 10:00MSP/10:00Lima/11:00Ottawa/15:00UTC/17:00Europe


-   Pacific: 17:00MSP/17:00Lima/18:00Ottawa/22:00UTC/08:00Sydney

-   Atlantic: 10:00MSP/10:00Lima/11:00Ottawa/15:00UTC/17:00Europe


Other business




[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]