In article <20180114224928.5w3ktquyuxdz2...@mx4.yitter.info> you write: >On Sun, Jan 14, 2018 at 02:31:37PM -0500, John Levine wrote: >> >> There's little reason to put an ANAME into a TLD zone file. Whatever >> you wanted to do with one, you can do equally well with an ANAME at >> the apex of a 2LD. > >Which "you" are we talking about here? There are reasons to put ANAME >or DNAME, if you believe those things will work, that have to do with >parent-side policy. That can't be done on the child side because then >the parent has to monitor all its children, which sucks.
I don't understand the objection. Anyone can put a DNAME at the apex of a 2LD now, and if we invent ANAMEs, anyone will be able to put ANAMEs there too. As far as I'm aware, almost no gTLDs or ccTLDs police the contents of 2LDs now and when they do, it's for content rather than technical reasons, e.g., to be sure that a sponsored or restricted domain has the right kind of stuff. Are you anticipating TLDs that will allow only approved DNAMEs? That seems implausible and unenforcable to me. R's, John _______________________________________________ regext mailing list regext@ietf.org https://www.ietf.org/mailman/listinfo/regext
