ACCC & DSB | CDR Implementation Call Agenda & Meeting Notes | 7th of July 2022
When: Weekly every Thursday at 3pm-4.30pm AEST
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
- Introductions
- Actions
- CDR Stream updates
- Presentation
- Q&A
- Any other business
- 5 min will be allowed for participants to join the call.
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.
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.
By participating in the Consumer Data Right Implementation Call you agree to the Community Guidelines. These guidelines intend to provide a safe and constructive space for members to discuss implementation topics with other participants and members of the ACCC and Data Standards Body.
| Type | Topic | Update |
|---|---|---|
| Standards | Version 1.17.0 Published | Link to change log here |
| Maintenance | Maintenance Iteration 12 | Planned to Commence on the 20th of July 2022 |
| TSY Newsletter | To subscribe to TSY Newsletter | Link here |
| DSB Newsletter | To subscribe to DSB Newsletter | Link here |
| TSY Newsletter | 1st of July 2022 | View in browser here |
| DSB Newsletter | 1st of July 2022 | View in browser here |
| Consultation | Normative Standards Review (2021) | No Close Date Link to consultation |
| Consultation | Decision Proposal 229 - CDR Participant Representation | Placeholder: no close date Link to consultation |
| Noting Paper | Noting Paper 255 - Approach to Telco Sector Standards | Link to consultation |
| Consultation | Decision Proposal 256 - Telco Endpoints Feedback closes: 5th of August 2022 |
Link to consultation |
| Consultation | Decision Proposal 257 - Customer Data Payloads for Telco Feedback closes: 5th of August 2022 |
Link to consultation |
| Noting Paper | Noting Paper 258 - Independent Information Security Review | Link to consultation |
| Consumer Experience | Accessibility Report on the CX Standards and related artefacts | Link to report |
Provides a weekly update on the activities of each of the CDR streams and their stream of work
| Organisation | Stream | Member |
|---|---|---|
| ACCC | CDR Register | Emma Harvey |
| ACCC | CTS | Andrea Gibney |
| DSB | CX Standards | Michael Palmyre |
| DSB | Technical Standards - Energy & MI11 | Hemang Rathod |
| DSB | Technical Standards - Register | Ivan Hosgood |
| DSB | Technical Standards - Telecommunications | Brian Kirkpatrick |
| DSB | Technical Standards - Banking & Engineering | James Bligh |
None this week.
Questions will be received by the community via WebEx chat before the questions are opened to the floor. Participants can submit questions outside of the CDR Implementation Call to the CDR Support Portal.
In regards to topics for questions, we ask the participants on the call to consider the Community Guidelines when posing questions to the subject matter experts.
| Ticket # | Question | Answer |
|---|---|---|
| 1584 | For closed energy accounts, what is the period of sharing? Is it 2 years from the time of the arrangement setup or 2 years before the closure of the account? | The ACCC have now published an article on Zendesk about this issue that we trust will assist. You can find it here: https://cdr-support.zendesk.com/hc/en-us/articles/5097958962831 |
| 1595 | For the 4th July requirement for JWKS URIs: “Data Holders and Data Recipients JWK sets MUST NOT contain multiple keys with the same ‘kid’” As a data holder, having the JWKS endpoint https://openbanking.api.rabobank.com.au/oauth2/connect/jwks, we have multiple JWKS keys with just one key with PS256 algorithm. The kid associated with this key is shared with other keys with different algorithm which is as part of the product. Can you please let us know if we are compliant with the CDR standards for the 4th July release with this configuration? |
The Consumer Data Standards state the following: - Data Holders and Data Recipients JWK sets MUST NOT contain multiple keys with the same "kid" Therefore, the kid value MUST be unique for each key in a set. The intent here is to avoid complexity for data recipients searching for keys based on the potentially bespoke implementation of a data holder. Data Recipients can simply filter on kid to reach the key they require. |
| 1613 | I have noticed that the documentation of the DCR API has code samples where "register" is repeated twice in the URL like "https://data.holder.com.au/register/register". I would like to clarify if this is a mistake and the URL is actually supposed to be "https://data.holder.com.au/register"? | This is indeed a documentation defect, is known by the team, and is currently being staged for delivery in the 1.18.0 release of the Consumer Data Standards. Details of the issue are documented at: https://github.com/ConsumerDataStandardsAustralia/standards-maintenance/issues/487 |
View a number of informative and useful links in the Consumer Data Standards Guide on Information Links.
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
|
 |
 |