>If SRV continues to specify _Proto choices from a separate IANA >registry, ....
It never did and does not now. There is no protocol name registry or _proto tag registry. (There is a S-NAPTR application protocol tag registry, but since it contains entries like "diameter.tls.tcp" this is not the registry you are looking for.) >In the case of _Proto names, the set is tiny, so the burden of >explicitly registering these names in an _underscore registry is not >onerous, given that it is the only way to ensure that name collisions >are avoided. I agree. The current set of _proto names used by SRV. NAPTR, and URI is sort of defined by examples and hints. RFC 2782 which defined SRV calls out _TCP and _UDP as interesting protocols and then waves its hands about possible other ones. It creates no registry. RFC 6335 calls out SCTP, DCCP, TCP, and UDP as interesting protocols, and then says that future protocols that support services should use the same services registry. It has a lot of advice for IANA, but it doesn't create a protocol name or tag registry either. RFC 2780 created a protocol number registry updated by RFCs 5237 and 7045. It has a "keyword" column, but many of the keywords include undesirable characters like +./. Most of the protocols are dead experiments from 20 or 30 years ago, and most of the live ones like ICMP aren't suitable for services. One possibility would be to add a tag column to that registry and populate it with the four tags that seem plausibly useful. But ugh. The other which I prefer is simply to put the four _proto tags into the new underscore registry. Add a note that they have subnames from the RFC 6335 services registry, and for anew new protocol tags try to to keep the protocol names consistent with the keywords in the protocol number registry. I see the universe of underscore tags falling into three categories. 1. Tags that mean something under a hostname. This includes the _proto tags and things like _domainkey and _vouch. 2. Tags that only mean something under a _proto tag. This is the set of service names in the RFC 6335 registry and _nnn (port number) used to name TLSA records. 3. Tags that only mean something under some other underscore tag. This is a very small list, _adsp._domainkey and _report._dmarc are the only ones I know. It would be useful to define the registry for the first kind of tags. The second already has a registry, the third is uninteresting since it has no collision issues. R's, John _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
