CII status: NONRTRIC
Last Update: January 2021
Basics (12 Points)
(Result/Proof point (column A: enter Met/Unmet; Column B: enter relevant URLs/comments)
| NONRTRIC - Q1 2021 | |
Criteria | Result / Proof point | |
|---|---|---|
Identification | ||
What is the human-readable name of the project? | Met | OSC Non-RealTime RIC (NONRTRIC) |
What is a brief description of the project? | Met | The Non-RealTime RIC (RAN Intelligent Controller) is an Orchestration and Automation function described by the O-RAN Alliance for non-real-time intelligent management of RAN (Radio Access Network) functions. The primary goal of the NONRTRIC is to support non-real-time radio resource management, higher layer procedure optimization, policy optimization in RAN, and providing guidance, parameters, policies and AI/ML models to support the operation of near-RealTime RIC functions in the RAN to achieve higher-level non-real-time objectives. NONRTRIC functions include service and policy management, RAN analytics and model-training for the near-RealTime RICs. The non-RealTime RIC project provides concepts, architecture and reference implementations as defined and described by the O-RAN Alliance architecture. |
What is the URL for the project (as a whole)? | Met | |
What is the URL for the version control repository (it may be the same as the project URL)? | Met | Gerrit (Multiple):
|
What programming language(s) are used to implement the project? | Met | Mostly Java |
What is the Common Platform Enumeration (CPE) name for the project (if it has one)? |
| No ID |
Basic project website content | ||
The project website MUST succinctly describe what the software does (what problem does it solve? | Met | See: |
The project website MUST provide information on how to: obtain, provide feedback (as bug reports or enhancements), and contribute to the software. | Met | |
The information on how to contribute MUST explain the contribution process (e.g., are pull requests used?) (URL required) | Met | Gerrit (Multiple):
|
The information on how to contribute SHOULD include the requirements for acceptable contributions (e.g., a reference to any required coding standard). (URL required) | Partly Met | |
FLOSS license | ||
What license(s) is the project released under? | Met | Apache 2 |
The software produced by the project MUST be released as FLOSS. | Met | Apache 2 |
It is SUGGESTED that any required license(s) for the software produced by the project be approved by the Open Source Initiative (OSI). | Met | Apache 2 |
The project MUST post the license(s) of its results in a standard location in their source repository. | Met | Apache 2 - referenced in all code & repos |
Documentation | ||
The project MUST provide basic documentation for the software produced by the project. | Met | |
The project MUST provide reference documentation that describes the external interface (both input and output) of the software produced by the project. | Met | |
Other | ||
The project sites (website, repository, and download URLs) MUST support HTTPS using TLS. | Met |
|
The project MUST have one or more mechanisms for discussion (including proposed changes and issues) that are searchable, allow messages and topics to be addressed by URL, enable new people to participate in some of the discussions, and do not require client-side installation of proprietary software. | Met |
|
The project SHOULD provide documentation in English and be able to accept bug reports and comments about code in English. | Met |
|
Change Control (9 Points)
(Result/Proof point (column A: enter Met/Unmet; Column B: enter relevant URLs/comments)
| NONRTRIC - Q1 2021 | |
Criteria | Result / Proof point | |
|---|---|---|
Public version-controlled source repository | ||
The project MUST have a version-controlled source repository that is publicly readable and has a URL. | Met |
|
The project's source repository MUST track what changes were made, who made the changes, and when the changes were made. | Met |
|
To enable collaborative review, the project's source repository MUST include interim versions for review between releases; it MUST NOT include only final releases. | Met |
|
It is SUGGESTED that common distributed version control software be used (e.g., git) for the project's source repository. | Met |
|
Unique version numbering |
|
|
The project results MUST have a unique version identifier for each release intended to be used by users | Met |
|
It is SUGGESTED that the Semantic Versioning (SemVer) format be used for releases. | Met |
|
It is SUGGESTED that projects identify each release within their version control system. For example, it is SUGGESTED that those using git identify each release using git tags. | Met |
|
Release notes | ||
The project MUST provide, in each release, release notes that are a human-readable summary of major changes in that release to help users determine if they should upgrade and what the upgrade impact will be. The release notes MUST NOT be the raw output of a version control log (e.g., the "git log" command results are not release notes). Projects whose results are not intended for reuse in multiple locations (such as the software for a single website or service) AND employ continuous delivery MAY select "N/A". (URL required) | Met | |
The release notes MUST identify every publicly known vulnerability with a CVE assignment or similar that is fixed in each new release, unless users typically cannot practically update the software themselves. If there are no release notes or there have been no publicly known vulnerabilities, choose "not applicable" (N/A). |
| N/A |
Reporting (8 Points)
(Result/Proof point (column A: enter Met/Unmet; Column B: enter relevant URLs/comments)
| NONRTRIC - Q1 2021 | |
Criteria | Result / Proof point | |
|---|---|---|
Bug-reporting process | ||
The project MUST provide a process for users to submit bug reports (e.g., using an issue tracker or a mailing list). (URL required) | Met |
|
The project SHOULD use an issue tracker for tracking individual issues. | Met | |
The project MUST acknowledge a majority of bug reports submitted in the last 2-12 months (inclusive); the response need not include a fix. | Met |
|
The project SHOULD respond to a majority (>50%) of enhancement requests in the last 2-12 months (inclusive). | Met |
|
The project MUST have a publicly available archive for reports and responses for later searching. (URL required) | Met | |
Vulnerability report process | ||
The project MUST publish the process for reporting vulnerabilities on the project site. (URL required) | Met | NONRTRIC: Bugs / Feedback / Vulnerabilities
|
If private vulnerability reports are supported, the project MUST include how to send the information in a way that is kept private. (URL required) Examples include a private defect report submitted on the web using HTTPS (TLS) or an email encrypted using OpenPGP. If vulnerability reports are always public (so there are never private vulnerability reports), choose "not applicable" (N/A). | Met | NONRTRIC: Bugs / Feedback / Vulnerabilities
|
The project's initial response time for any vulnerability report received in the last 6 months MUST be less than or equal to 14 days. If there have been no vulnerabilities reported in the last 6 months, choose "not applicable" (N/A). | N/A |
|
Quality (13 Points)
(Result/Proof point (column A: enter Met/Unmet; Column B: enter relevant URLs/comments)
|
| |
Criteria | Result / Proof point | |
|---|---|---|
Working build system | ||
If the software produced by the project requires building for use, the project MUST provide a working build system that can automatically rebuild the software from source code. | Met | Maven |
It is SUGGESTED that common tools be used for building the software. | Met | Maven |
The project SHOULD be buildable using only FLOSS tools. | ||