Some NSEC3 names are (unexpectedly) lower case
As observed while troubleshooting a support issue, although it causes no validation problems (names are case-insensitive) we were surprised to encounter NSEC3 hash names that were all lower case in the zone.
BIND was the only signer, and all other NSEC3 hash names were upper case.
Is there a corner case scenario in which the lower-cased names are used when creating an NSEC3 RR?