Below is the list of features with high priority 

1. Specification Upgrade (3GPP) upgrade of 5G Core (SD-Core) - details captured below 
   1. SBI interface
   2. PFCP interface (N4) 
   3. NAS interface (N1)
   4. NGAP interface (N2)
   5. GTPu interface (N3, N6, N9)
2. tool: gnbsim gNBSim support
   1. data support
   2. handover support
   3. UI support in gnbsimgNBSim
3. Update Upgrade mongodb and kafka to latest versions
4. TLS support on SBI interface (completed)
5. Dashboard for CI/CD repo health. 
6. Scalable SD-Core Core
7. Performance Results for UPF
8. CD tool (gitops) integration for community members
9. Creation of NFs per Slice 
10. UPF support based on Slice Id & DNN. Same UPF may support multiple DNNs but same slice Id.

Details about Specification Upgrade

1. Specification upgrade: 

                 This has multiple dimensions. I shall list the tasks required to do the specification upgrade

1. 1. Service Based Interface Update
      1. Take new openAPI files from specification
      2. Generating the golang code for openAPI
         1. Created golang code using the openapi imagetheopenAPIimage/container for one yaml file. I need to automate the process for all yaml files
         2. Can do this for release 17 files and for release 18 files. Which release should we target? I think we should target R18. What do you think? Here is are the release timelines: https://www.3gpp.org/specifications-technologies/releases
      3. Use newly generate openapi models generateopenAPImodels in at least 1 or 2 Network Functions
   2.  PFCP Specification update. 
      1. Impacts UPF & SMF 
      2. UPF currently uses go-pfcp project and SMF uses local pfcp code. We should plan to move to go-pfcp as standard way.
   3. NAS specification upgrade 
      1. Impacts SMF, AMF network functions
      2. Impacts simulator like gnbsimgNBSim
      3. Impacts the testing with real gNodeB, mobiles. 
   4. NGAP specification upgrade 
      1. Impacts AMF network function
         1. Created golang code (asn1 → proto → go) but the resulting GO code looks very different to the structure of the current ngap repository. What is the appropriate process to follow?
         2. ngap repository uses/calls aper repository. Does the aper repository also needs to be updated?
      2. Impacts simulator like gnbsimgNBSim
      3. Impacts the testing with real gNodeB
   5. gtpu specification upgrade (low priority)
      1. Impacts UPF network function
      2. Impacts optionally SMF 
      3. Impacts gnbsimgNBSim
      4. impacts the testing with real gNodeB
2. gNodeB Simulator changes. Only critical features listed below
   1. gNodeB handover Xn handover 
   2. gNodeB handover N2 handover
   3. Data support
   Update
   2. Enable all profiles by default?
3. Upgrade mongodb and kafka to latest versions
   1. Latest versions are mongodb 15.6.7 and kafka 29.3.3
   2. mongdb was upgraded updated from 13.6.4 to 13.16.4 and kafka was upgrade upgraded from 20.0.4 to 23.0.7, which are the newest versions that do not require any change in the sd-coreSD-Core
4. Dashboard for CI/CD repo health
   1. Ajay Lotan Thakur please provide specifics of what you have in mind about this ("dashboard")
   2. Aspects to complete for CI/CD (in general) are: 1) Make mandatory (required) to pass all GHAs before a PRs is merged; 2) Publish "latest" image to DockerHub?; 3) Does it make sense to have "three" places/registries where images are published (DockerHub, Opennetworking, Aetherproject)? This needs to be improved
5. Scalable SD-Core
   1. ??
6. Performance Results for UPF