ACCC & DSB | CDR Implementation Call Agenda & Meeting Notes | 16th of December 2021

ACCC & DSB | CDR Implementation Call Agenda & Meeting Notes

When: Weekly every Thursday at 3pm-4.30pm AEDT
Location: WebEx, quick dial +61-2-9338-2221,,1650705270##

Meeting Details:

Desktop or Mobile Devices https://treasuryau.webex.com/treasuryau/j.php?MTID=m9614a7c6166155d3d950a8999e437f9f Once connected to your meeting remember to start your audio and video
Please mute when you are not speaking.

Video Conferencing (VC) Rooms
Use the remote control or touch panel and dial the number indicated below:
External VC Room: 1650705270@webex.com

Phones - AUDIO ONLY

• Primary Australia: +61-2-9338-2221
• Quick Dial: +61-2-9338-2221,,1650705270##
• Other Global Numbers: https://treasuryau.webex.com/cmp3300/webcomponents/widget/globalcallin/globalcallin.do?MTID=m311f46c87a3ab9ae5335a6c0ea431da4&MTID=m311f46c87a3ab9ae5335a6c0ea431da4&MTID=m311f46c87a3ab9ae5335a6c0ea431da4&MTID=m311f46c87a3ab9ae5335a6c0ea431da4&serviceType=MC&serviceType=MC&serviceType=MC&siteurl=treasuryau&siteurl=treasuryau&siteurl=treasuryau&apiname=globalcallin.php&apiname=globalcallin.php&apiname=globalcallin.php&rnd=6124483603&rnd=6124483603&rnd=6124483603&tollFree=0&tollFree=0&tollFree=0&ED=1403111402&ED=1403111402&ED=1403111402&needFilter=false&needFilter=false&needFilter=false&actappname=cmp3300&actappname=cmp3300&actname=/webcomponents/widget/globalcallin/gcnredirector.do&actname=/webcomponents/widget/globalcallin/gcnredirector.do&renewticket=0
• Meeting Number/Access Code: 165 070 5270

---

Agenda

1. Introductions
2. Actions
3. CDR Stream updates
4. Presentation
5. Q&A
6. Any other business

Introductions

• 5 min will be allowed for participants to join the call.

Recording

The Consumer Data Right Implementation Calls are recorded for note taking purposes. All recordings are kept securely, as are the transcripts which may be made from them. No identifying material shall be provided without the participant's consent. Participants may contact@consumerdatastandards.gov.au should they have any further questions or wish to have any material redacted from the record.

Acknowledgement of Country

We acknowledge the Traditional Custodians of the various lands on which we work today and the Aboriginal and Torres Strait Islander people participating in this call.
We pay our respects to Elders past, present and emerging, and recognise and celebrate the diversity of Aboriginal peoples and their ongoing cultures and connections to the lands and waters of Australia.

Updates

Type	Topic	Update
CDR Implementation Call	Today is the final CDR Implementation Call for 2021	Updates for calendar invitations have been sent.
CDR Implementation Call	Will recommence on the 13th of January 2022 @ 3pm AEDT	Invitations are in your calendar.
Standards	Version 1.14.0 Published	Link to change log here
Standards	v1.15.0+ is imminent	Pending any minor tweaks, fixes or amendments to v1.14.0
Maintenance	Decision Proposal 212 - Banking Maintenance Iteration 9	Link to consultation
Maintenance	9th Iteration Retrospective	Survey
Maintenance	10th Maintenance Iteration	To commence on 16th of February 2022
TSY Newsletter	To subscribe to TSY Newsletter	Link here
DSB Newsletter	To subscribe to DSB Newsletter	Link here
TSY Newsletter	13th of December 2021	View in browser here
DSB Newsletter	10th of December 2021	View in browser here
Consultation	Normative Standards Review (2021)	Link to consultation
Consultation	Decision Proposal 225 - Data Recipient Security Standards	Link to consultation
Action	DSB Holiday Season Plan	Link to DSB Holiday Season Plan

CDR Stream Updates

Provides a weekly update on the activities of each of the CDR streams and their stream of work

Organisation	Stream	Member
ACCC	CDR Register	Hopeson Chiao
ACCC	CTS	Andrea Gibney
ACCC	Onboarding	Christine Atkins
DSB	CX Standards	Michael Palmyre
DSB	Technical Standards - Register	Ivan Hosgood
DSB	Technical Standards - Energy	Hemang Rathod
DSB	Technical Standards - Banking & Engineering	Mark Verstege

Presentation

Version 1.15.0 of the Consumer Data Standards
Presented by: Mark Verstege, Michael Palmyre, Ivan Hosgood and Hemang Rathod

Q&A

Questions will be received by the community via WebEx chat before the questions are opened to the floor. Participants can pre-submit questions to the DSB mailing box.

We are trialling Sli.do for Question and Answer. Join our Q&A live here: https://www.sli.do/ Code: #169517

Answer provided

Ticket #	Question	Answer
1064	Is there in rules or guidance relating to what non-account data is to be shared under consent arrangements entered into be Secondary Users. There is a knowledge base article clarifying the customer detail of the Secondary User is to be shared when that SU has authorised data sharing that includes a secondary user account. However, what is to happen if the scope includes other non-account data such as saved payees? Does this include saved payees of the Secondary User, Account Holder or both?	Information about saved payees is considered to be account data under schedule 3, clause 1.3 of the CDR Rules. The secondary user is not able to share the customer data of another person but is able to share transaction data, account data, billing data and product-specific data as they are defined in schedule 3, clause 1.3 of the CDR Rules.
1182	Part 1 - 18th of November 2021 What is the reasoning behind using this field at all? What is the value of a DR passing it to a DH?	Two-fold. It is a header defined in the FAPI 1 specification. This is used to share information related to the end user for the DH to determine customer-present scenarios and whether the end user has authenticated with the ADR. This was originally considered important for data holder fraud monitoring.
1242	This regarding the Decision Proposal 208 - Binding NFRs (https://github.com/ConsumerDataStandardsAustralia/standards/issues/208). Accordingly, for the Dynamic Client Registration (DCR) API, the Data Standard has currently set 1000ms as the response time threshold. But the DCR registration request involves few external calls (1. Registration validation by ADR, 2. SSA validation, 3. Sector identifier) whereas the performance on those external endpoints is beyond the control of the data holder. We expect ACCC's clarification on the following points. 1. How the external dependencies outside of the Data Holders sphere of control are factored into this 1000ms overall response time threshold defined for the DCR API ? 2. In the current standard, a response time of 4 milliseconds is defined for unattended traffic. Similarly, will there be any consideration on increasing the response time threshold for the DCR requests as this current 1000ms threshold is highly unlikely to achieve due to the external calls involved.	The non-functional requirements do set a high expectation of performance on the dynamic client registration process. I'd like to also point you to standards-maintenance issue 418 which stresses the need for NFRs to be aligned to so that manual or slow automation is not incorporated into the registration validation process. As for changes to the NFR itself, I'd encourage you to raise an issue on the standards-maintenance issue log with your position, so this topic can be discussed in our public forums. This is the type of topic where getting input from various stakeholders on the implications of change is beneficial.

Useful Links

View a number of informative and useful links in the Consumer Data Standards Implementation Guide on Information Links.