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

[Magnus Westerlund <[e-mail]>]

Hi Alfred,

I have now read draft-gudmundsson-dnsext-srv-clarify-00 again.

Me personally hasn't really digged into the issues that you bring up in
your document, I don't think I am alone in this. Thus, I think it would
be jumping to conclusions that there are agreement on your suggested
approach simple because you haven't received comments on them yet.

>From the perspective of trying to advance draft-ietf-tsvwg-iana-ports,
we do come down to trying to find the reasonable interface between our
documents.

On the issue of the protocol label for a given service name. I find it
reasonable that your document do extended the registry with an
additional column that enumerates any non-default protocol label order.
I get the impression that you want this to be described in
draft-ietf-tsvwg-iana-ports due to that it should be included in any
service name registration request.

I had hoped that we could avoid normative dependencies from IANA ports
towards draft-gudmundsson-dnsext-srv-clarify. This to enable
draft-ietf-tsvwg-iana-ports to be approved and published as soon as
possible.

>From my perspective I see three ways forward:

1. We write nothing about the protocol label in regards to Service name
registrations and lets draft-gudmundsson-dnsext-srv-clarify update the
Registration RFC.

2. We include some text about the need to specify protocol label
priority list unless the default one (also included listed in
draft-ietf-tsvwg-iana-ports) but pushing of the explanation about the
issues to your document using a normative reference.

3. We fudge something together in the middle trying to avoid a normative
reference.

I think I am leaning towards 1 personally even if it has some obvious
downside in that the registration rules information will not be
contained to a single document. However, I think IANA's registration
template can clearly make it clear to applicants that you need to read
things in both.

Cheers

Magnus Westerlund

IETF Transport Area Director
----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM
----------------------------------------------------------------------
Ericsson AB                | Phone  [phone]
Färögatan 6                | Mobile [phone]
SE-164 80 Stockholm, Sweden| mailto: [e-mail]
----------------------------------------------------------------------