Is your feature request related to a problem? Please describe.
When reporting network_counts in the UI or derived database products (such as JSON, CSV, or KMZ exports) the counts include Internet Exchange owned and operated networks such as route servers and, lately, $cdn caches.
Who is affected by the problem?
Users of PeeringDB
What is the impact?
The resulting count of networks is artificially inflated; the intent of net_count is to display an indicator of peering opportunity. Counting the IX route servers and appurtenances isn't part of that peering opportunity since they're considered IX infrastructure. Without at least one network to peer with, the value of that infrastructure is zero hence shouldn't be reported in network_count.
Are there security concerns?
No.
Are there privacy concerns?
No.
Describe the solution you'd like
Stop counting IX affiliated infrastructure as network peering opportunity which is reflected in net_count as well as passed through to various products.
Do you think this feature will require a formal design?
Perhaps. Increasing cost would make this not worthwhile. As well, its worth considering if this is just too minor to matter. However, while its available to code in the UI less sophisticated users relay on the UI and it's derivations so accuracy is key.
Could this feature request need support from the Admin Committee?
No.
arnoldnipper
commented
3 weeks ago
Is your feature request related to a problem? Please describe.
When reporting network_counts in the UI or derived database products (such as JSON, CSV, or KMZ exports) the counts include Internet Exchange owned and operated networks such as route servers and, lately, $cdn caches.
Who is affected by the problem?
Users of PeeringDB
What is the impact?
The resulting count of networks is artificially inflated; the intent of net_count is to display an indicator of peering opportunity. Counting the IX route servers and appurtenances isn't part of that peering opportunity since they're considered IX infrastructure. Without at least one network to peer with, the value of that infrastructure is zero hence shouldn't be reported in network_count.
Are there security concerns?
No.
Are there privacy concerns?
No.
Describe the solution you'd like
Stop counting IX affiliated infrastructure as network peering opportunity which is reflected in net_count as well as passed through to various products.
Do you think this feature will require a formal design?
Perhaps. Increasing cost would make this not worthwhile. As well, its worth considering if this is just too minor to matter. However, while its available to code in the UI less sophisticated users relay on the UI and it's derivations so accuracy is key.
Could this feature request need support from the Admin Committee? No.
What is the proposed priority? Low.
Provide a rationale for any/all of the above
Data quality improvement.