In article <654358a9-10a9-52f3-c1e9-5f6e3392f...@dcrocker.net> you write: >>>> For URI records RFC 7553 says they're either named the same as SRV >>>> records, or they use enumservice names from the Enumservice
>> Patrik's and John 's postings notwithstanding, I'm still concerned about >> the proposed way of handling this, namely to rely on IANA to do a manual >> check of the two registries the URI RR might call on. First, it does >> not seem reasonable to me to impose that burden on the IANA staff and >> second a manual process like that is almost certain to produce errors. >Again, my concern is with handing IANA an on-going task -- making a >check every time they update the Attrleaf table -- that requires their >being perfect at detecting collisions with one or more other tables. Has anyone asked IANA whether they have an opinion on how hard this would be? For that matter, are there other registries with similar issues? Do they have or would they plan to write software to do the cross check automatically when one of the registries is to be updated? I wouldn't think it'd be much different from checking whether a single registry has duplicate entries. R's, John _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
