The second issue is the login procedure. Today, NIMS has contextless login. It doesn't need to know the context since every user ID is unique. Under the model outlined above, users would somehow need to specify a context when logging in. This brings up a number of other sticky issues.
Context management becomes a nightmare in such a scenario.
By allowing domains to be included in the User object name, NIMS can provide mail services to users who have the same user ID in different Internet domains. By supporting NDS user object names in Internet e-mail format, NIMS allows users with the same ID to exist in the same or different contexts. With this structure, you can organize users in contexts alphabetically, geographically, or in other ways without respect to the domain name. This usually results in fewer NDS contexts and thus provides better overall performance. Limitations to Keep in Mind When implementing this scenario in NIMS, you need to be aware of a few limitations.