Richard Fink has some information on the name table requirements for EOT:
I have implemented some of these in my TTX-based webfont pre-processing system and never had any problems with EOT.
I don’t think style-linking is a problem as long as it is restricted to the basic 4 RIBBI, same as for other MS apps.
For the CSS, I’d recommend a syntax like this:
This way, IE9+ loads the WOFF, which is usually what we want (then we can strip the EOT of all information not applied by EI6-8).
As far as I have tested, the CSS
font-family name can always be freely chosen and a mismatch is not a reason for EOT not working in IE.