Versions Compared

Old Version 53

changes.mady.by.user Herbert Damker

Saved on

compared with

New Version 54

changes.mady.by.user Tanja de Groot

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

General Updates

Table of Contents
maxLevel3
minLevel2
include^(New Participants|Fund Updates|Technical Steering Committee)$

Working Groups

Table of Contents
maxLevel3
minLevel2
include^(Marketing \(Outreach Committee\)|Release Management|Commonalities|APIBacklog|IdentityAndConsentManagement)$

Sub Projects

Table of Contents
maxLevel4
include^(BlockchainPublicAddress|CallForwardingSignal|CarrierBillingCheckOut|ClickToDial|ConnectivityInsights|DeviceIdentifier|DeviceLocation|DeviceStatus|DeviceSwap|EdgeCloud|HomeDevicesQoD|KnowYourCustomer|LocationInsights|NetworkAccessManagement)$

Sub Projects

Table of Contents
maxLevel3
include^(NetworkSliceBooking|NumberVerification|OTPvalidationAPI|PopulationDensityData|QualityOnDemand|RegionDeviceCount|ShortMessageService|SimSwap|SiteToCloudVPN|VerifiedCaller|WebRTC|SimpleEdgeDiscovery|Tenure)$

General Updates

New Participants

  • 1091 people from 386 companies have joined CAMARA
  • 1318 people and 221 companies are in (first) talks
  • Logos see landscape

Updated:  

Markus Kümmerle 

Fund Updates

  • Status of the technical project (same as below)
  • Budget approvals

Updated  

Casey Cain Evan Harrison 

Technical Steering Committee

  • EasyCLA introduction
    • https://github.com/camaraproject/EasyCLA available as neutral repository where you can open a trivial PR and initiate the EasyCLA signing process.
      • Especially all Codeowners should use this opportunity to ensure that they can continue working after the project wide activation of EasyCLA.
    • The check for a signed CLA will be activate on all repositories soon. 
  • New structure of Sub Projects agreed within the TSC (see PR Governance/pull/146)
    • A Sub Project can be now a set of API Repositories (one or multiple)
    • Details are described within ProjectStructureAndRoles.md
    • Opportunity for Sub Projects with multiple APIs to put them into separate repositories
      • Allows independent releases of APIs, simplifies the management of releases
  • API Backlog 
    • RegionUserCount got renamed into RegionDeviceCount
    • ShortMessageService scope extended with "Receive SMS"
    • DeviceStatus has been discussed the adoption of the two new APIs (Device Connection Quality Indicator, Device Data Volume)
  • Commonalities
    • Release candidate of v0.4.0 available
    • Please consider this version for your APIs, especially the ones planned for the Meta-Release Fall24
  • Identity & Consent Management (ICM)
    • Release candidate of v0.2.0
    • Please consider this version for your APIs, especially the ones planned for the Meta-Release Fall24
  • Release Management 
    • See below


Updated

Herbert Damker 

Working Group Updates

Marketing (Outreach Committee)

Updated:  

Markus Kümmerle 

Jill Lovato

Release Management

  • Meta-release schedule 
    • M1 - Declared at TSC of 2024-07-04 for Commonality alpha release available at 2024-06-10. Decision to skip the M1 for ICM and go directly to the first release-candidate for M2. 
    • M2 - Release candidates of Commonalities and ICM are available, see Meta-release Fall24 plan.
    • M3 - First release-candidates of API Sub Projects to be provided by 07-21. 
    • M4 - Final release candidates of API Sub Projects: target 08-30.
  • Supporting documentation:
  • Next steps
    • All Sub Projects are asked to prepare for the meta-release, including creating API release trackers for their APIs under their wiki pages, preparing their release-candidate API version and their API readiness checklist items.
      • Reminder: the API version number within this first pre-release shall have the format x.y.z-rc.1 for the targeted release of API version x.y.z in the meta-release 
      • Before M3 you may release 1 or more x.y.z-alpha.n versions as needed for the API development, but you can also go from the current release directly to the first release-candidate by M3. (Pre-)release numbering starts at r1.1. Please reflect this in the CHANGELOG.md.
    • Milestone timeline is here: Meta-release Fall24.
    • The Release Management team will start checking APIs and highlighting any points related to the release process where needed using the API Sub Project's issues list to help in the meta-release progress.

Updated:  

Tanja de Groot 

Commonalities

  • Release 0.4.0-rc.1 of Commonalities was published on 11th of July
    • Please provide feedback on needed corrections for final release.
  • New issues:

    • Request body is required but all properties are optional #247

    • Add rules in design guideline about multi-endpoint API design & implementation requirement #246

    • How to inform API consumer about unprocessable subscription request in Async mode #243

    • Add an “Area” data-type into CAMARA_common.yaml #242

  • Announcements

    • See the Release 0.4.0-rc.1 Changelog

    • M0 for Spring25 meta-release is on 30-09-2024 

      • Please indicate the topics to be included in Commonalities v.0.5.0 

Updated:  

Rafal Artych 

APIBacklog

  • Documents

    • Live table for API backlog availablehere. Stable version.

    • Accepted API proposals stored here. 

  • New Issues

    • OGW Drop

      #3

      #4 APIs: 

      #19 (Device Quality Indicator)OGW Drop #4 APIs:

       #35 (5G New Calling), #34 (Shutdown Service Status), #41 (Telco Scoring), #50 (Device Management), #54 (Number Recycling), #63 (IMEI Fraud)

    • Other APIs:  #17 (Consent and Measurement), #18 (Receive SMS),  #23 (Carrier Wholesale Pricing),  #24 (Steering of Roaming Information),

      #29 (Call Status

       #60 (Dedicated Networks),

      #28 (Device Data Volume

       61 (network Info)

    • Scope Enhancement: #45 (KYC-Match API - Scoring Logic), #48 (RegionUserCount)
    • Governance: #4 (Structures and roles,

      Governance: #4 (Structures and roles, RACI, Maintainers initiative), #53 (Scope Enhancement API Template)

  • PRs
    • Application templates for those API proposals which have not been discussed yet in TSC.
  • Announcements

    • API Backlog will be held from then to now in a separate GitHub Repo and migration of issues have been completed. Active PRs will be moved to the new repo

    • Changes in the way of approving new API proposals are under review

    • Closing issues being treated in the TSC:

    • #20 (Best Interconnection), #22 (Capability and Runtime Restrictions)

    • Created new subproject/repos:

      • Verified Caller → #27 (China Telecom, ZTE, China Unicom, Huawei, China Mobile)

      • Tenure → #2 (Vodafone, Telefonica, Orange, DT)

Updated:  

Ricardo Serrano Gutierrez 

IdentityAndConsentManagement

Deliverable

R/O

Current status / Achievements

API Definition

R

N/A yet. 

If identified, a proposal will be made once core issues are clarified and closed.

API doc/user stories/testcases

R

New CAMARA "Security and Interoperablitity" profile created

Existing CAMARA "API access and user consent management document" updated according to the new profile.

New CAMARA ICM examples file created.

OpenAPI securitySchemes ICM guidelines relevant information included in Commonalities API Design Guidelines documentation.

Implementation

R

N/A yet

API Reviews and extensions

O

Release 0.2.0 scope definition for Fall 24 CAMARA meta-release is defined and available in IdentityAndConsentManagement/issues/146. Only one issue still under discussion to close all items under the scope of the meta-release.

Updated:  

Axel Nennker 

Sub Project Updates

BlockchainPublicAddress

Expand

Deliverable

R/O

Current status / Achievements

API Definition

R

Working in next release: v0.2.0-wip

  • No additional Business Requirements so far.
  • ON-HOLD: Working in technical enhancements in the meantime (see latest section)

API doc/user stories/testcases

R

API Doc

Full API documentation pending to be consolidated under API Spec

Use Cases - First version available

Implementation

R

Not yet

API Reviews and extensions

O

Some typos fixed in PR#55

Pending Points:

- Issue #16 - Discussion about consent management considerations in retrieval of blockchain public addresses ON-HOLD

- Issue #51 - Avoiding the use of "plain" phoneNumber as filter criteria of blockchain retrieval

- Issue #52 - Enhancement of blockchainPublicAddress belongs to the user whose phoneNumber is indicated to set-tp the binding relationship

Updated:  

Pedro Diez Garcia 

CallForwardingSignal

Expand

Deliverable

R/O

Current status / Achievements

API Definition

R

Released and approved v0.1.9-wip

PR on 0.2.0-wip with further alignment with CAMARA guidelines (error codes). Conditional Call FWD endpoint as optional (error code 501)

API doc/user stories/testcases

R

User Story and Documentation released. PR for the full Test Cases for the two endpoints

Implementation

O

NA (Optional according to CAMARA Readiness Checklist)

API Reviews and extensions

O

NA

Updated:  

Fabrizio Moggio 

CarrierBillingCheckOut

Expand

Deliverable

R/O

Current status / Achievements



API Definition

R

API spec:

  • Current API Spec Release is v0.2.1.

Next outputs for MetaRelease Fall24:

  • Payment Evolution v0.3.0 align with NEW Refund functionality v0.1.0.


API doc/user stories/testcases

R

Use Cases - First version available



Implementation

R

Not yet



API Reviews and extensions

O

Deliverable

R/O

Current status / Achievements



API Definition

R

API spec:

  • Current API Spec Release is v0.2.1.

Next outputs for MetaRelease Fall24:

  • Payment Evolution v0.3.0 align with NEW Refund functionality v0.1.0.


API doc/user stories/testcases

R

Use Cases - First version available



Implementation

R

Not yet



API Reviews and extensions

O

Several Open Issues, listed here. Current status:

  • Merged PR#152, covering several issues and defining initial refund functionality
  • Next steps are going into the generation of the next -rc spec versions

Updated:  

Pedro Diez Garcia 

ClickToDial

Expand

Deliverable

R/O

Current status / Achievements

API Definition

R

Repository, Mailing list have been set up. 

API Definition - Draft version available

Subsequent modifications and improvements will be made.

API doc/user stories/testcases

R

API doc - First version contributed

TBD part will be added in next version.

Use Cases - First version available

TBD part will be added in next version, format needs to be adjusted.

          

Test Cases - Work in progress

Implementation

R

No implementation available yet

API Reviews and extensions

O

N/A

Updated:  

@Hanbai


ConnectivityInsights

Expand

Deliverable

R/O

Current status / Achievements

API Definition

R

Working in release: 0.4.0 which is targeted to be  a tagged release.

Most issues have been resolved and release mgmt being planned.

API doc/user stories/testcases

R

Documentation is now available as part of the yaml

user stories available.

test cases, not yet

Implementation

R

Not Yet

API Reviews and extensions

O

  • updated yaml as per latest linting rules.
  • Incorporated latest commonalities guidelines for subscriptions and notifications.
    • separated out application-profiles into a different yaml to promote using it in other APIs.

    Open Issues:

    #44 

    Network Info - Scope change and overlap with DeviceStatus API?

    Updated:  

    Mahesh Chapalamadugu 

    DeviceIdentifier

    Expand

    Deliverable

    R/O

    Current status / Achievements

    API Definition

    R

    Device Identifier API: Initial public release 0.1.0 now available

    API doc/user stories/testcases

    R

    Device Identifier API:

    • Documentation embedded within OAS definition
    • User Stories now added
    • Test cases under development

    Implementation

    R

    China Unicom

    API Reviews and extensions

    O

    IMEI Fraud API:

    • API removed from scope of Sub-Project for now, but has been resubmitted to API Backlog WG by Chenosis (see Issue #63)

    Updated:  

    Eric Murray 

    DeviceLocation

    Expand

    Deliverable

    R/O

    Current status / Achievements

    API Definition

    R

    		Last API family release: 0.2.0,  including 3 APIs: 
      • location-verification v0.2.0
      • location-retrieval v0.1.0
      • geofencing v0.1.0​ (to be renamed as geofencing-subscriptions)

    (next release of the 3 APIs expected for meta-release Fall24. TBD if some of them will be major) 

    API doc/user stories/testcases

    R

    • All API documentation consolidated within spec.
    • Working on test plans for the 3 APIs 

    Implementation

    R

    No contribution  yet

    API Reviews and extensions

    O

    • Alignments with Commonalities and transversal issues:
      • Simplification of device object
      • Alignment of error scenarios
    • PRs with proposals for test definitions
    • Clarifications for implementation guidelines. enhancement of documentations and implementation guidelines, new error scenarios
    • Support of polygon as input for geofencing-subcriptions, under discussion

    Updated:  

    Jose Luis Urien 

    DeviceStatus

    Expand

    Deliverable

    R/O

    Current status / Achievements

    API Definition

    R

    Target for version 0.6.0  - separated endpoints

    • device-roaming-status v0.6.0
    • device-reachability-status v0.6.0
    • device-roaming-status-subscriptions v0.6.0
    • device-reachability-status-subscriptions v0.6.0

    API doc/user stories/testcases

    R

    Drafts prepared according to API Testing Guidelines

    Implementation

    R

    No implementation available yet

    API Reviews and extensions

    O

    Alignment to Commonalities 0.4.0

    Updated:  

    Rafal Artych 


    DeviceSwap

    Expand

    Deliverable

    R/O

    Current status / Achievements

    API Definition

    R

    Work to be started

    API doc/user stories/testcases

    R


    Implementation

    R


    API Reviews and extensions

    O

    Please add to https://github.com/camaraproject/DeviceSwap/issues/1 and on the mailing list if interested to support

    Updated:  

    @Wassam


    EdgeCloud

    Expand


    Deliverable

    R/O

    Current status / Achievements

    API Definition

    R

     •Traffic Influence – 0.9.5-wip :PR for v0.9.6-wip: addition of the "sourceTrafficFilters" object to help identify the traffic flow to influence. Minor updates following commonalities.

    •Edge Application Management – 0.9.3-wip:A couple of PRs have been created to improve the onboarding of an Application using K8s.

    •Application Endpoint Discovery: Update the device object according to the commonalities v0.4.0 definition and improve the API documentation to clarify its scope.

    API doc/user stories/testcases

    R

    •The documentation was provided according to Commonalities v0.3.0 but will be updated according to the new requirements of Commonalities v.0.4.0.

    •Edge Cloud User Story now available to understand the relationship of the 4 current APIs

    Implementation

    R

    No provider implementation (PI) available yet.However:

    •Traffic Influence: Implementation under validation by Telecom Italia (TIM):

    •Simple Edge Discovery: Partly validated (Vodafone and Telstra).

    API Reviews and extensions

    O

    Exposure and Experience Management API:This API has recently received a contribution and has been renamed the Edge Service Discovery API. As the name suggests, the API has discovery functionalities but does not overlap with the current APIs but has advanced functionalities that can enhance Simple Edge and App Endpoint Discovery. We are discussing next steps.

    Updated:  

    Cristina Santana 

    HomeDevicesQoD

    Expand


    Deliverable

    R/O

    Current status / Achievements

    API Definition

    R

    Current API Spec release is v0.3.0

    API doc/user stories/testcases

    R

    Existing test definitions are available in the repository.

    Implementation

    R

    N/A

    API Reviews and extensions

    O

    • The next expected activity is to make the necessary adjustments for the Fall24 meta-release to align with CAMARA Commonalities and IdentityAndConsentManagement.

    Updated:  

    Jesús Peña 

    KnowYourCustomer

    Expand

    Deliverable

    R/O

    Current status / Achievements

    API Definition

    R

    Work in progress on KYC Match API, KYC Fill-in API, Age Verification API

    KYC Match and KYC Fill-in: release v0.1.0 is available here

    - KYC Match: provides the customer with the ability to compare information it has for a particular user with that owned by MNO

    - KYC Fill-in: provides the customer with the ability to request to MNO and receive KYC information for a particular user

    - KYC Match and Fill-in: upgrade to v0.1.1 with some corrections → Approved PR #100 (June 18, 2024)

    Age Verification: release v0.1.0 discussion ongoing

    - provides the customer with the ability to check age information for a particular user with MNO data

    - discussion on going, Issue #46, PR #50(initial API definition proposal) 

    API doc/user stories/testcases

    R

    - KYC Match / Fill-in v0.1.1: API doc embedded in YAML, user stories available, testcases not yet available.

    - Age Verification v0.1.0: User story is being discussed, in alignment with API definition discussion; Issue#81.

    Implementation

    R

    - Not yet

    API Reviews and extensions

    O

    - KYC Match and KYC Fill-in v0.2.0: work in progress for enhancements; Issues #38 #39, #47, #65, #66, #71, #77, #85, #86, #87, #88, #89, #90, #91, #95, #96, and PRs #43, and some others. 

    - KYC Match Scoring function has been discussed on #85 since June 2024, which is in line with KYC Match enhancement proposal approved in API Backlog WG.  → KYC Match Scoring function was agreed as optional function, and to create KYC Match v0.2.0 including Match Scoring function, PR #104 has been approved and merged. 

    - KYC Match Scoring: if Match result for a string-type attribute is 'false', a score on how close the string sent by the API request and the data stored in the MNO/CSP database are will be calculated and returned.   

    - Meta Release Fall-24 candidate is being discussed; Plans to include KYC Match v0.2 (basic Match + Match Scoring) and KYC Fill-in v0.1 (basic Fill-in). Issue#75



    - Note: Tenure API is in KnowYourCustomer Family. Tenure API will share some resources, e.g. meeting slots, with other KYC-SP APIs.  In addition, API Backlog WG is discussing on whether two new APIs, NumberRecycling API and ShtudownServiceStatus API, can fit in KnowYourCustomer Family.

    Updated:  

     Toshiyasu Wakayama 

    LocationInsights

    Expand

    Deliverable

    R/O

    Current status / Achievements

    API Definition


    Most Frequent Location (MFL): 

    • KO celebrated, including discussion of use cases and area type details
    • First code proposal shared (PR#6)

    API doc/user stories/testcases


    		MFL: Included as part of first code proposal

    Implementation


    		N/A

    API Reviews and extensions


    		N/A

    Updated:  

    Fan Yang Fernando Prado Cabrillo 

    NetworkAccessManagement

    Expand

    Deliverable

    R/O

    Current status / Achievements

    API Definition

    O

    Merged reworked initial proposal with updates to align with commonalities:
    https://github.com/camaraproject/NetworkAccessManagement/pull/7

    Created follow up issues for additional alignment:

    API doc/user stories/testcases

    O

    Documentation integrated into yaml file

    Implementation

    O

    N/A

    API Reviews and extensions

    O

    N/A

    Updated:  

    Christopher Aubut @Justin Pace

    NetworkSliceBooking

    Expand


    Deliverable

    R/O

    Current Status / Achievements

    API Definition

    O

    Work in progress in API Yaml and User Stories. Specs:

    Initial API definition of create, query, and deletion session: 

    https://github.com/camaraproject/NetworkSliceBooking/pull/11

    API doc/user stories/testcases

    O

    API Doc and User Stories:

    ppt can be found in https://github.com/camaraproject/NetworkSliceBooking/pull/4, while md with reference scenario can be found in https://github.com/camaraproject/NetworkSliceBooking/pull/13

    Implementation

    O

    Not yet

    API Reviews and extensions

    O

    Not yet

    Updated:  

    Shuting Qing 

    NumberVerification

    Expand

    Deliverable

    R/O

    Current status / Achievements

    • Preparing all asset for Meta Release (issue107)
      • Target to have a stable maturity-level version (need to go thru CAMARA TSC)
      • Candidate version is v0.4

    API Definition

    R

    Current release is v0.3.1: https://github.com/camaraproject/NumberVerification/releases/tag/v0.3.1

    API doc/user stories/testcases

    R

    Documentation integrated into YAML file

    • Additional documentation (Sequence diagram) in progress (PR94)

    In order to align with Release Management check list, work in progress:

    Implementation

    R

    Live implementation could be fine here in:

    • Brazil
    • China
    • Finland
    • France
    • Germany
    • Indonesia (Certified)
    • Italy
    • Netherlands
    • Singapour
    • South Africa (Certified)
    • Spain (Certified)
    • Thailand (Certified)

    API Reviews and extensions


    Updated:  

    Ludovic Robert 

    OTPvalidationAPI

    Expand

    Deliverable

    R/O

    Current status / Achievements

    • Preparing all asset for Meta Release (issue62)
      • Target to have a stable maturity-level version (need to go thru CAMARA TSC)
      • Candidate version is v0.6

    API Definition

    R

    Current release v0.5.0
    https://github.com/camaraproject/OTPvalidationAPI/releases/tag/v0.5.0

    API doc/user stories/testcases

    R

    Documentation integrated into YAML file

    In order to align with Release Management check list, work in progress:

    • Test Definition (PR61)
    • User story (TBD)

    Implementation

    R

    Live implementation could be fine here in:

    • China (Certified)
    • Brazil
    • Italy
    • Saudi Arabia (Certified)
    • Sri Lanka

    API Reviews and extensions

    O

    Change for meta-realse:

    • Alignement with commonalities & icm
      #56 Align securitySchemes and Auth description with commonalities and ICM
      #50 Make '+' mandatory

    Updated:  

    Ludovic Robert 

    PopulationDensityData

    Expand

    Deliverable

    R/O

    Current status / Achievements

    API Definition

    R

    Version 0.1 released: https://github.com/camaraproject/PopulationDensityData/releases/tag/v0.1.0

    Working on ensuring that the API is ready for meta-release :

    • Prediction/Extrapolation algorithm draft proposal under review → Algorithm
    • ATP
    • User stories

    API doc/user stories/testcases

    R

    Reference Use case closed in API documentation. 

    Test cases pending.

    Implementation

    R

    N/A

    API Reviews and extensions

    O

    1. First release ready
    2. Start creating scope for v2

    Updated:  

    Jorge Garcia Hospital 

    QualityOnDemand

    Expand

    Deliverable

    R/O

    Current status / Achievements

    API Definition

    R

    Current release: v0.10.1
    https://github.com/camaraproject/QualityOnDemand/releases/tag/v0.10.1

    API doc/user stories/testcases

    R

    Documentation inline within API OAS

    Implementation(s)

    R

    Three repositories for Provider Implementations (PI):

    API Reviews and extensions

    O

    • v0.11.0 - Scope definition within QualityOnDemand/issues/292
      • Several issue and PRs for v0.11.0 still in work or review
    • Done:
      • Duration, extentDuration, and time formats consolidated
      • Security schemes and scopes according to Commonalities & ICM updated
    • PR for new API “QoD provision mode” still in review

    Updated:  

    Herbert Damker 

    RegionDeviceCount

    Expand

    Deliverable

    R/O

    Current status / Achievements

    API Definition

    R

    API Specs will be discussed in first meeting:

    https://github.com/camaraproject/RegionUserCount/pull/2

    https://github.com/camaraproject/RegionUserCount/pull/5

    API doc/user stories/testcases

    R

    API Doc and User Stories:

    https://github.com/camaraproject/RegionUserCount/pull/3

    Implementation

    R

    Not Yet

    API Reviews and extensions


    Not Yet

    Updated:  

    Fan Yang 

    ShortMessageService

    Expand

    Deliverable

    R/O

    Current status / Achievements

    API Definition

    R

    Send SMS API Spec is defined. 

    https://github.com/camaraproject/ShortMessageService/commits/main/code/API_definitions/SMS.yaml

    SMS Delivery Notification Subscription API is defined.

    https://github.com/camaraproject/ShortMessageService/blob/release-v0.1.0/code/API_definitions/sms-delivery-notification-subscription.yaml

    Alpha release-v0.1.0 - camaraproject/ShortMessageService at release-v0.1.0 (github.com)

    API doc/user stories/testcases

    R

    API doc/user stories;

    https://github.com/camaraproject/ShortMessageService/tree/main/documentation/API_documentation

    Implementation

    R

    Not yet

    API Reviews and extensions


    PRs closed - 8

    PR Open - 1

    Updated:  

    Ramit Chawla Tet (Tetsuya) CHIBA 

    SimpleEdgeDiscovery

    Expand

    Deliverable

    R/O

    Current status / Achievements

    API Definition


    		0.11.0-alpha.1 near completion, wip  available  

    API doc/user stories/testcases


    		Gherkin .feature available, user story to be ported from EdgeCloud

    Implementation


    		two operators: R0.93 (done) and v0.9.2 (underway) 

    API Reviews and extensions


    		0.11.0-alpha.1 is mostly alignment with Commonalities 0.4-rc.1

    Updated:  

    Kevin Smith 

    SimSwap

    Expand

    Deliverable

    R/O

    Current status / Achievements

    • Preparing all asset for Meta Release (issue62)
      • Target to have a stable maturity-level version for the sims swap api (need to go thru CAMARA TSC) (not for sim swap subscription API)
      • Candidate version is v0.5
    • For the simswap-notification-subscription we are aligning the API model with cloud events structure (PR111)

    API Definition

    R

    Current release v0.4.0

    https://github.com/camaraproject/SimSwap/releases/tag/v0.4.0

    API doc/user stories/testcases

    R

    Documentation integrated into YAML file

    In order to align with Release Management check list, work in progress for SIM swap

    • Test Definition (PR70)
    • User story (TBD)

    Implementation

    R

    Live implementation could be fine here in:

    • Argentina (Certified)
    • Brazil (Certified)
    • China (Certified)
    • Ethiopia
    • France
    • Germany (Certified)
    • Indonesia (Certified)
    • Italy
    • Netherlands
    • South Africa (Certified)
    • Spain (Certified)
    • Thailand (Certified)
    • UAE (Certified)
    • UK (Certified)
    • USA

    API Reviews and extensions

    O

    Change for meta-release for SIM swap:

    • Alignement with commonalities & icm
      • Align securitySchemes and Auth description with commonalities and ICM
      • Make '+' mandatory (PR100)
      • Add API wildcard scope in the yam (PR103)

    Updated:  

    Ludovic Robert 

    SiteToCloudVPN

    Expand

    Deliverable

    R/O

    Current Status / Achievements

    API Definition

    O

    API definition in progress:

    https://github.com/camaraproject/SiteToCloudVPN/issues/9

    API doc/user stories/testcases

    O

    API Doc and User Stories:      

    https://github.com/camaraproject/SiteToCloudVPN/pull/1

    https://github.com/camaraproject/SiteToCloudVPN/pull/2

    https://github.com/camaraproject/SiteToCloudVPN/pull/3

    Implementation

    O

    Not yet

    API Reviews and extensions

    O

    Not yet

    Updated:  

    @Dan Xu

    Tenure

    Expand

    Deliverable

    R/O

    Current status / Achievements

    API Definition



    API doc/user stories/testcases



    Implementation



    API Reviews and extensions



    Updated:  

    VerifiedCaller

    Expand

    Deliverable

    R/O

    Current Status / Achievements

    API Definition



    API doc/user stories/testcases



    Implementation



    API Reviews and extensions



    Updated:  

    @Dan Xu

    WebRTC

    Expand

    Deliverable

    R/O

    Current status / Achievements

    API Definition

    R

    First and current release is ready v0.1.0.

    camaraproject/WebRTC at v0.1.0 (github.com)

    API Definition:

    WebRTC /code/API_definitions at v0v0.1.0 · camaraproject/WebRTC (github.com)2

    API doc/user stories/testcases

    R

    Documentation is ready:

    WebRTC/documentation/API_documentation /webrtc voice api.md at v0.1.0 at main · camaraproject/WebRTC (github.com)

    New API flow for user story is under reviewFlow review - BYON by stroncoso-quobis · Pull Request #27 · camaraproject/WebRTC · GitHubready

    Implementation

    R

    • T-Mobile US is currently working in the implementation 
    • One more operator is needed to validate new versions of the API

    API Reviews and extensions

    O

    Under discussion for next releases:

    • Emergency calls to be supported is under proposaldiscussion: Emergency Calling in WebRTC - CAMARA Project - Confluence
    • Propper error codes have been included
    • Linting Rules script have been performed and is under review
    • New version of the API have been merged recently. Preparing for META release

    Updated: 13 Jun  

    Ricardo Serrano Gutierrez