Hi!
Several years ago I added ipService to our LDAP Database, then I thought it's time to
update it.
Now I have a conceptual problem:
Some services have multiple protocols and port numbers. For example
"compressnet".
While it's possible to assign unique names like
cn=compressnet@2/tcp,...
cn=compressnet@2/tcp,...
cn=compressnet@3/tcp,...
cn=compressnet@3/udp,...
I wonder how a standard query for "compressnet" should look like.
Basically I'd like to leave out the port (@n), but the IANA registry is not unique.
I identified these:
compressnet
mit-ml-dev
sql-net
rap
meter
pip
csdmbase
csdm
nmsp
uma
raid-cd
...
optohost004
It seems ipService can have multiple values for ipServiceProtocol, cn, and
ipServiceProtocol, but wouldn't that silently assume that all port numbers are valid
for all listed protocols? For the example it would be any combination of (UDP,TCP) and
(2,3).
To me the only solution seems to force IANA to clean up the mess.
RFC-6335/BCP-165 claims: "Service names are the unique key in the Service Name and
Transport Protocol Port Number registry." (page 8)
Opinions?
Regards,
Ulrich
Show replies by date