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

[Olafur Gudmundsson <[e-mail]>]

At 05:01 15/01/2010, Magnus Westerlund wrote:
>Olafur Gudmundsson skrev 2010-01-14 15:13:
> > At 03:39 13/01/2010, Lars Eggert wrote:
> >
> >> > IMO, this basically treats SRV names as old port numbers were treated -
> >> > i.e., ask for a name, get ALL transports. That's how port number
> >> > assignments were done until recently, where now only the needed
> >> > transport is assigned.
> >> >
> >> > So IMO a service means something only relative to a transport. However,
> >> > it'd be useful to require the transport be specified only if the same
> >> > name would mean different things for different transports. Do we ever
> >> > see that happening?
> >>
> >> Right. Or, in other words, if you have a service name, it's yours for
> >> all transports, just as ports used to be. (There are so many service
> >> names that we can burn combinations that aren't used, and limit
> >> interactions with IANA.)
> >>
> >> Lars
> >
> > The important point is:
> > Each service is going to have one or more transports that are "preferred",
> > these preferences need to be noted in the registry.
> > (this point applies both to port allocations and service names).
> >
> > See section 5.1 of
> > http://tools.ietf.org/html/draft-gudmundsson-dnsext-srv-clarify-00
> >
> > for proposed search order when priority order is not known.
> >
>
>I thought this was going to be covered in the reference that explains
>how the SRV is used with service X. I think that is the most appropriate
>place to indicate which protocols are expected to be supported and for
>which usages which is the most appropriate.
>
> >From the Service name registry point of view this is not needed
>information. However, I agree that for the user of the service name it
>is clearly of interest. But as I said before, it is service specific.
>
>Cheers
>
>Magnus Westerlund


What Alfred and I envision (and apps people correct me if I'm wrong):
The SRV update document specifies a default order of transports to use,
the registry in the Notes field[1] stores transports in priority order
for a service if different from default.
If a service does not envision using SRV then that should be noted.

The document/application for service lists the priority order when
different from the default.

[1] We can add a special column to the Service registry for transport list.

         Olafur