Why is WPA2 still being used??

Question

This a message I wrote recently in a forum that brought up my idea from a couple of years and every year I see new products/WIFI being released, but not changes so here it is again....and hopefully someone who works with the WIFI alliance can bring this to the table.
I think WPA 3 or 4 needs to come out...I have written on this in different areas and attempted to contact the Wifi Alliance (Austin Texas) with no luck because I can't afford a $15,000 membership... Also linked a stack exchange post I made talking about the SIMPLE change/additions and the post was deleted....SO here it goes
Current PSK formula is
DK = PBKDF2(HMAC−SHA1, passphrase, ssid, 4096, 256)
What this means is it uses HMAC-SHA1 with your passphrase/ssid, 4096 iterations, and produces a 256 bit key
So for the past 10+ years people have been able to create databases/rainbow tables, etc because your only solving for 1 piece of the formula.
First thing that needs to change is the number of iterations, 10+ years ago hardware could only bruteforce 100-300 passwords a second. The number of iterations needs to be increased in order to bring that change back in effect. Currently with GPU's this number reaches the 10's of thousands (actually more).
The next thing would be to change the salt to include the mac of the ***router or client/both so that each router brute forced would require starting from scratch
DK = PBKDF2(HMAC−SHA1, passphrase, ssid + Router mac***, 4096000, 256) *iterations are 100 times current..not sure if hardware can take this, again it would have to be tested, the number shown is just for illustration purposes.
Next we need to take the HUMAN element out of the Equation.
1) a password of 12 or more needs to be implemented
2) if not already present in the password entered, the router would then GIVE the user a couple of permutations that include at least TWO upper/TWO lower/TWO special characters/TWO numbers and make them choose one. In other words the router would not allow anything less than a more "sophisticated" password.
Another option would be that after the first formula is used and the client connects successfully the FIRST TIME.... the router then "remembers" that mac address and now the formula changes to
DK = PBKDF2(HMAC−SHA1, passphrase, ssid + Router Mac, RND, 256)
Where RND is a random number generated by the router 6-8 digits long for the iterations. Unless a "Hacker" just happened to catch the first handshake and then ran through the set standard 500,000 iteration formula and happened to find the password (being able to decrypt the aes256 exchange of RND), from that point on the formula would be different. This could be the same for the router, or even more secure, for each client connected. So the router would keep a table of Client macs and RND so when the client says "HELLO I want to connect" it would be done using the RND value/formula. If someone was to find how the RND value was saved on the client (physical access to the client) then it would be different for each client. After X many days/X many hours this could be re-set/established again using the first formula and AES256 as an option.
So this is just some Ideas, with todays technology/hardware it shouldn't be that hard to do. WPA2 is old and getting easier to crack. Many wordlists have been created that easily go up to 10 if not more... "hackers" have been generating wordlists for YEARS. Making the first formula iterations high enough to slow down the brute force attack, and then making the hacker start from scratch with the combination of SSID + Router Mac, PLUS add the fact that after the client is first set up/connected to that router making the number of iterations RND (6-8+ digits)........this just makes it VERY VERY VERY difficult for a wardriver to accomplish finding the password.
One last thing to add would be to encrypt the DEAUTH packets.. Currently a "wardriver" can deauth the client and when the connection is regained it captures the 4 way handshake...prevent this and again it would be a little more difficult to capture that handshake. Also even if it is captured and its not the FIRST time... it would be a RND value so the "wardriver" wouldn't know where to start, but from scratch. This time with every combination of a 12 character min password, and for each RND 6-8* digit of iterations...
Honestly with something like this implemented (which isn't too far fetched, especially the simple formula change adding router mac***), and possibly the Random Iterations, wardriving would almost become worthless. Currently a wardriver knows the formula and nothing changes so there is SOME hope that the user used a really easy password, but with the option above even trying the correct password wouldn't work (unless was the first time or a re-authentication time). Even still it would be with a new formula that uses 12 min password/more iterations.
Hopefully I don't get trashed on this post, all criticisms/ideas/opinions are open.

Answer 1

thank you for your reply..
Hopefully it will change... back when this idea was originally thought of (when attempting to vb.net a PSK just for fun), I took into account costs...thats why the changes are pretty simple depending on hardware.  I remember when WPA, WPA 2 first came out it, it was just the cost of a router/new devices (back then lots of money, now routers/hardware is less expensive), depending on the current hardware a simple coding could just be updated (firmware)...example the new WIFI Passport system could be implemented on older hardware once tested/certified...at least according to WiFi alliance.
The other reason for the change again is the 10+ years of using the same system, i understand it "secure" but with all the computer breaches/security breaches this is just one method to prevent it.  I would definitely upgrade if a newer secure encryption came out...however this really isn't a new encryption, same scheme, basically same formula with a different implementation, which is why I think a simple upgrade would be great...
so a real world example of the implementation..
Client says "Hello"
Router uses DK1 = PBKDF2(HMAC−SHA1, passphrase, ssid + Router Mac, 24576, 256) to encrypt a random number between 15000-30000 and uses it to send its message AES(16745 & message authentication, DK1).
Client uses DK1 to reverse it to get 16745/message authentication and now uses DK2 = PBKDF2(HMAC−SHA1, passphrase, ssid + Router Mac, 16745, 256) to AES(original message, DK2) in order to show the router that I have the original key/and have recived the new iterations.
The router now stores 16745 and the client stores 16745 from that point on when wanting to communicate with that mac address.  makes it totally random except the first formula.
anyway just a concept.. thanks for your reply again.