> David Conrad <mailto:d...@virtualized.org> > Sunday, September 21, 2014 2:10 PM > ... > > There are at least three implementations of 'alias mechanism for zone apex' > I'm aware of (DNS Made Easy's ANAME, PowerDNS's ANAME (same thing?), and > CloudFlare's "CNAME Flattening"). Not sure if they interoperable (or even if > there is a need for interoperability).
from the point of view of many operators and implementers (so, like dns made easy, powerdns, and cloudflare from your example above) there is almost certainly a disadvantage to interoperability and standardization here, that being economic, in that as long as this feature remains incompatible, a single vendor is likely to gain business via "lock in". my reason for preferring a standardized way to do this is to make it possible for a registrant to get primary name service from one vendor and secondary name service from one or more others vendors. i don't think it makes sense to question, inside the IETF, whether a vendor-independent interoperable standard is desirable. we can ask questions of the form "but is this good engineering?" or "is this the best way to do it?" or even "what should the applicability statement be?" but since the IETF's stated purpose is to promote interoperable standards, if we want to argue about whether we need an interoperable standard for this widely-used feature, we should move that thread to a non-IETF forum where it would not be a nonsequitur. -- Paul Vixie
_______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
