Hi Pascal, This is an interesting idea.
As for the RDAP portion, there is an existing 'links' JSON structure which you may also leverage instead of creating a new structure. If you are just providing links, that may be easier. If you need additional data, then a separate structure is probably appropriate. I hope this helps. -andy On Fri, Jun 3, 2016 at 11:31 PM, Pascal Bouchareine <pas...@gandi.net> wrote: > Greetings from Gandi, > > Inspired by the current ietf-draft on 3rd party operator to > registrar/registry, for which we're hoping to publish an experimental > service soon, we've been digging into RDAP-based discovery of registrar > or dns operator services (or documentation) - and how end user > experience can be improved. > > I've contacted Gavin Brown about his rdap.org experiment - and he kindly > gave me a lot of interesting pointers, including this list. > > We've pushed a draft here: > https://github.com/Gandi/dnsknife/blob/master/docs/extending_registrar_functions.txt > > > We also setup a few experimental services to test the idea: > - rdap.gandi.net > - partners.gandi.net has a rough welcome process and implements NS > changes > - ten.pm is basically faking a 3rd party operator > - rdap.io is a temporary glue, to make the documentation part work with > more registrars > > We would love to hear feedback and maybe find other interested parties > wanting to work on this with us. > > Regards, > Pascal > > > _______________________________________________ > regext mailing list > regext@ietf.org > https://www.ietf.org/mailman/listinfo/regext _______________________________________________ regext mailing list regext@ietf.org https://www.ietf.org/mailman/listinfo/regext
