DSB Maintenance Iteration 18: Minutes (3 April 2024) - ConsumerDataStandardsAustralia/standards GitHub Wiki

Meeting Minutes

Release Plan

  • Candidates for MI18 are progressively being staged and the Decision Proposal is being drafted for the Chair's approval. The changes will be published in v1.30.0.

Requirements Analysis

Common

Errors

Security

Maintenance Iteration 18 Candidates

MI 18

  • #629 Maintenance Iteration 18 Holistic Feedback
    • With the exception of the item on Register API descriptions, all items have been staged.
    • The Register API Description may be moved into MI19 depending on the outcome of discussions with the ACCC.
    • ACTION: Participants are invited to review the staged changes.

CX

Security

  • #543 refresh_token_expires_at and sharing_expires_at claims listed as MUST be supported
    • Discussed incorrect references to the token in the current proposal, but should only reference the token introspection endpoint.
    • Discussed whether an FDO is required for ADRs calling DHs with the claims listed as essential - if an ADR currently makes an authorisation call with the claims listed as essential, but the DH doesn't support the claims some implementations may return an error.
    • Discussed the OIDF community view is standards are not always clear with regard to what should happen when claims are not authorized, supported or unrecognized. Consensus was, for interoperability sake, these claims should not be rejected, but ignored.
    • Discussed whether a better approach is to require ADRs to check the OpenID Discovery Document hosted by the DH to verify the claims supported before making an authorisation call that includes unsupported claims.
    • ACTION: DSB to correct description to mention the refresh token introspection endpoint only.
    • ACTION: DSB to consider behaviour for ADRs to ensure claims are no longer requested.
    • ACTION: DSB to consider an FDO for ADRs to implement the change to avoid unintended consequences.
    • ACTION: Data Holders are required to ensure their discovery endpoint matches system behaviour.
  • #631 Updates to 'Revoking consent' Standards
    • Staged changes will be published in v1.30.0.
  • #632 Concurrent consent support and cdr_arrangement_id
    • Staged changes will be published in v1.30.0.

Admin

  • #626 AuthorisationMetricsV2 abandonmentsByStage property descriptions and CDS Guide
    • Discussed three broad options to proceed with this change request:
        1. Proceed with aligning to the guidance which will result in a breaking change and an FDO.
        1. Change all abandonment by stage language to remove ambiguity in the description of each stage and consider a broader change.
        1. Accept there will be difference in interpretation and make no change. This would need to be confirmed with the ACCC to ensure they look at relative counts of abandonment metrics within a DH not across DHs.
    • Discussion considered what is an abandonment vs an active action taken by the end user to reject/cancel/deny the authorisation.
    • Also heard from implementers that not all implementations have a Deny button on the final stage and as such, there would never be any rejections at that stage. Also heard that different implementations have interpreted closing of browsers as either a user action or an abandonment.
    • Consideration to proceed without making a change would not impact ANZ because they have implemented against the guidance and remain aligned to the standards.
    • It was also considered that a future version of metrics could incorporate rich authorisation data sharing and authentication uplift, therefore postponing uplift of metrics to a future date with further discussion on these considerations.
    • ACTION: this item will be carried into MI19.

Energy

  • #623 Add new pricing models to EnergyPlanContractV2
    • Summary of the issue, noted in this comment , was provided
    • ACTION: Agreement that no change is required. This issue can be closed.
  • #624 Improved structure for Solar Time Varying Tariffs
    • There was broad agreement to adopt option 1 noted in the original proposal with a displayName field as opposed to new ENUM values. This would align the change with similar structures across the standards.
    • ACTION: DSB to update Proposed Solution with displayName field and removing new ENUM values as per original proposal
    • ACTION: Participants to review updated recommendation and if no objections are raised by next week the change will be recommended for adoption to the Chair.
  • #625 Additional field to support Step Tariff calculations
    • Discussion around potential need for the start and end of a step period to facilitate calculation and if a calculation time/period should be considered or introduced as part of the change.
    • Noted that some retailers (e.g. GloBird) use the billing period to calculate step rates for a consumer. The invoice period, as a result, can help calculate step rates for a given invoice. Therefore, specific start and end time/date for the step period is not required (and may not even be held by the retailers).
    • Noted this CR was raised to address a missing period field in some structures, without which step rates cannot be properly determined.
    • AER noted they currently only rely on the period fields for step rate calculation for plan comparisons from Retailer data.
    • There was broad support for the change.
    • ACTION: DSB will attempt to get further input from participants offline prior to recommending the change.
  • #627 EnergyPlanTariffPeriod - Change to daily supply charge
    • Discussed the approach of separating the original issue of sharing banded daily supply charges and the broader issue of changing the interface between retailers and AER to share banded daily supply charges as noted in this comment.
    • A suggestion was made to align the FDO with when the AER can incorporate such banded charges, however it was noted that introducing the change would address the immediate need for DHs to share the banded supply charges and will enable AER to start sharing them once the collection issue is resolved.
    • There was broad agreement for the above approach, noting that it is important for the Retailer-AER data sharing interface (which is outside CDR scope) to be corrected to cater for banded daily supply charges, and it would have to be managed outside MI/CDR channels.
    • ACTION: Pending further comments from participants, the change will be recommended to the Chair.

Telco

Other business

Maintenance Iteration 19 is scheduled to commence on 17 April 2024. Invites will be issued shortly.

Next Steps

DSB will finalise proposed solutions based on the decisions made in the call, post updates on tickets with outstanding issues and continue to stage the changes for v1.30.0. Community review and contribution on the issues is essential to ensure DSB's proposed solutions align with your understanding of the requirements and discussion outcomes.