On Sun, Nov 12, 2017 at 10:50:51AM +0800, Kim Davies <kim.dav...@icann.org> wrote a message of 32 lines which said:
> Just one of the many things that would need to be looked at is how > to transmit DNAME provisioning requests via EPP. I don't know if > there is even an EPP mapping for this. Interesting remark. I indeed did not find one. It should probably be a small extension of RFC 5731: C: <domain:create C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.1"> C: <domain:name>example.com</domain:name> C: <domain:period unit="y">2</domain:period> C: <domain:dname>empty.as112.arpa</domain:dname> C: <domain:registrant>jd1234</domain:registrant> C: <domain:contact type="admin">sh8013</domain:contact> C: <domain:contact type="tech">sh8013</domain:contact> C: <domain:authInfo> C: <domain:pw>2fooBAR</domain:pw> C: </domain:authInfo> C: </domain:create> I'll ask regext tomorrow about it :-) > We haven't studied what would be involved, but I feel confident in > predicting the whole exercise would be non-trivial. But there is no choice. If we decide to delegate .internal to AS112 (*if*: see Joe Abley's message), we cannot use NS records because the AS112 servers won't recognize the new TLD, and there is no way to change them all these servers (RFC 7535, section 1). _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
