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

Create roadmap for 1.9.2 #15377

Open
lucasgonze opened this issue Feb 5, 2024 · 6 comments
Open

Create roadmap for 1.9.2 #15377

lucasgonze opened this issue Feb 5, 2024 · 6 comments
Labels
tsc-discussion TSC discussions about process, proposal, amendments,

Comments

@lucasgonze
Copy link
Contributor

lucasgonze commented Feb 5, 2024

Set a target closing date

Define scope:

  1. Add "Post 1.9" items from Yogesh' issue list
  2. Add fixes for recent disclosures from Nathaniel Bennett and Jorge Vargas
  3. Move all new PRs to 1.9.2

Actual version identifier is TBD.

Community members should use comments here to add or remove items.

@jordanvrtanoski jordanvrtanoski added the tsc-discussion TSC discussions about process, proposal, amendments, label Feb 5, 2024
@lucasgonze
Copy link
Contributor Author

lucasgonze commented Feb 19, 2024

Proposed component: C++ rewrite of message parser

Need fuzz data for testing

Scope 2 months.

Yogesh to write a proposal to patch in C or rewrite in C++.

@lucasgonze
Copy link
Contributor Author

Invert PLMN restriction logic from block list to allowed list:
#15368
#13801

@lucasgonze
Copy link
Contributor Author

Possible: 5G SA UEs

@edaspb
Copy link
Contributor

edaspb commented Feb 20, 2024

From the WISP perspective of view (We use 4g part only)

  1. Datapath issue #15303 Hope it would be solved in 1.9 release, in my opinion multi APN non-NAT config is an AGW's killer feature.
  2. Magma SCTP and MME crash v1.8 #14539 Very critical bug. One of the few that make Magma still not carrier grade solution (IMO again)
  3. MME High Memory usage #14940 The second one.
  4. MME crash #15046 I'm not sure if it is related to number 1 or separate issue.

As a conclusion, I would like to ask community to shift a focus to AGW stability. The datapath is excellent but MME and sctpd stability is a weakest part of the project.

New features from my part:

  1. Make logs less noisy. Even with INFO level MME generates a lot of messages, especially when mobile UE are used. I believe many of those messages could be hidden. Less stress to disk subsystem.
  2. Increase amount of supported subscribers per network. For the version 1.8 this number is about 16.000 if I'm not wrong. This number doesn't look too small but in real deployments many times it is very far from enough. Here is technical reference.
  3. Implement QoS per ToS. Now policy matching is limited by IP and protocols. It would be more operator friendly to have policy matching packets by DSCP or ToS. It would help to integrate AGW to the operators networks with existed QoS profiles (For example, with external DPI platforms).
    Use of DSCP for polices #14467

@lucasgonze
Copy link
Contributor Author

lucasgonze commented Feb 26, 2024

@lucasgonze
Copy link
Contributor Author

The label for the release is still open.

The meaning of the label should be documented.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
tsc-discussion TSC discussions about process, proposal, amendments,
Projects
None yet
Development

No branches or pull requests

3 participants