I'm not blocking really, just fail to understand the need to "reserve" a
port
range in Osmocom. We're not going to fork
iana.org. It is far too easy to just
pick some random port range that is unlikely to ever collide with Osmocom.
I think I don't really grasp the "deployment-specific" part yet.
On Mon, Dec 25, 2023 at 12:43:50AM -0800, Mychaela Falconia wrote:
The table in the wiki page already lists 5000 as A/IP
for osmo-bsc_nat.
I am now thinking about 5100 to 5199 range.
or 6000 or 10001. There will always be some program or some service out there
that picked a port in the same range. Ultimately it's up to each individual
site to avoid conflicts. Same with picking RTP port ranges for osmo-mgw.
When we designate a port range for use by sites, that may *encourage*
developers from various third party projects to create port collisions between
their projects, because we sort of ask them to stay within that range.
Please note the "deployment-specific"
language I propose above. If I
deployment-specific == site-specific?
When your applications are site specific, then you can adjust the ports to your
site?
~N