Agenda

The project's Antitrust Policy is linked from the LF and project websites. The policy is important when multiple companies, including potential industry competitors, are participating in meetings. Please review it, and if you have any questions, please contact your company’s legal counsel. Members of the LF may contact Andrew Updegrove at the firm Gesmer Updegrove LLP, which provides legal counsel to the LF.

• Agreement of last minutes (link)

• Action Items Review

• General Aspects

  • Comparison with QOS Booking API (see QOS Booking issue (link) and Table (link))

• Closed Pull Request:

  • Pull Request #23: Enhancing security features

    • Merged with Main

  • Pull Request #29: General Dedicated Network description outside yaml

    • Merged with PR #27

• Issues and Pull Requests:

  • Issue #8: Scope of Dedicated Networks API version 0.1.0

    • Issue #28: API Description / API Documentation

      • Pull Request #27: Proposals for info.description section

        • Updated to integrate merged PR #23 changes

        • No technical changes since more than two weeks

    • New Pull Request #31: Test definition

      • Needed for the CAMARA release procedure

    • New Pull Request #33: API Readiness Checklist

      • Needed for the CAMARA release procedure

    • New Pulld Request #34: Release R1.1 with API version v0.1.0-rc.1

      • Needed for the CAMARA release procedure

  • Issue #17: Correlating a Dedicated Network resource within a subsequent IoT Data Transfer Activation API call

  • Issue #21: dedicated-network-accesses.yaml missing device lifecycle

    •  

Minutes

Agenda is approved.

Minutes from previous meeting are approved without comments.

Action Items from previous meeting are completed.

Pull Request #23 and Pull Request #29 are merged as described in the agenda.

Agreement to merge Pull Request #27 after the meeting.

Comparison table between QoS Booking and Dedicated Network - presentation, discussion, and online updates of the table:

• Hubert comments on device access QoS profile which must be part of Network Profile - updated in the table

• Hubert comments on potential future extension of service area to support flexible service area as discussed earlier - updated in the table

• Hubert comments that device access can also be done while the reservation is already active - updated in the table

• Masaharu asks about provisioning of devices and Thorsten clarifies how device gains access to dedicated network via the API - updated in the table that “provisioning of devices” is a CSP realisation option how to give device access to dedicated network

• Thorsten clarifies that multiple device accesses can be provided by a dedicated network, therefore there is support for multiple devices - updated in the table

• Thorsten clarifies that B2B2C can also be supported as a future extension as discussed earlier- updated in the table

New PRs: #31, #33 and #34 are related to the release candidates for the 3 APIs:

• these PRs need to be merged by mid June to comply with the release candidate process

• all members are encouraged to review to ensure timely merge!

• Steve is added as a reviewer of these PRs

Issue #17 - iI it obsolete? Is it covered by the IoT Optimisation WG?

Issue #21 - Steve comments that it is an ongoing discussion for the next release

Action items