Granting all you say, I think I expressed it badly by using the word "available" (edited to "accessible"). In somewhat anthropomorphic terms:
If a device of any sort has an internet address then I can make a (logical) connection to it. Granted, it may decide to ignore me, but in order to ignore me it has to know I'm there.
If it's an IPv6-only device and I'm using IPv4 I can't even get to that stage!
Not really. Plenty of nodes have IP addresses that are legitimate and you can't access them in any way, shape or form as their prefixes aren't advertised to you. From your point of view they don't exist.
Further devices with routable addresses don't need to know you're there to ignore you - you'll get nowhere near them before something else ignores you. Try reaching the /29 I have at home you'll get blocked when you hit the /32 on the router in front of them
Yet more have IP addresses but you are not permitted to talk to them - they have no visibility of you whatsoever, they don't talk IP natively they just carry it and unless you access the via a specific path you're getting nothing from them.
13 brnt-ic-1-ae0-0.network.virginmedia.net (62.254.42.198) 112.523 ms 205.923 ms *
14 * * *
15 * * *
16 * * *
17 leed-core-2a-ae4-0.network.virginmedia.net (82.15.94.254) 77.059 ms 85.573 ms 61.107 ms
18 lee2-cmts-14-tenge412.network.virginmedia.net (80.0.50.198) 72.855 ms
lee2-cmts-14-tenge413.network.virginmedia.net (80.0.50.202) 65.216 ms *
14, 15, 16 all speak IPv4 and v6. Neither are interested in responding unless you know exactly how to talk to them.
The other side of hop 17 was actually manc-bb-2a-ae4-0.network.virginmedia.net. brnt-bb-2a-ae4-0.network.virginmedia.net was possibly hop 14. All have IP addresses, none of them talk to you unless you address them specifically.
With that in mind it's a very, very tricky precedent to set had they started down this road.
I see your point but with all the encapsulation options available it's tricky. A number of devices use neither IPv4 or IPv6 as their main native protocol, they only carry it and respond to it from restricted management networks.
So do we start preventing VRFs too as they restrict parts of Internet-connect devices from reachability via IP? Force ISPs to advertise all VRFs to customers via some IGP so that they can reach all devices on the publicly reachable Internet the ISP is responsible for?
Core internet protocols. Where's my MPBGP session from my provider? Core protocol.
Can of worms I don't think anyone wants to open.
Building better networks, not just faster ones.
Edited by CarlTSpeak (Fri 06-Dec-19 10:24:01)