Re: [port-srv-reg] [tsvwg] "assigned" ( vs. "registered"), and relates issues

[Joe Touch <[e-mail]>]

Hi, Alfred,

Taking this up a level to summarize. there are two points. Let me know
if this is consistent with your understanding...

Joe

------
#1 -- I think (correct me if wrong) that you want service names without
assigned port numbers, to be registered only for  specific protocols.

For services with assigned port numbers, we assign a triple:

	namestring	transport	portnum

There's no one index to that triple. The index is the
<namestring,transport> pair, i.e.:

	namestring,transport -> unique portnum

For services, I can see why we would assign (or, in this case, register):

	namestring	transport

------
#2 -- There's an interesting question of 'who gets to add transport
protocols to a service that exists', regardless of whether the service
has a port or not.

I think IANA can handle that as it happens. I had been assuming that
ownership of that was done at the time the service name was assigned,
but that clearly needs potential override for abandoned services, e.g.

------