ACCC & DSB | CDR Implementation Call Agenda & Meeting Notes | 25th of November 2021 - ConsumerDataStandardsAustralia/standards GitHub Wiki
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: [email protected]
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
- Introductions
- Actions
- CDR Stream updates
- Presentation
- Q&A
- 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 [email protected] 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 |
|---|---|---|
| Standards | Version 1.14.0 Published | Link to change log here |
| Standards | v1.15.0+ is planned for mid December | Pending any minor tweaks, fixes or amendments to v1.14.0 |
| Maintenance | 9th Maintenance Iteration | Agenda from the 24th of November 2021 meet |
| Maintenance | 9th Maintenance Iteration | Extended until 1st of December 2021 Dates updated here on the comment in Decision Proposal 212 |
| Maintenance | Decision Proposal 212 - Banking Maintenance Iteration 9 | Link to consultation |
| 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 | 11th of November 2021 | View in browser here |
| DSB Newsletter | 19th of November 2021 | View in browser here |
| Consultation | Normative Standards Review (2021) | Link to consultation |
| Consultation | Decision Proposal 222 - CX Standards & Insights and Trusted Adviser Disclosure Consents | Link to consultation |
| Consultation | Decision Proposal 225 - Data Recipient Security Standards | Link to consultation |
| Consultation | Decision Proposal 162 - CX Standards & Joint Accounts | Link to consultation |
| Action | Question: "Hi can it be confirmed if there will be any changes announced between 16 Dec to 20 Jan?" | 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 - Banking | Mark Verstege |
| DSB | Technical Standards - Energy | Hemang Rathod |
| DSB | Technical Standards - Engineering | James Bligh |
Presentation
Title: Participant view of conformance test execution log Presenter(s): Munishwar Bajwa, Preeti Patel About: CTS has recently enabled a participant view of logging for conformance test execution. The information displayed in the log is being improved iteratively. This presentation will cover the new participant view, the information we currently present and what is planned during next iteration. We also welcome your feedback on priorities for future iterations.
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 |
|---|---|---|
| 865 | Q: Will the ACCC require data holders to retest via CTS for CDR Phase 2? Section 4.3.2 of the Test Strategy says ‘under certain circumstances ACCC may mandate or request existing participants retest their solution through CTS’. We were advised that the guidance remains the same at this stage, which is to say that phase 2 is still in the development stage and that at this stage the ACCC are advising participants to revisit CTS post activation. Does this mean that we should plan for testing post CTS activation? It is not clear what ‘advising participants to revisit CTS post activation’ actually means. We would like to understand If we need to plan for this. | Please see section 4.3 of the CDR Participant Conformance approach for more information. https://www.cdr.gov.au/sites/default/files/2021-08/CDR_Participant%20conformance%20approach_v1.0_1.pdf |
| 1181 | Are there are any specific requirements with regards to Test Data when conducting CTS. eg, type of accounts, no. of accounts etc. Also, does the CTS tests invoke all the CDR APIs as part of the e2e flow. | Thank you for contacting us, please refer to the CTS Technical Guidance documentation linked below - if you have any further questions post review of the below, please do not hesitate to let us know. https://cdr-support.zendesk.com/hc/en-us/articles/900004178766-CTS-Guidance-Materials |
| 1189 | Error Handling. Will the ACCC be mandating the Error Handling CTS before February 2022, if not will the ACCC be verifying in the live ecosystem? | As per the Participant Conformance Approach the ACCC will allocate participants the most relevant test plan for their obligation date. In regards to February 2022 obligations the most relevant CTS test plan is v3.4 The ACCC does not intend to mandate v3.4 for active participants although v3.4 is available for participants should they wish to confirm usage of standardised error codes in preparation for February 2022. Please do not hesitate to reach out and discuss with your ACCC contact via [email protected] Note - as per the Participant Conformance Approach under certain circumstances, the Registrar may mandate active participants to retest their solution through the CTS. The Registrar will confirm the test plan to be completed. As with all mandatory standards and CDR obligations, the expectation is that all participants comply. Any non-compliance would be considered in-line with the ACCC/OAIC Compliance and Enforcement Policy for the Consumer Data Right. |
| 1195 | We would like to understand whether the API developer portal is mandatory for all banks, at the time of going live with Consumer data-sharing APIs in the Open Banking ecosystem. If it's not mandatory at the time of going live, please advise the timeframe by when the portal is expected to be made available after the point of go-live. On the other hand, we're also keen to know whether it's always left as an option at the discretion of data holders to make the API developer portal available publicly. | I have checked with the rest of the DSB team. While there is a clear obligation for a Data Holder to present certain experiences such as the CDR Policy and Data Holder Dashboard, we are not aware of an obligation to publish a developer portal. There is certainly no obligation for this in the standards. Which part of the rules/legislation were you specifically interpreting as requiring this? If you can point me to the clauses you're concerned about I get seek some better advice. |
| 1199 | I note in the CDR Rules Expansion Amendments Consultation Paper Sept 2020 the ACCC indicated they would likely release an explanatory statement for nominated representative rules. Is the ACCC releasing an explanatory statement on Competition and Consumer (Consumer Data Right) Amendment Rules (No. 1) 2021 that would cover Secondary Users/Nominated representatives? And if so when? | The ACCC plans to provide guidance on CDR representatives, nominated representatives (which are relevant to business consumers) and secondary users by the end of this year or early next year. |
Useful Links
View a number of informative and useful links in the Consumer Data Standards Implementation Guide on Information Links.