The point I was making was that the use cases appear to be very small. Even where a name registry might use it, there appear to be actual solutions that don't use it. If you're bundling IDN domains, that's typically a server side policy. No epp necessary. If you're allowing user choice, then a dname within the zone of the registered name would certainly work. <- this option is still available to registrants of domains where bundling is handled by enforcing shared NS records.
As I said in my earlier email, I don't see harm in adding the mapping. Kal Feher Neustar Inc. Melbourne, Australia On 13/11/17, 11:09, "regext on behalf of 'Stephane Bortzmeyer'" <regext-boun...@ietf.org on behalf of bortzme...@nic.fr> wrote: >On Mon, Nov 13, 2017 at 02:26:00AM +0000, > Feher, Kal <Kalman.Feher@team.neustar> wrote > a message of 34 lines which said: > >> certainly in breach of current gTLD requirements for zone contents. > >There are not only ICANN-regulated registries. Besides the root (my >personal use case), there are ccTLD and also all the registries at >lower levels (they typically don't use EPP today but it may change). > >Also, this is a technical proposal, independent of the _current_ >policy. ICANN may accept DNAME in the future (they should). > >_______________________________________________ >regext mailing list >regext@ietf.org >https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_mailman_ >listinfo_regext&d=DwICAg&c=MOptNlVtIETeDALC_lULrw&r=_-v0M-gLiqWrtaHtP66hjS >Pyu3ePgw9YIihGxxybjqU&m=Dj_J_Do1FDcSWQXvXH_ohS0LMKQPdU6QE_Dqm1Tk71k&s=gIMG >bpcW488Th1pBS9qwmPUBj9QYGCZKTwjOzcso-98&e= _______________________________________________ regext mailing list regext@ietf.org https://www.ietf.org/mailman/listinfo/regext
