Case-sensitiveness for stem/OU with AD

We configured the base DN for groups and members to be "OU=People,DC=domain,DC=umontreal,DC=ca"
We have a base Stem "UdeM" (not shown in DN)

We created the Stem "UdeM:Groupes" to match the already existing AD OU "ou=groupes,OU=People,DC=sim,DC=umontreal,DC=ca", but as you can see in the PSP Diff response below, the PSP doesn't match the built DN with the existing one. My guess would be the case difference in "ou=Groupes" vs "ou=groupes".

Right now it isn't causing much problem in our test environment; we were able to provision a group inside the mismatching Stem/OU, but it would be nice to not have all those errors. Would it be possible to have the same kind of parameter (caseSensitive=false) for stem provisioning in the PSP ?

Previously we let Grouper create the OUs in AD so I guess it created them with the right case, but in the future there will be a lot of "mapping" to the current AD directory (though we might import some of them with the Loader or PSP), so this might be a problem.

Time estimate : We will be going into production in a few months (~6 months) and would like some time to test the fix after it's released.

Example output of the PSP :
bin/gsh.sh -psp -bulkDiff

<psp:bulkDiffResponse xmlns:psp='http://grouper.internet2.edu/psp' status='success' requestID='2012/04/30-08:46:46.885'>
<psp:diffResponse status='success' requestID='2012/04/30-08:46:46.986'>
<modifyRequest xmlns='urn:oasis:names:tc:SPML:2:0' entityName='stem' requestID='2012/04/30-08:46:47.084' returnData='everything'>

• • <psoID ID='ou=Groupes,OU=People,DC=domain,DC=umontreal,DC=ca' targetID='ldap'/>
    <modification modificationMode='add'>
    <dsml:modification xmlns:dsml='urn:oasis:names:tc:DSML:2:0:core' name='description' operation='add'>
    <dsml:value>Groupes</dsml:value>
    </dsml:modification>
    </modification>
    </modifyRequest>
    <psp:id ID='UdeM:Groupes'/>
    </psp:diffResponse>
    [...]
    </psp:bulkDiffResponse>