Re: [port-srv-reg] Aliased service names

[Lars Eggert <[e-mail]>]

Hi,

On 2010-9-3, at 10:27, Stuart Cheshire wrote:
> In most cases I believe these are *not* aliases. They're two different services inadvertently colliding on the port number. The service names are *not* aliases of each other in these cases because they're not the same service.
> 
> In this whole list I only see four names that look like aliases to me:
> 
> "name" looks like an alias for "nameserver".
> 
> "www" and "www-http" are aliases for "http".
> 
> "auth" may be an alias for "ident".
> 
> So it looks like we have a total of THREE service names that have aliases.

Not sure. For example:

> stun            3478/udp   Session Traversal Utilities for NAT (STUN) port
> turn            3478/udp   TURN over UDP
> stun-behavior   3478/udp   STUN Behavior Discovery over UDP
> 
> stun            3478/tcp   Session Traversal Utilities for NAT (STUN) port
> turn            3478/tcp   TURN over TCP
> stun-behavior   3478/tcp   STUN Behavior Discovery over TCP
...
> stuns           5349/tcp   STUN over TLS
> turns           5349/tcp   TURN over TLS
> stun-behaviors  5349/tcp   STUN Behavior Discovery over TLS

TURN is a backward-compatible extension of STUN. So if a client looks up "stun", a TURN server can offer service to that client. So a TURN server that wanted to support STUN would need to register both service names.

(Similarly, stun-behavior is backwards compatible with stun.)

Lars