Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Spring25 M3 review comment on telco terminology in API .yaml(s) #414

Open
tanjadegroot opened this issue Feb 7, 2025 · 2 comments · May be fixed by #424
Open

Spring25 M3 review comment on telco terminology in API .yaml(s) #414

tanjadegroot opened this issue Feb 7, 2025 · 2 comments · May be fixed by #424
Labels
documentation Improvements or additions to documentation Spring25 Issue in scope of Spring25 meta-release cycle

Comments

@tanjadegroot
Copy link

Problem description
Rasing an issue as pre recommendation here: #407 (comment)

In the qos-profiles.yaml, in the various description fields, there is a lot of Telco terminology that should be replace by more developer friendly terms (or just dropped).

examples:

  • 3GPP
  • QBR QCI and QCI_1_voice
  • l4s
  • etc.

Expected action
For the M4 milestone, revisit/remove the telco terminology used in the API yaml description fields.
Recheck the other APIs as well for alignment

@tanjadegroot tanjadegroot added the documentation Improvements or additions to documentation label Feb 7, 2025
@hdamker hdamker added the Spring25 Issue in scope of Spring25 meta-release cycle label Feb 19, 2025
@hdamker
Copy link
Collaborator

hdamker commented Feb 19, 2025

@benhepworth @RandyLevensalor can you take the issue as discussed in last call and prepare a PR for the points which easily can be resolved before the public release?

@RandyLevensalor
Copy link
Collaborator

@tanjadegroot thanks for the feedback. L4S is not a telco specific term. We are enabling the application to manage congestion control. The network marks the packet and the application does the heavy lifting with support from the operating system.

I'll address the other issues and look at the L4S description.

@hdamker hdamker linked a pull request Feb 22, 2025 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation Spring25 Issue in scope of Spring25 meta-release cycle
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants