Hi @yotam Trade secret - if we need IPv4 services we just use our own server to call and aggregate that data, and then serve that data to the IC via IPv6 Outcalls. Why?
a. We can control the way the data looks, prune it, before is gets replicated across a subnet.
b. If there are a chain of calls needed and we only care about the final result… we just need an endpoint for the final result in the IC.
c. We can have the server in our physical possession or a controlled environment. (only bad things happen if we let them) Cannot say the same about calling a third party provider directly from the IC.
- Do you think HTTPS outcalls should support IPv4 destinations?
Would it be convenient? yes. Many prominent and trusted services have IPv6 endpoints.
This is a bit like adding Oauth into Internet Identity because most people use Gmail login.
Future proof is my bias.
- Do you have any suggestions or comments on the proposed solution?
Your proxy idea seems correct.
- Do you have any preferences on the default pricing options?
Engineers will most likely do what we do if IPv6 is not available for a API provider. Build their own aggregator and serve it via IPv6. Particularly if there is a price difference.
- Do you see any other options or do you have any suggestions?
Secure data enclaves have more business use cases to pull new orgs into the IC. I would like that to be high on the dev to-do list 