On 13/01/2016 20:09, John Levine wrote:
When Dave and I last discussed that draft in any detail (back in
Orlando!) my proposal was that it should for SRV-based services the only
entries should be _tcp and _udp (or other L3 protocols), and that
anything that exists in the IANA port registry (with the prepended
underscore) would be a legal label to the left of that.
I think we're in violent agreement -- that's why I want to put _client
into the service registry so it doesn't further mess up the list of L3
protocols.
Right, except that I want that service registry to only include the
most-significant-label.
Yes, there's then a recursive situation in my proposed order where the
stuff to the left of that also then potentially comes out of the service
registry. To me, though, that's preferable from having the _client
label separate the existing _<service> and _<proto> labels that SRV uses.
Ray
_______________________________________________
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop
