i think an ANAME whose only purpose was to inform some outer process that AAAA and A RRsets should be copied from somewhere periodically using RFC 2136 UPDATE messages, could be useful if some name server implementors decided to offer the feature of doing this internally, "as if UPDATE had been done" but not actually requiring a cron job and perl script and so on. it would likely be seen as a reasonable compromise by the CNAME flattening DNS hosters of the era, and may lead to interoperability.
for better dynamicism we should be pushing SRV. and there's no reason why an FYI document couldn't explain how to use an apex SRV to inform an UPDATE of apex AAAA and A RRsets. this, too, could be added as a nonstandard enhancement to authority servers who could do it internally, without cron or perl. it's very likely that the high volume sites of the world will just go on using CDN as before, where every apex AAAA or A query is crafted by load estimating or triangulation software, no matter what we do here. however, something like ANAME, or something like ANAME but based on apex SRV, could be used to inform that estimation/triangulation, and could lead to greater interoperability. i'm not sure CDN's currently want interoperability, due to competition concerns, but i expect that their customers would like a multi-CDN option to avoid lock- in. in other words i don't think there's a glaring need for elegance on this one. vixie _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
