Are there any plans to fix the misinterpretation of the Exchange ActiveSync policy "Minimum number of character sets" in IOS6?

Question

We are testing using IOS6 in our Corporate environment and came across a scenario where IOS6 incorrectly interprets the Exchange 2010 ActiveSync policy "Minimum number of character sets" as the number of special characters required rather than the number of character sets required. Is anyone aware of any plans to correct this in future releases? Here is a thread on Microsoft's forums about the issue:
http://social.technet.microsoft.com/Forums/en-US/exchangesvrmobility/thread/fe05 1d55-24ba-45e4-b054-67861f28422d/

Answer 1

We have tried Android, Windows Phone7/8 and they all adhere to the "Minimum number of character sets" set in the ActiveSync policy, but IOS does not.
Require an alphanumeric password   Select this check box to require device passwords to contain both numbers and letters. The default is numbers only.
Passwords must include this many character sets   To enhance the security of device passwords, you can require passwords to contain characters from multiple character sets. Select a number from 1 to 4. The sets are letters, uppercase letters, numbers, and symbols. For example, if you select 3, passwords must contain characters from three of these sets.
All other mobile device except IOS 5.x/6.X don't follow this.
You have to select "Require an alphanumeric password" which is letters and numbers.  But then you can only select 1-4 for the character sets. 
So we set it at 1, so that would mean you would only need letters and numbers, IOS does not reconize letters, letters uppercase, numbers or symobols as a charator set, it interprets the setting as how symbols you need.
If you set it at 2, then IOS makes you have "2" symbols in your password.....and so on...
Make sense?
It just seems that IOS does not reconize charator sets, it just looks at the number as how many symbols you need in a password.