No, iris has not been widely deployed. My point is that if there were some reason to have this data available in a convenient machine readable format, then iris would already be deployed. That there's no uptake seems to me to be an indication that registries don't want additional costs. So they won't sign up to expand their dns operation costs for these purposes either.
If they _will_ spend on this, then it seems to me the deployment cost for an existing protocol will be lower than for one we still have to invent. A -- Andrew Sullivan <a...@shinkuro.com> On 2010-11-21, at 13:13, Lawrence Conroy <lcon...@insensate.co.uk> wrote: > Hi Andrew, folks, > Does anyone actually use IRIS? > Telling someone to "go look over here for IRIS" seems like telling them > everything has to be in XML (only squared). > DNS provisioning and lookup for TXT in "srv-like" sub-domains is easy and > cheap (for implementers). > Provisioning, querying and parsing and IRIS data is not, I'd venture. > > So ... is your comment "Why do that?" really meant as "Why make life easier > for malcontents and spammers"? > > all the best, > Lawrence > > On 21 Nov 2010, at 17:41, Andrew Sullivan wrote: >> On Sun, Nov 21, 2010 at 05:33:12PM +0000, Paul Vixie wrote: >>> how would the registry system implement something like this? >> >> I would argue that they shouldn't. >> >>> i know there are a lot of related proposals in XML. that's another topic. >> >> No, it isn't. It's one thing to say, "Go look over here for IRIS." >> It's quite another to try to duplicate all that in the DNS itself. >> Why do that? >> >> A > > _______________________________________________ > DNSOP mailing list > DNSOP@ietf.org > https://www.ietf.org/mailman/listinfo/dnsop _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
