I have read through the ILP addressing spec and there is no mention of support for IP addresses to be used, just the allocation schemes described.
I think this can be a hangup for developers since it requires an additional devops skillset to deploy named based routing which is beyond getting started in ILP.
We should have an option to have “explicit addressing” or some override for what might be considered private infrastructure nodes.
I arrive at this post because I have some ILP nodes in the same subnet and want to push some ILP packets around but I see some challenges in the routing. For all intents there is no DNS services. (unless I create them).
BTP works with IP
ILP over HTTP works with IP
The embedded ILP packet with addressing however enforces rules. That means that deep within a private network I have no way to simply specify an ILP address like ip.172.25.0.4.alice . In a private infrastructure or local ‘dev0’ setup the packet will get parsed at the first node and fail to get routed if no name resolution services are available.
I understand the addresses for the most part were not planned to be ‘user’ facing and that SPSP provides payment pointer abstractions.
Nonetheless the addressing is logical and should support an IP allocation scheme. Maybe it does and I missed it.
Thoughts? I am suggesting an ‘ip’ scheme.