I hate to say it but, there is no one right way to do things, I guess thats the beauty of it. Its going to depend on how your organization is shaped, admin, circuts, etc. People are going to try and tell you one way or another how it should be, honestly, if your asking anyone with the amount of information you have given and they give you a straight answer, dont listen. While security might be an issue, Microsoft and Compaq both went with a single domain modle. Thats what OU's, Delegation and Group Pol's are all about. I think having an empty root domain keeping things flexable at the root sounds like a good idea, perhaps even having two child domains in which perhaps two diverse areas make sense, again guessing from what little I have. The more you add to the mix though, the more planing you should be doing, if done right AD makes your life a dream, poor planing and its going to be no better then most peoples NT domains that were out there. Keep it simple! Make sure your getting people from all departments involved with the design phase, getting buy in. MOST important, your designing AD around the business, not the business around AD. AD is nothing more then a database, the yellow pages and if you make it too difficult, people wont use it to its potential and in effect you will end up with nothing more then a fancy User Manager For Domains. Nuff
Pete