eSIM Management APIs and General Description for the eSIM APIs#23
eSIM Management APIs and General Description for the eSIM APIs#23rkandoi wants to merge 5 commits intocamaraproject:mainfrom
Conversation
maheshc01
left a comment
There was a problem hiding this comment.
considering the this is an initial commit and would be good to have for visibility of the work done as part of the API working group during the MWC Barcelona event, I am good with this pull request.
We can consider addressing the review comments when we plan for a release candidate as par to fall release cycle.
| @@ -0,0 +1,1270 @@ | |||
| openapi: 3.0.3 | |||
| info: | |||
| title: eSIM Management API | |||
There was a problem hiding this comment.
title mismatch with repo might throw exceptions during the automated checks in the release management process. Needs to be confirmed and updated
| $ref: '#/components/responses/Generic422' | ||
|
|
||
| /esim/delete: | ||
| post: |
| '422': | ||
| $ref: '#/components/responses/Generic422' | ||
|
|
||
| /esim/set-fallback: |
There was a problem hiding this comment.
do we need a separate endpoint for setting fall back? Could we not make it part of the earlier POST call to include this information?
|
|
||
| ## Operation-Specific Identification | ||
|
|
||
| - **Download**: Requires both EID (target device) and ICCID (profile to install) |
There was a problem hiding this comment.
Actually download does not require ICCID. Download requires activation code. ICCID is not used during download per se. ICCID could be optional for tracking purposes.
|
|
||
| The target of the eSIM operations is typically the eUICC on the device (as opposed to the cellular network). | ||
|
|
||
| **Terminology Note**: In this API, "eSIM" and "eSIM profile" refer to the same thing - downloadable connectivity configurations installed on eSIM hardware. We use "eSIM" for simplicity. |
There was a problem hiding this comment.
Actually "eSIM" more often means "eUICC", so using "eSIM" like this may confure readers. I would prefer that "eSIM profile" is used consistently, as it has much more clear meaning.
What type of PR is this?
API Specification and General Description for eSIM Management functionality.
Special notes for reviewers:
This PR is created to make some of the work visible before MWC. It would be appreciated if you can perform an expedited review and we can merge this PR.
The version of the API is vwip and all changes needed as we progress the work are okay to make.
Changelog input