Update tech-specs.md for ev reporting (#35)

### Proposed changes

Updated tech specs to account for this issue:

nginxinc/docs#1528

Problem: Give a brief overview of the problem or feature being
addressed.

Solution: Explain the approach you took to implement the solution,
highlighting any significant design decisions or
considerations.

Testing: Describe any testing that you did.

Please focus on (optional): If you any specific areas where you would
like reviewers to focus their attention or provide
specific feedback, add them here.

If this PR addresses an
[issue](https://github.com/nginx/documentation/issues) on GitHub, ensure
that you link to it here:

Closes #ISSUE

### Checklist

Before creating a PR, run through this checklist and mark each as
complete.

- [ ] I have read the [contributing guidelines](/CONTRIBUTING.md)
- [ ] I have signed the [F5 Contributor License Agreement
(CLA)](https://github.com/f5/.github/blob/main/CLA/cla-markdown.md)
- [ ] If applicable, I have added tests that prove my fix is effective
or that my feature works
- [ ] If applicable, I have checked that any relevant tests pass after
adding my changes
- [ ] I have updated any relevant documentation
([`README.md`](/README.md) and [`CHANGELOG.md`](/CHANGELOG.md))
- [ ] I have rebased my branch onto main
- [ ] I will ensure my PR is targeting the main branch and pulling from
my branch from my own fork
- [ ] If the change involves:
  - Code
  - Anything that resembles Personally identifying information (PII)
    - Make sure to use placeholders such as `<username>` in place of PII
- URLs (watch for
[typosquatting](https://support.microsoft.com/en-us/topic/what-is-typosquatting-54a18872-8459-4d47-b3e3-d84d9a362eb0))
  - Significant new/revised content
    
In these cases, the change will require at least two (2) approvals
before merging

Author: mjang

content/nim/fundamentals/tech-specs.md

@@ -27,7 +27,7 @@ You can deploy NGINX Instance Manager in the following environments:
 
 {{< include "nim/tech-specs/supported-nginx-versions.md" >}}
 
-## Sizing recommendations {#system-sizing}
+## Sizing recommendations for Managing NGINX Instances {#system-sizing}
 
 The following recommendations provide the minimum guidelines for NGINX Instance Manager. These guidelines ensure adequate performance, but for optimal results, we strongly recommend using solid-state drives (SSDs) for storage.
 
@@ -58,6 +58,18 @@ For environments requiring more resources, **large configurations** are suitable
 | 250                            | 4 vCPU | 8 GB RAM | 1 GbE NIC | 2 TB    |
 {{</bootstrap-table>}}
 
+### License and usage reporting only {#reporting-sizing}
+
+This section assumes you've configured NGINX Instance Manager to manage your NGINX instances for licensing and usage reporting only. NGINX commercial license and usage reporting is done in an “unmanaged” way, where NGINX sends a request periodically to NGINX Instance Manager solely for counting purposes. For more information, see how you would [Prepare your environment for reporting]({{< relref "/solutions/about-subscription-licenses.md#set-up-environment" >}}).
+
+Therefore, the requirements for NGINX Instance Manager when used solely for licensing and usage reporting are minimal.
+
+{{<bootstrap-table "table table-striped table-bordered">}}
+| Number of Data Plane Instances | CPU    | Memory   | Network   | Storage |
+|--------------------------------|--------|----------|-----------|---------|
+| n/a                            | 2 vCPU | 4 GB RAM | 1 GbE NIC | 20 GB   |
+{{</bootstrap-table>}}
+
 ### Sizing benchmarks for storage
 
 The following benchmarks focus on **disk storage** requirements for NGINX Instance Manager. Storage needs depend on the **number of instances** and **data retention periods** (in days). The benchmarks are divided into three configuration sizes: