DRAFT AGENDA
...
- PR #295 Add required security scheme and scopes by Eric Murray
- Herbert Damker Should we add an explicit "manage" scope which includes all session operations? (can be done also in separate PR)
- Points to document:
- Device object depending on used authentication => separate PR (after decision in Commonalities #171)
- Endpoints which have different behaviour with 2-legged vs 3-legged
- Endpoints which don't require 3-legged token (no user resource involved)
- Eric will update the PR
- PR #296 Consolidation of changes related to session duration by Jose Luis Urien Pinedo
- Ready to be merged
- New issue to discuss format alignment between session and profiles
- PR #299 New API QOD Provision
- ...
- Jose introduced the proposed API
- Eric: the API still allows to have multiple provisions? Or should it be restricted to one, and enhance the complete traffic of the device (would simplify the API a lot)
- Jose: all traffic is one use case (hence applicationServer as optional proposal)
- Are there use cases to provision QoD for specific flows (defined by applicationServer)? - Jose will ask on product side
- PR #301 Make + prefix mandatory for phoneNumber
- Ready to be merged
- ...
- Merged
- PR #302 fix for enhancement proposal #302
- Background material for issue #302, see below
- Herbert Damker proposal to change to draft until the issue is discussed
...
- #291 Consolidated issue for duration, extentDuration, startedAt, expiredAt, maxDuration and their formats (to be updated)
- Closing also: #288, #281, #280, #266, #249
- Should we create a new issue to the format alignment with Commonalities? Yes → Herbert Damker
- #298 Align phoneNumber with guidelines, with prefix + mandatory
- see PR #301 above
New Issues
- #300 Simplification of Device object - short term solution
- see discussion above
- #302 Providing developers with alternate to QoS profile
- new enhancement proposal by Mahesh Chapalamadugu
- ...
Issues relevant for v0.11.0
...