-
Notifications
You must be signed in to change notification settings - Fork 56
ACCC & DSB | CDR Implementation Call Agenda & Meeting Notes (1st of July 2021)
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.
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.
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.
| Type | Topic | Update |
|---|---|---|
| Standards | Version 1.11.0 Published | Link to change log here |
| Standards | Version 1.11.0+ | Stay tune - next version being planned |
| Maintenance | 7th Maintenance Iteration Complete | Agenda of the backlog session |
| Maintenance | Decision Proposal 178 - Banking Maintenance Iteration 7 | Link to consultation |
| DSB Newsletter | To subscribe to DSB Newsletter | Link here |
| TSY Newsletter | To subscribe to TSY Newsletter | Link here |
| TSY Newsletter | 24th of June 2021 Edition | View in browser here |
| DSB Newsletter | Pending Website Migration | Will post link once available again |
| Consultation | Decision Proposal 180 - Energy Draft Feedback Cycle 3 | Link to consultation |
| Consultation | Decision Proposal 182 - InfoSec Uplift for Write | Link to consultation |
| Consultation | Decision Proposal 183 - Purpose Based Consents | Link to consultation |
| Consultation | Decision Proposal 186 - Engineering Support | Link to consultation |
| Consultation | Decision Proposal 187 - CX Standards - Disclosure Consents | Link to consultation |
| Consultation | Decision Proposal 191 - Retailer to AEMO InfoSec Profile | Link to consultation |
| Rules | Consumer Data Right rules amendments (version 3) | Link to 30day Consultation |
Provides a weekly update on the activities of each of the CDR streams and their workplaces
| Organisation | Stream | Member |
|---|---|---|
| ACCC | CDR Register (Technical) | Ivan Hosgood |
| ACCC | Onboarding | Jonathon Ingle |
| DSB | CX Standards | Michael Palmyre |
| DSB | Technical Standards - Banking | Mark Verstege |
| DSB | Technical Standards - Energy & 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 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
| Ticket # | Question | Answer |
|---|---|---|
| 884 | Can you please clarify if "Get Account Detail" is intended to only be used for NPP transactions? How about BSB/Account No. based transactions? The mandatory service value of "X2P1.01" seems to imply that it's only intended for NPP transactions. Please confirm? |
Transaction detail is currently only intended for NPP's X2P1.01 (Osko) overlay service. It has been suggested that transaction detail be extended to describe other payment schemes in the same manner as X2P1.01. The DSB would welcome a change request to that effect if the community saw benefit. |
| 890 Part 1 | Must we include x-fapi-interaction-id in the Response Header for 403, 404 and 405 HTTP Error codes? At the moment, there is a list of error codes in ACCC website(https://consumerdatastandardsaustralia.github.io/standards/#get-accounts) for all Banking APIs that shows x-fapi-interaction-id must be included in the Response header, however it's only covering 400, 406 and 422 but not 403, 404 and 405 as mentioned above. |
The explicit list shown are mandatory errors. Noting that DHs will respond with other 4xx's based on their implementation logic and guidance from recommended SHOULDs and MAYs for error code responses. In other words, the explicit list is non-exhaustive. The x-fapi-interation-id must be returned for any error to a requested protected resource as per the FAPI specifications. |
| 890 Part 2 | In regards to your last statement, "The x-fapi-interation-id must be returned for any error to a requested protected resource as per the FAPI specifications", the developers responded back saying, "404(Wrong URL) and 405 (Wrong Method) are not Protected Resources, hence they think it's not mandatory to respond back with x-fapi-interaction-id in the header response for 404 and 405 specifically. Could you please comment on that? | that is true from the sense that the CDS does define specific resource URIs. Where it is not a voluntary protected resource or mandated protected resource then it is at the discretion of the DH's implementation. However for compatibility I would recommend a response including the x-fapi-interaction-id where the client has provided an access token and is using MTLS. |
Updating the table below - if your question/ ticket has not received a response yet the team continues to work on a response. We do apologise for the delay on some tickets, the teams are doing their best to get to everyone's questions.
To our valued CDR participants, We have undertaken a review of the CDR Support Portal as a channel for providing guidance on CDR Rules. Based on the volume and nature of questions we have received recently, we have decided to move to a model based on publishing guidance to the community, rather than providing individual responses to stakeholder questions. Our goal is to prioritise the provision of guidance that is accessible, transparent and has industry-wide application. We intend to develop this to meet clear community needs, which we will identify and prioritise based on questions and issues raised by stakeholders. We kindly ask for your patience as we work our way through the tickets, feedback and guidance
View a number of informative and useful links in the Consumer Data Standards Implementation Guide on Information Links.