DSB Maintenance Iteration 11: Agenda & Meeting Notes (22 June 2022) - ConsumerDataStandardsAustralia/standards GitHub Wiki
Date and time: 22/06/2022, 2:00pm – 4:00pm AEST
Location: WebEx
Dial-in details:
- https://treasuryau.webex.com/treasuryau/j.php?MTID=m1d45159837de8df8bae6d3b8bb693cc3
- Dial In Number: +61 2 9338 2221
- Dial In Access Code: 2652 195 1973
- Quick Dial: +61-2-9338-2221,,26532937148## Australia Toll
Chair: Hemang Rathod, DSB
Maintenance overview: Further information
Maintenance project board: See here
Decision Proposal: This maintenance iteration is being consulted on under Decision Proposal 249
Recording
The Maintenance Iteration Calls are recorded for note taking purposes only. All recordings are kept securely, as are the transcripts which may be made from them. No identifying material will be provided without the participant's consent. Participants may email [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.
Agenda
- Introductions
- Outstanding Actions
- Release plan
- Open / Active Decision Proposals
- Iteration 11 issues
- CRs for discussion
- Any other business
- Next Steps
Meeting notes
Introductions
This week is the sixth and final call of the 11th maintenance iteration.
The purpose of the meeting is to review and close out the candidates that have been consulted on in the 11th maintenance iteration.
- Housekeeping
- Note: Tentative MI11 call planned for next week to cover issues missed today
- CRs for discussion
Outstanding Actions
Energy
- DSB/AEMO Issue #477 DSB and AEMO to meet offline and agreed on an FDO for Issue 477.
- Retailers to raise a ticket on energy usage data covering multiple FRMPs. DSB to table this in their discussions with AEMO.
- This was discussed in recent meeting with AEMO, Biza and big 3 retailers. AEMO presented their analysis which indicated the scenario accounted for less than 1%. Retailers have taken action to conduct analysis on their own data. Pending outcome, ticket may be required.
InfoSec
- DSB (In Progress) Issue #435 DSB will follow up with the CDR Rules team and the OAIC regarding privacy considerations with sharing a second-party's details under the primary consumer's consent.
- DSB to confirm PAR requirement for
scopeandclient_idoutside the request object through review of upstream specs. Issue #458 :bulb: - DSB to raise a change request and stage a proof of concept minimising the OpenID Provider Configuration End Point section to strip out parameters already required by upstream specs so that the CDS doesn't redundantly repeat normative references. Issue #458 :bulb:
- CBA to raise a change request to drop encryption for the JARM token response. Issue #458 :bulb:
Register
- INDUSTRY to provide feedback to indicate when data holders with multiple sectors will need to be represented in the Register for Issue 481. :bulb:
- ACCC to advise on what iteration issue #481 should be resolved in.
- DSB to post early analysis on issue 484 to determine whether its covered in DP245 or whether there is further work outside of the Decision Proposal. :bulb:
- ACCC to advise on whether MI12 is an appropriate iteration to resolve issue #431. :bulb:
Register / DCR
- DSB to stage the change for Issue 491 and consider a patch release.
Other
- DSB/ACCC: DSB to work with ACCC to explore opportunities to reconcile actions raised during the Maintenance Iteration.
- ACCC to provide feedback to the community on what their release schedule will look like.
MI11 Holistic Feedback
Release plan
- Decision Proposal 237 for MI 10 was approved by the Chair on 12 May 2022.
- V1.17.0 of the standards is now published and live.
Open / Active Decision Proposals
The following decision proposals are open for community feedback
| DP # | Closing date | DP |
|---|---|---|
| 229 | Placeholder | Decision Proposal 229 - CDR Participant Representation |
| 248 | No closing date | Noting Paper 248 - Energy PRD |
Future Plan
Review of Q1 and new changes: https://github.com/ConsumerDataStandardsAustralia/future-plan/projects/1
Iteration 11 Issues
All open change requests can be found here: Standards Maintenance Issues.
The standards maintenance backlog can be found here: Data Standards Maintenance
Iteration 11 Progress
The following change requests are proposed for this iteration.
CRs under consultation
Closed CRs
| Issue # | Sector | Change Request | Outcome |
|---|---|---|---|
| Issue 78 | High Level Standards | HTTP Header to be returned in the case where the request is not entirely well formed and a large page size is requested | Close issue - No change |
CRs for discussion
InfoSec
(Urgent) #521 Transition of required parameters in the CDR Arrangement JWT
- For discussion
Energy
- Review feedback and agree on next steps
- Summary of feedback
- Placement of
calculationTypeandpaymentFrequencey - Inclusion of
servicePointId- Included as part of addressing the feedback to cater for scenarios where a single account may cover multiple service/connection points, each with its own distinct payment agreement.
- For example a customer having direct debit setup for property/connection point A and manual payments for property/connection point B. In this scenario, servicePointId would be used to identify which connection point the agreement is related to.
- If same payment agreement is used for all connection points within an account, servicePointId is not required.
- Access to
servicePointId
- Placement of
#512 Distributor needed for EnergyPlan.geography object
- Review feedback and agree on next steps
CX
#485 Common Data Clusters altered for Energy Data Language
- To discuss
Register
- Review proposal
- Discuss problem space and next steps
#480 1.13.0 appears to have broken pseudonymity of Pairwise Identifiers
- Discuss problem space and next steps
#484 1.13.0 Appears to have introduced new SSA error behaviours
- Discuss problem space and next steps
- Review Deferral
#481 Provide timeline of when multiple sectors per data holder brand will be supported
- Review Proposal
**#510 Register API error codes need to be aligned with the CDS standardised error codes
- Review Proposal
MI11 Holistic Feedback
#511 Iteration 11 Holistic Feedback
- Update on contributions to date
Any Other Business
Meeting Minutes
Notes
Progress on Outstanding Action Items
Energy
- DSB/AEMO Issue #477 DSB and AEMO to meet offline and agreed on an FDO for Issue 477.
- This action will be carried over to the next MI
- Retailers to raise a ticket on energy usage data covering multiple FRMPs. DSB to table this in their discussions with AEMO.
- This action will be carried over to the next MI
InfoSec
- DSB (In Progress) Issue #435 DSB will follow up with the CDR Rules team and the OAIC regarding privacy considerations with sharing a second-party's details under the primary consumer's consent.
- No details for secondary user will be made available however a flag for complex/joint accounts will be incorporated in a later MI.
Register
- INDUSTRY to provide feedback to indicate when data holders with multiple sectors will need to be represented in the Register for Issue 481.
- ACCC to advise on what iteration issue #481 should be resolved in.
- Issue #481 has been resolved, refer to GitHub for details.
Register / DCR
- DSB to stage the change for Issue 491 and consider a patch release.
- A patch release hasn't been necessary; the update will be addressed in DP249
Other
- DSB/ACCC: DSB to work with ACCC to explore opportunities to reconcile actions raised during the Maintenance Iteration.
- No update
- ACCC to provide feedback to the community on what their release schedule will look like.
- This item will be moved to the Implementation Call.
CRs for discussion
InfoSec
(Urgent) #521 Transition of required parameters in the CDR Arrangement JWT
- Discussed new options presented by the community.
- Considered minimising cutover impact by continuing support for both methods without penalising shipping the form parameter. It was confirmed that ADRs are currently supporting this
- Discussed relaxing the MUST for Self-Signed JWT claims validation to a SHOULD. This would mean ADRs must validate everything in the JWT but expect only the
cdr_arrangement_idfrom some Data Holders - It would then leave the onus on Data Holders to uplift to ship all claims at a future date to improve their security posture.
- Agreed that the DSB would write up the requirements for review and publish to the issue.
Energy
- There were a number of issues raised in this CR resulting in the following outcomes:
- The intent of the endpoint was re-iterated - it is to provide details on how a consumer has elected to make payment/s
- Debate on inclusion of servicePoint due to the concern this change would force transformation of data which may not be possible with UTYPES and requires further Standards consultation in order to adopt a new feature.
- Preference is to retain the value as an array.
- DSB to assess if viable to remove servicePoint and keep the response as an array.
#512 Distributor needed for EnergyPlan.geography object
- There was agreement from participants on the call to introduce distributor as mandatory field, given that it only directly impacts EnergyPlan schema.
- This change will be recommended to the Chair for approval.
#505 Representation of time within EnergyPlanDetail Schema
- Concern that changing the timeString could have an impact on banking, refer RFC3339 as it already caters for it.
- There was agreement from participants on the call to not update timestring as it impacts banking sector as well. If required in the future, it can be addressed via a separate CR.
- This change will be recommended to the Chair for approval.
The following Energy CRs, in addition to a number of documentation fixes, have been consulted on and the proposed changes documented on each ticket will be recommended to the Chair:
- #472 Modify Energy Plans structure to allow Time of Use based Controlled Load rates
- #502 Review ENUM values for representation of days in Energy Standards
- #515 Clarity around GET Metrics for AER, DELWP and AEMO
- #514 Get Usage For ... Shared Responsibility APIs Payload size
CX
#485 Common Data Clusters altered for Energy Data Language
- This proposal is limited to reorganising where data language for common customer sits within the CX standards, it does not change the corresponding technical standards.
- This reorganisation involves aligning common customer language for Energy with Banking by removing the sector specificity and listing the details in a common section.
- DSBs interprets this change as having no impact, however requests Banking participants consider this and advise.
- With this additional clarification provided in the call Option 2 was supported, however there was some confusion where one participant preferred Option 1 to make no change.
- The confusion is believed to stem from the mandatory nature of some fields that are not held about organisations in the Energy sector, however while these fields are mandatory an empty array is permitted. These fields are required in the technical standards regardless of this change to the CX standards.
- This change has been requested to be marked as urgent to support Energy sector testing commencing in July.
- DSB to consider further and seek input from the Banking sector before finalising the recommendation on 29 June 2022.
Register
#510 Register API error codes need to be aligned with the CDS standardised error codes
- Concern there is insufficient time to make the changes proposed on this CR to meet Energy testing timeframes, both for the Register and participants.
- Preference is to go live with the known inconsistencies in error codes and address this change at a later stage.
- DSB to work with ACCC on appropriateness of bringing this in now and provide commentary on the CR.
There was insufficient time in the call to discuss the Register issues listed, these will now be discussed when the Approvals and Documentation call is reconvened on 29 June.
- #486 Allow ADRs to specify scopes for a Software Statement Assertion (SSA) to support cross industry software products
- #507 FDO for data holders ignoring unsupported authorisation scopes to be set earlier than energy release date
- #480 1.13.0 appears to have broken pseudonymity of Pairwise Identifiers
- #484 1.13.0 Appears to have introduced new SSA error behaviours
- #431 Register participant statuses do not detail data holder behaviour when ADR is revoked and SP inactive
- #481 Provide timeline of when multiple sectors per data holder brand will be supported
MI11 Holistic Feedback
#511 Iteration 11 Holistic Feedback
- Not discussed
Any other business
- N/A
New Actions
Energy
- DSB to assess if viable to remove servicePoint from Issue #495 and keep the response as an array.
CX
- DSB to consider Issue #485 further and seek input from the Banking sector before finalising the recommendation on 29 June 2022.
Register
- DSB to work with ACCC on appropriateness of bringing Issue #510 in now and provide commentary on the CR.
Next Steps
Resolve urgent Change Requests and reconvene the Approvals and Documentation call on 29 June 2022 to close out MI11.