magma icon indicating copy to clipboard operation
magma copied to clipboard

Published 20 hours ago • verified publisher icon magma

Create roadmap for 1.9.2

Open lucasgonze opened this issue 1 year ago • 7 comments

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.

lucasgonze avatar Feb 05 '24 16:02 lucasgonze

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 avatar Feb 19 '24 15:02 lucasgonze

Invert PLMN restriction logic from block list to allowed list: https://github.com/magma/magma/issues/15368 https://github.com/magma/magma/discussions/13801

lucasgonze avatar Feb 19 '24 16:02 lucasgonze

Possible: 5G SA UEs

lucasgonze avatar Feb 19 '24 16:02 lucasgonze

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

  1. https://github.com/magma/magma/issues/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. https://github.com/magma/magma/issues/14539 Very critical bug. One of the few that make Magma still not carrier grade solution (IMO again)
  3. https://github.com/magma/magma/issues/14940 The second one.
  4. https://github.com/magma/magma/issues/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). https://github.com/magma/magma/issues/14467

edaspb avatar Feb 20 '24 20:02 edaspb

In terms of my own priorities:

  1. https://github.com/magma/security/issues/181
  2. https://github.com/magma/security/issues/180

lucasgonze avatar Feb 26 '24 16:02 lucasgonze

The label for the release is still open.

The meaning of the label should be documented.

lucasgonze avatar Mar 11 '24 15:03 lucasgonze

Another candidate for 1.9.2: https://github.com/magma/magma/issues/11160

lucasgonze avatar Jun 07 '24 15:06 lucasgonze