what? IPv6 has been supported by major telecomunication equipment manufacturers for nearly 2 and a half decades by now.
It is just a matter of getting an inet6 prefix from your RIR/LIR, and configuring it in your network.
IPv6 is not hard nor is it difficult to implement, and its nitty gritty details are actually far more logically sound then IPv4. (ARP is a major paint point for instance in large networks, so is IP broadcast traffic).
Most large WAN networks have a core which is either label switched (MPLS) and this doesn't care about anything in regards to the protocol which it is transporting, or is doing dual stack already.
>It is just a matter of getting an inet6 prefix from your RIR/LIR, and configuring it in your network
Which is easier said than done. Since my ISP won't provide me with IPv6, requesting a block from my RIR is my only option.
However, I don't meet the requirements[0] for getting a block directly from an RIR (in my case, ARIN).
In fact, unless you have a fairly large internet-facing presence, RIR's won't even give you the time of day:
Have an IPv4 assignment from ARIN or one of its
predecessors
Intend to immediately be IPv6 multi-homed
Have 13 end sites (offices, data centers, etc.)
within one year
Use 2,000 IPv6 addresses within one year
Use 200 /64 subnets within one year
Hard to blame ARIN there, They have about 70 people working for them, they're not scaled to deal with every tom dick and harry coming to them for assignments.
>you can get provider independant IP space from a LIR.
My understanding was that it was primarily ISPs that filled the role of LIRs. Is that incorrect?
If so, how can I find an LIR in my area?
Edit: I should have added that I've looked around, but AFAICT, the only "provider independent" group handing out IP addresses in my area is ARIN. I may be missing something obvious, but I don't think my google-fu is so bad that I can't find it, if it does indeed exist.
Generally agree, for basic configuration it just works. But I was planning to use IPv6 in some network segments in my company. Providing proper VPN (road warrior style) for employees to access such network isn't simple with IPv6 where every address is routable over internet. Morver Fortigate devices we have don't have such functionality.
It is just a matter of getting an inet6 prefix from your RIR/LIR, and configuring it in your network. IPv6 is not hard nor is it difficult to implement, and its nitty gritty details are actually far more logically sound then IPv4. (ARP is a major paint point for instance in large networks, so is IP broadcast traffic).
Most large WAN networks have a core which is either label switched (MPLS) and this doesn't care about anything in regards to the protocol which it is transporting, or is doing dual stack already.