On Thu, May 31, 2018, at 05:13, Ryan Finnesey wrote: > we have been keen to architect the system that will interact > between the Registries and the Registrar to run within the public cloud. > Azure and or AWS. We had a discussion the other day about using Azure > Functions but had to quickly rule it out because EPP requirement on TCP > Sockets. Azure Functions only support http as a protocol . > > Has there been any conversation about the Registries using REST?
There has been in the past, see my earlier email in the thread. But noone implemented anything in that regard, from what I know. Also, it would be sad if the problem comes only from the fact that the use of come cloud is needed. I would provide maybe 2 ideas: - see Google GAE Proxy used for Nomulus because they have the exact same problem: the underlying App Engine supports only HTTP(S) so they needed a proxy from TCP/700 and TCP/43 (but the whois problem is kind of solved if you switch to RDAP) - the .BE registry "recently" migrated all their systems in the cloud too (AWS) so there is at least this solution that works. See https://www.dnsbelgium.be/en/news/first-european-cctld-cloud -- Patrick Mevzek p...@dotandco.com _______________________________________________ regext mailing list regext@ietf.org https://www.ietf.org/mailman/listinfo/regext
