-
Notifications
You must be signed in to change notification settings - Fork 56
DSB Maintenance Iteration 13: Agenda & Minutes (23 November 2022)
Date and time: 23/11/2022, 2:00pm – 4:00pm AEDT
Location: Microsoft Teams Meeting
Dial-in details:
- https://teams.microsoft.com/l/meetup-join/19%3ameeting_MzRhZmJhZTctYzRhNi00ZGY4LTkxZDgtYWU5YWVmMjczMTBj%40thread.v2/0?context=%7b%22Tid%22%3a%22214f1646-2021-47cc-8397-e3d3a7ba7d9d%22%2c%22Oid%22%3a%2257cd8c59-9b50-4670-bc85-25281a11ec8d%22%7d
- Meeting ID: 496 099 061 829
- Passcode: qten9K
- Dial In Number: +61 2 9161 1229
- Phone Conference ID: 118 337 962#
- Quick Dial: +61 2 9161 1229,,118337962# Australia, Sydney
Chair: James Bligh, DSB
Maintenance overview: Further information
Maintenance project board: See here
Decision Proposal: This maintenance iteration is being consulted on under Decision Proposal 272: Maintenance Iteration 13
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.
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.
- Introductions
- Outstanding Actions
- Release plan
- Open / Active Decision Proposals
- Proposing changes to the Standards
- Maintenance Iteration 13 Issues
- Urgent Changes
- Any other business
- Next Steps
Meeting notes
The purpose of this meeting is to discuss approvals and documentation for Maintenance Iteration 13 change requests to conclude the iteration.
- Retailers to raise a ticket on energy usage data covering multiple FRMPs. DSB to table this in their discussions with AEMO.
- Analysis ongoing
- The DSB has asked participants to publicly request Issue #479 be treated as urgent on GitHub.
- Only one participant request was made.
- This request will be taken to the Chair for a decision this week.
- See Release Plan for latest information.
None
- DSB to confirm with Energy retailers that readQualities in comment does not cause a breaking change.
- This defect was fixed in version 1.20.0 of release standards.
- DSB to consider the timing of retros and advise on a planned approach.
- The purpose of the Retro is to review the Maintenance Iteration process not the outcome of it.
- We'll keep this action open to revisit the discussion at the end of MI13.
- The Data Standard's Chair has approved Issue #479 in combination with Issue #547 be treated as urgent. A separate Decision Proposal will be drafted for these changes to be staged and made in v1.21.0
- Changes for MI13 will be staged for community review in preparation for Decision Proposal 272: Maintenance Iteration 13 to be drafted for approval from the Chair in v1.22.0.
The following decision proposals are open for community feedback
DP # | Decision Proposal | Closing date |
---|---|---|
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 |
Noting Paper | Noting Paper 258 - Independent Information Security Review | Link to consultation |
Consultation | Decision Proposal 267 - Telco Data Language | TBD Link to consultation |
Consultation | Noting Paper 273 - Consent Review | Workshop on 22/11/2022 Link to consultation |
Consultation | Decision Proposal 275 - Holistic Feedback on Telco Standards | TBD Link to consultation |
Consultation | Noting Paper 276 - Proposed V5 Rules: Standards Impacts | TBD Link to consultation |
Review of October-December Quarter and new changes: https://github.com/ConsumerDataStandardsAustralia/future-plan/projects/1
Continue the discussion on channels available when proposing changes to the standards. See minutes from the meeting on 26/10/2022 for more detail.
All open change requests can be found here: Standards Maintenance Issues.
The standards maintenance backlog can be found here: Data Standards Maintenance
Domain | Issue # | Issue | Proposal Status | Change Proposed | Standards Staging link |
---|---|---|---|---|---|
InfoSec | Issue #479 | Clarification on Minimum Algorithm Required for JARM | Proposal made | Adopt minimum set of encryption and signing algorithms. | Marked as Urgent by the Chair |
InfoSec | Issue #547 | Update SSA and Client Registration standards for JARM and Authorization Code Flow | Proposal made | Update OIDD and DCR APIs to support JARM negotiation | Marked as Urgent by the Chair |
-
Issue #479: Clarification on Minimum Algorithm Required for JARM
-
Issue #547: Update SSA and Client Registration standards for JARM and Authorization Code Flow
-
Issue #522: OpenID Provider Configuration End Point parameter requirements
-
Issue #535: Standard appears to redefine requirements for private_key_jwt authentication
-
Issue #546: Update Register and DCR Swagger specs to use Common Field Types
-
Issue #544: Update x-v header to be mandatory for Register APIs
- Retailers to raise a ticket on energy usage data covering multiple FRMPs. DSB to table this in their discussions with AEMO.
- Analysis ongoing
None.
None
None
- DSB to consider the timing of retros and advise on a planned approach.
- DSB will trial holding the Retrospective once the DP has been drafted and changes staged.
- DSB to schedule an adhoc MI Meeting to conduct the MI13 retrospective before the end of the year.
- The Data Standard's Chair has approved Issue #479 in combination with Issue #547 to be treated as urgent. A separate Decision Proposal will be drafted for these changes to be staged and made in v1.21.0
- Changes for MI13 will be staged for community review in preparation for Decision Proposal 272: Maintenance Iteration 13 to be drafted for the Chair's approval in v1.22.0.
Taken as read.
This item was not discussed however it can be revisited at the request of participants in MI14. Refer minutes from the meeting on 26/10/2022 for more detail.
The intention here is to move proposals into a separate decision before the end of the week to seek approval then stage changes next week.
-
Issue #479: Clarification on Minimum Algorithm Required for JARM
- Summarised the solution proposal
-
Issue #547: Update SSA and Client Registration standards for JARM and Authorization Code Flow
- Walked through error scenarios and design questions
- Seeking participant feedback on the design questions in relation to default behaviour in some scenarios
- Participants were requested to comment on the issue before the end of the week.
- DSB do develop guidance on how to implement the changes to SSA and Client Registration standards for JARM and Authorization Code Flow (#547)
-
Issue #522: OpenID Provider Configuration End Point parameter requirements
- Option 2 is preferred.
- Next step is that the DSB will stage the changes for review.
-
Issue #535: Standard appears to redefine requirements for private_key_jwt authentication
- There was support for the change.
- Discussion centred on whether the obligation should be bundled with other InfoSec changes or set a standalone obligation date.
- DSB to publish correction to Issue 535 in the Infosec section of the minutes on 9 November.
- Data Holders on the call will follow up with their teams to post their position on the Issue.
-
Issue #475: Representation of Spot price based contracts for C&I customers
- As no specific issues or solution options were identified, this CR will be carried over to Maintenance Iteration 14.
-
Issue #520: Stepped solar feed in tariffs in Energy
- As per participant feedback requesting more time to review the proposed options, this CR will be carried over to Maintenance Iteration 14.
-
Issue #513: Specify if an Account is a joint account in the API response
- Changes to original proposal: (a) Changed field from optional to mandatory (b) Added UNKNOWN and OTHER and added '_PARTY' to existing values (c) Updated descriptions
Property | Value | Description |
---|---|---|
accountOwnership | UNKNOWN | The exact party relationship cannot be determined. |
accountOwnership | ONE_PARTY | One party is the owner of the account. |
accountOwnership | TWO_PARTY | Two parties are the owners of the account. |
accountOwnership | MANY_PARTY | Three or more parties are the owners of the account. |
accountOwnership | OTHER | The account ownership relationship is a complex arrangement that cannot be expressed by the number of owning parties. |
- Participants to consider the updated proposal as discussed and post on the issue.
-
Issue #546: Update Register and DCR Swagger specs to use Common Field Types
- Not discussed, participants requested to review proposal.
-
Issue #544: Update x-v header to be mandatory for Register APIs
- The current proposal was confirmed as the position that will be taken to the Chair for approval.
-
Issue #551: Iteration 13 Holistic Feedback
- Reviewed, no additions or comments on items recorded.
- Maintenance Iteration 14 is scheduled to commence on 8 February 2023.
- DSB to send MI14 invitation to attendees.
InfoSec
- DSB do develop guidance on how to implement the changes to SSA and Client Registration standards for JARM and Authorization Code Flow (#547)
- DSB to publish correction to Issue #535 in the Infosec section of the minutes on 9 November.
- Data Holders on the call will follow up with their teams to post their position on Issue #535
Energy
- None
Banking
- Participants to consider the updated proposal on Issue #513: Specify if an Account is a joint account in the API response as discussed and post on the issue.
Register
- None
MI13 Holistic Issues
- None
Other
- DSB to schedule an adhoc MI Meeting to conduct the MI13 retrospective before the end of the year.
- DSB to send MI14 invitation to attendees.
Community to provide comment on proposals and review staged changes when available. DSB to prepare Decision Proposal 272 for the Chair's approval.