I very much like the idea of this draft, given that I use multiple DNS hosting providers who all have their own unique (and proprietary) way of doing "CNAME flattening at the apex". I think the reality of today's user experience with domain names is that we are increasingly dropping the "www" or any other kind of second-level domain. So we want to talk about our sites as "example.com<http://example.com>" ... but as the publisher we want to use CDNs, load balancers and other systems that need us to use a CNAME. A standardized way of doing this would be helpful.
One comment... On Mar 30, 2017, at 7:13 PM, Evan Hunt <[email protected]<mailto:[email protected]>> wrote: (Incidentally, I'm working on a somewhat more ambitious ANAME draft with Peter van Dijk and Anthony Eden, who has kindly agreed to merge his efforts with ours. I expect to post it in a few days, stay tuned.) ... I think it would be helpful for the new draft to have a few examples of what the RR would look like in a zone file. (This was the one component I found missing from Anthony's ALIAS draft.) Thanks for doing this, Dan -- Dan York Senior Manager, Content & Web Strategy, Internet Society [email protected]<mailto:[email protected]> +1-603-439-0024 Jabber: [email protected]<mailto:[email protected]> Skype: danyork http://twitter.com/danyork http://www.internetsociety.org/
_______________________________________________ DNSOP mailing list [email protected] https://www.ietf.org/mailman/listinfo/dnsop
