Re: [port-srv-reg] Survey of current service (port) names

[Joe Touch <[e-mail]>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



Magnus Westerlund wrote:
> Hi,
> 
> I am actually getting a bit confused by this whole debate. Are the port
> registries "keyword" used in the getservname? 

There are different registries:

	IANA's TCP/UDP number registry
	Stuart's name-only registry (SRV service types, rfc2782)
	IANA's SCTP registry
	IANA's DCCP registry

Currently, all three have different rules for names:
  IANA legacy - 15 chars, start a-z0-9, interior/end .+*/_-, use cases
  IANA new names -
	as specified on the application - 14 characters (no other rules)
	as reviewed - 14 chars, start a-z0-9, interior -, no case
  DNS SRV service types - 14 chars, start/end a-z0-9, include -, no case
  SCTP names - (no length specified) a-z0-9 .+*/_-, use cases
  DCCP names - (no length specified) a-z0-9 .+*/_-, use cases

> What other usages are
> there real for the "keyword"?

TCPMUX defines their use. My TCP portnames draft did too (expired, but
still bumping around). Neither one is particularly sensitive to the
characters used.

> We are trying to merge three different registries because there usage
> seems to have gotten entangled. Are there other ways we could untangle
> them?

SCTP and DCCP did NOT subsume existing IANA TCP/UDP names, though they
could easily have done so.

SRV names claim to subsume existing IANA ports when created, but many
are not listed. New IANA assignments are required to register with the
SRV service type registry separately.

We could redefine the names to use the IANA legacy rules, which are a
superset of all the rules. The key question at that point is whether
this breaks anything - presumably only DNS SRV use would be an issue,
since everything else either uses primarily the numbers IANA assigns
rather than the names, or uses the name as an opaque string
(getsrvbyname, TCPMUX, TCP portnames).

Joe
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkomlcAACgkQE5f5cImnZrt/4ACbBzt6lZk8Lh3XTXm1CqjOtehi
ZrgAoJVbiekvFgiR+OKPj4ruP8F9BYXC
=71R5
-----END PGP SIGNATURE-----